1 / 17

Distributed Common Ground System – Army Net-centric ISR for future Army Battle Command

Distributed Common Ground System – Army Net-centric ISR for future Army Battle Command. For AOC Battle Management Conference Melbourne, FL 8 June 2004. Colonel Steve Bond, U.S. Army TRADOC System Manager DCGS-A. Jun 04. Distributed Common Ground System – Army (DCGS-A). Sequence:

hop
Download Presentation

Distributed Common Ground System – Army Net-centric ISR for future Army Battle Command

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Distributed Common Ground System – Army Net-centric ISR for future Army Battle Command For AOC Battle Management Conference Melbourne, FL 8 June 2004 Colonel Steve Bond, U.S. Army TRADOC System Manager DCGS-A Jun 04

  2. Distributed Common Ground System – Army (DCGS-A) Sequence: • Why DCGS-A? • What is DCGS-A? • Objective Concept — “To Be” • “As Is” Migration—DCGS-A “Spirals” • Where will it be? • When (Timeline)? THIS BRIEFING IS UNCLASSIFIED

  3. DoD DCGS DoD directed program for “Net-Centric ISR for JTF and Below” DoD Distributed Common Ground/Surface System Capstone Requirements Document SERVICE PROGRAMS DCGS INTEGRATED (SOFTWARE) BACKBONE (DIB) DCGS-A ORD AROC Approved 2 Dec 03 Air Force- Distributed Common Ground System Marine Air- Ground Information System Distributed Common Ground System— Army Distributed Common Ground/ Surface System-- Navy DoD Envisioned and mandated program. CRD JROC Approved 9 Jan 03 All Services are building components of DCG/SS

  4. Interoperable ISR Sensors & Platforms From DoD DCGS CRD; DCGS-A ORD Interoperability KPP, IER Matrix • FUTURE SYSTEMS • Space Based Radar • MC2A • Allied Sensors • Commercial Sensors • Aerial Common Sensor • UAVs • Apache • JLENS • Division Tactical SIGINT Package • Prophet • SOF/HUMINT • Unattended Ground Sensors • Robots • Future Combat System Sensors • Objective Force Warrior • And Others… • DCGS CRD BASELINE • National Space Systems • U2 • Global Hawk • Predator UAV • Joint STARS • Rivet Joint • EP-3 • F/A-18 Super Hornet • Vertical Takeoff UAV • Guardrail Common Sensor • Airborne Reconnaissance Low • Shadow Tactical UAV • Other Service DCGS “Persistent” Intelligence, Surveillance, and Reconnaissance

  5. CHIMS (HUMINT) Army Intelligence System Convergence Ground Station Migration--from DCGS-A ORD Para 1.5 System Description FUTURE CURRENT ACS GRCS IPF (SIGINT) GRCS Ground Station ARL GRIFN (SIGINT) TES-M/TES-F(SIGINT/IMINT) GRIFN / IPF Ground Station Functions migrate to DCGS-A DCGS-A TES / TES-F / DTES AEPDS / MITT / FAST FCS Sensor Data JSTARS CGS CGS(IMINT/MTI) ASAS + CHATS / CHIMS TUAV ASAS (ALL SOURCE INTEL) Family of UAVs UAV GCS HUNTER QUICKFIX PROPHET REMBASS Prophet Control TUAV GCS(IMINT) GSR E-TRACK / TRACKWOLF TRAILBLAZER / TRAFFIC JAM / TEAMMATE

  6. Gaps in Current Systems From DCGS-A ORD Para. 1.1.2. Critical Shortfalls of Current ISR capabilities • Large tactical footprint—vehicles, hardware, tents… • Operate from static positions—not enroute or “on-the-move” • Limited collaboration and visualization • Limited security exchange policies and technology • Most current systems built around single ISR platforms • Significant training and sustaining challenges with multiple ground systems • Limited interoperability among Services and Intel Agencies • Data flow stops before reaching the Combat User

  7. ISR Lessons Learned3d Infantry Division OIF Experience • Ability to strike exceeded the ability to target • Inadequate Battalion and Brigade S2 / Intel organization and sensor structure • Uneven skill mix, lack of branch standards, requirement for ad hoc teaming for intel • No Analytic Centers providing overwatch for the tactical fight or transitions • ISR priorities focused on higher echelons • No red/blue COP after crossing the Line of Departure • Inability to support BCOTM with threat data • Inability to share higher picture to and across the ‘last tactical mile’ • Unreliable BDA from joint fires The Future Force Can’t be Fought, it Doesn’t Exist. The Army has to be Ready to go to War with What it Has. Gen Peter J. Schoomaker Army Chief of Staff FOUO

  8. DCGS-A Objective Concept From DCGS-A ORD Para 1. Enables and Supports Commanders to: • See First • Orchestrates, synchronizes, and integrates Joint, Interagency, Multi-National, and Army (MI and non-MI) ISR sensors in all operational phases across the spectrum of conflict • Eliminates information barriers • Understand First • Provides fusion and analytical capabilities to support situational understanding • Act First • Supports maneuver to positions of advantage and develops targets • Finish Decisively • Provide battle and effects damage assessment

  9. DCGS-A Is… From DCGS-A ORD Para 1. • Joint Interoperable,Network-Centric ISR for Commanders, Shooters, and Analysts • Brings National, Joint, Coalition, and Commercial ISR to Units of Action…down to the Future Combat System (FCS) and Land Warrior • Facilitates “Reach” and “Collaboration” • Army’s Future Force ISR sensor fusion and processing system • Single Army System for tasking sensors, providing information and intelligence to all Users (embedded on FCS & in Future Battle Command System) • Brings Threat, Neutral, Terrain & Weather to the Common Operating Picture, enables the Intel Running Estimate, supports targeting & effects • Fixed Sites at “Units of Employment”; Mobile (deployable/ man-portable) for UE and “Units of Action”-Bde Intel Comms Company; and Embedded Software Application on FCS & Battle Command System • Part of the DoD C4ISR Architecture; mandated by JROC, DoD & Congress • Shared interoperable baseline for all Services DCGS; common hardware, software, and protocols • Not a communications system--Relies on the Global Information Grid (GIG), WIN-T, & JTRS (“Critical Dependency”) • A “Complementary System” to FCS; ISR Processing Component of future Battle Command System 9

  10. Core Functions From DCGS-A ORD Para 1.5. System Description • Enable the Joint ISR Architecture • Link ISR Sensors--“Mud to Space” • Reach--“Combat Unit to Intel Agency” • Sensor Collection Management • Collection & Processing of National/Joint ISR Sensor Systems • Control of Select Army/Joint ISR Sensors • Intelligence Synchronization, ISR Planning, Recon & Surveillance Integration • Fusion of Sensor Information • Build the COP; Enable Situational Awareness • Direction, Distribution & Dissemination of Sensor Information

  11. Where Will DCGS-A Be? Part of the DoD C4 & ISR Architecture From DCGS-A ORD Para 1.5.5. Organizational Description JTF XXXX / XXX / XX JIC UE DCGS-A “Nodes” in Architecture: • Fixed DCGS-A – Units of Employment Home Station Operations Centers enhance reach “heavy lifting”. Provide tailored products to the force Manpower shared between fixed and deployable segments • Mobile DCGS-A – UE & UA BICC Deployable segments tailorable and scaleable to the mission. Ground control system for Prophet, Aerial Common Sensor and select UAV – operates on-the-move UE UA Link to sensors—mud to space • Embedded DCGS-A – SoftwareApplications embedded in FCS--tailorable to platform role/function/need and provide common tools in BCS for ISR tasking, fusing data, collaboration, and visualization in units – operates on-the-move II / X (BICC) UA 11

  12. SOF SOF ACS CIA Knowledge Centers Global Hawk DHS ER / MP Apache Prophet SIGINT MP DCGS-AF CI U2R JSTARS RJ MMR UGS ARV R&SV DCGS-N Interoperability--“Mud to Space”From DoD DCGS CRD; DCGS-A ORD Interoperability KPP, IER Matrix National NGOs Open Sources Allied Sensors DCGS Theater DCGS-Army DCGS-A ACC JTF/UE DCGS-A Theater, JTF & UE… Fixed DCGS-MC Home Station Operations Center UA Battalion Company MEF Squad/ platoon Mobile UA UE & UA… Soldier DCGS-A Net Fires UA… NCC Embedded BCOTM

  13. Fusion-- Building the Red Piece of the COP From DCGS-A ORD Fusion KPP, Para 4.2.2, & 1.5.2 UE Data must be fused at multiple echelons. Automated Organization and Correlation Bde COP Plus…Information from UE, JTF, Theater, National Bn COP Report count based on MAPEX results using Caspian Sea Scenario 170K+ Reports/Hour Co COP 56K+ Reports/Hour • Complexity increases the higher the echelon • Proliferation of sensors at lower echelons • Resolution of conflicting data/reports • Cumulative effects of reporting • Therefore…Not all data should go into the COP • Clarity and accuracy of the Red COP requires reporting criteria (METT-TC • dependent), profiles and filters—DCGS-A provides the capability C o m p l e x i t y 18K+ Reports/Hour PLT COP 6K+ Reports/Hour Reports generated from FCS EO/IR and COMINT Sensors only. Add MASINT sensors and reporting at UA goes to @ 600K/hour. 13

  14. The Path Ahead—DCGS-A “Spirals” Spiral 1 Fixed Site (FY03) Spiral 2 Interim UE Mobile (FY04) Spiral 3 Interim UE Mobile (FY05) • III Corps, Fort Hood • Reduce Forward Footprint • Improve Interoperability • Improve Information Sharing XVIII Abn Corps, Fort Bragg • Reduce Forward Footprint • Improve Interoperability • Improve information sharing HUMINT MASINT 513th MI BDE Fort Gordon • Use common COTS/GOTS/NDI Work Stations • Use proven current force software applications TES-F (SIGINT/IMINT) Commander Commander CHIMS (HUMINT) Block II ACE (ALL SOURCE INTEL) TES-M (SIGINT/IMINT) Collaborative Data Environment Collaborative Data Environment Battle Captains & Analysts Block II ACE (ALL SOURCE INTEL) IMINT SIGINT CHIMS (HUMINT) GRCS IPF (SIGINT) GRIFN (SIGINT) 513th MI BDE Spiral 1 501st MI BDE Spiral 1 66th MI BDE Spiral 1 525th MI BDE Spiral 2 504th MI BDE Spiral 3 ACS Spiral 4 FCS (UA) Spiral 5 Site: Base Conf SIGINT IMINT MASINT HUMINT Fusion Cell Operational Date TBD TBD TBD NA TBD TBD TBD Jan 04 TBD Aug 03 TBD Nov 03 4QFY04 3QFY05 2QFY06 2Q07

  15. Key Events Schedule to 2012 2003 • Requirements Analysis Study Completed • ORD Army Requirements Oversight Council (AROC) Approved • First (Spiral 1) Fixed Facilities Established at Fort Gordon & Korea 2004 • ORD for JROC Approval • Fixed Facilities Established in Europe • Current force enhancement (Spiral 2), Fort Bragg / XVIII ABN Corps • Milestone ‘B’ Decision 2005 • Digitized force enhancement (Spiral 3), Fort Hood / III Corps • “DIB” Implementation 2006 • Aerial Common Sensor (ACS) (Spiral 4) Ground Station • Accelerate Capabilities into Current Force 2007 • Embedded Capability in Future Combat System (FCS) (Spiral 5) • Milestone ‘C’ 2010 • Objective DCGS-A Initial Operational Capability (IOC) per ORD 2012 • Objective DCGS-A Full Operational Capability (FOC)

  16. DCGS-A End State—EnableDecision Superiority GIG ISR Sensor Grid JTF UE JIC UA • Link and leverage sensors for Ground Commanders--“Mud to Space” • Reach--“FCS to Intel Agency” • Army Fusion System • Provides Red, Grey, Wx, Terrain Information for the COP & Intel Running Estimate • Sensor Management System • at all levels—FCS and above • Enables “See First” and supports “Understand First”… for Battle Command DCGS-A C4 & ISR Communications & See First Red Understand First TAI NAI Blue Act First Battlespace Characterization NGO PVO Terrain, Weather, Grey Computers Finish Decisively …at the point of Decision 16

  17. Distributed Common Ground System – Army (DCGS-A) QUESTIONS? Colonel Steve Bond U.S. Army TSM DCGS-A/Joint STARS Phone: 520-533-2480 E-mail: steve.bond@hua.army.mil 17

More Related