Algorithm for Monitoring ISR Success


The Detailed Detection Monitor Form interface allows the umpire to dynamically review the accuracy of detection reports on selected targets. The interface provides Truth data with a white background and Perception with a blue background (as reported to the force players) with a light blue background. A number of the columns are interactive. For example, the first column (the target) provides current target status including location. In order to be monitored on this interface the target must be listed in the detailed_monitor database table. Targets will not automatically be added to this list.

The second area of this interface is a series of buttons. The information is broken down by sensor type (e.g. EO, IR, SAR). For each sensor type and target combination the interface provides a two-color button with amplifying data when clicked. The inner color indicates the timeliness of any reports, starting at green (current) and then progressing through yellow and red as the reports get stale. The current thresholds for color changes are:

Detection Age

Color

<3600 seconds

Green

Between 3600 and 10000 seconds

Yellow

Over 10000 seconds

Red

These values are TCL variables, meaning not only can they be reset between runs but can be reset during runs for changing conditions. The programmer is referred to the bad_delay and warning_delay members of the d_monitor array in the detailed_sensor_monitoring.tcl file.



The outer color is report accuracy, green for very accurate and then degrading through yellow and red. Clicking on the button will provide detection details. The current thresholds for color changes are:

Detection Accuracy

Color

<250 meters

Green

Between 250 and 1000 meters

Yellow

Over 1000 meters

Red

Again, these values are TCL variables, meaning not only can they be reset between runs but can be reset during runs for changing conditions. The programmer is referred to the bad_error and warning_error members of the d_monitor array in the detailed_sensor_monitoring.tcl file.

The third area indicates the user confidence in the detection. When clicked a listing of the sensors and report times used to achieve the confidence is provided. The confidence in the detection of a specific target is computed by the addition of the combination of add timely sensor reports on the target within the region being evaluated for ISR. Currently timely reports are those that occur within 15 minutes. The reason this value is used is that the confidence algorithm was developed primarily to support the detection of mobile targets. The detections are taken as a series of paired detections. The confidence for any two sensor reports taken during this 15 minute epoch are based on the types and quality of detections. Note that while two sensor reports from separate platforms can improve confidence, Two sensor reports from the same sensor type and from the same sensor platform can not improve confidence. Currently the confidence values for combining two disparate sensor reports are:

Sensor Type A

Detection Quality A

Sensor Type B

Detection Quality B

Confidence for Paired Detection

IR

High

IR

High

80

IR

High

EO

High

100

IR

High

SAR

High

100

IR

High

SIGINT

High

60

IR

High

IR

Medium

80

IR

High

EO

Medium

85

IR

High

SAR

Medium

80

IR

High

SIGINT

Medium

60

IR

High

IR

Low

40

IR

High

EO

Low

50

IR

High

SAR

Low

55

IR

High

SIGINT

Low

60

IR

Medium

IR

High

60

IR

Medium

EO

High

80

IR

Medium

SAR

High

80

IR

Medium

SIGINT

High

30

IR

Medium

IR

Medium

30

IR

Medium

EO

Medium

40

IR

Medium

SAR

Medium

45

IR

Medium

SIGINT

Medium

30

IR

Medium

IR

Low

10

IR

Medium

EO

Low

30

IR

Medium

SAR

Low

30

IR

Medium

SIGINT

Low

30

IR

Low

IR

High

40

IR

Low

EO

High

40

IR

Low

SAR

High

40

IR

Low

SIGINT

High

15

IR

Low

IR

Medium

10

IR

Low

EO

Medium

12

IR

Low

SAR

Medium

15

IR

Low

SIGINT

Medium

15

IR

Low

IR

Low

1

IR

Low

EO

Low

4

IR

Low

SAR

Low

5

IR

Low

SIGINT

Low

15

EO

High

SAR

High

90

EO

High

EO

High

80

EO

High

SIGINT

High

60

EO

High

EO

Medium

60

EO

High

SAR

Medium

79

EO

High

SIGINT

Medium

60

EO

High

EO

Low

40

EO

High

SAR

Low

50

EO

High

SIGINT

Low

60

EO

Medium

EO

High

60

EO

Medium

SAR

High

70

EO

Medium

SIGINT

High

30

EO

Medium

EO

Medium

30

EO

Medium

SAR

Medium

35

EO

Medium

SIGINT

Medium

30

EO

Medium

EO

Low

10

EO

Medium

SAR

Low

20

EO

Medium

SIGINT

Low

30

EO

Low

EO

High

40

EO

Low

SAR

High

40

EO

Low

SIGINT

High

15

EO

Low

EO

Medium

10

EO

Low

SAR

Medium

11

EO

Low

SIGINT

Medium

15

EO

Low

EO

Low

30

EO

Low

SAR

Low

2

EO

Low

SIGINT

Low

15

SAR

High

SAR

High

80

SAR

High

SIGINT

High

60

SAR

High

SAR

Medium

60

SAR

High

SIGINT

Medium

60

SAR

High

SAR

Low

40

SAR

High

SIGINT

Low

60

SAR

Medium

SAR

High

60

SAR

Medium

SIGINT

High

30

SAR

Medium

SAR

Medium

30

SAR

Medium

SIGINT

Medium

30

SAR

Medium

SAR

Low

10

SAR

Medium

SIGINT

Low

30

SAR

Low

SAR

High

40

SAR

Low

SIGINT

High

15

SAR

Low

SAR

Medium

10

SAR

Low

SIGINT

Medium

15

SAR

Low

SAR

Low

1

SAR

Low

SIGINT

Low

15

SIGINT

High

SIGINT

High

20

SIGINT

High

SIGINT

Medium

20

SIGINT

High

SIGINT

Low

20

SIGINT

Medium

SIGINT

High

20

SIGINT

Medium

SIGINT

Medium

20

SIGINT

Medium

SIGINT

Low

20

SIGINT

Low

SIGINT

High

20

SIGINT

Low

SIGINT

Medium

20

SIGINT

Low

SIGINT

Low

20



For those who care, here's the pseudocode for the algorithm that computes the composite confidence. The code is in the alternate_plans.c file in the sim/initial directory.




The confidence due to pairing is combined for all timely pairs . The actual confidence is displayed on the interface and color-coded according to the following thresholds:



Confidence

Color

>=90%

Green

Between 50% and 90%

Yellow

<50%

Red



Again, these values are TCL variables, meaning not only can they be reset between runs but can be reset during runs for changing conditions. The programmer is referred to the bad_confidence and warning_confidence members of the d_monitor array in the detailed_sensor_monitoring.tcl file.

The fourth area provides a listing of the automated responses from the system. This is based upon the responses input into the sensor_cueing database table for this scenario. This table permits the user to designate which (if any) sensors should be tasked to confirm an initial report, either to add detection accuracy or confirm an uncertain detection. This is an example of possible responses with one selected.

The final entry indicates the automated system response, if any. Do not expect this column to be populated during a live exercise. The responses are based on the "Immediate high value target" rules defined under "Scenario Defn->Automatic Rules " in the Mission Planner mode.