Tactical Control System (TCS) General TCS is a DoD program to provide joint warfighters with a surface command, control, communications and data dissemination system for UAVs. It has made considerable progress over the past year and demonstrated initial functionality and versatility in a variety of land- and sea-based exercises. TCS is composed primarily of software, but also related hardware and additional ground/ship support equipment, to enable: Software interoperability on host-Service computer platforms; Five levels of scalable interaction, from passive imagery/data receipt to full AV control (see figure below); and Rapid imagery dissemination to tactical users through a variety of C4I system interfaces. It is being designed as an open architecture system to facilitate future hardware and software enhancements and will comply with: ASD(C3I)’s Joint Technical Architecture; Distributed Common Ground System (DCGS) standards of the Common Imagery Ground/Surface System (CIGSS); and The Defense Information Infrastructure/Common Operating Environment (DII/COE). Initially, TCS will be integrated with Outrider and Predator and will incorporate the five levels of interaction. Integration planning has also been initiated for Pioneer and Hunter. Subsequently, receipt of payload information from the HAE UAVs will enable TCS’s rapid dissemination of their imagery and data to selected C4I systems. TCS thus provides a migration path to interoperable UAV employment with a common interface to the C4I infrastructure. NATO is interested in TCS’s range of flexible options for Alliance operations. The NATO Industry Advisory Group’s Project Group 35 (NIAG PG/35) has initiated a study to define a common, interoperable NATO UAV GCS architecture. In September 1998, TCS will take part in an interoperability demonstration with a German UAV. FY 1997 Activities JROC Activity The JROC fully supports TCS as critical to the successful development and employment of UAV systems (see p. 18). In JROCM 173-96, which updated UAV priorities, the JROC emphasized the need for commonality and interoperability in the control of UAVs and dissemination of their data . Programmatic Activities In January 1997, the Expanded Defense Re-sources Board (EDRB) approved $63 million in additional funding for FY 1998 – 03 to accelerate the program. TCS is being developed as a three-phase effort (see table above-right).9 Phase I is an incremental build to demonstrate increasing TCS functionality from passive receipt of data to payload and multi-UAV control. Its three fieldable prototypes represent the various TCS operational environments: sea-based, HMMWV-shelterized, and in a Tactical Operations Center (TOC). Phase II will continue demonstrations and acquire six low-rate initial production (LRIP) systems for an Initial Operational Test and Evaluation (IOT&E) program. Phase III will include production, support, preplanned product improvements (P3I), and incorporation of additional C4I interfaces. In March 1997, contracts were awarded to General Atomics and Alliant Techsystems for TCS integration into Predator and Outrider, respectively. In November, Logicon was selected to provide an off-the-shelf TCS Mission Planner. An RFP for a TCS Systems Integrator is planned for release to industry in 2Q/FY 1998, with contract award in 4Q/FY 1998. In coordination with DARO, the Assistant Secretary of the Navy (Research, Development and Acquisition) (ASN(RD&A)) formed an Acquisition Coordination Team (ACT) to support the TCS program after designating it an ACAT II program on 12 September 1997. Demonstrations A TCS prototype took part in the Army’s TF XXI AWE in March 1997 (see p. 8). During April and May lab demonstrations, TCS showed it could receive Predator SAR and DarkStar EO data, respectively. It hosted demonstrations at sev-eral locations, including the Pentagon. During Joint Warrior Interoperability Demonstration 1997 (JWID-97) in June, it was used in a sensor-to-shooter in-teroperability demon-stration aboard the USS Stennis. In mid-summer, it performed shipboard data receipt and dissem-ination of simulated UAV payload imagery gen-erated by MUSE.10 In August, TCS/MUSE sup-ported the Army’s Exercise Ulchi Focus Lens 97 (see p. 9). TCS’s use during exercises has shown operators at all levels what it can do and what is planned for the future. In addition, the exercises demonstrated successful data distribution to various C4I nodes and also provided valuable feedback to developers. Near-Term Plans With enactment of its FY 1998 budget, the TCS Program Office will: Continue functionality demonstrations of land- and sea-based TCS units; Procure a Predator AV and GCS with additional funds provided (see p. 3); Select a TCS/LRIP System Test and Integration contractor; Downselect for mission and payload planning application; Complete the TCS TEMP; Coordinate TCS incorporation into the Pioneer and Hunter programs; Participate in joint warfighting and Service experiments and exercises, to include Predator and Outrider demonstrations; and Engage in multi-UAV simulation efforts.