Afghanistan: CJTF-76 joint fires board in OEF 04-06.

You are assigned to the fires and effects cell (FEC) at the combined joint task force (CJTF) level as a fire support officer (FSO). There are two regional commands and a task force (TF) within your area of responsibility (AOR), each with its own enemy situation, unique capabilities and constraints.

[ILLUSTRATION OMITTED]

In Regional Command I, there are two significant combat operations currently in planning and several humanitarian assistance (HA) missions underway to prepare for the coming winter. Recently, there has been an increase in improvised explosive devices (IEDs) discovered or detonated.

In Regional Command 2, one significant combat operation is underway and another is in planning. Reports indicate a strong possibility that enemy indirect fire attacks will occur within the next 48 hours.

Finally, in TF Alpha, border security remains the top priority while the rainy season has brought major flooding to the region, requiring an immediate humanitarian relief mission.

The CJTF has increased air support throughout the area to resource an increase in the operational tempo (OPTEMPO); several close air support (CAS) platforms have scheduled maintenance within the next seven days. Your task is to distribute the limited theater assets available to best support each regional command and TF while complying with the CJTF commander's intent.

In March 2005, the US Army Southern European Task Force (Airborne) (USASETF-ABN) deployed to Afghanistan as the CJTF-76 Headquarters in support of Operation Enduring Freedom (OEF) 04-06. After its relief-in-place with the 25th Infantry Division (Light), the USASETAF-ABN/CJTF-76 Chief of Staff directed the joint FEC (JFEC) to revise the staff system that prioritizes, synchronizes and gains approval for lethal and nonlethal operational fires, a seemingly daunting task at the CJTF level.

The JFEC quickly learned that each regional command (or brigade combat team, BCT) and TF had unique needs while the JFEC, the information operations (IO) cell and the J2 collection management division on the CJTF staff each had its own methods for providing regional commands operational resources. The JFEC knew that the diverse cells must work together to synchronize effects in accordance with the commander's intent. So, the CJTF-76 JFEC developed the daily joint fires board (JFB) to synchronize the efforts of these cells in OEF.

This article describes the OEF JFB, explains format and procedures and recommends its use to other CJTFs or divisions.

JFB Composition and Intent. The CJTF-76 JFB began in March 2005 with a daily face-to-face morning meeting with the chief of staff, JFEC chief and representatives from J2 collection management, the air support operations center (ASOC) and the electronic warfare officer (EWO). Over time, the board evolved to include other cells and the regional commands and TFs and took place in a "virtual" conference room within the information workspace (IWS) software used in OEF. (See Figure 1 for the JFB participants.) This allows all elements to take the briefing from their desktops and includes distant stations, providing a collaborative information environment for personnel at multiple sites.

Each briefer supplies PowerPoint slides for display in the conference room. All participants in the virtual meeting can address the other attendees in the session. The ability to communicate within the virtual environment facilitates discussions and usually allows most issues to be resolved quickly.

The JFB's intent is to ensure unity of effort and synchronize kinetic and non-kinetic fires within the combined joint operations area (CJOA). The chief of staff chairs the board and provides guidance and approval to the JFB participants.

The JFB focuses on two air tasking order (ATO) days into the future and works backward to the current ATO day. This allows the regional commands, TFs and the CJTF staff sections to better forecast requirements, ensure synchronization and unity of effort, and identify in advance any potential conflicts that may develop with pending operations.

JFB Process. The joint operations center (JOC) FSO opens the meeting with a brief introduction that includes a review of the day's agenda. The JFB's first briefer is the CJ3 current operations officer, who discusses level 1 and 2 unit operations in execution or scheduled to begin within the next two ATO days. A level 1 operation means there is the possibility of contact with the enemy and a limited chance of political or economic implications and requires CJTF-76 resourcing. A level 2 operation is a deliberate operation (day or night) where contact is expected and political, economic or strategic implications are anticipated. A level 2 operation requires CJTF resourcing and is more complex than a level 1 operation. Only levels 1 and 2 operations are briefed in the JFB.

The current operations officer describes these operations by day and by regional command or TF within each day. His update allows the OEF joint fires community to recognize any requirement to focus operational-level resources in advance. If an operation also involves pre-planned air strikes, the JFEC and the ASOC can ascertain any unique requirements for that operation.

Next, the JOC FSO recaps the last 24-hours of EW coverage. Specifically, the FSO discusses any EW missions not supported due to maintenance, fuel issues or deconfliction problems. This allows the regional commands and TFs to make better decisions about operations and convoys for the current day. Many units plan their movements and operations with the expectation that the EW plan was flown as scheduled. In some instances, this is a critical factor that can change the overall risk assessment for an operation if the EW mission is not flown as scheduled.

The CAS synchronization briefing shows air support requests (ASRs) for a three-day period--the current day and the next two days--in an easy-to-read comprehensive table. Typically, one slide for each regional command and TF and one for the CJTF captures all the ASR submissions for the period. See Figure 2 on Page 35 for a sample CAS synchronization matrix for Regional Command 1.

[FIGURE 3 OMITTED]

The FSO confirms with each regional command or TF that the number and the details are correct for each ASR submitted for the next two days. Because the JFB focuses two days in the future, the ASRs in the last column of the CAS synchronization matrix are briefed in two other segments of the meeting: the ASR/intelligence, surveillance and reconnaissance (ISR) tracker section (a timeline format) and in the ISR/CAS coverage section (map format). Any changes or unsupported ASRs for the current day also are briefed to verify all regional commands and TFs have the most current picture of the ATO.

Aircraft maintenance days are a part of continuous combat operations and have a considerable impact on CAS and ISR planning. The intent of briefing the monthly maintenance calendar is to minimize the effects of aircraft maintenance on operations within the CJOA by making all regional commands and TFs aware of the limitations on air support for their operations. As a result, units may adjust their plans to ensure maximum coverage. It also is possible to move some maintenance days earlier or later to meet tactical requirements identified and coordinated in advance.

The staff weather officer's (SWO's) part of the JFB has been very useful, especially through the winter months. Because weather affects rotary-wing, fixed-wing and ISR platforms, identifying potential weather implications in advance significantly aids the joint fires planning process. The SWO also briefs from the current ATO day through the ATO-plus-two days, focusing on the latter.

[ILLUSTRATION OMITTED]

A representative from the CJ2 collection management division, usually the collection manager, discusses the theater ISR assets the CJTF has allocated and where they are scheduled to fly two days out. He uses two slides for this portion, one for each regional command. If the chief of staff has a change in an ISR priority during the JFB, the collection manager gives that guidance to the Central Command (CENTCOM) Joint Collection Management Board (JCMB) to secure the collection assets.

The EWO follows the CJ2 collection manager. He briefs one slide showing scheduled EW support two days out. He gives a quick overview of the areas to be supported and at what time.

During the past year, deconfliction of EW missions has gone from being a difficult challenge to a manageable part of the joint fires daily battle rhythm. This is largely due to efforts to increase knowledge of EW at the CJTF level and below as well as regular discussions on EW at the regional command and TF levels, often during a JFB session. Any units struggling with deconfliction, wanting to request adjusted time lines or needing cancellations, have a forum in the JFB to discuss these issues. This gives all the regional commands and TFs immediate feedback on current issues and facilitates answers to those issues.

The JOC FSO follows the EWO and briefs the ASR/ISR tracker. This includes two slides, one each for the first and final 12 hours of the ATO day being discussed. These slides depict the times for the scheduled ISR platforms and the unit being supported by that platform.

Given the limited CAS assets in theater, graphically depicting ASRs from each unit on a timeline allows the CJTF staff to easily identify any need to request air support above normal levels (called "steady-state plus" air support or "air support surge"). The staff also can identify ASRs that might be unsupported or require a time change to be supported.

As the discussion moves toward the current day, the JFB can track late or immediate ASRs and discuss with the fire support elements (FSEs) why a particular mission may go unsupported. The JFB also gives participants the chance to discuss specific concerns about ASR submissions.

This daily forum for discussion with each regional command and TF FSE has dramatically improved communications among the fires elements throughout the CJOA.

Like other JFB briefings, the IO briefing covers a three-day period, again focusing on the ATO-plus-two days. Thus the chief of staff can verify that IO is synchronized with lethal operational fires and ISR. It also allows him to ensure that regional command and TF operations are properly resourced. See Figure 3 for a sample CJTF-76 IO campaign for Regional Command 1.

The JFB not only is a tool for coordinating assets, but also is the forum for gaining the CJTF command group's approval (via the chief of staff) for the proposed prioritization and synchronization of lethal and nonlethal fires. As such, the JFB validates the distribution of operational assets two days in advance in accordance with the commander's intent.

The chief of staff's approval permits the JFEC to submit its ASRs to the battlefield coordination detachment (BCD) at the combined air operations center (CAOC). The chief of staff's approval also allows the collection manager to finalize his plans with the JCMB and the IO cell to proceed with the plans.

Synchronizing kinetic and non-kinetic operational fires between key cells is critical to success on a nonlinear, adaptive battlefield. The OEF 04-06 JFB has been a useful tool to coordinate such effects at the CJTF level.

We recommend that units preparing to deploy consider the OEF JFB concept and adjust it to meet their tactical and operational needs.

Captain Daniel C. DiNicola is a Fire Support Officer (FSO) in the US Army Southern European Task Force (Airborne) (USASETF-ABN), Vicenza, Italy. He served as the FSO-Night for Combined Joint Task Force-76 (CJTF-76) during Operation Enduring Freedom (OEF) from May 2005 to February 2006. He was previously assigned to 4th Battalion, 1st Field Artillery (4-1 FA), 3rd Brigade, 1st Armored Division (1st AD), Fort Riley, Kansas, as an Assistant Battalion Operations Officer, Platoon Leader, Fire Direction Officer (FDO) and FSO. Also in the 1st AD, he was the Targeting Officer for 2-70 AR, 3rd Brigade Combat Team (3rd BCT) during Operation Iraqi Freedom (OIF) in 2003.

Captain Leo F. Brennan III is an FSO in USASETF-ABN. He served as the FSO-Day for CJTF-76 during OEF from March 2005 to February 2006. Previously he was the Operations Officer for the Secretary Combined Joint Staff for US Forces Korea (USFK). He also served as Support Platoon Leader, FSO and Executive Officer (XO) for Charlie Battery, 1-12 FA, 17th FA Brigade, Fort Sill, Oklahoma.

Captain Bruce J. Carter is on the Division Artillery Staff, 1st AD, Baumholder, Germany. He served as the Joint Operations Center (JOC) Battle Major-Day for CJTF-76 during OEF from March 2005 to February 2006. Also in the 1st AD, he served with 4-27 FA as a Task Force FSO for 1-6 IN, where he deployed in support of operations in Kosovo and as a Liaison Officer. He commanded Headquarters and Headquarters Service Battery, 1-94 FA, 1st AD during OIF from 2003 to 2004.

By Captains Daniel C. DiNicola, Leo F. Brennan III and Bruce J. Carter

* Chief of Staff
* Chief, Joint Fires and Effects Cell (JFEC)
* Chief, CJ3 Current Operations
* Chief, CJ2 Collection Management
* Director, Air Support Operations Center (ASOC)
* Staff Weather Officer (SWO)
* Electronic Warfare Officer (EWO)
* Information Operations (IO) Officer
* FSO, JOC
* Fires Rep, Regional Command 1
* Fires Rep, Regional Command 2
* Rep, Task Force (TF) Alpha Fire Support Element (FSE)
* Rep, TF Bravo FSE
* Rep, Aviation Brigade FSE

Figure 1: Participants in the Combined Joint Task Force 76 (CJTF-76)
Joint Fires Board (JFB) in Operation Enduring Freedom (OEF) 04-06. The
chief of staff chairs the daily JFB and provides guidance while the fire
support officer (FSO) from the joint operations center (JOC) runs the
meeting.

All times
are Zulu
Current
as of 09   ATO: LB              ATO: LC              ATO: LD
Aug 05     (09/0300-10/0259)    (10/0300-11/0259)    (11/0300-12/0259)

Regional   ZAS601; (1000-1130)  ZAS702; (0130-0259)  ZAS601; (1000-1200)
Command 2  Armed Recce IVO      Armed Recce IVO N.   Armed Recce IVO
           Khost ISO Op Viper   Paktika              Khost ISO Op Cobra
           ZAS602; (1400-1630)  ZAS901; (0330-0530)  ZAS602; (1200-1400)
           Armed Recce IVO      Armed Recce IVO      Armed Recce IVO
           Khost ISO Op Viper   Nangahar ISO Op      Khost ISO Op Cobra
           ZAS903; (0330-0530)  Dragon               ZAS901; (0630-0930)
           Armed Recce IVO      ZAS902; (0530-0700)  Armed Recce IVO
           Nangahar ISO Op      Armed Recce IVO      Nangahar ISO Op
           Dragon               Nangahar ISO Op      Dragon
           ZAS904; (0530-0700)  Dragon               ZAS902; (0930-1130)
           Armed Recce IVO      ZAW701; (1600-0100)  Armed Recce IVO
           Nangahar ISO Op      Force Protection     Nangahar ISO Op
           Dragon               IVO Paktika          Dragon
           ZAW701; (2330-2350)                       ZAW701; (1600-0100)
           Force Protection                          Force Protection
           IVO Paktika                               IVO Paktika
           ZAW901; (0300-0400)                       ZAW901; (0300-0700)
           Force Protection                          Force Protection
           IVO Nangahar ISO Op                       IVO Nangahar ISO Op
           Dragon                                    Dragon
                                                     ZAW902; (1100-1400)
                                                     Force Protection
                                                     IVO Nangahar ISO Op
                                                     Dragon

Legend:
IVO = In the Vicinity of
ISO = In Support of
Op = Operation
Recce = Reconnaissance

Figure 2: CJTF-76 Close Air Support (CAS) Synchronization Matrix. "LB"
identifies the current day's air tasking order (ATO), "LC" the ATO one
day out and "LD" two days out.