Annex F13 Intro to Basic C2 Applications

Question 0

COP/CTP software and its corresponding warfighting function

Answer 0

GCCS-J: Global Command and Control System-Joint
IOSv1: Intell Operations Server Version 1
C2PC: Command and Control Personal Computer
BFT: Blue Force Tracking
CPOF: Command Post of the Future
Falconview

Question 1

Purpose of a C2 System

Answer 1

Operational success would not be possible w/o effective C2

C2 encompasses all military functions and operations, synchronizing them into a meaningful whole

Question 2

Logistics software and its corresponding warfighting functions

Answer 2

GCSS-MC: Global Combat Service Support System
CLC2S: Common Logistics C2 System
TCPT: Transportation Capacity Planning Tool
BCS3: Battle Command Support Sustainment System

Question 3

Fires Software and its corresponding warfighting function

Answer 3

AFATDS: Advanced Field Artillery Tactical Data System
JADOCS: Joint Automated Deep Operations Coordination System
TLDHS: Target Location Designation and Handoff System
PSS-SOF: Precision Strike Suite-Special Operations Forces
TBMCS: Theater Ballistic Missile Core System

Question 4

Intellegience software and its corresponding warfighting function

Answer 4

Marine Link
IAS: Intelligence Analysis Systems
BAT/HIIDE-Biometric Automated Toolset/Handheld Interagency
ID Detection Equipment
COIC Tools: Counter IED Operations Integration Center Tools

Question 5

Collaboration software

Answer 5

Sharepoint

Transverse

Question 6

Planning considerations for GCCS-J

Answer 6

IP of IOSv1 servers

Question 7

Planning considerations for IOSv1

Answer 7

IP of C2PC Gateway (at your location)

IP of GCCS-J Server (Higher)

Question 8

Planning considerations for C2PC

Answer 8

IP of C2PC Gateway

IP of IOZv1 Server

Question 9

Planning considerations for CPOF

Answer 9

Client IP
Mid Tier Server IP
Master Repository Server IP

Question 10

Planning considerations for FBCB2-BFT

Answer 10

User role names

Is the network in place?

Question 11

Planning considerations for TBMCS

Answer 11

Web based applications

Your AirO may require access to view the ATO

Question 12

Planning considerations for JADOCS

Answer 12

Managed by fires personnel, typically at the Regt and above

IP scheme required

Question 13

Planning considerations for AFATDS

Answer 13

Client IP address

Adj/Higher IP’s as stated in the Annex K/U

Question 14

Planning considerations for TLDHS StrikeLink

Answer 14

Typically managed by Fires community

Ensure your FO/FAC/JTAC has frequencies for the PRC-117F

Question 15

Planning considerations for PSS-SOF

Answer 15

Managed by fires community

Question 16

Planning considerations for COIC Tools

Answer 16

SIPR access

URL

Question 17

Planning considerations for IAS

Answer 17

Used within the Intel community
Ensure they have connectivity with higher
Connectivity based on IP scheme

Question 18

Planning considerations for MarineLink

Answer 18

Client IP address
Intranet access
Connection to database server

Question 19

Planning considerations for BAT/HIDE

Answer 19

Used primarily by operators, not necessarily intel
Standalone system, data needs to be physically transported to HHQ to get info into databases
If you are at HHQ make sure someone has a plan to collect data

Question 20

Planning considerations for GCSS-MC

Answer 20

To be explained by system/application

Question 21

Planning considerations for BCS3

Answer 21

Client Ip address

Intranet access

Question 22

Planning considerations for CLC2S

Answer 22

Client IP address
Intranet access
URL to CLC2s server
If un-tethered-H/W with pre loaded software

Question 23

Planning considerations for TCPT

Answer 23

Client IP address
Intranet access
URL for TCPT server

Question 24

Planning considerations for MS Sharepoint

Answer 24

Understand how your unit intends to use Sharepoint | Who will be the site manager?