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

More documents

Recommendations

Info

Core Avionics Master Plan 2011 Appendix A-2Core AvionicsCapability EvolutionRoadmapsLine of Sight (LOS) CommunicationsCapabilityElementsUninterrupted, Secure LOS Information ExchangeHardwired & Airframe-based Wireless IntercomSecure Wireless IntercomInteriorCommsATC Voice/Have Quick/SINCGARSFirst RespondersInteroperability (APCO-25)TacticalCommsUHF/VHFCommon Digital Data Exchange [Variable Message Format (VMF) over Combat Net Radio]Block 1 (VMF Rev D Change 1)VMF Rev E VMF Rev FDigitallyAided CloseAir SupportVMFTactical Common Operating Picture [Link 16]Enhanced Throughput;Concurrent Multi-netting (CMN)Crypto Mod/Frequency Remapping (FR)Permissive& ContestedTacticalData LinksLPI/LPD Data LinkStealth Platform Interoperability (iMADL)Anti-Access Tactical Data Link (MADL)Anti-AccessTactical DataLinkPoint to Point ISR Data Link [Common Data Link (CDL); Remotely Operated Video Enhanced Receiver (ROVER)]ISR DataLink/FMVDaCASBaselineJTRS-AMFFRPARC-210Gen 5 IOCMIDS JTRSIOCSATURN (2004);IPv6 (2008)Mandates &MilestonesFY: 10 11 12 13 14 15 16 17 18Mandate orMilestoneUnfunded PotentialCapability DevelopmentFunded CapabilityEnhancementAdv ResearchOr Tech DevCurrent CapabilityBaseline StateA-2 Information Exchange 2
Core Avionics Master Plan 2011 Appendix A-2Interoperability between Services and among Coalition partners currently reliesheavily on advance configuration planning and system synchronization. Translating,sharing, or "gatewaying" data between dissimilar systems can provide commonoperational visualizations and data distribution. Gateways have been in development formany years and principally take small pieces of information in one link format andtranslate it into its equivalent in a different data link. This approach becomes verycomplex as additional data links, formats, or network connections are added. Messagecorrelation between links, loss of precision, and differing data representations furthercomplicate the task.Data gateways and range extensions have been demonstrated through severalinitiatives and fielded experiments. There are no specific acquisition programs of recordfor gateway capabilities; however, the Battlefield Airborne Communications Node(BACN), Joint Range Extension (JRE), and Interim Objective Gateway/ObjectiveGateway (IOG/OG) have proven the benefits of information translation.BACN: is an Air Force system that serves as a BLOS communications relay platformto connect different radio frequencies through a computer controlled bridge in the skycalled a gateway manager. The system includes Tactical Digital Information Link radiosto transmit data between aircraft, VHF AM and FM voice radios for ground forces,Situational Awareness (SA) data links for ground troops, and satellite communications.JRE: Joint Range Extension (JRE) Gateway is a multi-protocol router of Link 16tactical data that provides Tactical Digital Information Link – Joint (TADL-J) messagingover LOS terminals or through a BLOS medium. JRE is based on the Joint RangeExtension Applications Protocol-C (JREAP-C) in MIL-STD-3011. JREAP-C is a securedata link interface that encapsulates TADL-J information into IP based networks.IOG/OG: Interim Objective Gateway / Objective Gateway is an Air Force family ofsystems connecting data and voice networks to provide mission critical informationaccess to Joint forces, coalition partners and civil authorities. Advanced gatewaycapabilities enable a transition from legacy gateways with niche requirements andnarrow user-sets to the Global Information Grid (GIG) through a router/ server and a linkback to the IP environment. The system also allows different data links, such as Link 16or TTNT, to communicate with each other. It will also allow legacy communicationssystems to connect with the Joint Tactical Radio System (JTRS) and allies systems.Strategic Approach: The PMA 209 Communications and Airborne Networking (CAN)team has adopted a three pronged strategy to managing the Naval Aviation Enterprise‟s(NAE) communications and airborne networking capability:1) Support efforts to maintain the NAE‟s existing communications capability.2) Indentify and field improvement and upgrades to our current systems which allowthe NAE to expand capability through an evolutionary approach where practical.3) Transform our communications and airborne networking capability by promotingthe fielding of a Common Operating Environment (COE) across Naval Aviation andsupporting the establishment of standards that enable the rapid fielding ofcollaborative capability.A-2 Information Exchange 3
Page 3 and 4: Table of ContentsExecutive SummaryE
Page 5 and 6: Core Avionics Master PlanExecutive
Page 7 and 8: Core Avionics Master PlanPursue Per
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 Plan4. Define
Page 15 and 16: Core Avionics Master PlanAvCIP proc
Page 17 and 18: Core Avionics Master PlanSECNAVISNT
Page 19 and 20: Core Avionics Master PlanSimilar to
Page 21 and 22: Core Avionics Master PlanInterface
Page 23 and 24: Core Avionics Master PlanSECNAV Mem
Page 25 and 26: Core Avionics Master Plan 2011Appen
Page 27 and 28: Core Avionics Master Plan 2011 Appe
Page 43 and 44: EP-3EP-3CRQ-4AMQ-8BEP-8AP-8AAH-1WAH
Page 45: Core Avionics Master Plan 2011 Appe
Page 97 and 98:
Core Avionics Master Plan 2011 Appe
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:
show all

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

Create successful ePaper yourself

Delete template?

Save as template?