PMA209 2012 Core Avionics Master Plan - NAVAIR - U.S. Navy

More documents

Recommendations

Info

EP-3EP-3CEP-8AP-8ARQ-4AMQ-8BC-130 ***KC-130 ***AH-1WAH-1Z *UH-1YUH-1N *AV-8BMV-22 (all)CH-46ECH-46EMH-53E *CH-53 (all)SH-60B/FHH-60HMH-60R/SF-35BPHIBRON **C-2AE-2C (all)E-2DEA-6B(all)FA-18(all)EA-18GF-35CX-47BCore Avionics Master Plan 2012 Appendix A-1JMPS-M MPEs are currently approved for connection to various naval networks,including Integrated Shipboard Network System (ISNS), Navy/Marine Corps Intranet(NMCI), and Marine Corps Enterprise Network (MCEN), and is expected to be approvedfor connection to Consolidated Afloat Networks and Enterprise Services (CANES)networks as well. Connections to these networks provide JMPS-M users access to awide variety of network resources and databases that are helpful for coordination andplanning of their missions.Tables A-1 through A-3 identify Mission Planning support constructs:Mission Planning System J J J J J J U UTable A-1: Carrier Strike Group UsersMission Planning System J J J J J J J J J J J J J U JTable A-2: Expeditionary Strike Group UsersMission Planning System J J U U U U P PTable A-3: Maritime-Patrol and Support Aircraft UsersJ=JMPS, P=PFPS, U=Unique.* = PFPS software provided as part of a JMPS-M integrated/managed MPE forspecific functionality until this function is moved to JMPS application software.** = JMPS-Expeditionary (JMPS-E) systems installed on LHA/LHDs for thiscommunity.*** = Aircraft being supported by USAF-provided PFPS system configurations.A-1 Information Management 16
Core Avionics Master Plan 2012 Appendix A-1Weapons, avionic subsystems, and sensors supported by JMPS: High-Speed Anti-Radiation Missile (HARM) Advanced Anti-Radiation Guided Missile (AARGM) Joint Stand Off Weapon (JSOW) Joint Direct Attack Munitions (JDAM) Laser JDAM and Dual-mode Laser JDAM Standoff Land Attack Missile – Extended Range (SLAM-ER) Joint Tactical Information Distribution System (JTIDS) Multifunctional Information Distribution System (MIDS) Global Positioning System (GPS) equipment ARC-210 radios HAVEQUICK nets, Blue Force Tracker (BFT) Airborne Electronically Scanned Array (AESA) Radar.Several of the capabilities listed above cannot be employed without JMPS.For additional details Platform, sensor, and weapon capabilities that are in work bydevelopers across the JMPS Enterprise, contact PMA-281 for coordination assistancewith the appropriate developing agency.2. Funded Enhancements and Potential Pursuits.Improved framework stability, Faster planning, Air drops Planning AerialRefueling Planning. (2014) Microsoft Windows XP, the current operating system forJMPS-M, will no longer be supported by industry after April 2014. JMPS-M is upgradingto Windows 7 architecture, which provide a more stable framework environment andresult in fewer system crashes. It will also increase throughput speed, resulting in fasterspeed of mission planning. Additionally, there will be new operational capabilities cut inwith the new framework, including Airdrop Planning (supports C-130 [if desired] and V-22) and Air Refueling (supports C-130 [if desired]).Improved framework stability, Faster planning, Increased data/detail loading,Data at Rest encryption. (2018) In order to keep pace with industry, JMPS-M mustcontinue evolving to adopt current and supported versions of operating systems anddata management architectures. Current 32 bit processing is challenged to support thehuge amounts of data required for planning tactical missions, particularly in F/A-18E/Fand EA-18G aircraft. This causes additional system instability that movement toWindows 7 can only partially address. PMA281 would implement a 64 bit datamanagement, which is much more efficient and fast, enabling a quantum leap in datavolume management and processing speed. Windows 8 is expected to be the minimalbaseline operating system required for the next generation of processors. Thecombination of Windows 8 and 64 bit processing will again stabilize the systems andspeed up planning. Operators will be able to load much more and higher fidelity data fortheir missions. Additionally, the new architecture would meet Data at Rest encryptionrequirements established by DoDI 8500.2, Information Assurance (IA) Implementationpolicies.A-1 Information Management 17
Page 1 and 2: PMA209Endorsement and DistributionP
Page 3 and 4: Table of ContentsExecutive SummaryE
Page 5 and 6: Core Avionics Master PlanExecutive
Page 7 and 8: Core Avionics Master Plan Ensure th
Page 9 and 10: I. INTRODUCTION.Core Avionics Maste
Page 11 and 12: IV. RECOMMENDED PRACTICES.Core Avio
Page 13 and 14: Core Avionics Master Plan2. Where p
Page 15 and 16: Core Avionics Master Plan3. Leverag
Page 17 and 18: Core Avionics Master PlanSECNAVISNT
Page 19 and 20: Core Avionics Master PlanThe follow
Page 21 and 22: Core Avionics Master PlanIn 2010, P
Page 23 and 24: Core Avionics Master PlanDoD 4140.1
Page 25 and 26: Core Avionics Master Plan 2012Appen
Page 27 and 28: Core Avionics Master Plan 2012 Appe
Page 41: Core Avionics Master Plan 2012 Appe
Page 93 and 94:
Core Avionics Master Plan 2012 Appe
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
show all

PMA209 2012 Core Avionics Master Plan - NAVAIR - U.S. Navy

Create successful ePaper yourself

Delete template?

Save as template?