11.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

IV. RECOMMENDED PRACTICES.<strong>Core</strong> <strong>Avionics</strong> <strong>Master</strong> <strong>Plan</strong>With limited resources available to balance current and future readiness, NavalAviation cannot afford to pay for independent development or separate and discretemodification of core avionics over every platform’s life cycle. The Fleet cannot affordduplicative overhead costs of multiple unique systems that address a similarfunctionality. The acquisition workforce must work to capture overhead efficiencies thatreduce their costs of doing business. The Secretary of Defense (SECDEF) andChairman of the Joint Chiefs of Staff (CJCS) recently instituted a comprehensiverevision of the requirements generation process and acquisition managementinstructions. In order to provide the greatest aviation system capabilities and warfightingbenefits for the dollars available, this master plan presents recommended practices foreach realm of the NAE triad.A. Requirements. Requirements are capability needs identified (generated) bywarfighters and formally documented using processes prescribed in CJCS Instruction3170.01F, Joint Capability Integration and Development System (JCIDS). Solutions tosatisfy requirements are developed, fielded and sustained by acquisition programmanagers. Funds to cover solutions development, fielding and sustainment areallocated by <strong>Navy</strong> OPNAV and Marine Corps Deputy Commandant, Aviation (DC/A),resource sponsors. When Fleet operators first identify specific mission capability gaps,they are not constrained by resource limitations. Fiscal realities are applied later duringissue prioritization in the programming and budgeting phases of budget building.Leaders are encouraged to apply the following recommended requirementsidentification and documentation practices to promote efficient fielding and sustainmentof capabilities enabled by core avionics.1. Use the USN Naval Aviation Requirements Group (NARG) and USMCOperational Advisory Group (OAG) processes to identify and prioritize coreavionics requirements according to collective need and benefits. In response tothe Fleet Forces Command (FFC) Requirements office call for more standardization inFleet requirements identification, the aviation Type Commander (TYCOM), Naval AirForces (CNAF), promulgated CNAF Instruction 3025.1. It establishes methodologiesand guidance for aviation requirements identification and prioritization. This documentwas updated in December 2011. It outlines roles, responsibilities and processes forconducting NARG events, which replaced the former <strong>Navy</strong> OAGs. The Marine Corpscontinues to use the OAG process, but directly interfaces with the NARG process. Theinstruction establishes both Platform NARGs and Enabler NARGs.Common <strong>Avionics</strong>, Cooperative Surveillance and Airborne Electronic WarfareEnabler NARGs are held prior to Platform NARG and OAG meetings. A Marine Corps<strong>Avionics</strong> Officer serves as the CNAF N8 Common <strong>Avionics</strong> Requirements Officer, andchairs the Common <strong>Avionics</strong> Enabler NARG and Executive Steering Committee (ESC)events. Platform community representatives are invited to the Enabler NARGs. Theyare briefed on avionics-enabled capability areas to help understand solution maturity,operational relevance and timing of applicable deadlines. They also collaborativelydevelop tailored recommended priority lists of commodity system enabled requirements.<strong>Core</strong> Section CAMP <strong>2012</strong> 3

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!