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

Core Avionics Master PlanPlatform NARG and OAG attendees review the Enabler NARG recommendedpriority lists at their platform events and formally report concurrence or changes to therecommendations. Each Enabler NARG ESC then collates the Platform NARG andOAG responses and builds a collective (Enterprise-perspective) priority list that ispresented to the TYCOM Priority Panel (TPP). The TPP uses those lists to generate theTYCOM Priority List (TPL), which is used to influence the Aviation Sponsor‟s ProgramProposal (SPP) budget build. Marine Corps Platform OAG results are also provided tothe Headquarters Marine Corps (HQMC) Aviation Weapons Systems RequirementsBranch (APW) Council of Colonels, which prioritizes issues for budget consideration.Community leaders are strongly recommended to send experiencedoperators who are familiar with their mission sets to the Enabler NARG events.When possible, it is best if these same personnel are available to carry what they learnat the Enabler NARG event to the Platform NARG or OAG event. This allows avionicsenabledcapability growth to be championed by a community member, rather than thecommodity system managers. Except for safety systems, which are mandated byOPNAV and DoD instructions, there are no formal requirements to field avionicssystems per se. The requirement comes in the form of the operational missioncontribution that a platform performs with the capability enabled by the avionics.Therefore, all requirements for avionics must be sponsored by Fleet (platform) users.The Enabler NARG process provides a vehicle to align that sponsorship.2. Where possible, leverage existing other Service and Joint capabilitydocuments to accelerate formal requirement establishment. The JCIDS instructionlays out the procedures for analyzing identified capability deficiencies and formallydocumenting them in Initial Capability Documents (ICDs), Capability DevelopmentDocuments (CDDs), and Capability Production Documents (CPDs). In the MarineCorps, capability needs can also be documented by Joint Urgent Operational Needs(JUONs) and Universal Needs Statements (UNSs) or Urgent UNS (UUNS). JointCapability Documents (JCDs) are required to be established in order to initiateacquisition programs and apply resources to field and sustain solutions. There are fewcapabilities that have not already been base-lined in JCDs. Platform and commoditymanagers pursuing new programs or spiral upgrades are encouraged to leverageexisting JCDs to accelerate program initiation. OPNAV N88 has personnel assigned toassist with reviewing existing JCDs, as well as development and staffing of new ones.3. Use commodity evolution roadmaps to align the timing of evolution anddelivery of avionics enabled capabilities across platforms for collectiveresourcing and broader benefits. Requirements are generated when threats change,tactics change or new mission creates a capability gap. Avionics solutions addressmany of those requirements. This document speaks to „core‟ solutions that apply tomost platforms. The roadmaps presented in the appendices of this document aredivided into the core capability areas shown in Section 3. The timelines for the capabilitysub-elements portray when enhancements are expected to be mature, based upontechnology growth and programmatic preparation time. Platform requirements officersand program managers are recommended to use these roadmaps to create theircapability roadmaps and flight plans, so that they will align with other platform roadmapsand those enhancements will bring broader benefit across the enterprise.Core Section CAMP 2011 4