Military

[ Navy Training System Plans ]




 

 

N88-NTSP A-50-9301D/P

 

 

 

 

 

NAVAL

MISSION PLANNING

SYSTEM

(NavMPS)

 

 

 

NAVY TRAINING SYSTEM

PLAN

 

 

 

 

 

 

N88-NTSP A-50-9301D/P

January 2001

EXECUTIVE SUMMARY

 

 

This Naval Mission Planning System (NavMPS) Navy Training System Plan (NTSP) addresses the continued fleet introduction of NavMPS hardware, the incorporation of the current Tactical Automated Mission Planning System (TAMPS) software release 6.2K.

The NavMPS 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 data, and environmental data, as well as, aircraft and weapon system parameters. In addition, NavMPS also provides digital download capabilities (i.e., JTIDS, GPS, EMDU, F/A-18 MU, etc.).

The NavMPS system includes software and a tactical computing system. TAMPS software release 6.2K is hosted on the SUN ULTRA 2 and the Aircraft Carrier Intelligence Center (CVIC) Enterprise 4000 and 2300 configurations. The TAMPS software version 6.2K was released in December 1998.

A properly maintained NavMPS system (software and hardware) will greatly enhance the ability of associated aircrews to rapidly plan missions and evaluate potential threats with greater accuracy. This will increase mission effectiveness, and at the same time, increase aircraft survivability. In addition, it provides aircrew additional time to enhance their situational awareness during stressful periods prior to launch.

Instructor requirements at the Fleet Replacement Squadrons (FRSs), the weapon schools, the Sea-based Weapons and Advanced Tactics School, Pacific (SWATSCOLPAC), and the Navy and Marine Corps Intelligence Training Center (NMITC) remain consistent with existing billet structure. Fleet and fleet support billet requirements will also remain consistent.

Since the approval of the preceding NTSP, various refinements have been made in the NavMPS community. The following is a brief description of changes that have occurred:

- The introduction schedule has been modified to meet current NavMPS deliveries.

- Technical Training Equipment delivery schedules and Ready For Training (RFT) dates

have been updated to reflect current planning.

- The SUN ULTRA 2, CVIC Enterprise 4000 and 2300 information has been

updated.

- The Navy - Portable Flight Planning Software (N-PFPS) information has been

updateded.

- The Tactical Strike Coordination Manager (TSCM) information has been deleted.

This NTSP contains Navy and Marine Corps Active Duty (ACDU), Navy Selected Reserves (SELRES), and Selected Marine Corps Reserve (SMCR) Manpower, Personnel and Training requirements regarding the NavMPS. As future modifications are made to the NavMPS program, they will be included in this NTSP via the annual review/revision process.

 

 

 

 

N88-NTSP-A-50-9301D/P

January 2001

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)

Section I.D. SYSTEM DESCRIPTION

1. Operational Uses. The Naval Mission Planning Systems (NavMPS) currently provides the Navy and Marine Corps with automated methods 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, avionics, precision guided munitions (PGMs), 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), Tactical Tape Cartridges (TTCs), and PCMCIA Cards). 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. One of the greatest benefits of these products is that they enhance the aviator's situational awareness when he is on the flight deck strapped into an aircraft preparing for a flight They give the aviator more time to concentrate on the immediate tasks at hand.

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 Navy - Portable Flight Planning Software (N-PFPS) 3.0 completed testing during the first quarter of FY98.

2. 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.

3. The Navy - Portable Flight Planning Software (N-PFPS) 3.01 completed testing during the first quarter of FY00.

4. The Navy - Portable Flight Planning Software (N-PFPS) 3.1 completed testing during the second quarter of FY00.

5. The Navy - Portable Flight Planning Software (N-PFPS) 3.1.1 completed testing during the fourth quarter of FY00.

6. The TAMPS 6.2.1 software is planned to begin testing during the first quarter of FY01. It is planned to be released during the third quarter of FY01.

7. The Navy - Portable Flight Planning Software (N-PFPS) 3.2 is planned to complete testing during the second quarter of FY01.

8. The Joint Mission Planning System (JMPS) developmental software is planned to complete Version 1 testing during the third quarter of FY02.

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.

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 TAMPS 6.2K is hosted on the SUN ULTRA 2 and the Aircraft Carrier Intelligence Center (CVIC) Enterprise 4000 and 2300.

4. TAMPS software release 6.2.1 will be hosted on the SUN ULTRA 2 (1200/1300).

Section I.G. DESCRIPTION OF NEW DEVELOPMENT

1. Functional Description. The different systems that constitute NavMPS have certain characteristics in common. They are all software intensive systems that help the planner analyze the mission environment (e.g., weather, terrain, threats), develop specific mission plans (e.g., route, fuel calculation, communications, weapons employment), and prepare all required mission and briefing products (e.g., briefing slides, knee board cards, charts, data transfer devise loads). NavMPS systems are designed to operate either as stand-alone assets or in a variety of networked configurations that provide server applications and/or access to external imagery and intelligence data sources. Specific hardware and Data Tranfer Devices (DTD) descriptions are provided elsewhere in this document.

    1. Software. The software of all NavMPS systems can be divided into three distinct areas: Operating System, Core/Framework, and Mission Specific Applications. Operating system and Core/Framework are required for all mission planning. Mission specific applications will vary depending on the aircraft, weapon, or avionics system being planned for.
    1. Operating System. In all NavMPS systems the Operating System (OS) is a Commercial Off-The-Shelf (COTS) product, supported by commercial documentation and training materials. The OS for TAMPS is UNIX, the OS for N-PFPS is Microsoft Windows NT, and the OS for JMPS is Microsoft Windows 2000.
    2. Core/Framework. Core/Framework software is that component of each NavMPS system that has been developed to represent the "release" version of the system. In some cases the core/framework may be modularized, permitting adequate system operation with less than 100% of the code loaded (if certain applications are not required by the planner). Core/Framework software executes the common or "community" functions within the system. For example, manipulations of background map displays are handled by core/framework instead of having each specific mission platform develop its own way of performing those operations. Among the other functions handled by core/framework software are data loading to the system, search and retrieve from databases, basic route calculations (range, bearing, time), user account management, and controlling communication in networked configurations.

      The current TAMPS core version is TAMPS 6.2.K, the current N-PFPS core version is N-PFPS 3.1.1, and the first JMPS framework version will be JMPS 1.0
    3. Mission Specific Applications. Mission specific applications are modules of software that permit the mission planner to prepare missions that are exactly tailored to an aircraft, weapon, or avionics system. In most cases, options allow the planner to specify down to the weapon or aircraft operational flight program or hardware version. In addition to functional capabilities, the mission specific applications typically contain specific performance data for the aircraft, weapon, or avionics system that they support. Mission specific application modules have a different name depending on the NavMPS system they are associated with:

      TAMPS mission specific applications are called Mission Planning Modules (MPMs) or Mission Planning Functions (MPFs). Currently TAMPS has MPMs/MPFs supporting the following aircraft, weapons, and avionics systems:

      -HH-60H -CH-53D -KC-130F/R/T -UH-1
      -CH-53E -P-3C -C-2 -F/A-18
      -AV-8B -EA-6B -S-3B -E-2C
      -CH-46E -F-14A/B/D -SH-60B/F -HARM
      -SLAM -SLAM-ER -JSOW -JDAM
      -ARC-210

      N-PFPS mission specific applications are called Flight Planning Modules (FPMs). Currently N-PFPS FPMs support the following aircraft:

      -AH-1 -CH-46E -SH-60F -HH-60H
      -S-3B -P-3C -C-2R -F/A-18 E/F
      -UH-1N -T-45A/C -E-2C -F/A-18 A/B/C/D

      N-PFPS also provides the planner with the ability to do "generic" mission planning with operator specified parameters. Other aircraft are being added periodically and current configuration management documents should be consulted for specific platform availability.

      JMPS mission specific applications will be called Unique Planning Components (UPCs). UPCs will be added continuously throughout the life cycle of JMPS and current configuration management documents should be consulted for specific platform availability.

b. TAMPS Hardware. There are currently three hardware configurations TAMPS Desktop Portable, the CVIC system and the Mini Server system) hosting the TAMPS software. This is due to the evolutionary acquisition process that 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) TAMPS Desktop Portable. The TAMPS 6.2.1 software is hosted on the SUN ULTRA 2 (1200/1300) that 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 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

2 18 GB Hard Drives

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 Color Laser Printer

1 DSU Receptacle, and/or MDL, and/or TID (as required by site)

1 Uninterruptable Power Supply

(2) CVIC System. The TAMPS 6.2.1 software is hosted on the CVIC system that 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 Laser Printer

2 Uninterruptable Power Supplies

Permanent Client System (SUN ULTRA 2 (2300))

1 Two 300MHz CPU w/512 MB RAM

2 18 GB Hard Drives

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 Laser Printer (Server Mode)/Xerox Color Laser 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 PC

1 3.5 GB Hard Drive

1 Ethernet Adapter

1 PCMCIA

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

1 Black and White Laser Printer

(3) Mini-Server System. The TAMPS 6.2.1 software is hosted on the Mini-Server System that is composed of the SUN Ultra 2 (2300) and is composed of COTS non-developmental hardware and is Y2K compliant hardware. The following is a list of the main hardware components that make up a Mini-Server configured system.

    1. CCA, System Board, Ultra2

2 CCA, CPU ULTRA SPARC2, 300 MHz

8 CCA, Memory Module, 64 MB

1 CCA, Video Display Controller

1 CCA, Interface Adapter

1 Adapter, Host Fiber Channel

1 CCA, Fiber Channel

2 CCA, ATM Interface

1 Power Supply

1 Cable Assembly, Power, 18AWG

1 Disk Array Assembly

1 Fan Tray Assy

1 Backplane

1 CCA, Controller Assembly

1 Power Supply Assy

1 Power Supply 440W

2 Disk Tray Assy

4.2 GB Disk Drive

2 CCA, Fiber Channel

1 SCSI Enclosure (9 Bay)

1 Drive, PCMCIA

1 Drive, CD-ROM, 12X

1 Drive, Tape, 8mm

(c) N-PFPS Hardware

(1) Laptops

1 Pentium III PC

1 12 GB Hard Drive

1 3.5" Floppy Drive

1 CD-ROM/DVD Drive

1 PCMCIA Card

1 56K Modem

1 10/100 Ethernet Network Card

1 15" SXGA+ Monitor

 

 

(2) Desktops

1 Pentium III PC

1 30 GB Hard Drive

1 3.5" Floppy Drive

1 CD-ROM/DVD Drive

1 Zip Drive

1 10/100 Ethernet Network Card

1 19" Color Monitor

2. Physical Description. 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 the NavMPS SUN ULTRA 2 (1200/1300) configuration.

 

 

 

 

 

TAMPS SUN ULTRA 2 (1200/1300) CONFIGURATION

FIGURE 1

 

b. Figure 2 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 2

c. Figure 3 is a representation of the TAMPS Mini-Server configuration.

 

MINI-SERVER SYSTEM CONFIGURATION

FIGURE 3

 

3. New Development Introduction. NavMPS hardware and software is are based upon evolutionary upgrades to the previous version. This allows the program to take advantage of hardware and software advancements as well as fleet inputs to further enhance the NavMPS's capability 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 on magnetic tape, produced by Atlantic Intelligence Command. For software release 6.2K it is from the Defense Intelligence Agency (DIA) Modernized Intergrated Database (MIDB). The MIDB 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 possesses the capability 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 are able to transfer route data across this interface.

d. 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 could 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 on the detailed products developed by NavMPS (software release 6.2K and subsequent) that 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. 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 third quarter of FY01. 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) N-PFPS Software Release 3.2. Software release 3.2. This is PC compatible software that will be updated annually until JMPS software is available.

(3) JMPS. Fleet release of the JMPS software Version 1 is projected to be during the fourth quarter of FY02. This software release will incorporate N-PFPS with increased functionality and run in a Windows 2000 environment. JMPS version 2 will incorporate TAMPS 6.2.1 and previous versions functionality into JMPS.

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.

(a) SPAWAR C4I Programs Office, Philadelphia, also provides ship riders aboard each deployed aircraft carrier to assist the ship and the Air Wing units in mission planning, SA/DBA, maintenance, and LAN functions.

(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 (i.e., pilots, Naval Flight Officers (NFOs), navigators).

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. The F/A-18 community has a tailored training package that has been developed for their use of NavMPS.

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 have appropriate schoolhouses 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.

(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 NavMPS 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 NavMPS 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, strike mission 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 Oceana, VA

- 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 Jacksonville, 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

(2) System Administrator/Database Administrator. The intent of the SA/DBA course is to provide Navy Intelligence Specialist (IS) 3923 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

Course Length . . . . . . . . . . . . . . . . . . . . . . . .10 Days

Ready For Training (RFT) Date (6.2K) . . . . Available

Course Location . . . . . . . . . . . . . . . . . . . . . . NMITC (Stand-alone Course)

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 includes the CVIC system and the SUN ULTRA 2 (1200/1300).

(a) The Marine Corps is conducting maintenance training on the SUN ULTRA 2 (1200/1300) for MOS 6494. This was 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 can cover mission planning, SA/DBA, and maintenance training for personnel at activities receiving the NavMPS hardware and/or software. Any specialized NavMPS training in addition to the training mentioned above shall also be conducted by SPAWAR C4I Programs Office, Philadelphia Fleet Introduction Team (FIT). 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.

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.2K software integrator, and SUN is the prime Sun Enterprise 4000/SUN ULTRA 2 hardware contractor. The following are the current contract numbers:

a. 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.

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 for fleet and schoolhouse units. PMA-233 is responsible for overall distribution including test, NMITC, NSAWC, and SWATSCOLPAC assets.

Note:

    • No additional hardware will be procured for TAMPS (Last year was FY99).
    • CVIC hardware is being procured to support the JMPS Combat version.
    • Hardware is refreshed on a three-year basis (five years for servers).

The following is the proposed hardware procurement plan: (Delivery of hardware may not be completed in the fiscal year that the hardware is procured.)

CVIC (JMPS) PROCUREMENT PLAN

                   
 

FY99

FY00

FY01

FY02

FY03

FY04

FY05

FY06

USN

                 
 

CV/CVN

0

0

0

4

8

0

0

0

COMBAT PLANNING (TAMPS/JMPS) PROCUREMENT PLAN

                   
   

FY99

FY00

FY01

FY02

FY03

FY04

FY05

FY06

USN

                 
 

VFA

15

0

0

24

0

0

24

0

 

VF

5

0

0

12

0

0

12

0

 

VAW

2

0

0

10

0

0

10

0

 

VP

0

0

0

0

0

0

0

0

 

VS

0

0

0

0

0

0

0

0

 

LHD/LHA

0

0

0

0

12

0

0

12

 

LPD

0

0

0

0

11

0

0

11

 

LSD

0

0

0

0

16

0

0

16

                   

USMC

                 
 

VMFA

10

0

0

8

0

0

8

0

 

VMFA(AW)

12

0

0

6

0

0

6

0

                   

RESERVES

                 

USN

                 
 

VFA

0

0

0

3

0

0

3

0

                   

USMC

                 
 

VMFA

0

0

0

4

0

0

4

0

Note: The above NavMPS hardware requirements are displayed for informational purposes only. Actual procurements may very depending on budget constraints. Initial delivery of assets is coordinated by SPAWAR SSC C4I Programs Office, Philadelphia following approval from the asset managers (NAVAIRLANT, NAVAIRPAC, CMC(APW), etc.). Refer to the asset managers for any questions regarding distribution of NavMPS hardware.

 

FLIGHT PLANNING (N-PFPS/JMPS) PROCUREMENT PLAN

                   
   

FY99

FY00

FY01

FY02

FY03

FY04

FY05

FY06

USN

                 
 

VFA

48

48

24

0

48

24

0

48

 

VF

24

20

12

12

24

0

12

24

 

VP

36

12

0

24

12

0

24

12

 

VPU

4

2

0

2

2

0

2

2

 

VAQ

28

14

0

15

15

0

15

15

 

VAW

10

10

10

0

0

10

0

0

 

VQ

12

4

0

8

4

0

8

4

 

VS

20

10

0

10

10

0

10

10

 

VRC

4

5

0

0

4

0

0

4

 

VC

0

0

0

2

0

0

2

0

 

HS

20

10

0

10

10

0

10

10

 

HC

5

5

5

5

5

5

5

5

 

HSL

60

20

20

20

20

20

20

20

 

HM

2

2

0

0

2

0

0

2

 

UH-1N DETs

0

0

9

0

0

9

0

0

 

NAS

4

0

31

4

0

31

4

0

                   

USMC

                 
 

VMFA

24

16

8

0

16

8

0

16

 

VMFA(AW)

18

12

6

0

12

6

0

12

 

VMAQ

8

4

0

8

4

0

8

4

 

VMGR

18

6

0

12

6

0

12

6

 

VMA

28

14

7

21

14

7

21

14

 

HMX-1

3

2

0

1

2

0

1

2

 

HMH

30

9

0

18

9

0

18

9

 

HMM/VMM

45

14

14

17

14

14

17

14

 

HMLA

36

6

6

24

6

6

24

6

 

MCAS

2

0

8

2

0

8

2

0

 

Note: The above NavMPS hardware requirements are displayed for informational purposes only. Actual procurements may very depending based on budget constraints. Initial delivery of assets is coordinated by SPAWAR SSC C4I Programs Office, Philadelphia following approval from the asset managers (NAVAIRLANT, NAVAIRPAC, CMC(APW), etc.). Refer to the asset managers for any questions regarding distribution of NavMPS hardware.

 

FLIGHT PLANNING (N-PFPS/JMPS) PROCUREMENT PLAN

                   
   

FY99

FY00

FY01

FY02

FY03

FY04

FY05

FY06

RESERVES

                 

USN

                 
 

VFA

6

3

0

6

3

0

6

3

 

VAQ

2

1

0

1

1

0

1

1

 

VP

21

7

0

14

7

0

14

7

 

VAW

2

2

2

0

0

2

0

0

 

VR

16

4

4

8

4

4

8

4

 

HCS

4

0

0

4

0

0

4

0

 

HM

2

0

0

2

0

0

2

0

 

HS

2

1

0

1

1

0

1

1

                   

USMC

                 
 

VMFA

8

4

4

4

4

4

4

4

 

VMGR

8

4

4

0

4

4

0

4

 

HMH

6

2

0

4

2

0

4

2

 

HMM

6

2

0

4

2

0

2

2

 

HMLA

8

4

2

2

4

2

2

4

 

Note: The above NavMPS hardware requirements are displayed for informational purposes only. Actual procurements may very depending based on budget constraints. Initial delivery of assets is coordinated by SPAWAR SSC C4I Programs Office, Philadelphia following approval from the asset managers (NAVAIRLANT, NAVAIRPAC, CMC(APW), etc.). Refer to the asset managers for any questions regarding distribution of NavMPS hardware.

 

 

 

b. Time Required to Install at NavMPS Operational Sites

The NavMPS hardware will require approximately one week for equipment installation, software loading, and system testing. Training, at the recipient's 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. JMPS Combat level hardware will be less timely to install. Estimates will be available in FY02.

c. Technical Training Equipment (TTE) Delivery Schedule.

TTE will be utilized at fleet training sites in order to fulfill follow-on training requirements. NMITC and SWATSCOLPAC TTE requirements are based upon one NavMPS workstation per student. The following is the TTE delivery schedule:

 

CVIC (JMPS) TTE PROCUREMENT PLAN

                   
   

FY99

FY00

FY01

FY02

FY03

FY04

FY05

FY06

USN

                 
 

NSAWC

0

0

0

1

0

0

0

0

 

NMITC

0

0

0

1

0

0

0

0

 

SWATSCOLPAC

0

0

0

1

0

0

0

0

 

 

COMBAT PLANNING (TAMPS/JMPS) TTE PROCUREMENT PLAN

                   
   

FY99

FY00

FY01

FY02

FY03

FY04

FY05

FY06

USN

                 
 

NSAWC

2

0

0

5

0

0

5

0

 

NMITC

3

0

0

6

0

0

6

0

 

SWATSCOLPAC

2

0

0

6

0

0

6

0

 

SWATLANT

0

0

0

1

0

0

1

0

 

SFWSLANT

1

0

0

2

0

0

2

0

 

SFWSPAC

3

0

0

2

0

0

2

0

 

AEW WTU

0

0

0

1

0

0

1

0

 

MINEWARTRACEN

0

0

0

1

0

0

1

0

 

VFA-106

2

0

0

1

0

0

1

0

 

VFA-125

2

0

0

1

0

0

1

0

 

VFA-122

0

0

0

1

0

0

1

0

 

VF-101

1

0

0

1

0

0

1

0

 

VAW-120

0

0

0

1

0

0

1

0

                   

USMC

                 
 

MAWTS-1

0

0

0

1

0

0

1

0

 

VMFAT-101

2

0

0

1

0

0

1

0

 

NSCS

1

0

0

5

0

0

5

0

 

 

FLIGHT PLANNING (N-PFPS/JMPS) TTE PROCUREMENT PLAN

                   
   

FY99

FY00

FY01

FY02

FY03

FY04

FY05

FY06

USN

                 
 

NSAWC

4

0

0

4

0

0

4

0

 

SWATSCOLPAC

4

0

0

4

0

0

4

0

 

SWATLANT

2

5

0

2

4

0

2

4

 

SFWSLANT

2

5

0

2

4

0

2

4

 

SFWSPAC

6

1

0

6

0

0

6

0

 

ECWS

3

0

0

3

0

0

3

0

 

AEW WTU

3

0

0

3

0

0

3

0

 

HS WTU PAC

3

1

0

2

1

0

2

1

 

HS WTU LANT

3

1

0

2

1

0

2

1

 

SEACONWPNSLANT

4

0

0

3

0

0

3

0

 

VFA-106

10

4

0

6

4

0

6

4

 

VFA-125

10

0

0

10

0

0

10

0

 

VFA-122

12

2

0

8

2

0

8

2

 

VF-101

6

4

0

6

4

0

6

4

 

VP-30

4

2

0

2

2

0

2

2

 

VAQ-129

2

1

0

1

1

0

1

1

 

VAW-120

2

0

0

2

0

0

2

0

 

VS-41

4

2

0

2

2

0

2

2

 

VT/HT

23

0

6

30

0

6

30

0

 

HS-10

6

0

0

6

0

0

6

0

 

HC-2

1

0

0

1

0

0

1

0

 

HC-3

1

0

0

1

0

0

1

0

 

HSL-40

6

0

2

4

0

2

4

0

 

HSL-41

6

0

2

4

0

2

4

0

                   

USMC

                 
 

MAWTS-1

8

1

0

8

0

0

8

0

 

VMFAT-101

10

2

0

8

2

0

8

2

 

VMGRT-253

4

0

2

2

0

2

2

0

 

VMAT-203

5

0

1

4

0

1

4

0

 

VMMT-204

3

0

0

3

0

0

3

0

 

HMT-301

3

0

0

3

0

0

3

0

 

HMT-302

3

0

0

3

0

0

3

0

 

HMT-303

3

0

0

3

0

0

3

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

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 Approved Aircraft July 99

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 Approved

March 00

DOCUMENT/ DA

NTSP/DOCUMENT TITLE NTSP NUMBER CODE STATUS

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

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-8508D PMA299 Approved

Zone Helicopter August 00

SH-60R Multi Purpose A-50-9403 PMA299 Proposed

Helicopter

V-22A Aircraft A-50-8412D PMA275 Approved

August 99

DOCUMENT/ DA

NTSP/DOCUMENT TITLE NTSP NUMBER CODE STATUS

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 Approved

Missile September 00

AN/ARC-210(V) A-50-9012B PMA209 Proposed

Electronic Protection

Radio

Joint Direct Attack A-50-9104 PMA201 Draft

Munitions (JDAM)

Joint Stand Off A-50-8906A PMA201 Approved

Weapon (JSOW) March 00

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