text: Appendix F
  Example Target Information Folder
  The Army targeting methodology does not have a prescribed target packet format or
  requirements unlike the joint targeting standards. Nevertheless, in order to database,
  sort, and share the targets developed through D3A, a digital format must be established
  by SOPs and Commander’s guidance and built on specific information points. This
  appendix will display an example format and content to be completed. This example
  is meant to support all target types but does not represent any prescribed requirements.
  TARGET PACKETS
  F-1. Targeting often requires that targets be in a shareable format. Whether in a joint or Army role, targeting
  teams must maintain the ability to save progress, share, or database targets during the development process
  to satisfy validation requirements. In an Army role, the presentation of a target is entirely unit and SOP based.
  The method, format, and content in which to build a target packet is typically driven by the commander's
  requirements, FSCOORD and targeting officer's guidance, and intelligence capabilities at echelon.
  F-2. In a joint role, CJCSI 3370.01D establishes the target development standards that must be met to
  present an electronic target folder to a validation authority.
  EXAMPLE TARGET INFORMATION FOLDER
  F-3. Target information folders (TIF) have proven to be an efficient and effective way of tracking
  information related to targets that require more than a cursory recommendation. The TIF typically contains
  three primary sections of data, they are listed and described below.
  F-4. The first section is the administrative data located at the top of every page of the TIF. The
  administrative data contains the following data fields:
  * Target System or HPTL category- Depending typically on the guidance from the commander,
  FSCOORD, or unit SOP, the targeting team will track targets by the systems, warfighting
  functions, or HPTL items they are attempting to affect.
  * Supported Operation- This will delineate which phase, critical event, or operation this target is
  supporting.
  * Date of Information (referred to as DOI) - This specifies the latest date of intelligence supporting
  this target.
  * Basic Encyclopedia (BE), Counter-Terror Identification (CTID), Unique Identification (UID),
  Target Number- Depending on the target type or how the target is defined will determine the
  BE/CTID/UID/ Target Number. Any target being nominated to the joint level must have a BE,
  CTID, or UID. Targets at the tactical army level should be assigned a target number. These target
  numbers are unit or SOP based.
  * Location/ Military Grid Reference System (referred to as MGRS) - Typically in MGRS coordinate
  form that can provide a horizontal accuracy sufficient to make the target geospatially distinct from
  any other target in the surrounding area. In some cases, a common name is added to the location
  data field to further identify the target within an AO. For example, if a target is within a geographic
  area without civil identification such as city, village, or town name.
  * Targeting Tasks or Objectives- This data field provides the operational linkage to the target. Not
  to be confused with supported operation, this field identifies the specific operational effort that
  will be aided in creating the desired effects against this target.