Forum
Battle Damage
S
ince the dawn of organized forces, assessing battle damage became
combat, assessing the effects correspondingly more complicated.
of actions against enemies The difficulty of accurate damage
has played a key role in the assessment became evident during Op-
prosecution and outcome of battles, eration Desert Storm, where the rapid
campaigns, and ultimately wars. Early tempo and large scale of combined
assessments were simple because battles operations exceeded the capabilities
were confined in space and time, so a of the traditional ad hoc approach to
commander could observe all devel- battle damage assessment (BDA). In its
opments as they occurred. As combat Final Report to Congress, Conduct of the
became more complex, especially with Persian Gulf War, 1992, the Department
the increased use of joint and combined of Defense (DOD) cited this problem as
a major lesson learned and identified
BDA as a failure: “The number-one
Colonel James G. Diehl, USA, is a joint test director, Joint Battle Damage Assess- DOD finding concerning BDA was that
ment Joint Test and Evaluation Center. Charles E. Sloan is a senior military analyst it was slow and inadequate.” Although
with Computer Sciences Corporation. technology has evolved since the first
Public reporting burden for the collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering and
maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information,
including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, Arlington
VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of information if it
does not display a currently valid OMB control number.
14. ABSTRACT
16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF 18. NUMBER 19a. NAME OF
ABSTRACT OF PAGES RESPONSIBLE PERSON
a. REPORT b. ABSTRACT c. THIS PAGE Same as 6
unclassified unclassified unclassified Report (SAR)
Gulf War, the assessment mission dur- processes and test the JBDA-developed Improved Interoperability
ing both Operations Enduring Freedom enhancements applied to those base- Initial analysis of BDA data high-
and Iraqi Freedom was again overrun line processes. Although the primary lighted several trends in joint C 4 ISR in-
by the rapid operations tempo and test venue was Exercise Ulchi Focus Lens teroperability to which enhancements
endured much of the same criticism it (UFL ’02 and ’03), the program also were applied:
received in the previous decade. collected and analyzed BDA data dur-
■ failure to feed immediate poststrike
To address chronic BDA process ing Enduring Freedom and Iraqi Freedom.
BDA information to air and ground com-
issues, the Office of the Director, Stra- Data collection consisted of manual ponent decisionmakers (especially against
tegic and Tactical Systems, chartered observation by collectors and augmen- time-sensitive/mobile targets)
the Joint Battle Damage Assessment tee subject matter experts at key the- ■ lack of BDA information cross-flow
(JBDA) Joint Test and Evaluation Pro- ater nodes, semi-automated capture among joint and service component head-
Forum
gram in August 2000. The program of planning and execution products, quarters
subsequently fell under the cognizance and automated capture of command, ■ limited theater visibility of damage
Forum
Satellite image
of Baghdad prior
Space Imaging
to Operation Iraqi
Freedom
CAOC Hardened Theater Air Control locations. This amounted to a needle JBDA also discovered similar prob-
Center combat operations execution in a haystack for intelligence analysts lems in getting the overall ground ma-
floor. JBDA achieved this by replacing and operators seeking assessment in- neuver BDA status from the Ground
a manual CUWTF targeting coordi- formation. Furthermore, the existence Component Command–Combined
nation process, hampered by limited of component-specific systems such Analysis and Control Center (GCC–
stovepipe reporting, with an ADOCS as ADOCS, Interim Targeting Solution CACC) PERL-based Web server. It com-
network approach that provided near- (ITS), and All-Source Analysis System pletely rewrote the center’s BDA Web
real-time reporting of SOF target detec- (ASAS) negated the possibility of a sin- page to account for enhanced TTP for
tion and strike results to all joint the- gle database management system for managing maneuver information, pro-
ater ADOCS nodes. This proved to be joint BDA. viding USFK with a modern, coher-
a low-cost, high-payoff enhancement The answer was to establish a ently coded Web capability for tracking
and was demonstrated during live op- single repository of assessment infor- maneuver BDA results.
erations in Exercise Foal Eagle ’03. This mation by developing a Web-enabled While observing the dissemina-
enhancement is now permanently in- database to accomplish remote query tion of BDA-related products on the
tegrated into CUWTF operations. and storage of data read from ADOCS, USFK theater dissemination Web site,
ITS, and ASAS. That allows users to see JBDA noted delays of up to 4 hours in
Theater-wide Visibility specific target information such as the posting damage assessment and battle
of BDA Status identification number, name, next mis- rhythm-related products. The answer
Joint Battle Damage Assessment sion number scheduled against it, hit or was to develop the theater intelligence
discovered that the primary reason no hit status, BDA, re-attack recommen- dissemination battle-rhythm support
theater operations and intelligence dation, and intelligence, surveillance, Web site, another low-cost, high-payoff
personnel did not have up-to-date situ- and reconnaissance (ISR) collections solution that provides one-stop shop-
ational awareness on the overall BDA status. This solution is currently in ping for damage assessment and other
mission was that parts of BDA resided place within U.S. Forces Korea (USFK) intelligence-related information.
in numerous unconnected or unlinked and is being incorporated into the joint
targeting toolbox.
Improved Joint TTP the federated partners to post, query, personnel to ensure that USMTF 2000
Closely associated with the C ISR4 and collaborate on damage assessment messages were generated and valida-
interoperability problems were trends data in support of CFC operations. This tion software was installed on all C 4 I
pointing to outdated or nonexistent enhancement provided USFK with im- and simulation systems. JBDA also
joint BDA tactics, techniques, and mediate connectivity to their feder- conducted a robust campaign to edu-
procedures. JBDA developed enhance- ated BDA counterparts and allowed cate CFC and ACC active-duty and
ments targeted at the following defi- warfighters to view and collaborate on civilian operations, intelligence, and
ciencies: important information with up-to-the- simulation support personnel on the
minute timeliness. importance of the USMTF program and
■ insufficient mobile/maneuver BDA
Procedures and exercise scripting directives to utilize it.
TTP
■ inadequate poststrike reporting/
inputs for multiple intelligence sources JBDA found that mission report-
Forum
processing TTP (multi-INTS) BDA. During UFL ’02, ing and processing was not only an
■ overreliance on imagery intelligence JBDA observed that intelligence ana- exercise simulation problem, but that
(IMINT) for BDA lysts relied almost exclusively on im- it also was, and still is, a real-world
■ minimal involvement of federated agery intelligence (IMINT) to assess problem. Observations from Enduring
partners BDA, even though the exercise simula- Freedom and Iraqi Freedom, along with
■ no single BDA procedures/checklists tion systems supporting UFL were ca- interviews of U.S. Central Command
publication. pable of generating reports from over (CENTCOM) BDA cell chiefs and after-
New maneuver and ground mobile 50 non-IMINT collection assets. This action lessons learned, all indicated
target TTP. Observations made in the included theater and national signals that mission reporting was plagued
GCC–CACC during UFL ’02 pointed to by nonstandard report-
areas within the maneuver and ground observations from Enduring Freedom ing formats employed
mobile target (M&GMT) BDA process by service, joint com-
in need of further refinement, includ- and Iraqi Freedom indicated that mission ponent, and headquar-
ing enemy unit association, report sub- reporting was plagued by nonstandard ters-level intelligence
mittal procedures, locations of appli- cells. Since Iraqi Free-
cable information, and specific battle
reporting formats dom, JBDA has worked
rhythm requirements. closely with the Air
Joint BDA targeted these deficien- intelligence assets, other electronic Force Combat Assessment Working
cies by developing a detailed guide intelligence producers, and nontradi- Group (CAWG), the Joint Chiefs of
explaining the Combined Forces Com- tional, technically derived intelligence Staff lead agent for joint combat as-
mand (CFC) M&GMT BDA TTP that such as measurement and signature in- sessment solutions, to develop a per-
incorporated improvements in analy- telligence. JBDA focused on increasing manent approach to mission report-
sis methods, reporting requirements, interaction between the training audi- ing standardization. More recently,
and the portrayal and coordination of ence and the USFK exercise modeling U.S. Joint Forces Command (J–7/8)
M&GMT BDA. These changes were also and simulation coordinators to provide and JBDA have teamed to forward a
incorporated into the JBDA-enhanced more timely and relevant raw multi- transitional change proposal contain-
GCC–CACC BDA Web server. INTS data to the intelligence analysts ing poststrike reporting enhancements
Improved BDA template and com- responsible for producing BDA. to the Joint Requirements Oversight
munications for federated BDA sites. Fed- Standardize and facilitate flow of Council for approval.
erated BDA is a process in which other poststrike reports to BDA cells. During
joint and national agencies around the UFL ’02, JBDA noted that mission re- Improved Joint BDA Training
world perform specific BDA functions ports were not flowing properly from Joint BDA documented a chronic
in support of USFK. These functions the Air Simulation Cell to the Air Com- problem with untrained or unquali-
usually pertain to some particular ex- ponent Command (ACC) BDA Cell fied augmentees arriving in the USFK
pertise resident in the BDA federated targeting database. The primary reason theater to perform BDA cell functions
partners. During UFL ’02, JBDA data was that the simulation models and during UFL exercises. Worse, the same
collectors noted extensive delays in the UFL ’02 player databases were con- problem plagued the CENTCOM BDA
exchanging BDA-related products be- figured to process different versions mission throughout Enduring Freedom
tween USFK and its off-peninsula BDA of U.S. message text format (USMTF) and Iraqi Freedom, even though the
federated partners. 1998 and 2000. The result was a 24- shortfall was thoroughly documented.
The solution was to install Global hour backlog of messages and failure The problem of untrained augmentees
Command and Control System–Korea of the information to reach other com- remained a lesson not learned from
terminals at each federated partner site ponents and federated partners until a Desert Storm, Kosovo, and even Endur-
and optimize the federated template for workaround was devised. ing Freedom. JBDA developed several
BDA information exchange. This made In an attempt to resolve this sit- enhancements to improve this issue.
it possible for the USFK BDA cell and uation, the JBDA staff worked with
USMTF users, simulation center con-
tractors, and USMTF program office
Forum
tle historical evidence of any formal at-
tempt to fix it or to simply agree what
it is. Indeed, joint organizations such