Army Battle Command System Pocket Guide
Transcript of Army Battle Command System Pocket Guide
ABCS Pocket Guide
Battle Command And ABCS Pocket Guide
ABCS Pocket Guide
Purpose………………………………………………………………………………...Purp-1
Battle Command and ABCS (Selected Acronyms)..…………………….……………Acro-1
Battle Command and ABCS (Unit Architecture)…………………………………….Arch-1
Battle Command and ABCS (Common Operational Picture)…………………….....COP-1
Battle Command and ABCS (BCSoSIT)…………………………….………...……...BCSoS-1
Battle Command and ABCS (Using BCS / BCCS)………………...…………….…...BCS-1
Battle Command and ABCS (Using BCS3)……………..………………...…..……...BCS3-1
Battle Command and ABCS (Tactical Battle Command)………………...…..……...TBC-1
Battle Command and ABCS (Using MCS)……...………...………….………............MCS-1
Battle Command and ABCS (Using FBCB2)…………………………………….…..FBCB2-1
Battle Command and ABCS (Using CPOF)…………….….……….…………….….CPOF-1
Battle Command and ABCS (Using TIGR)…………………….…………………….TIGR-1
Battle Command and ABCS (Using DCGS-A)……………………………...…...…...DCGS-1
Battle Command and ABCS (Using CIDNE)………………………………….….….CIDNE-1
Battle Command and ABCS (Using AFATDS)...…………………….……....…...….AFATDS-1
Battle Command and ABCS (Using TAIS)…………………………………………...TAIS-1
Battle Command and ABCS (Using AMDWS)……………………………………….AMDWS-1
Battle Command and ABCS (Using GCCS-A)…………………………….….....…...GCCS-1
Battle Command and ABCS (Using WIN-T)………………………………….……...WIN -1
Battle Command and ABCS (Using JNN)………………………………..……...…...JNN-1
References ………………….………………………………………...……...….…….Ref-1
Points of Contact…………………………….………………………….….…...……..POC-1
TABLE OF CONTENTS
TOC-1
ABCS Pocket Guide
PURPOSE
This pocket guide has been prepared to provide a quick reference for Soldiers who utilize the
various systems and supporting communications equipment in the Army Battle Command Sys-
tem (ABCS) which enable a digital battlefield to frame an architecture of every stationary and
moving platform in the operational environment / area of operations (AO).
This guide was prepared by the Army National Guard (ARNG) Battle Command Training Center
(BCTC) at Fort Leavenworth, Kansas, and is derived from the January 2011 edition of The Azi-
muth, entitled, Battle Command and ABCS, Volume 3. While annual copies of The Azimuth are
devoted to ABCS updates, their size sometimes complicates “carry-around” convenience for the
Soldier. This guide’s cargo pocket design alleviates that problem, and although systems are up-
dated and software versions change, it will still provide valuable information on the basic capa-
bilities that are available to the Soldier.
Purp-1
ABCS Pocket Guide
SELECTED ACRONYMS
The accompanying list of common acronyms has been added as a consolidated, quick reference list to assist in the reading
of this pocket guide. It is not intended to be all inclusive of the myriad terms that exists. While most of these terms are
explained in the following pages, repetitive identification of some of these acronyms is purposeful to assist in reader un-
derstanding.
A2C2 ACO
AFATDS
AFCS
AIS
AMDWS ArcGIS
ASORTS
ASAS
ATCCS ATI
ATO
ATTAC
BAS BCS
BCS3
BLF
BLOS
BnCPN C2PC
C2R
CAT
Army Airspace Command and Control Air Control Order
Advanced Field Artillery Tactical Data System
Advanced Fire Control System
Advanced Information System
Air and Missile Defense Workstation Arc Geographic Information System
Army Status of Operational Readiness and
Training System
All Source Analysis System
Army Tactical Command and Control System Automated Tactical Intelligence
Air Tasking Order
Asymmetric Threat and Tactical Analysis Note-
book
Battlefield Automated System Battle Command Server
Battle Command Sustainment Support System
Blue Live Feed
Beyond Line-of-Sight
Battalion Command Post Node Command and Control Personal Computer
Command and Control Registry
Civil Affairs Team
CGRS CIDNE
CGS
C/JMTK
CLOS
COP CPN
CPOF
CTIL
CTP
D3A
DCGS-A
DSN
DTSS
ENSIT EMT
EPLRS
FBCB2
FOS
GCCS-A GIG
GUI
HDWS
IDM
Common Grid Reference System Combined Information Data Network Exchange
Common Ground Station
Commercial Joint Mapping Tool Kit
Circular Line-of-Sight
Common Operational Picture Command Post Network
Command Post of the Future
Commander’s Tracked Item List
Common Tactical Picture (Software)
Decide, Detect, Deliver, Assess (Targeting Method)
Distributive Common Ground System –Army
Defense Switched Network
Digital Topographic Support System
Enemy Situation Effects Management Tool
Enhanced Position Location Reporting System
Force XXI Battle Command Brigade-and-Below
Flight Operations System
Global Command and Control System Army Global Information Grid
Graphical User Interface
Human Domain Workstation
Internet Download Manager
Acro-1
ABCS Pocket Guide
IP IWEDA
IMETS
I3
JCDB
JEM JIOC-I
JOPES
JMTK
JNN
JNTC JWARN
LAN
LSD
MCOO
MCS MCS-WS
MFWS
MIDB
MILSATCOM
NMIB NRTS
PASS
PSDS2
SALUTE
SICPS
SINCGARS
Internet Protocol Integrated Weather Effects Decision Aid
Integrated Meteorological System
Integrated Imagery and Intelligence
Joint Common Database
Joint Effects Management Joint Intelligence Operations Capability-Iraq
Joint Operations and Planning Execution System
Joint Mapping Tool Kit
Joint Network Node
Joint Network Transport Capability Joint Warning and Reporting Network
Local Area Network
Large Screen Display
Modified Combined Obstacle Overlay
Maneuver Control System Maneuver Control System – Workstation
Multi Function Workstation
Modernized Integrated Database
Military Satellite Communications
New Material Information Brief Near Real Time Server
Publish and Subscribe Services
Persistent Surveillance and Dissemination Sys-
tem of Systems
Report - S ize, Activity, Location, Uniform, Time, and Equipment
Standardized Integrated Command Post Systems
Single Channel Ground to Air Radio System
SIPR
SOA
SQL
TACREP
TAIS
TBC
TCA
TI
TIDAT
TIGR
TIMS
TSAT
UHN
USF
TPFDD
USMTF
VMF
VoIP
WAN
WEM
WIN-T
WIT
XML
Secure Internet Protocol Routing
Services Oriented Architecture
Structured Query Language
Tactical Report
Tactical Airspace Integration System
Tactical Battle Command
Transformational Communications
Architecture
Tactical Internet
Target Intelligence Data
Tactical Ground Reporting
Tactical Internet Management Software
Transformational Satellite System
Unit Hub Node
Unit Set Fielding
Time Phased Force Deployment Data
US Message Text Format
Variable Message Format
Voice over Internet Protocol
Wide Area Network
Weather Effects Matrix
Warfighter Information Network-Tactical
Weapons Intelligence Team
Extensible Markup Language
SELECTED ACRONYMS (CONT)
Acro-2
ABCS Pocket Guide BATTLE COMMAND AND ABCS - UNIT ARCHITECTURE
The capability of ABCS systems to assist com-
manders with battlefield lethality, tempo, and
the ability to dominate from a planning and con-
trol standpoint is enormous. Battle command
systems provide a substantial increase in the
level of situational information units may
achieve, significantly speed the process of creat-
ing and disseminating orders, allow for exten-
sive data basing of information, and increase the
speed and fidelity of coordination and synchro-
nization of battlefield activities. That said, real-
izing the potential of these systems requires
extensive training, a high level of technical pro-
ficiency by both operators and supervisors, and
the disciplined use of detailed standing operat-
ing procedures (SOP). Commanders are at the
hub of their unit realizing the combat multiplier
advantages of digital systems. Operator and
leader sustainment training should be viewed as
a command responsibility.
GCCS-A - Global Command and Control System-Army
C2PC - Command and Control Personal Computer
FBCB2 - Force XX1 Battle Command Brigade-and-Below
BFT – Blue Force Tracking
TBC – Tactical Battle CommandDTSS - Digital Topographic Support System
DCGS-A – Distributed Common Ground System-Army
IMETS - Integrated Meteorological System
PASS – Publish and Subscribe Services
NRTS – Near Real Time Server
C2PC GW – C2PC Gateway
AFATDS– Advanced Field Artillery Tactical Data SystemAMDWS – Air and Missile Defense Workstation
BCS3 - Battle Command Sustainment Support System
BCS – Battle Command Server
Arch-1
ABCS Pocket Guide
COMMON OPERATIONAL PICTURE (COP)
What is it?
Any discussion of ABCS must address the Common Operational Picture (COP). As a single, identical display of relevant
information shared by more than one command, it is based on information fed up from Force XX1 Battle Command Bri-
gade-and-Below (FBCB2) / Blue Force Tracker (BFT), from the ABCS systems in the command post, and information sent
down from higher echelon ABCS systems. All of this information is fed into the tactical operations center (TOC) server
and displayed using the Maneuver Control System (MCS) and / or Command Post of the Future (CPOF).
The COP consists of combat power charts, events, battle rhythm reports, battle update assessments / analysis, threat updates,
and leverages the digital technology provided by the MCS. In the TOC, the MCS provides the near-real-time ability to “see
yourself” and “see the threat,” and is accessible from any ABCS system in the TOC. CPOF is also a major contributor to
the COP, as it provides situational awareness (SA), which allows users to collaborate in near-real-time with real data.
Through a shared visual workspace, commanders and staff can analyze data, share thoughts, and plan courses of action
(COA). CPOF users verbally communicate using the Voice over Internet Protocol (VoIP) and visually communicate using
the on-screen drawing features.
The COP is an operational picture tailored by the
commander’s requirements, is based on common data
and information shared by more than one command,
and facilitates collaborative planning and the
achievement of situational understanding .
COP-1
ABCS Pocket Guide
COP
Range Card(Graphical depiction of range
cards developed for defensive
fighting positions)
Obstacle Overlay(Graphical depiction of
friendly and enemy obstacles)
Position Report(Friendly vehicle / unit locations)
Fire Plan Overlay(Graphical depiction of information
used to control fires at
company level and below)
Air Space Coordination Overlay(Graphical depiction of airspace
control area, routes)
Operations Overlay(Graphical depiction of OPORD Annex C)
Combined Obstacle Overlay(Graphical depiction of terrain
for use in avenue of approach
analysis)
Logistics Overlay(Map overlay depicting location
and mission information
about sustainment operations)
Enemy Overlay(Location, size, activity
of enemy)
NBC Overlay(Graphical depiction of the location of
decontamination and reconnaissance
sites and smoke operation lines)
Traffic Control Overlay(Graphical depiction of routes,
locations, and size of depicted units)
Sector ID Overlay(Graphical depiction of
defensive operations at
company level and below)
Modified Combined Obstacle Overlay
(MCOO)(Graphical depiction of
terrain analysis results)
Fire Support Overlay(Graphical depiction of FS coordinating measures
and location of fires assets)
COMMON OPERATIONAL PICTURE (COP)
COP-2
ABCS Pocket Guide
What are the advantages?
The COP is key to each step within the operations
process . . . plan, prepare, execute, and assess.
Following are some of the advantages:
PLAN
Assists the commander in providing his in-
tent and issuing planning guidance.
Helps the commander, staff, and subordinate
leaders focus on relevant information (RI) for
an operation.
Enhances collaboration, thus allowing more efficient planning, directing, and brief-backs.
Promotes subordinate unit parallel planning.
Allows for picture modification to match anticipated branches and sequels.
Reduces the need for production of extensive control measures to coordinate maneuver and avoid fratricide.
PREPARE
Through brief-backs, subordinate leaders are better able to confirm the commander’s intent and concept of operations.
Tactical plans and running estimates can be revised to meet changes, and units can monitor the tactical situation while
they prepare for combat.
Helps ensure that rules of engagement (ROE) are disseminated uniformly down to the lowest echelons.
COMMON OPERATIONAL PICTURE (COP)
COP-3
ABCS Pocket Guide
What are the advantages? (cont)
EXECUTE
Allows for rapid response to the evolving tactical situation and allows commanders to make
the right decisions, synchronize forces and fires, and seize and retain the initiative.
Supports better risk assessment.
Reduces the chance of fratricide with enhanced situational understanding.
Supports the commander rapidly communicating changes to an ongoing operation.
ASSESS
Promotes better battle tracking and helps leaders measure, analyze, and report unit performance during an operation.
Promotes subordinate unit and staff focus of CCIR if depicted on the COP.
Supports pre-planning to react to anticipated change.
What information can be displayed?
The graphic on the following page depicts the types of information input that commanders and staffs will find highly
relevant in forming the COP. All of the systems addressed in this publication have the capability to exchange (send and
receive) the depicted information except for the Range Card and Sector ID Overlay, that are only supported by MCS and
FBCB2.
COMMON OPERATIONAL PICTURE (COP)
COP-4
ABCS Pocket Guide
Typical COP Flow During Brigade or Battalion Exercise
Battalion or Company Work Cells/White Cells
DCGS-A
ASAS
Brigade or Battalion
AFATDS
BCS
PASS
NRTS
C2PC GW
TBC
Simulation Simulation Simulation Simulation
Red
Units/
Tracks
Blue
Units/Tracks
Simulation
Server
Intelligence Graphics
Artillery Graphics
Ops/Plans Graphics
BCS3
Logistics Graphics
ABCS
Battalion or Company Work Cells/White CellsBattalion or Company Work Cells/White Cells
Brigade or Battalion
The simulation
emulates
FBCB2/BFT during
an exercise
ABCS
COP
BCS
Units/Tracks
Depending on the
exercise focus and
type of simulation,
some or all of the
enemy units/tracks
may be fed f rom the
simulation
COMMON OPERATIONAL PICTURE (COP)
COP-5
ABCS Pocket Guide BATTLE COMMAND SYSTEM OF SYSTEMS INTEGRATION TRAINING (BCSOSIT)
Battle Command Sys-
tem of Systems Inte-
gration Training
(BCSoSIT) is com-
prised of three events
conducted separately
or sequentially de-
signed to train the unit
to use all command
post equipment, ABCS
Systems and enablers,
and the network as a
system of systems in a
command post envi-
ronment. The
BCSoSIT primary
reference is FM 7-15,
The Army Universal
Task List (AUTL).
BCSoSIT-1
ABCS Pocket Guide
Key Tasks:
The Command Post and Staff Integration Team (CP&SIT) supports the integration of Command Post System of Systems
equipment (enablers, Standardized Integrated Command Post Systems (SICPS), the network (tactical communications
systems), ABCS, and their supporting systems) into the unit's command post to ensure the staff is confident employing
the equipment to execute command post operations.
Key Tasks:
Attend Unit Set Fielding (USF) Sync Conferences (Phase I and V) to conduct CP&SIT Brief (schedule New Mate-
rial Information Brief (NMIB) with Product Management (PdM) CPS&IT site lead, and Battle Command System of
Systems Integration Training (BCSoSIT)
Attend PdM CP&SIT NMIB (provide CP&SIT Information Brief, Schedule In Progress Review (IPRs), and review
BCSoSI requirements)
Configure SICPS network equipment (Command Post Platform) as required
Execute and support BCSoS Integration Training
Support unit’s collective training event (mission rehearsal exercise or similar).
Mission
Events:
Event 1 - BCSoS Command Post Integration Training (4 days)
Mission: Conduct Battle Command System of Systems Integration Training in the unit’s command post using the
unit’s equipment in order to validate command post infrastructure and network.
BATTLE COMMAND SYSTEM OF SYSTEMS INTEGRATION TRAINING (BCSOSIT)
BCSoSIT-2
ABCS Pocket Guide
Events: (cont)
Event 1 - BCSoS Command Post Integration Training (4 days) (cont)
Mission: Conduct BCSoSI Training (immediately following Event I) in the unit’s command post using unit informa-
tion systems (INFOSYS) equipment to execute command post operations.
Key Tasks:
TLO 2: Manage tactical information
ELOs:
Overview
Process higher command’s operations order
Develop staff products
Create a COP
Event 2 - BCSoS Staff Integration Training (4 days)
Mission: Conduct BCSoSI Training in the unit’s command post using the unit’s equipment in order to validate com-
mand post infrastructure and network.
Key Tasks:
Terminal Learning Objective (TLO) 1: Establish the command post
Enabling Learning Objectives (ELO):
Establish the SICPS
Establish the power grid
Establish section cells
Establish the network
Conduct command post network validation (voice and data)
End State: Successful integration of all command post equipment. Staff is confident in their ability to setup and inte-
grate their equipment and restore capability upon major failures.
BATTLE COMMAND SYSTEM OF SYSTEMS INTEGRATION TRAINING (BCSOSIT)
BCSoSIT-3
ABCS Pocket Guide
Events: (cont)
Event 2 - BCSoS Staff Integration Training (4 days) (cont)
Conduct a collaborative briefing using INFOSYS
Publish unit order
Process CCIR requirements
Execute practical exercise
End State: The staff has increased confidence in abilities to execute command post operations by collecting, proc-
essing, displaying, disseminating, and storing relevant information using the INFOSYS.
Mission: Conduct BCSoSI Training in the unit’s command post using the units CP equipment to conduct command
post operations.
- Tailored to a specific unit training event, i.e., existing CPX
- Provide over-the-shoulder support to unit battle staff in command post
- Unit training objectives focused on integration of command post equipment (INFOSYS (BC Systems), net
work)
End State: The battle staff has confidence in their ability to establish the command post, manage tactical informa-
tion, and conduct command post operations.
Event 3 - Command Post Integration Exercise (4 days)
POC: Commercial 256-774-6703, or e-mail to [email protected]
http://peoc3t.monmouth.army.mil/win_t/cpsi.html
BATTLE COMMAND SYSTEM OF SYSTEMS INTEGRATION TRAINING (BCSOSIT)
BCSoSIT-4
ABCS Pocket Guide BATTLE COMMAND SERVER (BCS) / BATTLE COMMAND COMMON SERVICES (BCCS) Battle Command Server (BCS) provides infrastructure services used by ABCS and other tactical operations center (TOC)
systems including alerts, messaging, communications, address book, and command and control registry (C2R). BCS is the
key piece of the ABCS architecture that provides interoperability between the various ABCS workstations. Interoperability
is achieved through the system as it hosts a number of common services through which data can pass and become readable
and/or accessible to all ABCS systems on the network. These services include: SQL Database, C2PC Gateway (C2PC
GW), Near-Real-Time Server (NRTS), Publish and Subscribe Services (PASS), Time Server, and C2R Server.
Used for sharing data between MCS Systems. The data shared includes: overlays,
task organizations, filters, SA Groups, bookmarks and live feed groups.
Used to connect and transfer data between MCS / BCS Servers and MCS Gate-
ways as well as the joint picture from Global Command and Control System Army
(GCCS-A).
Moves data between the C2PC GW and the Near-Real-Time Server (NRTS) .
Receives data from battlefield automated system processes and disseminates the
information to the Live Feed. This process distributes all friendly and enemy unit
and platform icons to provide the COP.
An information routing system that delivers data from publishers to subscribers.
Publishers publish data to a topic and subscribers subscribe to information topics.
The PASS is the bridge through which overlays and events pass from one type of
ABCS system to another. This exchange can also take place with multiple systems
of the same type.
Synchronizes time throughout the servers. The Time Server is essential to BCS
functions like NRTS, C2PC GW, PASS and C2R.
Used to perform the C2R configuration and the C2R Planner application. This
process is used to create and edit the C2R organizational data and create certain
files that are required for proper operation of the MCS messaging software.
MCS SQL DATABASE
C2PC GATEWAY
NRTS
PASS
TIME SERVER
C2R SERVER
TMS Broker
BCCS-1
ABCS Pocket Guide
TIPS:
The Server Configuration Console is
designed like a checklist. When you are
configuring your server for the first
time, start at the top of the tree and
work your way down, step by step. In
many cases, the default options will
work fine for you. Remember to click
“Configure” after you have made
changes!
The MCS Server uses several ports to exchange data between itself and other computers. Make sure that
none of the ports you are using are blocked. Network administrators often block ports at the operating
system (OS) or at the router if they think they are not in use for security purposes.
The PASS Data Provider will be the primary means of receiving updated data from other ABCS systems.
BCS Screens
Server Configuration Console
The Server Configuration Console
allows users to configure the vari-
ous server processes. All of the
processes can be run on one
server or some / all of the proc-
esses can be split between several
servers to lessen the load if system
resources are being taxed.
BATTLE COMMAND SERVER (BCS) / BATTLE COMMAND COMMON SERVICES (BCCS)
BCCS-2
ABCS Pocket Guide
AutoSetup Utility
The AutoSetup Utility is used to
set up the desired client connec-
tions to the server processes. If
configured on the BCS, the
MCS clients can simply Auto
Setup to the Server and pull in
most of the settings necessary
for operation rather than hav-
ing to manually enter the data
in each plug-in.
BCS Screens (cont)
BATTLE COMMAND SERVER (BCS) / BATTLE COMMAND COMMON SERVICES (BCCS)
BCCS-3
ABCS Pocket Guide
BCS Screens (cont)
NRTS Console
The NRTS Server Console allows
administrators to configure, start,
and stop data providers to control
the Live Feed, which is then dis-
seminated to the ABCS end-users. The Console alerts administrators
to issues that may require their at-
tention. In this example, the GCCS
Provider has a connection issue and
the AFATDS Provider requires at-
tention and has been stopped.
BATTLE COMMAND SERVER (BCS) / BATTLE COMMAND COMMON SERVICES (BCCS)
BCCS-4
ABCS Pocket Guide
BCS Screens (cont)
EZ PASS Explorer
The EZ PASS Explorer gives ad-
ministrators a way to manage and
view the topics that are published to
the PASS.
BATTLE COMMAND SERVER (BCS) / BATTLE COMMAND COMMON SERVICES (BCCS)
BCCS-5
ABCS Pocket Guide
Battle Command Common Services (BCCS) is an integral System of Systems (SoS) component of ABCS supporting
the infrastructure requirements for all ABCS systems, therefore enabling both tactical unit digital modularity and
joint interoperability. The BCCS currently includes the BCS, which hosts the processes discussed on the previous
three pages critical to ABCS, as well as the Battle Command Enterprise Services which provide:
- Windows Service Configuration and User Management (AD / DNS / Win 2003)
- Email (MS Exchange 2003)
- Common Database (MS SQL Server)
- SharePoint Portal
- Security and virus protection
- Service / HW specification, configuration, backup, failover, and restoration.
BCCS is installed on a series of blade-type servers that are mounted together in a server rack. The system is typically
housed in the G-6 / S-6 Section as a Long Stack or a Short Stack, depending on echelon level and unit mission.
Common Misconception
Quite often, units are under the impression that they must have a BCCS to produce a COP. This is not the case, however,
as the BCS hosts the services necessary for ABCS interoperability. ABCS alone will facilitate the exchange necessary for
COP production. Nevertheless, the implementation of a BCCS does greatly improve digital TOC operations with the En-
terprise Services that it provides. This is important not only to ABCS users, but to all workstations in the architecture.
Some examples include: the Exchange Server, which provides e-mail capability; the Domain Controller, which allows for
creation and management of a domain; and the SharePoint Portal, which gives users the ability to share products through
a web-based interface.
What is BCCS?
BATTLE COMMAND SERVER (BCS) / BATTLE COMMAND COMMON SERVICES (BCCS)
BCCS-6
ABCS Pocket Guide
Long Stack and Short Stack
Configuration
BATTLE COMMAND SERVER (BCS) / BATTLE COMMAND COMMON SERVICES (BCCS)
BCCS-7
ABCS Pocket Guide
BATTLE COMMAND SUSTAINMENT SUPPORT SYSTEM (BCS3)
What is it?
What Does it Do?
The Battle Command Sustainment Support System (BCS3) is the Army’s maneuver
sustainment command and control system. BCS3 makes extensive use of client / server
relationships to bring logistical information to the Warfighter. BCS3 also shares logis-
tics situational awareness data with other ABCS systems in the form of web-based re-
ports, charts, and maps.
BCS3 fuses sustainment, in-transit visibility, and force-level information data to aid com-
manders in making critical decisions at all echelons for maneuver sustainment support.
Logistics Reporting Tailorable to any computer
Provides standard reports
Map Centric Display Provides the logistics common operational picture (LCOP)
Operates in multiple environments
Asset Visibility Integrates enterprise data (STAMIS)
Visibility of stock levels for Army, USMC, and Joint assets Supports map-centric display
In-Transit Visibility Visibility of unit supplies and equipment moving
Convoy tracking / visibility of sustainment shipments BCS3-1
ABCS Pocket Guide
What’s New?
(BCS3 Version BCS3-S-08-10.02.04
with / 3rd Quarter 2010 IAVA Patch)
Unit Task Organization (UTO) Unit Task Organization provides for adding, attaching, detaching, creating, and placing units or supply points
under operational control (OPCON) of other units. Users can graphically portray “support to supported” relation-
ships.
Tracked Items List (TIL) A Tracked Items List (TIL) usually consists of multiple supply items from one or more classes of supply and can
represent anything the commander wants to track. These items are derived from FEDLOG, which contains over
seven million items to select from. Users have the ability to manipulate and share their TIL and other published
TILs.
Logistics Reporting Tool (LRT) The Logistics Reporting Tool (LRT) focuses on tactical-level readiness and supports the commander’s ability to
fight battles, engagements, and achieve stability or support missions by providing an automated, bottom-up report-
ing procedure and relationship integrity between the unit and the supply point.
Combat Power (CP) Combat Power (CP) Reports bring together major weapon systems, ammunition, fuel, and personnel for the
selected reporting unit and its direct subordinates in one display.
BATTLE COMMAND SUSTAINMENT SUPPORT SYSTEM (BCS3)
BCS3-2
ABCS Pocket Guide
Unit Task Organization (UTO)
The user has the ability to manipulate their UTO by
easily left-clicking and dragging from an organic DoD
UTO that has all Army and Marine Corps units. This
allows commanders the ability to modify planned or
current task organizations to best achieve logistical
mission support requirements. The UTOs can be pub-
lished to distributed and shared systems with all BCS3
workstations using the subscription process associated
with PASS software applications and the BCS, or
shared through the Tapestry Information Manager
Client (TIM).
Tracked Item List (TIL)
Using a Tracked Item List (TIL) is another way to filter
information to be displayed on reports and to provide a
predetermined list for logistics data input. The BCS3
uses the FEDLOG as the baseline database to select all
classes of items to be included in the TIL.
BATTLE COMMAND SUSTAINMENT SUPPORT SYSTEM (BCS3)
BCS3-3
ABCS Pocket Guide
Logistics Reporting Tool (LRT)
The Logistics Reporting Tool (LRT) shows logistical status re-
porting process from a unit to its higher headquarters and Sup-
ply Point status reports, which provides a current logistical snap-
shot in order to identify requirements, provides visibility on criti-
cal shortages, project mission capability, and provide input to
the logistical common operational picture (LCOP). Configurable
to any computer with manual inputs, it provides standard re-
ports to the Combat Power Slant Report and Running Estimate
Reports.
The LRT can easily change
Tracked Item List (TIL)
and Unit Task Organiza-
tions (UTO) from Fargo's
to make a customized unit
view for input /output and
multi-unit rollups and re-
ports. It also can change
planning consumption
factors, status thresholds
(Color Coded % levels),
and Planning Days of Sup-
ply (PDOS) that make
automatic calculations for
reports.
Export reports to ExcelExport reports to Excel
Logistics ReportingLogistics Reporting
By UnitBy Unit
BATTLE COMMAND SUSTAINMENT SUPPORT SYSTEM (BCS3)
BCS3-4
ABCS Pocket Guide
Combat Power (CP) / Running Estimate (RE)
Class VIIClass VII
Class VClass V
MAINT.MAINT.
Class IIIBClass IIIB
Combat PowerCombat Power
PersonnelPersonnel
BCS3 provides over ninety different Running Estimate (RE)
reports covering every unit and supply point class from I – X.
Class IV Const and Barrier
Materials
Class IV Const and Barrier
Materials
Class VII Equipment
Maintenance
Class VII Equipment
MaintenanceCombat Power and Running Estimate brings the UTOs,
TILs, and LRT inputs together to display a single report
status of commander-selected major weapon systems
(Class VII), ammunition (Class V), fuel (Class III) and
personnel (MOS) of a selected unit and its direct subordi-
nates.
BATTLE COMMAND SUSTAINMENT SUPPORT SYSTEM (BCS3)
BCS3-5
ABCS Pocket Guide
BCS3-6
This page intentionally left blank.
ABCS Pocket Guide TACTICAL BATTLE COMMAND (TBC)
Tactical Battle Command (TBC) is a suite of products and services that includes the Maneuver Control System (MCS) and
the Command Post of the Future (CPOF).
The suite of products is being fielded and used by Active, Reserve, and National Guard
units from company to Army Service Component Command (ASCC). Operators in-
clude commanders, primary staff, and battle staff personnel from across the warfighting
functions.
Within the TBC product line, CPOF and MCS are only part of the suite of interop-
erable systems provided to the Warfighting Team. CPOF and MCS Client Work-
station Applications are co-hosted on one laptop computer with a keyboard, mouse,
and a headset with microphone. Three monitors are used with an adapter allowing the
mouse to move across all three monitors as one large workspace to provide a flexible
workspace that can be customized to meet individual user needs. The workspace com-
bines real-time voice communication with three-dimensional (3-D) and two-dimensional
(2-D) terrain data and work products. The monitors can be tailored to the needs of the
user, 3-D terrain data is typically displayed on the left screen, 2-D terrain data is dis-
played on the center screen, and CPOF tools and Shared Products are available on the
right screen. The laptop monitor or one of the three stand-alone monitors may be used for
MCS. The current version is BC09.0.4.
Versions following BC09 are scheduled to have MCS
removed.
TBC-1
ABCS Pocket Guide MANEUVER CONTROL SYSTEM (MCS)
The Maneuver Control System (MCS) is an integrated system of hardware, software, per-
sonnel, and procedures used at corps, division, brigade, battalion, and selected companies.
MCS serves as a C2 system designed to assist commanders and staffs in planning, direct-
ing, monitoring, and controlling combat operations. The system incorporates battle staff
tools and maneuver functional capabilities, including Chemical, Biological, Radiological,
Nuclear (CBRN) capabilities and engineering tools for combat and construction engineers.
MCS software is Microsoft OS based and is capable of being installed and operated in ar-
mored and wheeled vehicles, tents, and in those aircraft used as C2 nodes. It is typically
fielded today as a dual-loaded system with CPOF.
What does it do?
Displays the COP and provides tools to graphically support the unit MDMP: graphically displays critical informa-
tion. Critical information includes, but is not limited to: near-real-time battlefield information, maneuver graphics,
mission information, task organization, courses of action, significant events, field artillery coordination graphics, unit
positions, known and suspected enemy locations, obstacle overlays, and shape files. Information is graphically dis-
played after being received from other ABCS machines directly, through Publish and Subscribe Services (PASS),
and through the BCS database.
MCS PASS: provides a vehicle for critical information to be distributed throughout the battlefield across echelons
and functional areas. All ABCS computers have the ability to subscribe to the PASS to both push information to and
pull information from other computers.
Supports Controlled Imagery Base (CIB) maps and Google Earth®- type maps that convert to usable maps, layers,
and other spatial data supported by Arc Geographic Information Systems (ArcGIS).
Supports attaching files to graphics. These attached files are distributed as the graphics are distributed and can be
opened by any user who needs the information contained, regardless of echelon or function.
Effective 1 January 2011, the Army will no longer support MCS. ABCS-ST how-
ever, will continue to train and support units that still have MCS.
MCS-1
ABCS Pocket Guide
Supports CBRN data dissemination and analysis through Joint Warning and Reporting Network (JWARN) and Joint
Effects Management (JEM).
MCS versions currently in use run the gamut from version 6.4.5.1P9 through version MCS BC09.0.3. The latest ver-
sions support JWARN and JEM more fully.
MANEUVER CONTROL SYSTEM (MCS)
What does it do? (cont)
What’s new in MCS version BC09.0.3?
Simplified setup through an expanded AutoSetup Utility, which allows SA’s to configure most settings from the
Server and have them distributed to clients automatically.
The Auto Setup Utility provides a central point for the server to keep BCS and all MCS clients synchronized.
Data Explorer allows simplified management and transfer of data between the various data sources available to the
workstation operator.
Redesigned Task Organization Creator Application – TO / EOB Planning Tool.
Upgraded ArcGIS to 9.2 to allow MCS to display and work with geospatial data from the Digital Topographical Sur-
vey System (DTSS), DCGS-A, and ASAS-L.
NRTS in BCS is updated for better data correlation and performance.
PASS Server is upgraded for better data management, storage, and fast forwarding.
JWARN (Joint Warning and Reporting Network) version is upgraded to version 1F. This version works with Signals
Fires. It is also designed to work with JEM (Joint Effects Management).
Maps and Overlays performance is enhanced for performance. Routes and obstacles have been restructured for better
performance.
Messaging capabilities have been upgraded.
MCS-2
ABCS Pocket Guide MANEUVER CONTROL SYSTEM (MCS)
Consider these questions
by the commander . . .
How MCS helps answer them . . .
Position reports from FBCB2/BFT are received through the PASS or directly,
then filtered from the Live Feed. Position reports from non-FBCB2 units are
received from other MCS clients sent through the PASS.
Actual status for units is updated on the task organization from the MCS
server.
Other friendly unit locations are sent through the PASS from FBCB2, MCS, AFATDS, C2PC, and GCCS as a Live feed.
Slant and position reports are received from the PASS and updated on the
task organization from the MCS server.
Uncorrelated FBCB2 spot reports are sent through the PASS to the MCS Red Live Feed. Correlated enemy intelligence data is received as an overlay from
the ASAS through the PASS and pushed through Near Real Time Server
(NRTS) to become Live Feed.
The enemy status is updated from the correlated ASAS data described above.
Where am I?
What is my status?
Where are the other
friendly units?
What is their status?
Where is the enemy?
What is the enemy’s
status?
MCS-3
ABCS Pocket Guide MANEUVER CONTROL SYSTEM (MCS)
MCS Screens
Task Organization Management
The MCS Task Organization
Tool provides commanders a
means to view, analyze, and
modify friendly and enemy unit
organizations and their support
relationships.
MCS-4
ABCS Pocket Guide MANEUVER CONTROL SYSTEM (MCS)
MCS Screens (cont)
Maps and Overlays
The MCS Maps and
Overlays applica-
tion is used to create
and share overlays
and events as well as
display and manage
the COP.
MCS-5
ABCS Pocket Guide MANEUVER CONTROL SYSTEM (MCS)
MCS Screens (cont)
MCS provides users with a messag-
ing application to support USMTF
and JVMF messaging that functions
similar to commercial e-mail opera-
tions (create, edit, transmit, print,
store, and auto-update).
Common Message Processor
MCS-6
ABCS Pocket Guide MANEUVER CONTROL SYSTEM (MCS)
MCS Screens (cont)
MCS Data Explorer
MCS provides users with a data ex-
plorer application. The MCS Data
Explorer allows simplified manage-
ment and transfer of data between the
various data sources available to the
workstation operator.
MCS-7
ABCS Pocket Guide
The FBCB2 hardware is a mix of commercial, ruggedized, and militarized computers installed in
vehicles and command posts at all levels. FBCB2 is the system that provides friendly position loca-
tion information (PLI) that forms the basis for the COP. FBCB2 is currently fielded in multiple
variants. The EV4 is the most common system fielded to the total force, but over time will be re-
placed by the JV5 system, which incorporates hardware changes to increase speed.
FBCB2 uses the joint variable message
format (JVMF) to send and receive mes-
sages horizontally and vertically on the
battlefield, regardless of task organization. VMF facilitates com-
munication and processing capabilities for the Warfighter, which
yield significant advantages in two key areas:
FBCB2 supports command and control at the
lowest tactical echelons (platform level) via the
transmission and receipt of orders, reports, and
data using terrestrial communications (tactical
voice and data radios). FBCB2 supports the
monitoring, planning, preparation, and execution
of operations by depicting friendly and enemy
unit locations. BFT provides friendly force loca-
tions (platform level) via satellite-based commu-
nications. FBCB2 and BFT automatically pro-
vide these locations to MCS
(commonly referred to as “live
feed”) to provide the com-
mander and battle staff with
SU within the battlespace COP.
Situational Awareness (SA)
Situational awareness is immediate knowl-
edge of the conditions of the operation,
constrained geographically and in time.
Simply put, it is Soldiers knowing
what is currently happening around
them.
Command and Control (C2) C2 is direction by a commander over as-
signed forces in accomplishing a mission.
A commander employs C2 functions as he
plans, directs, and controls forces and op-
erations to accomplish a mission. FM 6-0
FM 3-0
FBCB2-1
FORCE XXI BATTLE COMMAND, BRIGADE–AND-BELOW (FBCB2)
ABCS Pocket Guide
What does it do?
FBCB2 significantly improves the effectiveness of the force by pro-
viding up-to-date combat situation information based on echelon and
location, including the following:
- Friendly and known enemy positions
- Air and ground unit positions
- Maps, terrain, and elevation.
FBCB2 also provides rapid generation and dissemination of messages and acknowledgments, including the following:
- Orders and requests
- Fires and alerts
- Reports
- Rapid generation and dissemination of overlays on the situation picture
- Semiautomatic exchange of selected mission-critical data between the FBCB2 and the ABCS component systems.
FBCB2 provides all echelons with
battlefield situational awareness.
Note that massive changes are coming to the FBCB2 architecture. Versions 6.4 / 6.5 include a massive database
that is similar to a phone book. This db requires frequent updates based on mission, rotation, unit task organiza-
tion and other factors. Moving forward to the next variant, called Joint Capabilities Release (JCR), users only re-
ceive a unit specific data set. As units conduct operations across the battlefield, Self Descriptive Situational
Awareness (SDSA) data is transmitted to populate other users’ local data sets. This information includes URN,
2525B map symbology, IP address, classification, and role name.
FBCB2-2
FORCE XXI BATTLE COMMAND, BRIGADE–AND-BELOW (FBCB2)
ABCS Pocket Guide
Call for Fire
FBCB2 6.4 / 6.5 Screen
FBCB2 supports the call-for-fire process
via JVMF message. Integration of the
laser range finder with lightweight, hand
-held Global Positioning System (GPS)
receivers improves the speed and accu-
racy of calls-for-fire and reports on en-
emy locations (via SPOT Report). BFT
currently does not have this capability
because it has no direct interface with
AFATDS.
FBCB2-3
FORCE XXI BATTLE COMMAND, BRIGADE–AND-BELOW (FBCB2)
ABCS Pocket Guide
FBCB2 JCR Screen
FBCB2-JCR also uses the Commercial /
Joint Mapping Tool Kit (C/JMTK) to
display maps and geographical data. C/
JMTK assists users by simplifying the
building of custom maps for loading on
the FBCB2-JCR system. Simplification is
achieved because the majority of the other
Battle Command Systems utilize C/
JMTK.
Users and S-6 types are encouraged to go to https://fbcb2.army.mil and access the training materials, Technical Bulle-
tins, “The Combat Message” from the TCM and other products available to keep current on FBCB2 specific issues.
TTP
JCR provides a similar look and
feel to FBCB2 6.4 / 6.5 with the
addition of several enhancements.
First, users requested that the feel
be more “Windows like,” and sec-
ond, that controls be easier to ma-
nipulate while wearing gloves or
other PPE. JCR accomplishes
this while providing multiple ser-
vice enhancements aimed at fur-
ther reducing latency.
FORCE XXI BATTLE COMMAND, BRIGADE–AND-BELOW (FBCB2)
FBCB2-4
ABCS Pocket Guide
FBCB2-JCR Service Enhancements
One of the major changes under the new Joint Capabilities Release is the inculcation of NSA Type I encryption. This en-
hancement is accomplished through the use of the KGV-72 (hardware) loaded with crypto from a Simple Key Loader (SKL).
This enhancement allows satellite-connected users the ability to transmit SECRET classified information. The benefit to this
is that JCR users will be provided the same level of services and access to the upper tactical internet Battle Command Sys-
tems at the platform level. FBCB2 6.4 users previously only had access to PLI, MEDVAC requests, Free Text messages, and
SPOT Reporting. Users equipped with the KGV-72 will be able to use JCR full functionality.
UNCLASS NETWORK
SECRET NETWORK
FBCB2-5
FORCE XXI BATTLE COMMAND, BRIGADE–AND-BELOW (FBCB2)
ABCS Pocket Guide
FBCB2-JCR Service Enhancements (cont)
New FBCB2-JCR TOC Kit
The Ruggedized Laptop (Dell XFR Latitude) is
a notebook-size computer that has been
ruggedized to resist harsh conditions and
rough handling.
It is equipped with:
• 2.53 GHz Intel Dual Core processor
• 4 GB of RAM, upgradeable to 8 GB
• 256 GB removable, Solid State Drive (SDD)
• Linux Red Hat operating system
FBCB2-6
FORCE XXI BATTLE COMMAND, BRIGADE–AND-BELOW (FBCB2)
ABCS Pocket Guide
Multi-Function Display
PLGR (can be substituted for a DAGR)
Computer Processing Unit
FBCB2-6.4 / 6.5 Applique Components
FBCB2-7
FORCE XXI BATTLE COMMAND, BRIGADE–AND-BELOW (FBCB2)
ABCS Pocket Guide
FBCB2-6.4 / 6.5 Applique Components (cont)
KGV-72 in-line encryption device
Current Hard Drives in Use
Simple Key Loader (SKL)
FBCB2-8
FORCE XXI BATTLE COMMAND, BRIGADE–AND-BELOW (FBCB2)
ABCS Pocket Guide
So . . . who gets what?
As a general rule, units are already fielded FBCB2 to some extent or another. As FBCB2-JCR transitions to Joint
Battle Command-Platform (JBC-P), additional fieldings will occur to reach objective state across the force (~200K
systems).
General rules apply for the type of FBCB2 units receive. All III Corps units and the Stryker Brigades (including
SBCT 6, 56 / 28 ID, PAARNG) are fielded terrestrial versions of FBCB2. This system utilizes the Enhanced Posi-
tion Location Reporting System (EPLRS) radios to communicate from platform to platform. The entire rest of the
Army receives the FBCB2-BFT variant which uses the MT-2011 L-Band satellite transceiver to communicate with
the BFT Global Network (BGN). Decisions are still pending as to which communications networks will be used for
JBC-P, but indications are that the JBC-P will use a hybrid network that communicates over
radio and satellite depending on which is more efficient and reliable based on conditions on
the ground.
So . . . how do I know when I am getting fielded?
ABCS (including FBCB2) Fielding (and re-fielding) occurs as a deliberate initiative through
the Unit Set Fielding (USF) Process. This process is designed to either initially field or per-
form refresh (hardware (H/W) and software (S/W)) to units during the Reset Phase. In actuality, this process typi-
cally occurs for ARNG units just prior to or during the available year of the ARFORGEN cycle. This is because
units must deploy with the most current H/W – S/W or their systems will not function properly while deployed.
The USF Program is controlled by Program Executive Office Command Control Computers and Technology (PEO-
C3T), headquartered at Fort Monmouth, NJ.
FBCB2-9
FORCE XXI BATTLE COMMAND, BRIGADE–AND-BELOW (FBCB2)
ABCS Pocket Guide
Units are encouraged NOT to contact PEO-C3T directly, rather call the National Guard Bureau for information on
USF.
The National Guard Bureau points of contact for USF scheduling / issues are MAJ Todd Carter, 703-601-6939, e-
mail: [email protected]; and Mr. Ronald Marshall, 703-601-7778, e-mail: [email protected].
So . . . how do I know when I am getting fielded? (cont)
What is the fielding based on?
The short answer is that units will not know the density or types of systems they are scheduled to be fielded until
they have attended their USF conference. This is due to multiple factors:
- Unit type / MTOE
- Current BC software version
- Mission set while deployed
- Current fielding guidance from the Army and joint community
- Systems availability
- Other factors.
Note: Some Battle Command Systems may not return to CONUS with their units; they may remain in theater as
stay-behind equipment!
FBCB2-10
FORCE XXI BATTLE COMMAND, BRIGADE–AND-BELOW (FBCB2)
ABCS Pocket Guide COMMAND POST OF THE FUTURE (CPOF)
CPOF is an executive-level, decision support system that provides situational awareness
(SA) and collaborative tools for a unified picture of the operational environment. By
including real-time collaboration, integrated Voice over Internet Protocol (VoIP), and
ABCS feeds, users can gain situational awareness from one system rather than several.
CPOF is a planning and communication tool, which allows users to collaborate in near-
real-time with real data, and improves the shared SA throughout the command. CPOF
provides commanders and staffs situational understanding by sharing ideas, experiences,
and vision. This helps in applying analysis to the COP from multiple perspectives so that
it more accurately reflects ground truth.
What does it do?
CPOF provides a collaborative operating environment, highly-intuitive, graphical user interface (GUI), and enhanced
briefing capabilities that give commanders the ability to control the information Management Design of their organiza-
tion.
CPOF allows commanders at battalion level and higher to feed real-time situational awareness into the system and re-
ceive near-real-time feeds from ABCS systems that track combat elements and follow enemy forces. Commanders and
staffs can analyze the data, share thoughts, plan courses of action, communicate through on-screen tools, VoIP, and
visually communicate using the on-screen maps and other situational understanding features.
CPOF allows for collaborative planning to take place asynchronously by using the VoIP capability and data-sharing
features. All planners need not be interacting at a fixed time. CPOF data is current at all times because users can access
and change (if they have permission) shared plans and data, which simultaneously changes the shared data for every-
one.
Briefs can be limited in number, shorter in duration, and do not require travel. CPOF-1
ABCS Pocket Guide
3-D Workspace
Shared Workspace
2-D Workspace
What it is NOT . . . .
CPOF is not a replacement for ABCS. It has access to
data from several ABCS systems.
CPOF does not operate in a stand-alone mode. It runs
on a battlefield network and requires a connection to a
CPOF server. If the network goes down, CPOF’s dis-
connected operations are extremely limited.
COMMAND POST OF THE FUTURE (CPOF)
CPOF-2
ABCS Pocket Guide
Position reports from BFT / FBCB2 are received through the PASS and
displayed on the 2-D and 3-D map applications.
A commander can disseminate courses of action and relevant information
to CPOF users using shared maps and VoIP.
The status is updated via either the PASS from ASAS-L, via other ABCS
systems, or directly input to CPOF from SPOT or Intelligence reports
from the ground units. This information is updated in near-real-time.
The status of each unit’s individual missions can be updated and dis-
played on a CPOF calendar or map, showing a commander what the last,
current, and next 24-hour operations are, who is responsible for them, and
where they are happening.
How CPOF helps answer them . . .
Where are friendly units on
the battlefield?
Can I collaborate from my
office?
Full-spectrum operations follow a cycle of planning, preparation, execu-
tion, and continuous assessment. CPOF provides commanders with situ-
ational awareness throughout this cycle.
COMMAND POST OF THE FUTURE (CPOF)
What is the enemy situation
on the ground?
What are my units doing?
CPOF-3
Consider these questions
by the commander . . .
ABCS Pocket Guide
CPOF supports preparation by helping the commander . . .
Refine the plan
Facilitate collaborative 2-D and 3-D map rehearsals
To be actively involved in the IPB Process
Predict the tempo of future operations.
CPOF supports planning by helping the commander . . .
Visualize tactical action
Better understand METT-TC
Visualize the elements of operational design
Communicate the commander’s intent
Communicate the commander’s planning guidance
Coordinate with staff and senior and subordinate commanders
Collaboratively evolve his plan with the input of others
Develop the concept of operations
Generate branches and sequels
Abbreviate the MDMP process and reduce planning time.
COMMAND POST OF THE FUTURE (CPOF)
CPOF-4
ABCS Pocket Guide
Continuously monitor and assess the situation and progress of an operation
Facilitate comparison of what is happening with his initial vision of what should
happen – the Running Estimate
Evaluate the operation against measures of effectiveness through graphic, tex-
tual, and audio clues.
COMMAND POST OF THE FUTURE (CPOF)
CPOF-5
CPOF supports execution by helping the commander . . .
CPOF supports assessment by helping the commander . . .
Anticipate enemy reaction
Recognize tactical opportunities
Issue orders to exploit opportunities
Identify when and where to mass combat power
Reduce enemy options
Better understand acceptable risk
Maintain momentum and adapting
Control operational tempo
Maintain synchronized operations.
ABCS Pocket Guide
CPOF Screens This is an example of the 2-D workspace on CPOF. This example is showing a battle
board that has a map with operational graphics, friendly unit locations, enemy significant
activity (SIGACT), and a tasking (cordon and search).
COMMAND POST OF THE FUTURE (CPOF)
CPOF-6
ABCS Pocket Guide
CPOF Screens (cont)
This screen is a detailed
example of a Com-
manders Update Brief
(CUB). This brief can
be shared with all of the
CPOFs in a unit so that
commanders can utilize
CPOF’s greatest
strength: collaboration
in real time.
This presentation in-
cludes several paste-
boards from different
staff sections, as well as
subordinate units. Each
section / unit can brief
their portion by simply
selecting their tab at the
top of the screen. The
stickies (in yellow to the
left) depict past and
present pertinent infor-
mation.
COMMAND POST OF THE FUTURE (CPOF)
CPOF-7
ABCS Pocket Guide
CPOF Screens (cont) Below are examples of the 3-D application and some of the tools that it offers.
The 3-D map can be connected to the 2-D map to show the same area in a
different view or disconnected to show a different map area or scale.
Unit Movement and Planning Time Line Line of Sight Distance and Terrain Contour Tool
Terrain Exaggeration Air Tracks and Operating Zones
COMMAND POST OF THE FUTURE (CPOF)
CPOF-8
ABCS Pocket Guide
What’s coming?
CPOF version BC10.0.1
CPOF version BC10.0.1 will be officially released in 2nd QTR FY11.
BC10.0.1 includes several new features and functionality improvements.
CPOF has also undergone significant visual and usability upgrades to better
serve the Warfighter.
These are just some user / administrative features and changes included:
1. Stickies and image support
2. Schedules
3. Task Organization
4. Charts
5. Personal Assistant that Learns (PAL)
1. There are no longer Stickies and
Rich Stickies – all Stickies allow for
rich formatting. You can also copy
and paste images into Stickies and
Pasteboards.
2. Previous versions of CPOF included the Master, Subset Master, Archive,
and the Scratch Schedule. This schedule functionality has been consolidated
into one application: the Schedule. The new Schedule most closely resem-
bles the functionality of the previous Scratch Schedule.
3. Task Organization was previously part
of the Master Schedule but is now accessi-
ble through the Tree Viewer.
COMMAND POST OF THE FUTURE (CPOF)
CPOF-9
ABCS Pocket Guide
What’s coming? (cont)
CPOF version BC10.0.1 (cont)
4. Charts will aid in analysis and deci-
sion making by helping you visualize
your data in multiple ways. Available
charts: Vertical Summary Bar Chart,
Horizontal Summary Bar Chart, Scatter
Plot, Column Chart, Network Chart, and
Task Organization Chart.
5. Access prepared PAL procedures in
the Library and run them on your own
workspace. The Library is a dynamic
collection of components that you can
drag out and customize for your own
use. PAL procedures are designed to
automate routine work tasks, freeing you
to spend more time on strategic decision-
making.
COMMAND POST OF THE FUTURE (CPOF)
CPOF-10
ABCS Pocket Guide TACTICAL GROUND REPORTING (TIGR)
Tactical Ground Reporting (TIGR) is a multimedia reporting system for Soldiers at the patrol
level, allowing users to collect and share information to improve situational awareness and to
facilitate collaboration and information analysis among junior leaders. TIGR is particularly
suited to counterinsurgency operations and enables collection and dissemination of intelli-
gence on people, places, and insurgent activity. Being focused on users at company level and
below, TIGR complements existing reporting systems that focus on the needs of users at bat-
talion or brigade level and above.
The TIGR system, shown in this
screenshot and the one on the follow-
ing page, provide its users with a
platform to consolidate report infor-
mation and share that information
with intelligence analysts and com-
manders at higher echelons. Its capa-
bility to provide near-real-time infor-
mation provides patrols and convoys
with an up-to-date look at their sur-
roundings before they head out on a
mission.
TIGR-1
ABCS Pocket Guide
What does it do?
TIGR enhances local knowledge – Local knowledge is critical to effective operations. TIGR helps ground Soldiers
collect information on key infrastructure, landmarks, and terrain. Photos of key locations can be captured into TIGR,
geo-referenced, and displayed as map overlays. Such data serve as a navigation aid in a land where there are no street
names or numbers. Overlays of routes, critical infrastructure, tribal areas and ethnic maps, recent attacks, and recent
changes in the terrain are all used to enhance Soldier knowledge. TIGR is also used to capture and share information
on human terrain. Meetings with religious leaders and encounters with local villagers or business owners can be re-
corded and shared in TIGR.
TACTICAL GROUND REPORTING (TIGR)
TIGR-2
ABCS Pocket Guide
What does it do? (cont)
TIGR tracks dynamic changes – The data in TIGR is dynamic and easily updated. While infrastructure is usually
viewed as static, the reality is that battlefield terrain and infrastructure is dynamic - new structures appear, bridges are
destroyed and new obstacles appear along roads. TIGR manages this dynamic tactical landscape using before / after
photos and updated imagery to provide the most up-to-date views of the operational environment.
TIGR assists the unit rotation process – During the regular Relief in Place - Transfer of Authority (RIP – TOA) proc-
ess, TIGR can be used to transfer the key historical and contextual information to the new unit rotating into the area of
operation (AO). Instead of reviewing a stack of PowerPoint or Word files, new units can start the rotation process by
reviewing past and ongoing activities in the areas of interest (AOI).
Dynamic Search Capability and Tracking of Key Locations
Attack sites
Mosques
Churches
Police stations
VIP residences
High Value Targets (HVT)
Caches
Enemy sniper hides
Taxi stands
Gas stations
Water and power plants
Safe houses
This screen
enlarged on the
following page.
TACTICAL GROUND REPORTING (TIGR)
TIGR-3
ABCS Pocket Guide
What does it do? (cont)
TACTICAL GROUND REPORTING (TIGR)
TIGR-4
ABCS Pocket Guide
What does it do? (cont)
Media Rich Event Reporting by Importing Photos, Excel, Word, and PowerPoint Documents or
Attachments
Sheikhs
Politicians
Tribal leaders
Police officers
Iraqi Army
personnel
Local militia
HVTs
Event & SI
GACT photos
TACTICAL GROUND REPORTING (TIGR)
TIGR-5
ABCS Pocket Guide
What does it do? (cont)
Detailed Planning and Tracking
Using existing detailed imagery, TIGR creates products from key location photos of an existing building; commanders and
platoon leaders can plan their routes and operations in their AO using the TIGR interface.
TACTICAL GROUND REPORTING (TIGR)
TIGR-6
ABCS Pocket Guide
Strengths and Weaknesses
Often, initial SPOT Reports received at the brigade level from adjacent units contain gaps in information. To clarify or
obtain additional information, TIGR provides users with the ability to contact the individual who submitted the report
through e-mail or its forum function. TIGR enables all users to submit postings and reports. This is both one of
TIGR’s strengths and one of its limitations – the level of detail and specificity of a report depends on the individual
submitting it. If a company submits an inaccurate grid location to TIGR, those coordinates will be widely passed along
to other units.
TIGR is not a mandatory reporting requirement for units. As a result, many events that may be beneficial to other units
that use TIGR go unreported. This can give commanders at lower echelons a false representation of the battlefield.
(Battalions and brigades are able to get information from the Command Post of the Future, Distributed Common
Ground System-Army, and CIDNE.)
Reliant upon SIPR connection.
TIGR, when emphasized by brigade leaders, will reduce inaccurate reporting from subordinate units and provide a
solid COP within the unit structure. TIGR is a positive step toward closing the time gap of critical reporting between
the sender and receiver. The Army’s adoption of this program takes advantage of the military’s most effective and
valuable information-gathering resource – the Soldier. The modern battlefield relies heavily on programs like TIGR to
assist in gathering and processing information from the asymmetrical battlefield.
TACTICAL GROUND REPORTING (TIGR)
TIGR-7
ABCS Pocket Guide
Disconnected Operations
User specifies the geographic area that he will operate in while disconnected.
Map imagery (at all zoom levels) and TIGR data for the area are pre-loaded on the client in a portable package that is
optimized for available disk space.
Client provides search and reporting functionality while disconnected, then automatically synchronizes both ways
with the server when the network connection is re-established. Example: Platoon leader’s laptop
screen while on
patrol, incorporating the different types of
data that might be
pertinent to his op-eration. Any newly
imputed data will
update once plugged
back into the net-
work.
TACTICAL GROUND REPORTING (TIGR)
TIGR-8
ABCS Pocket Guide
TIGR Information Flow
This graphic shows the information
flow of TIGR and how it ties to-
gether with current Army Battle
Command Systems (ABCS).
TACTICAL GROUND REPORTING (TIGR)
TIGR-9
ABCS Pocket Guide
Network Robustness
Key Characteristics: Decentralized data management via caching serv-
ers
High network disruption tolerance (TIGR tolerates
typical at-the-edge network outages and degrada-
tions through resynchronization when connectivity
returns).
Low bandwidth utilization (transfers media-rich
reports with minimum impact on the overall net-
work performance).
TACTICAL GROUND REPORTING (TIGR)
Tested and validated over JNN
network at JRTC, PEOC3T testing, and in theater.
TIGR-10
ABCS Pocket Guide DISTRIBUTED COMMON GROUND SYSTEM – ARMY (DCGS-A)
Distributed Common Ground System (DCGS) is the overarching Department of Defense integrated
communications and information architecture program for the Joint Task Force and below. Its Mis-
sion Area Initial Capabilities Document (ICD) defines DCGS as a program to migrate select intelli-
gence systems to a new, multi-discipline, common and interoperable, open family of systems (FoS)
architecture. The entire DCGS FoS consists of the Army (DCGS-A), Air Force (DCGS-AF), Navy
(DCGS-N) and Marine Corp (DCGS-MC) components.
DCGS-A is the ISR gateway to joint, interagency, allied, coalition, and national data, information,
intelligence, and collaboration. It will provide access to theater and national intelligence collection, analysis, early warn-
ing, and targeting capabilities in support of maneuver brigades and battalions. DCGS-A will vertically and horizontally
synchronize ISR efforts and operate in a networked environment at multiple security levels. DCGS-A emphasizes the use
of reach and split-based operations to improve accessibility to data and reduce the forward footprint. DCGS-A software
and hardware provide a single integrated ISR ground processing system composed of joint common components that are
interoperable with sensors, other information sources, war-
fighting functions (WFF), and the DoD DCGS FoS. DCGS-
A software and hardware are tailored by echelon and scal-
able to the requirements of each mission, task, and purpose.
The core functions of DCGS-A are: receipt and processing of
space, airborne, ground and maritime ISR sensor data; con-
trol of select Army and joint ISR sensor systems; intelligence
synchronization; ISR planning and integration; fusion of
sensor information; and direction and distribution of sensor
information. As an element of the Future Force Battle Com-
mand architecture, DCGS-A allows the integration of all ISR
assets based on the Commander’s Critical Information Re-
quirements (CCIR) to produce intelligence that contributes to
the COP, situational understanding (SU) and situational
awareness (SA). DCGS-1
ABCS Pocket Guide
The fixed configuration (e.g., Home Station Operations Center (HSOC)) will conduct day-to-day intelligence plan-
ning, collection, processing, and production to enable information superiority during all phases of an operation.
Mobile DCGS-A configurations are flexible enough to operate from HSOC and deploy into contingency area(s) based
on the commander’s requirements. Mobile and embedded configurations support forward-deployed units currently in
the Iraq and Afghanistan theaters and enable forward-deployed organizations to collaborate with, and reach, fixed and
mobile configurations across the network. This substantially expands the commander’s situational awareness without
increasing the forward footprint.
Embedded DCGS-A is the common software baseline used in fixed and mobile DCGS-A. The embedded configura-
tion is also provided for integration into other systems to provide ISR capabilities.
To eliminate the legacy “stove piped” military intelligence ISR architecture and enable the sharing of data via distrib-
uted intelligence repositories.
DCGS-A will not have proprietary system interfaces, rather DCGS-A will leverage common commercial interfaces
and share a similar “look and feel” from workstation to workstation at all echelons. DCGS-A will work and share
information with other Services under the overarching DCGS DoD initiative.
Where is DCGS-A? DCGS-A is employed in fixed, mobile, and embedded configurations.
Why DCGS-A?
DISTRIBUTED COMMON GROUND SYSTEM – ARMY (DCGS-A)
DCGS-2
ABCS Pocket Guide
DCGS-A enables a horizontally- and vertically-integrated, network-centric, information architecture that co-exists
within a hierarchical operational architecture. It offers a powerful tool to further integrate intelligence, operations, and
plans, and may provide a more effective, time-sensitive, and complete common operational-intelligence picture acces-
sible at the tactical level. Once implemented, DCGS-A provides a theater-wide, net-centric, intelligence architecture
that provides a single, fully-integrated, intelligence knowledge base with input from selected data sources.
DCGS-A will integrate “Intelligence into Action” in a number of fashions, most notably, by redistributing the time
spent working through the phases of the intelligence cycle and, in some cases, possibly accelerating the cycle. Col-
lection and processing time will be dramatically reduced through the introduction of the DCGS-A applications, allow-
ing more time to conduct actual analysis of the acquired information.
The cornerstone and primary value-added benefit of the DCGS-A concept is the integrated intelligence data reposi-
tory. This repository will provide the means to overcome the current analytic challenge of routinely having to query,
build, and share multiple databases at various echelons with no assurance that all data pertinent to a given question
has been identified and incorporated for analysis. It will integrate all sensor feeds, databases, and other data sources
accessible to the DCGS-A to create a comprehensive analytic resource.
Why DCGS-A? (cont)
Integrated Capabilities
V.3.0 is the beginning step to the overall integration of all Programs of Record (POR) and the Multi-Functions Work-
station, which is a common software interface that will eventually be capable of performing all DCGS-A common ISR
visualization, collaboration, data mining, and other needed tools to support intelligence analysts in all intelligence do-
mains.
DISTRIBUTED COMMON GROUND SYSTEM – ARMY (DCGS-A)
DCGS-3
ABCS Pocket Guide
Integrated Capabilities (cont)
Multi-Functional Workstation (MFWS) is a software application within DCGS-A v.3 (and beyond) which enables
the interface between v.2 applications and the added ABCS capability which comprises v.3. The MFWS applica-
tions include ASAS, Prophet Control, certain CGS applications, HDWS, access to PSDS2, DTSS, and IMETS.
DCGS-A v.3 begins the integration of the Programs of Record and Battle Command Systems. It will start this proc-
ess by integrating v.2 tools and applications, ASAS-L, counter-intelligence (CI) and intelligence operations,
IMETS, and DTSS.
V.3 will integrate these systems and applications through one common interface for the user, the MFWS.
The MFWS will display data / products from individual POR to include:
- All-Source Analysis System (ASAS)
- Common Ground Station (CGS)
- Human Domain Workstation (HDWS)
- Persistent Surveillance and Dissemination System of Systems (PSDS2)
- Prophet Control
- Digital Terrain (Topographic) Support System (DTSS)
- Integrated Meteorological System (IMETS)
- Ground Control Station (GCS)
DISTRIBUTED COMMON GROUND SYSTEM – ARMY (DCGS-A)
DCGS-4
ABCS Pocket Guide DISTRIBUTED COMMON GROUND SYSTEM – ARMY (DCGS-A)
Operational Benefits
Two-way battle command communication
MCS or FBCB2, access battle command information
Visualization and manipulation of an entity database
Battle Command and “brain” data transferable into the JITDB
Visualize data on the map (Map View – MFWS)
Share entity data with other applications (AXIS to ANB)
Enemy situation, fire support, blue SA, enemy observation reports
Disseminate entity data (Web UI)
Multi-Function Workstation (MFWS) (Common Interface Framework)
Conduct messaging, data-mining, collaboration, alerts, and visualization from one interface
Create, edit, display (visualize), and analyze entities and associations from one interface (Analysis and eXploration
of Information Sources (AXIS)).
DCGS-A Screens
Multi-Function Work Station (MFWS)
The v.3.0 MFWS provides a common framework leveraging the advanced analytical capabilities of Joint Intelligence
Operations Capability-Iraq (JIOC-I) and incorporates them into a DCGS-A enterprise.
DCGS-5
ABCS Pocket Guide DISTRIBUTED COMMON GROUND SYSTEM – ARMY (DCGS-A)
DCGS-A Screens (cont)
Multi-Function Work Station (MFWS)
(cont)
MFWS functionality includes: visualization;
mapping services, military standard graph-
ics, messaging, tools to support data mining,
alerts and alarms, analysis and presentation,
and BCS interoperability.
MFWS gives the intelligence analyst a
streamlined tool set which will be the com-
mon application framework for the Intelli-
gence WFF for ease of training, improved
visualization, data mining, and alerting.
MFWS allows the user to create numerous
layouts with these plug-ins you see here
within the interface to meet the needs of the
analysts.
DCGS-6
ABCS Pocket Guide
Map View
Map View is a premier visuali-
zation and analytical tool within
the MFWS available to assist
the analyst in providing the
commander with overall situ-
ational awareness.
MFWS Map View Capabilities:
Enabling tool for analysis
and production
Provides mapping data via
ArcIMS
Provides / displays mes-
sages from BCS live data
feeds
Displays data from:
- ArcSDE, ArcIMS, Arc-
GIS exported shape files
- 2525B symbology from
the drawing palette.
DISTRIBUTED COMMON GROUND SYSTEM – ARMY (DCGS-A)
DCGS-A Screens (cont)
DCGS-7
ABCS Pocket Guide
Query Tree
The Query Tree is a develop-
mental and operational, net-
work-based, data mining appli-
cation designed to query large
volumes of textual information.
Analysts are able to use simple
terms, as well as Boolean logic,
to generate queries for informa-
tion. Query Tree is used to
search, read, and save mes-
sages.
MFWS Query Tree Capabili-
ties: Data-mining tool
Constructing and running
simple queries
Boolean logic operators
Transfer results to other
MFWS plug-ins
Review results
Name variant generator
capability
Query history.
DISTRIBUTED COMMON GROUND SYSTEM – ARMY (DCGS-A)
DCGS-A Screens (cont)
DCGS-8
ABCS Pocket Guide
Message Center and Message Editors
MFWS Message Capabilities:
Message center
Provides 2-way BCS communication
via limited number of incoming and
outgoing USMTF messages
Manages incoming and outgoing data
Connects to Interop Service (IOP
Server)
Connects to address book service
(C2R)
Connects to JMS queue
Message editors
Provides limited reporting capabilities
previously conducted by ASAS-L
Message editors provide the means for
outgoing USMTF reporting, to include:
- Enemy Situation Reports
- Target Intelligence Data (TIDAT)
Reports
- General Administrative (GEN-
ADMIN Reports)
- FREETEXT reports / messages.
DISTRIBUTED COMMON GROUND SYSTEM – ARMY (DCGS-A)
DCGS-A Screens (cont)
DCGS-9
ABCS Pocket Guide
Alert Manager
MFWS Alert Manager Capabilities:
Create an alert by AOI
Generate alert by contextual
data
Create alert by pre-determined
data types
Enable / disable alerts
Visual, audible alerts
Alerts are generated from in-
coming traffic through the Mes-
sage Center / live feeds from
Map View.
DISTRIBUTED COMMON GROUND SYSTEM – ARMY (DCGS-A)
DCGS-A Screens (cont)
DCGS-10
ABCS Pocket Guide
ArcGIS
ArcGIS is a situational
awareness tool for geo-
spatially displaying
populated layers. The
dynamic mapping tool
incorporates real-time
and static layers on a 2-
D map.
The software allows
query of data layers,
creation of subsets
from layers, and hot-
link to documents or
web pages.
DISTRIBUTED COMMON GROUND SYSTEM – ARMY (DCGS-A)
DCGS-A Screens (cont)
DCGS-11
ABCS Pocket Guide
COMBINED INFORMATION DATA NETWORK EXCHANGE (CIDNE)
The Combined Information Data Network Exchange (CIDNE) is the US Central Command (USCENTCOM)-directed
reporting tool within Iraq and Afghanistan. CIDNE serves the primary bridge between communities who might not other-
wise share data by providing a standardized reporting framework across multifunctional disciplines supporting operations
and intelligence. This common
framework allows structured
information to be shared verti-
cally and horizontally as part
of flexible, user-defined work
flow processes that collect,
correlate, aggregate, and ex-
pose information as part of the
end-user’s individual informa-
tion life-cycle requirements.
Note: CIDNE is not a component of ABCS. It is an enabler.
Information entered into
CIDNE by one community
can be tied to other infor-
mation within the system,
providing a correlated
view of information across
multiple communities.
CIDNE-1
ABCS Pocket Guide
What does it do?
Over the years, CIDNE functionality grew throughout the course of numerous troop rotations. As critical applications
were left without support due to troop rotations or inability of the software to scale to support increased user demand, the
program source code and all data were usually handed over to MNC-I for full incorporation of all functionality within the
CIDNE software baseline. As these applications were incorporated into CIDNE, entire communities shifted their proc-
esses, procedures, and their legacy data into CIDNE. Since the program’s inception, coalition forces have amassed con-
siderable amounts of information within the CIDNE database.
CIDNE contains structured, relational information on:
Operations Reporting: All known SIGACT reports since 2003; Air MEDEVAC Reports, Police Training Team
Reports, and Surface-to-Air Fire (SAFIRE) Pilot Debriefs.
Counter IED and Exploitation: EOD and Weapons Intelligence Team (WIT) reports for IED, Cache, and IDF
events, including Forensic Materials tracking and exploitation.
Intelligence: Hundreds of thousands of Human Intelligence (HUMINT) reports associated to targets, events, and
other entities in the area of operations.
Targets: High Value Individuals, terrorist networks, biographies, organization profiles, and target lists.
Effects: PSYOP product development tracking, Blue and Red PSYOP activity, Information Operations (IO), and
Operations Security (OPSEC) reporting.
CIDNE-2
COMBINED INFORMATION DATA NETWORK EXCHANGE (CIDNE)
ABCS Pocket Guide
What does it do? (cont)
Civil Affairs: Civil Affairs Team (CAT) Situation Reports (SITREP), facility and infrastructure assessments on hos-
pitals, schools, essential services, election sites, etc. used for identifying civil capacity / reconstruction priorities, at-
mospheric reporting (e.g., mosque monitoring, price reports, etc.), and project tracking.
Engagement: Information on engagements with host nation individuals, including key leaders, meeting deconflic-
tion, and capturing agreements and follow-up.
Socio-Cultural: Capabilities to capture relevant tribal management information (ethnicity, linguistics, demograph-
ics) and related event categorization.
In addition to being the designated Significant Activity (SIGACT) reporting tool of record in the USCENTCOM area of
responsibility (AOR), CIDNE is also the designated Human Intelligence (HUMINT), Explosives Ordinance Disposal
(EOD), and WIT (Weapons Intelligence Team) reporting tool. Though not officially designated by USCENTCOM as the
reporting tool of record for target development, Civil Affairs (CA), Psychological Operations (PSYOP), engagement, or
indirect fire, CIDNE’s proven capabilities have made it the primary tool for each of these communities as well.
History
Because no formal Programs of Record (POR) existed with the capability to support the asymmetric warfare reporting
requirements within the USCENTCOM AOR, units on the ground in Iraq and Afghanistan developed and improvised
their own reporting tools and formats to accomplish the mission. Some of this data was reported in free-text format
within Microsoft Word and PowerPoint utilizing templates or forms. Other data were captured in semi-structured for-
mats using Microsoft Excel or Access using custom code or macros. Finally, a smaller portion of this data was re-
ported in locally developed software applications created by professional software engineers working on site.
CIDNE-3
COMBINED INFORMATION DATA NETWORK EXCHANGE (CIDNE)
ABCS Pocket Guide
History (cont)
As these disparate software initiatives began to tackle immediate local reporting requirements, new challenges
emerged. The first issue was the lack of standardized tools which presented training and adoption challenges. A sec-
ond, related issue that became increasingly problematic to data analysts was the lack of data standards. A third prob-
lem identified was the lack of interoperability. In most cases, these tools were not interoperable because they did not
share a common data standard or data structures. Finally, there was a lack of continuity as a result of unit and person-
nel rotations into and out of theater. This created islands of information which were not being readily shared across
communities, and when units left theater, they often removed the systems and data they created.
This also meant increased risk to the Warfighter. Since the incoming unit could not readily identify and review past
missions and efforts, troops were often sent to investigate / assess activity done several times already. There were no
means to ensure that the Soldier who wrote or used the local reporting solution would be replaced by someone with
the knowledge on how to maintain or adapt the system in response to changes in the operational environment.
The lack of common reporting tools, compounded by the lack of data standards, resulted in a fragmented reporting
architecture that made it extremely difficult to correlate, aggregate, and analyze data for long-term trend analyses.
The lack of standardization also made training new Soldiers problematic. As a result of these problems, critical op-
erations and intelligence information wasn’t readily available to decision makers and planners. Coordination in many
cases relied on personal relationships, rather than institutionalized, automated processes. Efforts to make sense of the
disparate data required a disproportionate level of resources. Data was literally lost or taken home during Transfers of
Authority and processes would be completely redesigned when a new unit rotated into theater.
CIDNE-4
COMBINED INFORMATION DATA NETWORK EXCHANGE (CIDNE)
ABCS Pocket Guide
History (cont)
In response to the growing reporting challenges in Iraq, Multi-National Forces-Iraq and Multi-National Corps-Iraq
started the CIDNE program in March 2005 in order to standardize reporting. As a result of these efforts, CIDNE was
designed to provide a single common toolset with well-defined data standards, and a robust web services layer to
facilitate interoperability with external systems in a services oriented architecture (SOA). It also provides data stor-
age and retrieval within a fully relational database that is in near-real-time replication across multiple sites in Iraq and
Afghanistan, as well as back to USCENTCOM HQ in Tampa, FL and other CONUS sites. In effect, CIDNE provides
a robust framework that includes advanced database and free-text search capability, geospatial visualization, work-
flow and report production capabilities with customizable reports to meet evolving Warfighter needs.
Another natural evolution resulting from the large number of user communities is the fact that CIDNE has continued
to grow to the point where it is now the primary database for event reporting information in Iraq and Afghanistan.
CIDNE is also the originating source database for nearly all stand-alone analytical databases and their accompanying
reports used for official data analysis and long-term trend reporting.
CIDNE-5
COMBINED INFORMATION DATA NETWORK EXCHANGE (CIDNE)
ABCS Pocket Guide
Architecture and Software
The CIDNE software is Government-owned software, developed and managed by USCENTCOM in partnership
with Air Force Research Laboratories (AFRL). The CIDNE system consists of a server, workstation, and Web-
Enabled Temporal Analysis System (WebTAS) portal.
The CIDNE 2.0 server requires several Commercial Off-the-Shelf (COTS) licenses, including ColdFusion 8.0.1
Enterprise Application Server, Microsoft SQL Server 2005 SP3, and Microsoft 2003 Enterprise Server. Additional
applications and licenses for these products may be necessary.
The CIDNE software has several tools and features that help augment the CIDNE capabilities. These include:
- Dashboards that provide module-specific, one-stop-shopping for predominant analytical views. The dashboard
is literally the first thing the analyst sees after clicking on the module menu option. There are preset queries
available to kick start the analytical process.
- GeoQuest 2.0 (Interactive Map) provides a library of geo-political and military shape files, including tribal
operating areas. It also allows users to create custom shape files and query for all reporting in specified areas.
All data can be exported to Google Earth and other geospatial tools. Also popular with users is a one-button
screenshot capability, enabling import into PowerPoint and other graphics and presentation software.
- WebTAS Interoperability provides a robust capability to visualize data from multiple data sources. CIDNE
uses WebTAS directly for its advanced query capability, which provides users with the ability to query
CIDNE event databased on any desired attribute. CIDNE is also completely mapped in WebTAS, which al
lows WebTAS users to correlate the data in CIDNE with data in external systems.
CIDNE-6
COMBINED INFORMATION DATA NETWORK EXCHANGE (CIDNE)
ABCS Pocket Guide
Architecture and Software (cont)
- “Asymmetric Threat and Tactical Analysis Casebook (ATTAC)” is one of the analytical products required in
the prosecution of IEDs is a storyboard which captures different facets of an IED event.
- “List Management Capability” is the most basic level of data management allowing people to organize the in-
formation they care about in lists. This can involve reports where they are watching for updates, reports they
themselves update on a regular basis, or just collections of reports that have some relationship to each other,
either directly or by context.
- “Tearline Capability” is a version of an intelligence report created by removing sensitive information, source,
and collection methods while still retaining substantive content to warrant dissemination. The resulting tear-line
report is therefore available to a wider audience who might not otherwise have access to the information.
- “Report Workflows” adopts a standard module that can be customized for use across all CIDNE report types.
CIDNE has adopted a more flexible user management capability that includes integrated authentication that
forms the basis for developing workflows.
CIDNE-7
COMBINED INFORMATION DATA NETWORK EXCHANGE (CIDNE)
ABCS Pocket Guide
ADVANCED FIELD ARTILLERY TACTICAL DATA SYSTEM (AFATDS)
The Advanced Field Artillery Tactical Data System (AFATDS) is an integrated fire support
C2 system that processes fire missions
and other related information to coordi-
nate and maximize the use of all fire sup-
port assets (mortars, field artillery, attack
helicopters, air support, naval gunfire, and
offensive electronic warfare). It meets the
needs of the field artillery by managing
critical resources and collecting and pass-
ing intelligence information.
What does it do?
AFATDS facilitates tactical command and control for fire support elements.
AFATDS is both UNIX and Windows based and operates as a “stand alone” system configured as the specific unit
and section.
By using the Joint Mapping Tool Kit (JMTK), AFATDS displays the COP. Utilizing the COP, AFATDS can provide
an accurate “picture” of the battlefield, so fire support assets can be utilized more effectively.
AFATDS allows the commander’s targeting priorities to be included into the database and used in the processing of
missions. This increases the efficiency of fires and planning, allowing the process to take place digitally. Using infor-
mation from the OPORD, Field Artillery Support Plan (FASP), and TACSOP, users can incorporate items such as the
High Payoff Target List (HPTL) and the Attack Guidance Matrix (AGM) into the database. Having this data in the
AFATDS database enables the digitization of the target analysis process.
AFATDS publishes Targets, Unit Position Reports, and Tactical Graphics to the BCS so the fire support picture can
be added to the COP.
AFATDS is the system used to process
fire mission requests,. It gives the com-
mander a planning tool for proposed and
planned targets. It also provides infor-
mation to DCGS-A to create Priority In-
formation Requirements (PIR) for the
commander’s approval.
AFATDS-1
ABCS Pocket Guide
What does it do? (cont)
AFATDS has the
ability to main-
tain technical and
tactical control of
fire support as-
sets. AFATDS
can compute
ballistic data,
issue deployment
orders, and track
ammunition for
artillery assets.
This control is
integrated into
the software and
database.
ADVANCED FIELD ARTILLERY TACTICAL DATA SYSTEM (AFATDS)
AFATDS-2
ABCS Pocket Guide
AFATDS incorporates fires coordination for surface-to-surface and air-to-surface missions using the Common Grid
Reference System (CGRS) and Kill Boxes. The creation of Kill Boxes allows for better coordination with associated
air assets.
AFATDS incorporates the Minimum Safe Distance (MSD) into the database. The MSD is the maximum effective
radius of munitions types used with each system. This function allows AFATDS to check for violations of friendly
units and fire support coordination measures (e.g. limited / protected area, friendly unit).
To ensure an accurate COP, AFATDS exchanges data between other ABCS (DCGS-A, MCS, and FBCB2) and non-
ABCS systems such as: Automated Fire Control System (AFCS), Command and Control Personal Computer (C2PC),
and the Forward Observation System (FOS). It does this through both direct and indirect communications. The indi-
rect communication path currently utilized is the PASS. The PASS contains “Topics” or categories of information
based upon the system and type of data. These topics contain information such as an enemy situation from DCGS-A
or position reports from FBCB2 / BFT. AFATDS can only publish three types of topics to the PASS. These are
graphics, position reports for artillery units, and targets. The Tracks Workspace in AFATDS allows users to sub-
scribe to as many topics as needed.
What does it do? (cont)
AFATDS provides the fire support view to the COP by de-
picting fire support coordination measures, pre-planned
fires, final protective fires, and active missions. The target
data includes active, inactive, planned, and on-call targets.
TTP
ADVANCED FIELD ARTILLERY TACTICAL DATA SYSTEM (AFATDS)
AFATDS-3
ABCS Pocket Guide
Position reports from FBCB2 or BFT are received through the PASS or di-
rectly via EPLRS. Position reports from non-FBCB2 / BFT units are received
from other AFATDS or from the Weapon Asset.
Slant reports are sent through the PASS or directly from FBCB2 or BFT. Ac-
tual status for units and weapons are sent from other AFATDS or from the
Weapon Asset.
Other Friendly units are sent as rack data or actual unit information through
the PASS from the MCS, FBCB2, or through AFATDS from fire support as-
sets.
Slant reports and position reports are received from the PASS or AFATDS for
the FS systems. It is updated automatically as the systems send the informa-
tion.
S309 (report) and other enemy intelligence data are received from the ASAS-L
and FBCB2 directly or through the PASS server. AFATDS sends ATI and
target data to the ASAS-L directly or through the PASS.
The status is updated via either the PASS from ASAS-L or through other
AFATDS as targets are engaged.
Consider these questions
by the commander . . .
Where am I?
What is my status?
Where is the enemy
and what is their
status?
How AFATDS helps answer them . . .
ADVANCED FIELD ARTILLERY TACTICAL DATA SYSTEM (AFATDS)
AFATDS-4
Where are the other
friendly units and
what is their status?
ABCS Pocket Guide
AFATDS Screens Fire Support COP
AFATDS contains in-
formation such as: Fire
Support Unit Loca-
tions, Fire Support Co-
ordination Measures,
and Targets. AFATDS
contains detailed data
for each unit and type
of asset (cannon, ra-
dar, air). AFATDS will
display range fans for
radar, observer, and
artillery units. It allows
the incorporation of the
Fire Support Coordina-
tion Measures into fire
mission processing.
Using information from
air support assets,
AFATDS can track and
display air missions
and air support units.
ADVANCED FIELD ARTILLERY TACTICAL DATA SYSTEM (AFATDS)
AFATDS-5
ABCS Pocket Guide
AFATDS Screens (cont)
AFATDS incorporates
the commander’s intent
into the processing and
analysis of targets.
AFATDS uses the infor-
mation from an
OPORD, FASP, or a
TACSOP to properly
prioritize and associate
targets based upon the
mission. For example, if
the commander wants
cannon artillery to
shoot three volleys of
HE RAP at tank-type
targets, this can be
specified as an attack
method, thereby
streamlining the target-
ing process.
Commander’s Guidance
ADVANCED FIELD ARTILLERY TACTICAL DATA SYSTEM (AFATDS)
AFATDS-6
ABCS Pocket Guide
AFATDS uses the Re-
mote AFATDS Appli-
cation Server (RAAS)
to connect to the
PASS. The RAAS is
the data broker for
ABCS information.
AFATDS publishes
graphics, position re-
ports, and targets to
the PASS. AFATDS
can also subscribe to
various topics pub-
lished to the PASS
from other systems
such as ASAS, DCGS-
A, MCS, CPOF, and
TAIS. AFATDS can
filter for specific infor-
mation sent to, and
received from, the
PASS.
PASS Connection AFATDS Screens (cont)
ADVANCED FIELD ARTILLERY TACTICAL DATA SYSTEM (AFATDS)
AFATDS-7
ABCS Pocket Guide
AFATDS will display friendly
and enemy tracks published to
the PASS. Using the Minimum
Safe Distance, AFATDS will
check targets against friendly
track locations for safer fires.
Enemy tracks can be targeted in
AFATDS. These targets will
follow their specific track if the
location is updated. AFATDS
can also communicate directly
with other systems such as
ASAS-L, DCGS-A, FBCB2 /
BFT, and TAIS. Using this con-
nection, AFATDS can exchange
information directly with the
system. AFATDS can auto dis-
tribute target Mission Fired
Reports (MFR) and fire mission
information to the intelligence
systems.
ABCS Interoperability AFATDS Screens (cont)
ADVANCED FIELD ARTILLERY TACTICAL DATA SYSTEM (AFATDS)
AFATDS-8
ABCS Pocket Guide
A Field Artillery Support Plan can
be digitally generated using infor-
mation from the maneuver course
of action (COA). It uses either ex-
isting data or new data to plan fu-
ture operations and calculate effec-
tive use of fire support assets and
ammunition based upon the ma-
neuver commander’s intent. Text
information pertaining to the plan,
fire missions, and fire plans can be
created within the plan. By digi-
tally creating this plan, it can be
distributed to all AFATDS affected
by the plan.
AFATDS Screens (cont) Fire Support Planning
ADVANCED FIELD ARTILLERY TACTICAL DATA SYSTEM (AFATDS)
AFATDS-9
ABCS Pocket Guide
AFATDS is capable of gen-
erating and tracking air
targets, air support re-
quests, and air support
lists. It also utilizes air con-
trol measures to ensure
coordination with aviation /
air units for indirect fire
support for SEAD missions.
Utilizing the Modernized
Integrated Database
(MIDB), AFATDS can re-
quest fixed-wing air sup-
port from the Air Force for
both air interdiction and
close air support missions.
AFATDS Screens (cont) Air Support Requests / Air Support Lists
ADVANCED FIELD ARTILLERY TACTICAL DATA SYSTEM (AFATDS)
AFATDS-10
ABCS Pocket Guide
Air Space Coordination
AFATDS makes
use of the Com-
mon Grid Refer-
ence System
(CGRS) to pro-
vide air-to-surface
and surface-to-
surface fires coor-
dination. Kill
Boxes can be cre-
ated for each type
of air support cov-
ering the battle-
field. These are
used in fires coor-
dination with
AFATDS FSCMs
to ensure accurate
and safe fires.
AFATDS Screens (cont)
ADVANCED FIELD ARTILLERY TACTICAL DATA SYSTEM (AFATDS)
AFATDS-11
ABCS Pocket Guide
Limited / Protected Areas (L/
PA) allow the operator to cre-
ate special graphics for infra-
structure and sensitive areas
such as schools, power sta-
tions, and hospitals. These can
be set to restrict the types of
munitions fired near or within
sensitive areas. AFATDS ac-
complishes this through the
use of Minimum Safe Dis-
tances (MSD). An MSD is the
maximum effective radius of
each type of munition utilized
in AFATDS. If the MSD ra-
dius for the munition called
for in the mission violates an
L/PA or friendly unit, it will
require coordination before
the mission can be fired.
MS D for each
Munition
L/PA radius
AFATDS Screens (cont)
Limited Protective Area and Minimum Safe Distance
ADVANCED FIELD ARTILLERY TACTICAL DATA SYSTEM (AFATDS)
AFATDS-12
ABCS Pocket Guide
AFATDS Screens (cont)
Effects Management Tool (EMT)
As a client of the
AFATDS, the EMT
allows the fire support
staff (FAIO, FSO,
FSCOORD, etc.) di-
rect access to data on
AFATDS. The EMT
operator can modify,
create, and export
information contained
in AFATDS. It can
generate fire missions
and track current mis-
sions. EMT receives
this data through a
direct client connec-
tion to AFATDS. This
allows the EMT to
receive AFATDS data
when it is received by
the AFATDS.
ADVANCED FIELD ARTILLERY TACTICAL DATA SYSTEM (AFATDS)
AFATDS-13
ABCS Pocket Guide
Effects Management Tool (EMT)
EMT allows for the
creation of planned
targets and target
lists. It can also be
assigned it’s own tar-
get block and generate
fire missions. Track
data received in
AFATDS can be dis-
played and used in
EMT. SEAD plans
can be auto-generated
using an existing air
corridor, and enemy
ADA tracks within a
certain radius can be
added to the plan.
Geometries and target
lists can be imported
from an Excel spread-
sheet created using
the template or from
other EMTs.
AFATDS Screens (cont)
ADVANCED FIELD ARTILLERY TACTICAL DATA SYSTEM (AFATDS)
AFATDS-14
ABCS Pocket Guide TACTICAL AIRSPACE INTEGRATION SYSTEM (TAIS)
The AN/TSQ-221 Tactical Command System, also known as the Tactical Airspace Integration Sys-
tem (TAIS), is a mobile communications and digitized Battlefield Automated System (BAS). The
TAIS can be deployed in any theater of operation to meet both Airspace Command and Control (AC2)
and Air Traffic Services (ATS) requirements.
TAIS is the designated Army Battle Command System (ABCS) used to integrate AC2. It provides
automated AC2 planning; enhanced AC2 execution; and improved theater, intra-corps, inter-corps,
and division ATS support. TAIS is used to synchronize area of operations in the third (altitude) and fourth (time) dimen-
sions. It also has an added civil and gov-
ernment interagency capability. TAIS
combines multiple input sources into a sin-
gle air picture. Combined with the electronic
ground picture, TAIS provides the com-
mander with visualization for both the air
and ground area of operations. TAIS pro-
vides a direct link to the Theater Air Ground
System (TAGS) through interface with the
Theater Battle Management Core System
(TBMCS). TAIS 10 upgrades the system
from Unix to Windows and incorporates
improved visualization using Command Post
of the Future (CPOF) technology, added
functionality to display and process the
Global Area Reference System (GARS),
Digital Automated Flight Information File
(DAFIF), and weather radar imagery, plus a
host of other improvements for airspace
management within Army Battle Command.
TIP: This system is typically found at Corps, Division, and Combat Aviation Brigades only.
TAIS-1
ABCS Pocket Guide AIR / MISSILE DEFENSE WEAPONS SYSTEMS (AMDWS)
AMD / AMDWS
The Air / Missile Defense Planning and Control System (AMDPCS) is the
backbone of Army air defense. It combines a fire control system; common air
and missile defense (AMD) planning; area of operation situational awareness;
joint, interoperable battle management; and command, control, communica-
tions, computers, and intelligence capability.
AMDPCS consists of sheltered systems
with integrated communications equip-
ment that provide air defense artillery
brigades with a fire control system for
monitoring and controlling engagement
operations by subordinate battalions via
the Air Defense System Integrator
(ADSI).
AMDPCS provides a common air and
missile defense staff planning and opera-
tional environment situational awareness
tool to achieve a common tactical and
operational air picture via the Air and
Missile Defense Workstation
(AMDWS). The AMDWS is fielded to
AMD units at all echelons of command,
battery through theater. AMDWS-1
ABCS Pocket Guide AIR / MISSILE DEFENSE WEAPONS SYSTEMS (AMDWS)
Air Defense and Airspace Management (ADAM) Cell
The Air Defense and Airspace Management (ADAM) Cell is an automated, inte-
grated, planning and control system that provides forces vertical and horizontal
interoperability with joint and coalition forces. The ADAM System will provide
Air Defense Artillery (ADA) commanders, staffs, and Fire Direction Center
(FDC) crews with fully-automated capabilities to enhance the execution of AMD
operations.
Air Defense Systems Integrator (ADSI)
The Air Defense System Integrator (ADSI) provides the Army Air and Missile Defense Commands (AAMDC) and the
ADA brigades with access to tactical and strategic communications, tactical data links, and intelligence networks such
the Joint Planning Network, Joint Data Network, and the Integrated Broadcast Service. Access to this information gives
the Commander and his staff the ability to monitor all aspects of air and missile defense operations. The ADSI also en-
ables them to coordinate and integrate Army, joint, and multinational Theater Missile Defense (TMD) forces in support
of a warfighting Combatant Commander. ADSI receives, processes, correlates, fuses, and displays up to two thousand
tracks from multiple tactical data links and intelligence sources. That integrated picture is forwarded to the Air and Mis-
sile Defense Workstation (AMDWS) to provide air situational awareness for dissemination into the Army Battle Com-
mand System (ABCS). In addition to Army locations, the ADSI is deployed with joint elements (NORAD, USSPACE-
COM), Air Force elements (AOC, air communications squadrons) and Navy vessels (command ships, aircraft carriers,
AEGIS cruisers).
AMDWS-2
ABCS Pocket Guide
The Global Command and Control System - Army (GCCS-A) provides command, con-
trol, and planning tools for Army strategic and theater commanders to enhance Warfighter
capabilities throughout the spectrum of conflict during joint and combined operations. In
operations other than war, it supports the National Command Authorities. GCCS-A is the
Army implementation of the Joint Staff Global Command and Control System (GCCS-J).
It works at the strategic and operational levels, acting as a bridge between GCCS and the
tactical components of ABCS.
What does it do?
GCCS-A is comprised of both
UNIX- and Windows-based
systems. The systems consist of
a TOC LAN Server (UNIX)
and Deployable Workstations
(Windows).
GCCS-A acts as the interface
between the Joint Staff Global
Command and Control System
(GCCS-J), ensuring information
exchange between Army ABCS
and joint forces systems.
GLOBAL COMMAND AND CONTROL SYSTEM - ARMY (GCCS-A)
GCCS-1
ABCS Pocket Guide
What does it do? (cont)
GCCS-A provides automated
warfighting tools for Army
commanders. These tools sup-
port a full spectrum of opera-
tions including: mission plan-
ning, deployment support, op-
erations in theater, and rede-
ployment of forces.
GCCS-A provides deliberate
and crisis planning projection of
Army forces using data from
Defense Readiness Reporting
System-Army (DRRS-A),
Movement Planning Execution
(MPEX), and Mobilization,
Operations, Deployment, Em-
ployment Execution (Mob /
ODEE).
GCCS-A allows personnel ac-
cess to the Joint Operations and
Planning Execution System (JOPES) to view Time Phased Force Deployment Data (TPFD) during the build process.
It can also view and refine force hierarchy contained in the OPLAN.
GCCS-2
GLOBAL COMMAND AND CONTROL SYSTEM - ARMY (GCCS-A)
ABCS Pocket Guide
GCCS-A can track Army forces during deployment into areas of operation and compare the plan with their actual
status. It can gauge how projected arrival and transfer of authority times will affect specific units based upon the ac-
tual departures.
GCCS-A allows for situational awareness between joint forces and Army headquarters by providing access to the
joint COP and interfacing with other ABCS systems on the battlefield.
GCCS-A allows the commander to specify unit equipment movement requirements and track intra-theater transporta-
tion of forces and logistics thru ALOG.
GCCS-A uses additional functions such as: Joint Warning & Reporting Network (JWARN) for NBC event tracking,
Theater Ballistic Missile Defense (TBMD) for missile tracking, and Integrated Imagery and Intelligence (I3), for up-
dated battlefield intelligence imagery.
GCCS-A provides the ability to track unit readiness, de-
ployed elements of units by personnel quantities and types,
and entire units embarked onboard ship.
TTP
What does it do? (cont)
GCCS-3
GLOBAL COMMAND AND CONTROL SYSTEM - ARMY (GCCS-A)
ABCS Pocket Guide
Position reports from FBCB2 or BFT are received through the PASS or di-
rectly via EPLRS / satellite. Position reports from joint forces (Marines, Air
Force, Navy, and coalition), are received from the GCCS-J and from C2PC via
the GCCS-Maritime (Navy, Marines).
Slant reports are sent through the PASS or directly from FBCB2 or BFT. Re-
ports are also sent from the GCCS-J for joint or coalition forces.
Other friendly units are sent as Track data or actual unit information
through the PASS from the MCS, FBCB2, or from GCCS-J for joint and coa-
lition forces.
Slant reports and position reports are received from the PASS or JOPES. It is
updated automatically as the systems send the information. Deployment status
is received via DRRS-A.
S309 (report) and other enemy intelligence data is received from the DCGS-A
and FBCB2 directly or through the PASS server. GCCS-A receives intelli-
gence information from the GCCS-I3 (Integrated Imagery and Intelligence)
through the I3 interface for live surveillance data from joint forces.
The status is updated via either the PASS from DCGS-A or
through other GCCS systems, (GCCS-AF, GCCS-M, GCCS-J).
Consider these questions
by the commander . . .
Where am I?
What is my status?
Where is the enemy
and what is their
status?
How GCCS-A helps answer them . . .
GCCS-4
GLOBAL COMMAND AND CONTROL SYSTEM - ARMY (GCCS-A)
Where are the other
friendly units and
what is their status?
ABCS Pocket Guide
GCCS-A Screens Joint COP
GCCS-A adds informa-
tion from ABCS systems
– from the lower echelons
into the joint picture to
create the joint COP.
GCCS-A is capable of
displaying imagery and
video from joint collec-
tion assets. GCCS-A in-
corporates friendly air
and ground units, enemy
units, logistics informa-
tion and status, from
Navy, Air Force, Ma-
rines, and coalition forces
into the COP allowing
Army elements to have an
accurate COP.
GCCS-5
GLOBAL COMMAND AND CONTROL SYSTEM - ARMY (GCCS-A)
ABCS Pocket Guide
GCCS-A Screens (cont)
GCCS-A provides
readiness reporting
of Army units en
route between arri-
val in the AO and
Transfer of Author-
ity (TOA). Interact-
ing with the De-
fense Readiness
Reporting System
Army (DRRSA), it
can see the readi-
ness unit capability
with mission essen-
tial tasks. This al-
lows commanders
to gauge the readi-
ness of units when
planning deploy-
ments.
Force Projection and Readiness
GCCS-6
GLOBAL COMMAND AND CONTROL SYSTEM - ARMY (GCCS-A)
ABCS Pocket Guide
GCCS-A assists in delib-
erate and crisis planning
of projection of Army
forces for utilization. It
also allows personnel to
access JOPES to view the
Time Phased Force De-
ployment Data (TPFDD)
during the planning proc-
ess using Army status of
resources and training
data to determine opera-
tional readiness. GCCS-A
can determine and review
force structure contained
in the OPLAN and use
this to create a Unit Task
Organization.
GCCS-A Screens (cont) Planning Tools
GCCS-7
GLOBAL COMMAND AND CONTROL SYSTEM - ARMY (GCCS-A)
ABCS Pocket Guide
GCCS-A tracks Army
forces during deploy-
ment into areas of op-
erations and compares
the plan against actual
status. This can show
how projected arrival
times and estimated
transfer authority of
specific units will af-
fect specific units
based upon actual
departure. GCCS-A
also provides tracking
of intra-theater trans-
portation of forces.
GCCS-A allows the
commander to specify
unit equipment move-
ment requirements for
deploying units.
GCCS-A Screens (cont)
Intra-Theater Deployment Support
GCCS-8
GLOBAL COMMAND AND CONTROL SYSTEM - ARMY (GCCS-A)
ABCS Pocket Guide
GCCS-A utilizes the
intelligence information
from the GCCS-J, the
Theater Battle Manage-
ment Core System
(TBMCS) used by the
USAF, JWARN, and
linked imagery and
UAV feed to provide
accurate intelligence
data to the Army. GCCS
- A adds the Army
ABCS intelligence data
to the Joint COP. Using
the Integrated Imagery
and Intelligence (I3)
function, GCCS-A can
view near-real-time data
from UAV and other
sources to create an ac-
curate joint enemy pic-
ture.
GCCS-A Screens (cont)
GCCS-9
GLOBAL COMMAND AND CONTROL SYSTEM - ARMY (GCCS-A)
ABCS Pocket Guide
With today’s tactical, digital environment, critical communication between the differ-
ent ABCS systems is paramount. To accomplish this mission, the Department of De-
fense has introduced a safe, secure, fast, and reliable network called Warfighter Infor-
mation Network-Tactical (WIN-T). This network brings ABCS systems together,
while at the same time providing a stand-alone network for Secure Internet Protocol
Router (SIPR) and Non-Classified Internet Protocol Router (NIPR) communications.
By using WIN-T, ABCS can be integrated on
a reliable network in a secure environment.
What does it do?
What is it comprised of?
WIN-T is fielded in four increments. Each
increment builds off the previous one so that
it will provide the tools necessary to seam-
lessly communicate from one location to
another. This allows the Warfighter the abil-
ity to stay in constant communications with
their commanders.
WARFIGHTER INFORMATION NETWORK-TACTICAL (WIN-T)
WIN-1
ABCS Pocket Guide
What are the Increments?
Increment 1 of WIN-T fielding is the Joint Network Node (JNN). This commercial equipment is a set of Cisco routers
and Promina switches that are housed in a S-250 shelter that is either mounted on a HMMWV or on a trailer for mobil-
ity and gives users the ability to communicate from anywhere in the world. JNN creates a secure, tactical network that
can be used for communicating and networking from a mobile platform to a fixed location using satellite technology.
JNN provides a satellite network that allows users to communicate beyond the line-of-sight network that the Mobile
Subscriber Equipment (MSE) previously provided. JNN has the ability to connect to SIPR and the NIPR at speeds of
up to 3Mbps constant and up to 4Mbps shared. The satellite receiver is usually housed at the division and BCT eche-
lons.
Increment 1
Increment 2 builds off of Increment 1 with all of the same qualities. However, it brings with it the ability to commu-
nicate from ground station to ground station using beyond line of sight tools (BLOS). This stage is focused on the
BCT with the anticipation of communications to the battalion and company levels.
Increment 2 uses commercial off-the-shelf and Government off-the-shelf technologies to add mobility from the BCT
to the company level. Increment 2 initially enabled planning, monitoring, controlling, and prioritizing (PMCP) at the
division headquarters and/or the brigade network. It was expected to disseminate critical information in less than five
seconds and time-sensitive information in less than eight seconds.
Increment 2
WARFIGHTER INFORMATION NETWORK-TACTICAL (WIN-T)
WIN-2
ABCS Pocket Guide
What are the Increments? (cont)
WIN-T Increment 2
gives the user the
ability to communi-
cate on a high-
bandwidth network
while on the move.
This increment al-
lows the companies
to communicate
with the BCT while
moving throughout
the battlefield. In-
crement 2 uses Gov-
ernment and com-
mercial technology
to create a mobile
network with both
satellite and line-of-
sight antennas.
Increment 2 (cont) WIN-T Architecture
On-The-Move SATCOM
Antenna
Highband Networking Waveform Line of
Sight Antenna
MPM 1000 Modem Limited Network Operations
Highband Network-ing Waveform Line
of Sight Radio
WARFIGHTER INFORMATION NETWORK-TACTICAL (WIN-T)
WIN-3
ABCS Pocket Guide
Increment 2 (cont)
WIN-T Increment 2 adds embedded communications gear that allows for SIPR to the commander’s platform for the
ability to maneuver anywhere on the battlefield and still have complete command and control. This increment also
delivers broadband networking capability using satellite and radio links.
WIN-T Increment 3 builds on the previous two increments and introduces an aerial tier that is mounted on Unmanned
Aerial Vehicles (UAV). This, combined with satellite communications and line-of-sight waveforms, complete a 3-
tiered network for communication superiority.
Increment 3
WIN-T Increment 4 is the final stage of the package. Increment 4 is designed to keep communications up to date with
the latest technology the civilian sector has to offer. This increment is still in its early stages. Once operational, this
stage will provide satellite communications (on-the-move) capability against jamming, detection, and interception for
Warfighters on the battlefield.
WIN-T Increment 4 is a Transformational Satellite System (TSAT). This is a 5-satellite constellation that allows for
between 10-40 gigabyte per second upload and download speed with a price tag of $12 billion to $16 billion. Once in
place, this network of satellites will be able to provide a fast, reliable, secure, high bandwidth network for Military
Satellite Communications (MILSATCOM) that is defined in the Transformational Communications Architecture
(TCA).
Increment 4
WARFIGHTER INFORMATION NETWORK-TACTICAL (WIN-T)
What are the Increments? (cont)
WIN-4
ABCS Pocket Guide
Increment 4 (cont)
The purpose of the TCA is have an ever-evolving
system so that the net-centric Warfighter does
not fall behind with the ever-changing technol-
ogy of today's battlefield. TCA is looking for the
US Air Force to launch the 5-satellite constella-
tion sometime in 2013.
TSAT is the spaceborne component of the Global
Information Grid (GIG). This piece extends the
GIG to users who are without terrestrial connec-
tions, providing an improved connectivity to the
Warfighter. WIN-T and telecommunications
were supposed to be integrated by the year 2016.
However, due to high costs and programming
issues, TSAT was pulled from the program on
April 6, 2009. A replacement has not yet been
named.
WARFIGHTER INFORMATION NETWORK-TACTICAL (WIN-T)
What are the Increments? (cont)
WIN-5
ABCS Pocket Guide JOINT NETWORK NODE (JNN)
The Joint Net-
work Node, or
JNN as it is
commonly
called, allows
units to send
their data from
various ABCS
Systems over
long distances to create the Joint COP. The JNN
system is a communications system the Army
uses for remote, satellite-based communication. It
provides beyond line-of-sight (BLOS) capabilities
for the Warfighter. Previous communications
equipment systems required line of sight for net-
work capability. JNN provides a high-speed,
wide area network infrastructure that connects the
BCT Main CP and BCT Support Battalion CP to
the joint voice and data network. For example,
brigades deployed overseas can send their ABCS
information to their division in garrison for higher
echelon visibility.
JNN-1
ABCS Pocket Guide
JNN and BNCPN Satellite Transportable Terminal (STT)
Environmentally sealed elec-tronic enclosure with integral rack mounts and cooling
Shock antenna boom rest with integrated aerial lift-ing points. Out riggers stow to side of structure
Front leveling jack used in con-junction with two rear jacks for leveling
Air Conditioner and Storage area Generator
Deployable outriggers for stabilization w/large pads for loose soil conditions
JNN-2
JOINT NETWORK NODE (JNN)
ABCS Pocket Guide
What does it do?
Commercial equipment inside the JNN allows tactical users to interface with the global information grid, joint and
interagency organizations, and the division headquarters. JNN is also interoperable with commercial networks and
current force communications systems, and can provide video teleconferencing, e-mail, and local area network ser-
vices.
The JNN suite consists of:
- A S-250E shelter mounted on a M-1152 HMMWV
- SIPR access interface transit case w/Tactical Local Area Network Encryption (TACLANE)
- NIPR access interface transit case w/Uninterruptible Power Supply (UPS)
- Router transit case
- Voice over IP (VoIP) phone transit case
- LAN management resources.
The JNN is located at the division and BCT levels. The JNN consists of a high-mobility, multipurpose, wheeled vehi-
cle (HMMWV)-mounted S-250 shelter communications platform that allows a division and BCT headquarters to as-
sume control of critical pieces of network services, network management, and establish communication priorities
when the division and BCT fight as a whole. The division and BCT JNN connect into the Unit Hub Node (UHN) for
end-to-end network service connection into the Global Information Grid (GIG), Defense Information Systems Net-
work (DISN), and Defense Switched Network (DSN).
JNN-3
JOINT NETWORK NODE (JNN)
ABCS Pocket Guide
What does it do? (cont)
The system provides a communications gateway and interoperability with legacy tactical communications assets. The
conversion from an MSE-based to a JNN-based system means that Soldiers will be able to communicate more effi-
ciently and effectively. JNN, unlike MSE, is lighter, easier to set up and maintain, and works with satellites instead of
LOS communications, a feature that makes communication less prone to interference from earthly terrain and allows
for systems to be widely dispersed without the use of radio relays.
The increase in capability will also be felt greatly at the battalion level, which will receive satellite communications
trailers and transit-cased switch systems as part of the Joint Network Transport Capability (JNTC). Battalion com-
manders will now have communications capability that ties back in to JNNs at the brigade level. When preparing for a
movement or a patrol mission, the battalion will be able to access much needed information which could include
maps, graphics, photographs, extensive descriptions of the mission terrain, and potential threats. This helps them plan
out the mission and have key intelligence on where they’re going . . . thus saving Soldiers’ lives.
The JNN at the division and/or BCT levels provides a high-speed, wide area network (WAN) infrastructure that con-
nects the BCT Main CP to the joint voice and data networks. The JNN allows tactical users to interface into the GIG,
joint, interagency organizations, and the division headquarters. The JNN is also interoperable with commercial net-
works and current force communications networks.
The JNN is designed to be employed at all levels of the Army structure and fully supports the modularity concept of
the Army. The JNN is scalable to provide capabilities necessary to support different CPs, ranging from battalion CPs
to larger and more complex CPs at the brigade and division.
JNN-4
JOINT NETWORK NODE (JNN)
ABCS Pocket Guide
What equipment is involved in a basic JNN setup?
JNN-5
JOINT NETWORK NODE (JNN)
ABCS Pocket Guide
What are some lower echelon JNN assets?
Battalion-level communication sections are fielded via the Battalion Command Post Node (BnCPN). The BnCPN pro-
vides enhanced voice and data capabilities at support battalions. It also has SIPRNET and NIPRNET devices and access.
The BnCPN has the capability to interface directly to Ku satellite or line-of-sight radio transmission resources.
The BnCPN suite of communications equip-
ment is housed in transit cases:
SIPR data interface transit case w/TACLANE
Red voice interface using Cisco IP phones
Black voice interface using Cisco IP phones
LOS Di-Phase Modem Case w/KIV-19
IP phone case
LAN network management resources.
Front Front
Back Back
Case 1 Case 2
JNN-6
JOINT NETWORK NODE (JNN)
ABCS Pocket Guide
What are some lower echelon JNN assets? (cont)
There is one BnCPN located at the battalion level to provide voice and data capabilities. It uses Time Division Multiple
Access (TDMA) satellite transmission to gain access through the JNN or Unit Hub Node (UHN) to the Global Information
Grid (GIG). The BnCPN uses Ku band trailers. This is a type of satellite frequency primarily used for sending informa-
tion from remote locations back to home station. With these assets, the battalion commander will be able to send his unit
information to his higher command in a much more timely fashion.
JNN-7
JOINT NETWORK NODE (JNN)
ABCS Pocket Guide
DCGS-A Information (Knowledge Center) Several Documents
https://www.us.army.mil/suite/kc/9778559
Global Command and Control System - Army (GCCS-A) AKO site: https://www.us.army.mil/suite/page/135817 Global Transportation Network
https://www.gtn.transcom.mil/
PEO C3T Homepage http://peoc3t.monmouth.army.mil/connecting_systems/ConnectingSystems.html
LIW Homepage ( AKO account required ) https://liw.logsa.army.mil/index.cfm?fuseaction=login.main
National ITV Server https://national.rfitv.army.mil/login/Login.do
PM BC Homepage http://peoc3t.monmouth.army.mil/battlecommand/battlecommand.html
Single Mobility System https://sms.transcom.mil/sms-perl/smswebstart .pl
Tactical Ground Reporting System (TIGR) TIGR POI_v4262 TIGR (Updated 13 Mar09)
TIGR SOI - March 02, 2009 TIGR Unclassified SOP http://www.darpa.mil/news_images/tigr2.html http://www.gdc4s.com/featurettes/detail.cfm?featureid=53
http://www.almc.army.mil/alog/issues/May-June10/groundrpt_oppic.html https://search.us.army.mil/AKOSearch/TIGR
Time Zone Converter http://t imezoneconverter.com/cgi-bin/tzc.tzc
Warfighter Information Network – Tactical (WIN – T) https://www.us.army.mil/suite/portal/index.jsp;jsessionid=5A9256BC6DFBD063F3E943E87A7EA635.appd05_2
http://www.globalsecurity.org/military/systems/ground/win-t.htm Web REPO L (DESC Homepage) ( SIPR only. Scroll down and select JCS REPOL, account required ) http://www.dla.smil.mil/desc/plan/index.html
Advanced Field Artillery Tactical Data System (AFATDS) TM 11-7025-297-10 Operators Manual Advanced Field Artillery Tactical
Data System (AFATDS) Operational System Software Version BC 10.0 TCM FSC3 AKO site: https://www.us.army.mil/suite/page/111551 TB 11-7025-354-10-1 thru 8 TCM FSC3 AKO site: https://www.us.army.mil/suite/page/111551
Air and Missle Defense Workstation (AMDWS) http://peoc3t.monmouth.army.mil/cram/AMD_AMDWS.html
AKO Homepage https://www.us.army.mil
Battle Command Server (BCS) TB 11-7010-440-13 (Maneuver Control System (MCS) Software Admini-stration Manual (SAM) Version 6.4.5.1 P7
Battle Command Sustainment Support System (BCS3) PdM BCS3 Homepage https://bcs3.army.mil BCS3 Help Desk (C4ISR SIF) (AKO account required )
https://hd.kc.us.army.mil/ BCS3 Software Assurance Site (IAVAs and Security Patches for BCS3) https://www.us.army.mil/suite/page/412075 TCM BCS3 Homepage
http://www.cascom.army.mil/esd/tcm/bcs3
CIDNE Capabilities O verview (Unclassified) 03July2009 https://www.us.army.mil/suite/doc/11761856
Command Post of the Future (CPO F) TB 11-7010-464-13 Command Post of the Future (CPOF) Software User's Manual (SUM) Version QR1FY09 (BC09.0.4)
Combined Information Data Network Exchange (CIDNE) Combines Information Data Network Exchange CIDNE 2.X Capabilities White Paper Feb 2010 https://www.us.army.mil/suite/doc/22519953
Distributed Common Ground System – Army (DCGS – A) DCGS-A Overview (Unclassified) IEW&S PEO February 2010
https://www.us.army.mil/suite/doc/22824262
REFERENCES
Ref-1
ABCS Pocket Guide
POINTS OF CONTACT
The ABCS-ST
Celebrating 10 Years of
Training Excellence
Program Manager Mr. Derek Stidham
[email protected] 913-758-5585 Team Lead
Mr. Robert Lopez [email protected]
913-758-5587
For Specific System Questions, Contact:
C2 Mr. Steve Lutze
[email protected] 785-633-3538
Intel / CPOF Mr. Jerry Jackson
[email protected] 913-775-1552
BCS3 Mr. Gregg Kline
[email protected] 816-273-6889
AFATDS Mr. John Doty
[email protected] 913-705-0246
POC-1