• Military Menu                       

• Introduction
• Systems
• Facilities
• Agencies
• Industry
• Operations
• Countries
• Hot Documents
• News
• Reports
• Policy
• Budget
• Congress
• Links

• WMD
• Intelligence
• Homeland Security
• Space

	Director, Operational Test & Evaluation
	FY98 Annual Report

SYSTEM DESCRIPTION & CONTRIBUTION TO JOINT VISION 2010

The Class 2M Joint Tactical Information Distribution System (JTIDS) terminal is the last of the Class 2 second generation of the JTIDS family. The Army JTIDS is comprised of the Class 2M terminal, the JTIDS Terminal Controller, and the JTIDS antenna; and was uniquely designed to meet Army Link 16 requirements. Host platforms for Army JTIDS include the Forward Area Air Defense (FAAD) Command and Control, Patriot, and Theater Missile Defense Tactical Operations Centers. A small number of Class 2M terminals were provided to the Theater High Altitude Area Defense (THAAD) program manager for integration engineering. The Army has decided to acquire 100 Class 2M terminals and satisfy its remaining Link 16 requirements with an Army variant of the next generation Link 16 terminal¾ the Multifunctional Information Distribution System Low Volume Terminal.

The Army JTIDS completed IOT&E in November 1996. The results indicated that the system was operationally effective but not operationally suitable. The key suitability problem was the low reliability of the system (Mean Time Between Operational Mission Failure of 26 hours compared to a requirement of > 323 hours. Other key deficiencies included operator training, publications, and Army JTIDS network design and management. These deficiencies were unresolved due to non-existent Army capability. Full-rate production was approved but the Army was directed to complete a Corrective Action Plan to improve suitability. The Corrective Action Plan modified both Class 2M and JTC software to: (1) improve troubleshooting and rollover of crypto-variable codes; (2) revise the Army JTIDS training syllabus so that it includes more "hands-on" training, (3) modify fault isolation and Built-In Test routines; and (4) rework operator publications.

A FOT&E was conducted at Fort Bliss, TX, during November and December 1997. The FOT&E evaluated the improved suitability, training and publications portions of the Army JTIDS network management, and Army JTIDS-AWACS interoperability. Two Army JTIDS systems participated in the test. One system was integrated into a Patriot Information Coordination Center and the other into a FAAD Command and Control shelter.

• Mean Time Between Operational Mission Failure was 44.2 hours compared to IOT&E's 26 hours. This is still significantly less than the required > 323 hours. Key problem areas included Terminal Controller software and changing crypto-variable codes.



• Training and publications were much improved and contained none of the "redlines" and "workaround" procedures present during IOT&E. Soldiers commented positively on the "hands-on" portions of the training.



• The Army established their own interim network design capability at Huntsville, AL, and subsequently successfully demonstrated over-the-air re-keying and over-the-air initialization capabilities during FOT&E.



• Only one successful Link 16 network was established between the Army elements and E-3 AWACS during six attempts.

DOT&E is concerned about the impact of poor Army JTIDS suitability demonstrated during IOT&E and FOT&E. DOT&E's B-LRIP report, released before the Army's IOT&E report, helped focus the Air Defense Artillery Corps' command attention. Subsequently, this resulted in the Corrective Action Plan and other efforts (after FOT&E) to improve Army JTIDS suitability prior to fielding approval. The Army should resist allowing full materiel release until the required system reliability is demonstrated.