AUTOMATED SYSTEMS B ATTALION

4-24. The MLRS battalion automated command and control systems consist of the fire control system (FCS) at the launcher and the AFATDS at platoon, battery, and battalion.

4-25. The FCS provides a link between the crew, launcher external digital traffic, and the launcher components. The FCS monitors, coordinates, and controls all electronic devices used by the launcher during the launch cycle. The FCS computes fire data for fire missions and communicates digitally with the AFATDS.

4-26. The AFATDS performs tactical fire direction processing at platoon, battery, and battalion level. The AFTADS receives, processes, and transmits fire unit, ammunition, and target data. It maintains databases that include fire units, munitions, and tactical fire plans.

4-27. AFATDS is the fire support C2 system within the ABCS. It provides decision aids and an information system for the control, coordination, and synchronization of all types of FS means. It acts as the force field artillery C2 system.

4-28. AFATDS is located at FA command posts from platoon to FIB to echelons above division. It is employed in varying configurations at different operational facilities. AFATDS is interconnected by the ACUS, the ADDS, or CNR communications. AFATDS operates with other services using the variable message format (VMF), joint tactical data link or, to a lesser degree, the USMTF messages. The system also complies with standardized message formats derived from North Atlantic Treaty Organization (NATO) Standardization Agreement (STANAG) 5620 and bilateral agreements with the United Kingdom, Germany, and other nations, as applicable.

C

’

G

4-29. The key to exploiting AFATDS capabilities is integrating the commander’s fire support guidance into the AFATDS database. Targeting guidance tells AFATDS which targets to process or deny. AFATDS automatically filters and screens mission requests and recommends denying those missions that do not meet the established commander’s guidance. It prioritizes multiple missions to ensure that the most important missions are processed first. It also checks incoming fire missions against fire support coordinating measures and unit zones of responsibility. If violations occur, AFATDS notifies the operator and electronically requests clearance from the unit that established the control measure. AFATDS then determines how to attack the target, applying guidance by system preference (FA preference, FA attack methods, mortar, naval gunfire, or air attack).

4-30. The system preference table allows the operator to tell AFATDS the weapon the commander deems most appropriate for each target type. The weapon systems are ranked from 1 to 4 in priority for consideration.

AFATDS F

F

4-31. Filters tell AFATDS which targets not to attack. One filter is target decay time; this defines how long, after a target type is acquired, it is still suitable for engagement. This filter highlights for the commander those targets with short dwell times and prevents firing on targets that may have moved. Other filters include—

• Target duplication filter. This filter allows fire supporters to specify the distance (in meters) that separates targets or similar targets to determine if they are duplicates. This prevents different sensors or observers from firing separate missions on the same target. If 2 missions violate target duplication, AFATDS will process the first mission and recommend denial on the second.

• Target build-up area filter. This filter allows the commander to specify the number of targets within an area that must be identified before engagement. It is particularly useful for counter fire elements that want to focus on developing a template for enemy area before attacking it.

• Target exclusion filter (part of the target management matrix [TMM]). This filter allows the commander to specify targets he does not want fire support to consider for attack.

4-32. AFATDS target selection standards (TSS) contains the same information normally used in a TSS matrix, including the TLE for potential sensors. This filter, generally used for intelligence reports, specifies a report age to prevent firing on targets that are too old.

AFATDS S

F

4-33. After a target clears the filters, AFATDS screens the mission to assign a mission value. This focuses fires by ensuring that the most important targets are engaged first. In AFATDS, this screening guidance includes mission prioritization, the high-value target list (HVTL), and the TMM.

AFATDS M

P

4-34. AFATDS prioritizes missions by assigning each a “mission value” of 0 to 100 based on 4 weighted criteria to determine the overall mission value. The 4 criteria are—

• On-call precedence allows the commander to decide that targets from the fire plan (stored in the on-call target list) have a higher priority than a target of opportunity. (A commander may not want targets of opportunity to disrupt the execution of preplanned, rehearsed targets in specific target areas of interest [TAIs] or engagement areas.)

• Priority of fires enables the commander to establish a preference among a pool of potential sensors/observers.

• If a target falls within a TAI, AFATDS will increase its mission value.

• AFATDS can weight targets based on their relative importance to the supported commander's mission. The target type value is identified in the HVTL and the TMM.

4-35. A commander can define the desired effects in the HVTL for each target category by specifying effects or any percentage of destruction from 0 percent to 100 percent. He can also assign a weighted value from 0 to 100 to each target category.

4-36. The HVTL is a starting point for the development of the HPTL and is a component of the TMM.

HPTs are HVTs that must be attacked to achieve success during friendly operations. The HPTL in the TMM applies additional guidance to weight the target types.

4-37. The TMM used in AFATDS provides the same information normally seen on an attack guidance matrix (AGM). It separates HPT types from non-HPT types. A commander can define the effects for each HPT type or any percentage of destruction up to 100 percent. He can also weight the value of each HPT type from 0 to 100. This is a second target value (for HPTs only) that AFATDS uses to compute an overall mission value.

4-38. As a result of mission prioritization, each target is assigned a mission value. Cutoff values set the minimum thresholds that targets must attain to be considered for attack by certain fire support assets. The commander assigns these to tell AFATDS which weapon systems to consider (and not to consider) as attack options for certain targets.

4-39. In the TMM, the commander can specify which target types require target damage assessment (TDA) or should not be fired upon but handed off to the IEW officer for exploitation. The commander can specify when targets will be engaged as “acquired,” “immediate,” or “planned.” The commander can also exclude target types in the TMM display from consideration for attack by fire support assets.

A

A

4-40. The next step AFATDS takes is to determine how to attack the targets. The commander can assign a preferred system (for example, FA, mortars, naval gunfire) to each target type. He can also build a series of tables in AFATDS to further define preferences (shell/fuze combination, for example) for each system against specific target types.

F

M

P

4-41. Another powerful capability AFATDS offers is the ability to eliminate the traditional mission delays associated with processing fire missions through multiple layers of fire support coordination. Not every mission needs to stop at every fire support node in the mission thread (digital route). By tailoring AFATDS intervention points (IPs), the commander can specify which missions stop for review (human intervention) at intermediate fire support nodes (battalion/task force and brigade fires cells [FCs]) and which automatically process through the fire support system to a firing unit for rapid response. The following are examples of fire mission processing:

• All fire missions for “armor, medium” or “missile, heavy” targets process rapidly without human intervention, a decision based on the type of target.

• Control IPs of fire missions, based on the mission value and every request for fire against a target type with a value of less than 50 stop for human review.

• Specify IPs by types of missions such as screening, adjust fire or illumination missions before they are processed.

• All fire missions AFATDS-assigned to the mortar platoon are processed automatically without human intervention.

4-42. The commander may want only fire missions that violate the filtering or screening guidance to have an IP. This adds a human review of an AFATDS decision before a mission is denied or coordination is requested. If the commander does not want a computer denying a supported commander's request for fire, he can establish an IP in AFATDS to review all missions the system recommends be denied.

4-43. Designing IPs in AFATDS offers tremendous flexibility. Tailoring IPs may be an alternative to quick-fire channels and has the potential of offering near real-time sensor-to-shooter capabilities. These IPs (filters) can be designed based on the following:

• Specific target type.

• Assigned mission value.

• Mission type.

• Attack option (mortars, FA, air, naval gunfire).

• Target duplication, exclusion, IEW routing, build up targets, or coordination required.

4-44. AFATDS is capable of receiving targets from a variety of sources. By filtering and screening potential targets for engagement, AFATDS automates many of the functions currently performed manually by the FAIO and other staff members.

4-45. The following paragraphs summarize the ATCCS devices that the MLRS battalion may interface with and/or operate.

M

C

S

4-46. The maneuver control system (MCS) provides Army tactical commanders and their staffs (corps through battalion) automated, online, near real-time systems for planning, coordinating, and controlling tactical operations. It is the maneuver component of ABCS. It receives, processes, and displays the increasing volume and variety of tactical command and control information available. MCS has a wide array of capabilities that allow for more efficient battle planning and execution. MCS capabilities range from modifying unit task organization to creating complex map overlays. MLRS elements at brigade and battalion/squadron level will interface with MCS through their AFATDS.

F

XXI B

C

B

B

(FBCB2)

4-47. FBCB2 interfaces with the ABCS and is located at the brigade level and below. It provides mounted/dismounted tactical combat and service support units the ability to gain situational understanding of the battlefield. FBCB2 provides accurate and real-time information about friendly, enemy, neutral, and noncombatant locations—a common relevant picture of the battlefield scaled to specific level of interest and special needs.

4-48. For the purposes of FBCB2, situational awareness is a state of understanding and knowledge gained through a graphical common operating picture of the battlefield consisting of the enemy situation, friendly situation, and logistics. The common operating picture that FBCB2 provides presents a new way to visualize the battlefield. This digital visualization provides a picture with dimensions that mitigate surprise and uncertainty. FBCB2 does this by providing soldiers with a common ability to see where they are, see where other soldiers are, see over the “next hill,” see the enemy, and know what each of them is doing.

This situational awareness contributes to mobility and force synchronization, and reduces the possibility of fratricide. This automated portrayal of the common operating picture becomes more critical as darkness, weather, and obscurants reduce visibility; when operating with night vision devices; or when operating in terrain where visibility is reduced (for example, heavily forested terrain, urban terrain, or rolling terrain).

4-49. Every vehicle in the FBCB2-equipped team has a computer that displays a digital image of the map.

Symbols (icons) representing individual friendly and enemy vehicles or units appear on the map and move in near real-time as the platforms they represent move on the battlefield. This continually updated situational understanding is a fully automatic function.

4-50. The Army intends to incorporate FBCB2 functionality to a platform in 2 separate ways:

• FBCB2 hardware (computer, radios, GPS receiver, mounting equipment) and software are added to an existing platform. Any platform can have FBCB2 functionality through this mechanism. This type of installation is termed stand-alone FBCB2 or an appliqué (see table 4-1).

• Embedded battle command (EBC) software embedded to operate on a computer that is already in a platform. EBC will be inserted into AFATDS and M270A1/M142 launchers to facilitate situational understanding on the future battlefield.

Table 4-1. Appliqué

Situational Awareness Battle Command

Execution Battle Command

Table 4-1. Appliqué

Situational Awareness Battle Command Execution EPW = enemy prisoner of war msg = message

CBRN = nuclear, biological, and chemical

OPLAN = operations plan

SALUTE = size, activity, location, unit, time, and equipment

SITREP = situation report VMF = variable message format