Military

TOPIC: Joint Tactical Information Data System (JTIDS).

DISCUSSION: Significant problems were encountered by the ICU when attempting to implement JTIDS network operations among JTID 5-capable units participating in the joint interface. The JTIDS network parameters initially developed and published for use in the area of responsibility (AOR) were incorrect. There were no personnel in-theater (except for one technical representative working at the Control and Reporting Center (CRC) knowledgeable in JTIDS network design and terminal initialization parameters. This lack of knowledge resulted in numerous attempts to make the system work by modifying various timing and initialization parameters without full knowledge of the consequences. This situation was finally corrected by contacting the JTID S Program Office and requesting assistance. Support provided by HQ, ESD TCD-4, was timely. It was able to validate the network configuration that had been developed in-theater and recommend additional terminal initialization settings that improved the performance of the links. ClNCFOR should establish a working group to assess the current method of teaching JTIDS Class I network design and operation for all users. The focus of the assessment should be on defining the operational level at which this knowledge should reside.

LESSON(S): Employment of any tactical data system in real-world operations must be supported by trained planners and operators. Attempting to trouble-shoot network operations from remote locations is extremely difficult and is usually unsuccessful.

TOPIC: Voice and Data Configuration.

DISCUSSION: Many of the interface participants did not have a clear understanding of the various configurations available for data-link interface. A complex data-link interface was employed for Operation DESERT SHIELD. Both joint and combined forces were employed in a number of different voice and data configurations to form a C2 interface. Visualization of the interface is nearly impossible without the development of aids to understand the communications connectivity, operational connectivity, and the resulting C2 connectivity. Once the technical prearranged data items for the data link are received by the interface participants, their understanding of t he interface configuration options can be enhanced if they draw out the various possible combinations for a data-link interface.

LESSON(S): Visualization of the data-link interface will help with trouble-shooting equipment malfunctions, communications outages, connectivity problems, and reconfiguration, when necessary.

One methodology for accomplishing this is:

TOPIC: Coordinating Configuration Changes.

DISCUSSION: Interface units were making unilateral data-link or communications configuration changes without coordinating with the ICU. The data-link interface employed was extensive. Many different participants from all of the U.S. Services, NATO and other allies employed a variety of equipment with varying data-link capabilities. The ICU is charged with the responsibility for managing this extensive network. Various units complicated their efforts by changing communications configurations and data-link configurations unilaterally.

These input changes to the interface tumed a barely manageable situation into an unmanageable situation quickly. At times, coordination with the ICU was missing. The ICU could not quickly determine the current interface configuration or needed changes to maximize the performance of the interface. The ICU had incomplete information.

Changes were necessitated by communications outages or equipment outages. Several units took it upon themselves to make changes to the interface configuration or to the communication configuration without the proper coordination.

LESSON(S): Any changes to the data-link configuration must be made only at the direction of, or with the concurrence of, the ICU. Without the proper coordination, the integrity of the interface is destroyed. There should be a single agency directing changes to the data-link interface. When more than one unit attempts to control the makeup and direction of the interface, there is no unity of effort.

TOPIC: Interface Management.

DISCUSSION: The ICU had problems managing the data-link interface participants. The ICU had problems getting other participating units to execute the game plan for interface management. Using the parameters listed in the Technical Operational Data (TECHOPDAT), combined with the procedures in the TACOPDAT (Tactical Operational Data), the ICU maintains the unity of command. It has the responsibility to the interface participants to deal with communications outages, equipment outages or other interface problems in a timely manner to include controlling the direction the interface takes as communications, equipment availability, or unit availability changes. The ICU had reliable communications to most of the data-link participants, but was sometimes unable to manage the interface properly. Some of the interface participants had priorities different than the ICU affecting their participation. Several of the interface participants were interested in only mutual support of like airborne assets. Several of the interface participants did not have direct communications to the ICU. Each of the interface participants has the responsibility to contribute to the interface to the best of his ability. This includes informing the ICU of any anticipated outages or equipment configuration problems that are discovered.

LESSON(S): The ICU must direct the interface participants to contribute individually towards maintaining the interface, and be responsive to the need for adjusting the communications, connectivity or configuration of the interface. Conversely, the interface participants must coordinate with the ICU on any matter that affects the communications, connectivity or configurations used in the data link interface.

TOPIC: Data-link Performance Monitoring.

DISCUSSION: Periodic data-link performance monitoring by the ICU and selected interface participants was sporadic. Link monitoring and performance feedback by interface participants (coordinated through the ICU) must be conducted periodically to assess link status. This performance feedback can identify potential problems as well as assist in the trouble-shooting process. During the initial stages, link monitoring was infrequent, and the troubleshooting process was hit or miss. Some agencies failed to provide necessary equipment to trouble-shoot links, such as LSM- 11, or provided HF frequency analysis, such as chirpsounders. When fielded, automatic linking equipment (ALE) for HF radios may alleviate the shortcoming.

LESSON(S): Continual performance feedback and link monitoring are effective aids in assessing link performance and strengthening the troubleshooting process. Each capable interface participant must develop procedures to ensure that link performance is periodically monitored, assessed and documented.

TOPIC: Logbooks.

DISCUSSION: ICU Logbooks contained minimum required information which was often incomplete or vague. Information in the ICU logbooks concerning data-link performance, reconfigurations, problem description, troubleshooting, or corrective actions was often incomplete if addressed at all. This made any trend analysis or trouble-shooting of deep-rooted problems difficult, if not impossible. Accurate records must be kept by all stations participating in the interface, especially the ICU, to ensure final fixes to problems with the interface or to identify the source of problems. Accurate track counts must be taken at selected locations; perform ance of communications equipment monitored; configuration of the link when problems were encountered; and location of airborne platforms documented to aid in the problem-solving process. Troubleshooting and problem solving are next to impossible without adequate historical data.

LESSON(S): Recommend that ICU personnel be instructed to log information concerning data-link performance, make detailed entries concerning problems or outages and make followup entries outlining corrective actions for problem areas.

TOPIC: Skilled Operators.

DISCUSSION: The ICU needs to have skilled operators using established radio procedures to effectively manage the data-link interfaces. Personnel that work in the ICU should be able to readily provide information about the interface and facilitate answering policy questions. Communications procedures used by the ICU need to be clear and concise. This will provide effective, positive direction to all interface units.

Care should be taken by the ICU to ensure personnel working in or supporting the facility are knowledgeable about the current situation, the data-link interface configuration in use, current frequency assignments, and any other factors likely to affect the interface.

Personnel working in the ICU need to be able to answer questions about the interface in a timely manner. They need to either provide information themselves or be able to frnd answers to questions. A majority of the questions asked of the ICU concerns information needed by a unit to enter the interface. The ICU personnel need to know what current operational parameters, such as frequencies, data filters, or reference points, are in use.

Policy questions for the ICU need to be referred to the Interface Control Officer (ICO). The ICO is the oniy one authorized to make policy decisions affecting the interface. Personnel in the ICU that support the ICO need to be able to address the policy issues (interpret the calling party request), and not make defmitive statements concerning policy.

LESSON(S): The ICU should have knowledgeable personnel that can answer questions or know where to retrieve the defmitive policy-type information.

Table of Contents
Chapter 3: Interoperability, Part 2
Chapter 5: Tactics, Techniques, and Procedures (TTPs)