Lessons Learned From Developing the ABCS 6.4 Solution

Abstract

In response to Army decisions during the 1980s to develop increasingly lethal platforms aided by automation, several automated command and control (C2) systems were developed to support various battlefield functional areas. These C2 systems were successful during Operations Enduring Freedom and Iraqi Freedom; however, each system was evolving independently of the others. In 2003, after the Good Enough Army Battle Command Systems (ABCS) decision by Army leaders, Program Executive Office Command, Control, and Communications Tactical initiated a concerted battle command integration effort. The Army designated ABCS version 6.4 software as the standard version to field. This article reviews lessons learned from the systems engineering and integration of ABCS 6.4, moving from stovepipe development and testing to an integrated and interoperable System-of-Systems, leading to operational evaluation preparation and fielding.

Open PDF

Document Details

Document Type
Technical Report
Publication Date
Jan 01, 2005
Accession Number
ADA441759

Entities

People

  • Harold Greene
  • Robert Mendoza

Organizations

  • Defense Acquisition University

Tags

Communities of Interest

  • C4I
  • Electronic Warfare
  • Engineered Resilient Systems
  • Space
  • Weapons Technologies

DTIC Thesaurus Topics

  • Artillery
  • Business Administration
  • Command And Control
  • Command And Control Systems
  • Computer Programs
  • Computer Science
  • Control Systems
  • Electronic Warfare
  • Engineering
  • Engineers
  • Iraqi-War
  • Lessons Learned
  • Network Architecture
  • Systems Engineering
  • Test And Evaluation
  • War Colleges
  • Warfare

Fields of Study

  • Computer science

Readers

  • Defense Acquisition Program Management
  • Military and Counterinsurgency Studies.
  • Software Engineering.

Technology Areas

  • Fully Networked C3
  • Fully Networked C3 - Command and Control