Chapter 3 header image


Joint-Service/Navy-Wide Systems

Automated Digital Network System

Nighttime Photo of several large ground-based Satellite Dishes

Description: The Automated Digital Network System provides ship and shore Internet Protocol (IP) connectivity, facilitating the merging of "stove-piped" information-exchange systems and increasing the effective throughput of existing radio frequency (RF) circuits. Specifically, it automates the routing and switching of tactical and strategic C4I data via Transmission Control Protocol/ Internet Protocol (TCP/IP) networks linking deployed battle group units with each other and with the Defense Information Systems Network (DISN) ashore via multiple RF paths. ADNS uses Commercial Off-the-Shelf (COTS) and Non-Developmental Item (NDI) Joint Tactical Architecture (JTA)-compliant hardware (routers, processors, and switches), and commercial-compliant software in a standardized, scalable, shock-qualified rack design.

Program Status: Two hundred and twenty-four shipboard and four shore sites (Network Operations Centers) have been fielded through Fiscal Year 2001. Afloat installations include amphibious ships, carriers, cruisers, command ships, destroyers, and frigates; the shore installations of multiple ADNS nodes have been fielded at the three Naval Computer and Telecommunications Area Master Stations (NCTAMS) as well as in Bahrain. Plans for Fiscal Year 2002 and beyond are to continue battle group fielding in accordance with the Fleet Commander-in-Chief coordinated IT21 fielding plans.

Developer/Manufacturer: Science Applications International Corporation, Arlington, Virginia.

ATDLS Link-11/16/22
Advanced Tactical Data
Links Systems Program

Description: Link-11 is the common tactical data link for all U.S. Navy and allied ships not equipped with Link-16; it will remain in service until at least 2015. Link 16 is the DoD's primary Joint Tactical Data Link. In accordance with the Joint Tactical Data Link Management Plan (JTDLMP), the Navy is implementing Link 16 in most of its link-capable platforms. The program delivers Link 16 hardware to the Fleet and funds planned improvements. Link-22 is a multi-national tactical data link and will implement the Tactical Data Link Joint Message Standard (J-Series). The ATDLS program, improves advanced tactical data link connectivity, promotes equipment commonality and interoperability, and provides training and fleet support. Major supported efforts are as follows:
These projects will allow more effective employment of fleet units by increasing timeliness, accuracy, and content of tactical data transfer.

Program Status: Delivery of initial CSDTS production units began in early Fiscal Year 1998. CDLMS delivery began in Fiscal Year 2000. Next-Generation C2P is scheduled for IOC in 2004. Link-22 is a co-development program with seven NATO countries and is in the latter half of its research and development phase with IOC scheduled for 2006. Three Multiple Universal Link Translator System (MULTS) vans are deployed with Commander-in-Chief, U.S. Naval Forces Europe (CINCUSNAVEUR), and five Multiple UnitLink Test and Operational Training System (MULTOTS) units are operated worldwide.

Developer/Manufacturer: GAC, Valley Forge, Pennsylvania; Logicon, San Diego, California; and Rockwell International, Dallas, Texas.

Challenge Athena Commercial
Wideband Satellite
Communications Program

A Shipboard Challenge Athena Antenna

Description: Challenge Athena is a full-duplex, high data-rate (1.544 Mbps) communications link (C/Ku wideband) capable of providing access to high-volume primary national imagery dissemination; intelligence data base transfers; video tele-conferencing, tele-medicine, and tele-training services; and various other computer data systems. Challenge Athena also supports tactical strike and Tomahawk mission planning, the Defense Information Support Network (DISN) Joint Interoperable Networks (JIN), including Joint Worldwide Intelligence Communications System (JWICS), Secret/ Unclassified Internet Protocol Router Networks, and Air Tasking Order/Mission Data Update (ATO/MDU) transmissions. The Challenge Athena system uses commercial satellite connectivity and COTS/NDI equipment to augment existing, extremely overburdened military satellite communications systems.

Program Status: Current funding provides Challenge Athena terminals to approximately 40 Joint Task Force command-capable ships by Fiscal Year 2005. Concurrent with this effort is the extension of medium data-rate connectivity to other accompanying surface warships, amphibious assault ships, and logistics support ships via a battle group IT-21 wide-area network that will eventually provide these capabilities to all Navy ships. Future transponder leasing options are being evaluated.

Developer/Manufacturer: Various COTS/NDI.

Cryptologic On-Line Trainer

Description: COLT is an organic training system for operators and decision-makers on systems that use TAC-N computers. COLT emulates the operations of cryptologic systems such as Combat DF, Cooperative Outboard Baseline Logistics Update (COBLU), Ship's Signals Exploitation Equipment (SSEE), and Battle Group Passive Horizon Extension System-Surface Terminal (BGPHES-ST). It will interface with the Battle Force Tactical Training (BFTT) System to include the Joint Tactical Combat Training System (JTCTS). The system is based on an open, distributed architecture to provide commonality, reduce costs, make efficient use of training networks, and minimize data-transfer requirements. COLT minimizes change to operational systems and maximizes the use of resident computer resources for simulation, and is the first step toward embedding a software cryptologic training capability in existing and future systems.

Program Status: COLT software version updates are continuing. These updates incorporate additional training tasks and revise training as installed system baselines change.

Developer/Manufacturer: SPAWAR Systems Center, San Diego, California.

Cryptologic Unified Build

Photo of a US Navy Battlegroup in a close formation

Description: CUB is an evolving, integrated set of software applications that run on the Global Command and Control System-Maritime (GCCS-M). CUB provides the Defense Information Infrastructure-Common Operating Environment (DII-COE) compliant components of GCCS-M for Navy Tactical Cryptologic Systems. It eliminates duplication of effort, reduces training needs, and supports maintainability and interoperability. CUB software is the backbone for the Common Cryptologic Workstation (CCWS), which is an all-purpose workstation on a "system high" Sensitive Compartmented Information (SCI) LAN. Certain CUB segments provide an interface to the shared functionality and database repositories of the GCCS-M common operation environment. Access to certain data is not necessarily via a TCS system but via a CUB segment.

Program Status: The CUB development cycle is in "lock step" with the GCCS-M development team and release schedule. Frequent technical interchanges with the GCCS-M engineers and adherence to DII COE compliance procedures and standards ensures the CUB segments continue to support the evolving architecture. CUB is installed in CG-47 Aegis cruisers, DD-963 destroyers, DDG-51 Aegis destroyers, LHD-1 amphibious assault ships, aircraft carriers, amphibious command ships, and certain cryptologic shore sites.

Developer/Manufacturer: SPAWAR Systems Center, San Diego, California.

Digital Modular Radio/Joint
Tactical Radio System-Maritime

Description: The Digital Modular Radio (DMR) /Joint Tactical Radio System-Maritime (JTRS-M) will be an open architecture, scalable, modular and software-reprogrammable system that will allow for upgrades to satisfy existing and future communications waveforms. The baseline DMR will satisfy the UHF SATCOM, UHF Line of Site (LOS) and Single Channel Ground and Airborne Radio System (SINCGARS). Also, DMR requirements will be a multi-mode and multi-band system providing a demand adaptive communications capability. The DMR requirements are derived from the main body and annex B (Maritime and Fixed Station Domain) of the Joint Tactical Radio System (JTRS) Operational Requirements Document (ORD) Version 2.2 of 30 January 2001 (the JTRS ORD will be updated on an annual basis). It is being fielded as a modernization of UHF SATCOM radios on ships (WSC-3) and ashore (WSC-5). It will also be an enabler of IT-21 capability by implementing full Demand Assigned Multiple Access (DAMA) standard compliance and higher data rate waveforms. In FY 2003, DMR will transition to JTRS-M as the Manufacturer implements changes to the hardware and software to bring the system into compliance with the JTRS Software Communications Architecture (SCA) as developed and maintained by the JTRS Joint Program Office (JPO). The first iteration of JTRS-M will be designated Block I and will satisfy the narrowband waveform requirements of the JTRS ORD noted above. This will include HF, VHF, UHF Line-of-Sight (LOS), and current and future UHF SATCOM requirements. JTRS-M Block II will be a follow-on contract that will provide for narrowband and wideband requirements derived from the ORD to include the Wideband Networking Waveform. Block II is expected to reach Milestone III in FY 2006.

Program Status: The program is an ACAT III program. In September 1998, two Firm Fixed Price, Indefinite-Delivery/Indefinite-Quantity contracts were signed with Motorola and Raytheon to begin development and delivery of the DMR Service Test Models. Motorola was awarded the LRIP contract in February 2000, and initial delivery occurred in October 2000. The program is currently undergoing Developmental Testing with Operational Testing expected to occur in FY 2002.

Developer/Manufacturer: Motorola, Inc., Phoenix, Arizona.

DoD Teleport

Photo  of Operations Specialists aboard USS John F. Kennedy (CV-67) tracking contacts from Carrier Directions Center

Description: Department of Defense Teleport is an initiative to provide tactical users a worldwide communications interface between the space segment and the shore infrastructure across multiple RF (radio frequency) media (military and commercial bands). Teleports will provide inter-theater reachback into the Defense Information Support Network (DISN) and intra-theater communications support for tactical users. The Navy operates and maintains three of the six identified major Teleport sites.

Program Status: In May 2000, the Office of the Secretary of Defense selected the Defense Information Systems Agency (DISA) as the Executive Agent. The Joint Requirements Oversight Council approved the DoD Teleport ORD and architecture in July 2000. It is an ACAT 1AM program reporting to ASD (C3I) for Milestone Decision Authority, and received congressional new start approval September 2001. The Navy expects Clinger-Cohen Authorization to be completed January 2002. Based on an initial September 2001 Integrating Integrated Product Team (IIPT) meeting, and and follow on meeting with the OSD C3ISR/Space Systems Overarching Integrated Product Team (OIPT) leader, a decision to forego a Milestone A decision and press forward with a Milestone B is being pursued and expected to be completed March 2002.

Developer/Manufacturer: N/A. Teleports is an integration of existing Standardized Tactical Entry Point (STEP) sites and Naval Computer and Telecommunications Area Master Stations (NCTAMS) assets.

Defense Message System

Description: The DMS initiative is an Office of the Secretary of Defense (OSD) mandated program designed to eliminate the multitude of expensive stovepipe legacy record messaging systems that provide organizational and individual message traffic between operational units. The DMS architecture has been derived using the MROC (Multicommand Required Operational Capability) requirements, and has been targeted to provide the Services and agencies with a high assurance essaging capability. The DMS provides messaging, directory, and management services.

Program Status: Current DOD implementation of DMS is in line with guidance to close the DMS Transitional Hubs (DTHs) by 30 September 2003.

Developer/Manufacturer: Lockheed Martin, Manassas, Virginia.

next page back page contents page Return to the Table of Contents