AFATDS improvements--we hear you!

While reading the March-June edition of the FA Journal, I found two articles of particular interest. The first was "IMEF Fires in OIF" by Lieutenant Colonels Paul M. Andrus and Randol D. Rule and Major Robert J. Terselic, all USMC. The second was "4th ID: Clearing Airspace for Counterfire in Iraq" by Army Major Michael Donahue and Captain Carl F. Robinson.

These articles were of interest to me as an Assistant TRADOC [Training and Doctrine Command] Systems Manager for Field Artillery Tactical Data Systems (TSM FATDS) working on the AFATDS [advanced Field Artillery tactical data system] program. Both articles mention AFATDS and suggest specific changes to make AFATDS more effective. It may be of interest to readers to note that the authors' suggestions already are programmed for future AFATDS and its effects management tool (EMT) software releases.

Large Numbers of No-Strike Targets. In "IMEF Fires in OIF," the Marine officers took AFATDS to task for its inability to handle their 13,000-plus no-strike OIF targets on the AFATDS' "Limited Protected Area List." The current version of EMT (2.16), which is issued with AFATDS Version 6.3.2 software, has eliminated problems associated with the extremely large Limited Protected Area List. It also can import the Limited Protected Target List from a spreadsheet file and perform automated coordination checks against the list. AFATDS 6.3.2 and EMT 2.16 are fielded or being fielded to units today. AFATDS Version Software Block 2 (SWB2), due for release in November 2006, will be able to handle the Limited Protected Target List by itself (no EMT needed).

No Restricted Operating Zones (ROZ). The "4th ID: Clearing Airspace for Counterfire in Iraq" article stated that AFATDS does not have a ROZ geometry type. This is true. The 4th ID's use of the platoon area hazard (PAH) as a means to identify danger areas associated with their firing elements was both innovative and technically correct. The Air Force system, theater battle management-core system (TBMCS), considers a PAH a ROZ.

In the future, AFATDS Version SWB2 will support the ROZ as a new geometry type, an improvement suggested by the 4th ID article.

Improved Web-Based Interface with TBMCS. Additionally, AFATDS SWB2 will incorporate an improved web-based interface with TBMCS. This interface will overcome many of the limitations imposed by the USMTF [US message text format] currently used to communicate with TBMCS and will allow greater visibility of air tasking order [ATO] and airspace control order [ACO] data.

These articles are examples of how creative and innovative our warfighters are and how requirements for automated systems are continually evolving. The members of TSM FATDS read all articles and feedback about AFATDS and react to fix our warfighters' challenges as quickly as funding allows. We welcome users' comments and recommendations.

Please visit our website at http://www.army.mil/tsm_fatds/ to get the latest information on AFATDS or give us feedback by contacting me at [phone] (DSN 639) or [e-mail].

MAJ Neil P. Patterson, FA

Assistant TSM FATDS

Fort Sill, OK