Tactical Reconnaissance Exchange System Relay [TRIXS]
The Tactical Reconnaissance Intelligence Exchange System (TRIXS) Network is a corp-level line-of-sight (LOS), interactive (transmit-receive), ultrahigh frequency (UHF) network that transmits messages in near-real-time to up to 250 addressees. The TRIXS operates at the SECRET and sensitive compartmented intelligence (SCI) levels.
Four important networks support the dissemination of tactical intelligence. The Tactical Receive Applications (TRAP) and Tactical Data Exchange System Broadcast (TADIXS-B) broadcast networks disseminate global detection and cueing information to users worldwide. The Tactical Information Broadcast Service (TIBS) network disseminates theater area information with tracking accuracy. The Tactical Reconnaissance Intelligence Exchange System (TRIXS) network disseminates tactical intelligence with targeting accuracy.
TRIXS currently supports up to five airborne relays and producers:
- Army's Guardrail Common Sensor (GRCS) on board the RC-12 aircraft
- Air Force Contingency Airborne Reconnaissance System (CARS) on board the U-2
- Army's Airborne Reconnaissance Low (ARL) on the D-7 [starting in 1996]
- Navy's Storyteller (EP-3 / E-8) [starting in 1997 ]
- The fifth source has not been determined, but could be Joint STARS, UAV, or another airborne system.
TRIXS is being integrated into the Integrated Broadcast Service approved by the ASD(C3I)in 1996. The IBS standardized protocols, with compatible hardware and software, were directed by the 1996 House Intelligence Bill. As a part of a larger Intelligence Systems Secretariat/ Intelligence Systems Board (ISS/ ISB) intelligence migration initiative to reduce the number of separate intelligence systems, the Broadcast/ Receive Working Group was formed in 1994 to examine the existing Ultra High Frequency (UHF) intelligence broadcast services and one emerging concept for combining the services (Binocular). The group's objective was to uncover and examine issues surrounding the potential combining of service functionality into a smaller
number of services– functional re-dundancy, inefficiency, and impacts on the user;
resource duplication; formatting issues; band-width contention and to make
recommendations concerning concepts warranting further study.
Sources and Methods
Created by John Pike
Maintained by Steven Aftergood
Updated Tuesday, January 19, 1999 6:50:41 PM