Military

The amount of processing required to develop a target varies extensively. In its simplest form, target data processing is the passing of a target from a known, accurate, and reliable source to the fire control element (FCE) or fire direction center (FDC) for attack within established attack guidance and target selection standards (TSS). In its most complex form, it is the collation of target indicators and suspect targets from diverse sources into a target identification and location accurate enough to justify attack.

In ABCS equipped units, target data is transmitted and processed automatically according to the commander's guidance and TSS stored in the AFATDS computer.

AFATDS uses the Target Generation function to automate the tasks performed by the targeting and target processing elements of the DIVARTY or Field Artillery Brigade TOC. The Target Generation function consists of a series of processes that compare and combine target information to generate targets and update the suspect target list and target indicator file. Target Generation takes suspect targets, Artillery Target Intelligence (ATI) targets, and target indicators (such as shell reports) as inputs, and through several processes eliminates duplication, determines and refines suspect target locations, and generates targets. The Target Generation function can be turned on or off based on the targeting needs in a given tactical situation. The outputs of this function are generated targets and an updated suspect target list and target indicator file. Some key definitions related to Target Generation are:

• Target Indicators are directional information that forms a ray (line) from a given point, in a given direction, to a derived maximum distance along which a possible enemy target may be located. Examples of target indicators include shelling, flash, and jam strobe reports. A target indicator will have a target type (e.g. "Artillery, Unknown", "EW Equipment").

• Target Data are grid producing information received at AFATDS via a fire request (e.g., a call for fire received from an observer or a fire mission initiated by an AFATDS operator) or intelligence information (e.g., ATI report received from an observer). Target data are also produced by AFATDS. For example, AFATDS uses intersecting target indicator rays to determine a grid location, thereby generating target data.

• A target is target data that has passed TSS, and therefore, is worthy of attacking because it meets the commander's criteria for reliability, accuracy, and timeliness. Targets undergo further mission processing to determine if a fire mission will be initiated based on comparisons to additional targeting and attack guidance, the target's relative value to other targets, and if attack systems are capable of engaging the target.

• A suspect target is target data that has failed TSS and may not be worthy of attacking because it does not meet the commander's criteria for reliability, accuracy or timeliness. Suspect targets are further refined until they pass TSS and the operator initiates a fire mission on the suspect target, or the suspect target decays (based on target decay guidance) and is deleted from the suspect target list.

If an Operational Facility (OPFAC) does not routinely process shelling reports, a routing function is available to forward shelling reports to a designated OPFAC for processing. For example, a battalion FSE receives a shelling report from one of his observers. The battalion FSO may direct that the report be forwarded to DIVARTY (or the designated counterfire headquarters). The following procedure is used to forward a shell report. Select "Alerts & Messages" -à "Messages" à "Configure Receiving Setup" and highlight the "Target Indicators" message type and input the DIVARTY address (make sure DIVARTY is in your communications configuration). This procedure routes the shelling report to the appropriate processing element.

AFATDS always performs certain functions when a target indicator is initially received whether it was received from an observer or created through operator input. When AFATDS receives target indicator data, some of the information required to process the indicator may or may not be present. AFATDS automatically determines missing information based on reporting observers' unit data and default data files. Missing information is determined as follows:

• Target Indicator Number - If the received target indicator does not have a target indicator number, one is assigned based on the next available target indicator number from the OPFAC target indicator number block. The target indicator number must always begin with "II". If a target indicator is received with a number that does not begin with "II", the number will automatically be replaced with an "II" number. AFATDS maintains a target indicator numbering block, which the operator cannot edit. This block goes from "II0000 to II9999".

Note: When you enter a target indicator into AFATDS do not enter a target number (AFATDS will automatically number the indicator).

• Target Indicator Decay DTG - If Target Indicator Decay DTG for the target indicator is not provided AFATDS computes the DTG by adding target decay guidance for the target type to the DTG of acquisition/report. The DTG of report will default to the current time if not provided.

• Target Type - If the received target indicator does not specify a target type, one is assigned based on the following rules:

  – If the weapon type is Artillery: Artillery, Unknown.

  – If weapon type is Mortar, the target type is based on the reported caliber, otherwise the target type is Mortar, Unknown. If the caliber of the mortar is reported, AFATDS will determine the target type as shown in Table A-1.

– If the weapon type is Rockets or Missiles: Rocket or Missile, Unknown is used.

– If the weapon type is an Electronic Emitter (or any other electronic target), then the target type is Electronic Warfare Equipment.

• Sensor Directional Error - If the target indicator does not include the sensor directional error (mils) then it is determined based on the default value for the reporting sensor's unit data or unit type in Table A-2.

• Sensor Location - If the sensor location at time of report is not provided, then that sensor unit's most current location is used to determine this value. If no location for the reporting unit is available, the target indicator report is discarded.

AFATDS uses target similarity to determine if targets should be combined or if target indicators are close enough to generate target data. Table A-3 lists target categories, types and their similarity to other targets. The matrix number is the individual number for that target type. The similar to matrix numbers are the targets that are considered similar to the target type. The matrix is also used for target duplication checks.

The direction and distance of the target indicator ray is determined by:

• Direction of ray originates from the sensor/shell impact location.

• Length of ray is based on the following:

  – Use length provided, if given.

  – If a flash to bang is provided, use Distance = 350 X Time (sec). The result is the length of ray in meters.

  – If length or flash to bang time is not provided, the ray length is based on the target type as shown in Table A-4:

Target indicators are displayed as "fans" based on the sensor directional error. Figure A-1 shows a target indicator with a 10,000 meter length and a sensor directional error of 10 mils.

Each target indicator ray has an assigned color based on target type. The colors of target indicator rays are shown in Table A-5.

Based on the tactical situation, the AFATDS operator may or may not want the system to run the Target Indicator function. AFATDS allows the operator to turn target indicator processing on or off. When the target indicator processing is "off", AFATDS adds the target indicator to the target indicator list with no additional processing or comparisons. When Target Indicator Processing is "on", AFATDS performs the following checks (in order):

• Compares the target indicator against the current (but non-active) target files (i.e. targets on the "On-call", "Suspect", "Planned" and "Inactive" target lists). If the indicator ray covers a similar target, the OPFAC with target indicator processing duty is notified of the "Target Indicator Match" via an alert and reviews information on the target indicator and all matched targets. The operator may take various actions from this alert:

  – Selectively initiate fire mission(s) against the target(s) indicated as a match. This will open the initiate fire mission screen already filled out for the selected target.

  – Add selected matched target(s) to an existing fire plan. This will place the targets on the selected fire plan.

  – Display the target indicator fan-target comparison. This graphically displays the indicator fan and the associated matched target(s) on the map.

  – Selectively update matched target(s) with a new "last updated" value based on the target indicator DTG of acquisition/report.

  – Delete the target indicator. This will discard the received target indicator data and will not add it to the target indicator list.

  – Continue Processing the Target Indicator. This will add the target indicator to the target indicator list for possible combination with existing target indicators.

• Compare the target indicator with other target indicators already on file. If the target indicator did not match a target or the operator selected "Process TI" from the target match window, AFATDS will add the new target indicator to the target indicator list and determine if it can be combined with existing target indicators. See Figure A-2 for an example of target comparison The following rules are used in this comparison:

  – The new target indicator is compared against existing target indicators in the target indicator file that have a similar target type. Only target indicators that have not passed their decay DTG are considered.

  – When target indicator rays of three or more of the compared target indicators intersect to form a point or common area, and all points are located within 400 meters, AFATDS automatically combines the rays and generates a new target number and passes the target to the TSS check for further processing. Combined TIs are deleted from the TI list.

  – If no match is found, the new target indicator is added to the target indicator file. The operator can purge the target indicator list of target indicators when their "decay time" DTG is passed. To do this simply select "automatically purge" option on the target indicator list window.

Figure A-3 provides a summary of the possible results of target indicator processing.

Suspect targets represent target information that has not passed TSS. This section discusses how AFATDS processes suspect targets after TSS failure. The operator may turn Suspect Target Processing "on" or "off". When it is turned off, all suspect targets are simply added to the suspect target list with no further processing. When it is turned on, AFATDS evaluates each suspect target against other suspect targets to combine the new suspect target with an existing suspect target and generate a target with a better TLE and/or more current DTG. AFATDS applies the following considerations when identifying suspect targets for combination and applying the associated target data for the "new" (combined) target:

• Decay Time. Only suspect targets that have not passed their decay DTG are considered for combination.

• Target Type. Only targets with a similar type will be considered for combination. For example, an "Artillery, Unknown" target would not be combined with a "Building, Metal" target.

• Target Size. The target size and TLE, for the new or extracted suspect targets is used to determine overlap. If an overlap exists between the new target and a single existing target and the overlap area meets or exceeds the operator established percentage of overlap required, then the two targets match. Basically, the overlap percentage tells AFATDS how close two targets must be (considering the area and TLE of each target) in order to combine them. Figure A-4 shows some examples of this comparison.

If multiple overlaps exists between the new suspect target and two or more existing suspect targets and each overlap area meets or exceeds the operator established percentage of overlap required, then the following rules apply:

• The suspect target with the greater degree of similarity to the new suspect target is combined with the new suspect target.

• If the degree of similarity is the same, the suspect target with the greater degree of overlap with the new suspect target is combined with the new suspect target. Figure A-5 illustrates multiple target overlap.

When two targets are combined, the new target is sent to TSS for further processing. Both of the "parent" targets (the two that were combined) are removed from the suspect target list.

The operator may specify the "Overlap %" to be used by AFATDS when considering targets for combination. A larger percentage (like 75%) will result in fewer, but more accurate, combinations than a smaller percentage (like 25%). As with the target indicator list, the operator may decide to have the suspect target list purged of targets when their "decay time" DTG is passed. To do this simply select "automatically purge" option on the suspect target list window. Finally, the operator may see the targets on the suspect target list that were generated by AFATDS (these will be the targets that have a "yes" in the "Combined?" column of the list). There is an option to "uncombine" a combined target if desired.

An ATI;CDR message received from IFSAS could be treated as a fire request, intelligence data, mission fired report (MFR), On-Call Target, or Planned Target depending upon the information contained in the message. Table A-6 summarizes the various dispositions possible for an ATI message received by AFATDS.

An ATI message received from a Package 11 device could be treated as a fire request, intelligence data, MFR, On-Call Target, or Planned Target depending upon the information contained in the message. Table A-7 summarizes the various dispositions possible for an ATI received by AFATDS.

If the message does not fit into the rules contained in Table A-7, it will be displayed upon receipt to the AFATDS operator. A summary of the possible results of suspect target processing is provided in Figure A-6.

Target Damage Assessment (TDA) is a function of AFATDS that allows target disposition to be entered by the observer on the MFR after attack of a target. TDA can be flagged in the commanders guidance of AFATDS, causing targets to remain active until disposition is received from the observer for the particular target. TDA in AFATDS guidance is target type specific. Therefore, it is not very useful in the determination of TDA on a particular target generated from the suspect target processing function. Flagging an individual target type in the target management matrix (TMM) will cause that target type to remain active until the reporting sensor sends a MFR for that target that contains target damage. This requires eyes on target. A target generated by the suspect target or target indicator processing function will have the processing AFATDS station as the observer. This station very seldom has eyes on target.

File maintenance for suspect target and target indicator processing consists of purging targets that are no longer valid. This can be done manually or automatically. Manually deleting targets from the suspect target or target indicator list involves selecting the target list requiring maintenance and reviewing individual targets, and validating or deleting individual targets from the target list. The most effective method of performing file maintenance is to set target purging to automatic. This automatically purges targets based on the target decay time established in the TSS. This is accomplished by selecting "Automatic Purge" on the suspect target or target indicator list.