Mission Planning
Abstract
Joint Mission Planning System (JMPS) is the designated automated mission planning system for the Navy, supporting over 40 T/M/S. Future JMPS platforms include: MQ-4C (Triton), P-8 and CH-53K. JMPS enables weapon system employment by providing the information, automated tools, and decision aids needed to rapidly plan aircraft, weapon, or sensor missions, load mission data into aircraft and weapons, and conduct post-mission analysis. JMPS is a mission critical system which is a co-development effort between the United States Navy (USN) and United States Air Force (USAF). Common requirements are identified and capabilities are developed and prioritized in an evolutionary approach. An individual JMPS Mission Planning Environment (MPE) is a combination of the JMPS framework, common components, unique planning components (UPCs), federated applications, and the necessary system hardware required to satisfy mission planning objectives. Most Tactical Naval Aviation platforms are dependent solely on JMPS to plan precision guided munitions, sensor systems, tactical data links, secure voice communications, and basic Safety of Flight functions. The JMPS Increment 4 will support mission planning for over 40 T/M/S. Increment 4, which includes 64-bit, delivers JMPS FW 1.5 and will transition JMPS from Windows 7/32-bit Operating System (OS) to Windows 10/64-bit OS. Transition to 64-bit allows for memory space expansion to accommodate future Microsoft Operating Systems, emerging technologies, and critical Cybersecurity updates. Funding profile includes JMPS baseline efforts for all existing T/M/S on Windows 7/32-bit framework while concurrently re-architecting to a 64-bit framework. Increment 4 development requires software conversion and refactoring to address memory limitations and system errors resulting in JMPS computer crashes. The transition from the current 32-bit architecture (4GB RAM) to a 64-bit architecture (192GB RAM) provides additional memory access, increased planning efficiencies; creating a increased stability in the architecture resulting in fewer system crashes. Delaying JMPS 64-bit transition (Increment 4) will allow existing system crashes to continue, and will decrease system stability in the future due to platform capability enhancements that require increased amounts of data and processing power.
Document Details
- Document Type
- Project
- Publication Date
- Oct 01, 2017
- Source ID
- 2213_0605215N_5_1319_PB_2017
Related Documents
- Root: (U)Mission Planning
- Child Accomplishment: Joint Mission Planning System Expeditionary (JMPS-E)
- Child Accomplishment: Mission Planning Environment Program Mgmt, Integration, and Test
- Child Accomplishment: JMPS Framework (FW) and Common Components (CC) Development
- Child Cost Item: cb6139bd4014e1d60ba68be9bdd087ce
- Child Cost Item: 93c592185e68c5ea784b251bbe1d4558
- Child Cost Item: 10c154981dccbd996a31ba9be5c40d31
- Child Cost Item: c6cc1ff08dba3c23ce2c342f4b0bdea4
- Child Cost Item: 35c2f51bab8e69e708437a96f74173de
- Child Cost Item: a0e818773383db0e009c76eb9553ce52
- Child Cost Item: 286260ae32e57bc1f4321b5ecd442c27
- Child Cost Item: 90a671a8b1e6dea3959dc7760986d09a
- Child Cost Item: 04d45ce300c5d9ca1fdbbe903a546e73
- Child Cost Item: 80218801d7ecaa145e75569daf1f3e44
- Child Cost Item: d326c5babf901b8c46bb96ac6cf3ad4d
- Child Cost Item: 51cf3a08e3a82dfd362a0974f628ad2b