Professional Documents
Culture Documents
Army Battle Command System Pocket Guide
Army Battle Command System Pocket Guide
TABLE OF CONTENTS
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 TOC-1
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 System (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 Azimuth, 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 guides cargo pocket design alleviates that problem, and although systems are updated and software versions change, it will still provide valuable information on the basic capabilities that are available to the Soldier.
Purp-1
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 understanding.
A2C2 ACO AFATDS AFCS AIS AMD WS ArcGIS AS ORTS AS AS ATCCS ATI ATO ATTAC BAS BCS BCS 3 BLF BLOS BnCPN C2PC C2R CAT Army Airspace Command and Control Air Control Order Advanced Field Artillery Tactical Data S ystem Advanced Fire Control System Advanced Information S ystem Air and Missile Defense Workstation Arc Geographic Information S ystem Army S tatus of Operational Readiness and Training S ystem All S ource Analysis S ystem Army Tactical Command and Control S ystem Automated Tactical Intelligence Air Tasking Order Asymmetric Threat and Tactical Analysis Notebook Battlefield Automated S ystem Battle Command S erver Battle Command S ustainment Support S ystem 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 DS N DTSS ENS IT EMT EPLRS FBCB2 FOS GCCS -A GIG GUI HDWS IDM Common Grid Reference S ystem Combined Information Data Network Exchange Common Ground S tation Commercial Joint Mapping Tool Kit Circular Line-of-Sight Common Operational Picture Command Post Network Command Post of the Future Commanders Tracked Item List Common Tactical Picture (S oftware) Decide, Detect, Deliver, Assess (Targeting Method) Distributive Common Ground S ystem Army Defense S witched Network Digital Topographic S upport S ystem Enemy Situation Effects Management Tool Enhanced Position Location Reporting S ystem Force XXI Battle Command Brigade-and-Below Flight Operations S ystem Global Command and Control S ystem Army Global Information Grid Graphical User Interface Human Domain Workstation Internet Download Manager
Acro-1
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
Acro-2
IMETS - Integrated Meteorological System PASS Publish and Subscribe Services NRTS Near Real Time Server C2PC GW C2PC Gateway AFATDS Advanced Field Artillery Tactical Data System AMDWS Air and Missile Defense Workstation BCS3 - Battle Command Sustainment Support System BCS Battle Command Server
Arch-1
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 Brigade-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 commanders 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
Position Report
(Friendly vehicle / unit locations)
Enemy Overlay
(Location, size, activity of enemy)
Obstacle Overlay
(Graphical depiction of friendly and enemy obstacles)
NBC Overlay
(Graphical depiction of the location of decontamination and reconnaissance sites and smoke operation lines)
Sector ID Overlay
(Graphical depiction of defensive operations at company level and below)
COP
Range Card
(Graphical depiction of range cards developed for defensive fighting positions)
COP-2
PLAN Assists the commander in providing his intent 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 commanders 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. COP-3
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.
COP-4
Simulation
Simulation
Simulation Server
Simulation
Simulation
Blue Units/Tracks
Ops/Plans Graphics
TBC
Depending on the exercise f ocus and type of simulation, some or all of the enemy units/tracks may be f ed f rom the simulation
BCS
Red Units/ Tracks
ABCS
DCGS-A ASAS
PASS
NRTS
Intelligence Graphics
C2PC GW
COP
ABCS
AFATDS
Artillery Graphics
BCS3
Logistics Graphics
COP-5
BCSoSIT-1
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:
Key Tasks: Attend Unit Set Fielding (USF) Sync Conferences (Phase I and V) to conduct CP&SIT Brief (schedule New Material 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 units collective training event (mission rehearsal exercise or similar).
Events:
Event 1 - BCSoS Command Post Integration Training (4 days)
Mission: Conduct Battle Command System of Systems Integration Training in the units command post using the units equipment in order to validate command post infrastructure and network. BCSoSIT-2
Mission: Conduct BCSoSI Training in the units command post using the units equipment in order to validate command 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 integrate their equipment and restore capability upon major failures.
End State: The staff has increased confidence in abilities to execute command post operations by collecting, processing, displaying, disseminating, and storing relevant information using the INFOSYS.
BCSoSIT-4
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.
MCS SQL DATABASE
C2PC GATEWAY
TMS Broker
NRTS
PASS
TIME SERVER
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 Gateways 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. BCCS-1
TIPS:
The PASS Data Provider will be the primary means of receiving updated data from other ABCS systems. 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 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!
BCS Screens
The Server Configuration Console allows users to configure the various server processes. All of the processes can be run on one server or some / all of the processes can be split between several servers to lessen the load if system resources are being taxed.
BCCS-2
The AutoSetup Utility is used to set up the desired client connections 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 having to manually enter the data in each plug-in.
BCCS-3
The Console alerts administrators to issues that may require their attention. In this example, the GCCS Provider has a connection issue and the AFATDS Provider requires attention and has been stopped.
The NRTS Server Console allows administrators to configure, start, and stop data providers to control the Live Feed, which is then disseminated to the ABCS end-users.
BCCS-4
EZ PASS Explorer
The EZ PASS Explorer gives administrators a way to manage and view the topics that are published to the PASS.
BCCS-5
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 Enterprise 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. BCCS-6
BCCS-7
Logistics Reporting
Tailorable to any computer Provides standard reports
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
BCS3-3
By Unit By Unit
BCS3-4
Combat Power Combat Power Class V Class V Class VII Class VII
Class IV Const and Barrier Class IV Const and Barrier Materials Materials
BCS3 provides over ninety different Running Estimate (RE) reports covering every unit and supply point class from I X.
BCS3-5
BCS3-6
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 include 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 interoperable systems provided to the Warfighting Team. CPOF and MCS Client Workstation 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 combines 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 displayed 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
The Maneuver Control System (MCS) is an integrated system of hardware, software, personnel, 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, directing, 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 armored and wheeled vehicles, tents, and in those aircraft used as C2 nodes. It is typically fielded today as a dual-loaded system with CPOF.
Effective 1 January 2011, the Army will no longer support MCS. ABCS-ST however, will continue to train and support units that still have MCS.
Displays the COP and provides tools to graphically support the unit MDMP: graphically displays critical information. 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 displayed 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. MCS-1
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 versions support JWARN and JEM more fully.
What is my status?
MCS-3
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
The MCS Maps and Overlays application is used to create and share overlays and events as well as display and manage the COP.
MCS-5
MCS provides users with a messaging application to support USMTF and JVMF messaging that functions similar to commercial e-mail operations (create, edit, transmit, print, store, and auto-update).
MCS-6
MCS provides users with a data explorer application. The MCS Data Explorer allows simplified management and transfer of data between the various data sources available to the workstation operator.
MCS-7
FBCB2-1
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.
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 organization and other factors. Moving forward to the next variant, called Joint Capabilities Release (JCR), users only receive 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
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 accuracy of calls-for-fire and reports on enemy locations (via SPOT Report). BFT currently does not have this capability because it has no direct interface with AFATDS.
TTP
FBCB2-4
SECRET NETWORK
UNCLASS NETWORK
FBCB2-5
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
FBCB2-7
FBCB2-8
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 nearreal-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.
Shared 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, CPOFs disconnected operations are extremely limited. CPOF-2
Full-spectrum operations follow a cycle of planning, preparation, execution, and continuous assessment. CPOF provides commanders with situational awareness throughout this cycle.
CPOF-3
Visualize tactical action Better understand METT-TC Visualize the elements of operational design Communicate the commanders intent Communicate the commanders 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.
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.
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, textual, and audio clues. CPOF-5
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).
CPOF-6
This screen is a detailed example of a Commanders Update Brief (CUB). This brief can be shared with all of the CPOFs in a unit so that commanders can utilize CPOFs greatest strength: collaboration in real time. This presentation includes several pasteboards 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 information. CPOF-7
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.
Terrain Exaggeration
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)
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 resembles the functionality of the previous Scratch Schedule.
3. Task Organization was previously part of the Master Schedule but is now accessible through the Tree Viewer.
CPOF-9
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 decisionmaking. CPOF-10
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 intelligence 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 battalion or brigade level and above.
The TIGR system, shown in this screenshot and the one on the following page, provide its users with a platform to consolidate report information and share that information with intelligence analysts and commanders at higher echelons. Its capability to provide near-real-time information provides patrols and convoys with an up-to-date look at their surroundings before they head out on a mission. TIGR-1
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) process, 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).
TIGR-3
TIGR-4
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
TIGR-5
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.
TIGR-6
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 TIGRs 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 Armys adoption of this program takes advantage of the militarys 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.
TIGR-7
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 leaders laptop screen while on patrol, incorporating the different types of data that might be pertinent to his operation. Any newly imputed data will update once plugged back into the network.
TIGR-8
TIGR-9
Tested and validated over JNN network at JRTC, PEOC3T testing, and in theater.
TIGR-10
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 Mission Area Initial Capabilities Document (ICD) defines DCGS as a program to migrate select intelligence 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 warning, 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, warfighting functions (WFF), and the DoD DCGS FoS. DCGSA software and hardware are tailored by echelon and scalable 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; control 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 Command architecture, DCGS-A allows the integration of all ISR assets based on the Commanders Critical Information Requirements (CCIR) to produce intelligence that contributes to the COP, situational understanding (SU) and situational awareness (SA). DCGS-1
The fixed configuration (e.g., Home Station Operations Center (HSOC)) will conduct day-to-day intelligence planning, 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 commanders 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 commanders situational awareness without increasing the forward footprint. Embedded DCGS-A is the common software baseline used in fixed and mobile DCGS-A. The embedded configuration is also provided for integration into other systems to provide ISR capabilities.
Why DCGS-A?
To eliminate the legacy stove piped military intelligence ISR architecture and enable the sharing of data via distributed 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. DCGS-2
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 accessible 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. Collection and processing time will be dramatically reduced through the introduction of the DCGS-A applications, allowing 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 repository. 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.
Integrated Capabilities
V.3.0 is the beginning step to the overall integration of all Programs of Record (POR) and the Multi-Functions Workstation, 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 domains. DCGS-3
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 applications 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 process 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)
DCGS-4
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
DCGS-6
DCGS-7
DCGS-8
DCGS-9
DCGS-10
DCGS-11
Information entered into CIDNE by one community can be tied to other information within the system, providing a correlated view of information across multiple communities.
CIDNE-1
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, CIDNEs 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 formats using Microsoft Excel or Access using custom code or macros. Finally, a smaller portion of this data was reported in locally developed software applications created by professional software engineers working on site. CIDNE-3
CIDNE-4
CIDNE-5
CIDNE-7
AFATDS-2
Position reports from FBCB2 or BFT are received through the PASS or directly 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. Actual 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 assets. 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 information.
What is my status?
Where are the other friendly units and what is their status?
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. AFATDS-4
Commanders Guidance
AFATDS-6
PASS Connection
ABCS Interoperability
AFATDS-8
AFATDS-9
AFATDS-10
AFATDS-11
AFATDS-12
The AN/TSQ-221 Tactical Command System, also known as the Tactical Airspace Integration System (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) dimensions. It also has an added civil and govTIP: This system is typically found at Corps, Division, and Combat Aviation Brigades only. ernment interagency capability. TAIS combines multiple input sources into a single air picture. Combined with the electronic ground picture, TAIS provides the commander with visualization for both the air and ground area of operations. TAIS provides 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. TAIS-1
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, communications, computers, and intelligence capability.
AMDPCS consists of sheltered systems with integrated communications equipment 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 operational 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
Air Defense and Airspace Management (ADAM) Cell The Air Defense and Airspace Management (ADAM) Cell is an automated, integrated, 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 enables 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 Missile Defense Workstation (AMDWS) to provide air situational awareness for dissemination into the Army Battle Command System (ABCS). In addition to Army locations, the ADSI is deployed with joint elements (NORAD, USSPACECOM), Air Force elements (AOC, air communications squadrons) and Navy vessels (command ships, aircraft carriers, AEGIS cruisers).
AMDWS-2
TTP GCCS-A provides the ability to track unit readiness, deployed elements of units by personnel quantities and types, and entire units embarked onboard ship. GCCS-3
Position reports from FBCB2 or BFT are received through the PASS or directly 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. Reports 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 coalition 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 intelligence 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). GCCS-4
What is my status?
Where are the other friendly units and what is their status?
Joint COP
GCCS-5
GCCS-6
Planning Tools
GCCS-7
WIN-1
Increment 2
Increment 2 builds off of Increment 1 with all of the same qualities. However, it brings with it the ability to communicate 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. WIN-2
WIN-T Architecture
Highband Networking Waveform Line of Sight Antenna MPM 1000 Modem Limited Network Operations Highband Networking Waveform Line of Sight Radio
WIN-3
WIN-T Increment 2 adds embedded communications gear that allows for SIPR to the commanders 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.
Increment 3
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 3tiered network for communication superiority.
Increment 4
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). WIN-4
WIN-5
JNN-1
Front leveling jack used in conjunction with two rear jacks for leveling
Deployable outriggers for stabilization w/large pads for loose soil conditions
JNN-2
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 services. 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 vehicle (HMMWV)-mounted S-250 shelter communications platform that allows a division and BCT headquarters to assume 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 Network (DISN), and Defense Switched Network (DSN).
JNN-3
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 efficiently 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 commanders 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 theyre going . . . thus saving Soldiers lives. The JNN at the division and/or BCT levels provides a high-speed, wide area network (WAN) infrastructure that connects 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 networks 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
JNN-5
JOINT NETWORK NODE (JNN) What are some lower echelon JNN assets?
Battalion-level communication sections are fielded via the Battalion Command Post Node (BnCPN). The BnCPN provides 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. Case 1 Case 2
Front
Front
Back
Back
JNN-6
JNN-7
REFERENCES
Advance d 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 T CM FSC3 AKO site: https://www.us.army.mil/suite/page/111551 T B 11-7025-354-10-1 thru 8 T CM FSC3 AKO site: https:// www.us.army.mil/suite/page/111551 Air and Missle De fense Workstation (AMDWS) http://peoc3t.monmouth.army.mil/cram/AMD_AMDWS.html AKO Homepage https://www.us.army.mil Battle Command Serve r (BCS) T B 11-7010-440-13 (Maneuver Control System (MCS) Software Administration 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 T CM 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) T B 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
Ref-1
POINTS OF CONTACT
Program Manager Mr. Derek Stidham [email protected] 913-758-5585
BCS3 Mr. Gregg Kline [email protected] 816-273-6889 C2 Mr. Steve Lutze [email protected] 785-633-3538
POC-1