Keu y la detractio: el decir del senescal y el hacer del héroe

5-114. AFOM fire missions can be initiated by any agency capable of requesting fire. Agencies supported by digital communications systems may not be able to request the AFOM automatically.

However, they can compose and send a plain text message requesting fires. Fire mission source is important for estimated TLE (when TLE is not reported), munition selection, and effects calculation.

Automated processing depends on:

• Target type.

• Point of entry into the fire unit selection process (node/system).

• Shooter linkage or communications.

• Method of control.

• Specified munition (if any).

5-115. Once an AFOM variant has been selected (usually at the corps/division FC), a fire mission message format (for example, fire mission; CFF) is generated. It contains a minimum of a weapon type (or J-code) and a designated unit to fire in effect. It is then transmitted to the selected battalion FDC for execution. The battalion FDC transmits the fire mission to a battery FDC where launchers are selected from the designated platoons.

A

P

5-116. To ensure the fastest possible reaction, the subordinate echelon FDC computers should be set up to perform automatic processing of missions. This procedure streamlines the mission processing during non-routine operations or when responsiveness to time critical targets is required. When the FDC computer is set up to automatically process missions, it performs all necessary processing to ensure receipt of a valid message. If the message passes the consistency checks and the UFFE is available, the FDC computer relays the message to the next subordinate echelon. The battery FDC computer—

• Performs consistency checks based on commander’s guidance/operator inputs.

• Validates the selected UFFE (no effects processing will be performed).

• Assigns launcher(s) to fire from within the designated UFFE.

• Prepares call for fire message for transmission to launcher(s).

I

P

5-117. AFATDS allows the mission to be processed automatically or lets operators view and make decisions on every fire mission they receive. It also permits a mix; certain types of missions will be processed automatically while the operator handles only specified types of missions. The intervention point window provides the operator the target number, mission value, mission precedence, and a list of filter guidance and whether they passed or not. All attack assets capable and available to shoot the mission with the required munitions are also listed.

5-118. The operator can set up intervention rules that allow given target conditions to cause an intervention point to be generated when the mission is processed. However, AFOM missions are always presented at an intervention point, regardless of operator criteria. The operator can accept, reject, or change the mission.

5-119. AFATDS presents all attack options for the operator to review. Non-capable attack options will have a reason stated. This provides the operator enough information to understand the problem and, perhaps, fix it.

P

M

5-120. The AFOM is most effective when used on planned targets. Attack of planned targets permits refinement of target locations (or predicted locations for moving targets) to required (or better) accuracy and description and for posturing missiles and launchers. Planned fires typically use the following methods of control: AMC, TOT, ONC, TWR, FWR, and TTT.

5-121. Planned fires may be scheduled missions that are executed according to a predetermined time schedule or sequence of events or on call. Scheduled missions are planned and sent to the lowest command and control echelon for execution at the appropriate time. This allows mission execution on receipt of the engagement trigger event or scheduled time to fire. AFOM missions are scheduled in the same manner as rocket missions. On-call missions are like scheduled missions because they are sent to the lowest command and control echelon, but the time of execution is unknown.

5-122. AMC missions are planned missions for which the time of execution depends on the occurrence of a trigger event or confirmation of target location or activity. The FDC can use these missions when the commander desires rapid attack of a target, or when attack is keyed to other significant events on the battlefield. When the launcher receives this type of AMC mission, it moves to a firing point (if in hide

position) and elevates to aim-point. The launcher reports “READY” to the controlling FDC and awaits the command to fire.

U

M

5-123. The AFOM may also be fired against targets of opportunity. All available communications means are used in mission processing. Prior coordination among the various agencies may reduce the processing time associated with targets of opportunity. For selected targets or areas of interest, more direct links may be established between higher and lower agencies to reduce processing time. Those nodes left out of the process will be provided information and status as the mission progresses.

AFATDS M

P

AFOM

5-124. When a fire mission is initiated, AFATDS assigns it a target number (if this has not already occurred) and calculates its mission value. AFATDS then goes through a series of “filter” checks (for example, duplication, TSS) to see if it qualifies as a fire mission. If it passes these filters, a set of munitions that could be used to shoot the mission will be generated from the guidance as well as from the munitions requested in the call for fire. AFATDS generates a list of units that are both capable and available, based on the OPFAC unit organization (from both command and supported HQs that the operator entered in the current database) as well as observer specified and guidance specified entries. AFATDS then matches munitions with available units to see which units can actually shoot the mission given the munition requirements. This set is ordered (sorted) such that the best choice units are listed first. AFATDS will always present the number 1 recommended solution to the operator for AFOM missions.

5-125. When a mission is in progress, it is said to be active. While active, a target appears yellow on the AFATDS screen and is located on the active target list. A number of messages can be initiated while a target is on the list. However, the AFATDS operator should not interrupt subsequent messages the fire mission initiator sends, except in extreme circumstances. The operator can trace status or missions on the active target list. This permits the operator to quickly gain a record of the mission history as well as its current status at other OPFACs.

5-126. When a mission is completed and an end of mission (EOM) or MFR is received, the target is processed to the inactive target list. The inactive target list can be purged to rid the system of all old missions.

T

R

M

T

5-127. The commander should always direct automatic processing at intermediate nodes to attack AFOM targets. Automatic processing allows the mission to pass through echelons without operator activity.

However, the battalion must ensure that the following information is kept updated: whether the designated firing platoon is available, within range of the target, and loaded with the right munitions. The battery FDC has the additional burden of keeping the firing point database current. This is the primary cause of automatic processing failure.

Stay Hot, Shoot Fast

5-128. The commander should strongly consider establishing a quick fire channel or mandating decentralized execution for time-sensitive targets. This reduces the mission execution response time.

Extremely time-sensitive targets designated for attack may necessitate a technique often called "stay hot, shoot fast(SHSF)."

5-129. Most units will describe when to use the stay hot, shoot fast technique and the procedures for this technique in their TSOP. The following is an example. AFATDS operator sets up the User Preferences for Mission Processing in the (SHSF) tab. Tolerance Zone 1 is for no adjustment when mission is received, Tolerance Zone 2 is when SHSF mission comes in and adjustments are sent to the launcher for amended grid. Minimum Distance is for minimum distance between an ATI target location and ATI impact predicts

location. The launcher is placed on a firing point and laid, LM elevated, on a target grid of an expected enemy target. The method of control at the AFATDS is a Warning Order but sent to the launcher as an AMC. The launcher will complete the mission sequence up to the point of achieving aim-point and then report ready status. When an enemy target is acquired firing from the expected grid, the BOC uses its AFATDS to send a fire order to the launcher(s) to engage the preplanned target(s). On receipt of an amended fire mission changing the method of control to FWR (or TOT), the launcher completes the mission as directed when the target falls in tolerances zone 1. Often, the preplanned or expected target location differs slightly from the actual target location. If this occurs, instead of firing the preplanned target grid, the fire mission is shifted, or amended, to the new target grid acquired by friendly force systems. The launcher accepts amended missions up to 200 mils on either side of the direction of fire to the preplanned target for a total shift fan of 400 mils.

5-130. The BOC can plot the amendment fan, or shift zone, on its operations map for all launchers laid on a potential or preplanned target. This is done by plotting the launcher location and target location, drawing the azimuth to the target, and then plotting azimuths 200 mils left and right of the azimuth to the target.

When the minimum and maximum ranges are added to this fan, the result is a shift zone where the launcher can engage targets using amended mission procedures.

5-131. When an acquisition source sends the target location to the BOC, fire direction personnel determine which launcher or launchers can engage the target and send an amended CFF to the unit(s) to fire.

5-132. There are distinct challenges to an MLRS unit using stay hot, shoot fast tactics, techniques, and procedures (TTP). First, the BOC must closely monitor the status of launchers and the database associated with them. The stay hot, shoot fast procedures require the precise location and status of each launcher to work properly. Any error that goes undetected until the fire mission is processed simply adds more time to correct the error and execute the mission when we can least afford the time to do so.

5-133. Secondly, stay hot, shoot fast requires clear digital communications from the BOC to launcher.

First time acknowledgement of messages is crucial. Non-acknowledgements add more time to the processing. Thirdly, the launcher and fire direction crews must be well-rehearsed.

5-134. The launcher must park on, or as close to, the park heading as possible. Any mils sacrificed by not parking on the parking heading may take mils away from the shift fan and cause the launcher to reject the mission.

5-135. Last, by selecting well-concealed FPs nestled in hillside cuts, valleys, or streambeds, units can minimize vulnerability to observation. Additionally, after each fire mission, the launcher should scoot to another FP and lay on the next preplanned target if required.

S

-

-S

C

5-136. Various sensor-to-shooter configurations are available to support the commander's needs, depending on the missions to be accomplished and level of control required:

• Sensor->Corps FC->Bde->Bn->Btry->Launcher (Centralized Control)

• Sensor->Corps FC->Bn->Btry->Launcher (Centralized Control)

• Sensor->Bde->Bn->Btry->Launcher (Decentralized Execution)

• Sensor->Corps FC->Btry->Launcher (Centralized Control) (preferred method for all AFOM missions)

• Sensor->Corps FC->Plt->Launcher (Centralized Execution) (preferred method for all AFOM missions)

• Sensor->Bn->Btry->Launcher (Decentralized Execution).

5-137. In all cases, the commander must decide whether less control or fewer intervening processors is worth the added responsiveness. (See FM 6-20-40 [to be replaced by FM 3-09.42] for a complete discussion of sensor-to-shooter operations.)

L

M

M

5-138. The AFOM weapon-specific loadable munition module (LMM) software incorporates AFOM selection, effects processing, and airspace coordination. The LMM software is unique to each AFOM.

5-139. The LMM software processing complies with the established attack guidance (commander’s criteria) in its database, and the message priority. The operating mode (fully automatic or manual) determines the amount of processing required. In the automatic processing mode, the FS computer checks message validity, the unit to fire, and ammunition availability. If it finds no exceptions, it enters the data and forwards the message to the next subordinate echelon. If it finds exceptions, it reassigns the mission if an alternate is available.

AFOM M

P

S

5-140. The battalion and battery FDCs process AFOM missions the same way they do other missions (except for effects processing and airspace message generation). The FDC computer software has no default for the number of AFOM missiles to be fired on an aim-point. When the fire mission is received at battalion, the FDC performs the tactical processing and formats the call for fire for transmission to the battery. The battalion FDC uses the designated fire unit or selects the platoon to fire if it has not been selected. Otherwise, it validates the FC selection.

5-141. At the battery level, the FDC performs the tactical functions appropriate to the battery echelon, selects the launcher or launchers to fire, and generates a separate fire mission message format to each selected launcher. Basic fire mission processing at the launcher requires no special activities.