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

More documents

Recommendations

Info

Core Avionics Master PlanC. Acquisition. Acquisition management is performed by the “Provider” element ofthe NAE triad. NAVAIRSYSCOM delivers and sustains system solutions for the Fleetusers. DoD Transformation has driven significant revision of the DoD and Secretary ofthe Navy (SECNAV) 5000 series acquisition instructions. Policies and direction nowmore directly align with JCIDS processes to focus on support for the COCOMs. DoDI5000.02 also presents a new framework for Evolutionary Acquisition, which is describedas the preferred strategy for rapid acquisition of mature technology for the user. PMshave ultimate responsibility for cradle to grave management of their weapons systems.Recommended practices presented in CAMP 2011 are built upon existing acquisitionpolicies that support defined NAE objectives.Defense Acquisition Management System, Dec 2008.The following acquisition guidance covers processes and practices that supportCAMP 2011 and Naval Aviation leadership objectives.SECNAVINST 5000.2D (para.3.4.6.5. Standardization and Commonality) states:“Common systems can provide efficiencies that include inherently greaterinteroperability, lower total ownership costs, improved human performance, consistentand integrated roadmaps for system evolution, and planned dual-use functions.Acquisition strategies shall identify common systems integrated into the acquisitionprogram.”SECNAVINST 5000.2D (para 6.4.1 Weapon System Analysis of Alternatives)states: “The cognizant Program Executive Officer (PEO)/SYSCOM Commander/DirectReporting Program Manager (DRPM), or ASN(RD&A), and Chief of Naval Operations(CNO)/Commandant of the Marine Corps (CMC), but not the PM, shall have overallresponsibility for the Analysis of Alternatives (AoA). The CNO/CMC, or designee, shallpropose an AoA Plan in coordination with an AoA Integrated Product Team (IPT), underthe overall guidance of the Acquisition Coordination Team (ACT) where established(see reference (d)). All AoAs shall include analysis of Doctrine, Organization, Training,Materiel, Leadership and education, Personnel, and Facilities (DOTMLPF) and jointimplications. Common systems shall be included as one of the alternatives when onemay provide the needed capability.Core Section CAMP 2011 8
Core Avionics Master PlanSECNAVISNT 5000.2D (para.7.1.9.2. Standardization and Commonality) states:“PMs shall establish a process to reduce the proliferation of non-standard parts andequipment within and across system designs. The process shall include the periodicevaluation of different items having similar capabilities, characteristics, and functionsused in existing type, model, series and class designs to reduce the number of distinctitems.”ASN RDA Memorandum (23Dec04. Horizontal Systems Engineering) states:“Cross-platform commonality is difficult to reconcile with requirements and schedules inour normal vertical management of acquisition programs. It becomes furthercomplicated when we delegate decisions on modularity and families of systems to primecontractors, who will understandably optimize for their particular business models ratherthan ours.” This memorandum established Executive Committees to “makerecommendations and action assignments to develop architectures, roadmaps andimplementation plans to increase commonality” and to “seek opportunities forEnterprise-wide commonality in hardware and software modules.”OPNAV N88 Program Objective Memorandum (POM), Fiscal Years 2013-2017Initial Scheduling and Program Requirements Review (PRR) (02Sep10, para 5.g.)states: “Common Capabilities: Common capabilities are those systems that can beemployed across multiple platforms. Issues that address these capabilities should becoordinated with the appropriate Common Systems Requirements Officers in N881, toinclude Aircrew Systems, Avionics, Mission Planning and Safety Systems. CommonSystems program offices will work with each platform program office to capture theirrequirements and coordinate the building of a consolidated issue sheets detailing theefficiencies achieved by leveraging multiple users. Common Systems RequirementsOfficers will brief a prioritized consolidated issue sheet in their PRR. Programs shouldbe fully prepared to justify any unique stand alone system to a common solution duringtheir PRR.Leaders are encouraged to apply the following recommended practices topromote efficient acquisition and fielding of core avionics-enabled capabilities.1. Prominently factor commonality, standardization, interoperability,supportability and affordability during development of new capability solutions orenhancements. Component commonality can enable the following benefits:Avoidance of duplicative research and development program investmentsAvoidance of duplicative sustainment management and upgrade effortsReduced acquisition staffingEconomy of scale in procurementIncreased competitive Industry interest (larger contracts)Fewer logistics tails and reduced logistics overheadReduced spares requirements and smaller inventory footprintsIncreased applicability of upgrades and enhancementsIncreased interoperabilityCore Section CAMP 2011 9
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: Core Avionics Master PlanAvCIP proc
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 67 and 68:
Core Avionics Master Plan 2011 Appe
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:
show all

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

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

Delete template?

Save as template?