Endouring freedom - military intelligence

Military Intelligence Professional Bulletin, Jan-March, 2003 by Robert J. Ehrlich

Extract From Operation Enduring Freedom Lessons Learned and Observations Afghanistan: 19 May 2002-12 June 2002.

Editor's Note: This article is an extract from a Center for Army Lessons Learned (CALL) publication and reflects two intelligence-related lessons learned from operations conducted in Afghanistan. MIPB thanks SFC Ehrlich and CALL for sharing this information.

Observation 9: Theater Maps

Discussion. The unit deployed with insufficient maps of the area of operations (see Figure 1), especially those of 1:50,000 scale. The unit installed software program Falcon View on all of the TOC and TAC computers before departure. A tremendous asset, Falcon View was employed for the duration of the operation. With it, the unit could quickly and easily add graphics to a map, boundaries, and other information then simply print a color map of area they were going into. A 1:50,000 scale map of the area was not available for download to Falcon View and that used by MCS Lite was incompatible with Falcon View.

Editor's Note. Falcon View is an integral part of the Personal Flight Planning Software (PFPS). This software suite includes Falcon View, Combat Flight Planning Software (CFPS), Combat Weapon Delivery Software (CWDS), Combat Air Drop Planning Software (CAPS), and several other software packages built by various software contractors. Falcon View is a Windows 95[TM] and Windows NT[TM] mapping system that displays various types of maps and geographically referenced overlays. It supports many types of maps, but the primary ones of interest to most users are elevation and aeronautical charts and satellite images. Falcon View also supports a large number of overlay types that the user can display over any map background. The current overlay set is targeted toward military mission planning users and is oriented towards aviators and aviation support personnel. Additional information can be found at http://www.falconview.org/contacts.htm.> DTLOMS Implications:

Doctrine. Doctrine must include digital mapping and planning software functions as these can significantly assist in the military decision-making process (MDMP).

Training. Training in various software programs must occur in the schoolhouse and home station to allow staff soldiers to use the equipment and tools properly, and make the most of the programs available to assist in planning and combat control.

Materials. Software packages must all include a commonality in maps, either by being able to import the various formats used by other programs, or by using a common format. All DOD map programs must have a commonality in exporting and importing map sheets. If not, DOD must support each authorized program with all (map) sheet scales for download.

Observation 14: Falcon View or MCS Lite.

Discussion (Extract). The 3d Battalion S2 was very forthright in comparing Falcon View to MCS Lite. He favored Falcon View because it-

* Was much easier to learn and use than MCS Lite.

* Allowed you to develop a plan quickly, lay it out, then if required, change it without having to delete and redraw a boundary.

* Allowed "printed to scale" without the hassles of putting together map sheets, acetate, alcohol pens, and the like.

* Allowed you to download icon pallets or create your own.

* Allowed conduct of fly-through rehearsals in support of air assault missions. In this use, it allowed us to "see" exactly what we had templated along the flight route.

* Allowed a change in the magnification (zoom).

* Allowed rotation of the view using only a few simple keystrokes.

* Allowed easy updating to other users by sending databases via the LAN, E-mail, or by disk. This was important because it allowed everyone use of the same graphics.

Recommendation. Relook program software for simplicity of use and compatibility across platforms. The digital TOC must be something that has simple-to-learn functions, but be robust enough to handle task such as those explained above.

DTLOMS Implications:

Doctrine. Doctrine must include digital mapping and planning software functions as these can significantly assist in the MDMP.

Training. Training in various software programs must occur in the schoolhouse and home station to allow staff soldiers to use the equipment and tools properly, and make the most of the programs available to assist in planning and combat control.

Materials: Software packages available to soldiers must all include a commonality in maps, either by being able to import the many formats, or use a common format.

Soldiers: Soldiers assigned to staff positions must be computer-literate and seek training for the operating systems and programs they will use. They must be self-starters and before being assigned to a staff, all must be competent in all aspects of their military occupational specialties (MOSs). Assignment to a staff position should not hinder the soldier's chance for advancement; rather, it should make them stand them out as being the highest qualified.

Observation 23: Brigade Intelligence Analysis

Discussion. During operations, the brigade Intelligence section was severely understaffed and under-equipped to handle the volume of information coming in during actual combat operations. Part of the problem was that although each higher headquarters had a Secure Internet Protocol Router Network (SIPRNET) information page, they had not been maintained. Many pages were outdated but even those shown in the CAAT were more than 3 weeks old and some pages were more than month old. Neither SOF nor TF 11 reported through standard intelligence channels, even on areas the Rakkasans were targeting. When SOF or TF 11 came in from a mission, the S2 shop attempted to capture a quick intelligence snapshot of the area. Otherwise that data was lost to the soldiers about to go into the area. Additionally, during the course of the MDMP, areas of interest changed with almost every FRAGO.

 

BNET TalkbackShare your ideas and expertise on this topic

Please add your comment:

  1. You are currently: a Guest |
  2.  

Basic HTML tags that work in comments are: bold (<b></b>), italic (<i></i>), underline (<u></u>), and hyperlink (<a href></a)

advertisement
advertisement
  • Click Here
  • Click Here
  • Click Here
advertisement

Content provided in partnership with Thompson Gale