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

More documents

Recommendations

Info

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.Platform community leaders are strongly encouraged to send experiencedoperators who are familiar with their mission sets to the Enabler NARG events. Whenpossible, it is best if these same personnel are available to carry what they learn at theEnabler NARG event to the Platform NARG or OAG event. This allows avionics-enabledcapability 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.Dec - Feb Mar - Jun Jul - Aug Aug - Oct Dec - JanCommonAvionicsEnablerNARGUSNPlatformNARGTop 5PlatformIssuesCNAFN8CNAFTYCOMPriority PanelCNAFTYCOMPriority ListRecommendedAvionics Priority ListsPlatformTop 5AvionicsIssuesAvionicsESCTop 5 FleetAvionicsIssuesOPNAVN98 PRRBriefsN98Rack &StackFlag LevelInvestmentPrioritiesConferenceFleetFeedUSMCPlatformOAGTop 5PlatformIssuesHQMCAPWAPWCouncil ofColonelsDCARack &StackAviationSponsor’sProgramProposalCommonAvionicsUSN PlatformUSMC PlatformAcquisitionAlignmentPMA209 ACEPlatform PMAsCommon &Platform ROsAcquisition FeedACE = Air Combat ElectronicsNARG = Naval Aviation Reqts GroupOAG = Operational Advisory GroupESC = Executive Steering CommitteeCNAF = Commander Naval Air ForcesOPNAV = CNO OfficesDCA = Deputy Commandant AviationAPW = HQ USMC Aviation Pgms WepsPRR = Program Requirement ReviewsFLIP = Flag Level Investment PrioritiesSPP = Sponsor’s Program ProposalCore Avionics Issue Capture Process.Core Section CAMP 2012 4
Core Avionics Master Plan2. Where possible, leverage existing 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 outlined in JCDs in at least one of the militaryServices. Platform and commodity managers pursuing new programs or spiral upgradesare encouraged to leverage existing JCDs to accelerate program initiation. OPNAV N98has personnel assigned to assist with review of existing JCDs, as well as developmentand staffing of new ones.3. Use commodity evolution roadmaps to align the timing of pursuit andintegration of avionics-based capabilities across platforms to enable collectiveresourcing and broader benefits. Requirements are generated when threats change,tactics change or new mission creates a capability gap. Avionics solutions can 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 III above. The timelines foractivities in the capability sub-elements portray when enhancements are beingdeveloped and are expected to be mature, based upon technology growth andprogrammatic preparation time. Platform requirements officers and program managersare recommended to use these roadmaps to create their capability roadmaps and flightplans so that they may align with planned avionics capability enhancements as well asother platform initiatives to deliver broader collective benefits and improvedinteroperability across the enterprise.4. Define requirements in terms of warfighting capabilities necessary toaccomplish a platform mission in support of Combatant Commander strategicobjectives. DoD leadership has outlined future warfighting capability objectives in JointVision 2020. The Navy Aviation Plan 2030 (NAvPlan) and Marine Corps Aviation Plan(Marine AvPlan) list more detailed objectives for Naval Aviation warfighting capabilities,including more detailed definition of future force structures. The ultimate customers forcapabilities enabled by core avionics are not necessarily the platform communities, butthe COCOMs who apply their mission sets in Joint operations. Clear explanation of thespecific tactical application is essential in the budgeting prioritization process. Proposedissue costs are built upon programmatic aspects, but resource allocation prioritizationdecisions are primarily based upon criticality of operational capability gaps andwarfighting benefits. For example: funds are not required to ‘integrate SATCOM;’ theyare required to ‘enable platform X to conduct over the horizon tactical informationsituational awareness exchanges in order to perform long range expeditionaryoperations in support of Joint Command and Control objectives.’Core Section CAMP 2012 5
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: IV. RECOMMENDED PRACTICES.Core Avio
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 63 and 64:
Core Avionics Master Plan 2012 Appe
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Page 91 and 92:
Page 93 and 94:
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?