Mission Planning
Abstract
Mission Planning: The Joint Mission Planning System (JMPS) is the designated automated mission planning system for the Navy. 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, 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 following type/model/series (T/M/S) naval aircraft are supported by JMPS: AH-1W, F/A-18 A-F, E-2C, EP-3E, EA-6B, AV-8B, S-3, V-22, Chief of Naval Air Training (CNATRA), EA-18G, MV-22, C-2, MH-53E, P-3, Aircraft Carrier Intelligence Center (CVIC), SH-60B/F, HH-60H, CH-53D/E, CH-46E, UH-1N, VH-3/VH-60, AH-1Z, UH-1Y, MH-60R/S and E-2D. All T/M/S are required to transition to Microsoft Windows 7 due to End of Life (EOL) of Microsoft XP (April 2014) using Framework (FW) Version 1.3.5. Custom support for Windows XP is planned to allow remaining naval aircraft to be supported during the transition. Future JMPS platforms include: MQ-4C (Triton) and CH-53K. The re-architecture of JMPS will support net-centric goals by providing route "publish and subscribe" capabilities, transition to 64 bit allows for memory space expansion to accommodate future Microsoft Operating Systems, emerging technologies, and critical Cyber Security vulnerabilities as identified in Operational Test (OT). 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. 64-bit development requires complete software restructure 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 (196GB RAM) provides additional memory access, increased planning efficiencies; creating a more stabilized architecture with fewer fleet memory crashes. Delaying JMPS 64-bit transition to the fleet will cause system crashes to continue. It will also delay required mission planning fixes based upon known software obsolescence, and will expose the system to risks based upon architectural weaknesses in regards to cyber security vulnerabilities.
Document Details
- Document Type
- Project
- Publication Date
- Oct 01, 2016
- Source ID
- 2213_0604231N_5_1319_PB_2016
Related Documents
- Root: Tactical Command System
- Child Accomplishment: JMPS Framework (FW) & Common Components (CC) Development
- Child Accomplishment: Joint Mission Planning System Expeditionary (JMPS-E)
- Child Accomplishment: Mission Planning Environment (MPE) Integration and Test
- Child Cost Item: 038292833fbf93a0b820c8df7b7b9245
- Child Cost Item: 70ccdcff2e0bdec22dfe030fea6fb70c
- Child Cost Item: 7265814db917f6af0871b9e18b0302b5
- Child Cost Item: 3c1e7d3efeee386bf1a03d9afb2e52c8
- Child Cost Item: 7eadbafe809612fc477c7ade014f3f1f
- Child Cost Item: d9d59d96661cb87d45bb679d0f720e52
- Child Cost Item: 0d6781a951f5950ebf142c2ee8782d92
- Child Cost Item: 3c038138196bd6a3f660c5fac0ebdf1b
- Child Cost Item: 99b6a18032d3d4169689d31ac2ddbd34
- Child Cost Item: 94b4295f2c9ac833885e24da2ab0ade8
- Child Cost Item: 4bd20203b75b7797c403148a11531e51