TAMPS core software provides flexible interfaces to a wide variety of USN and USMC C4I systems to provide users near real time updates to weather and intelligence databases. A modular, open systems architecture was developed to satisfy specialized aircraft, weapons and avionics systems requirements while maintaining consistent displays and user interactions across all platforms. Platform unique requirements are provided via a Mission Planning Module (MPM) system that integrates platform developed MPMs with appropriate core libraries and servers providing a complete planning environment for any user platform. This integrated MPM planning environment is used to develop, analyze, store missions and create mission planning products (including digital loads, strip route charts, and pilot kneeboard cards) to support tactical aviation combat operations.

TAMPS is currently hosted on the Navy Standard Desktop Tactical-support Computer 2 (DTC-2) which is comprised of Commercial Off-the-Shelf (COTS) hardware. The bulk of fleet TAMPS installations consists of a DTC-2 unit containing three work stations; one data base administrator station and two mission planner stations. A portable configuration of TAMPS is hosted on the ACE/VME single workstation computer. Future hardware upgrades to be incorporated with TAMPS 6.1.1 include a Solaris workstation with upgrade memory and improved processing speed.

TAMPS evolved from interest in modification of the Strategic Air Command's Deployable Aircraft Planning System (DAPS) to support A-6 and F/A-18 mission planning in December, 1985. DAPS and the McDonnell Douglas Tactical Aircraft Planning System (TAPS) evolved into TAMPS and, at the direction of the Secretary of the Navy, attained initial IOC in December 1986 with two workstations aboard USS Carl Vinson. No IOT&E was conducted prior to fleet release. Responsibility for TAMPS was transferred to Program Executive Officer for Tactical Aircraft Programs (PEO(T)) in August 1991.

FOT&E (OT-IIIA) was first conducted from DEC90 to APR91 on TAMPS S/R 4.2 and the F/A-18 digital storage unit. COMOPTEVFOR concluded that TAMPS S/R 4.2 was potentially operationally effective for mission planning and system support, but NOT operationally effective for mission support, and potentially operationally suitable. Major corrections from recommendations of OT-IIIA were implemented in subsequent software releases and verified by squadron operations with TAMPS S/R 5.1.

OT-IIIC in 1994 concluded TAMPS S/R 6.0 was potentially operationally effective and potentially operationally suitable with recommendations to proceed to OT-IIID contingent upon the resolution of 15 critical software trouble reports (STR) that related primarily to system crashes and major errors in loadout data bases.

OT-IIID Phase I in 1995 concluded S/R 6.0 was potentially operational effective and potentially operationally suitable, though proceeding to Phase 2 was contingent upon the resolution of 26 critical STRs. Phase 2 was concluded in August 1995 and determined that S/R 6.0.3 was operationally effective and operationally suitable and recommended for fleet release.

TAMPS S/R 6.0.5 was determined to be NOT ready for full operational test at the OTRR in May 1996. TAMPS 6.0.5 was to be fully tested in support of F/A-18 Operational Flight Program (OFP) 11C; however, COMOPTEVFOR raised concerns about system stability and human machine interface (HMI) issues discovered during a DT assist period. As a result, the planned test period (OT-IIIE, test plan signed October 1996) was downgraded to an OA with no more than a limited fleet release, to only those units with OFP-11C and critical data upload requirements, to be recommended at the end of the test.

The latest version of the TEMP, Revision B, dated January 15, 1997, was approved in April 1997. The Test Plan for OT-IIIF was also approved by DOT&E and TAMPS 6.1/6.1.1 is currently in test. A Quick Reaction Assessment of TAMPS 6.1 was released in AUG97 to support fleet release of this version of the software hosted on existing hardware. This interim report concluded that TAMPS 6.1 hosted on the DTC is projected to be operationally effective and operationally suitable. However, TAMPS 6.1 hosted on the portable ACE/VME computer is projected to be operationally effective, but not operationally suitable. Version 6.1.1 is functionally identical to 6.1 but is hosted on a Sun ULTRASPARC workstation. System enhancements observed during the test include greatly improved system reliability, greatly improved human machine interfaces, and a 400% improvement in data storage capacity.

TAMPS has evolved from a stand alone mission planning support system into an integral part of key weapons systems including the F/A-18C/D/E/F, F-14D, E-2C, HARM, Joint Standoff Missile (JSOW), and Joint Direct Attack Missile (JDAM). Other key functionality includes operations with Global Positioning System (GPS), Tactical Electronic Reconnaissance Processing and Evaluation System (TERPES), Common Operational Modeling, Planning and Simulation Strategy (COMPASS), and the ARC-210 radio. TAMPS has become a critical mission planning and data upload system that will be required to be both operationally effective and operationally suitable in order to achieve mission success. Current software releases provide basic functionality, but system stability and user interface problems continue to hamper the system's effectiveness.

DOT&E has been directly involved with oversight of TAMPS T&E and the development of the test strategy for S/R 6.1 (OT-IIIF). Key issues in determining the effectiveness and suitability of TAMPS that remain are system stability ("crashes"), Human Machine Interface issues, and new functionality support of major weapons programs. TAMPS 6.2, scheduled for testing in FY98, will include many key new functionality's such as with JSOW, JDAM and SLAM-ER capability. Continued emphasis from the service OTA, with DOT&E oversight, on comprehensive OT of future software releases will help to insure continued product improvement of this evolving mission planning system.

The ACE/VME portable version of TAMPS hardware continues to perform very poorly in test and operation. It was procured before adequate testing had been done and is also plagued with poor quality control in production.

Test resources/Hardware. Gathering suitability data at VX-9, the Navy's tactical operational test and evaluation squadron, was limited by the reality of having only one DTC system for test. Excellent effectiveness data was gathered by combining test and training with air wing training at NAS Fallon, Nevada. For operational test, fleet squadrons used TAMPS 6.1 hosted on hardware at the Naval Strike and Air Warfare Center in conjunction with standard air wing training events; making the scenarios very realistic.