Joint Tactical Information Distribution System

From Wikipedia, the free encyclopedia
  (Redirected from JTIDS)
Jump to: navigation, search
Joint Tactical Information Distribution System Users, 1990

The Joint Tactical Information Distribution System (JTIDS) is an L band TDMA network radio system used by the United States armed forces and their allies to support data communications needs, principally in the air and missile defense community. It provides high-jam-resistance, high-speed, crypto-secure computer-to-computer connectivity in support of every type of military platform from Air Force fighters to Navy submarines.

The full development of JTIDS commenced in 1981 when a contract was placed with Singer-Kearfott (later GEC-Marconi Electronic Systems, now BAE Systems E&IS). Fielding proceeded slowly throughout the late 1980s and early 1990s with rapid expansion (following 9/11) in preparation for Operation Enduring Freedom (Afghanistan) and Operation Iraqi Freedom. Development is now carried out by Data Link Solutions, a joint BAE/Rockwell Collins company.

Overview[edit]

JTIDS is one of the family of radio equipment implementing what is called Link 16. Link 16, a highly-survivable radio communications design to meet the most stringent requirements of modern combat, provides reliable Situational Awareness (SA) for fast-moving forces. Link 16 equipment has proven, in detailed field demonstrations as well as in the AWACS and JSTARS deployment in Desert Storm, the capability of basic Link 16 to exchange user data at 115 kbit/s, error-correction-coded. (Compare this to typical tactical systems at 16 kbit/s, which also have to accommodate overheads in excess of 50% to supply the same transmission reliability.)

While principally a data network, Link 16 radios can provide high quality voice channels and navigation services as accurate as any in the inventory. Every Link 16 user can identify itself to other similarly equipped platforms at ranges well beyond what Mark XII IFF systems can provide. Additionally, Link 16-equipped platforms capable of identification through other means (such as radar and TENCAP Blue Force Tracking) can pass that "indirect" identification data as part of its SA exchange. The capabilities of Link 16 are best represented by the JTIDS or its follow-on Multifunctional Information Distribution System (MIDS) terminals. The TADIL-J message format forms the basis for the mandates in the DoD Tactical Data Link Management Plan.

There are benefits to the full-scale implementation of the two key elements of Link-16: (1) the message "catalog" and (2) the specific radio waveform (i.e., frequency hopped, Lx-band CPSM, spread-spectrum and Reed-Solomon coding, omni-directional broadcast). Link 16 terminals implement the "NI" node-to-node protocols as well as one or more of the ICD-compliant user interfaces.

In a typical theater of operations combat forces and elements that are deployed to gather information tend to be scattered, are not always associated with a single unit, may even belong to different services and are not always well coordinated. As a result considerable information may exist about both friendly and enemy forces but the elements that possess that information often are not aware of the combat units who need it. Conversely, combat elements need information about both friendly and enemy forces but have no knowledge about who has it. Classically these "disconnects" have often made the difference between success and failure of a particular military mission. Conventional circuit oriented communications cannot solve this problem. With JTIDS people who have information can broadcast it without explicitly knowing where it is going and combat elements can filter the composite data stream to extract exactly what they need (and no more). One could argue that this is inefficient since more information is being conveyed over the network that any single user wants or needs but given the inability to precisely coordinate information sources and information users JTIDS is the only available architecture that meets the information distribution needs of the modern battlefield. There are situations where specific circuit oriented communications are necessary. For instance the transmission of a command to a combat unit to attack a specific target. It is also reasonable to attempt to exploit the security and jam resistance of JTIDS to accommodate some present communications such as voice. As a result these circuit oriented capabilities were included in the design. At the time this was done, there was concern that operators who were used to dealing with conventional communications would gravitate toward replicating the circuits they were used to over JTIDS at the expense of the new and more responsive architecture. To some degree this seems to have happened. I don't know how to fix it but the capacity concerns and overloading are a symptom of this problem. JTIDS needs to be viewed as a unique and precious resource that does a specific and necessary job better than any other system. For emerging communications needs they should be evaluated and if the specific JTIDS benefits are not needed the problem should be solved by a more conventional approach. JTIDS is bound by a set of parameters dictated by its unique properties in a way that makes it extremely difficult to make significant adjustments to its parameters. It has sufficient capacity to accomplish its primary task (situational awareness) and has some modest additional capacity to accommodate communication tasks that would not justify adding more equipment to a combat unit. This capability, however needs to be used sparingly and carefully so that the primary JTIDS objective is not compromised.

—A description of the JTIDS system from the original MITRE program manager Eric Ellingson

Origin and history[edit]

JTIDS began with an advanced planning study sponsored by the Air Force Electronic Systems Division (ESD) Advanced Plans (XR) at L.G. Hanscom Field. The study was conducted by The MITRE Corporation in 1967 and the principal investigators were Vic Desmarines who later became MITRE President and Gordon Welchman aho had been instrumental in breaking the German Enigma code as the head of "Hut 6" at Bletchley Park England. Gordon wrote a book titled "The Hut 6 Story" which described his activities and contains some additional information about his work at MITRE. The study concluded that on the battlefield valuable information was available that was not getting to the combat forces that needed it because of fundamental deficiencies in communications architecture. Gordon suggested a radical architecture where elements that had critical information could broadcast it and units that needed the information could selectively process what was of immediate value. This was a significant departure from the circuit oriented communications architectures then in use and a way to eliminate over crowding and confusion in the radio nets used to interconnect aircraft and some ground forces. A second recommendation was the need for a consistent and reliable basis for position which was available to all combat elements dubbed a "Common Position Grid". The overall study was called "Control and Surveillance of Friendly Forces" CASOFF.

The advanced planning study was well received both at MITRE and ESD and it was decided to pursue a practical design to see if these ideas could be translated into a usable system. In 1968 MITRE Technical Director John H. Monahan appointed C. Eric Ellingson to head this effort and Ellingson put together a technical team to pursue these ideas. Early on it became apparent that the CASOFF architecture was sufficiently radical that a "proof of concept" activity was needed to better understand and ultimately demonstrate the feasibility and benefits of such an approach. The demonstration system used a synchronized Time Division Multiple Access architecture and incorporated position location as an integral part of the communications process. Because funds were extremely limited every effort was made to use already available equipment. Transmitters were surplus AN/APX-25 IFF transponders and data processing was accomplished using surplus IBM 4piTC-2 computers that were obtained from the F-111 terrain avoidance program. The unique components called the Control and Display Units (CDU) were built in the MITRE laboratory.

By 1970 an operating TDMA system had been constructed and ground stations were installed at Boston Hill in Andover MA, Millstone Hill in Groton MA, MITRE in Bedford MA and Prospect Hill in Waltham MA. An airborne terminal was also installed in an ESD T-29 Navigation Trainer. Tests of both the communications architecture and position location capability were conducted and the overall system design was shown to be practical. Note that this demonstration preceded GPS, Ethernet and the internet each of which incorporated similar principals. It is also worth noting that these experiments would not have been possible without the support of John Klotz of DOD/DDR&E.

In 1972 General Ken Russell, the AWACS System Program Office chief asked Ellingson if MITRE could support a 1973 demonstration of AWACS to key NATO personnel in Europe. The idea was to bring the AWACS data to the ground command and control centers in selected locations throughout Europe to show how AWACS could augment their existing air defense capability. Russell thought that the MITRE CASOFF demonstration system could do the job. Ellingson responded in the affirmative and immediately set about to implement the needed interfaces with the various NATO systems and equipping a KC135 aircraft that was to be used as a relay.

In 1973 the AWACS demonstration took place with interfaces to the British Linesman system, the French Strida II system, the NATO Ground Environment System in Germany and an element of the U.S. 407L Tactical Command and Control System in Belgium and 407L systems at Sembach and Neu Ulm in Germany. An Army NIKE site at the Fliegerhorst Caserne near Hanau Germany was also equipped. The demonstration was very successful and generated great NATO interest in both AWACS and JTIDS.

During this period the name of the program underwent several iterations. John Klotz didn't like acronyms and dubbed the program Tactical Position Location/Common Grid Capability which immediately became Tipplekeg. Next the program was called Position Location Reporting and Control of Tactical Aircraft (PLRACTA). At the time of the first European demonstration the program was known as Seek Bus. Finally in 1973 DOD created a joint program office with the Air Force as Executive agent and Col. Breeden Brentnall was appointed as System Program Office Chief. The Joint Service SPO was co-located with Ellingson's development group at MITRE. From then on, the program was officially known as Joint Tactical Information Distribution System (JTIDS).

A second European demonstration of AWACS and JTIDS was conducted in 1975 under the direction of AWACS SPO Director Gen. Larry Skantz. An interface with the Navy NTDS system was added and demonstrated aboard a Guided Missile Cruiser in the Mediterranean. Dignitaries were able to view AWACS data at various NTDS locations including a Nuclear Aircraft Carrier. As a result of these demonstrations, and resulting NATO interest, a NATO JTIDS program was instituted called Multifunction Information Distribution System (MIDS).

During this period contracts were awarded to Hughes Aircraft (Ground Systems Group) to develop a terminal suitable for operational use in AWACS and ground command and control systems and to Singer Kearfott Corporation, now BAE Systems, to develop a terminal suitable for fighter aircraft installation. The Hughes effort was led by Bob Kramp and the Singer effort by John Sputz. In concert with contractor efforts a MITRE team led by Myron Leiter and consisting of communications and digital signal processing engineers refined the JTIDS design to optimize interference rejection and link performance. The results of these efforts were incorporated into performance specifications and provided guidance to the contractors. Operational considerations were provided by experienced Air Force combat pilots Col. Ken Kronlund and Col. Cliff Miller as well as valuable inputs from the Air Force Tactical Fighter Weapons Center. A pair of jet instrument trainers were equipped with F-15 like displays and were used to evaluate display techniques and understand pilot work load and benefits.

Ellingson was promoted to Associate Technical Director of the MITRE Command and Control Division in 1979, became Technical Director for the MITRE Communications Division in 1982 and in 1986 Technical Director for the MITRE Command and Control Division. During this period he did not have day-to-day management responsibility for the program but did have oversight responsibility. Ellingson retired from MITRE in 1989.

JTIDS was not created by a single individual. Rather it was the culmination of a group of individuals each having expertise in specific disciplines including but not limited to system engineering, operational analysis, cost benefit analysis, message standards, software development, communications, signal processing, vulnerability analysis, error detection and correction, antenna design, multipath analysis, electromagnetic compatibility mechanical engineering, navigation, specification generation and others. For a considerable period during JTIDS conception as many as 50 people were employed full-time in its development with as many as 50 more in part-time supporting roles. In the ensuing years the program has transitioned from an intensive development effort to a more classical acquisition effort. Development has continued but efforts have been oriented more toward incorporation of breakthroughs in technology and efforts to improve quality and reduce size, weight and cost. In the early 1990s the Navy took over the executive management of the program. As the program has expanded throughout the U.S services and NATO a great deal on operational innovation has occurred driven by the basic flexibility of the architecture and the imagination of the operational user. As a result the operational utility of the system has been enhanced over what was originally envisioned by the early developers. Although the JTIDS system has been a long time in development most of the technology is still "state of the art" and the system should be viable for the foreseeable future.

JTIDS is also used by other members of NATO.

See also[edit]

References[edit]

External links[edit]