[ Navy Training System Plans ]
N88-NTSP-A-50-9301C
March 1999
November 1998
PART I - TECHNICAL PROGRAM DATA
Section I.A. TITLE - NOMENCLATURE - PROGRAM
1. Naval Mission Planning System (NavMPS), AN/UYQ-81(V)
2. Program Element Number: 0204571N
Section I.B. SECURITY CLASSIFICATION
1. Selected System Capabilities: SECRET
2. Hardware: UNCLASSIFIED
3. System Description: UNCLASSIFIED
4. Navy Training System Plan: UNCLASSIFIED
Section I.C. NTSP PRINCIPALS
OPNAV Principal Official (OPO)
Program Sponsor: CNO (N6/N62H)
OPO Resource Sponsor: CNO (N6/N62H)
MPM Resource Sponsor: CNO (N88/N880G9)
Marine Corps Program Sponsor: CMC (APW)
Developing Activity (DA): Program Executive Office for
Tactical Aircraft Programs
(PEO(T))/PMA233
Training Agency (TA): CNET/CINCLANTFLT/
CINCPACFLT/MCCDC
Training Support Agency (TSA): COMNAVAIRSYSCOM (PMA205)
Manpower and Personnel (M&P)
Mission Sponsor: CNO (N1, N7),
COMNAVPERSCOM/CMC (ASM)
Director of Naval Training: CNO (N7)
Commandant of the Marine Corps
(CMC) Manpower Management: CMC (MMOA-2, MMEA-84)
Setion I.D. SYSTEM DESCRIPTION
1. Operational Uses. The Naval Mission Planning System (NavMPS) currently provides the Navy and Marine Corps with an automated method of mission planning and optimizing routes for strike warfare. NavMPS provides mission planners with a computer-based system capable of rapidly processing large quantities of digitized terrain, threat and environmental data, aircraft and weapon system parameters, and imagery. NavMPS is a proven tactical mission planning system that has demonstrated the ability to effectively integrate intelligence data for Navy and Marine Corps fixed-wing and rotary-wing aircraft, stand-off weapons, avionics systems, mission support systems, and unmanned aerial vehicles. Strike planners meet mission objectives by using NavMPS' extensive databases to generate applicable mission planning products (e.g., strip charts, radar predictions, flight plans, and data transfer to Data Storage Units (DSUs), Memory Units (MUs), Mission Data Loaders (MDLs), and Tactical Tape Cartridges (TTCs)). These NavMPS products greatly increase the probability of mission success while providing the capability to greatly decrease mission planning and weapon system preflight preparation time.
Section I.E. DEVELOPMENTAL TEST (DT) AND OPERATIONAL TEST (OT). The NavMPS program is based upon an evolutionary acquisition strategy. This allows the NavMPS to be fielded while enhancements are developed in a series of software releases and hardware updates. NavMPS DTs and OTs are structured to ensure that new software and hardware updates incorporate requirements generated from fleet use of previous software releases and hardware configurations.
1. The Tactical Automated Mission Planning System (TAMPS) 6.1.1 software completed testing during the first quarter of FY98.
2. The Navy - Portable Flight Planning Software (N-PFPS) completed testing during the first quarter of FY98.
3. The TAMPS 6.2 software began testing during the first quarter of FY99. An interim report on TAMPS 6.2 was released 16 December 1998, OPNAV released 6.2K in a stand alone mode on 21 December 1998.
4. The Tactical Strike Coordination Manager (TSCM) software is planned to complete testing during the fourth quarter of FY99.
5. The Joint Mission Planning System (JMPS) developmental software is planned to complete testing during the fourth quarter of FY01.
Section I.F. EQUIPMENT/SYSTEM/SUBSYSTEM REPLACED. The NavMPS strategic goals are to continually provide the fleet strike planners with a user-friendly, automated mission planning system that processes mission critical information quickly, accurately, and reliably.
1. For most activities receiving NavMPS systems for the first time, NavMPS will augment the manual method of presenting threat data to the mission planners and automate mission route planning and chart development.
2. For most activities currently utilizing a NavMPS system, the older version will be replaced by updated hardware and software. This transition provides the fleet a faster system with expanded memory, improved graphics, and media transfer and printing capabilities that are essential to ensuring operational readiness and usability. To those ends the TAMPS software release 6.1 is hosted on the All Computing Environments/Versa Modular Europa (ACE/VME) and software release 6.1.1, a rehost of software release 6.1, is hosted on the SUN ULTRA 2.
3. Currently, the NavMPS hardware is migrating from UNIX based systems to a Personal Computer (PC) based system with the introduction of the autonomous N-PFPS to be followed by JMPS hosted on Navy standard PC computers. Software release 6.2K is hosted on the SUN ULTRA 2 and the Aircraft Carrier Intelligence Center (CVIC) Enterprise 4000 and 2300.
Section I.G. DESCRIPTION OF NEW DEVELOPMENT
1. Functional Description. NavMPS is a stand-alone, software driven computer system currently capable of providing the mission planner with strip charts, radar predictions and reports. Mission routes will be defined by specifying turn points and flight conditions. The outputs from NavMPS can be electronically transferred to aircraft platforms utilizing DSUs, MUs, MDLs, or TTCs as applicable.
a. Software. The software is designed with a modular architecture to support mission planning requirements of the various weapon systems supported by NavMPS. A set of core modules satisfies common requirements and permits the integration of independently developed Mission Planning Modules (MPMs) and Mission Planning Functions (MPFs). This architecture greatly increases the speed and flexibility of NavMPS and allows for the ease of adding and updating specific modules without disturbing the entire suite of NavMPS software or changing the core.
(1) Core Module. The core module is composed of five separate modules. A majority of the functions performed by these modules are transparent to the operator, but they are essential functions that allow total system integration. The core module is required in order to accomplish mission planning and provide accessibility to update all threat data, geographic information, and other data files. The core module also allows the operator to execute mission packages, where relative strike mission planning data is distributed to all applicable MPMs. Listed below are the five modules comprising the core module.
(a) Common Database Access (CDBA) Module
(b) Inter-Process Communications (IPC) Module
(c) Mission Planning Executive (MPE) Module
(d) Data Preparation and Maintenance (DPM) Module
(e) System Functions (SF) Module
(2) MPMs/MPFs. MPMs/MPFs allow the operator/mission planner to utilize the specifications for the type aircraft and/or weapon to be used in order to effectively execute the selected mission. MPMs/MPFs are modularized in order to allow independent development and, as required, allow MPM/MPF modification without disturbing other software elements within the NavMPS. Below are the current MPM/MPF modules and their associated unique functions.
(a) Aircraft Mission Planning Module. The aircraft MPM software and associated Database Administration (DBA) software contain aircraft configurations and parameters as defined in the Naval Air Training and Operating Procedures Standardization (NATOPS) and Tactical Manuals (TACMANs), Naval Strike and Air Warfare Center (NSAWC)
fuel look-up tables and other applicable sources for each aircraft. The following aircraft are currently available in this MPM.
- HH-60H - CH-53D - KC-130F/R/T - UH-1
- AH-1W - CH-53E - P-3C - C-2
- AV-8B - EA-6B - S-3B
- CH-46E - F-14A/B/D - SH-60B/F
(b) F/A-18 MPM. The F/A-18 MPM and DBA software contain the current F/A-18 aircraft configurations and polynomials. In addition, this MPM allows the NavMPS to down-load mission planning data to the aircraft's MU. This MPM will receive updates as required to reflect Operational Flight Program (OFP) changes for the F/A-18 aircraft.
(c) E-2C MPM. The E-2C MPM contains the current E-2C aircraft polynomials. Additionally, it is used to modify Joint Tactical Information Distribution System (JTIDS) parameters on operational networks and provide Enhanced Main Display Unit (EMDU), Multi Function Control and Display Unit (MFCDU), map and geodesic files creation capability.
(d) High Speed Anti-Radiation Missile (HARM) MPM. The HARM MPM contains the current parameters and capabilities of the HARM.
(e) Forward Area Minefield Planning (FAMP) MPM.
The FAMP MPM allows for planning of effective mine disbursement.
(f) Stand-off Land Attack Missile (SLAM) MPM. The SLAM MPM allows planning for missile version 2.42 only.
(g) Global Positioning System (GPS) MPF. The TAMPS software allows for GPS planning.
(h) JTIDS MPF. The JTIDS MPF will allow the E-2C and F-14D MPMs to initialize the data needs associated with a mission.
(i) The following aircraft/systems are candidates for incorporation of independent MPMs/MPFs into the NavMPS.
- E-6A - T-45 - AV-8B (MOMS) - JSOW
- MH-53E - EP-3 - SH-60 - TEAMS
- P-3 - AH-1 (Mid-Life) - V-22 - MIDS
b. Hardware. There are currently four hardware configurations (Desktop Tactical Computer (DTC-II), ACE/VME, SUN ULTRA 2 (1200/1300), and the CVIC system) hosting the TAMPS software. This is due to the evolutionary acquisition process which takes advantage of gains in software and hardware capabilities. Naval Air Systems Command (NAVAIRSYSCOM) (PMA-233) will coordinate the NavMPS hardware quantity and the delivery schedule with the appropriate NavMPS asset managers.
(1) DTC-II. The TAMPS software is hosted on the DTC-II which is comprised of Commercial Off-The-Shelf (COTS), non-developmental hardware. All of these systems will soon be retired from the fleet. The following is a list of the main hardware components of a fleet configured TAMPS DTC-II.
DTC-II HARDWARE COMPONENTS
1 Sun 4/600 w/90 MHZ HyperSPARC CPU w/128 MB RAM
1 Sun GX 8-bit Color Graphics Daughterboard
1 Megatek Dual Frame Buffer Graphics Board
1 8 Port Mux Card
2 Serial Ports
1 Ethernet Port
2 SCSI Ports
1 1553 (VME) Controller
4 4.8 GB Removable Disk Drives
1 1.2 MB 5 1/4" Disk Drive (UNIX/DOS)
1 1.44 MB 3 1/2" Disk Drive (UNIX/DOS)
1 150 MB 1/4" Tape Drive
1 5 GB 8mm Tape Drive
1 CD-ROM Drive
* 19" High Resolution Color Monitors
* Keyboards
* Rugged Trackballs
1 Laser Printer
1 Color Ink Jet Printer/Copier
1 Data Storage Unit Receptacle, and/or MDL,
and/or Tactical Information Device (TID) (as required by site)
* The quantity of monitors, keyboards, and trackballs will be dependent upon the number required by the recipient unit.
This represents a single DTC-II system. Afloat systems on Aircraft Carriers (CV/CVNs) have two DTC-IIs in a client/server environment.
(2) ACE/VME. The TAMPS 6.1 software runs on the portable ACE/VME. These portable systems are for squadrons to use at homebase or on detachment afloat or ashore. All of these systems will be soon retired from the fleet. The following is a list of the main hardware components of a TAMPS ACE/VME.
ACE/VME HARDWARE COMPONENTS
1 ACE/VME w/90 MHZ HyperSPARC CPU w/64 MB RAM
1 24 BIT Graphics Control Board
2 Serial Ports
1 Ethernet Port
1 SCSI Port
2 4.8 GB Disk Drives
1 1.44 MB 3 1/2" Disk Drive (UNIX/DOS)
1 8mm Tape Drive
1 CD-ROM Drive
1 17" High Resolution Color Monitor
1 Keyboard with Integrated Trackball
1 Color Ink Jet Printer
1 Data Storage Unit Receptacle, and/or MDL,
and/or TID (as required by site).
(3) SUN ULTRA 2 (1200/1300). The TAMPS 6.1.1 and 6.2K software is hosted on the SUN ULTRA 2 (1200/1300) which is comprised of COTS, non-developmental hardware. The SUN ULTRA 2 (1200/1300) have the capability to operate as a stand-alone system or may be connected to a Local Area Network (LAN). The SUN ULTRA 2 is year 2000 (Y2K) compliant NavMPS hardware. The following is a list of the main hardware components of a fleet configured NavMPS SUN ULTRA 2.
SUN ULTRA 2 (1200/1300) HARDWARE COMPONENTS
1 Sun Ultra 2 1200/1300 w/ 300MHz Ultra SPARC CPU w/256 MB RAM
1 9 GB Hard Drive
1 18 GB Hard Drive
1 ATM Network Card
1 1.44 MB 3 1/2" Disk Drive
1 CD-ROM Drive
1 8mm Exabyte Tape Drive
1 20" High Resolution Color Monitor
1 Keyboard
1 ITAC Trackball
1 Xerox C55MP Printer
1 DSU Receptacle, and/or MDL, and/or TID (as required by site)
1 Uninterruptable Power Supply
(4) CVIC System. The TAMPS 6.2K software is hosted on the CVIC system which is composed of the SUN Enterprise 4000 (Model 4002), the SUN ULTRA 2 (2300), PC clients and server printers. These hardware components are comprised of COTS, non-developmental hardware and are Y2K compliant hardware. The following is a list of the main hardware components of a fleet configured CVIC system.
CVIC SYSTEM HARDWARE COMPONENTS
Primary Server System (SUN Enterprise 4000 (Model 4002))
1 Four 250MHz CPU w/1 GB RAM
1 126 GB Disk Array
1 Ethernet Controller
1 Fibre Channel Interface
2 ATM Network Cards
1 CD-ROM Drive
1 8mm 14 GB Exabyte Tape Drive
1 17" High Resolution Color Monitor with Creator 24 Bit Graphics
1 Keyboard
1 ITAC Trackball
1 HP 6MP Printer
1 Uninterruptable Power Supply
Permanent Client System (SUN ULTRA 2 (2300))
1 Two 300MHz CPU w/512 MB RAM
1 9 GB Hard Drive
1 18 GB Hard Drive
1 Ethernet Controller
1 Fibre Channel Interface
2 ATM Network Cards
1 1.44 MB 3 1/2" Disk Drive
1 CD-ROM Drive
1 8mm Exabyte Tape Drive
1 20" High Resolution Color Monitor with Creator 24 Bit Graphics
1 Keyboard
1 ITAC Trackball
1 HP 6MP Printer (Server Mode)/Xerox C55MP Printer (Client Mode)
1 DSU Receptacle, and/or MDL, and/or TID (as required by site)
1 Uninterruptable Power Supply
PC Client System
1 Pentium II, 233 MHz Processor w/80 MB RAM
1 3.5 GB Hard Drive
1 Ethernet Adapter
1 PCMICA
1 CD-ROM Drive
1 17" High Resolution Color Monitor
1 Keyboard
1 Mouse
1 Microphone
2 Speakers
Server Printers
1 High-Quality Color Laser Printer (Xerox C55)
1 Black and White Laser Printer (HP 6MP)
2. Physical Description. A fleet DTC-II configuration may contain up to three work stations and a peripheral rack. A fleet ACE/VME configuration will contain one work station and peripherals. A fleet SUN ULTRA 2 (1200/1300) configuration will contain one work station and peripherals. A fleet CVIC system configuration manages the shipboard NavMPS LAN. If a NavMPS activity receives multiple systems, only one peripheral rack will be required. The peripheral rack will contain the DSU receptacles. Depending upon the recipient activity's location and deployability, the NavMPS systems may be in a desktop or rack mounted configuration.
a. Figure 1 is considered the standard NavMPS DTC-II configuration. All other NavMPS DTC-II hardware configurations are derivatives of this setup.
DBA PERIPHERALS MISSION PLANNING
WORK STATIONS RACK WORK STATIONS
TAMPS DTC-II STANDARD AFLOAT CONFIGURATION
FIGURE 1
b. Figure 2 is the NavMPS SUN ULTRA 2 (1200/1300) configuration.
TAMPS SUN ULTRA 2 (1200/1300) CONFIGURATION
FIGURE 2
c. Figure 3 is a generic representation of the NavMPS CVIC system, comprised of the SUN Enterprise 4000 (Model 4002), the SUN ULTRA 2 (2300), PC clients, and printers.
TAMPS CVIC SYTEM OVERVIEW
(Generic Representation of the System)
FIGURE 3
3. New Development Introduction. NavMPS hardware and software is based upon evolutionary upgrades to the previous version. This allows the program to take advantage of hardware and software advancements as well as fleet input to further enhance the NavMPS ability to assist the mission planner.
4. Significant Interfaces. In order for TAMPS to be able to provide reliable and useful data to the mission planner, the databases must be updated to keep abreast of constant global changes. This data is provided by existing resources and will not increase/decrease the interfacing systems manpower requirements. Below are the methods for maintaining the NavMPS databases.
a. Threat Databases. The initial source data is magnetic tape, produced by Atlantic Intelligence Command. For software release 6.1 it is from the Defense Intelligence Agency (DIA) Integrated Database (IDB) and for software release 6.2K it is from the DIA Modernized Intergrated Database (MIDB). It consists of friendly, neutral, and enemy order of battle.
(1) Manual Updates. The System Administrator (SA)/DBA may utilize available resources to maintain the database by updating the threat files with the latest intelligence data, reconnaissance information, or pilot reports.
(2) Electronic Updates. The SA/DBA may utilize the ETHERNET or Asynchronous Transfer Mode (ATM) interface from the Aircraft Carrier Intelligence Center (CVIC) to the Global Command and Control System - Maritime (GCCS-M) for retrieving updates to Order of Battle.
b. System Database. The NavMPS database will also consist of geo-political data. This data will be imported into the NavMPS from the National Imagery and Mapping Agency (NIMA) charts, Digital Terrain Elevation Data (DTED), Controlled Image Base (CIB) files and Digital Aeronautical Flight Information Files (DAFIF).
c. There are additional interfaces under development that could potentially be utilized in loading and updating NavMPS data files.
(1) Tactical EA-6B Mission Support (TEAMS) System. NavMPS will possess the ability, in FY99, to interface with TEAMS. TEAMS handles mission activities of the EA-6B aircraft and its intelligence information. This interface can save SA/DBAs time in interactive updates to the threat database. Data review and SA/DBA initiated actions are required to apply the TEAMS updates to the NavMPS program. Mission planners will be able to transfer route data across this interface.
d. Tactical Strike Coordination Manager (TSCM). The TSCM is a distributed collaborative joint Force Level automated mission planning system that enables mission planners to develop integrated joint strike plans for Tactical Aircraft (TACAIR), support aircraft, Tomahawk cruise missiles, and Unmanned Aerial Vehicles (UAV), both ashore and afloat. TSCM provides mission planners with a computer based system, capable of rapidly processing large quantities of DTED, Arc-second Raster Chart (ARC) digitized raster graphics, threat and environmental data, intelligence, imagery, and aircraft flight and performance data. TSCM interfaces with GCCS-M and NavMPS. This interface enables the complete integration of intelligence, imagery and tasking in the development of Force Level and Unit Level mission planning. Using TSCM, the planner can easily and quickly build strike plans, construct and edit individual mission routes, transfer/receive individual missions to/from TAMPS, deconflict routes, adjust timelines, furnish projected attrition, and then provide a graphic playback of the strike plan for briefing the Battle Group Commander, Carrier Air Group (CAG) Commander, Strike Leads and Strike Groups.
TSCM also performs Air Tasking Order (ATO) analysis, validation, and preview; Airspace Control Order (ACO) development, analysis, and validation; and provides contingency missions development and analysis. TSCM accepts United States Message Text Format (USMTF) formatted ATO messages and automatically transforms these into easily read tabular formats for execution. TSCM can also build ATOs and ACOs quickly and easily from contingency missions developed on TSCM.
TSCM is being used at NSAWC and aboard CVs/CVNs to support strike planning. NSAWC provides strike planning training in preparation for Air Wing deployments to execute ATOs or contingency tasking. Top level mission descriptions and/or straight line missions from an ATO are quickly converted into concept missions using TSCM's autorouter and form the basis for the CAG laptop brief. Concept missions can easily be passed from TSCM to NavMPS. The NavMPS unit level planners will no longer be required to develop a mission one waypoint at a time. Instead, the planner will select the concept mission passed from TSCM, which in turn causes the complete mission to be displayed. Typically the unit level planner will need only to clear the target waypoint provided by TSCM and insert NavMPS target waypoint data, which contain weapon delivery tactics to complete the detailed route. Once the detailed routes are completed on NavMPS, they can be returned to TSCM for final coordination and deconfliction. Processes which ordinarily take hours will be reduced to minutes through the use of TSCM/NavMPS interfaces.
e. Mission Rehearsal. Mission Rehearsal is the practice of planned tasks and functions critical to mission success using a true-to-life, interactive representation of the expected operating environment. Upon the fleet release of TAMPS software release 6.2K, planner selected missions from NavMPS can be passed to TOPSCENE where mission rehearsal can occur using realistic scenes of imagery draped over DTED. Prior to execution, aircrews will receive
detailed briefings based in part on the big picture from TSCM and in part on the detailed products developed by NavMPS (software release 6.2K and subsequent) which include mission data loads, kneeboard cards, strip charts, etc.
5. New Features, Configuration, or Material
a. NavMPS does not drive technology breakthroughs, but utilizes state-of-the-art, commercially available hardware in conjunction with a mix of COTS, Government Off-The-Shelf (GOTS), and NavMPS specific software to perform mission planning.
b. TAMPS software version 6.1 operates in a Windows-like environment and features an enhanced human-machine interface.
(1) TAMPS 6.1.1 software is a rehost of the TAMPS 6.1 software to the SUN ULTRA 2 (1200/1300) hardware.
(2) TAMPS Software Release 6.2. Software release 6.2 was introduced during the first quarter FY99 and incorporated improved fuel accuracy and intelligence databases with automatic updates. Additionally, it added imagery archiving and manipulation, mission rehearsal, electronic data folders, force level planning interface, and local and wide area network connection of GCCS-M, CVIC, and Ready Rooms. The GCCS-M interface with the Enterprise 4000 server will provide real time order of battle and weather updates during aircraft carrier operations. TAMPS software release 6.2 also provides planning for the AH-1, F/A-18 reconnaissance and SLAM Extended Response (ER).
(a) TAMPS Software Release 6.2K. Software release 6.2K is a maintenance release for UNIX systems and was released in stand alone mode by OPNAV on 21 December 1998. It incorporates the Y2K compliant software to ensure TAMPS functionality after midnight 31 December 1999.
(3) TAMPS Interim N-PFPS. The N-PFPS software was released during the second quarter of FY98. This is PC compatible software that will be updated annually until JMPS software is available.
c. The NavMPS program is built upon the philosophy of adding enhanced capabilities through new software releases. Below is a summary of system upgrades planned to be incorporated into future NavMPS software releases.
(1) TAMPS Software Release 6.2.1. Software release 6.2.1 will be a maintenance release for UNIX systems and will be introduced during the first quarter of FY00. It will incorporate improved force level planning tools connection, Joint Direct Attack Munition (JDAM), Tactical Aircraft Moving Map Capability (TAMMAC), and GPS terminal procedures.
(2) JMPS. Fleet release of the JMPS software is projected to be during the fourth quarter of FY01. This software release will incorporate N-PFPS with increased functionality and run in a Windows NT environment. JMPS version 2 will incorporate TAMPS 6.2.1 and previous versions functionality into JMPS.
d. TSCM operates on a standard Navy Tactical Advanced Computer (TAC) -3, a SUN SPARC station or SUN ULTRA 2. TSCM does not drive technology breakthroughs, but utilizes state-of-the-art, commercially available hardware in conjunction with a mix of COTS, GOTS, and TSCM specific software to perform mission planning.
(1) TSCM software operates in a windows-like environment and features enhanced human-machine interfaces. TSCM employs operator friendly interfaces that reduces required manual entries with point and click mouse action. TSCM is compatible with current NavMPS software and as NavMPS upgrades are fielded, TSCM will incorporate upgrades to ensure compatibility. TSCM will be hosted on Windows NT (FY00) and Computer Based Training (CBT) will be available via CD.
Section I.H. CONCEPTS
1. Operational Concept. NavMPS, with properly maintained databases, will greatly enhance the mission planning process by providing the operator with threat projections, calculating aircraft and weapons data (although the pubs must still be used to verify the output data) and providing flight data, strip charts, and radar predictions upon mission route selection. NavMPS will also allow the mission planner to initiate route modifications to enhance the probability of mission success.
2. Maintenance Concept. The NavMPS maintenance concept has been designed to provide a high degree of operational readiness. Because of the variety of COTS hardware in NavMPS, a modified maintenance approach is used to provide optimum coverage during equipment changes. Two levels of maintenance associated with the NavMPS are organizational and interim depot level maintenance. Direction and guidance concerning the maintenance concept for the NavMPS hardware is provided in NavMPS User Logistic Support Summaries (ULSSs).
a. Organizational Level. Organizational level maintenance is performed at the operating unit. These maintenance actions encompass preventive and some corrective maintenance, depending on whether the equipment is deployed or not.
(1) Preventive Maintenance. Periodic inspections and/or servicing of equipment will be accomplished as defined in the NavMPS Maintenance Requirements Cards (MRCs).
(2) Corrective Maintenance. Corrective maintenace actions taken will vary depending on the deployment status of the operating unit. For deployed equipment, corrective maintenance consists of Lowest Replaceable Unit (LRU) and Shop Replaceable Unit (SRU) removal and replacement. For nondeployed equipment, corrective maintenance consists of LRU removal and replacement only.
b. Interim Depot Level. Repair and disposition of retrograde assemblies beyond the capability of the organizational level is accomplished by the designated depot activity. The Space and Naval Warfare Systems Center San Diego, C4I Programs Office, Philadelphia, PA, (SPAWAR C4I Programs Office, Philadelphia) is currently the designated depot site for all NavMPS hardware. Interim level depot maintenance consists of special shop equipment and trained personnel for testing, troubleshooting, inspecting, servicing, lubricating, adjusting, and replacing parts, major assemblies, and subassemblies to the original configuration.
c. Technical Assistance
(1) SPAWAR C4I Programs Office, Philadelphia is the focal point for product support. This will consist of field level training in conjunction with initial system installation and maintenance support.
(2) The Naval Air Warfare Center - Weapons Division (NAWC - WD), Pt. Mugu is the Software Support Activity (SSA), integrator, and configuration manager for TAMPS software. Naval Air Warfare Center - Aircraft Division (NAWC - AD), Patuxent River is responsible for software Independent Verification and Validation (IV&V).
3. Manning Concept
a. NavMPS. The NavMPS manning concept is driven by the total system requirements for effective utilization and confidence in NavMPS. Functional operating requirements will be accomplished through the utilization of existing manpower. These positions include mission planners, SAs, DBAs, and maintenance personnel. Mission planners will be squadron level aircrew (pilots or Naval Flight Officers (NFOs)).
b. TSCM. The TSCM manning concept is driven by the total system requirements for effective utilization and confidence in TSCM. Functional operating requirements will be accomplished through the utilization of existing manpower. These positions include mission planners and system administrators. Mission planners will be squadron level aircrew (pilots or NFOs). All required TSCM functions will be filled by qualified personnel as additional tasking to their present duties, and are to remain within the current manning structures of recipient activities or commands.
4. NavMPS Training Concept. The NavMPS training concept is based on the precept that the users and maintainers have attained the necessary primary Navy Officer Billet Classification (NOBC), Navy Enlisted Classification (NEC), or Military Occupational Specialty (MOS) and prerequisite levels of experience in their specialty prior to receiving NavMPS training. The NavMPS training will build upon this knowledge base and provide the student with the necessary instruction to effectively operate the NavMPS hardware and software.
The automated mission planning training concept is for an integrated training continuum that lays the foundation for automated mission planning at the Naval Aviation Training Command (Level 1) and continues to build on that knowledge at the Fleet Replacement Squadrons (FRSs) (Level 2). Intermediate level training will be conducted at the appropriate intermediate weapon schools and specific fleet squadrons (Level 3), and advanced training will be conducted at the advanced weapon schools and specific fleet squadrons (Level 4).
The intent of the NavMPS training program is to provide applicable training at each major phase of the aviation training pipeline. This will include primary pilot training and basic NFO training, FRS, and weapon school training. The goal is to teach automated mission planning as a team of products or "system of applications" so they appear as a seamless family. This will provide each aviator with the knowledge of what tools are available to assist him in planning a single flight plan or a complete strike package.
Due to the evolutionary nature of the NavMPS program and the open architecture of the software, there is potential for new MPMs/MPFs to be added to the NavMPS. As new MPMs/MPFs are developed, the developing agency will ensure the appropriate training and training material are also generated. Additionally, the developing agency will ensure that this course data is coordinated with SPAWAR C4I Programs Office, Philadelphia for distribution, prior to fleet introduction, to the impacted FRSs, weapon schools, and Navy and Marine Corps Intelligence Training Center (NMITC)/Sea-Based Weapons and Advanced Tactics School, Pacific (SWATSCOLPAC) for incorporation into their NavMPS training unit of instruction modules. The SA/DBA package is distributed to NMITC and SWATSCOLPAC while the full mission planning package is distributed to the weapon schools, FRSs, Marine Aviation Weapons and Tactics Squadron One (MAWTS-1), Marine Aircraft Wings (MAWs), and Marine Aircraft Groups (MAGs). The individual communities will modify the mission planning course materials to fit their requirements and integrate the NavMPS training into their respective mission planning curricula. NSAWC is the Model Manager for the NavMPS functionality. NMITC is the Model Manager for the SA/DBA course and the maintenance course.
a. Initial Training. For each new software release, SPAWAR C4I Programs Office, Philadelphia provides initial SA/DBA training to the instructors at NMITC and SWATSCOLPAC and initial mission planning training to the FRS and weapon schools instructors.
b. Follow-on Training. Follow-on training is formal training conducted at military schools to ensure qualified operators and proper life cycle support. This is accomplished through a training methodology that tailors the courseware to the targeted student population. The ultimate goal of the NavMPS training program is to provide applicable training at each major phase of the aviation training pipeline. This will include primary pilot training and basic NFO training, FRS, and weapon school training. Currently though, only some FRS and weapon school training is available.
(1) NavMPS Mission Planner. Pilots and NFOs will be provided the necessary skills and knowledge requirements for proper operation of the NavMPS. The aircrew training is building block in nature and based on minimum terminal objectives. This is accomplished by integrating the required NavMPS information into the specific aircraft mission planning training syllabus at each level of an aviator's training.
(a) The Naval Air Training Command will introduce the system of applications concept with a focus on basic mission planning capabilities using the N-PFPS.
(b) All FRSs will integrate the NavMPS training into the existing type aircraft mission planning syllabus by having training materials tailored to specific platforms, utilizing basic systems applications, and focusing on combat mission planning capabilities. Courses will be updated for TAMPS software 6.2 upon the FRSs receipt of the appropriate hardware and software. The major objectives are to use NavMPS for basic mission planning as follows:
- Create single aircraft mission to include the Target Attack event, if applicable.
- Display chart, imagery, and elevation data background.
- Display target area threats.
- Generate single aircraft kneeboard products.
- Generate applicable aircraft digital loads.
(c) The weapons schools will integrate NavMPS training into their existing weapon system/advanced readiness program syllabi with training materials tailored to specific platforms, providing full use of system applications capabilities, and focusing on integrated combat and strike/force level mission planning. The major objectives are to use TAMPS for mission planning as follows:
- Analyze strike mission susceptibility to target threats.
- Create strike mission package.
- Generate strike mission briefing products.
- Generate products provided by the applicable mission planning modules and
digital loads.
(d) Advanced weapons schools (NSAWC and MAWTS-1) will provide strike planning focused on advanced, full spectrum, planning with NavMPS products. NSAWC evaluates NavMPS training effectiveness through practical application during air wing deployments to NAS Fallon. MAWTS-1 conducts two major strike planning exercises annually.
Aircrews will attend applicable courses as part of their normal pre-deployment workups. The participating weapons schools are as follows:
- Strike Fighter Weapons School, Atlantic
(SFWSLANT), NAS Cecil Field, FL
- Strike Fighter Weapons School, Pacific
(SFWSPAC), NAS Lemoore, CA
- Strike Weapons and Tactics School, Atlantic
(SWATSLANT), NAS Oceana, VA
- Sea Control Weapons School, Atlantic
(SEACONWPNSLANT), NAS Cecil Field, FL
- Electronic Combat Weapons School
(ECWS), NAS Whidbey Island, WA
- Sea-based Weapons and Advanced Tactics School, Pacific
(SWATSCOLPAC), NAS North Island, CA
- Naval Strike and Air Warfare Center
(NSAWC), NAS Fallon, NV
- Mine Warfare Training Center
(MINEWARTRACEN), Ingleside, TX
- Marine Aviation Weapons and Tactics Squadron One
(MAWTS-1), MCAS Yuma, AZ
(c) The Marine Corps NavMPS mission planner training will be established at the MAG level to provide training for NavMPS MAG instructors. These MAG instructors will provide NavMPS mission planning training to fleet operators.
(2) System Administrator/Database Administrator. The intent of the SA/DBA course is to provide Navy Intelligence Specialist (IS) and Marine Corps MOS 0231 personnel in-depth database and system management training to include descriptions of database files, a functional description of the database administration subprocess, and instruction in procedures for generation and update of operational and aircraft databases. The students will also be trained to oversee and coordinate the use of NavMPS equipment, loading of upgraded software, system backup procedures, and the ability to limit access through password and level of use assignment. The Marine Corps will use the Navy training at NMITC and SWATSCOLPAC. The following is the course information:
Course Title . . . . . . . . . . . . . . . . . . . . . . . . . TAMPS System Administrator
CIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . J-150-2965
(Part of J-150-0987)
Course Length . . . . . . . . . . . . . . . . . . . . . . . .10 Days
Ready For Training (RFT) Date (6.2K) . . . . Available
Course Location . . . . . . . . . . . . . . . . . . . . . . NMITC
SWATSCOLPAC (Stand-alone Course)
(3) Maintenance Technician. The NavMPS hardware maintenance course is embedded in the Intelligenance Center Maintenance Course for Electronics Technician (ET) training for NEC 1654 (course J-150-2019). This training is available only at NMITC and provides maintenance technicians with the skills and knowledge required to perform both preventive and corrective maintenance on the NavMPS hardware. In addition, the maintenance technician will receive limited instruction on the operation of the software to facilitate troubleshooting the NavMPS in accordance with the established Maintenance Plans. The maintenance course has been updated to the CVIC system and the SUN ULTRA 2 (1200/1300) that is replacing the DTC-II aboard ship.
(a) The Marine Corps will start conducting maintenance training on the SUN ULTRA 2 (1200/1300) for MOS 6494 during the fourth quarter of FY99 This will be accomplished by integrating the appropriate NavMPS data in the Aviation Logistics Tactical Information Systems (ALTIS) specialist course (C-150-2010) conducted at the Navy Supply Corps School, Athens, GA.
(4) An abbreviated NavMPS mission planning demonstration is incorporated into the Naval Intelligence Officer Basic Course (NIOBC), Course Identification Number (CIN) J-3A-0010. This will provide the attending students with a basic knowledge of TAMPS capabilities and data interface requirements.
(5) A four-day introduction class is embedded in the Afloat Strike Planning Support Course (STRIKE), CIN J-150-0987. This block of instruction will provide attending students with basic skills and an introduction to basic mission planning.
c. Cadre Training. Cadre Training will be conducted by the SPAWAR C4I Programs Office, Philadelphia Fleet Introduction Team (FIT). This training will be for personnel at activities receiving the NavMPS hardware and/or software. Formal (school house) NavMPS follow-on training, however, will be obtained by activities when notified of receiving their first NavMPS system and prior to NavMPS installation. The FIT will evaluate the NavMPS training requirements at the recipient activity and tailor the training program to meet the training requirements of that activity. Upon completion of the instruction, the FIT will again evaluate the students at the recipient activity to ensure that they possess the necessary skills and knowledge to effectively operate the NavMPS hardware and software.
d. Student Profiles. The installation of the NavMPS will not change the existing qualitative manpower requirements in the recipient fleet activities.
(1) Watch Station Requirements. The display and tracking of information in relation to aircraft mission planning is currently required at all targeted NavMPS sites. NavMPS provides, organizes, and displays information already available for use by aircrew personnel.
e. Reserve Component. The current delivery schedule includes reserve activities that will receive NavMPS work stations. All training required for effective system utilization is available for reserve personnel by attending the active duty curriculum.
5. TSCM Training Concept. The TSCM training concept is based on the precept that the users and maintainers have attained the necessary primary NOBC, NEC, or MOS and prerequisite levels of experience in their specialty prior to receiving TSCM training. The TSCM training will build upon this knowledge base and provide the student with the necessary instruction to effectively operate the TSCM hardware and software.
a. Initial Training. The initial training for TSCM consists of two parts.
(1) The first part involves mission planning training for the Battle Group staffs. This training will be initially provided to the Tactical Training Group (TACTRAGRU) staffs who will then provide the training to Battle Group Staffs. The TSCM training for Battle Group staffs will be integrated into the existing syllabus at TACTRAGRUPAC and TACTRAGRULANT. The focus of the training will be on typical Force Level mission planning issues such as Joint Task Force (JTF) organization and structure, the integration of the deployed carrier Battle Group into their organization and tasking procedures from the Commander Joint Task Force (CJTF). Subsequent focus is on training the process of converting tasking from the CJTF into execution. The training to support this activity will be centered around TSCM and include the training listed under Intermediate Mission Planning Training but expanded on ATO/ACO contingency mission development and distributive/collaborative planning.
(2) The second part involves the training of the FRS and Weapon School instructors. This training progression will also be employed for future software releases.
b. Follow-on Training. Follow-on training is formal training conducted at military schools to ensure qualified operators and proper life cycle support. This is accomplished through a training methodology that tailors the courseware to the targeted student population. The ultimate goal of the TSCM training program is to provide applicable training at each major phase of the aviation training pipeline.
(1) TSCM Mission Planner. Pilots and NFOs will be provided the necessary skills and knowledge requirements for proper operation of the TSCM. The aircrew training is building block in nature and based on minimum terminal objectives. This is accomplished by integrating the required TSCM information into the specific aircraft mission planning training syllabus.
(a) All FRSs will integrate the TSCM training into the existing type aircraft mission planning syllabus upon receipt of TSCM systems. The major objective for TSCM training at the FRS is to familiarize the aircrew in TSCM capabilities and operation for force level mission planning.
(b) The weapons schools will integrate TSCM training into their existing weapon system/advanced readiness program syllabi. TSCM training will include:
TSCM Overview
Force Level Mission Planning
TSCM Human to Computer Interface
TSCM Start-up and Shut-down Procedures
TSCM Main Menu Functions
Creating a New Strike Plan
Displaying Overlays Controller
Evaluating the Strike Plan
Utilities
Aircrews will attend applicable courses as part of their normal pre-deployment workups. The participating weapons schools are as follows:
- SFWSLANT, NAS Cecil Field, FL
- SFWSPAC, NAS Lemoore, CA
- SWATSLANT, NAS Oceana, VA
- SEACONWPNSLANT, NAS Cecil Field, FL
- ECWS, NAS Whidbey Island, WA
- SWATSCOLPAC, NAS North Island, CA
- NSAWC, NAS Fallon, NV
- MAWTS-1, MCAS Yuma, AZ
(c) Advanced mission planning training will take place at NSAWC and will incorporate TSCM training in the Strike Lead Air Training Syllabus (SLATS). The TSCM syllabus will be identical to that at the weapons school, but the training will be directed to specifically address mission planning system utilization and improvements, strike planning team composition, ATO utilization/generation, and integration of mission planning with mission review.
(d) The Marine Corps TSCM mission planner training will be established at the MAG level to provide training for TSCM MAG instructors. These MAG instructors will establish TSCM training at the MAG level to provide TSCM mission planning training to fleet operators.
(2) System Administrator. The SA training will be incorporated into the NavMPS SA/DBA course at NMITC. The intent of the SA course is to provide in-depth database and system management training to include descriptions of database files, a functional description of the database administration subprocess, and instruction in procedures for generation and update of operational and aircraft databases. The students will also be trained to oversee and coordinate the use of TSCM equipment, loading of upgraded software, system backup procedures, and the ability to limit access through password and level of use assignment. The Marine Corps will use the Navy training at NMITC
(3) NSAWC, NAS Fallon, NV, will conduct TSCM training as it applies to the strike leader. The training will address mission planning system utilization and improvements, strike planning team composition, and integration of mission planning and mission preview systems. NSAWC will evaluate TSCM training effectiveness through practical application during Air Wing deployments to NAS Fallon.
Section I.I. ON-BOARD (IN SERVICE) TRAINING. There is currently no on-board training required.
Section I.J. LOGISTICS SUPPORT
1. Manufacturer/Contract Number. NAWC - WD Pt. Mugu is the prime 6.2 software integrator, TELOS is the prime DTC-II and ACE/VME hardware contractor, and SUN/Intergraph is the prime Sun Enterprise 4000/SUN ULTRA 2 hardware contractor. The following are the current contract numbers:
a. DTC-II Hardware: N66032-89-D-0004
b. ACE/VME Hardware: F19628-90-D-0018
c. SUN ULTRA 2 Hardware: N66032-94-D-0012
2. Program Documentation. An Acquisition Logistics Support Plan (ALSP), dated April 1999, has been generated to identify the logistic support elements and the manner in which support resources will be developed for the operation and maintenance of the NavMPS systems of application.
3. Technical Data Plan
a. TAMPS. Hardware manuals are products of commercially available documentation. Software manuals have been developed and tailored to the specific requirements of each functional position. TAMPS 6.X manuals will be available concurrent with each fleet release of the software. The user manuals are available on compact disk as an alternative to the hard copy format. Additionally, distribution of the TAMPS software user manuals are available on-line.
b. TSCM. Hardware manuals are products of commercially available documentation. Software manuals have been developed and tailored to force level mission planning requirements. TSCM users manuals are available in hard copy format. Additionally, distribution of the TSCM Software User Manuals are available on soft copy.
4. Test Sets, Tools, and Test Equipment. In-depth analysis of the NavMPS maintenance philosophy has resulted in the identification of test equipment requirements. The test equipment requirements identified are items carried on the individual material readiness list of the recipient activities. Therefore, the installation of NavMPS does not drive additional special tools or test equipment requirements.
5. Repair Parts. The supply support initiated for NavMPS will provide a centralized repository of NavMPS repair parts. SPAWAR C4I Programs Office, Philadelphia will provide all repair parts provisioning. Pack up kits are provided to CV/CVN and USMC forward deployed activities to ensure limited computer "down time". Shore based activities will coordinate repair parts requirements with SPAWAR C4I Programs Office, Philadelphia.
Section I.K. SCHEDULES
1. Schedule of Events. The NavMPS systems will be delivered to CV/CVNs, USN/USMC activities, and Naval Reserve squadrons.
a. Delivery Schedule. Asset managers at NAVAIRLANT, NAVAIRPAC, CMC (APW), etc. will control the distribution of hardware assets into the fleet units. The following is the proposed hardware procurement plan:
CVIC PROCUREMENT PLAN
FY98 FY99 FY00 FY01 FY02 FY03
USN
CV/CVN 0 12 0 0 0 0
SUN ULTRA 2 PROCUREMENT PLAN
FY98 FY99 FY00 FY01 FY02 FY03
USN
VFA 0 48 0 0 0 0
VF 0 24 0 0 0 0
VAW 0 10 0 0 0 0
LHD/LHA 0 0 0 0 12 0
LPD 0 0 0 0 11 0
LSD 0 0 0 0 16 0
USMC
VMFA 0 16 0 0 0 0
VMFA (AW) 0 12 0 0 0 0
RESERVES
USN
VFA 0 6 0 0 0 0
VAW 0 0 2 0 0 0
USMC
VMFA 0 8 0 0 0 0
Note: The above NavMPS hardware requirements are displayed for informational
purposes only. For a complete delivery schedule by total units for each
squadron/activity refer to the asset managers (NAVAIRLANT, NAVAIRPAC,
CMC(APW), etc.).
N-PFPS PROCUREMENT PLAN
FY98 FY99 FY00 FY01 FY02 FY03
USN
VFA 0 144 0 0 0 0
VF 0 96 0 0 0 0
VP 0 72 0 0 0 0
VPU 0 8 0 0 0 0
VAQ 0 56 0 0 0 0
VAW 0 30 0 0 0 0
VQ 0 0 20 0 0 0
VS 0 0 60 0 0 0
VRC 0 0 8 0 0 0
VC 0 0 0 0 4 0
HS 0 0 20 0 0 0
HC 0 0 20 0 0 0
HSL 0 0 120 0 0 0
UH-1N DETs 0 0 9 0 0 0
HM 0 0 0 8 0 0
NAS 0 0 36 0 0 0
USMC
VMFA 0 48 0 0 0 0
VMFA (AW) 0 36 0 0 0 0
VMAQ 0 20 0 0 0 0
VMGR 0 24 0 0 0 0
VMA 0 0 0 0 70 0
HMX 0 0 6 0 0 0
HMH 0 0 60 0 0 0
HMM 0 0 90 0 0 0
HMLA 0 0 36 0 0 0
MCAS 0 12 0 0 0 0
Note: The above NavMPS hardware requirements are displayed for informational
purposes only. For a complete delivery schedule by total units for each
squadron/activity refer to the asset managers (NAVAIRLANT, NAVAIRPAC,
CMC(APW), etc.).
N-PFPS PROCUREMENT PLAN
FY98 FY99 FY00 FY01 FY02 FY03
RESERVES
USN
VFA 0 18 0 0 0 0
VAQ 0 4 0 0 0 0
VP 0 0 48 0 0 0
VQ 0 0 5 0 0 0
VAW 0 0 6 0 0 0
VR 0 0 78 0 0 0
HC 0 0 2 0 0 0
HCS 0 0 4 0 0 0
HM 0 0 8 0 0 0
HS 0 0 6 0 0 0
HSL 0 0 24 0 0 0
USMC
VMFA 0 24 0 0 0 0
VMGR 0 16 0 0 0 0
HMH 0 0 12 0 0 0
HMM 0 0 12 0 0 0
HMLA 0 0 24 0 0 0
Note: The above NavMPS hardware requirements are displayed for informational
purposes only. For a complete delivery schedule by total units for each
squadron/activity refer to the asset managers (NAVAIRLANT, NAVAIRPAC,
CMC(APW), etc.).
TSCM PROCUREMENT PLAN
FY98 FY99 FY00 FY01 FY02 FY03
Fleet Commanders 0 0 5 0 0 0
Battle Group Commanders 0 0 14 0 0 0
Carriers 0 48 0 0 0 0
Carrier Air Wings 0 10 0 0 0 0
Tactical Support Centers 0 0 0 14 0 0
Marine Aircraft Wings 0 0 6 0 0 0
Marine Aircraft Groups 0 0 18 0 0 0
Marine Expeditionary Units 0 7 0 0 0 0
LHD/LHA 0 0 0 0 36 0
LPD 0 0 0 0 11 0
Reserves
Carriers Air Wing 0 1 0 0 0 0
Marine Aircraft Wing 0 0 0 2 0 0
Marine Aircraft Groups 0 0 0 4 0 0
Note: The above NavMPS hardware requirements are displayed for informational
purposes only. For a complete delivery schedule by total units for each
squadron/activity refer to the asset managers (NAVAIRLANT, NAVAIRPAC,
CMC(APW), etc.).
b. Time Required to Install at NavMPS Operational Sites
(1) TAMPS. The TAMPS hardware will require approximately one week for equipment installation, software loading, and system testing. Training, at the recipients site by SPAWAR C4I Programs Office, Philadelphia, will not take place though until the hardware and software have been installed and tested and prerequisite training requirements have been met.
(2) TSCM. The TSCM hardware will require approximately three days for installation and testing. Training, at the recipients site by SPAWAR C4I Programs Office, Philadelphia, will not take place until the hardware and software have been installed and tested and prerequisite training requirements have been met.
c. Technical Training Equipment (TTE) Delivery Schedule. TTE will be utilized at fleet training sites in order to fulfill follow-on training requirements.
(1) NavMPS. NMITC and SWATSCOLPAC TTE requirements are based upon one NavMPS work station per student. The following is the TTE delivery schedule:
CVIC TTE PROCUREMENT PLAN
FY98 FY99 FY00 FY01 FY02 FY03
USN
NSAWC 1 0 0 0 0 0
NMITC 1 0 0 0 0 0
SWATSCOLPAC 1 0 0 0 0 0
USMC
MAWTS-1 0 1 0 0 0 0
SUN ULTRA 2 TTE PROCUREMENT PLAN
FY98 FY99 FY00 FY01 FY02 FY03
USN
NSAWC 1 4 0 0 0 0
NMITC 2 5 0 0 0 0
SWATSCOLPAC 2 5 0 0 0 0
SWATSLANT 3 0 0 0 0 0
SFWSPAC 0 2 0 0 0 0
SFWSLANT 2 0 0 0 0 0
AEW WTU 0 2 0 0 0 0
MINEWARTRACEN 0 1 0 0 0 0
VFA-106 0 2 0 0 0 0
VFA-125 0 2 0 0 0 0
VFA-122 0 1 0 0 0 0
VP-30 0 2 0 0 0 0
VAW-120 1 1 0 0 0 0
VF-101 0 0 2 0 0 0
USMC
MAWTS-1 2 3 0 0 0 0
VMFAT-101 0 1 0 0 0 0
NSCS 0 10 0 0 0 0
N-PFPS TTE PROCUREMENT PLAN
FY98 FY99 FY00 FY01 FY02 FY03
USN
NSAWC 0 8 0 0 0 0
NMITC 0 6 0 0 0 0
SWATSCOLPAC 0 6 0 0 0 0
SWATSLANT 0 6 0 0 0 0
SFWSPAC 0 6 0 0 0 0
SFWSLANT 0 6 0 0 0 0
ECWS 0 6 0 0 0 0
AEW WTU 0 6 0 0 0 0
HS WTU PAC 0 6 0 0 0 0
HS WTU LANT 0 6 0 0 0 0
SEACONWPNSLANT 0 6 0 0 0 0
VFA-106 0 20 0 0 0 0
VFA-125 0 20 0 0 0 0
VFA-122 0 20 0 0 0 0
VP-30 0 8 0 0 0 0
VAQ-129 0 4 0 0 0 0
VAW-120 0 6 0 0 0 0
VF-101 0 0 10 0 0 0
VS-41 0 0 8 0 0 0
VT/HT 0 0 54 0 0 0
HS-10 0 0 10 0 0 0
HC-2 0 0 2 0 0 0
HC-3 0 0 2 0 0 0
HSL-40 0 0 12 0 0 0
HSL-41 0 0 12 0 0 0
USMC
MAWTS-1 0 8 0 0 0 0
VMFAT-101 0 20 0 0 0 0
VMGRT-253 0 6 0 0 0 0
VMAT-203 0 0 0 0 10 0
HMT-204 0 4 0 0 0 0
HMT-301 0 4 0 0 0 0
HMT-302 0 4 0 0 0 0
HMT-303 0 4 0 0 0 0
TSCM TTE PROCUREMENT PLAN
FY98 FY99 FY00 FY01 FY02 FY03
USN
NSAWC 0 5 0 0 0 0
NMITC 0 3 0 0 0 0
SWATSCOLPAC 0 3 0 0 0 0
SWATSLANT 0 1 0 0 0 0
SFWSPAC 0 2 0 0 0 0
SFWSLANT 0 1 0 0 0 0
ECWS 0 2 0 0 0 0
AEW WTU 0 2 0 0 0 0
HS WTU PAC 0 2 0 0 0 0
HS WTU LANT 0 2 0 0 0 0
SEACONWPNSLANT 0 1 0 0 0 0
MINEWARTRACEN 0 1 0 0 0 0
VAW-120 0 1 0 0 0 0
VP-30 0 1 0 0 0 0
USMC
MAWTS-1 0 4 0 0 0 0
Section I.L. GOVERNMENT FURNISHED EQUIPMENT (GFE) AND CONTRACTOR FURNISHED EQUIPMENT (CFE) TRAINING REQUIREMENTS. There are currently no GFE or CFE training requirements beyond the current NavMPS training program.
Section I.M. RELATED NTSPs AND OTHER APPLICABLE DOCUMENTS
DOCUMENT/ DA
NTSP/DOCUMENT TITLE NTSP NUMBER CODE STATUS
AH-1W Aircraft A-50-8520D PMA276 Approved
February 96
C-2A (Reserve) A-50-8308B PMA221 Approved
October 96
C-9B/DC-9 Logistics R-50-9402 COMNAVRESFOR Approved
Aircraft (Reserves) December 94
DOCUMENT/ DA
NTSP/DOCUMENT TITLE NTSP NUMBER CODE STATUS
CH-53E Helicopter A-50-7604F PMA261 Draft
E-2C Aircraft A-50-8716D PMA231 Approved
December 97
E-2C Aircraft A-50-8715B PMA231 Approved
Transition to Reserves March 93
E-6A TACAMO A-50-8516D PMA271 Draft
Aircraft
EA-6B ICAP II A-50-7904C PMA234 Draft
Aircraft, Block 89
EP-3E ARIES II A-50-8605D PMA290 Draft
Aircraft
ES-3A Aircraft A-50-8818B PMA244 Approved
March 93
F-14A/B/D Aircraft A-50-8511B PMA241 Draft
August 98
F-18 Aircraft A-50-7703G PMA265 Approved
Weapon System November 97
H-46 Communication A-50-9409 PMA226 Draft
Navigation Control
System
HH/UH-1N Aircraft A-50-9404 PMA(F)225 Approved
October 94
KC-130T Aircraft A-50-8423 PMA200 Approved
June 85
MH-53E Helicopter A-50-8417C PMA261 Draft
DOCUMENT/ DA
NTSP/DOCUMENT TITLE NTSP NUMBER CODE STATUS
Navy Undergraduate A-50-8703B PMA273 Approved
Jet Flight Training February 95
System, T45TS
P-3C Update II.5/III A-50-8112B PMA290 Approved
and ASUW Improvement June 98
Program
S-3B Aircraft A-50-8310D PMA244 Draft
SH-60B LAMPS MK-III A-50-7702D PMA299 Proposed
Part B, Aircraft
Subsystems
SH-60F Carrier Inner A-50-8508C PMA299 Approved
Zone Helicopter Sept 94
SH-60R Multi Purpose A-50-9403 PMA299 Proposed
Helicopter
V-22A Aircraft A-50-8412D PMA275 Draft
Afloat Planning A-00-9001 PMA281 Approved
System (APS) December 90
AGM-84E SLAM A-50-8813B PMA258 Approved
May 96
AGM-84H SLAM A-50-9502 PMA258 Approved
Expanded Response May 96
AGM-88A HARM A-50-8101B PMA242 Draft
Missile
AN/ARC-210(V) A-50-9012B PMA209 Proposed
Electronic Protection
Radio
DOCUMENT/ DA
NTSP/DOCUMENT TITLE NTSP NUMBER CODE STATUS
Joint Direct Attack A-50-9104 PMA201 Draft
Munitions (JDAM)
Joint Stand Off A-50-8906 PMA201 Draft
Weapon (JSOW)
Joint Tactical E-70-8901B PMW159 Approved
Information Distribution July 94
System (JTIDS)
JMCIS E-70-9401A PMW172 Approved
January 96
NAVSTAR Global E-70-8215F PMW177 Approved
Positioning System July 95
(GPS)
|
NEWSLETTER
|
| Join the GlobalSecurity.org mailing list |
|
|
|
