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

More documents

Recommendations

Info

Core Avionics Master Plan 2012 Appendix A-2Interoperability between Services and among Coalition partners currently reliesheavily on pre-mission 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. They principally take small pieces of information in one link format andtranslate them into equivalent protocol in a different data link. This approach becomesvery complex as additional data links, formats, or network connections are added.Message correlation between links, loss of precision, and differing data representationsfurther complicate 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(TADIL) radios to transmit data between aircraft, VHF AM and FM voice radios forground forces, Situational Awareness (SA) data links for ground troops, and satellitecommunications (SATCOM).JRE: Joint Range Extension (JRE) Gateway is a multi-protocol router of Link 16tactical data that provides TADIL-Joint (TADIL-J; NATO designation is Link 16)messaging and voice between LOS terminals or over a BLOS medium. JRE is based onthe Joint Range Extension Applications Protocol-C (JREAP-C) in MIL-STD-3011.JREAP-C is a secure data link interface that encapsulates TADIL-J information into IPbased networks.IOG/OG: is an Air Force family of systems connecting data and voice networks toprovide mission critical information to Joint forces, coalition partners and civilauthorities. Advanced gateway capabilities enable transition from legacy gateways withniche requirements and narrow user-sets to the Global Information Grid (GIG) through arouter/ server and a link back to the IP environment. The system also allows differentdata links, such as Link 16 or TTNT, to communicate with each other. It will also allowlegacy communications systems 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 capabilities:1) Support efforts to maintain the NAE’s existing communications capabilities.2) Indentify and field improvement and upgrades to our current systems which allowthe NAE to expand capabilities through an evolutionary approach where practical.3) Transform our communications and airborne networking capabilities by promotingthe fielding of a Common Operating Environment (COE) across Naval Aviation andsupporting the establishment of standards that enable the rapid fielding ofcollaborative capabilities.A-2 Information Exchange 2
Core Avionics Master Plan 2012 Appendix A-2I. Line of Sight (LOS) Information Exchange.Mandates and Milestones:Multifunctional Information Distribution System – Joint Tactical Radio System(MIDS-JTRS) Initial Operational Capability (IOC). (2010) MIDS-JTRS (or MIDS-J) is aform-fit-function replacement for the MIDS Low Volume Terminal (LVT), which providesenhanced through-put Link 16 for tactical aircraft. It was deployed on Super-Hornet in2011. It provides Tactical Air Navigation (TACAN), Link 16 digital tactical data anddigital voice (J-Voice), and programmable encryption to comply with the NationalSecurity Agency’s (NSA) crypto modernization mandate. It is Software CommunicationsArchitecture (SCA) compliant (i.e. capable of running JTRS software waveforms) andhas additional transceiver slots to accommodate to future upgrades of JTRS waveformsincluding the TTNT waveform.ARC-210 Generation 5 RT-1939(C) IOC. (2012) The Gen 5 ARC-210 was approved forintegration on new production aircraft in 2011 and will be operationally deployed in2012. The Receiver Transmitter (RT) employs a Software Defined Radio (SDR)architecture with an increased frequency range (30-941 MHz) and red-side Ethernetdata port. It includes the capabilities resident in earlier ARC-210 versions. Futuresoftware upgrades will add UHF SATCOM Integrated Waveform (IW), the updated linklayer protocol for Combat Net Radio (CNR), the Second-generation Anti-jam TacticalUHF Radio for NATO (SATURN) waveform, the Enhanced SINCGARS (Single ChannelGround/Airborne Radio System) Improvement Program (ESIP) waveform, theBandwidth Efficient Advanced Modulation (BEAM) LOS waveform, and hooks to supportJoint Precision and Landing Approach (JPALS) and Mobile Users Object System(MUOS) functionality.Digitally aided Close Air Support (DaCAS) baseline implementation (2014). In Dec2009 the Joint Requirements Oversight Council (JROC) approved the Joint FiresExecutive Steering Groups objective to digitally interconnect Joint Terminal AttackController (JTAC) and Joint Fires Observer (JFO) systems with CAS platforms. TheJROC endorsed the Variable Messaging Format (VMF) over CNR as the near term LOSCAS standard protocol, and directed the Joint Forces Command (JFCOM) DaCASChange Control Board to define a common implementation of the appropriate standards(Block 1) by the end of 2010. Block 1 defines a link layer protocol (MIL-STD 188-220Rev D Chg1), a message header standard (MIL-STD 47001D), and the VMF messagestandard (MIL-STD 6017B). CAS mission aircraft must configure for VMF Rev D Chg 1.Capability Element Evolution:A. Interior Communications. This element addresses wireless systems used forcrew members to communicate with each other within the platform.1. Current capabilities. Hardwired and Airframe-based Wireless Intercomm.Naval aircraft primarily use Intercomm Systems (ICS) that require aircrew to beplugged in via a hard cord to an embedded hard-wired system outlet at each operatingstation. This design restricts crew mobility and presents an entanglement hazard duringemergency egress. The current Naval standard for wireless intercom, Airborne WirelessICS (AWICS), is being incorporated into the C-2, H-46, H-53, H-60, UH-1Y and MV-22.A-2 Information Exchange 3
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 45: Core Avionics Master Plan 2012 Appe
Page 97 and 98:
Core Avionics Master Plan 2012 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:
Page 117 and 118:
Page 119 and 120:
show all

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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?