64
Requirements for the GCCS-M Replacement based on Land Forces Systems Elisa Shahbazian Prepared By: OODA Technologies Inc. 4891 Grosvenor Montreal (Qc), H3W 2M2 PWGSC Contract Number: W7707-145677 CSA: Liesa Lapinski, DRDC Atlantic Research Centre, (902) 426-3100 Ext. 180 The information contained herein is proprietary to Her Majesty and is provided to the recipient on the understanding that it will be used for information and evaluation purposes only. Any commercial use including use for manufacture is prohibited. The scientific or technical validity of this Contract Report is entirely the responsibility of the Contractor and the contents do not necessarily have the approval or endorsement of the Department of National Defence of Canada. Defence Research and Development Canada Contract Report DRDC-RDDC-2015-C013 April 2015

Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

  • Upload
    others

  • View
    0

  • Download
    0

Embed Size (px)

Citation preview

Page 1: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Requirements for the GCCS-M Replacement based on Land Forces Systems

Elisa Shahbazian

Prepared By OODA Technologies Inc 4891 Grosvenor Montreal (Qc) H3W 2M2

PWGSC Contract Number W7707-145677

CSA Liesa Lapinski DRDC ndash Atlantic Research Centre (902) 426-3100 Ext 180

The information contained herein is proprietary to Her Majesty and is provided to the recipient on the understanding that it will be used for information and evaluation purposes only Any commercial use including use for manufacture is prohibited

The scientific or technical validity of this Contract Report is entirely the responsibility of the Contractor and the contents do not necessarily have the approval or endorsement of the Department of National Defence of Canada

Defence Research and Development Canada Contract Report DRDC-RDDC-2015-C013 April 2015

copy Her Majesty the Queen in Right of Canada as represented by the Minister of National Defence 2015

copy Sa Majesteacute la Reine (en droit du Canada) telle que repreacutesenteacutee par le ministre de la Deacutefense nationale 2015

Requirements for the GCCS-M Replacement basedon Land Forces Systems

Elisa Shahbazian

Prepared By OODA Technologies Inc4891 GrosvenorMontreal (Qc) H3W 2M2514-476-4773

Prepared For Defence Research amp Development Canada Atlantic Research Centre9 Grove Street PO Box 1012Dartmouth NSB2Y 3Z7902-426-3100 ext180

Scientific Authority Anna-Liesa S Lapinski Defence ScientistContract Number W7707-145677Call Up Number 6Project Requirements for the GCCS-M Replacement based on Land Forces SystemsReport Delivery Date April 15 2015

The scientific or technical validity of this Contract Report is entirely the responsibility of thecontractor and the contents do not necessarily have the approval or endorsement of the Departmentof National Defence of Canada

ccopy Her Majesty the Queen in Right of Canada as represented by the Minister of National Defence 2015

ccopy Sa Majeste la Reine (en droit du Canada) telle que representee par le ministre de la Defense nationale2015

This page is intentionally left blank

Abstract

In April 2014 the Maritime Information Warfare (MIW) program called the Next Generation ofOperational C2 Systems has been initiated

The aim of this study is to better understand the functionality of the land systems to help definethe requirements of the sea system

This document contains the results of the analysis of over 200 open publications to evaluate andgain knowledge from existing modern land force systems and use that knowledge to identify suc-cessful and useful functionalities and processes that should be recommended for the successor ofGlobal Command and Control System-Maritime (GCCS-M) leading to specification of require-ments for the GCCS-M replacement These recommendations are also based on experience andknowledge gained in OODA Technologies past projects

Study Report RISOMIA Call-up 6

This page is intentionally left blank

ii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Contents

Contents iii

List of Figures v

1 Scope 1

2 Introduction 3

21 Past Projects 3

211 Command Decision Aids Technology (COMDAT) TDP 3

212 MUlti-Sensor Integration within the Common Operating Environment (MU-SIC) 4

213 Joint Fire Support (JFS) 4

214 Tactical Planning and Execution Management (TPEM) project 4

22 Outlines 5

3 Modern Land Force Command and Control (C2) Systems 7

31 Afghan Mission Network 7

32 Future Mission Network 16

33 Canadian Land Command and Control (C2) 21

34 Land Command and Control (C2) Applications in Coalition Operations 22

341 Land Command and Control Information Services (LC2IS) 22

342 Joint Automated Deep Operations Coordination System (JADOCS) 23

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS) 24

iii

Study Report RISOMIA Call-up 6

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC) 25

4 Global Command and Control System 27

41 Global Command and Control System - Maritime (GCCS-M) 27

42 Global Command and Control System - Joint (GCCS-J) 28

43 Global Command and Control System - Army (GCCS-A) 29

44 GCCS Future Evolutions 29

441 Maritime Tactical Command and Control (MTC2) 29

442 Net Centric Enterprise Services (NCES) 30

443 Joint Mission Planning System (JMPS) 31

5 Interoperability in Coalition Land Operations 33

51 NATO Programs for Interoperability 33

52 USA Programs for Interoperability 35

6 Recommendations for GCCS-M Replacement 37

61 SoftwareSystem Functions Recommended for Next Generation GCCS-M 37

62 Interoperability Recommendations 40

63 Procedure and Policy Recommendations 40

7 Conclusion 41

71 Challenges Encountered 42

72 Future Analyses 42

Bibliography 45

iv

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF FIGURES

List of Figures

31 AMN Concept 2012 reproduced from [3] 9

32 AMN Mission Areas reproduced from [4] 10

33 Services Provided in AMN Mission Areas reproduced from [4] 11

34 German participation in AMN reproduced from [13] 15

35 Mission Partner Environment reproduced from [19] 18

36 Participation Options reproduced from [20] 19

37 FMN Evolution Phases reproduced from [20] 20

38 Interoperability Operational Concept reproduced from [24] 23

39 MAJIIC Capability Development reproduced from [27] 25

41 GCCS-M Evolution reproduced from [32] 29

42 NCES Services reproduced from [34] 31

51 NNEC Development Strategies reproduced from [40] 34

52 GCCS-M transition to NECC reproduced from [42] 35

61 AMN Collaborative Functions reproduced from [43] 38

v

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

vi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

List of Acronyms

ABCS Army Battle Command System

ACO Allied Command Operations

ACROSS Allied Commands Resource Optimization Software System

ACO Allied Command Operations

ACT Allied Command Transformation

ADatP-3 Allied Data Publications number 3

ADO Adaptive Dispersed Operations

AMN Afghan Mission Network

ASCC Army Service Component Commands

ASTERIX All Purpose Structured Eurocontrol Surveillance Information Exchange

ATM Air Tasking Message

ATO Air Tasking Order

BCD Battlefield Coordination Detachments

C2 Command and Control

C2C Command and Control Capability

C2IEDM Command and Control Information Exchange Data Model

C2PC Command and Control Personal Computer

C3 Consultation Command and Control

C4AD C4 Assessments Division

C4I Command Control Communications Computers and Intelligence

C4ISR Command Control Communications Computers Intelligence SurveillanceReconnaissance

vii

Study Report RISOMIA Call-up 6

C5ISR Coalition Command Control Communications Computers IntelligenceSurveillance and Reconnaissance

CAGE Coalition Attack Guidance Experiment

CAOC Combined Air Operations Centre

CCIRM Collection Coordination and Intelligence Requirements Management

CENTRIXS Combined Enterprise Regional Information Exchange System

CENTRIXS-GCTF Combined Enterprise Regional Information Exchange System-GlobalCounterterrorism Force

CFWC Canadian Forces Warfare Centre

CIAV Coalition Interoperability Assurance and Validation

CJTF-76 Combined Joint Task Force ndash 76

CMT Coalition Mission Threads

COA Courses of Action

COCOM Combatant Command

COA Courses of Action

COE Common Operating Environment

COP Common Operational Picture

COPIM Criminal Organisation Public Interest Monitor

CORSOM Coalition reception staging amp onward movement

CTSB Counter Terrorism Security Bulletin

CTSF Central Technical Support Facility

CTTP Coalition Tactics Techniques and Procedures

CWIX Coalition Warrior Interoperability Experiment

DDR Disarmament Demobilization and Reintegration

DoD Department of Defense

DP Deterrent Presence

DRDC Defence Research and Development Canada

DSAR Dissemination Storage Archival and Retrieval

ESM Electronic Support Measures

viii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

EVE Effective Visible Execution

FDR Fielding Decision Review

FFI Friendly Force Information

FMN Future Mission Network

FMV Full Motion Video

FP Focal Point

GAMMA Global Aggregated Model for Military Assessments

GCCS Global Command and Control System

GCCS-A Global Command and Control System-Army

GCCS-J Global Command and Control System-Joint

GCCS-M Global Command and Control System-Maritime

GIS Geographic Information System

GPS Global Positioning System

HMART Human Intel Management amp Reporting Tool

ICC Integrated Command and Control for Air Ops

ICTC ISAF Interim Consignment Tracking Capability

ICTS ISAF Interim Consignment Tracking System

IFF Identification Friend or Foe

IFTS ISAF Force Tracking System

IGeoSIT Interim Geo-Spatial Intelligence Tool

ISAF International Security Assistance Force

ISR Intelligence Surveillance Reconnaissance

ITAS Intra Theatre Air Support

JADOCS Joint Automated Deep Operations Coordination System

JC3IEDM Joint Consultation Command and Control Information Exchange Data Model

JCOP Joint Common Operational Picture

JDARTS Joint Defence Planning Analysis amp Requirements Toolset

JFS Joint Fire Support

ix

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

JITC Joint Interoperability Test Command

JMPS Joint Mission Planning System

JOCWatch Joint Operations Center Watch

JOPES Joint Operation Planning and Execution System

JTS Joint Targeting System

LC2IS Land Command and Control Information Services

LCSS Land Combat Support System

LOGFAS Logistics Functional Area Services

MAJIIC Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition

MC Military Committee

MCOC Marine Corps Operation Center

MedRPT Medical reporting

MedWATCH Medical operations watch

MEF Marine Expeditionary Force

MIDB Modernized Integrated Database

MIP Multilateral Interoperability Programme

MPE Mission Partner Environment

MIST Medical Illness Simulating Trauma

MN Mission Network

MOC Maritime Operations Center

MTC2 Maritime Tactical Command and Control

NAC North Atlantic Council

NATO North Atlantic Treaty Organization

NCES Net-Centric Enterprise Services

NCI NATO Communications and Information

NECC Net-Enabled Command Capability

NETOPS Network Operations

NFIP NATO FMN Implementation Plan

x

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

NIRIS Networked Interoperable Real-Time Information Services

NISP NATO Interoperability Standards and Profiles

NITB NATO Intel Tool Box

NNEC NATO Network Enabled Capability

NRT Near-Real-Time

NSCD NATO SIMPLE Compliant Device

OANT Online Analyser for Networked Tactical Data Link

OEF Operation Enduring Freedom

OODA Observe Orient Decide Act

OTH-Gold Over-the-Horizon-GOLD

PFPS Portable Flight Planning System

PPR Prior Permission Required

RCN Royal Canadian Navy

REACT Radar EW and Communications Coverage Tool

RFID Radio-frequency identification

RFIMS Request for Information Management

RSOI Reception Staging Onward Movement and Integration

SA Situational Awareness

SADI Situational Awareness Data Interchange

SAFE SIGINT Analyst Functional Environment

SDA SEWOC database application

SDM Supply Distribution Model

SEWOC SIGINT amp EW Operations Centres

SIGINT Signals Intelligence

SIMPLE Standard Implementation for Multiple Platform Link Evaluation

SIPRNet Secret Internet Protocol Router Network

SME Subject Matter Expert

SOA Service-Oriented Architecture

xi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 2: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

copy Her Majesty the Queen in Right of Canada as represented by the Minister of National Defence 2015

copy Sa Majesteacute la Reine (en droit du Canada) telle que repreacutesenteacutee par le ministre de la Deacutefense nationale 2015

Requirements for the GCCS-M Replacement basedon Land Forces Systems

Elisa Shahbazian

Prepared By OODA Technologies Inc4891 GrosvenorMontreal (Qc) H3W 2M2514-476-4773

Prepared For Defence Research amp Development Canada Atlantic Research Centre9 Grove Street PO Box 1012Dartmouth NSB2Y 3Z7902-426-3100 ext180

Scientific Authority Anna-Liesa S Lapinski Defence ScientistContract Number W7707-145677Call Up Number 6Project Requirements for the GCCS-M Replacement based on Land Forces SystemsReport Delivery Date April 15 2015

The scientific or technical validity of this Contract Report is entirely the responsibility of thecontractor and the contents do not necessarily have the approval or endorsement of the Departmentof National Defence of Canada

ccopy Her Majesty the Queen in Right of Canada as represented by the Minister of National Defence 2015

ccopy Sa Majeste la Reine (en droit du Canada) telle que representee par le ministre de la Defense nationale2015

This page is intentionally left blank

Abstract

In April 2014 the Maritime Information Warfare (MIW) program called the Next Generation ofOperational C2 Systems has been initiated

The aim of this study is to better understand the functionality of the land systems to help definethe requirements of the sea system

This document contains the results of the analysis of over 200 open publications to evaluate andgain knowledge from existing modern land force systems and use that knowledge to identify suc-cessful and useful functionalities and processes that should be recommended for the successor ofGlobal Command and Control System-Maritime (GCCS-M) leading to specification of require-ments for the GCCS-M replacement These recommendations are also based on experience andknowledge gained in OODA Technologies past projects

Study Report RISOMIA Call-up 6

This page is intentionally left blank

ii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Contents

Contents iii

List of Figures v

1 Scope 1

2 Introduction 3

21 Past Projects 3

211 Command Decision Aids Technology (COMDAT) TDP 3

212 MUlti-Sensor Integration within the Common Operating Environment (MU-SIC) 4

213 Joint Fire Support (JFS) 4

214 Tactical Planning and Execution Management (TPEM) project 4

22 Outlines 5

3 Modern Land Force Command and Control (C2) Systems 7

31 Afghan Mission Network 7

32 Future Mission Network 16

33 Canadian Land Command and Control (C2) 21

34 Land Command and Control (C2) Applications in Coalition Operations 22

341 Land Command and Control Information Services (LC2IS) 22

342 Joint Automated Deep Operations Coordination System (JADOCS) 23

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS) 24

iii

Study Report RISOMIA Call-up 6

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC) 25

4 Global Command and Control System 27

41 Global Command and Control System - Maritime (GCCS-M) 27

42 Global Command and Control System - Joint (GCCS-J) 28

43 Global Command and Control System - Army (GCCS-A) 29

44 GCCS Future Evolutions 29

441 Maritime Tactical Command and Control (MTC2) 29

442 Net Centric Enterprise Services (NCES) 30

443 Joint Mission Planning System (JMPS) 31

5 Interoperability in Coalition Land Operations 33

51 NATO Programs for Interoperability 33

52 USA Programs for Interoperability 35

6 Recommendations for GCCS-M Replacement 37

61 SoftwareSystem Functions Recommended for Next Generation GCCS-M 37

62 Interoperability Recommendations 40

63 Procedure and Policy Recommendations 40

7 Conclusion 41

71 Challenges Encountered 42

72 Future Analyses 42

Bibliography 45

iv

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF FIGURES

List of Figures

31 AMN Concept 2012 reproduced from [3] 9

32 AMN Mission Areas reproduced from [4] 10

33 Services Provided in AMN Mission Areas reproduced from [4] 11

34 German participation in AMN reproduced from [13] 15

35 Mission Partner Environment reproduced from [19] 18

36 Participation Options reproduced from [20] 19

37 FMN Evolution Phases reproduced from [20] 20

38 Interoperability Operational Concept reproduced from [24] 23

39 MAJIIC Capability Development reproduced from [27] 25

41 GCCS-M Evolution reproduced from [32] 29

42 NCES Services reproduced from [34] 31

51 NNEC Development Strategies reproduced from [40] 34

52 GCCS-M transition to NECC reproduced from [42] 35

61 AMN Collaborative Functions reproduced from [43] 38

v

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

vi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

List of Acronyms

ABCS Army Battle Command System

ACO Allied Command Operations

ACROSS Allied Commands Resource Optimization Software System

ACO Allied Command Operations

ACT Allied Command Transformation

ADatP-3 Allied Data Publications number 3

ADO Adaptive Dispersed Operations

AMN Afghan Mission Network

ASCC Army Service Component Commands

ASTERIX All Purpose Structured Eurocontrol Surveillance Information Exchange

ATM Air Tasking Message

ATO Air Tasking Order

BCD Battlefield Coordination Detachments

C2 Command and Control

C2C Command and Control Capability

C2IEDM Command and Control Information Exchange Data Model

C2PC Command and Control Personal Computer

C3 Consultation Command and Control

C4AD C4 Assessments Division

C4I Command Control Communications Computers and Intelligence

C4ISR Command Control Communications Computers Intelligence SurveillanceReconnaissance

vii

Study Report RISOMIA Call-up 6

C5ISR Coalition Command Control Communications Computers IntelligenceSurveillance and Reconnaissance

CAGE Coalition Attack Guidance Experiment

CAOC Combined Air Operations Centre

CCIRM Collection Coordination and Intelligence Requirements Management

CENTRIXS Combined Enterprise Regional Information Exchange System

CENTRIXS-GCTF Combined Enterprise Regional Information Exchange System-GlobalCounterterrorism Force

CFWC Canadian Forces Warfare Centre

CIAV Coalition Interoperability Assurance and Validation

CJTF-76 Combined Joint Task Force ndash 76

CMT Coalition Mission Threads

COA Courses of Action

COCOM Combatant Command

COA Courses of Action

COE Common Operating Environment

COP Common Operational Picture

COPIM Criminal Organisation Public Interest Monitor

CORSOM Coalition reception staging amp onward movement

CTSB Counter Terrorism Security Bulletin

CTSF Central Technical Support Facility

CTTP Coalition Tactics Techniques and Procedures

CWIX Coalition Warrior Interoperability Experiment

DDR Disarmament Demobilization and Reintegration

DoD Department of Defense

DP Deterrent Presence

DRDC Defence Research and Development Canada

DSAR Dissemination Storage Archival and Retrieval

ESM Electronic Support Measures

viii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

EVE Effective Visible Execution

FDR Fielding Decision Review

FFI Friendly Force Information

FMN Future Mission Network

FMV Full Motion Video

FP Focal Point

GAMMA Global Aggregated Model for Military Assessments

GCCS Global Command and Control System

GCCS-A Global Command and Control System-Army

GCCS-J Global Command and Control System-Joint

GCCS-M Global Command and Control System-Maritime

GIS Geographic Information System

GPS Global Positioning System

HMART Human Intel Management amp Reporting Tool

ICC Integrated Command and Control for Air Ops

ICTC ISAF Interim Consignment Tracking Capability

ICTS ISAF Interim Consignment Tracking System

IFF Identification Friend or Foe

IFTS ISAF Force Tracking System

IGeoSIT Interim Geo-Spatial Intelligence Tool

ISAF International Security Assistance Force

ISR Intelligence Surveillance Reconnaissance

ITAS Intra Theatre Air Support

JADOCS Joint Automated Deep Operations Coordination System

JC3IEDM Joint Consultation Command and Control Information Exchange Data Model

JCOP Joint Common Operational Picture

JDARTS Joint Defence Planning Analysis amp Requirements Toolset

JFS Joint Fire Support

ix

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

JITC Joint Interoperability Test Command

JMPS Joint Mission Planning System

JOCWatch Joint Operations Center Watch

JOPES Joint Operation Planning and Execution System

JTS Joint Targeting System

LC2IS Land Command and Control Information Services

LCSS Land Combat Support System

LOGFAS Logistics Functional Area Services

MAJIIC Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition

MC Military Committee

MCOC Marine Corps Operation Center

MedRPT Medical reporting

MedWATCH Medical operations watch

MEF Marine Expeditionary Force

MIDB Modernized Integrated Database

MIP Multilateral Interoperability Programme

MPE Mission Partner Environment

MIST Medical Illness Simulating Trauma

MN Mission Network

MOC Maritime Operations Center

MTC2 Maritime Tactical Command and Control

NAC North Atlantic Council

NATO North Atlantic Treaty Organization

NCES Net-Centric Enterprise Services

NCI NATO Communications and Information

NECC Net-Enabled Command Capability

NETOPS Network Operations

NFIP NATO FMN Implementation Plan

x

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

NIRIS Networked Interoperable Real-Time Information Services

NISP NATO Interoperability Standards and Profiles

NITB NATO Intel Tool Box

NNEC NATO Network Enabled Capability

NRT Near-Real-Time

NSCD NATO SIMPLE Compliant Device

OANT Online Analyser for Networked Tactical Data Link

OEF Operation Enduring Freedom

OODA Observe Orient Decide Act

OTH-Gold Over-the-Horizon-GOLD

PFPS Portable Flight Planning System

PPR Prior Permission Required

RCN Royal Canadian Navy

REACT Radar EW and Communications Coverage Tool

RFID Radio-frequency identification

RFIMS Request for Information Management

RSOI Reception Staging Onward Movement and Integration

SA Situational Awareness

SADI Situational Awareness Data Interchange

SAFE SIGINT Analyst Functional Environment

SDA SEWOC database application

SDM Supply Distribution Model

SEWOC SIGINT amp EW Operations Centres

SIGINT Signals Intelligence

SIMPLE Standard Implementation for Multiple Platform Link Evaluation

SIPRNet Secret Internet Protocol Router Network

SME Subject Matter Expert

SOA Service-Oriented Architecture

xi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 3: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Requirements for the GCCS-M Replacement basedon Land Forces Systems

Elisa Shahbazian

Prepared By OODA Technologies Inc4891 GrosvenorMontreal (Qc) H3W 2M2514-476-4773

Prepared For Defence Research amp Development Canada Atlantic Research Centre9 Grove Street PO Box 1012Dartmouth NSB2Y 3Z7902-426-3100 ext180

Scientific Authority Anna-Liesa S Lapinski Defence ScientistContract Number W7707-145677Call Up Number 6Project Requirements for the GCCS-M Replacement based on Land Forces SystemsReport Delivery Date April 15 2015

The scientific or technical validity of this Contract Report is entirely the responsibility of thecontractor and the contents do not necessarily have the approval or endorsement of the Departmentof National Defence of Canada

ccopy Her Majesty the Queen in Right of Canada as represented by the Minister of National Defence 2015

ccopy Sa Majeste la Reine (en droit du Canada) telle que representee par le ministre de la Defense nationale2015

This page is intentionally left blank

Abstract

In April 2014 the Maritime Information Warfare (MIW) program called the Next Generation ofOperational C2 Systems has been initiated

The aim of this study is to better understand the functionality of the land systems to help definethe requirements of the sea system

This document contains the results of the analysis of over 200 open publications to evaluate andgain knowledge from existing modern land force systems and use that knowledge to identify suc-cessful and useful functionalities and processes that should be recommended for the successor ofGlobal Command and Control System-Maritime (GCCS-M) leading to specification of require-ments for the GCCS-M replacement These recommendations are also based on experience andknowledge gained in OODA Technologies past projects

Study Report RISOMIA Call-up 6

This page is intentionally left blank

ii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Contents

Contents iii

List of Figures v

1 Scope 1

2 Introduction 3

21 Past Projects 3

211 Command Decision Aids Technology (COMDAT) TDP 3

212 MUlti-Sensor Integration within the Common Operating Environment (MU-SIC) 4

213 Joint Fire Support (JFS) 4

214 Tactical Planning and Execution Management (TPEM) project 4

22 Outlines 5

3 Modern Land Force Command and Control (C2) Systems 7

31 Afghan Mission Network 7

32 Future Mission Network 16

33 Canadian Land Command and Control (C2) 21

34 Land Command and Control (C2) Applications in Coalition Operations 22

341 Land Command and Control Information Services (LC2IS) 22

342 Joint Automated Deep Operations Coordination System (JADOCS) 23

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS) 24

iii

Study Report RISOMIA Call-up 6

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC) 25

4 Global Command and Control System 27

41 Global Command and Control System - Maritime (GCCS-M) 27

42 Global Command and Control System - Joint (GCCS-J) 28

43 Global Command and Control System - Army (GCCS-A) 29

44 GCCS Future Evolutions 29

441 Maritime Tactical Command and Control (MTC2) 29

442 Net Centric Enterprise Services (NCES) 30

443 Joint Mission Planning System (JMPS) 31

5 Interoperability in Coalition Land Operations 33

51 NATO Programs for Interoperability 33

52 USA Programs for Interoperability 35

6 Recommendations for GCCS-M Replacement 37

61 SoftwareSystem Functions Recommended for Next Generation GCCS-M 37

62 Interoperability Recommendations 40

63 Procedure and Policy Recommendations 40

7 Conclusion 41

71 Challenges Encountered 42

72 Future Analyses 42

Bibliography 45

iv

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF FIGURES

List of Figures

31 AMN Concept 2012 reproduced from [3] 9

32 AMN Mission Areas reproduced from [4] 10

33 Services Provided in AMN Mission Areas reproduced from [4] 11

34 German participation in AMN reproduced from [13] 15

35 Mission Partner Environment reproduced from [19] 18

36 Participation Options reproduced from [20] 19

37 FMN Evolution Phases reproduced from [20] 20

38 Interoperability Operational Concept reproduced from [24] 23

39 MAJIIC Capability Development reproduced from [27] 25

41 GCCS-M Evolution reproduced from [32] 29

42 NCES Services reproduced from [34] 31

51 NNEC Development Strategies reproduced from [40] 34

52 GCCS-M transition to NECC reproduced from [42] 35

61 AMN Collaborative Functions reproduced from [43] 38

v

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

vi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

List of Acronyms

ABCS Army Battle Command System

ACO Allied Command Operations

ACROSS Allied Commands Resource Optimization Software System

ACO Allied Command Operations

ACT Allied Command Transformation

ADatP-3 Allied Data Publications number 3

ADO Adaptive Dispersed Operations

AMN Afghan Mission Network

ASCC Army Service Component Commands

ASTERIX All Purpose Structured Eurocontrol Surveillance Information Exchange

ATM Air Tasking Message

ATO Air Tasking Order

BCD Battlefield Coordination Detachments

C2 Command and Control

C2C Command and Control Capability

C2IEDM Command and Control Information Exchange Data Model

C2PC Command and Control Personal Computer

C3 Consultation Command and Control

C4AD C4 Assessments Division

C4I Command Control Communications Computers and Intelligence

C4ISR Command Control Communications Computers Intelligence SurveillanceReconnaissance

vii

Study Report RISOMIA Call-up 6

C5ISR Coalition Command Control Communications Computers IntelligenceSurveillance and Reconnaissance

CAGE Coalition Attack Guidance Experiment

CAOC Combined Air Operations Centre

CCIRM Collection Coordination and Intelligence Requirements Management

CENTRIXS Combined Enterprise Regional Information Exchange System

CENTRIXS-GCTF Combined Enterprise Regional Information Exchange System-GlobalCounterterrorism Force

CFWC Canadian Forces Warfare Centre

CIAV Coalition Interoperability Assurance and Validation

CJTF-76 Combined Joint Task Force ndash 76

CMT Coalition Mission Threads

COA Courses of Action

COCOM Combatant Command

COA Courses of Action

COE Common Operating Environment

COP Common Operational Picture

COPIM Criminal Organisation Public Interest Monitor

CORSOM Coalition reception staging amp onward movement

CTSB Counter Terrorism Security Bulletin

CTSF Central Technical Support Facility

CTTP Coalition Tactics Techniques and Procedures

CWIX Coalition Warrior Interoperability Experiment

DDR Disarmament Demobilization and Reintegration

DoD Department of Defense

DP Deterrent Presence

DRDC Defence Research and Development Canada

DSAR Dissemination Storage Archival and Retrieval

ESM Electronic Support Measures

viii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

EVE Effective Visible Execution

FDR Fielding Decision Review

FFI Friendly Force Information

FMN Future Mission Network

FMV Full Motion Video

FP Focal Point

GAMMA Global Aggregated Model for Military Assessments

GCCS Global Command and Control System

GCCS-A Global Command and Control System-Army

GCCS-J Global Command and Control System-Joint

GCCS-M Global Command and Control System-Maritime

GIS Geographic Information System

GPS Global Positioning System

HMART Human Intel Management amp Reporting Tool

ICC Integrated Command and Control for Air Ops

ICTC ISAF Interim Consignment Tracking Capability

ICTS ISAF Interim Consignment Tracking System

IFF Identification Friend or Foe

IFTS ISAF Force Tracking System

IGeoSIT Interim Geo-Spatial Intelligence Tool

ISAF International Security Assistance Force

ISR Intelligence Surveillance Reconnaissance

ITAS Intra Theatre Air Support

JADOCS Joint Automated Deep Operations Coordination System

JC3IEDM Joint Consultation Command and Control Information Exchange Data Model

JCOP Joint Common Operational Picture

JDARTS Joint Defence Planning Analysis amp Requirements Toolset

JFS Joint Fire Support

ix

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

JITC Joint Interoperability Test Command

JMPS Joint Mission Planning System

JOCWatch Joint Operations Center Watch

JOPES Joint Operation Planning and Execution System

JTS Joint Targeting System

LC2IS Land Command and Control Information Services

LCSS Land Combat Support System

LOGFAS Logistics Functional Area Services

MAJIIC Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition

MC Military Committee

MCOC Marine Corps Operation Center

MedRPT Medical reporting

MedWATCH Medical operations watch

MEF Marine Expeditionary Force

MIDB Modernized Integrated Database

MIP Multilateral Interoperability Programme

MPE Mission Partner Environment

MIST Medical Illness Simulating Trauma

MN Mission Network

MOC Maritime Operations Center

MTC2 Maritime Tactical Command and Control

NAC North Atlantic Council

NATO North Atlantic Treaty Organization

NCES Net-Centric Enterprise Services

NCI NATO Communications and Information

NECC Net-Enabled Command Capability

NETOPS Network Operations

NFIP NATO FMN Implementation Plan

x

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

NIRIS Networked Interoperable Real-Time Information Services

NISP NATO Interoperability Standards and Profiles

NITB NATO Intel Tool Box

NNEC NATO Network Enabled Capability

NRT Near-Real-Time

NSCD NATO SIMPLE Compliant Device

OANT Online Analyser for Networked Tactical Data Link

OEF Operation Enduring Freedom

OODA Observe Orient Decide Act

OTH-Gold Over-the-Horizon-GOLD

PFPS Portable Flight Planning System

PPR Prior Permission Required

RCN Royal Canadian Navy

REACT Radar EW and Communications Coverage Tool

RFID Radio-frequency identification

RFIMS Request for Information Management

RSOI Reception Staging Onward Movement and Integration

SA Situational Awareness

SADI Situational Awareness Data Interchange

SAFE SIGINT Analyst Functional Environment

SDA SEWOC database application

SDM Supply Distribution Model

SEWOC SIGINT amp EW Operations Centres

SIGINT Signals Intelligence

SIMPLE Standard Implementation for Multiple Platform Link Evaluation

SIPRNet Secret Internet Protocol Router Network

SME Subject Matter Expert

SOA Service-Oriented Architecture

xi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 4: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

This page is intentionally left blank

Abstract

In April 2014 the Maritime Information Warfare (MIW) program called the Next Generation ofOperational C2 Systems has been initiated

The aim of this study is to better understand the functionality of the land systems to help definethe requirements of the sea system

This document contains the results of the analysis of over 200 open publications to evaluate andgain knowledge from existing modern land force systems and use that knowledge to identify suc-cessful and useful functionalities and processes that should be recommended for the successor ofGlobal Command and Control System-Maritime (GCCS-M) leading to specification of require-ments for the GCCS-M replacement These recommendations are also based on experience andknowledge gained in OODA Technologies past projects

Study Report RISOMIA Call-up 6

This page is intentionally left blank

ii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Contents

Contents iii

List of Figures v

1 Scope 1

2 Introduction 3

21 Past Projects 3

211 Command Decision Aids Technology (COMDAT) TDP 3

212 MUlti-Sensor Integration within the Common Operating Environment (MU-SIC) 4

213 Joint Fire Support (JFS) 4

214 Tactical Planning and Execution Management (TPEM) project 4

22 Outlines 5

3 Modern Land Force Command and Control (C2) Systems 7

31 Afghan Mission Network 7

32 Future Mission Network 16

33 Canadian Land Command and Control (C2) 21

34 Land Command and Control (C2) Applications in Coalition Operations 22

341 Land Command and Control Information Services (LC2IS) 22

342 Joint Automated Deep Operations Coordination System (JADOCS) 23

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS) 24

iii

Study Report RISOMIA Call-up 6

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC) 25

4 Global Command and Control System 27

41 Global Command and Control System - Maritime (GCCS-M) 27

42 Global Command and Control System - Joint (GCCS-J) 28

43 Global Command and Control System - Army (GCCS-A) 29

44 GCCS Future Evolutions 29

441 Maritime Tactical Command and Control (MTC2) 29

442 Net Centric Enterprise Services (NCES) 30

443 Joint Mission Planning System (JMPS) 31

5 Interoperability in Coalition Land Operations 33

51 NATO Programs for Interoperability 33

52 USA Programs for Interoperability 35

6 Recommendations for GCCS-M Replacement 37

61 SoftwareSystem Functions Recommended for Next Generation GCCS-M 37

62 Interoperability Recommendations 40

63 Procedure and Policy Recommendations 40

7 Conclusion 41

71 Challenges Encountered 42

72 Future Analyses 42

Bibliography 45

iv

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF FIGURES

List of Figures

31 AMN Concept 2012 reproduced from [3] 9

32 AMN Mission Areas reproduced from [4] 10

33 Services Provided in AMN Mission Areas reproduced from [4] 11

34 German participation in AMN reproduced from [13] 15

35 Mission Partner Environment reproduced from [19] 18

36 Participation Options reproduced from [20] 19

37 FMN Evolution Phases reproduced from [20] 20

38 Interoperability Operational Concept reproduced from [24] 23

39 MAJIIC Capability Development reproduced from [27] 25

41 GCCS-M Evolution reproduced from [32] 29

42 NCES Services reproduced from [34] 31

51 NNEC Development Strategies reproduced from [40] 34

52 GCCS-M transition to NECC reproduced from [42] 35

61 AMN Collaborative Functions reproduced from [43] 38

v

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

vi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

List of Acronyms

ABCS Army Battle Command System

ACO Allied Command Operations

ACROSS Allied Commands Resource Optimization Software System

ACO Allied Command Operations

ACT Allied Command Transformation

ADatP-3 Allied Data Publications number 3

ADO Adaptive Dispersed Operations

AMN Afghan Mission Network

ASCC Army Service Component Commands

ASTERIX All Purpose Structured Eurocontrol Surveillance Information Exchange

ATM Air Tasking Message

ATO Air Tasking Order

BCD Battlefield Coordination Detachments

C2 Command and Control

C2C Command and Control Capability

C2IEDM Command and Control Information Exchange Data Model

C2PC Command and Control Personal Computer

C3 Consultation Command and Control

C4AD C4 Assessments Division

C4I Command Control Communications Computers and Intelligence

C4ISR Command Control Communications Computers Intelligence SurveillanceReconnaissance

vii

Study Report RISOMIA Call-up 6

C5ISR Coalition Command Control Communications Computers IntelligenceSurveillance and Reconnaissance

CAGE Coalition Attack Guidance Experiment

CAOC Combined Air Operations Centre

CCIRM Collection Coordination and Intelligence Requirements Management

CENTRIXS Combined Enterprise Regional Information Exchange System

CENTRIXS-GCTF Combined Enterprise Regional Information Exchange System-GlobalCounterterrorism Force

CFWC Canadian Forces Warfare Centre

CIAV Coalition Interoperability Assurance and Validation

CJTF-76 Combined Joint Task Force ndash 76

CMT Coalition Mission Threads

COA Courses of Action

COCOM Combatant Command

COA Courses of Action

COE Common Operating Environment

COP Common Operational Picture

COPIM Criminal Organisation Public Interest Monitor

CORSOM Coalition reception staging amp onward movement

CTSB Counter Terrorism Security Bulletin

CTSF Central Technical Support Facility

CTTP Coalition Tactics Techniques and Procedures

CWIX Coalition Warrior Interoperability Experiment

DDR Disarmament Demobilization and Reintegration

DoD Department of Defense

DP Deterrent Presence

DRDC Defence Research and Development Canada

DSAR Dissemination Storage Archival and Retrieval

ESM Electronic Support Measures

viii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

EVE Effective Visible Execution

FDR Fielding Decision Review

FFI Friendly Force Information

FMN Future Mission Network

FMV Full Motion Video

FP Focal Point

GAMMA Global Aggregated Model for Military Assessments

GCCS Global Command and Control System

GCCS-A Global Command and Control System-Army

GCCS-J Global Command and Control System-Joint

GCCS-M Global Command and Control System-Maritime

GIS Geographic Information System

GPS Global Positioning System

HMART Human Intel Management amp Reporting Tool

ICC Integrated Command and Control for Air Ops

ICTC ISAF Interim Consignment Tracking Capability

ICTS ISAF Interim Consignment Tracking System

IFF Identification Friend or Foe

IFTS ISAF Force Tracking System

IGeoSIT Interim Geo-Spatial Intelligence Tool

ISAF International Security Assistance Force

ISR Intelligence Surveillance Reconnaissance

ITAS Intra Theatre Air Support

JADOCS Joint Automated Deep Operations Coordination System

JC3IEDM Joint Consultation Command and Control Information Exchange Data Model

JCOP Joint Common Operational Picture

JDARTS Joint Defence Planning Analysis amp Requirements Toolset

JFS Joint Fire Support

ix

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

JITC Joint Interoperability Test Command

JMPS Joint Mission Planning System

JOCWatch Joint Operations Center Watch

JOPES Joint Operation Planning and Execution System

JTS Joint Targeting System

LC2IS Land Command and Control Information Services

LCSS Land Combat Support System

LOGFAS Logistics Functional Area Services

MAJIIC Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition

MC Military Committee

MCOC Marine Corps Operation Center

MedRPT Medical reporting

MedWATCH Medical operations watch

MEF Marine Expeditionary Force

MIDB Modernized Integrated Database

MIP Multilateral Interoperability Programme

MPE Mission Partner Environment

MIST Medical Illness Simulating Trauma

MN Mission Network

MOC Maritime Operations Center

MTC2 Maritime Tactical Command and Control

NAC North Atlantic Council

NATO North Atlantic Treaty Organization

NCES Net-Centric Enterprise Services

NCI NATO Communications and Information

NECC Net-Enabled Command Capability

NETOPS Network Operations

NFIP NATO FMN Implementation Plan

x

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

NIRIS Networked Interoperable Real-Time Information Services

NISP NATO Interoperability Standards and Profiles

NITB NATO Intel Tool Box

NNEC NATO Network Enabled Capability

NRT Near-Real-Time

NSCD NATO SIMPLE Compliant Device

OANT Online Analyser for Networked Tactical Data Link

OEF Operation Enduring Freedom

OODA Observe Orient Decide Act

OTH-Gold Over-the-Horizon-GOLD

PFPS Portable Flight Planning System

PPR Prior Permission Required

RCN Royal Canadian Navy

REACT Radar EW and Communications Coverage Tool

RFID Radio-frequency identification

RFIMS Request for Information Management

RSOI Reception Staging Onward Movement and Integration

SA Situational Awareness

SADI Situational Awareness Data Interchange

SAFE SIGINT Analyst Functional Environment

SDA SEWOC database application

SDM Supply Distribution Model

SEWOC SIGINT amp EW Operations Centres

SIGINT Signals Intelligence

SIMPLE Standard Implementation for Multiple Platform Link Evaluation

SIPRNet Secret Internet Protocol Router Network

SME Subject Matter Expert

SOA Service-Oriented Architecture

xi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 5: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Abstract

In April 2014 the Maritime Information Warfare (MIW) program called the Next Generation ofOperational C2 Systems has been initiated

The aim of this study is to better understand the functionality of the land systems to help definethe requirements of the sea system

This document contains the results of the analysis of over 200 open publications to evaluate andgain knowledge from existing modern land force systems and use that knowledge to identify suc-cessful and useful functionalities and processes that should be recommended for the successor ofGlobal Command and Control System-Maritime (GCCS-M) leading to specification of require-ments for the GCCS-M replacement These recommendations are also based on experience andknowledge gained in OODA Technologies past projects

Study Report RISOMIA Call-up 6

This page is intentionally left blank

ii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Contents

Contents iii

List of Figures v

1 Scope 1

2 Introduction 3

21 Past Projects 3

211 Command Decision Aids Technology (COMDAT) TDP 3

212 MUlti-Sensor Integration within the Common Operating Environment (MU-SIC) 4

213 Joint Fire Support (JFS) 4

214 Tactical Planning and Execution Management (TPEM) project 4

22 Outlines 5

3 Modern Land Force Command and Control (C2) Systems 7

31 Afghan Mission Network 7

32 Future Mission Network 16

33 Canadian Land Command and Control (C2) 21

34 Land Command and Control (C2) Applications in Coalition Operations 22

341 Land Command and Control Information Services (LC2IS) 22

342 Joint Automated Deep Operations Coordination System (JADOCS) 23

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS) 24

iii

Study Report RISOMIA Call-up 6

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC) 25

4 Global Command and Control System 27

41 Global Command and Control System - Maritime (GCCS-M) 27

42 Global Command and Control System - Joint (GCCS-J) 28

43 Global Command and Control System - Army (GCCS-A) 29

44 GCCS Future Evolutions 29

441 Maritime Tactical Command and Control (MTC2) 29

442 Net Centric Enterprise Services (NCES) 30

443 Joint Mission Planning System (JMPS) 31

5 Interoperability in Coalition Land Operations 33

51 NATO Programs for Interoperability 33

52 USA Programs for Interoperability 35

6 Recommendations for GCCS-M Replacement 37

61 SoftwareSystem Functions Recommended for Next Generation GCCS-M 37

62 Interoperability Recommendations 40

63 Procedure and Policy Recommendations 40

7 Conclusion 41

71 Challenges Encountered 42

72 Future Analyses 42

Bibliography 45

iv

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF FIGURES

List of Figures

31 AMN Concept 2012 reproduced from [3] 9

32 AMN Mission Areas reproduced from [4] 10

33 Services Provided in AMN Mission Areas reproduced from [4] 11

34 German participation in AMN reproduced from [13] 15

35 Mission Partner Environment reproduced from [19] 18

36 Participation Options reproduced from [20] 19

37 FMN Evolution Phases reproduced from [20] 20

38 Interoperability Operational Concept reproduced from [24] 23

39 MAJIIC Capability Development reproduced from [27] 25

41 GCCS-M Evolution reproduced from [32] 29

42 NCES Services reproduced from [34] 31

51 NNEC Development Strategies reproduced from [40] 34

52 GCCS-M transition to NECC reproduced from [42] 35

61 AMN Collaborative Functions reproduced from [43] 38

v

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

vi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

List of Acronyms

ABCS Army Battle Command System

ACO Allied Command Operations

ACROSS Allied Commands Resource Optimization Software System

ACO Allied Command Operations

ACT Allied Command Transformation

ADatP-3 Allied Data Publications number 3

ADO Adaptive Dispersed Operations

AMN Afghan Mission Network

ASCC Army Service Component Commands

ASTERIX All Purpose Structured Eurocontrol Surveillance Information Exchange

ATM Air Tasking Message

ATO Air Tasking Order

BCD Battlefield Coordination Detachments

C2 Command and Control

C2C Command and Control Capability

C2IEDM Command and Control Information Exchange Data Model

C2PC Command and Control Personal Computer

C3 Consultation Command and Control

C4AD C4 Assessments Division

C4I Command Control Communications Computers and Intelligence

C4ISR Command Control Communications Computers Intelligence SurveillanceReconnaissance

vii

Study Report RISOMIA Call-up 6

C5ISR Coalition Command Control Communications Computers IntelligenceSurveillance and Reconnaissance

CAGE Coalition Attack Guidance Experiment

CAOC Combined Air Operations Centre

CCIRM Collection Coordination and Intelligence Requirements Management

CENTRIXS Combined Enterprise Regional Information Exchange System

CENTRIXS-GCTF Combined Enterprise Regional Information Exchange System-GlobalCounterterrorism Force

CFWC Canadian Forces Warfare Centre

CIAV Coalition Interoperability Assurance and Validation

CJTF-76 Combined Joint Task Force ndash 76

CMT Coalition Mission Threads

COA Courses of Action

COCOM Combatant Command

COA Courses of Action

COE Common Operating Environment

COP Common Operational Picture

COPIM Criminal Organisation Public Interest Monitor

CORSOM Coalition reception staging amp onward movement

CTSB Counter Terrorism Security Bulletin

CTSF Central Technical Support Facility

CTTP Coalition Tactics Techniques and Procedures

CWIX Coalition Warrior Interoperability Experiment

DDR Disarmament Demobilization and Reintegration

DoD Department of Defense

DP Deterrent Presence

DRDC Defence Research and Development Canada

DSAR Dissemination Storage Archival and Retrieval

ESM Electronic Support Measures

viii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

EVE Effective Visible Execution

FDR Fielding Decision Review

FFI Friendly Force Information

FMN Future Mission Network

FMV Full Motion Video

FP Focal Point

GAMMA Global Aggregated Model for Military Assessments

GCCS Global Command and Control System

GCCS-A Global Command and Control System-Army

GCCS-J Global Command and Control System-Joint

GCCS-M Global Command and Control System-Maritime

GIS Geographic Information System

GPS Global Positioning System

HMART Human Intel Management amp Reporting Tool

ICC Integrated Command and Control for Air Ops

ICTC ISAF Interim Consignment Tracking Capability

ICTS ISAF Interim Consignment Tracking System

IFF Identification Friend or Foe

IFTS ISAF Force Tracking System

IGeoSIT Interim Geo-Spatial Intelligence Tool

ISAF International Security Assistance Force

ISR Intelligence Surveillance Reconnaissance

ITAS Intra Theatre Air Support

JADOCS Joint Automated Deep Operations Coordination System

JC3IEDM Joint Consultation Command and Control Information Exchange Data Model

JCOP Joint Common Operational Picture

JDARTS Joint Defence Planning Analysis amp Requirements Toolset

JFS Joint Fire Support

ix

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

JITC Joint Interoperability Test Command

JMPS Joint Mission Planning System

JOCWatch Joint Operations Center Watch

JOPES Joint Operation Planning and Execution System

JTS Joint Targeting System

LC2IS Land Command and Control Information Services

LCSS Land Combat Support System

LOGFAS Logistics Functional Area Services

MAJIIC Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition

MC Military Committee

MCOC Marine Corps Operation Center

MedRPT Medical reporting

MedWATCH Medical operations watch

MEF Marine Expeditionary Force

MIDB Modernized Integrated Database

MIP Multilateral Interoperability Programme

MPE Mission Partner Environment

MIST Medical Illness Simulating Trauma

MN Mission Network

MOC Maritime Operations Center

MTC2 Maritime Tactical Command and Control

NAC North Atlantic Council

NATO North Atlantic Treaty Organization

NCES Net-Centric Enterprise Services

NCI NATO Communications and Information

NECC Net-Enabled Command Capability

NETOPS Network Operations

NFIP NATO FMN Implementation Plan

x

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

NIRIS Networked Interoperable Real-Time Information Services

NISP NATO Interoperability Standards and Profiles

NITB NATO Intel Tool Box

NNEC NATO Network Enabled Capability

NRT Near-Real-Time

NSCD NATO SIMPLE Compliant Device

OANT Online Analyser for Networked Tactical Data Link

OEF Operation Enduring Freedom

OODA Observe Orient Decide Act

OTH-Gold Over-the-Horizon-GOLD

PFPS Portable Flight Planning System

PPR Prior Permission Required

RCN Royal Canadian Navy

REACT Radar EW and Communications Coverage Tool

RFID Radio-frequency identification

RFIMS Request for Information Management

RSOI Reception Staging Onward Movement and Integration

SA Situational Awareness

SADI Situational Awareness Data Interchange

SAFE SIGINT Analyst Functional Environment

SDA SEWOC database application

SDM Supply Distribution Model

SEWOC SIGINT amp EW Operations Centres

SIGINT Signals Intelligence

SIMPLE Standard Implementation for Multiple Platform Link Evaluation

SIPRNet Secret Internet Protocol Router Network

SME Subject Matter Expert

SOA Service-Oriented Architecture

xi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 6: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

This page is intentionally left blank

ii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Contents

Contents iii

List of Figures v

1 Scope 1

2 Introduction 3

21 Past Projects 3

211 Command Decision Aids Technology (COMDAT) TDP 3

212 MUlti-Sensor Integration within the Common Operating Environment (MU-SIC) 4

213 Joint Fire Support (JFS) 4

214 Tactical Planning and Execution Management (TPEM) project 4

22 Outlines 5

3 Modern Land Force Command and Control (C2) Systems 7

31 Afghan Mission Network 7

32 Future Mission Network 16

33 Canadian Land Command and Control (C2) 21

34 Land Command and Control (C2) Applications in Coalition Operations 22

341 Land Command and Control Information Services (LC2IS) 22

342 Joint Automated Deep Operations Coordination System (JADOCS) 23

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS) 24

iii

Study Report RISOMIA Call-up 6

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC) 25

4 Global Command and Control System 27

41 Global Command and Control System - Maritime (GCCS-M) 27

42 Global Command and Control System - Joint (GCCS-J) 28

43 Global Command and Control System - Army (GCCS-A) 29

44 GCCS Future Evolutions 29

441 Maritime Tactical Command and Control (MTC2) 29

442 Net Centric Enterprise Services (NCES) 30

443 Joint Mission Planning System (JMPS) 31

5 Interoperability in Coalition Land Operations 33

51 NATO Programs for Interoperability 33

52 USA Programs for Interoperability 35

6 Recommendations for GCCS-M Replacement 37

61 SoftwareSystem Functions Recommended for Next Generation GCCS-M 37

62 Interoperability Recommendations 40

63 Procedure and Policy Recommendations 40

7 Conclusion 41

71 Challenges Encountered 42

72 Future Analyses 42

Bibliography 45

iv

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF FIGURES

List of Figures

31 AMN Concept 2012 reproduced from [3] 9

32 AMN Mission Areas reproduced from [4] 10

33 Services Provided in AMN Mission Areas reproduced from [4] 11

34 German participation in AMN reproduced from [13] 15

35 Mission Partner Environment reproduced from [19] 18

36 Participation Options reproduced from [20] 19

37 FMN Evolution Phases reproduced from [20] 20

38 Interoperability Operational Concept reproduced from [24] 23

39 MAJIIC Capability Development reproduced from [27] 25

41 GCCS-M Evolution reproduced from [32] 29

42 NCES Services reproduced from [34] 31

51 NNEC Development Strategies reproduced from [40] 34

52 GCCS-M transition to NECC reproduced from [42] 35

61 AMN Collaborative Functions reproduced from [43] 38

v

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

vi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

List of Acronyms

ABCS Army Battle Command System

ACO Allied Command Operations

ACROSS Allied Commands Resource Optimization Software System

ACO Allied Command Operations

ACT Allied Command Transformation

ADatP-3 Allied Data Publications number 3

ADO Adaptive Dispersed Operations

AMN Afghan Mission Network

ASCC Army Service Component Commands

ASTERIX All Purpose Structured Eurocontrol Surveillance Information Exchange

ATM Air Tasking Message

ATO Air Tasking Order

BCD Battlefield Coordination Detachments

C2 Command and Control

C2C Command and Control Capability

C2IEDM Command and Control Information Exchange Data Model

C2PC Command and Control Personal Computer

C3 Consultation Command and Control

C4AD C4 Assessments Division

C4I Command Control Communications Computers and Intelligence

C4ISR Command Control Communications Computers Intelligence SurveillanceReconnaissance

vii

Study Report RISOMIA Call-up 6

C5ISR Coalition Command Control Communications Computers IntelligenceSurveillance and Reconnaissance

CAGE Coalition Attack Guidance Experiment

CAOC Combined Air Operations Centre

CCIRM Collection Coordination and Intelligence Requirements Management

CENTRIXS Combined Enterprise Regional Information Exchange System

CENTRIXS-GCTF Combined Enterprise Regional Information Exchange System-GlobalCounterterrorism Force

CFWC Canadian Forces Warfare Centre

CIAV Coalition Interoperability Assurance and Validation

CJTF-76 Combined Joint Task Force ndash 76

CMT Coalition Mission Threads

COA Courses of Action

COCOM Combatant Command

COA Courses of Action

COE Common Operating Environment

COP Common Operational Picture

COPIM Criminal Organisation Public Interest Monitor

CORSOM Coalition reception staging amp onward movement

CTSB Counter Terrorism Security Bulletin

CTSF Central Technical Support Facility

CTTP Coalition Tactics Techniques and Procedures

CWIX Coalition Warrior Interoperability Experiment

DDR Disarmament Demobilization and Reintegration

DoD Department of Defense

DP Deterrent Presence

DRDC Defence Research and Development Canada

DSAR Dissemination Storage Archival and Retrieval

ESM Electronic Support Measures

viii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

EVE Effective Visible Execution

FDR Fielding Decision Review

FFI Friendly Force Information

FMN Future Mission Network

FMV Full Motion Video

FP Focal Point

GAMMA Global Aggregated Model for Military Assessments

GCCS Global Command and Control System

GCCS-A Global Command and Control System-Army

GCCS-J Global Command and Control System-Joint

GCCS-M Global Command and Control System-Maritime

GIS Geographic Information System

GPS Global Positioning System

HMART Human Intel Management amp Reporting Tool

ICC Integrated Command and Control for Air Ops

ICTC ISAF Interim Consignment Tracking Capability

ICTS ISAF Interim Consignment Tracking System

IFF Identification Friend or Foe

IFTS ISAF Force Tracking System

IGeoSIT Interim Geo-Spatial Intelligence Tool

ISAF International Security Assistance Force

ISR Intelligence Surveillance Reconnaissance

ITAS Intra Theatre Air Support

JADOCS Joint Automated Deep Operations Coordination System

JC3IEDM Joint Consultation Command and Control Information Exchange Data Model

JCOP Joint Common Operational Picture

JDARTS Joint Defence Planning Analysis amp Requirements Toolset

JFS Joint Fire Support

ix

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

JITC Joint Interoperability Test Command

JMPS Joint Mission Planning System

JOCWatch Joint Operations Center Watch

JOPES Joint Operation Planning and Execution System

JTS Joint Targeting System

LC2IS Land Command and Control Information Services

LCSS Land Combat Support System

LOGFAS Logistics Functional Area Services

MAJIIC Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition

MC Military Committee

MCOC Marine Corps Operation Center

MedRPT Medical reporting

MedWATCH Medical operations watch

MEF Marine Expeditionary Force

MIDB Modernized Integrated Database

MIP Multilateral Interoperability Programme

MPE Mission Partner Environment

MIST Medical Illness Simulating Trauma

MN Mission Network

MOC Maritime Operations Center

MTC2 Maritime Tactical Command and Control

NAC North Atlantic Council

NATO North Atlantic Treaty Organization

NCES Net-Centric Enterprise Services

NCI NATO Communications and Information

NECC Net-Enabled Command Capability

NETOPS Network Operations

NFIP NATO FMN Implementation Plan

x

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

NIRIS Networked Interoperable Real-Time Information Services

NISP NATO Interoperability Standards and Profiles

NITB NATO Intel Tool Box

NNEC NATO Network Enabled Capability

NRT Near-Real-Time

NSCD NATO SIMPLE Compliant Device

OANT Online Analyser for Networked Tactical Data Link

OEF Operation Enduring Freedom

OODA Observe Orient Decide Act

OTH-Gold Over-the-Horizon-GOLD

PFPS Portable Flight Planning System

PPR Prior Permission Required

RCN Royal Canadian Navy

REACT Radar EW and Communications Coverage Tool

RFID Radio-frequency identification

RFIMS Request for Information Management

RSOI Reception Staging Onward Movement and Integration

SA Situational Awareness

SADI Situational Awareness Data Interchange

SAFE SIGINT Analyst Functional Environment

SDA SEWOC database application

SDM Supply Distribution Model

SEWOC SIGINT amp EW Operations Centres

SIGINT Signals Intelligence

SIMPLE Standard Implementation for Multiple Platform Link Evaluation

SIPRNet Secret Internet Protocol Router Network

SME Subject Matter Expert

SOA Service-Oriented Architecture

xi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 7: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Contents

Contents iii

List of Figures v

1 Scope 1

2 Introduction 3

21 Past Projects 3

211 Command Decision Aids Technology (COMDAT) TDP 3

212 MUlti-Sensor Integration within the Common Operating Environment (MU-SIC) 4

213 Joint Fire Support (JFS) 4

214 Tactical Planning and Execution Management (TPEM) project 4

22 Outlines 5

3 Modern Land Force Command and Control (C2) Systems 7

31 Afghan Mission Network 7

32 Future Mission Network 16

33 Canadian Land Command and Control (C2) 21

34 Land Command and Control (C2) Applications in Coalition Operations 22

341 Land Command and Control Information Services (LC2IS) 22

342 Joint Automated Deep Operations Coordination System (JADOCS) 23

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS) 24

iii

Study Report RISOMIA Call-up 6

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC) 25

4 Global Command and Control System 27

41 Global Command and Control System - Maritime (GCCS-M) 27

42 Global Command and Control System - Joint (GCCS-J) 28

43 Global Command and Control System - Army (GCCS-A) 29

44 GCCS Future Evolutions 29

441 Maritime Tactical Command and Control (MTC2) 29

442 Net Centric Enterprise Services (NCES) 30

443 Joint Mission Planning System (JMPS) 31

5 Interoperability in Coalition Land Operations 33

51 NATO Programs for Interoperability 33

52 USA Programs for Interoperability 35

6 Recommendations for GCCS-M Replacement 37

61 SoftwareSystem Functions Recommended for Next Generation GCCS-M 37

62 Interoperability Recommendations 40

63 Procedure and Policy Recommendations 40

7 Conclusion 41

71 Challenges Encountered 42

72 Future Analyses 42

Bibliography 45

iv

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF FIGURES

List of Figures

31 AMN Concept 2012 reproduced from [3] 9

32 AMN Mission Areas reproduced from [4] 10

33 Services Provided in AMN Mission Areas reproduced from [4] 11

34 German participation in AMN reproduced from [13] 15

35 Mission Partner Environment reproduced from [19] 18

36 Participation Options reproduced from [20] 19

37 FMN Evolution Phases reproduced from [20] 20

38 Interoperability Operational Concept reproduced from [24] 23

39 MAJIIC Capability Development reproduced from [27] 25

41 GCCS-M Evolution reproduced from [32] 29

42 NCES Services reproduced from [34] 31

51 NNEC Development Strategies reproduced from [40] 34

52 GCCS-M transition to NECC reproduced from [42] 35

61 AMN Collaborative Functions reproduced from [43] 38

v

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

vi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

List of Acronyms

ABCS Army Battle Command System

ACO Allied Command Operations

ACROSS Allied Commands Resource Optimization Software System

ACO Allied Command Operations

ACT Allied Command Transformation

ADatP-3 Allied Data Publications number 3

ADO Adaptive Dispersed Operations

AMN Afghan Mission Network

ASCC Army Service Component Commands

ASTERIX All Purpose Structured Eurocontrol Surveillance Information Exchange

ATM Air Tasking Message

ATO Air Tasking Order

BCD Battlefield Coordination Detachments

C2 Command and Control

C2C Command and Control Capability

C2IEDM Command and Control Information Exchange Data Model

C2PC Command and Control Personal Computer

C3 Consultation Command and Control

C4AD C4 Assessments Division

C4I Command Control Communications Computers and Intelligence

C4ISR Command Control Communications Computers Intelligence SurveillanceReconnaissance

vii

Study Report RISOMIA Call-up 6

C5ISR Coalition Command Control Communications Computers IntelligenceSurveillance and Reconnaissance

CAGE Coalition Attack Guidance Experiment

CAOC Combined Air Operations Centre

CCIRM Collection Coordination and Intelligence Requirements Management

CENTRIXS Combined Enterprise Regional Information Exchange System

CENTRIXS-GCTF Combined Enterprise Regional Information Exchange System-GlobalCounterterrorism Force

CFWC Canadian Forces Warfare Centre

CIAV Coalition Interoperability Assurance and Validation

CJTF-76 Combined Joint Task Force ndash 76

CMT Coalition Mission Threads

COA Courses of Action

COCOM Combatant Command

COA Courses of Action

COE Common Operating Environment

COP Common Operational Picture

COPIM Criminal Organisation Public Interest Monitor

CORSOM Coalition reception staging amp onward movement

CTSB Counter Terrorism Security Bulletin

CTSF Central Technical Support Facility

CTTP Coalition Tactics Techniques and Procedures

CWIX Coalition Warrior Interoperability Experiment

DDR Disarmament Demobilization and Reintegration

DoD Department of Defense

DP Deterrent Presence

DRDC Defence Research and Development Canada

DSAR Dissemination Storage Archival and Retrieval

ESM Electronic Support Measures

viii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

EVE Effective Visible Execution

FDR Fielding Decision Review

FFI Friendly Force Information

FMN Future Mission Network

FMV Full Motion Video

FP Focal Point

GAMMA Global Aggregated Model for Military Assessments

GCCS Global Command and Control System

GCCS-A Global Command and Control System-Army

GCCS-J Global Command and Control System-Joint

GCCS-M Global Command and Control System-Maritime

GIS Geographic Information System

GPS Global Positioning System

HMART Human Intel Management amp Reporting Tool

ICC Integrated Command and Control for Air Ops

ICTC ISAF Interim Consignment Tracking Capability

ICTS ISAF Interim Consignment Tracking System

IFF Identification Friend or Foe

IFTS ISAF Force Tracking System

IGeoSIT Interim Geo-Spatial Intelligence Tool

ISAF International Security Assistance Force

ISR Intelligence Surveillance Reconnaissance

ITAS Intra Theatre Air Support

JADOCS Joint Automated Deep Operations Coordination System

JC3IEDM Joint Consultation Command and Control Information Exchange Data Model

JCOP Joint Common Operational Picture

JDARTS Joint Defence Planning Analysis amp Requirements Toolset

JFS Joint Fire Support

ix

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

JITC Joint Interoperability Test Command

JMPS Joint Mission Planning System

JOCWatch Joint Operations Center Watch

JOPES Joint Operation Planning and Execution System

JTS Joint Targeting System

LC2IS Land Command and Control Information Services

LCSS Land Combat Support System

LOGFAS Logistics Functional Area Services

MAJIIC Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition

MC Military Committee

MCOC Marine Corps Operation Center

MedRPT Medical reporting

MedWATCH Medical operations watch

MEF Marine Expeditionary Force

MIDB Modernized Integrated Database

MIP Multilateral Interoperability Programme

MPE Mission Partner Environment

MIST Medical Illness Simulating Trauma

MN Mission Network

MOC Maritime Operations Center

MTC2 Maritime Tactical Command and Control

NAC North Atlantic Council

NATO North Atlantic Treaty Organization

NCES Net-Centric Enterprise Services

NCI NATO Communications and Information

NECC Net-Enabled Command Capability

NETOPS Network Operations

NFIP NATO FMN Implementation Plan

x

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

NIRIS Networked Interoperable Real-Time Information Services

NISP NATO Interoperability Standards and Profiles

NITB NATO Intel Tool Box

NNEC NATO Network Enabled Capability

NRT Near-Real-Time

NSCD NATO SIMPLE Compliant Device

OANT Online Analyser for Networked Tactical Data Link

OEF Operation Enduring Freedom

OODA Observe Orient Decide Act

OTH-Gold Over-the-Horizon-GOLD

PFPS Portable Flight Planning System

PPR Prior Permission Required

RCN Royal Canadian Navy

REACT Radar EW and Communications Coverage Tool

RFID Radio-frequency identification

RFIMS Request for Information Management

RSOI Reception Staging Onward Movement and Integration

SA Situational Awareness

SADI Situational Awareness Data Interchange

SAFE SIGINT Analyst Functional Environment

SDA SEWOC database application

SDM Supply Distribution Model

SEWOC SIGINT amp EW Operations Centres

SIGINT Signals Intelligence

SIMPLE Standard Implementation for Multiple Platform Link Evaluation

SIPRNet Secret Internet Protocol Router Network

SME Subject Matter Expert

SOA Service-Oriented Architecture

xi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 8: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC) 25

4 Global Command and Control System 27

41 Global Command and Control System - Maritime (GCCS-M) 27

42 Global Command and Control System - Joint (GCCS-J) 28

43 Global Command and Control System - Army (GCCS-A) 29

44 GCCS Future Evolutions 29

441 Maritime Tactical Command and Control (MTC2) 29

442 Net Centric Enterprise Services (NCES) 30

443 Joint Mission Planning System (JMPS) 31

5 Interoperability in Coalition Land Operations 33

51 NATO Programs for Interoperability 33

52 USA Programs for Interoperability 35

6 Recommendations for GCCS-M Replacement 37

61 SoftwareSystem Functions Recommended for Next Generation GCCS-M 37

62 Interoperability Recommendations 40

63 Procedure and Policy Recommendations 40

7 Conclusion 41

71 Challenges Encountered 42

72 Future Analyses 42

Bibliography 45

iv

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF FIGURES

List of Figures

31 AMN Concept 2012 reproduced from [3] 9

32 AMN Mission Areas reproduced from [4] 10

33 Services Provided in AMN Mission Areas reproduced from [4] 11

34 German participation in AMN reproduced from [13] 15

35 Mission Partner Environment reproduced from [19] 18

36 Participation Options reproduced from [20] 19

37 FMN Evolution Phases reproduced from [20] 20

38 Interoperability Operational Concept reproduced from [24] 23

39 MAJIIC Capability Development reproduced from [27] 25

41 GCCS-M Evolution reproduced from [32] 29

42 NCES Services reproduced from [34] 31

51 NNEC Development Strategies reproduced from [40] 34

52 GCCS-M transition to NECC reproduced from [42] 35

61 AMN Collaborative Functions reproduced from [43] 38

v

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

vi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

List of Acronyms

ABCS Army Battle Command System

ACO Allied Command Operations

ACROSS Allied Commands Resource Optimization Software System

ACO Allied Command Operations

ACT Allied Command Transformation

ADatP-3 Allied Data Publications number 3

ADO Adaptive Dispersed Operations

AMN Afghan Mission Network

ASCC Army Service Component Commands

ASTERIX All Purpose Structured Eurocontrol Surveillance Information Exchange

ATM Air Tasking Message

ATO Air Tasking Order

BCD Battlefield Coordination Detachments

C2 Command and Control

C2C Command and Control Capability

C2IEDM Command and Control Information Exchange Data Model

C2PC Command and Control Personal Computer

C3 Consultation Command and Control

C4AD C4 Assessments Division

C4I Command Control Communications Computers and Intelligence

C4ISR Command Control Communications Computers Intelligence SurveillanceReconnaissance

vii

Study Report RISOMIA Call-up 6

C5ISR Coalition Command Control Communications Computers IntelligenceSurveillance and Reconnaissance

CAGE Coalition Attack Guidance Experiment

CAOC Combined Air Operations Centre

CCIRM Collection Coordination and Intelligence Requirements Management

CENTRIXS Combined Enterprise Regional Information Exchange System

CENTRIXS-GCTF Combined Enterprise Regional Information Exchange System-GlobalCounterterrorism Force

CFWC Canadian Forces Warfare Centre

CIAV Coalition Interoperability Assurance and Validation

CJTF-76 Combined Joint Task Force ndash 76

CMT Coalition Mission Threads

COA Courses of Action

COCOM Combatant Command

COA Courses of Action

COE Common Operating Environment

COP Common Operational Picture

COPIM Criminal Organisation Public Interest Monitor

CORSOM Coalition reception staging amp onward movement

CTSB Counter Terrorism Security Bulletin

CTSF Central Technical Support Facility

CTTP Coalition Tactics Techniques and Procedures

CWIX Coalition Warrior Interoperability Experiment

DDR Disarmament Demobilization and Reintegration

DoD Department of Defense

DP Deterrent Presence

DRDC Defence Research and Development Canada

DSAR Dissemination Storage Archival and Retrieval

ESM Electronic Support Measures

viii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

EVE Effective Visible Execution

FDR Fielding Decision Review

FFI Friendly Force Information

FMN Future Mission Network

FMV Full Motion Video

FP Focal Point

GAMMA Global Aggregated Model for Military Assessments

GCCS Global Command and Control System

GCCS-A Global Command and Control System-Army

GCCS-J Global Command and Control System-Joint

GCCS-M Global Command and Control System-Maritime

GIS Geographic Information System

GPS Global Positioning System

HMART Human Intel Management amp Reporting Tool

ICC Integrated Command and Control for Air Ops

ICTC ISAF Interim Consignment Tracking Capability

ICTS ISAF Interim Consignment Tracking System

IFF Identification Friend or Foe

IFTS ISAF Force Tracking System

IGeoSIT Interim Geo-Spatial Intelligence Tool

ISAF International Security Assistance Force

ISR Intelligence Surveillance Reconnaissance

ITAS Intra Theatre Air Support

JADOCS Joint Automated Deep Operations Coordination System

JC3IEDM Joint Consultation Command and Control Information Exchange Data Model

JCOP Joint Common Operational Picture

JDARTS Joint Defence Planning Analysis amp Requirements Toolset

JFS Joint Fire Support

ix

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

JITC Joint Interoperability Test Command

JMPS Joint Mission Planning System

JOCWatch Joint Operations Center Watch

JOPES Joint Operation Planning and Execution System

JTS Joint Targeting System

LC2IS Land Command and Control Information Services

LCSS Land Combat Support System

LOGFAS Logistics Functional Area Services

MAJIIC Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition

MC Military Committee

MCOC Marine Corps Operation Center

MedRPT Medical reporting

MedWATCH Medical operations watch

MEF Marine Expeditionary Force

MIDB Modernized Integrated Database

MIP Multilateral Interoperability Programme

MPE Mission Partner Environment

MIST Medical Illness Simulating Trauma

MN Mission Network

MOC Maritime Operations Center

MTC2 Maritime Tactical Command and Control

NAC North Atlantic Council

NATO North Atlantic Treaty Organization

NCES Net-Centric Enterprise Services

NCI NATO Communications and Information

NECC Net-Enabled Command Capability

NETOPS Network Operations

NFIP NATO FMN Implementation Plan

x

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

NIRIS Networked Interoperable Real-Time Information Services

NISP NATO Interoperability Standards and Profiles

NITB NATO Intel Tool Box

NNEC NATO Network Enabled Capability

NRT Near-Real-Time

NSCD NATO SIMPLE Compliant Device

OANT Online Analyser for Networked Tactical Data Link

OEF Operation Enduring Freedom

OODA Observe Orient Decide Act

OTH-Gold Over-the-Horizon-GOLD

PFPS Portable Flight Planning System

PPR Prior Permission Required

RCN Royal Canadian Navy

REACT Radar EW and Communications Coverage Tool

RFID Radio-frequency identification

RFIMS Request for Information Management

RSOI Reception Staging Onward Movement and Integration

SA Situational Awareness

SADI Situational Awareness Data Interchange

SAFE SIGINT Analyst Functional Environment

SDA SEWOC database application

SDM Supply Distribution Model

SEWOC SIGINT amp EW Operations Centres

SIGINT Signals Intelligence

SIMPLE Standard Implementation for Multiple Platform Link Evaluation

SIPRNet Secret Internet Protocol Router Network

SME Subject Matter Expert

SOA Service-Oriented Architecture

xi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 9: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

LIST OF FIGURES

List of Figures

31 AMN Concept 2012 reproduced from [3] 9

32 AMN Mission Areas reproduced from [4] 10

33 Services Provided in AMN Mission Areas reproduced from [4] 11

34 German participation in AMN reproduced from [13] 15

35 Mission Partner Environment reproduced from [19] 18

36 Participation Options reproduced from [20] 19

37 FMN Evolution Phases reproduced from [20] 20

38 Interoperability Operational Concept reproduced from [24] 23

39 MAJIIC Capability Development reproduced from [27] 25

41 GCCS-M Evolution reproduced from [32] 29

42 NCES Services reproduced from [34] 31

51 NNEC Development Strategies reproduced from [40] 34

52 GCCS-M transition to NECC reproduced from [42] 35

61 AMN Collaborative Functions reproduced from [43] 38

v

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

vi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

List of Acronyms

ABCS Army Battle Command System

ACO Allied Command Operations

ACROSS Allied Commands Resource Optimization Software System

ACO Allied Command Operations

ACT Allied Command Transformation

ADatP-3 Allied Data Publications number 3

ADO Adaptive Dispersed Operations

AMN Afghan Mission Network

ASCC Army Service Component Commands

ASTERIX All Purpose Structured Eurocontrol Surveillance Information Exchange

ATM Air Tasking Message

ATO Air Tasking Order

BCD Battlefield Coordination Detachments

C2 Command and Control

C2C Command and Control Capability

C2IEDM Command and Control Information Exchange Data Model

C2PC Command and Control Personal Computer

C3 Consultation Command and Control

C4AD C4 Assessments Division

C4I Command Control Communications Computers and Intelligence

C4ISR Command Control Communications Computers Intelligence SurveillanceReconnaissance

vii

Study Report RISOMIA Call-up 6

C5ISR Coalition Command Control Communications Computers IntelligenceSurveillance and Reconnaissance

CAGE Coalition Attack Guidance Experiment

CAOC Combined Air Operations Centre

CCIRM Collection Coordination and Intelligence Requirements Management

CENTRIXS Combined Enterprise Regional Information Exchange System

CENTRIXS-GCTF Combined Enterprise Regional Information Exchange System-GlobalCounterterrorism Force

CFWC Canadian Forces Warfare Centre

CIAV Coalition Interoperability Assurance and Validation

CJTF-76 Combined Joint Task Force ndash 76

CMT Coalition Mission Threads

COA Courses of Action

COCOM Combatant Command

COA Courses of Action

COE Common Operating Environment

COP Common Operational Picture

COPIM Criminal Organisation Public Interest Monitor

CORSOM Coalition reception staging amp onward movement

CTSB Counter Terrorism Security Bulletin

CTSF Central Technical Support Facility

CTTP Coalition Tactics Techniques and Procedures

CWIX Coalition Warrior Interoperability Experiment

DDR Disarmament Demobilization and Reintegration

DoD Department of Defense

DP Deterrent Presence

DRDC Defence Research and Development Canada

DSAR Dissemination Storage Archival and Retrieval

ESM Electronic Support Measures

viii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

EVE Effective Visible Execution

FDR Fielding Decision Review

FFI Friendly Force Information

FMN Future Mission Network

FMV Full Motion Video

FP Focal Point

GAMMA Global Aggregated Model for Military Assessments

GCCS Global Command and Control System

GCCS-A Global Command and Control System-Army

GCCS-J Global Command and Control System-Joint

GCCS-M Global Command and Control System-Maritime

GIS Geographic Information System

GPS Global Positioning System

HMART Human Intel Management amp Reporting Tool

ICC Integrated Command and Control for Air Ops

ICTC ISAF Interim Consignment Tracking Capability

ICTS ISAF Interim Consignment Tracking System

IFF Identification Friend or Foe

IFTS ISAF Force Tracking System

IGeoSIT Interim Geo-Spatial Intelligence Tool

ISAF International Security Assistance Force

ISR Intelligence Surveillance Reconnaissance

ITAS Intra Theatre Air Support

JADOCS Joint Automated Deep Operations Coordination System

JC3IEDM Joint Consultation Command and Control Information Exchange Data Model

JCOP Joint Common Operational Picture

JDARTS Joint Defence Planning Analysis amp Requirements Toolset

JFS Joint Fire Support

ix

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

JITC Joint Interoperability Test Command

JMPS Joint Mission Planning System

JOCWatch Joint Operations Center Watch

JOPES Joint Operation Planning and Execution System

JTS Joint Targeting System

LC2IS Land Command and Control Information Services

LCSS Land Combat Support System

LOGFAS Logistics Functional Area Services

MAJIIC Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition

MC Military Committee

MCOC Marine Corps Operation Center

MedRPT Medical reporting

MedWATCH Medical operations watch

MEF Marine Expeditionary Force

MIDB Modernized Integrated Database

MIP Multilateral Interoperability Programme

MPE Mission Partner Environment

MIST Medical Illness Simulating Trauma

MN Mission Network

MOC Maritime Operations Center

MTC2 Maritime Tactical Command and Control

NAC North Atlantic Council

NATO North Atlantic Treaty Organization

NCES Net-Centric Enterprise Services

NCI NATO Communications and Information

NECC Net-Enabled Command Capability

NETOPS Network Operations

NFIP NATO FMN Implementation Plan

x

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

NIRIS Networked Interoperable Real-Time Information Services

NISP NATO Interoperability Standards and Profiles

NITB NATO Intel Tool Box

NNEC NATO Network Enabled Capability

NRT Near-Real-Time

NSCD NATO SIMPLE Compliant Device

OANT Online Analyser for Networked Tactical Data Link

OEF Operation Enduring Freedom

OODA Observe Orient Decide Act

OTH-Gold Over-the-Horizon-GOLD

PFPS Portable Flight Planning System

PPR Prior Permission Required

RCN Royal Canadian Navy

REACT Radar EW and Communications Coverage Tool

RFID Radio-frequency identification

RFIMS Request for Information Management

RSOI Reception Staging Onward Movement and Integration

SA Situational Awareness

SADI Situational Awareness Data Interchange

SAFE SIGINT Analyst Functional Environment

SDA SEWOC database application

SDM Supply Distribution Model

SEWOC SIGINT amp EW Operations Centres

SIGINT Signals Intelligence

SIMPLE Standard Implementation for Multiple Platform Link Evaluation

SIPRNet Secret Internet Protocol Router Network

SME Subject Matter Expert

SOA Service-Oriented Architecture

xi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 10: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

This page is intentionally left blank

vi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

List of Acronyms

ABCS Army Battle Command System

ACO Allied Command Operations

ACROSS Allied Commands Resource Optimization Software System

ACO Allied Command Operations

ACT Allied Command Transformation

ADatP-3 Allied Data Publications number 3

ADO Adaptive Dispersed Operations

AMN Afghan Mission Network

ASCC Army Service Component Commands

ASTERIX All Purpose Structured Eurocontrol Surveillance Information Exchange

ATM Air Tasking Message

ATO Air Tasking Order

BCD Battlefield Coordination Detachments

C2 Command and Control

C2C Command and Control Capability

C2IEDM Command and Control Information Exchange Data Model

C2PC Command and Control Personal Computer

C3 Consultation Command and Control

C4AD C4 Assessments Division

C4I Command Control Communications Computers and Intelligence

C4ISR Command Control Communications Computers Intelligence SurveillanceReconnaissance

vii

Study Report RISOMIA Call-up 6

C5ISR Coalition Command Control Communications Computers IntelligenceSurveillance and Reconnaissance

CAGE Coalition Attack Guidance Experiment

CAOC Combined Air Operations Centre

CCIRM Collection Coordination and Intelligence Requirements Management

CENTRIXS Combined Enterprise Regional Information Exchange System

CENTRIXS-GCTF Combined Enterprise Regional Information Exchange System-GlobalCounterterrorism Force

CFWC Canadian Forces Warfare Centre

CIAV Coalition Interoperability Assurance and Validation

CJTF-76 Combined Joint Task Force ndash 76

CMT Coalition Mission Threads

COA Courses of Action

COCOM Combatant Command

COA Courses of Action

COE Common Operating Environment

COP Common Operational Picture

COPIM Criminal Organisation Public Interest Monitor

CORSOM Coalition reception staging amp onward movement

CTSB Counter Terrorism Security Bulletin

CTSF Central Technical Support Facility

CTTP Coalition Tactics Techniques and Procedures

CWIX Coalition Warrior Interoperability Experiment

DDR Disarmament Demobilization and Reintegration

DoD Department of Defense

DP Deterrent Presence

DRDC Defence Research and Development Canada

DSAR Dissemination Storage Archival and Retrieval

ESM Electronic Support Measures

viii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

EVE Effective Visible Execution

FDR Fielding Decision Review

FFI Friendly Force Information

FMN Future Mission Network

FMV Full Motion Video

FP Focal Point

GAMMA Global Aggregated Model for Military Assessments

GCCS Global Command and Control System

GCCS-A Global Command and Control System-Army

GCCS-J Global Command and Control System-Joint

GCCS-M Global Command and Control System-Maritime

GIS Geographic Information System

GPS Global Positioning System

HMART Human Intel Management amp Reporting Tool

ICC Integrated Command and Control for Air Ops

ICTC ISAF Interim Consignment Tracking Capability

ICTS ISAF Interim Consignment Tracking System

IFF Identification Friend or Foe

IFTS ISAF Force Tracking System

IGeoSIT Interim Geo-Spatial Intelligence Tool

ISAF International Security Assistance Force

ISR Intelligence Surveillance Reconnaissance

ITAS Intra Theatre Air Support

JADOCS Joint Automated Deep Operations Coordination System

JC3IEDM Joint Consultation Command and Control Information Exchange Data Model

JCOP Joint Common Operational Picture

JDARTS Joint Defence Planning Analysis amp Requirements Toolset

JFS Joint Fire Support

ix

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

JITC Joint Interoperability Test Command

JMPS Joint Mission Planning System

JOCWatch Joint Operations Center Watch

JOPES Joint Operation Planning and Execution System

JTS Joint Targeting System

LC2IS Land Command and Control Information Services

LCSS Land Combat Support System

LOGFAS Logistics Functional Area Services

MAJIIC Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition

MC Military Committee

MCOC Marine Corps Operation Center

MedRPT Medical reporting

MedWATCH Medical operations watch

MEF Marine Expeditionary Force

MIDB Modernized Integrated Database

MIP Multilateral Interoperability Programme

MPE Mission Partner Environment

MIST Medical Illness Simulating Trauma

MN Mission Network

MOC Maritime Operations Center

MTC2 Maritime Tactical Command and Control

NAC North Atlantic Council

NATO North Atlantic Treaty Organization

NCES Net-Centric Enterprise Services

NCI NATO Communications and Information

NECC Net-Enabled Command Capability

NETOPS Network Operations

NFIP NATO FMN Implementation Plan

x

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

NIRIS Networked Interoperable Real-Time Information Services

NISP NATO Interoperability Standards and Profiles

NITB NATO Intel Tool Box

NNEC NATO Network Enabled Capability

NRT Near-Real-Time

NSCD NATO SIMPLE Compliant Device

OANT Online Analyser for Networked Tactical Data Link

OEF Operation Enduring Freedom

OODA Observe Orient Decide Act

OTH-Gold Over-the-Horizon-GOLD

PFPS Portable Flight Planning System

PPR Prior Permission Required

RCN Royal Canadian Navy

REACT Radar EW and Communications Coverage Tool

RFID Radio-frequency identification

RFIMS Request for Information Management

RSOI Reception Staging Onward Movement and Integration

SA Situational Awareness

SADI Situational Awareness Data Interchange

SAFE SIGINT Analyst Functional Environment

SDA SEWOC database application

SDM Supply Distribution Model

SEWOC SIGINT amp EW Operations Centres

SIGINT Signals Intelligence

SIMPLE Standard Implementation for Multiple Platform Link Evaluation

SIPRNet Secret Internet Protocol Router Network

SME Subject Matter Expert

SOA Service-Oriented Architecture

xi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 11: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

List of Acronyms

ABCS Army Battle Command System

ACO Allied Command Operations

ACROSS Allied Commands Resource Optimization Software System

ACO Allied Command Operations

ACT Allied Command Transformation

ADatP-3 Allied Data Publications number 3

ADO Adaptive Dispersed Operations

AMN Afghan Mission Network

ASCC Army Service Component Commands

ASTERIX All Purpose Structured Eurocontrol Surveillance Information Exchange

ATM Air Tasking Message

ATO Air Tasking Order

BCD Battlefield Coordination Detachments

C2 Command and Control

C2C Command and Control Capability

C2IEDM Command and Control Information Exchange Data Model

C2PC Command and Control Personal Computer

C3 Consultation Command and Control

C4AD C4 Assessments Division

C4I Command Control Communications Computers and Intelligence

C4ISR Command Control Communications Computers Intelligence SurveillanceReconnaissance

vii

Study Report RISOMIA Call-up 6

C5ISR Coalition Command Control Communications Computers IntelligenceSurveillance and Reconnaissance

CAGE Coalition Attack Guidance Experiment

CAOC Combined Air Operations Centre

CCIRM Collection Coordination and Intelligence Requirements Management

CENTRIXS Combined Enterprise Regional Information Exchange System

CENTRIXS-GCTF Combined Enterprise Regional Information Exchange System-GlobalCounterterrorism Force

CFWC Canadian Forces Warfare Centre

CIAV Coalition Interoperability Assurance and Validation

CJTF-76 Combined Joint Task Force ndash 76

CMT Coalition Mission Threads

COA Courses of Action

COCOM Combatant Command

COA Courses of Action

COE Common Operating Environment

COP Common Operational Picture

COPIM Criminal Organisation Public Interest Monitor

CORSOM Coalition reception staging amp onward movement

CTSB Counter Terrorism Security Bulletin

CTSF Central Technical Support Facility

CTTP Coalition Tactics Techniques and Procedures

CWIX Coalition Warrior Interoperability Experiment

DDR Disarmament Demobilization and Reintegration

DoD Department of Defense

DP Deterrent Presence

DRDC Defence Research and Development Canada

DSAR Dissemination Storage Archival and Retrieval

ESM Electronic Support Measures

viii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

EVE Effective Visible Execution

FDR Fielding Decision Review

FFI Friendly Force Information

FMN Future Mission Network

FMV Full Motion Video

FP Focal Point

GAMMA Global Aggregated Model for Military Assessments

GCCS Global Command and Control System

GCCS-A Global Command and Control System-Army

GCCS-J Global Command and Control System-Joint

GCCS-M Global Command and Control System-Maritime

GIS Geographic Information System

GPS Global Positioning System

HMART Human Intel Management amp Reporting Tool

ICC Integrated Command and Control for Air Ops

ICTC ISAF Interim Consignment Tracking Capability

ICTS ISAF Interim Consignment Tracking System

IFF Identification Friend or Foe

IFTS ISAF Force Tracking System

IGeoSIT Interim Geo-Spatial Intelligence Tool

ISAF International Security Assistance Force

ISR Intelligence Surveillance Reconnaissance

ITAS Intra Theatre Air Support

JADOCS Joint Automated Deep Operations Coordination System

JC3IEDM Joint Consultation Command and Control Information Exchange Data Model

JCOP Joint Common Operational Picture

JDARTS Joint Defence Planning Analysis amp Requirements Toolset

JFS Joint Fire Support

ix

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

JITC Joint Interoperability Test Command

JMPS Joint Mission Planning System

JOCWatch Joint Operations Center Watch

JOPES Joint Operation Planning and Execution System

JTS Joint Targeting System

LC2IS Land Command and Control Information Services

LCSS Land Combat Support System

LOGFAS Logistics Functional Area Services

MAJIIC Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition

MC Military Committee

MCOC Marine Corps Operation Center

MedRPT Medical reporting

MedWATCH Medical operations watch

MEF Marine Expeditionary Force

MIDB Modernized Integrated Database

MIP Multilateral Interoperability Programme

MPE Mission Partner Environment

MIST Medical Illness Simulating Trauma

MN Mission Network

MOC Maritime Operations Center

MTC2 Maritime Tactical Command and Control

NAC North Atlantic Council

NATO North Atlantic Treaty Organization

NCES Net-Centric Enterprise Services

NCI NATO Communications and Information

NECC Net-Enabled Command Capability

NETOPS Network Operations

NFIP NATO FMN Implementation Plan

x

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

NIRIS Networked Interoperable Real-Time Information Services

NISP NATO Interoperability Standards and Profiles

NITB NATO Intel Tool Box

NNEC NATO Network Enabled Capability

NRT Near-Real-Time

NSCD NATO SIMPLE Compliant Device

OANT Online Analyser for Networked Tactical Data Link

OEF Operation Enduring Freedom

OODA Observe Orient Decide Act

OTH-Gold Over-the-Horizon-GOLD

PFPS Portable Flight Planning System

PPR Prior Permission Required

RCN Royal Canadian Navy

REACT Radar EW and Communications Coverage Tool

RFID Radio-frequency identification

RFIMS Request for Information Management

RSOI Reception Staging Onward Movement and Integration

SA Situational Awareness

SADI Situational Awareness Data Interchange

SAFE SIGINT Analyst Functional Environment

SDA SEWOC database application

SDM Supply Distribution Model

SEWOC SIGINT amp EW Operations Centres

SIGINT Signals Intelligence

SIMPLE Standard Implementation for Multiple Platform Link Evaluation

SIPRNet Secret Internet Protocol Router Network

SME Subject Matter Expert

SOA Service-Oriented Architecture

xi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 12: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

C5ISR Coalition Command Control Communications Computers IntelligenceSurveillance and Reconnaissance

CAGE Coalition Attack Guidance Experiment

CAOC Combined Air Operations Centre

CCIRM Collection Coordination and Intelligence Requirements Management

CENTRIXS Combined Enterprise Regional Information Exchange System

CENTRIXS-GCTF Combined Enterprise Regional Information Exchange System-GlobalCounterterrorism Force

CFWC Canadian Forces Warfare Centre

CIAV Coalition Interoperability Assurance and Validation

CJTF-76 Combined Joint Task Force ndash 76

CMT Coalition Mission Threads

COA Courses of Action

COCOM Combatant Command

COA Courses of Action

COE Common Operating Environment

COP Common Operational Picture

COPIM Criminal Organisation Public Interest Monitor

CORSOM Coalition reception staging amp onward movement

CTSB Counter Terrorism Security Bulletin

CTSF Central Technical Support Facility

CTTP Coalition Tactics Techniques and Procedures

CWIX Coalition Warrior Interoperability Experiment

DDR Disarmament Demobilization and Reintegration

DoD Department of Defense

DP Deterrent Presence

DRDC Defence Research and Development Canada

DSAR Dissemination Storage Archival and Retrieval

ESM Electronic Support Measures

viii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

EVE Effective Visible Execution

FDR Fielding Decision Review

FFI Friendly Force Information

FMN Future Mission Network

FMV Full Motion Video

FP Focal Point

GAMMA Global Aggregated Model for Military Assessments

GCCS Global Command and Control System

GCCS-A Global Command and Control System-Army

GCCS-J Global Command and Control System-Joint

GCCS-M Global Command and Control System-Maritime

GIS Geographic Information System

GPS Global Positioning System

HMART Human Intel Management amp Reporting Tool

ICC Integrated Command and Control for Air Ops

ICTC ISAF Interim Consignment Tracking Capability

ICTS ISAF Interim Consignment Tracking System

IFF Identification Friend or Foe

IFTS ISAF Force Tracking System

IGeoSIT Interim Geo-Spatial Intelligence Tool

ISAF International Security Assistance Force

ISR Intelligence Surveillance Reconnaissance

ITAS Intra Theatre Air Support

JADOCS Joint Automated Deep Operations Coordination System

JC3IEDM Joint Consultation Command and Control Information Exchange Data Model

JCOP Joint Common Operational Picture

JDARTS Joint Defence Planning Analysis amp Requirements Toolset

JFS Joint Fire Support

ix

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

JITC Joint Interoperability Test Command

JMPS Joint Mission Planning System

JOCWatch Joint Operations Center Watch

JOPES Joint Operation Planning and Execution System

JTS Joint Targeting System

LC2IS Land Command and Control Information Services

LCSS Land Combat Support System

LOGFAS Logistics Functional Area Services

MAJIIC Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition

MC Military Committee

MCOC Marine Corps Operation Center

MedRPT Medical reporting

MedWATCH Medical operations watch

MEF Marine Expeditionary Force

MIDB Modernized Integrated Database

MIP Multilateral Interoperability Programme

MPE Mission Partner Environment

MIST Medical Illness Simulating Trauma

MN Mission Network

MOC Maritime Operations Center

MTC2 Maritime Tactical Command and Control

NAC North Atlantic Council

NATO North Atlantic Treaty Organization

NCES Net-Centric Enterprise Services

NCI NATO Communications and Information

NECC Net-Enabled Command Capability

NETOPS Network Operations

NFIP NATO FMN Implementation Plan

x

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

NIRIS Networked Interoperable Real-Time Information Services

NISP NATO Interoperability Standards and Profiles

NITB NATO Intel Tool Box

NNEC NATO Network Enabled Capability

NRT Near-Real-Time

NSCD NATO SIMPLE Compliant Device

OANT Online Analyser for Networked Tactical Data Link

OEF Operation Enduring Freedom

OODA Observe Orient Decide Act

OTH-Gold Over-the-Horizon-GOLD

PFPS Portable Flight Planning System

PPR Prior Permission Required

RCN Royal Canadian Navy

REACT Radar EW and Communications Coverage Tool

RFID Radio-frequency identification

RFIMS Request for Information Management

RSOI Reception Staging Onward Movement and Integration

SA Situational Awareness

SADI Situational Awareness Data Interchange

SAFE SIGINT Analyst Functional Environment

SDA SEWOC database application

SDM Supply Distribution Model

SEWOC SIGINT amp EW Operations Centres

SIGINT Signals Intelligence

SIMPLE Standard Implementation for Multiple Platform Link Evaluation

SIPRNet Secret Internet Protocol Router Network

SME Subject Matter Expert

SOA Service-Oriented Architecture

xi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 13: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

LIST OF ACRONYMS

EVE Effective Visible Execution

FDR Fielding Decision Review

FFI Friendly Force Information

FMN Future Mission Network

FMV Full Motion Video

FP Focal Point

GAMMA Global Aggregated Model for Military Assessments

GCCS Global Command and Control System

GCCS-A Global Command and Control System-Army

GCCS-J Global Command and Control System-Joint

GCCS-M Global Command and Control System-Maritime

GIS Geographic Information System

GPS Global Positioning System

HMART Human Intel Management amp Reporting Tool

ICC Integrated Command and Control for Air Ops

ICTC ISAF Interim Consignment Tracking Capability

ICTS ISAF Interim Consignment Tracking System

IFF Identification Friend or Foe

IFTS ISAF Force Tracking System

IGeoSIT Interim Geo-Spatial Intelligence Tool

ISAF International Security Assistance Force

ISR Intelligence Surveillance Reconnaissance

ITAS Intra Theatre Air Support

JADOCS Joint Automated Deep Operations Coordination System

JC3IEDM Joint Consultation Command and Control Information Exchange Data Model

JCOP Joint Common Operational Picture

JDARTS Joint Defence Planning Analysis amp Requirements Toolset

JFS Joint Fire Support

ix

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

JITC Joint Interoperability Test Command

JMPS Joint Mission Planning System

JOCWatch Joint Operations Center Watch

JOPES Joint Operation Planning and Execution System

JTS Joint Targeting System

LC2IS Land Command and Control Information Services

LCSS Land Combat Support System

LOGFAS Logistics Functional Area Services

MAJIIC Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition

MC Military Committee

MCOC Marine Corps Operation Center

MedRPT Medical reporting

MedWATCH Medical operations watch

MEF Marine Expeditionary Force

MIDB Modernized Integrated Database

MIP Multilateral Interoperability Programme

MPE Mission Partner Environment

MIST Medical Illness Simulating Trauma

MN Mission Network

MOC Maritime Operations Center

MTC2 Maritime Tactical Command and Control

NAC North Atlantic Council

NATO North Atlantic Treaty Organization

NCES Net-Centric Enterprise Services

NCI NATO Communications and Information

NECC Net-Enabled Command Capability

NETOPS Network Operations

NFIP NATO FMN Implementation Plan

x

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

NIRIS Networked Interoperable Real-Time Information Services

NISP NATO Interoperability Standards and Profiles

NITB NATO Intel Tool Box

NNEC NATO Network Enabled Capability

NRT Near-Real-Time

NSCD NATO SIMPLE Compliant Device

OANT Online Analyser for Networked Tactical Data Link

OEF Operation Enduring Freedom

OODA Observe Orient Decide Act

OTH-Gold Over-the-Horizon-GOLD

PFPS Portable Flight Planning System

PPR Prior Permission Required

RCN Royal Canadian Navy

REACT Radar EW and Communications Coverage Tool

RFID Radio-frequency identification

RFIMS Request for Information Management

RSOI Reception Staging Onward Movement and Integration

SA Situational Awareness

SADI Situational Awareness Data Interchange

SAFE SIGINT Analyst Functional Environment

SDA SEWOC database application

SDM Supply Distribution Model

SEWOC SIGINT amp EW Operations Centres

SIGINT Signals Intelligence

SIMPLE Standard Implementation for Multiple Platform Link Evaluation

SIPRNet Secret Internet Protocol Router Network

SME Subject Matter Expert

SOA Service-Oriented Architecture

xi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 14: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

JITC Joint Interoperability Test Command

JMPS Joint Mission Planning System

JOCWatch Joint Operations Center Watch

JOPES Joint Operation Planning and Execution System

JTS Joint Targeting System

LC2IS Land Command and Control Information Services

LCSS Land Combat Support System

LOGFAS Logistics Functional Area Services

MAJIIC Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition

MC Military Committee

MCOC Marine Corps Operation Center

MedRPT Medical reporting

MedWATCH Medical operations watch

MEF Marine Expeditionary Force

MIDB Modernized Integrated Database

MIP Multilateral Interoperability Programme

MPE Mission Partner Environment

MIST Medical Illness Simulating Trauma

MN Mission Network

MOC Maritime Operations Center

MTC2 Maritime Tactical Command and Control

NAC North Atlantic Council

NATO North Atlantic Treaty Organization

NCES Net-Centric Enterprise Services

NCI NATO Communications and Information

NECC Net-Enabled Command Capability

NETOPS Network Operations

NFIP NATO FMN Implementation Plan

x

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

LIST OF ACRONYMS

NIRIS Networked Interoperable Real-Time Information Services

NISP NATO Interoperability Standards and Profiles

NITB NATO Intel Tool Box

NNEC NATO Network Enabled Capability

NRT Near-Real-Time

NSCD NATO SIMPLE Compliant Device

OANT Online Analyser for Networked Tactical Data Link

OEF Operation Enduring Freedom

OODA Observe Orient Decide Act

OTH-Gold Over-the-Horizon-GOLD

PFPS Portable Flight Planning System

PPR Prior Permission Required

RCN Royal Canadian Navy

REACT Radar EW and Communications Coverage Tool

RFID Radio-frequency identification

RFIMS Request for Information Management

RSOI Reception Staging Onward Movement and Integration

SA Situational Awareness

SADI Situational Awareness Data Interchange

SAFE SIGINT Analyst Functional Environment

SDA SEWOC database application

SDM Supply Distribution Model

SEWOC SIGINT amp EW Operations Centres

SIGINT Signals Intelligence

SIMPLE Standard Implementation for Multiple Platform Link Evaluation

SIPRNet Secret Internet Protocol Router Network

SME Subject Matter Expert

SOA Service-Oriented Architecture

xi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 15: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

LIST OF ACRONYMS

NIRIS Networked Interoperable Real-Time Information Services

NISP NATO Interoperability Standards and Profiles

NITB NATO Intel Tool Box

NNEC NATO Network Enabled Capability

NRT Near-Real-Time

NSCD NATO SIMPLE Compliant Device

OANT Online Analyser for Networked Tactical Data Link

OEF Operation Enduring Freedom

OODA Observe Orient Decide Act

OTH-Gold Over-the-Horizon-GOLD

PFPS Portable Flight Planning System

PPR Prior Permission Required

RCN Royal Canadian Navy

REACT Radar EW and Communications Coverage Tool

RFID Radio-frequency identification

RFIMS Request for Information Management

RSOI Reception Staging Onward Movement and Integration

SA Situational Awareness

SADI Situational Awareness Data Interchange

SAFE SIGINT Analyst Functional Environment

SDA SEWOC database application

SDM Supply Distribution Model

SEWOC SIGINT amp EW Operations Centres

SIGINT Signals Intelligence

SIMPLE Standard Implementation for Multiple Platform Link Evaluation

SIPRNet Secret Internet Protocol Router Network

SME Subject Matter Expert

SOA Service-Oriented Architecture

xi

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 16: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

SOCOM Special Operations Command

SORTS Status of Resources and Training System

SPM Sustainment Planning

STANAG Standardization Agreement

SVTC Secure Video Teleconferencing

STF STANAG Transformation Framework

TDL Tactical Data Link

TOPFAS Tool for Operational Planning Force Activation and Simulation

TS Top Secret

TST Time-Sensitive Targeting

UAV Unmanned Aerial Vehicle

UK United Kingdom

US United States

USAF US Air Force

USCENTCOM United States Central Command

USN US Navy

VOIP Voice Over Internet Protocol

WG working groups

XML eXtensible Markup Language

XMPP Extensible Messaging and Presence Protocol

xii

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 17: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 1 Scope

Part 1

Scope

The primary objectives of this study were

1 Identify functional and hardware capabilities of modern land force Command and Control(C2) systems in the open published literature that may be useful in a Global Command andControl System-Maritime (GCCS-M) replacement and develop documentation explaining therecommended capabilities

2 Identify and document innovative shifts in procedure or policy that have made modern landforce systems uniquely successful Identify those shifts that could be recommended as partof the Royal Canadian Navy (RCN)rsquos GCCS-M replacement and develop documentationexplaining why the shift is included and its applicability to C2

The analyses were based on around 200 papers collected from Internet as well as Defence Researchand Development Canada (DRDC) past studies on various aspects of land and maritime C2

1

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 18: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

This page is intentionally left blank

2

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 19: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 2 Introduction

Part 2

Introduction

The Canadian navy is currently using Global Command and Control System (GCCS) and its sup-porting systems architecture the US Defense Information Infrastructure (DII) Common OperatingEnvironment (COE) as part of its command and control system onboard Canadian Frigates Theformatted messaging structure Over-the-Horizon-GOLD (OTH-Gold) is used by GCCS for messagepassing with other GCCS nodes [1]

The GCCS-M is also part of the Maritime Operations Center (MOC)s on Atlantic and Pacificcoasts of Canada

Under the Maritime Information Warfare (MIW) program research into the Next Generation ofOperational C2 Systems is being carried out to help identify the requirements for the futureGCCS-M replacement This study is in support of this program gaining knowledge from existingmodern land force systems and using that knowledge to identify requirements for the GCCS-Mreplacement

As part of this work a large (over 200 papers) bibliography of open reportsdocumentation onmodern land system has been collected OODA Technologies Inc analysed these reports alsoleveraging their background experience in a number of projects in the past where various aspectsof how GCCS-M system is integrated with the naval C2 or in MOCs to provide enhanced situationalawareness have been demonstrated and analysed A short summary of some of these projects isgiven below

21 Past Projects

211 Command Decision Aids Technology (COMDAT) TDP

As part of the COMDAT Technology Development Program (TDP) members of OODA Technolo-gies Inc team demonstrated fusion of onboard sensor data tactical data-link and GCCS-M datato provide battle-space awareness within the Halifax Class Command and Control Systems Thefusion capability has been evaluated both in land-based test facility as well as in sea trials The

3

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 20: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

lesson learned from this exercise was that due to the latencies in GCCS-M data which are equalor larger than tactical data link (and of course also on-board sensor data) the main contributionto the ship tactical situation from GCCS-M were the targets that have not yet been detected byonboard sensors or reported by datalink (bearing in mind that GCCS-M includes the datalinkreports as well) In this experiment the GCCS-M was used as another information source andthere was no interoperability between the Halifax Class frigate and GCCS-M

212 MUlti-Sensor Integration within the Common Operating Environment(MUSIC)

The MUlti-Sensor Integration within a Common Operating Environment (MUSIC) TechnologyDemonstrator Project (TDP) has been established to demonstrate a capability for surveillancedata fusion within the Navyrsquos Recognized Maritime Picture (RMP) and to identify a suitablescalable computing architecture in which such fusion can take place It was developed by scientistsof OODA Technologies when they were at Lockheed Martin Canada The data fusion module weresuccessfully implemented within the Common Operating Environment (COE) demonstrated inthe GCCS-M environment and passed SPAWAR compliance testing As a lesson learned even ifthe fusion technology was proven to enhance situational awareness the overall process of improvinga specific feature of GCCS-M is rather long from design to implementation and compliance Bythe time the cycle was completed part of the framework had changed versions upgraded and theprocess had to be repeated Also because the technology and the integration framework weredeveloped by two different companies discrepancies were introduced causing uncertainties in theprogram

213 Joint Fire Support (JFS)

The Joint Fire Support (JFS) project was to build a Testbed comprised of a modeling and simu-lation environment in which scenarios and mission plans can be developed and executed within asimulation environment The distributed simulation thus built serves as a means of feeding thevarious C2 systems The different C2 systems contributed to the generation of a joint CommonOperational Picture (COP) to provide a means of testing future joint fire support concepts andtools One of goal of the project was to detect human error (through data capture) when usingthe framework features such as chat JADOCS VOIP in order to prevent fratricide As a lessonlearned one has to be careful when introducing new features within a framework and evaluate ifthe new technology can produce more benefits or harm (difficulty misuse etc)

214 Tactical Planning and Execution Management (TPEM) project

The Tactical Planning and Execution Management (TPEM) prototype is a system developed byThales-Quebec for DRDC Valcartier (Micheline Belanger Mohamad Allouche and Adel Guitouni)for dealing with Adaptive Dispersed Operations (ADO) In the course of this project the func-tionalities of many C2 land systems have been reviewed and compared Also 5 external SubjectMatter Expert (SME)s have participated in that review Unfortunately access to the reports could

4

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 21: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 2 Introduction

not be granted within the time of this call-up

22 Outlines

This document includes the results of the analyses of the collected documentation and summarisesthe recommendations derived from these analyses It is organized as follows

bull Section 3 presents an overview of the modern land systems and provides a description ofuseful functionalities for enhanced C2

bull Section 4 provides a description of current GCCS systems and provides a description of theUSA plans for the next generation GCCS developments

bull Section 5 provides a summary of interoperability architectures in land systems and GCCS

bull Section 6 describes recommendations for functionality policy and procedure for the nextgeneration Naval C2

bull Section 7 presents the general conclusions of this study including the challenges encounteredduring the realization of the objectives of the work as well as recommendations for futureanalyses

5

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 22: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

This page is intentionally left blank

6

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 23: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 3

Modern Land Force Command andControl (C2) Systems

31 Afghan Mission Network

Operation Enduring Freedom (OEF) (Afghanistan) began in October 2001 and was initially con-ducted by a relatively small coalition of United States United Kingdom Australian and Afghan(Northern Alliance) forces North Atlantic Treaty Organization (NATO) assumed leadership ofInternational Security Assistance Force (ISAF) in 2003 Prior to the 2005ndash2006 period ndash the timethat ISAFrsquos mission was expanded to cover all of Afghanistan ndash few concerted efforts were madeto integrate all or even a large portion of ISAFrsquos partner nation networks on one coherent andaccessible Coalition Command Control Communications Computers Intelligence Surveillanceand Reconnaissance (C5ISR) network Despite its ostensible utility a common mission networkfor ISAF forces did not emerge [2] This was due to three intertwined factors

1 Individual countries ndash information and data-sharing practices remained relatively stovepiped

2 Traditional and long-standing security concerns trumped operational necessity and

3 The difficulties associated with connecting disparate national and functional systems

United States (US) and the United Kingdom (UK) spurred an effort to establish shared serviceson a common network This effort manifested in the United States instituting an email exchangeservice with other NATO nations and the UK creating a connection mechanism within the ISAF-Secret or ISAF-S network ensuring the interoperability of UK and NATO forces on a commoncore network These initiatives demonstrated the feasibility and potential utility of establishinga common federated network that could enable information sharing for all of ISAFrsquos partnershowever a true coalition network did not begin to emerge until the 2008ndash2010 timeframe

The first major step in the development of a network to fully support ISAFrsquos expanded opera-tional scope occurred in 2008 at a United States Central Command (USCENTCOM) Network

7

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 24: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

Operations (NETOPS) conference held in Qatar At the conference it was proposed that theNATO ISAF should adopt one of the four primary networks used by the mission partners (listedbelow) namely the US Combined Enterprise Regional Information Exchange System-Global Coun-terterrorism Force (CENTRIXS-GCTF) as Combined Enterprise Regional Information ExchangeSystem (CENTRIXS)-ISAF constituting

1 Secret Internet Protocol Router Network (SIPRNet)

2 CENTRIXS-GCTF

3 ISAF-Secret and

4 NATO-Secret

This proposal was approved in 2009 leading to the development of the Afghan Mission Net-work (AMN) Subsequently GEN McChrystal the commander of ISAF established an ISAF-widerequirement for each partner nation to share data on the AMN

To overcome the problems information-sharing limitations which were having a significant effecton operational efficacy and force protection the policies and procedures that reinforced a ldquoneed-to-knowrdquo culture had to be replaced with policies and procedures emphasizing a ldquoneed-to-sharerdquo toensure that ISAF could collectively leverage disparate coalition data and populate COPs in a timelyfashion Operational necessity combined with guidance provided by commanders McKiernan andMcChrystal led to the full implementation of the AMN which began as a network for facilitatinghuman-to-human exchanges and included the following basic services

bull Voice Over Internet Protocol (VOIP) telephone connectivity

bull Chat

bull Email

bull Web browsing

bull Secure Video Teleconferencing (SVTC)

Over time it evolved to become the primary C5ISR system in Afghanistan consisting of theISAF-S core and each of the participating nations national extensions (eg CENTRIXS-ISAFUS CAESAR Italy OVERTASK UK Land Combat Support System (LCSS) Canada and soforth) as shown in figure 31 [3] [4]

In 2012 additional developments were funded to implement and support five (5) new capabilitiesunder the AMN 2012 project [5] These capabilities were

bull Enterprise Portal

bull Text Chat also named as JCHAT+

8

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 25: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 3 Modern Land Force Command and Control (C2) Systems

bull Track Augmentation

bull C2 interoperability

bull Software License Management

Figure 31 AMN Concept 2012 reproduced from [3]

The AMN has evolved into a federated network It provides connectivity and allows for informationsharing among all participating ISAF countries over a common secret network Data are organizedaround agreed upon ldquomission threadsrdquo that individually and collectively comprise the types ofmissions conducted throughout Afghanistan ISAF employs eight of these mission threads inAfghanistan and on the AMN Battlespace Awareness Joint Fires Joint ISR MEDEVAC C-IED Freedom of Movement Force Protection and Service Management as shown in figure 32 [6][4] The various services provided in these mission areas are shown in figure 33 [4]

Numerous battlespace awareness capabilities and tools like the sharing of significant activityreports or SIGACTS and friendly force tracking exchanges across COPs have been added overtime A list of decision support systems and capabilities currently supporting operations in thesemission threads [7] with short summary descriptions are included below

bull Land Command and Control Information Services (LC2IS) the primary NATO C2 tool toenable and improve the effective command and control of NATO Land Forces to support theLand Component Commander in the decision making process and to improve informationexchange horizontally and vertically at all levels [8]

9

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 26: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

Figure 32 AMN Mission Areas reproduced from [4]

bull COP Layer Manager Supports to ISAF Situational Awareness (SA) by providing capabilityfor creation of domain specific overlays and associated battle space object management Inaddition to that Multilateral Interoperability Programme (MIP) Gateway for informationsharing with coalition MIP compliant systems [9]

bull Joint Common Operational Picture COP Information management dissemination and In-tegration capability of existing NATO Information providers to compile a joint COP [9]

bull Joint Defence Planning Analysis amp Requirements Toolset (JDARTS) Suite of applicationsto support NATO and national capability-based defence planning Includes Deterrent Pres-ence (DP) Mission Study Tool DP Scenario Generation DP Capability Assignment LogicCalculator DP Requirements and Unit Matching and a Central Data Repository [9]

bull Allied Commands Resource Optimization Software System (ACROSS) Supports StockpilePlanning and Sustainment Planning by means of algorithms and optimisation techniques [9]

bull Global Aggregated Model for Military Assessments (GAMMA) Analysis tool for irregularwarfare on the operational level to support operational planning and the assessment ofCourses of Action (COA) Supports analysis of societal conflict and counterinsurgency [9]

bull Coalition reception staging amp onward movement (CORSOM) Supports the Reception Stag-ing Onward Movement and Integration (RSOI) of deploying personnel equipment and sup-plies during combined operations to provide Joint Force commanders with an enhanced RSOI

10

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 27: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 33 Services Provided in AMN Mission Areas reproduced from [4]

planning deconfliction and execution monitoring capability Links to other nationalAlliancesystems In-Transit Visibility support [9]

bull Effective Visible Execution (EVE) Web-based tool for movement coordination deconflictionand prioritisation Movement visibility monitoring Prior Permission Required (PPR) coor-dination with the airbases slot confirmation (Identification Friend or Foe (IFF) assignment)Management of Intra Theatre Air Support (ITAS) system supports efficient use of sharedtransportation lift assets [9]

bull Allied Deployment and Movement System NATOrsquos tool for planning coordination and de-confliction of movement and transportation operations in support of NATO force deployments[9]

bull ISAF Interim Consignment Tracking Capability (ICTC) A set of Radio-frequency identi-fication (RFID)-based tracking devices coupled with information exchange mechanism anda web-based tool for visualization and control of consignments Also referred to as ISAFInterim Consignment Tracking System (ICTS) [9]

bull Supply Distribution Model (SDM) Simulates in-theatre resupply testing robustness of sus-tainment policy against a variety of scripted ldquowhat-ifrdquo scenarios Highly scriptable simula-tion model of consumption and resupply including maritime elements convoys tankers andpipelines [9]

bull Sustainment Planning (SPM) Supports sustainment planning related requirements for sup-ply items in Classes I-V including Pharmaceuticals and Medical Materiel Assists stockpile

11

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 28: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

planners in calculating Sustainment Stockpile Requirements and Readiness Stockpile Re-quirements based on the Disarmament Demobilization and Reintegration (DDR) PlanningSituations [9]

bull Medical operations watch (MedWATCH) Medical mission management and tracking toolsupporting patient evacuation to medical facilities by means of C3 Recording of 9-liners Pa-tient Moving Requests casualtypatient details Medical Illness Simulating Trauma (MIST)reports evacuation timing [9]

bull Medical reporting (MedRPT) Automating data exchange mechanisms amp processing of medi-cal reports eg MEDSITREP MEDASSESSREP EPI-NATO Disease Surveillance SystemAn early warning and detecting capability for disease outbreaks and biological attacks bycontinuously monitoring unusual medical events signs and symptoms [9]

bull Tasker Tracker Web-based tasking management and collaboration tool integrated with Mi-crosoft SharePoint for Commands [9]

bull Tool for Operational Planning Force Activation and Simulation (TOPFAS) Supports JointOperations Planning and Force Generation Collaborative and integrated Knowledge devel-opment Systems Analysis Operations Planning and Campaign Assessment [9]

bull Radar EW and Communications Coverage Tool (REACT) Model for predicting sensor andcommunications coverage in terrain in the presence of countermeasures Includes groundand airborne radar passive radar Electronic Support Measures (ESM) multilateration andcommunications systems [9]

bull SEWOC database application (SDA) Provides a capability to allow SIGINT amp EW Opera-tions Centres (SEWOC) users to import validate query analyse and report Signals Intelli-gence (SIGINT) data at the NATO Secret security level This includes SIGINT messages anddata received from Nations and products generated by Allied Command Operations analysts[9]

bull Human Intel Management amp Reporting Tool (HMART) Theatre source registry incorporat-ing finger-print and face matching biometrics [9]

bull SIGINT Analyst Functional Environment (SAFE) Provides a searchable database of SIGINT

information at the Counter Terrorism Security Bulletin (CTSB) security level Include re-ports received from Nations and products generated by Allied Command Operations analysts[9]

bull Multi-Sensor Aerospace-Ground Joint ISR Interoperability Coalition (MAJIIC) Joint Intel-ligence Surveillance Reconnaissance (ISR) network-enabled interoperability and maximisethe use of surveillance and reconnaissance resources Collaborative employment and useof interoperable ISR sensor and exploitation capabilities Development and evaluation ofoperational technical and architectural capabilities [9]

bull Integrated Command and Control for Air Ops (ICC) Provides functional support for themost critical air C2 functions at the air component commander and Combined Air OperationsCentre (CAOC) levels These include planning and tasking generation of AODs generationof Airspace Control Orders generation of Air Tasking Order (ATO)sAir Tasking Message(ATM)s and a complete current operations capability (both offensive and defensive) [8]

12

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 29: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 3 Modern Land Force Command and Control (C2) Systems

bull Online Analyser for Networked Tactical Data Link (OANT) Protocol analyser to assessthe compliance of information flows with the information exchange protocols regulated byStandardization Agreement (STANAG) standards and specifications Supports all majormilitary and civil data link standards (Tactical Data Link (TDL) All Purpose StructuredEurocontrol Surveillance Information Exchange (ASTERIX) OTH-Gold etc) [9]

bull NATO SIMPLE Compliant Device (NSCD) It provides the capability to participate inInteroperability assessment of tactical and operational capabilities that use TDL networks Itis based on STANAG 5602 Standard Implementation for Multiple Platform Link Evaluation(SIMPLE) [9]

bull Joint Automated Deep Operations Coordination System (JADOCS) A command and sys-tem tool that helps provide strategic coordination and situational awareness at the opera-tional and tactical levels of combat It is a joint mission management software applicationthat provides an integrated set of functional capabilities for data analysis and managementmission planning coordination and execution of a variety of joint task [8]

bull JCHAT JChat provides an Extensible Messaging and Presence Protocol (XMPP)-basedchat system JChat allows one-to-one conversations user search whispers in chat roomsarchiving and retrieving previous conversations controllable file transfer broadcast servicekey-word-based notification font colouring and skinning multiple chat window views etc[8]

bull Joint Operations Center Watch (JOCWatch) A web-based incidentevent logging and mon-itoring tool for the Joint Operations Centre Incidentevent information can be updated overtime correlated and exported in various formats [9]

bull Logistics Functional Area Services (LOGFAS) Consists of five different systems developedto service the logistic and movementsrsquo of communities within NATO The LogFAS 60 ap-plication programs share a common database (LogBase) (1) ADAMS (Allied Deploymentand Movements System) (2) CORSOM (Coalition Reception Staging and Onward Move-ment) (3) DSSM (Deployment and Sustainment Simulation Model) (4) Geo Manager and(5) Trade Offs Wizard [8] [10]

bull ICC Initially AirC2 providing capabilities for integrated planning tasking intelligencetargeting and operations information management and decision support to operational andtactical level air operations during peacetime exercise crisis and conflict Grew to becomesuccessful JointC2 application (selected by UK as COP for Air Navy Land and Joint) Itis the largest operational NATO system Strong focus on user interface and user experienceICC is capable of displaying a Joint Common Operational Picture (JCOP) fully supportsthe joint targeting cycle (through JTS) and also has interfaces to get access to ISR data fromCoalition Shared Databases (CSD - MAJIIC) and display friendly force tracking information[8]

bull NATO Intel Tool Box (NITB) A productivity and collaboration environment for Intelligenceinformation related to NATO Missions It allows the management visualisation and exploita-tion of information related to Collection Coordination and Intelligence Requirements Man-agement (CCIRM) Imagery Documents Request for Information Management (RFIMS)motion imagery Standards based Widespread operational use [9] [8]

13

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 30: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

bull Joint Targeting System (JTS) JTS is NATOrsquos designated targeting tool for developing targetfolders managing target lists and maintaining a legal record of target development and targetoperations It is a joint tool with mapping and web-service capabilities It is the processof selecting targets and matching the appropriate response to them taking into accountoperational and legal limitations The process comprises the identification of a systemstructure person group or object in which an appropriate critical element or vulnerablepoint is selected against which the application of the least possible military force shouldachieve the desired politicalmilitary goal JTS includes a module for Dynamic or Time-Sensitive Targeting (TST) the Flexible Advanced C2 Services for NATO Time-SensitiveTargeting or FAST This module is designed as a coordination tool to aid in the trackingand prosecuting of time-sensitive targets and enables collaboration and efficient and timelyexchange of critical information between personnel participating in the TST process JTSis used throughout all command levels in NATO and multiple nations have chosen JTS astheir national targeting system [9]

bull Analyst Notebook Analystrsquos Notebook is a key tool to collect analyse and exploit infor-mation to target the Insurgency through focused operations Counterinsurgency operationsare complex and are unlike the conventional red and blue intelligence picture Forces haveto operate in a complex human terrain comprising multiple act-on and a constant stream ofintelligence Analystrsquos Notebook allows fusion of the information in terms of time space andcorroboration and enables the land forces to embrace and understand this complexity [9] [8]

bull Full Motion Video (FMV) Provides a robust CIS-based capability for the DisseminationStorage Archival and Retrieval (DSAR) of Near-Real-Time (NRT) FMV and FMV-derivedimagery intelligence products to ISAFrsquos operational commanders including Live-Steamingvideo visuals from Unmanned Aerial Vehicle (UAV) feed used for situational awarenessFull integration with existing NATO applications Video feeds from USUKITCA Remotevideo terminals [11]

bull Networked Interoperable Real-Time Information Services (NIRIS) Ensures tactical informa-tion sharing over IP networks between info producers (eg TDL (Link-16 Link-11 OTH-Gold) Friendly Force Information (FFI) Civ Convoy) and info consumers (eg C2 toolsLogistic tools JCOP etc) Includes recording replay translation capabilities as well as web-service and API interfaces Middleware application NIRIS provides a real-time C2 picturefor air land and maritime operations [9]

bull ISAF Force Tracking System (IFTS) The primary purpose of the IFTS is to provide jointcommanders at every echelon a clear unambiguous picture of the unfolding operationalscenario in near real-time including blue force red force and neutral position informationThis information may come from diverse coalition multinational interagency and even NGOtracking or information systems [12]

bull Interim Geo-Spatial Intelligence Tool (IGeoSIT) A web-services based COP viewer allow-ing the consumption and dissemination of overlays maintained by the different functionalservices Also allows the visualization and of Full Motion Video feeds Geo-Whiteboardingcollaboration and redlining is also available to allow collaboration between users [9]

bull Criminal Organisation Public Interest Monitor (COPIM) Is a tool to monitor criminalactivity [7]

14

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 31: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 3 Modern Land Force Command and Control (C2) Systems

An example view of how a coalition member (Germany) employs the AMN environment is shownin figure 34 [13]

Figure 34 German participation in AMN reproduced from [13]

The evolution of from 2008 until current times has occurred through an iterative theater testingassurance and validation efforts conducted by the Joint Interoperability Test Command (JITC)rsquosCoalition Interoperability Assurance and Validation (CIAV) program which enabled controllednetwork experimentation and testing pursuant to network solutions that have been later replicatedin theater [2] The initial problems that this program had to overcome included [4]

bull Coalition forces within Afghanistan could not communicate effectively and share operationalCommanderrsquos guidance information and intelligence

bull Operational Requirements were Nationally specific not oriented to Coalition Data Sharingand enterprise mission based execution

bull Different networks with inadequate cross-domain solutions resulted in poor ops planningand intelligence information exchange between US and NATO forces in ISAF

bull Communication gaps between partner nations increased risks to life resources and efficiency

15

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 32: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

While over a relatively short period AMN has succeeded to provide an infrastructure processdoctrine and advanced capabilities for coalition landjoint warfare a number of documents describeissues both in terms of the maturity and sophistication of technological solutions and also in termsof policy and procedural restrictions that hinder the collaboration for example [14]

bull National security restrictions still dominate interaction between NATO AMN and nationalsystems Information management is still in the weeds not all nations are already preparedto use AMN [15]

bull Very supportive set of applications systems and services however too many non-compatiblenational and NATO tools and huge variety of redundant apps systems and services [15]

bull Due to todayrsquos policy operational and technical limitations there are multiple CENTRIXSnetworks operating in AMN each at a single security classification level based on the informa-tion exchange requirements and the coalition membership These networks operate globallyregionally and locally in addition some of them have many members some have fewer andsome are bilateral in nature Although the means to pass information from one network toanother exists it is limited in nature and manpower intensive [16]

bull Operational Requirements initially were Nationally specific not oriented to Coalition DataSharing and enterprise mission based execution [4]

The history of AMN yielded tactical operational and policy-relevant lessons that can informfuture efforts-such as the Joint Staffrsquos Mission Partner Environment (MPE) (initially called FutureMission Network (FMN)) initiative to create a contingency network that is both effective acrossthe range of military operations and useful to a host of military and nonmilitary partners [17]This effort will also be able to take advantage of availability of new technological solutions whichcontinuously evolve and will be leveraged to provide enhanced connectivity more sophisticatedcapabilities to establish increased situational awareness and automated tools for collaborativedecision making

32 Future Mission Network

Based on the development of the AMN and the experiences realised from the Afghan mission theMilitary Committee (MC) recognised the potential of the AMN to act as a conceptual framework forthe FMN It was at this point that Allied Command Transformation (ACT) in close coordinationwith Allied Command Operations (ACO) was tasked to develop a generic concept informed bythe best practices and lessons learned from the implementation of the AMN [18]

At the end of 2012 the FMN Concept was agreed upon by the MC and noted by the NorthAtlantic Council (NAC) The aim of the concept is to provide overarching guidance for establishinga federated Mission Network (MN) capability that enables effective information sharing amongNATO NATO nations andor non-NATO entities participating in operations A federated MNwill be based on trust and willingness and will enable greater C2 in future NATO operations TheFMN Concept describes the FMN as a capability consisting of three components

16

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 33: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 3 Modern Land Force Command and Control (C2) Systems

1 Governance

2 FMN Framework and

3 Mission Network(s)

On 21 November 2012 the MC agreed on the FMN Concept as the basis for the development of anImplementation Plan that defines the implications for NATO and member nations and tasked ACTin coordination with ACO and NATO Communications and Information (NCI) Agency and theactive involvement of NATO nations and NATO partner nations to develop the ImplementationPlan This plan has been set to be called NATO FMN Implementation Plan (NFIP) The workon this highly important concept has begun based on the good experience and collaborationmade during the concept development To assist in the Implementation Plan development anorganisation was created consisting of six working groups (WG)) each group exploring a specifictopic

1 Governance

2 Baseline Components

3 Human-to-Human Services and Community of Interest Services

4 Standing Capability Components

5 Certification Process

6 Training

In addition rdquoFood-for-Thoughtrdquo papers were to be developed and presented to be discussed duringtwo workshops (MarchJune 2013) with the member nations This important step has been vitalto the success of working with the nations on the FMN Concept Nationsrsquo involvement is essentialas early on in the process as possible in order to obtain feedback views opinions and ideas whichwill feed the process and the implementation document

The NFIP document will present the proposed implementation of the Concept It is this documentand its contents that will provide the decision makers with sufficient details about the way aheadand the proposed solutions The importance of this document is to give an overarching viewof how to establish and evolve the FMN Concept Governance and Framework that will resultin the capability to establish Mission Networks And by establishing the MN it will furtherenable effective information sharing among NATO NATO nations andor non-NATO entitiesparticipating in operations The FMN its Concept and framework support the Connected ForcesInitiative (CFI) and Smart Defence two essential pieces to NATO and ACT Around Novembertimeframe the term FMN was replaced by Joint Staff to be MPE A high level view of thisenvironment with its mission threads is shown in figure 35 [19]

In the open literature the terms FMN and MPE are used interchangeably with the latter usedmore consistently in the US papers A 2014 NATO view of FMN is presented in [20] FMN willprovide federated mission networking which means

17

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 34: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

Figure 35 Mission Partner Environment reproduced from [19]

bull Federated mdash there is no one king Participants commit to common processes organisationand provide materiel

bull Mission mdash operational (including exercises) scenario driven

bull Networking mdash interaction of people processes and technology to exchange informationandor services

bull Governance mdash organizations and processes to govern and manage the Framework and eachMission Network Instance

bull The Framework mdash Pre-planned ldquostuffrdquo to minimize the time and money required to generatea mission network in a federation

bull Mission Network Instance(s) mdash one of a kind federated network(s) (people processes tech-nology) tailored for a specific operation (or exercise) and using the pre-planned informationand arrangements (ldquothe stuffrdquo)

How the coalition partners collaborate in the mission network is shown in figure 36 [20]

The planned evolution phases and corresponding capabilities are shown in figure 37 [20]

18

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 35: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 36 Participation Options reproduced from [20]

The coalition partners invest to enhance or evaluate FMNMPE The planned US investments forenhancements during 2013-2015 are described in [21] which include the following

bull Continue the efforts initiated for FY 2013 and respond to unpredictable operational issuesand shortfalls Interoperability assessments will be conducted to solve warfighter problemsincluding coalition challenges FY 2014 assessment objectives are focused on CyberspaceMission Partner Environment Common Operational Picture Wireless to the Tactical EdgeJoint Fires Capabilities Data Strategy Implementation and Information Sharing Capabili-ties

bull AMN CIAV Transition and Assessments mdash AMN is the primary C5ISR network for ISAFin Afghanistan C4 Assessments Division (C4AD) is supporting the assessment of CoalitionMission Threads (CMT)s and Coalition Tactics Techniques and Procedures (CTTP)s toidentify and correct interoperability problems

bull Bold Quest 2014 (BQ14) Technical Support and Interoperability Assessments mdash Assess in-teroperability and document identified deficiencies of select systems within the joint firesmission thread during BQ14 operational venues

bull Digitally-Aided Joint Fires Support and Assessment mdash Assess the implementation of variousmessaging standards for Close Air Support (CAS) mission execution

19

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 36: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

Figure 37 FMN Evolution Phases reproduced from [20]

bull Coalition Interoperability Assessments mdash Conduct interoperability assessments between se-lected systems during the Coalition Warrior Interoperability Experiment (CWIX) 2014 event

bull Deliberate and Dynamic Targeting Interoperability Assessment mdash Assess the system inter-operability of selected systems during Exercise Terminal Fury 2014

bull Command Control Communications Computers Intelligence Surveillance Reconnaissance(C4ISR) Interoperability Assessments mdash Assess interoperability of Service systems to GlobalCommand and Control System-Joint (GCCS-J)

bull Unified Cross Domain Management Office (UCDMO) Enterprise Cross Domain Solutions(ECDS) Capability Assessment mdash Conduct a capability assessment of the specified ECDSmeasuring the functional strengths and weaknesses against UCDMO prescribed criteria

bull MPE US Development and Assessment and Federated Mission Networking Developmentand Support mdash Provide interoperability assessments of selected US and Coalition systems

bull Network Integration Evaluation (NIE) Interoperability Assessment mdash Assess potential net-worked and non-networked capabilities in a robust operational environment

bull Tactical Infrastructure Enterprise Services (TIES) Coalition Warfare Program (CWP) In-teroperability Assessments mdash Assess the capability of sharing data from authoritative datasources using web services in a C2 Core conformant standardized data format

20

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 37: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 3 Modern Land Force Command and Control (C2) Systems

bull Distributed Common Ground System-Army (DCGS-A) Interoperability Assessment mdash As-sess DCGS-A v317 (32x) interface to the Modernized Integrated Database (MIDB)

Many of the investments listed above are focused on interoperability issues including the assess-ment of interoperability of the US joint command and control system (GCCS-J) with FMNMPEwhich is extremely important and should be done by every coalition member to make sure thatfuture coalition missions have fewer issues of interoperability

33 Canadian Land Command and Control (C2)

As shown above Canada used its LCSS with AMN during their participation in Coalition combatoperations in Afghanistan

The LCSS is a system of systems that integrates all the tools that Army commanders need toeffectively direct troops in all phases of military operations and provides enhanced Blue PositionalAwareness [22] The C2 solution in LCSS is based on service oriented architecture and is builtto common data standards based on the Joint Consultation Command and Control InformationExchange Data Model (JC3IEDM) data model [23] The system integrates many applicationsenabling commanders and staff to seamlessly exchange a myriad of tactical information betweenJoint and Coalition forces from operational level HQ to forward operating bases and tacticalvehicles

Battle planning and management is accomplished using BattleView a digital map-based appli-cation which provides the common operating picture Blue PA reporting terrain analysis andCourse-of-Action development

To improve efficiency of information management and communication the solution includes aTactical Information Management System (TIMS) that provides a collaborative tool for incidentmanagement document management and to automate reports and returns generation consolida-tion and tracking Collaboration is also facilitated with the Transverse Chat application whichprovides multiple chat rooms for real time communication between users For sensor managementthe solution includes the Surveillance Command and Control Planning Suite (SC2PS) to displayfull motion video RADAR GMTI and other STANAG 46074609 compliant systems This keyapplication enables users to view sensor feeds that are geo-referenced and stored in the CoalitionShared Database at any LCSS workstation TacticalView is the LCSS Battle Management Ap-plication for use on tactical vehicles including tanks and infantry fighting vehicles TacticalViewprovides the COP to the vehicle commander and crew to enhance their situational awareness andenhance security and effectiveness It is a key application in the LCSS suite and includes a fullyintegrated Geographic Information System (GIS) which is connected to the vehicle Global Posi-tioning System (GPS) to enhance navigation and positional awareness at the sub-unit level Inaddition TacticalView provides the ability to share contact information and operational reportsand returns automatically [23]

In the 2010-2011 time frame the first Coalition Attack Guidance Experiment (CAGE) was con-ducted originally hosted by the Canadian Forces Warfare Centre (CFWC) Joint Fires Support Bat-tle Lab to analyze evolving Coalition C2 configuration intended for ISAF CAGE Working Group

21

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 38: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

requesting Central Technical Support Facility (CTSF) support because of its interoperability andnetwork expertise This experiment analysed a number of interoperability issues between the C2systems which are part of AMN including the transfer of data between LCSS and JADOCS Is-sues have been detected regarding OTH-Gold type message exchanged and recommendations weremade about correcting the problem [22] As mentioned above it is very critical that interoper-ability between the C2 systems in AMN and FMN are assessed to ensure efficient operation incoalition warfare

Considering that the LCSS is controlled under Canadarsquos Control Goods regulation further detailedregarding the C2 capabilities of the LCSS cannot be included in this section

34 Land Command and Control (C2) Applications in CoalitionOperations

This section describes some of the decision support capabilities which potentially include function-ality useful in also maritime coalition warfare listed in sections 31 in more detail

341 Land Command and Control Information Services (LC2IS)

The development of NATOs LC2IS was proposed by Department of Defense (DoD) CombinedJoint Task Force ndash 76 (CJTF-76) in partnership with ACT around 2005 to enhance the degree ofinformation sharing particularly in the C2 domain between the CJTF-76 and the ISAF whichwas assessed to be less than adequate to meet the minimum military requirement for an expandingISAF The proposed LC2IS was to be based on Command and Control Information ExchangeData Model (C2IEDM) to provide a new capability and to create the conditions where nationalimplementations of C2IEDM-compliant systems could be brought to the operation by ISAF nations[24] In support of this development the MIP program comprised of member nations that haveacceded to the requirements of the baseline data model and information exchange mechanismswas established which in 2005 merged efforts with the NATO Data Administration Group andproduced a JC3IEDM The interoperability operational concept is shown in figure 38 [24]

A spiral development process was undertaken to prepare NATOrsquos LC2IS for introduction intotheater in conjunction with the US Maneuver Control System version 64 (MCS v64) and theSituational Awareness Data Interchange (SADI)GCCS

Currently LC2IS is the primary NATO C2 tool to enable and improve the effective commandand control of NATO Land Forces to support the Land Component Commander in the decisionmaking process and to improve information exchange horizontally and vertically at all levels [8]In the planning phase LC2IS supports the collaborative production of Land Operations Plansin coordination with other component Commands making full use of available planning toolsLC2IS supports the development of the Land element of the Joint Operation Plans and of theForce Generation Process thus contributing to the generation of a Recognized Ground Pictureshared between Allied Commands In the execution phase LC2IS provides the user with multi-theatre Situation Awareness and disseminates relevant information to support ground operations

22

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 39: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 3 Modern Land Force Command and Control (C2) Systems

Figure 38 Interoperability Operational Concept reproduced from [24]

through secure high-speed and reliable information flow These capabilities and the additionalenhancements planned for future increments ensure LC2IS is recognized as a key tool for thesupport of Command and Control of NATO Joint Operations with a Land focus LC2IS imple-ments NATO and MN interoperability standards ensuring that information exchange with otherNATO and national systems results in an accurate and complete RGP coherent with other com-ponent pictures Data replication (MIP block-2 C2IEDM) formatted text messages Allied DataPublications number 3 (ADatP-3) and graphical overlays provide accurate timely consistent andcoherent information exchange within and between headquarters LC2IS makes use of the latestweb-based technologies providing secure role-based access to mission-critical information througha Web Portal tailored to each service consumer The emerging Increment 11 includes also newcapabilities supporting implementation of an initial ldquocloudrdquo application environment

342 Joint Automated Deep Operations Coordination System (JADOCS)

JADOCS software provides joint fire support management and COP capabilities JADOCS com-plements the Mission Command architecture with joint and collaborative capabilities that can beemployed and tailored based on the unit mission and operational situation JADOCS softwareprovides integration between multiple joint C2 systems of the uniformed services involved in thetargeting process at US Air Force (USAF) US Navy (USN) and Marine Corps Operation Cen-ter (MCOC)s Marine Expeditionary Force (MEF)s Fleet MOCs and staff sections at the regionalCombatant Command (COCOM)s Special Operations Command (SOCOM) and Army Battle-field Coordination Detachments (BCD)s Army Service Component Commands (ASCC) Corpsand Divisions The final version of JADOCS Version 20 with new functionality has been fundedwith work beginning in FY2014 JADOCS V20 is required to incorporate critical Joint require-ments into JADOCS These requirements include modification and updates for joint interfaces

23

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 40: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

updates to databases and creation of non kinetic fires targeting [25]

The JADOCS is used at several levels for both tactical and strategic planning and is better suitedfor planning JADOCS has several functions critical to conducting operations that should not beoverlooked although they will be only lightly touched upon here The main display for JADOCSis a digital map that displays control measures threat information and COP feeds What setsthis apart from Command and Control Personal Computer (C2PC) is the added functionality ofseveral plug-in type subsystems With these subsystems it is possible to conduct planning down tothe company level unfortunately it is not optimized for planning at these lower levels JADOCSis also capable of plotting an air corridor and is capable of deconflicting the route made AnotherJADOCS feature used with some difficulty is the three-dimensional (3-D) viewer This featureoverlays a digital map or satellite image on a 3-D rendering of the terrain This in turn is usedto visualize the terrain and to allow the tactician to evaluate his or her position by comparativeanalysis Finally JADOCS uses a chate-mail subsystem for communicating between locationsThe versatility of this system is one reason why JADOCS is used by the Navy Air Force andArmy [26] JADOCS functions include calls for-fire close air support coordination and range fanplotting

343 Joint Defence Planning Analysis and Requirements Toolset (JDARTS)

The NCI Agencyrsquos JDARTS is an integrated federation of software applications developed to sup-port NATO and national capability based Defence Planning within NATO [8] JDARTS deliversa distributed collaborative networked environment for joint capability based defence planningJDARTS Capability Assignment Logic consolidates output from detailed operational analysis andsimulation studies with expert military assessments by NATO defence planners The toolset pro-vides an integrated federation of complementary applications for scenario based analysis TheJDARTS toolset consists of 5 major functional components

bull Defence Planning Mission Study Tool (D-MIST) to support joint capability based missiontask analysis (Military Estimate and Task Decomposition) for representative mission typesand planning situations D-MIST supports development of a clear audit trail between theidentification of capability requirements and the relevant military estimate From the de-tailed military analysis the mission is decomposed in a hierarchical structure identifying themandate operational objectives and finally all required and implied tasks for an operation

bull Defence Planning Scenario Generation (D-SIGN) application provides a map based interfacefor the generation and development of operational scenarios or planning situations D-SIGNis implemented as an ad in to an advanced mapping and geospatial analysis tool

bull Defence Planning Capability Assignment Logic Calculator (D-CALC) provides the environ-ment for the specification and execution of Capability Assignment Logic

bull Defence Planning Requirements and Unit Matching (D-RUM) support unit capability pre-processing and automatic comparison (optimization) for the generation of forcecapabilitypool requirements

bull Shared data environment the Central Data Repository (CDR)

24

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 41: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 3 Modern Land Force Command and Control (C2) Systems

344 Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition(MAJIIC)

MAJIIC was established as a project under the multinational coalition surveillance and recon-naissance memorandum of understanding (CSR MOU) The nations participating in MAJIIC areCanada France Germany Italy Netherlands Norway Spain United Kingdom and the UnitedStates of America The MAJIIC capability developments as planned currently are shown in figure39 [27]

Figure 39 MAJIIC Capability Development reproduced from [27]

The MAJIIC project addresses the ability to collaboratively employ and exchange data froma wide variety of ISR sensors and sensor types in a network-enabled manner including closecoupling between the ISR assets and the NATO and national C2 environments [28] The objectiveof MAJIIC is to address interoperability in a flexible and wide-reaching manner ranging fromsmall tactical systems usually assigned to tactical commands and all the way up to highly capablestrategic multi-user systems Although the name of the project indicates an emphasis on aerospace-borne ISR systems the project aims at addressing any sensor platform category including space-based airborne ground-based or maritime as well as manned and unmanned subsets of these Thesensor data types addressed in MAJIIC include ground moving target indicator (GMTI) radarsynthetic aperture radar (SAR) electro-optical (EO) and infra-red (IR) imaging and video sensorselectronic warfare support measures (ESM) sensors and artillery locating radar

MAJIIC aims to enable interoperability between ISR and C2 systems through the use of commoninterfaces for data formats and exchange mechanisms leaving the inner workings of each nationalsystem outside of the scope of the project and only requiring minor external interface modificationsto each system

MAJIIC is designed to provide a true network-enabled capability enabling a wide variety of usersat different locations and levels of command to access and retrieve data in accordance with own

25

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 42: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

tasks needs priorities and preferences The MAJIIC architecture is also compliant with theNATO Network Enabled Capability (NNEC) initiative

The first phase of MAJIIC development took place over 2005-2009 time frame and currently thesecond phase is on-going over 2011 - 2015

26

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 43: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 4

Global Command and Control System

41 Global Command and Control System - Maritime (GCCS-M)

GCCS-M is the maritime implementation of the GCCS family of systems It supports decisionmaking at all echelons of command with a single integrated scalable Command Control Com-munications Computers and Intelligence (C4I) system [29] The C4I system fuses correlatesfilters maintains and displays location and attribute information on friendly hostile and neutralland sea and air forces integrated with available intelligence and environmental information Itoperates in near real-time and constantly updates unit positions and other situational-awarenessdata GCCS-M also records data in databases and maintains a history of changes to those recordsSystem users can then use the data to construct relevant tactical pictures using maps chartstopography overlays oceanographic overlays meteorological overlays imagery and all-source in-telligence information coordinated into a common operational picture that can be shared locallyand with other sites Navy commanders review and evaluate the general tactical situation plan ac-tions and operations direct forces synchronize tactical movements and integrate force maneuverwith firepower The system operates in a variety of environments and supports joint coalition al-lied and multinational forces GCCS-M is implemented afloat and at select ashore fixed commandcenters

The GCCS-M program is designated an Acquisition Category IAC evolutionary acquisition pro-gram with development and implementation progressing in increments The acquisition strategycalls for each GCCS-M increment (major release) to proceed through acquisition milestone reviewsprior to fielding The program is operating in two simultaneous acquisition increments

Increment 1 (GCCS-M Version 40 and prior) is in deploymentsustainment and Increment 2(GCCS-M Version 41) completed a Fielding Decision Review (FDR) on August 16 2011 result-ing in authorization of full fielding of Increment 2 force-level and unit-level configurations TheIncrement 2 group level configuration is in the integration and testing phase with an operationaltest planned for the second quarter of FY 2014 and an FDR planned for the first quarter of FY2015 GCCS-M includes efforts necessary to ensure synchronization and interoperability with theGCCS family of systems

27

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 44: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

The currently fielded MOCs in the US in addition to GCCS-M also include the CENTRIXSndashMaritime Air Defense System Integrator Radiant Mercury Analyst Notebook Missile DefensePlanning System Command and Control Battle Management and Communications System C2PCas well as JADOCS [29] These systems together augment the C2 capabilities of GCCS-M witha wide range of additional decision support capabilities some of which are common with the landsystems discussed in the previous section

42 Global Command and Control System - Joint (GCCS-J)

GCCS-J is the USArsquos system of record for the command and control of joint and coalition forces Itincorporates the force planning and readiness assessment applications required by battlefield com-manders to effectively plan and execute military operations Its COP correlates and fuses data frommultiple sensors and intelligence sources to provide warfighters the situational awareness neededto act and react decisively It also provides an extensive suite of integrated office automationmessaging and collaborative applications GCCS-J incorporates the latest commercial computerhardware software and communications technology Through an innovative evolutionary acquisi-tion strategy GCCS-J is able to rapidly and cost-effectively field new applications as requirementsevolve and technology advances GCCS-J is fielded at many sites worldwide all networked via theDoDs classified private Intranet It is designed and implemented to provide USA warfighters theinformation superiority required to prevail now and well into the 21st century [30]

The 2013 update of GCCS-J consists of hardware software (commercial off-the- shelf and govern-ment off-the-shelf) procedures standards and interfaces that provide an integrated near real-timepicture of the battlespace necessary to conduct joint and multi-national operations GCCS-J con-sists of a clientserver architecture using open systems standards government-developed militaryplanning software and an increasing use of World Wide Web technology [31] GCCS-J consists oftwo components

bull Global v43 (Force Protection Situational Awareness Intelligence applications) to includethe Global Lite v10 variant (Situational Awareness Intelligence and Cross-functional ap-plications)

bull Joint Operation Planning and Execution System (JOPES) v4203 (Force EmploymentProjection Planning and DeploymentRedeployment applications) used to monitor planand execute mobilization deployment employment and sustainment activities associatedwith joint operations

GCCS-J also comprises Status of Resources and Training System (SORTS) and GCCS-T GCCS-T is a Top Secret (TS)-level system and provides the capability to transfer Focal Point (FP)information via Web news electronic mail and secure file transfer protocol [30]

The SIPRNet is the transport mechanism for GCCS-T GCCS-T data is cryptographically isolatedfrom the SIPRNet using approved TYPE-1 encryption devices Sites must be connected to theirserver sites through an approved TYPE-1 encryption device GCCS-T may only communicatewith other TS systems

28

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 45: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 4 Global Command and Control System

43 Global Command and Control System - Army (GCCS-A)

The C2PC system is the main component of the Global Command and Control System-Army(GCCS-A) GCCS-A was developed and still used by the Marine Corps The Army uses this systemat the division level and higher primarily for situational understanding Situational understandingis provided by the COP This is done by showing control measures collected over the networkon a digital map and more important displaying enemy and friendly positions The purposeof the COP is to ensure there is functional consistency among the different views The threatlocations are collected by way of databases throughout the network Friendly locations are usuallyinput manually by the unit or through databases that supply the information as part of the airpicture when collected through radar or through the Blue (friendly) Force Tracker database It isa difficult and unwieldy system and not well suited for planning [26]

44 GCCS Future Evolutions

441 Maritime Tactical Command and Control (MTC2)

Maritime Tactical Command and Control is a software program follow-on to the GCCS-M programof record which will provide tactical C2 capabilities and maritime unique operational level of warcapabilities not supported by the joint C2 effort [29] The evolution of GCCS-M to MaritimeTactical Command and Control (MTC2) is shown in figure 41 [32]

Figure 41 GCCS-M Evolution reproduced from [32]

29

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 46: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

Future fielding plan for MTC2 will include all echelons of command within the Navy MTC2 willretain capability of GCCS-M 41 system while ultimately providing a suite of maritime applicationsas part of an ldquoApplication Storerdquo concept that enables enhanced situational awareness planningexecution monitoring and assessment of unit mission tasking and requirements

MTC2 completed a Materiel Development Decision the first quarter of FY 2013 Command andControl Rapid Prototype Continuum Transition Readiness Assessment in the second quarter of FY2013 and an Analysis of Alternative in the third quarter of FY 2013 Following the MDD in FY2013 MTC2 was designated as a ldquoRapid ITrdquo acquisition program by Program Executive Officer(PEO) Command Control Communications Computers and Intelligence (C4I) The PEO ispreparing to execute an initial build decision for Release 1 in FY 2014 and expects formal approvalas a program of record in FY 2014 The MTC2 program will definedevelop reference architecturedevelop software complete Independent Technical Assessment (Phase II) and conduct Integratedand Operational Test in late-FY 2014 or early FY 2015

442 Net Centric Enterprise Services (NCES)

The next generation GCCS will transition into the Net-Centric Enterprise Services (NCES) archi-tecture The NCES will enable the secure agile robust dependable interoperable data-sharingenvironment for Global Coalition National Government and Governmental components and agen-cies enabling business and intelligence users to share knowledge on a global network This inturn will facilitate information superiority accelerating decision-making effective operations andnet centric transformation to decision superiority and superior effects NCES enables informationsharing by connecting people and systems that have information (data and services) with thosewho need information

bull For people who have information NCES provides global information discovery and deliveryservices

bull For people who need information NCES provides global services to discover and retrieveinformation

NCES provides a framework for better access to information enhancing its reach richness anddepth as a way to promote superior decision-making across the coalition and associated commu-nities The infrastructure enables net-centric operations to drive collaboration among people andsystems The approach will provide unprecedented visibility in the ability to measure the con-sumption and value of information and to assess needs without compromising affordability [33]NCES will make superior decisions a strategic advantage for coalition nations NCES is a set ofloosely coupled net-centric services on SIPRNet and NIPRNet that facilitate information sharingand interoperability within and across the Warfighter Business and Intelligence Mission Areasas shown in figure 42 [34]

30

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 47: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 4 Global Command and Control System

Figure 42 NCES Services reproduced from [34]

443 Joint Mission Planning System (JMPS)

The Joint Mission Planning System (JMPS) is still in the development stage Its main featureis a digital map with control measures layered on top It is capable of displaying both the COPand threat graphics JMPS appears to be an updated version of Portable Flight Planning System(PFPS) with a little bit of C2PC mixed in The PFPS was originally an Air Force system used toplan missions at the flight or individual level which has been expanded with a number of plug-inapplications to conduct detailed planning The JMPS software and capabilities development havebeen done using a more modern methodology using Microsoft eXtensible Markup Language (XML)allowing it to interface with Army Battle Command System (ABCS) and to eliminate currentproblems of compatibility between systems for such things as air corridors [26]

31

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 48: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

This page is intentionally left blank

32

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 49: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 5

Interoperability in Coalition LandOperations

51 NATO Programs for Interoperability

Information technology is undergoing a fundamental shift from platform-oriented computing tonetwork-oriented computing Platform-oriented computing emerged with the widespread prolif-eration of personal computers and the global business environment These factors and relatedtechnologies have created the conditions for the emergence of network-oriented computing Thisshift from platform to network is what enables the more flexible and more dynamic network-oriented operation The shift from viewing partners as independent to viewing partners as part ofa continuously adapting ecosystem fosters a rich information sharing environment NATO use ofthe NATO Interoperability Standards and Profiles (NISP) will provide a template for new systemsdevelopment as well as assist in defining the path for existing systems to migrate towards net-enabled operations NISP provides the necessary standards and profiles to support ConsultationCommand and Control (C3) interoperability by assisting in the transition to the NNEC Thesestandards are documented in great detail in [35] [36] [37] [38] [39]

The structure of the NISP is determined by several factors

bull Ease of use for the users of the NISP

bull Implementation strategy of the NNEC strategy vision

bull Nature of standards profiles and design rules

The strategies for the NNEC Development Strategies are shown in figure 51 [40]

The need for making data Visible Accessible Understandable and Interoperable in an NNECService-Oriented Architecture (SOA) environment is not fully addressed in current STANAGAs part of the multi-year standards transformation effort NCI Agency has developed under

33

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 50: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

Figure 51 NNEC Development Strategies reproduced from [40]

sponsorship of ACT the STANAG Transformation Framework (STF) to address this problem inall STANAG message formats

OTH-Gold is a text-based message format mainly used in the maritime domain It providesfor a message set similar in structure and syntax to ADatP-11 Message Text Format (MTF)messages with slant-delimited fields making up line-based Sets that are grouped into MessagesItrsquos governed by the ldquoOperational Specification for Over-the-horizon Targeting Goldrdquo publishedby USA Navy Center for Tactical Systems Interoperability The STF XML Schemas governingtext-based information exchanges have been used to capture the Data Element Dictionary andMessage Structure of OTH-Gold although itrsquos not a NATO STANAG This demonstrated thefollowing

bull STF can be successfully applied to OTH-Gold for capturing the DED and MS

bull OTH-Gold uses a nesting structure with one Set amplifying the previous The OTH-GoldMessage Structure STF representation can be enhanced to also indicate this nesting aspectThis is foreseen in the next version of the STF

bull The OTH-Gold specification does not provide unique identifiers for its Data Elements Aninitial approach has been taken to assign the DECI and DEI numbers although furtherharmonisation is still required

34

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 51: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 5 Interoperability in Coalition Land Operations

52 USA Programs for Interoperability

Net-Enabled Command Capability (NECC) program is in a Technology Development phase InJuly 2008 the Defense Acquisition Executive authorized continued work to refine cost estimatesconfirm technical maturity and clarify management provisions prior to entry into the System De-velopment and Demonstration phase [41] NECC is the DoDs principal Command and ControlCapability (C2C) that will provide access to a net-centric strategic operational and tactical envi-ronment NECC is a family of net-centric services comprised of software applications and databasesimplemented using service-oriented architecture technology Functionality is provided through asoftware architecture composed of Capability Modules that are collections of net-centric servicesor data providing an operationally useful capability Operators will access NECC via a standardGlobal Information Grid computing node on a physical network architecture consisting of operatorclients and sitesnodes that access Capability Modules (on both classified and non-classified net-works) The objective ldquomission spacerdquo for the NECC encompasses command capabilities and C2activities that extend from the National Military Command System (NMCS) through the domainof the existing GCCS Family of Systems (FoS)

Figure 52 GCCS-M transition to NECC reproduced from [42]

The DoD development NECC has been planned in three increments

bull Increment 1 was intended to provide net-centric capabilities which will replace the existingGCCS FoS Beginning in FY10 and completing in FY17 the DoD will initially extend NECCcapabilities to a Service Joint Task Force at one geographic Combatant Command withsubsequent NECC fieldings to users where GCCS FoS is currently accessed and used

35

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 52: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

bull Increments 2 and 3 will provide NECC capabilities beyond that of the current GCCS FoS

Joint Commanders will use the NECC to accomplish joint global command and control Thephases for transitioning GCCS to NECC is shown in figure 52 [42]

Commanders intend to use the NECC to

bull Link the National Command Authority to the Joint Task Force and Servicefunctional com-ponents down to the unit level

bull Access display and understand information necessary for the warfighter to make efficienttimely and effective decisions

bull Achieve decision superiority and to execute joint operations planning

While no documents were found to confirm that the NECC program is consistent with NCESarchitecture and sufficient documents were not found to do the detailed comparison between themit makes logical sense that they should be

36

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 53: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 6

Recommendations for GCCS-MReplacement

61 SoftwareSystem Functions Recommended for Next Genera-tion GCCS-M

In section 3 two basic types of functional capabilities are identified that provide enhanced col-laboration between coalition members and help enhance situational awareness For enhancedcollaboration the functional capabilities include

bull VOIP telephone connectivity

bull Chat

bull Text Chat also named as JCHAT+

bull Email

bull Web browsing

bull SVTC

In the current environment of commercial connectivity where all naval personnel are accustomed touse such cyberspace functions outside of their service they would be very efficient in their roles ifgiven such capabilities to use during their operations Such functionality is even more important forthe Canadian Navy than to most other coalition members considering that Canadians are viewedto have a more multinational nature and are easier to communicate with [44] than with the USNavy During the Iraq war from December 2001 until the end of October 2003 senior Canadiannaval officers exercised the unique responsibility of commanding a multinational coalition fleetgathered in the Arabian Sea and besides their commanding role Canadian Navy has recognized itsldquoforce multiplierrdquo potential by acting in a ldquoGateway C4ISRrdquo capacity between the USN and lesswell-equipped coalition members As observed by a senior Canadian naval officer ldquoTechnological

37

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 54: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

Figure 61 AMN Collaborative Functions reproduced from [43]

solutions are being developed to overcome these obstacles however a restrictive information sharingculture in the US is proving to be as difficult as the technical one Until these problems are resolvedthe Canadian Navyrsquos necessary vision of seamless technological procedural interoperability withthe USN will remain highly problematic [44]rdquo With additional functionality to be able to usemodern communication methods on one hand the communication with USN will be less difficultand on the other Canadian Navy can take on the role of helping lesser equipped Navies to betterparticipate in the coalition much easier

Figure 61 [43] demonstrates the elements of collaboration between partners in AMN identifyingfunctionality for interoperability that has been used in current land warfare and is recommendedfor next generation Naval C2 which are

bull FILE - exchange of files and documents

bull FMV - video exchange

bull CIDNE - Web browser

bull WEB

bull CHAT

bull EMAIL

bull VOIP

38

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 55: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 6 Recommendations for GCCS-M Replacement

As shown in the figure these functions provide interoperability via the US Secret network (USSIPR) or NATO Secret (NS) Wide-Area network (WAN) as necessary In past coalition operationsthe Canadian navy operated within these networks and availability of such functions would en-hance their efficiency as a coalition member Note that FMV (described in section 3) is more thana simple Internet tool It provides a capability for motion video dissemination storage archivaland retrieval in near-real-time At the same time in the reviewed documents no analysisdeci-sion support capabilities were identified for FMV hence it is identified together with the othercollaborative functions

The figure above also shows sharing of COP Within the level of detail available in open literatureCOP is collaboratively built in both land and naval C2 The quality of the established picturedepends on the availability of up to date information from as many sources as possible and thealgorithms used to integratefuse the information In terms of improving the quality of COP fornaval C2 it is not feasible to leverage algorithms from land C2 as these algorithms are usuallyoptimised for the specifics of information that has to be fused These will need to be evolvingand maturing within their own information framework However improving information exchangeand sharing approaches as well as enabling exchange of additional sources of information (egintelligence video information quality and pedigree GIS data etc) will contribute into a higherquality COP In this perspective land C2 systems provide ability to share a wider variety ofinformation and based on the limited detail available from open sources they also have a lessrestrictive information sharing strategy

The section 3 also listed a large number of decision support capabilities which provided function-ality to build situational awareness and collaborate in coalition operations The current version ofGCCS-M does not include any such functionality other than correlation and fusion methods fortactical situation compilation

A 2013 presentation [45] reports that Navy commanders struggle to Perform C2 with TodayrsquosSystems It involves labor intensive and repetitive processes to collect information for full SAThey create and maintain C2 artifacts manually in PowerPoint Excel web-based file archives(SharePoint) and isolated mission-specific tools Current Navy C2 system answers only ldquowhordquoand ldquowhererdquo while Future Navy C2 systems must address ldquowhatrdquo ldquohowrdquo ldquowhenrdquo ldquowhat isrdquoldquowhat wasrdquo ldquowhat nextrdquo and ldquowhat ifrdquo In other words current Navy C2 system providesfunctionality supporting only the Observe phase of the Observe Orient Decide Act (OODA) loopwhile Future Navy C2 systems must provide functionality for also Orient Decide Act phases

Many of the land C2 decision support capabilities listed in section 3 provide functionality sup-porting collaborative decision making in many of the OODA phases Unfortunately not enoughinformation was possible to find on Internet to learn more in terms of the level of maturity levelof automation as well as algorithmic capabilities of the specific functionality in these land C2capabilities Just based on high level descriptions functional capabilities supporting 3 importantareas of OODA decision making are identified within the above referenced land C2 decision supportcapabilities and recommended below for the future Naval C2 functionality as follows

1 LC2IS JADOCS JDARTS TOPFAS JTS and GAMMA provide functionality for situ-ational analysis mission planning and collaborative operational tactical and defence plan-ning including target development and target operations and courses of action analysis Such

39

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 56: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

functionality falls within the decide and act phases of the OODA loop and are necessary ina C2 system

2 MAJIIC SDA SAFE and NITB provide functionality for ISR and specifically intelligenceinformation management sharing and collaborative employment and exploitation of ISRinformation sources The GCCS-M system provides intelligence data however does notprovide functionality for management analysis sharing etc of such data As discussedabove such functionality will enhance the ability to develop COP and more over can also beused for situation understanding supporting the orient phase of the OODA loop

3 COP Layer Manager IFTS REACT SDM ICTC IGeoSIT and Tasker Tracker providefunctionality for situation modeling scenario analysis and visualization used for battlespacesensor coverage information sharing ldquowhat-ifrdquo scenarios etc aspects of situation analysissupporting the orient and decide phases of the OODA loop

While it is very likely that the corresponding naval C2 functions will need to be specific to navalcoalition operations but the detailed analysis of the land C2 functions will provide very valuableinsight ensuring that the naval C2 functions are based on the lessons learned from coalitionoperations of many years

62 Interoperability Recommendations

Regarding the interoperability as mentioned above the literature found points out that the UShas been investing to test and correct the interoperability issues with GCCS-J while the NISP hasdemonstrated ability to adapt OTH-Gold gold message formats for exchange within the NNECtherefore it appears to be less risky to adopt NNEC

63 Procedure and Policy Recommendations

For Policy recommendation the coalition operations in AMN have demonstrated the need to shiftthe information sharing paradigm from ldquoneed to knowrdquo to ldquoneed to sharerdquo and again bearingin mind Canadarsquos specific role in relationships with other nations it is recommended that RCNevaluate the possibility of such paradigm change

40

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 57: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 7 Conclusion

Part 7

Conclusion

This document provides the results of the study which analysed open literature on modern landsystems successfully deployed in coalition operations to identify functional and hardware capabili-ties that may be useful in a GCCS-M replacement The study included identification of innovativeshifts in procedure or policy that have made modern land force systems uniquely successful

First a literature survey was conducted which selected over 200 reports presentations and otheropen publications for the study The collected documents cover discussions on various aspects of

bull Existing land C2 systems including the AMN its evolution into FMN (or MPE) and theCanadian LCSS

bull The US GCCS-M GCCS-J and GCCS-A and plans for future upgrades

bull Interoperability programs of NATO and the USA

The collected literature has been analysed and a summary of capabilities architecture proceduresand evolution of each land system the GCCS systems and interoperability architectures is providedin this report

A list of land system interoperability collaboration functions demonstrated to be very successfulhave been recommended for the GCCS-M upgrade

Also a list of current land system decision support capabilities which provide valuable functionalitythat could be useful for a next generation naval C2 has been compiled based on various observationsmade in the collected literature regarding successes of land systems and the needs of modern navalsystems Because of lack of detail in terms of the level of maturity level of automation as wellas algorithmic capabilities of the specific functionality in these land C2 capabilities only high levelrecommendations regarding the general nature of future naval C2 functions are made

41

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 58: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

71 Challenges Encountered

The topic of analyses in this work is very interesting On one hand having worked on a numberof Canadian naval C2 research and development projects in the past analysing the integrationof GCCS-M with Canadian maritime C2 systems OODA Technologies Inc was familiar withsome limitations of this system On the other hand the analysis of the literature on modernland systems provided an appreciation that the technology solutions can be successful to overcomethese limitations and go further ahead supporting every phase of decision making in naval coalitionoperations However the analysis of the documentation and derivation of conclusions have beenquite challenging for many reasons including

bull The information downloaded from Internet is very fragmented with a significant subset ina form of slide presentations including inconsistencies as well as partial information andmany with no date information

bull The open publications express the specific views of the author and it not always clear howconsistent these are with the military organizations actually planning and putting in placethe program developments

bull None of the open publications downloaded contained sufficient level information providingappreciation of the detail in the interoperability and decision support capabilities successfullyused in the land coalition operations

bull There were some past projects conducted for DRDCs which could have given better levelof detail in some areas however during the time frame of this study it was not possible tomake them available

Nevertheless a high level consistent view of modern land systems has been achieved and on a highlevel and recommendations for functionality for next generation GCCS-M have been developedThis can be used as basis for future studies developing a more detail understanding of land systemfunctions and how they can be leveraged for naval C2

In the meantime OODA Technologies strongly recommends that the Scientific Authority shouldreview the reports of Task 1 through 3 of the TPEM project as they are related to the objectivesof this call-up

72 Future Analyses

Starting from an analysis of successfully operating land systems for the development of the re-quirements for the GCCS-M replacement is a very good idea However the conclusions and recom-mendations of this study are based on very high level information and before such a system canbe fully defined and implemented further analyses are necessary These future analyses could beinitiated as two parallel paths which could possibly start independently

42

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 59: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Part 7 Conclusion

1 Analyse each high level functionality identified in this report for integrations into the nextgeneration naval C2 This analysis would need to be done on one side through interviewsof naval C2 SMEs to build an understanding of how these functions would be used andon the other side through technical and technological analyses of naval C2 on Canadiannaval platforms and MOCs involved in coalition operations to evaluate how they would beintegrated

2 Interview SMEs in land C2 to build a detailed understanding of how the functions identifiedin this report are used their complementarity maturity automation etc and then obtaintechnical level documentation for a final subset functionality that is judged useful after theseinterviews

SME involvement in the future analyses of this topic is extremely important Initially an SMEinvolvement was planned in this study as well however this was not pursued as there was anexpectation that the documentation would suffice

43

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 60: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

This page is intentionally left blank

44

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 61: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Bibliography

[1] Anthony E Isenor and Eric Dorion The Use of GCCS in the Canadian Navy and itsRelationship to C2IEDM Technical report DTIC Document 2005 URLhttpcradpdfdrdc-rddcgccaPDFSunc35p523328pdf

[2] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network Technical report 2014 URL httpwww

randorgcontentdamrandpubsresearch_reportsRR300RR302RAND_RR302pdf

[3] Joan C Smith Coalition Interoperability Assurance amp Validation 2012 URLhttpwwwafceaorgeventstnlfsouth12

TechNetSouthCIAVActivitiesinSupportofOperationsinAMNv26pptx

[4] US CIAV ChairmanTKR AMN Coalition Interoperability Assurance and Validation(CIAV) 2012 URL httpwwwdticmilndia2012TEST13802_Phippspdf

[5] NATO-C3-Agency Invitation for bid Development implementation and support ofAfghanistan Mission Network (AMN) 2012 Core Capabilities 2012 URLhttpwwwdefensagobesGaleriasinfoserviciosconcursos201204

IFB-CO-13345-AMN12pdf

[6] John Gibson Quick Reaction Test (QRT) OutBrief 2013 URLhttpwwwincoseorghradocs2013QRT20Outbrief_NCOSE_1620Feb13pdf

[7] Kurt Herrmann Secure CIS Services Provision in NATO Resume And OperationalPerspectives 2012 URLhttpwwwafceaorgeuropehtmldocumentsGenHerrmannpdf

[8] NATO Interim Customer Catalogue 2014 of C4ISR services 2014 URLhttpswwwncianatointDocumentsAgency20publicationsInterim20Customer

20Catalogue20201420of20C4ISR20servicespdf

[9] Wolfgang Taubert Herausforderungen fur die NATO C3 Agentur in Projekten wieAfghanistan Mission Network (AMN) 2011 URLhttpwwwafceadefileadmindownloadsMittagsforen18032011AFCEA_

Mittagsforum_Taubert_18_Maerz_2011pdf

[10] Bela Reger New milestone in NATO Logistic Information Management System 2009 URLhttpwlxtwhuteducnnewwlxtgcpapers20in20logistics20systemNew

20milestone20in20NATO20Logistic20Informationpdf

45

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 62: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

[11] Kevin Scheid NC3Arsquos Experiences in Multinational Operations in Afghanistan 2010 URLhttpswwwafceadefileadmindownloadsFachtagungKoblenz_2010920Scheid

20-20AFCEA20Symposium20-20Koblenz20-200220Sep201020-20DGM20kjs

2028529pdf

[12] NATO NCI NOtification of Intent IFB NCIA-NCHQ-14-14 2014 URL https

wwwncianatointIndustryDocumentsNOI20IFB-NCIA-NCHQ-14-1420IFTSpdf

[13] Klaus F Veit The Afghanistan Mission Network (AMN) A model for network enabledcapabilities 2011 URL httpwwweuropean-defencecomReview2011

binarywriterservletimgUid=a3740d83-f8c1-b331-76b8-d77407b988f2ampuBasVariant=

11111111-1111-1111-1111-111111111111

[14] Holger W Kalnischkies FMN MLS ndash Lessons learned 2013 URLhttpwwwcybersecurityczdataSecunetpdf

[15] Joerg Josef Butterwegge AfghanFuture Mission Network (AMNFMN)from a UsersPerspective 2012 URLhttpswww-304ibmcomeventswwegrpgrp011nsfvLookupPDFsRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardt$fileRound20Table

20-20NATOs20Future20Mission20Network20-20Leonhardtpdf

[16] Douglas A Cook and Robert R Patto The combined enterprise regional informationexchange system-the way ahead Masterrsquos thesis Naval Postgraduate School 2007 URLhttpwwwdticmilcgi-binGetTRDocAD=ADA473894

[17] Chad C Serena Isaac R Porche Joel B Predd Jan Osburg and Brad Lossing LessonsLearned from the Afghan Mission Network URL httpwwwrandorgcontentdam

randpubsresearch_reportsRR300RR302RAND_RR302synopsispdf

[18] Jurgen Eckert Answering Questions on the Future Mission Network 2012 URLhttpwwwactnatointarticle-2013-1-16

[19] Stuart Whitehead Achieving Joint Force 2020 Through Coalition Information Sharing2014 URL httpwwwafeiorgPE4A05DocumentsWhitehead_4A052020AFEI

20Draft20520Mar201420(Smooth)1630pdf

[20] Friedrich Gernot From Afghanistan Mission Network to Federated Mission Networking2014 URL httpswwweiseverywherecomfile_uploads

2f6043f27e1576122f1b3e0319d5b1d8_FromAMNtoFMN-Friedrichpdf

[21] US ARMY and The Joint Staff Joint Systems Integration 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015dod-peds

0604787j_4_pb_2015pdf

[22] Stuart Grant Integrating Air Land and Sea Operations C2 Teams and their Technologies2011 URL httpwwwdticmilget-tr-docpdfAD=ADA555711

[23] Thales Connecting People Sensors and Systems URL httpswwwthalesgroupcom

sitesdefaultfilesassetdocumentthales_c2_brochurecanadapdf

46

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 63: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

BIBLIOGRAPHY

[24] Gerard J Christman and Mark Postal Coalition Interoperability a Modeled Approach In11TH ICCRTS COALITION COMMAND AND CONTROL IN THE NETWORKED ERA2006 URL httpwwwdodccrporgevents11th_ICCRTShtmlpapers003pdf

[25] US Army Joint Automated Deep Operation Coordination System (JADOCS) 2014 URLhttpwwwglobalsecurityorgmilitarylibrarybudgetfy2015army-peds

0203728a_7_pb_2015pdf

[26] William R Clemons The Case for Consolidating Tactical and Operational SystemsInstitute of Land Warfare Association of the United States Army 2005 URLhttpswwwausaorgSiteCollectionDocumentsILW20Web-ExclusivePubsLand

20Warfare20PapersLWP_52pdf

[27] Trygve Sparr Information Quality mdash A Key to Joint Intelligence Surveillance andReconnaissance 2012 URL httpswwwposccaesarorgsvnpubSemanticDays2012

PresentationsMay1002_Trygve_Sparrpdf

[28] Lars Nesse Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)2006 URL httpwwwnatointdocuupdate2007pdfmajicpdf

[29] US-Navy Program Guide 2014 2014 URLhttpwwwnavymilstrategicNPG14_CHINFO_Web_7Mar14pdf

[30] CRAIG A FRANKLIN Global Command and Control System-Joint (GCCS-J) SecurityPolicy 2010 URLhttpwwwdticmilcjcs_directivescdataunlimit6731_01pdf

[31] DOD Global Command and Control System ndash Joint (GCCS-J) 2013 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2013dot-edod2013gccsjpdf

[32] Refugio Delgado Modernizing Command and Control in support of InformationDominance 2010 URL httpwwwonrnavymil~mediaFiles

Funding-AnnouncementsBAA201010-018-C2RPC-Industry-Day-Overviewashx

[33] Leo Hillary Microsoft Word - Demonstrating NCES Compliance v10doc 2009 URLhttpwwwthoughtwebcomdocsDemonstrating20NCES20Compliance20-20A

20ThoughtWeb20Whitepaper20v10pdf

[34] Deidre Briggs NCES Enabling the DoD Net-Centric Data and Service Strategies 2009URL http1105govinfoeventscomevents2009sds09colbriggspresentationpdf

[35] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Introduction and Management 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol1-v7-releasepdf

[36] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Near Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol2-v7-releasepdf

[37] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Mid Term 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol3-v7-releasepdf

47

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

OODA Technologies Inc

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography
Page 64: Requirements for the GCCS-M Replacement based on Land ...Her Majesty the Queen in Right of Canada, as represented by the Minister of National Defence, 2015.c c Sa Majest e la Reine

Study Report RISOMIA Call-up 6

[38] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Interoperability Profiles and Guidance 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol4-v7-releasepdf

[39] C3B Interoperability Profiles Capability Team NATO Interoperability Standards andProfiles - Design Rules 2013 URL https

nhqc3shqnatointAppsArchitectureNISPpdfNISP-Vol5-v7-releasepdf

[40] Dario Cadamuro TDL Interoperability enhancement via Standard Transformation 2010URL httpswwwidlsoccomDocumentsSymposiumsIDLS2010MainDay2IDLS

20201020-20TDL20Interoperability20Enhancement20via20Standard

20Transformation20v0209_Cadamuropdf

[41] DOD Net Enabled Command Capability (NECC) 2008 URL httpwww

globalsecurityorgmilitarylibrarybudgetfy2008dot-edod2008neccpdf

[42] Steve Bullard US Navy C4I Roadmap 2007 URLhttpwwwidlsoccomdocumentssymposiumsidls2007idls2007_peoc4ipdf

[43] Jesse Scott CENTRIXS-ISAF Phase 1 Overview 2013 URLhttpscommunityapanorgcfs-fileashx__key

telligent-evolution-components-attachments13-975-00-00-00-00-59-497

-Scott-_2D00_-NC3A-CXI_2D00_P1_5F00_and_5F00_Beyondpptx

[44] Richard H Gimblett Command of Coalition Operations in a Multicultural Environment ACanadian Naval Niche The Case Study of Operation Apollo Technical report DTICDocument 2006 URL httpwwwdticmilget-tr-docpdfAD=ADA462300

[45] Donald Harder Moving Navy Command and Control into the Future 2013 URLhttpwwwpublicnavymilspawarPressDocumentsPublications1302013_

AFCEA[150_PM]pdf

48

The use or disclosure of the information on this sheet is subject to the restrictions on the title page of this document

  • Contents
  • List of Figures
  • Scope
  • Introduction
    • Past Projects
      • Command Decision Aids Technology (COMDAT) TDP
      • MUlti-Sensor Integration within the Common Operating Environment (MUSIC)
      • Joint Fire Support (JFS)
      • Tactical Planning and Execution Management (TPEM) project
        • Outlines
          • Modern Land Force Command and Control (C2) Systems
            • Afghan Mission Network
            • Future Mission Network
            • Canadian Land Command and Control (C2)
            • Land Command and Control (C2) Applications in Coalition Operations
              • Land Command and Control Information Services (LC2IS)
              • Joint Automated Deep Operations Coordination System (JADOCS)
              • Joint Defence Planning Analysis and Requirements Toolset (JDARTS)
              • Multi-sensor Aerospace-ground Joint ISR Interoperability Coalition (MAJIIC)
                  • Global Command and Control System
                    • Global Command and Control System - Maritime (GCCS-M)
                    • Global Command and Control System - Joint (GCCS-J)
                    • Global Command and Control System - Army (GCCS-A)
                    • GCCS Future Evolutions
                      • Maritime Tactical Command and Control (MTC2)
                      • Net Centric Enterprise Services (NCES)
                      • Joint Mission Planning System (JMPS)
                          • Interoperability in Coalition Land Operations
                            • NATO Programs for Interoperability
                            • USA Programs for Interoperability
                              • Recommendations for GCCS-M Replacement
                                • SoftwareSystem Functions Recommended for Next Generation GCCS-M
                                • Interoperability Recommendations
                                • Procedure and Policy Recommendations
                                  • Conclusion
                                    • Challenges Encountered
                                    • Future Analyses
                                      • Bibliography