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

More documents

Recommendations

Info

Core Avionics Master Plan 2011 Appendix A-1Core AvionicsCapability EvolutionRoadmapsInformation ManagementOpen Systems ProcessorCapabilityElementsComprehensive Mission Preparation & Effective ExecutionMulti-Level Security;On-board TacticalData Fusion (JSF)EmbeddedGraphics CardInformationProcessingFPGA Bit Stream Data Electromagnetic Field AnalysisModular, Aircraft OFPSoftwareManagementArchitectureCommon ApplicationProgramming Interfaces(API); Software LicensesSoftware Transportability(FACE)Future Airborne CapabilityEnvironment (FACE) StandardsVisualization Tools for Causal Data Mining.Low Cost High Assurance Separation Kernel.Integrity and Authentication of Real-Time Data.Limited Capacity Loaders/1553, Fiber Channel, Point to Point Ethernet BusesHigher Capacity, Multi-Level SecurityRecording & Up/Download (ADDS)Wireless InformationDownload (T-45, JSF)InformationTransfer &StorageNVG CompatibleImproved Backlighting (LEDs)Large Area Programmable Layout DisplayInformationDisplayLimited Map and Mission Information CapacityMoving MapMulti-Level Security (MLS);Obstacle RepresentationIncreased Data Capacity(DTED Level II Moving Map – TAMMAC)Enhanced Visualization - Perspective Viewing1553, Fibre Channel, Ethernet BusesIncreased Data Distribution SpeedHigh Bandwidth Fiber Optic WDM MLS NetworksInformationDistributionInteroperable Unit Level Collaborative PlanningMissionPlanningService-oriented Planning; Expeditionary Planning Strike & Expeditionary Force Level PlanningDoD Modular Open System Architecture;Encryption of Data at RestMandates &MilestonesFY: 10 11 12 13 14 15 16 17 18Mandate orMilestoneUnfunded PotentialCapability DevelopmentFunded CapabilityEnhancementAdv ResearchOr Tech DevCurrent CapabilityBaseline StateA-1 Information Management 2
Core Avionics Master Plan 2011 Appendix A-1Baseline to Objective Transition Strategy (continued).Legacy platforms risk losing relevance in modern warfighting environments iftheir internal data storage capacity, processing power, or distribution bandwidth getsaturated. Several platforms employ unique mission processors hosting uniqueoperating systems and mission software applications. Each requires an independenteffort and platforms end up competing with each other for funds for similar corecapability enhancements, such as Mode 5 Combat ID, JPALS, Networking waveforms,M-Code GPS, and more. In the commercial world, computers of any brand usestandardized operating systems, and applications are designed to run on virtually allmakes and models. For Naval Aviation to achieve these objectives in a timely andaffordable manner, integrated avionics need to evolve to more open architectures andinterfaces that enable simpler integration of capability enhancements, both in terms ofsystem performance and standardized mission software applications. Glass cockpitsbeing integrated to enable Communications Navigation Surveillance / Air TrafficManagement (CNS/ATM) mandate compliance are providing a limited Modular OpenSystem Architecture (MOSA) that partitions communication and navigation software toenable modification without affecting the core Operational Flight Profile (OFP) missioncomputer software and operating system. Although this a step forward, that solution iscurrently only compatible with specific vendor and government coordinated softwareand component interfaces. Standardization of interfaces, protocols and software willenable a common operational picture and enhance platform-to-platform interoperability.These concepts need to be proven out in Naval aviation applications and implementedacross multiple aircraft Type/Model/Series in order to reduce test requirements,integration costs and time required to incorporate new capabilities.Mandates and Milestones:Encryption of Data at Rest Policy Memorandum. (Jul 2007) Establishes policy forprotection of sensitive unclassified information on mobile computing devices andremovable storage media. All unclassified data stored on removable storage devicesmust be treated as sensitive and be encrypted per standards set by the NationalInstitute of Standards and Technology (NIST) Federal Information Processing Standard140-2 (FIPS 140-2). This standard affects data storage devices as well as missionplanning and mission recording information handling. This policy is an extension ofguidance provided in DoDI 8500.2, Information Assurance (IA) Implementation.Modular Open Systems Architecture (MOSA). (Dec 2008) DOD 5000.02 Instructiondictates operation of the Defense Acquisition System states that program managersshall employ MOSA to design for affordable change, enable evolutionary acquisition,and rapidly field affordable systems that are interoperable in the joint battle space.Five key principles of MOSA:– Principle I: Establish an Enabling Environment– Principle II: Employ Modular Design– Principle III: Designate Key Interfaces– Principle IV: Use Open Standards– Principle V: Certify ConformanceA-1 Information Management 3
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 and 16: Core Avionics Master PlanAvCIP proc
Page 17 and 18: Core Avionics Master PlanSECNAVISNT
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: Core Avionics Master Plan 2011 Appe
Page 31 and 32: Core Avionics Master Plan 2011 Appe
Page 43 and 44: EP-3EP-3CRQ-4AMQ-8BEP-8AP-8AAH-1WAH
Page 79 and 80:
Core Avionics Master Plan 2011 Appe
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

Create successful ePaper yourself

Delete template?

Save as template?