Avionics cost of ownership

The cost of ownership of avionics includes not only the development and acquisition cost, but also the yearly operating and support (O and S) (maintenance) cost of hardware, software, and support equipment. This paper presents an avionics cost of ownership methodology developed for USAF, its data sources, and business metrics computed for USAF decision makers as we move toward operating avionics as a business. The business model is used to determine which existing avionics are candidates for replacement with new technology and to prioritize the replacements. These avionics are often used on multiple aircraft types which necessitates analysis of the causes of the high cost of ownership on each type. Databases are used to document the processing functions, data flow, and constraints of the item being analyzed. These constraints include physical, environmental, electrical, and data interfaces. Databases containing alternatives are evaluated against standard mission scenarios for aircraft utilizing these high cost avionics to determine their impact on performance, O and S costs, and mission effectiveness. The results of the foregoing analyses steps are then used in life cycle cost analyses which consider different retrofit scenarios for each alternative for each aircraft type against the avionics being analyzed for replacement. The alternatives are prioritized and a risk analysis performed considering technical, schedule, and cost growth risks. The avionics cost of ownership methodology described in this paper processes data from USAF maintenance organizations. This has revealed the very large expenditures being made to support highly unreliable avionics. These methods can be applied to all military and commercial aircraft systems to determine not only the cost of ownership of existing systems, but also the cost of ownership of new systems when they are retrofit     

Aging avionics: the problems and the challenges

Aging avionics have become a problem because aircraft are being kept in service far longer than the original plan. This paper discusses the four key problems of aging avionics: (1) determining the systems that are the high cost drivers in order to select those that should receive priority; (2) determining the requirements for the replacement; (3) identifying alternative technologies that will satisfy the requirements and are affordable; and (4) determining the funding required and acquiring the funding needed to replace the aging avionics. Challenges encountered in solving these problems include management and technical. The problem of aging avionics is not limited to a single aircraft, but occurs across all aircraft. Cost-effective modernization requires cutting horizontally across all aging aircraft, and coordination with the end users and the existing management structure. A key technical challenge is to select an architecture that is upgradeable since the funding limitations may ensure parts will become obsolete prior to the completion of a drawn-out production.     

Aging avionics and net-centric operations

The transformation to net-centric operations necessitates evaluation of existing avionics capabilities, identification of deficiencies of these avionics for net-centric operations, and evaluation of alternative avionics that can provide the needed capabilities. The Global Information Grid (GIG) enables net-centric operations. The purpose of the GIG is to provide end users real-time or near-real-time access to multiple information sources ranging from airborne/satellite/ground sensors (video imagery and processed visual information/data) to databases. The end users in an aircraft view and interact with this information through the human system interface (HSI) or "smart" displays. The information is transmitted across a Gigabit Ethernet on-board the aircraft that interfaces with multiple channels of a software programmable radio that acts as a hub in the GIG network, or on-board sensors and processors. This paper presents the mandated capabilities, and the processes involved in determination of upgrades needed to achieve net-centric operations.     

Year 2000 impact on automated testing

Both US military and industry rely on automatic testing to verify the quality of manufacture and repair. Many testers still rely on computers designed and manufactured in the early 1980's. This includes systems using embedded controllers. Year 2000 problems can surface in computer operating systems, compilers, test programs, and in embedded systems. Until the impact of the Y2K “bug” is addressed, the risk of test program failure is unknown in most legacy automatic test systems. Problems may include embedded controllers in proprietary designs, old operating systems, and unique test program code. This paper will address the potential problem areas in automatic testing, and suggest an approach for determining the best course of action. In order to evaluate the impact, a complete systems inventory must be done to identify all potential sources of problems. Little attention has been paid to the legacy automated test systems and the potential impact of the Y2K problem on such systems. Although newer systems are less likely to be affected, no one can be sure until a complete inventory and test has been accomplished