Joint Operational Fires
A 1st BCD Perspective from
Operation Iraqi Freedom
Field Artillery and Joint Fires Conference
October 2003
Purpose
Purpose
• Provide unclassified insights into the good
and bad of joint operational fires during OIF
(MCO) from 1st BCD perspective
• Identify lessons learned for the Army and
Joint fires community
Agenda
Agenda
• Background
• The Good
• The Bad with recommendations to improve…
– Service and joint C4I functionality
– Training Army leaders to function more effectively
in joint/ operational fires environment
– The role/ capability of Battlefield Coordination
Detachments
• Conclusion
Background
Background
•
•
•
•
•
•
BCD “101” (-)
CFACC’s 5 “Fights”
Theater Air-Ground System (TAGS)
Air Force Operational distances
Complex Airspace
KI CAS CONOP
BCD MISSION
MISSION
BCD
• REPRESENT THE ARMY FORCES (ARFOR)
COMMANDER IN THE JOINT/COMBINED AIR
OPERATIONS CENTER (JAOC/CAOC).
• FACILITATE THE SYNCHRONIZATION OF AIR
OPERATIONS WITH ARMY GROUND
OPERATIONS THROUGH THE COORDINATION
OF AIR SUPPORT AND THE EXCHANGE OF
OPERATIONAL AND INTELLIGENCE
INFORMATION.
BATTLEFIELD COORDINATION
COORDINATION
BATTLEFIELD
DETACHMENTS
DETACHMENTS
19th
19th BCD,
BCD, RAMSTEIN,
RAMSTEIN, GE
GE
EUCOM
EUCOM
2ND
2ND BCD
BCD (RC),
(RC), HURLBURT
HURLBURT
PACOM
PACOM
1st
1st BCD,
BCD, FT
FT BRAGG,
BRAGG, NC
NC
SWA,
SWA, CONTINGENCIES,
CONTINGENCIES,
CENTCOM,
CENTCOM, SOUTHCOM,
SOUTHCOM,
JFCOM,
JFCOM, ETC
ETC
3rd
3rd BCD,
BCD, OSAN,
OSAN, ROK
ROK
KOREA
KOREA
BCD ORGANIZATION
•COL,FA
FACommander
Commander
•COL,
•CombinedArms
ArmsStaff
Staff
•Combined
•Mile-wide/ /Inch
InchDeep
Deep
•Mile-wide
HQ
Element
PLANS
SECT
OPNS
SECT
INTELL
SECT
32DAAMDC
AAMDC
32D
providedthe
the
provided
ADALiaison
Liaison
ADA
ADA
SECT
AIRSPACE
MGMT
SECT
16 x Officers
2 x Warrant Officers
22 x Enlisted
40 Total PAX
Augmentedwith
with22Marines
Marines
Augmented
and22UK
UKofficers
officersfor
forOIF
OIF
and
AIRLIFT
SECT
CFACC”S
CFACC”S
“Fights”
55 “Fights”
Support JSOTF-N (Green line)
Counter TBM in West
TF-20?
Counter Air
Strategic Targets
•Apportionment
•Apportionment
•WOE
•WOE
•DMPISortie
SortieEquivalents
Equivalents
•DMPI
•Allocation
•Allocation
Support CFLCC (Counterland)
Theater Air
Air Ground
Ground System
System (partial)
(partial)
Theater
CENTCOM
CFACC
CAOC
CAOC
SOLE
SOLE
NALE
NALE
MARLO
MARLO
CFLCC
TOC
TOC
ISR
OPS / PLANS
TF
TF20
20
LNO
LNO
BCD
BCD
DEEP
ASRs ATTACK
AIRS
PACE
ATO
ATO
WINGS
WINGS
AIRLIFT
GLOs
GLOs
G2
G3
G4
G4
XXX
XXX
II MEF
MEF
CP
CP
FSCC
FSCC DASC
DASC
DASC-A
DASC-A
XX
XX
ACE
ACE
CP
CP
TACC
TACC TADC
TADC
DOCC
XXX
XXX
V
V CORPS
CORPS
CP
CP
FSE
FSE
A2C2
A2C2
TACP
TACP ASOC
ASOC
OIF AF
AF Operational
Operational Distances
Distances
OIF
Anchorage, AK
Fairford, UK
Watertown, SD
Incirlik, TU
Salt Lake City, UT
Crete
Denver, CO
Med Carrier
Sioux City, IO
Diyabakir, TU
Alliance, NE
Cyprus
St Louis, MI
Baghdad, IZ
Whichita, KS
H-5, JO
Dallas, TX
Tabuk, KSA
Chattanooga,
TN
Al Jaber, KU
Albany, GA
Dahran,
KSA
Gulf of Mexico
Jeddah, KSA
Gulf of
Mexico
PSAB,
KSA
Moody AFB,
GA
Shaikh Isa, BA
Ft Stewart, GA
Al Udeid, QA
Cape Canaveral,
FL
Al Dhafra, UAE
Grand Bahama
Seeb, OM
Havana, Cuba
Thumrait, OM
Moura, Brazil
Deigo Garcia, UK
Complex Airspace
Airspace (ACO
(ACO M)
M)
Complex
•UAV Blanket
•Driveways
•Aerial Refueling
•CAS Areas
•U2 Track
•Kuwait ATC Zone
•EP-3, P-3 SIGINT Track
ATACMS
PAH
BAGHDAD
V CORPS DEEP
STRIKE AREA
TLAM
BREAKOUT
AREA
Complex Airspace
Airspace (ACO
(ACO YY- LOW
LOW LEVEL)
LEVEL)
Complex
•INTERCORPS BNDRY
•FSCL
•ATACMS PAH
•LSA BUSHMASTER
CLASS D
•MAINT TEST FLT ROZ
•HELO ROUTES
•SOF HELO AERIAL
REFUEL AREA
•CFLCC WEST BNDRY
MEF SECTOR
KI CAS
CAS
KI
AWACS
U2
FSCL
TACP
1
2
3
1
2
3
4
5
6
4
5
6
7
8
9
7
8
9
1
2
3
4
5
6
7
8
9
XXX
ASOC
FSCL
KI CAS
CAS CONOP
CONOP Issues
Issues
KI
•
•
•
•
Theater TTP- not doctrine
Airspace, FSCM and or Target
Need to add to TTP to better use C4I
Need to improve C4I to leverage
– KB COP and in AFATDS
– Rapid dissemination to the ground and the
cockpit
• Good TTP for mobile targeting—implications
for our ASR system
The “Good”
“Good”
The
“There were episodes in the fight when operational maneuver
caused the enemy to react; when the enemy reacted it allowed us
to employ joint fires against him which, in turn, allowed our
operational maneuver to be more successful.
Our joint fires were very effective. We had CAS in abundance.
First, the Army should give the Air Force credit for being as good
as it is. We’ve got the best Air Force in the world.
We’ve got to put a joint context in virtually all our training.”
LTGWallace,
Wallace,CDR,
CDR,VVCorps,
Corps,FA
FAMagazine
Magazine
LTG
Visibility of
of Army
Army operations
operations to
to the
the
Visibility
joint force
force
joint
•
•
•
•
•
Aviation and ATACMS on ATO
Airspace in ACO
Frequency coordination (Counterfire Radars)
Fratricide avoidance in spins
Impact of Blue Force Tracker (BFT)
Mutual operational
operational support
support
Mutual
between the
the Air
Air and
and Land
Land
between
• Air Component provided Land FOM, shaping and
CAS
• Each component provided enablers to the other
–
–
–
–
ISR
C2
SEAD / DEAD
Personnel Recovery
• Land Component integrated air effects into targeting
plan (EFSTs)
• Land provided direct and indirect SEAD- enabled Air
maneuver
• “Mother of all storms”JDAM “Fest”
• Coordinated FSCL and Battlespace (Killbox CONOP)
The Bad:
Bad:
The
Service and
and Joint
Joint C4I
C4I interfaces
interfaces
Service
• Too many partially redundant systems
• Battlefield Damage Assessment (BDA)
• AFATDS- TBMCS Interface
Too many
many partially
partially redundant
redundant systems
systems
Too
System
PLANS
Internal
2 x AFATDS (V. 6.3.1)
Advanced Field Artillery Tactical Data System
(Fire Support)
1
2 x ASAS (V. 4.6.0.1)
All Source Analysis System (Intelligence)
1
3 x ADOCS (V. 8.5.1.24)
Automated Deep Operations Coordination
System
2 x TAIS (V. 8.3)
Tactical Air Integration System
(Air Space)
1 x AMDWS (V 1.1c)
Air Missile Defense Work Station
(Air Defense)
OPS
Internal
ADA
Internal
21 PAX per shift:
1
N/A
43 computer
boxes
SIPR/ NIPR/ JWIC
1 4 “Chats”
N/A
4 “COPS”
N/A
Default: Excel and
PPT!
N/A
1
1
N/A
N/A
10/7
5/3
3/3
3/3
6 X TBMCS (V. 1.1)
Theater Battle Management Core System
4
1
N/A
1
4 x EMT
Effects Management Tool (FS Local Client,
AFATDS Server)
2
1
N/A
1
MIRC (chat)
10
5
3
3
IWS (V. 2.5.1)
Info-Work Space
10
5
3
3
N/A
N/A
N/A
SIPRNET/NIPERNET
N/A
INTEL
Internal
N/A
N/A
C2PC (V. 5.5.7.2)
Command & Control PC
ITS
Interim Targeting Solution
BDA Reporting
Reporting
BDA
•
• Lack of Pilot Reporting and BDA hampered
Targeting Processes
– CFLCC (and CFACC) lacked knowledge of what
targets were hit and what the effects on the target
were (Level 1 BDA)
– Pilot Reports not provided as planes came off
target
– MISREPS several days old
• Standardized language needed in PIREPs so report
is clearly understood
• BDA challenges in effects based operations
BDA Recommendations
Recommendations
BDA
• Discipline the system: reports and format
• Process needs to be in place to standardize PIREPS
and communication flow
• System needs to be devised to transmit WSV rapidly
to intel centers for BDA analysis.
• Accurate MISREPS and Phase I BDA provided NLT
12 Hours after strike.
• Automate phase I BDA by ordnance “death calls”
• Rethink range of Battlefield Damage Indicators that
with phase I BDA could provide better phase II BDA
(functional assessment
TBMCS1.1.1 vv AFATDS
AFATDS 6.3.1a
6.3.1a
TBMCS1.1.1
IRIS
ATO & ACO
TBMCS
AFATDS
Air Support Requests
Battlefield Geometry
Mission Reports
USMTF
MIDB
AODB
Interim Targeting
Solution
ASR Information
Information Flow
Flow
ASR
Messaging
Messaging
versusDatabase
Database
versus
interface
interface
AFATDS
TNL (JIPTL)
MIDB
MID
B
Imp
ort/
Exp
ort
IRIS
670
D
F
MT
S
U
Training
Training
Training
andSOP
SOP
and
and
SOP
WorkWorkWorkaround
around
DMPI
Weaponeering options
Priority
GAT Worksheet
ITS
TWM
ASR Number
ASR Number
ASR Number
Mission Class
Mission Class (AI)
Mission Class (AI)
Mission Type
Mission Type (AI)
Mission Type (AI)
Start Time
Start Time-----------------------------------------------------------------------around
End Time
End Time------------------------------------------------------------------------Target LAT/LONG
Target LAT/LONG
Target LAT/LONG
BE Number/O-Suffix
BE Number/O-Suffix
BE Number/O-Suffix
Unit Identifier Code
Unit Identifier Code
Unit Identifier Code
Facility Name
Facility Name--------------------------------------------------------------------Rationale
Rationale
Rationale
Desired Effects
Desired Effects
Desired Effects
Mission LAT/LONG---------------------------------------------------------------------------------------------------------------------Name U/I Units Manually
Generated
BCD Manual Input in ITS
DMPI (built or generated for UIC)
Air Force TT or Priority (in
numerical order)
CRITICALFOR
FOR
CRITICAL
Duplicates BE /UIC re-entered
MOBILETGTS
TGTS
Automate?
MOBILE
Times added to Desired Effects
Automate?
Messaging
Messaging
versusDatabase
Database
versus
interface
interface
ASR Information
Information Flow
Flow
ASR
IRIS
AODB
USMTF
ATO
PU
SH
MIDB
ATO
TAP (PVT)
ACTIONS
C2 Pairing
Mission Pairing
Tanker pairing
MAAP Tool Kit
ASR Number
ASR Number
ASR Number
Mission Class (AI)
Mission Class (AI)
Mission Class (AI)
Mission
Type
(AI)
Mission Type (AI)
Mission Type (AI)
Target LAT/LONG
Target LAT/LONG
Target LAT/LONG
BE
Number/O-Suffix
or
BE Number/O-Suffix or
BE Number/O-Suffix or
Unit
Identifier
Code
Unit Identifier Code
Unit Identifier Code
Rationale
Rationale
Rationale
Desired
Effects
Desired Effects
Desired Effects
DMPI (built or generated for UIC)
DMPI
DMPI
Priority
(in
numerical
order)
Priority
Priority
Times in Desired Effects
Times in Desired Effects
Times in Desired Effects
Weaponeering
Decision
Weaponeering Data
Weaponeering Data
TOT
Tactical Task---------------------------------------------------------------------------------------------------------------------------------------SCL
Pairs assets to TGTS
ASRNumber
NumberLost
Lost
ASR
Remarks
Implications
if Mission
Implications
forOP
OP
for
Assessment
Assessment
if Mission
planned
toair
air
planned to
space
space
ASR Information
Information Flow
Flow
ASR
WithoutASR
ASR##
Without
ARMYVisibility
Visibility
ARMY
ofCFACC
CFACCeffort
effortLOST
LOST
of
AFATDS
(BCD)
ASR Number
Mission Class
Mission Type
Start
End Time
Target LAT/LONG
BE Number/O-Suffix
Unit Identifier Code
Facility Name
Rationale
Desired Effects
Additional Air INFO
TOT
SCL
Remarks
Mission LAT/LONG
NO
NO
FEEDBACK
BACK
FEED
w/o
w/o
ATOCHANGE
CHANGE
ATO
AFATDS
(DOCC)
AODB
ATO EXECUTION
Mission data
Re-Roles
PIREP
MISREP
AFATDS Data Package
Transfer
AFATDS
(V Corps)
AFATDS
(MEF)
A USMTF TEXT COPY OF ATO and ACO
MESSAGE CAN BE PUSHED
BUT INADEQUATE VIEW/ DISPLAY TOOLS
WOC
Mission data
TO / Landing
MISREP
AFATDS-TBMCS
AFATDS-TBMCS
Recommendations
Recommendations
• IMMEDIATE:
– Build an ASR REQ NO. capability in all mission types in
TBMCS
– Increase ability to write all ASR mission types to MIDB
– Add a target location field to the MIDB that supports
targeting vice intel
– Automate the data entry for ITS/ GAT requirements
• NEAR TERM
– The requirement between all systems should be to
transfer data via relational databases- XML?
– Require all systems in the targeting process to conform
to standardized data base construction rules to allow
ease of data transfer between systems
– All defined and appropriate data points need to transfer
when data packages are transported between systems.
If needed, provide filtering capability to filter data viewed
by specific users
Improve Collective
Collective training
training
Improve
BLUEFLAGS
FLAGS
BLUE
BCTPWFX
WFX
BCTP
g Cycle
n
i
t
e
g
r
a
T
mplete
o
C
t
r
o
p
p
Su
Hi
gh
er
S
Better M&
Fid
eli
ty
Robust and Dynamic
ts
ffec
cE
listi
Rea
C4I
d
l
r
o
l -w
Standardize theater SOPs imulate rea
St
“DIRT”
“DIRT”
CTCs
CTCs
Pro
pe
rJ
oin
tC
on
tex
t
Train as we Fight
Joint
Joint
Exercises
Exercises
Improve Institutional
Institutional
Improve
Training
Training
• Improve USAFAS and CGSC curriculum
– ATO planning cycle and how the Army can interact and integrate
successfully
– Understand how the Air Force generates combat power
•
•
•
•
Concept of flow
Impact of carriers, air refueling, low density high demand assets
Concept of Air Force C2 and controlling agencies
Once resourced, air is flexible in location, less so in time
• Leverage existing AF Schools for personnel slated for Division
and higher operations/ plans staff
– JATOPC: Div and higher FECC folks, AV BDE staff, BCD
– JSSC: Army O5/ O6- D/A CDR, AV BDE CDR, Div / Corps G3
– JFACC Course: ADC (O)/ (M), DIV CDR
Improve Training
Training
Improve
• Rethink mobile targeting process
–
–
–
–
Effects based not sortie or bomb based
Top Down vice Bottom-up
CAS may be less efficient but more effective
Resource targeting effects in geographic areas (killboxes)
during ATO development
•
•
•
•
•
•
ISR
airspace
C2 plan
Delivery system
Logistic support
BDA
– Decide the target during ATO execution
Importance of
of the
the BCD
BCD
Importance
• Located at the nexus of land and air
• Helps bridge the seams
• More important to support for smaller,
modular land force
• Enhances “plug and play” into joint force
BCD Pre-OIF
Pre-OIF Challenges
Challenges
BCD
•
•
•
•
•
Impact of OEF
Manning / end strength
Turn-over
Army vs. Air Force ramp-up
IMPACT of multiple CENTAF CAOCs
Enhance BCD
BCD Capability
Capability
Enhance
es”duates”“graduat
BCD“gra
TrackkBCD
Trac
ASI
FixASI
Fix
131Anot
notcoded
coded
131A
For
For
5UASI?
ASI?
5U
Proponent?
Proponent?
More
More
BCDs?
BCDs?
Trainin
ining:
g:JAT
JATOPC
OPC
Tra
FTU?,
?,
FTU
Manw/
w/
Man
“Right”People
People
“Right”
Training&&System
System
Training
Support:
Support:
FundAJAST
AJAST
Fund
Summary
Summary
• Background
• The Good
• The Bad with recommendations to improve…
– Service and joint C4I functionality
– Training Army leaders to function more effectively
in joint/ operational fires environment
– The role/ capability of Battlefield Coordination
Detachments
QUESTIONS?
QUESTIONS?
Joint Operational Fires
A 1st BCD Perspective from
Operation Iraqi Freedom
Field Artillery and Joint Fires Conference
October 2003