Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Avionics”

Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.

Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.

At least 577 records · Page 32

Advanced software integration: The case for ITV facilities

The array of technologies and methodologies involved in the development and integration of avionics software has moved almost as rapidly as computer technology itself. Future avionics systems involve major advances and risks in the following areas: (1) Complexity; (2) Connectivity; (3) Security; (4) Duration; and (5) Software engineering. From an architectural standpoint, the systems will be much more distributed, involve session-based user interfaces, and have the layered architectures typified in the layers of abstraction concepts popular in networking. Typified in the NASA Space Station Freedom will be the highly distributed nature of software development itself. Systems composed of independent components developed in parallel must be bound by rigid standards and interfaces, the clean requirements and specifications. Avionics software provides a challenge in that it can not be flight tested until the first time it literally flies. It is the binding of requirements for such an integration environment into the advances and risks of future avionics systems that form the basis of the presented concept and the basic Integration, Test, and Verification concept within the development and integration life cycle of Space Station Mission and Avionics systems.

Garman, John R.↗

An overview of autonomous rendezvous and docking system technology development

The Centaur upper stage was selected for an airborne avionics modernization program. The parts used in the existing avionics units were obsolete. Continued use of existing hardware would require substantial redesign, yet would result in the use of outdated hardware. Out of date processes, with very expensive and labor intensive technologies, were being used for manufacturing. The Atlas/Centaur avionics were to be procured at a fairly high rate that demanded the use of modern components. The new avionics also reduce size, weight, power, and parts count with a dramatic improvement in reliability. Finally, the cost leverage derived from upgrading the avionics as opposed to any other subsystem for the existing Atlas/Centaur was a very large consideration in the upgrade decision. The upgrade program is a multiyear effort that began in 1989. It includes telemetry, guidance and navigation, control electronics, thrust vector control, and redundancy levels.

Nelson, Kurt D.↗

An overview of autonomous rendezvous and docking system technology development at General Dynamics

The Centaur avionics suite is undergoing a dramatic modernization for the commercial, DoD Atlas and Titan programs. The system has been upgraded to the current state-of-the-art in ring laser gyro inertial sensors and Mil-Std-1750A processor technology. The Cruise Missile avionic system has similarly been evolving for many years. Integration of GPS into both systems has been underway for over five years with a follow-on cruise missile system currently in flight test. Rendezvous and Docking related studies have been conducted for over five years in support of OMV, CTV, and Advanced Upper Stages, as well as several other internal IR&D's. The avionics system and AR&D simulator demonstrated to the SATWG in November 1990 has been upgraded considerably under two IR&D programs in 1991. The Centaur modern avionics system is being flown in block upgrades which started in July of 1990. The Inertial Navigation Unit will fly in November of 1991. The Cruise Missile avionics systems have been fully tested and operationally validated in combat. The integrated AR&D system for space vehicle applications has been under development and testing since 1990. A Joint NASA / GD ARD&L System Test Program is currently being planned to validate several aspects of system performance in three different NASA test facilities in 1992.

Kuenzel, Fred↗

Hypervelocity impact testing of the Space Station utility distribution system carrier

A two-phase, joint JSC and McDonnell Douglas Aerospace-Huntington Beach hypervelocity impact (HVI) test program was initiated to develop an improved understanding of how meteoroid and orbital debris (M/OD) impacts affect the Space Station Freedom (SSF) avionic and fluid lines routed in the Utility Distribution System (UDS) carrier. This report documents the first phase of the test program which covers nonpowered avionic line segment and pressurized fluid line segment HVI testing. From these tests, a better estimation of avionic line failures is approximately 15 failures per year and could very well drop to around 1 or 2 avionic line failures per year (depending upon the results of the second phase testing of the powered avionic line at White Sands). For the fluid lines, the initial McDonnell Douglas analysis calculated 1 to 2 line failures over a 30 year period. The data obtained from these tests indicate the number of predicted fluid line failures increased slightly to as many as 3 in the first 10 years and up to 15 for the entire 30 year life of SSF.

Lazaroff, Scott↗

Fault tolerant testbed evaluation, phase 1

In recent years, avionics systems development costs have become the driving factor in the development of space systems, military aircraft, and commercial aircraft. A method of reducing avionics development costs is to utilize state-of-the-art software application generator (autocode) tools and methods. The recent maturity of application generator technology has the potential to dramatically reduce development costs by eliminating software development steps that have historically introduced errors and the need for re-work. Application generator tools have been demonstrated to be an effective method for autocoding non-redundant, relatively low-rate input/output (I/O) applications on the Space Station Freedom (SSF) program; however, they have not been demonstrated for fault tolerant, high-rate I/O, flight critical environments. This contract will evaluate the use of application generators in these harsh environments. Using Boeing's quad-redundant avionics system controller as the target system, Space Shuttle Guidance, Navigation, and Control (GN&C) software will be autocoded, tested, and evaluated in the Johnson (Space Center) Avionics Engineering Laboratory (JAEL). The response of the autocoded system will be shown to match the response of the existing Shuttle General Purpose Computers (GPC's), thereby demonstrating the viability of using autocode techniques in the development of future avionics systems.

Caluori, V., Jr.↗

Development of a Vehicle Health Monitoring System for the Space Shuttle Solid Rocket Booster Program

During their brief flight, the space shuttle solid rocket boosters (SRBs) experience a severe environment. This environment in most cases is unknown. When the design engineers believe they understand the environments, something new occurs. For example, at water impact several SRBs have sustained noticeable structural damage. The severity of the damage is usually dependent upon the waves that the SRB encounter at splashdown. The space shuttle is presently scheduled to fly until 2030. To support the shuttle flight schedule, the avionics on the SRB's will need to be upgraded. The environments on the different sections of the SRB will need to be defined more completely to properly qualify the avionics for multiple flights. The combination of new avionics systems and unknown flight environments led Marshall Space Flight Center's (MSFC) SRB Project Office to request the Science and Engineering (S&E) Directorate to develop a stand-alone data acquisition system that could collect data from any area of the booster. The Enhanced Data Acquisition System (EDAS) was developed to meet this request. However, the EDAS has some technical drawbacks that needed resolved. To answer the EDAS problems, the SRB Project Office has funded MSFC's Avionics Department to begin investigating a new vehicle health monitoring (VHM) system. The major requirements are the system shall have 64 channels, have programmable sample rates up to 10,000 samples per second, have sufficient memory for a twenty minute flight and not interfere with existing operational flight avionics hardware. This paper will describe the effort to develop a VHM system that can meet the SRB requirements.

Crawford, Kevin↗

The Design of Model-Based Training Programs

This paper proposes a model-based training program for the skills necessary to operate advance avionics systems that incorporate advanced autopilots and fight management systems. The training model is based on a formalism, the operational procedure model, that represents the mission model, the rules, and the functions of a modem avionics system. This formalism has been defined such that it can be understood and shared by pilots, the avionics software, and design engineers. Each element of the software is defined in terms of its intent (What?), the rationale (Why?), and the resulting behavior (How?). The Advanced Computer Tutoring project at Carnegie Mellon University has developed a type of model-based, computer aided instructional technology called cognitive tutors. They summarize numerous studies showing that training times to a specified level of competence can be achieved in one third the time of conventional class room instruction. We are developing a similar model-based training program for the skills necessary to operation the avionics. The model underlying the instructional program and that simulates the effects of pilots entries and the behavior of the avionics is based on the operational procedure model. Pilots are given a series of vertical flightpath management problems. Entries that result in violations, such as failure to make a crossing restriction or violating the speed limits, result in error messages with instruction. At any time, the flightcrew can request suggestions on the appropriate set of actions. A similar and successful training program for basic skills for the FMS on the Boeing 737-300 was developed and evaluated. The results strongly support the claim that the training methodology can be adapted to the cockpit.

Polson, Peter↗

Results from an Interval Management (IM) Flight Test and Its Potential Benefit to Air Traffic Management Operations

NASA's first Air Traffic Management Technology Demonstration (ATD-1) subproject successfully completed a 19-day flight test of an Interval Management (IM) avionics prototype. The prototype was built based on IM standards, integrated into two test aircraft, and then flown in real-world conditions to determine if the goals of improving aircraft efficiency and airport throughput during high-density arrival operations could be met. The ATD-1 concept of operation integrates advanced arrival scheduling, controller decision support tools, and the IM avionics to enable multiple time-based arrival streams into a high-density terminal airspace. IM contributes by calculating airspeeds that enable an aircraft to achieve a spacing interval behind the preceding aircraft. The IM avionics uses its data (route of flight, position, etc.) and Automatic Dependent Surveillance-Broadcast (ADS-B) state data from the Target aircraft to calculate this airspeed. The flight test demonstrated that the IM avionics prototype met the spacing accuracy design goal for three of the four IM operation types tested. The primary issue requiring attention for future IM work is the high rate of IM speed commands and speed reversals. In total, during this flight test, the IM avionics prototype showed significant promise in contributing to the goals of improving aircraft efficiency and airport throughput.

Baxley, Brian↗

ISS Science Payload Command & Data Handling

For decades, the International Space Station (ISS) has provided a distinctive platform in low Earth orbit for experimental research. In support of this platform is a family of avionics systems that enables reliable data distribution of the many science payloads installed, and future internal and external payloads. This poster provides an update to the ISS avionics hardware system architecture, including design change successes, test bed architecture, and performance upgrades in the operation of all ISS avionics. We conclude with an outlook on future avionics system enhancements required to support additional modules and payload expansions taking place on the ISS, and how these avionics systems translate to a lunar gateway.

1553↗

Design and Technology Maturation of the Stratospheric Projectile Experiment of Entry Dynamics

The supersonic and transonic dynamic stability of blunt-body reentry vehicles currently poses large risks in all of NASA’s ongoing entry missions (MSR SRL, MSR EES, and Dragonfly). These projects have allocated millions of dollars to testing and modeling efforts to buy down risk by using the current state-of-the-art (SoA) facilities at NASA’s disposal. While these facilities have heritage in supplying dynamics data to reentry missions, their availability is severely limited – particularly with the high number of concur-rent projects requesting simultaneous testing– and are costly when considering the science density per dollar. None of the current SoA facility methodologies allow the test model to have the dynamics fully develop through a flight relevant free-stream profile and as such require extrapolations with resultant high uncertainties in order to relate the test dynamics to flight expectations. SPEED is a NASA Ames Center Innovation Fund (CIF) project that is developing a highly tailorable and cost-effective test methodology to better assess the dynamic stability of blunt-body reentry vehicles via a stratospheric balloon flight. This is accomplished by dropping a suite of instrumented capsules from a stratospheric balloon to gain a statistically relevant dataset of scaled reentry vehicles in mission relevant free-flight conditions. This presentation will walk through how the test methodology is being implemented specifically for the Mars Sample Return (MSR) Earth Entry System (EES) geometry in an awarded Flight Opportunities Program (FOP) test flight in early CY24. SPEED Application to MSR: SPEED consists of three main mechanical systems: the Drop Platform, the Projectile, and the test Capsule. SPEED is being developed as a set of guidelines and recommendations for how to test with the proposed Concept of Operations (Conops) since the specific design parameters will vary depending on the specific project’s reference trajectory and entry vehicle design. As such, this presentation will walk through the development time-line as shown in Fig. 2. This is meant to serve as a blueprint for further missions as desired. Mechanical and Avionics Design. The SPEED test platform designed for the MSR-EES capsule geometry with nominal entry parameters has the ability to carry 10 Capsules to altitude instrumented with: 1. 3-Axis Accelerometer 2. IMU 3. Gyroscope 4. Magnetometer 5. Pressure Transducer cruciform 6. Uplook and Horizon Cameras To package the avionics/instrumentation suite, the capsule is approximately 1’ in diameter with the Outer Mold Line (OML) centroid-scaled from the full EES design. The internal volume is gutted and custom-shaped to fit the desired instrumentation suite, as well as to allow for the positioning of ballast mass such that the Center of Gravity is analogous to the flight vehicle. All structural components in the Capsule and Projectile are 3D printed, which significantly reduces the cost of each flight unit to around $1500 including all instrumentation, avionics, and structural components. Flight Conops. The test Capsule is accelerated to the desired altitude and Mach number while stowed in the Projectile, a missile-like vehicle consisting of steel ballast in the nose, a low-drag OML, and an Ejection Mechanism to reliably release the Capsule into the free-flow supersonic conditions. For the MSR-EES design, the capsule employs ~3kg of ballast mass at the nose to accelerate the 1.25kg test Capsule to ~Mach 1.7 at 23km altitude. This requires an initial release altitude of 40km, the quoted limit of a 80kg payload by the FOP-contracted balloon provider. Once the Ejection Mechanism avionics detect the proper conditions, the spring-loaded Ejection Mechanism will release and – guided by the sabot – expose the test Capsule to the desired test conditions for ~5 seconds of free-flight in the supersonic/transonic regimes. Dynamics in the subsonic regime will also be captured with the instrumentation suite with post-flight recovery operations aimed at recovering the high-G-load capable SD cards after the planned hard impact landings. Testing and Development: In the few months the SPEED project has worked the development of MSR-EES flight test, the team has performed lab and drone based testing which this presentation will overview. After the first design phase, the team fabricated Engineering Demonstration Units (EDUs) of all subsystems to perform validation testing shown in Fig. 5. After validation was completed on the subsystem level, a drone-drop test was performed at the recreational flight ceiling of 400ft altitude to assess the SPEED systems in a flight environment. Parameters such as in-flight stability, hard impact landing performance, and avionics performance were quantified and qualified. The FY23 CIF will culminate in a helicopter drop test aboard an Air National Guard Blackhawk. This will prepare the team for the CY24 FOP stratospheric balloon flight that should provide the final verification to begin offering the test platform for mission support. Focus of Presentation: This presentation will outline the technology maturation path of the SPEED implementation to the MSR-EES capsule baseline as well as the details regarding the mechanical system, avionics and instrumentation, and flight operations. Note that a complementary presentation is being submitted for a methodology overview of the SPEED test platform, introducing the testing technique and benefits as well as the full application space of the technology.

pitch damping coefficient↗

Verification of the Space Shuttle ascent flight control

The unique avionics design features of the Space Shuttle ascent flight control are described, along with the test article, test equipment, and test techniques used to verify the ascent flight control prior to commitment to the first orbital flight test. The ascent mission profiles are described, noting that upon ignition of the solid rocket boosters the Shuttle vehicle will rise vertically until achieving tower clearance. The Space Shuttle vehicle uses an integrated avionics system with the Orbiter avionics providing the command, control, and monitoring for the total mated Shuttle vehicle. The sensors and the actuator systems are discussed; the method of ascent flight control system verification is described, and it is concluded that the need for an advanced avionics integration and verification laboratory was recognized early in the program to provide maximum support to all program requirements.

Chambers, T. V.↗

Functional design to support CDTI/DABS flight experiments

The objectives of this project are to: (1) provide a generalized functional design of CDTI avionics using the FAA developd DABS/ATARS ground system as the 'traffic sensor', (2) specify software modifications and/or additions to the existing DABS/ATARS ground system to support CDTI avionics, (3) assess the existing avionics of a NASA research aircraft in terms of CDTI applications, and (4) apply the generalized functional design to provide research flight experiment capability. DABS Data Link Formats are first specified for CDTI flight experiments. The set of CDTI/DABS Format specifications becomes a vehicle to coordinate the CDTI avionics and ground system designs, and hence, to develop overall system requirements. The report is the first iteration of a system design and development effort to support eventual CDTI flight test experiments.

Goka, T.↗

Primary display latency criteria based on flying qualities and performance data

With a pilots' increasing use of visual cue augmentation, much requiring extensive pre-processing, there is a need to establish criteria for new avionics/display design. The timeliness and synchronization of the augmented cues is vital to ensure the performance quality required for precision mission task elements (MTEs) where augmented cues are the primary source of information to the pilot. Processing delays incurred while transforming sensor-supplied flight information into visual cues are unavoidable. Relationships between maximum control system delays and associated flying qualities levels are documented in MIL-F-83300 and MIL-F-8785. While cues representing aircraft status may be just as vital to the pilot as prompt control response for operations in instrument meteorological conditions, presently, there are no specification requirements on avionics system latency. To produce data relating avionics system latency to degradations in flying qualities, the Navy conducted two simulation investigations. During the investigations, flying qualities and performance data were recorded as simulated avionics system latency was varied. Correlated results of the investigation indicates that there is a detrimental impact of latency on flying qualities. Analysis of these results and consideration of key factors influencing their application indicate that: (1) Task performance degrades and pilot workload increases as latency is increased. Inconsistency in task performance increases as latency increases. (2) Latency reduces the probability of achieving Level 1 handling qualities with avionics system latency as low as 70 ms. (3) The data suggest that the achievement of desired performance will be ensured only at display latency values below 120 ms. (4) These data also suggest that avoidance of inadequate performance will be ensured only at display latency values below 150 ms.

Funk, John D., Jr.↗

Analysis of Autopilot Behavior

Aviation and cognitive science researchers have identified situations in which the pilot's expectations for behavior of autopilot avionics are not matched by the actual behavior of the avionics. These "automation surprises" have been attributed to differences between the pilot's model of the behavior of the avionics and the actual behavior encoded in the avionics software. A formal technique is described for the analysis and measurement of the behavior of the cruise pitch modes of a modern Autopilot. The analysis characterizes the behavior of the Autopilot as situation-action rules. The behavior of the cruise pitch mode logic for a contemporary modern Autopilot was found to include 177 rules, including Level Change (23), Vertical Speed (16), Altitude Capture (50), and Altitude Hold (88). These rules are determined based on the values of 62 inputs. Analysis of the rule-based model also shed light on the factors cited in the literature as contributors to "automation surprises."

Sherry, Lance↗

A Comprehension Based Analysis of Autoflight System Interfaces

This cooperative agreement supported Dr. Peter Polson's participation in two interrelated research programs. The first was the development of the Situation-Goal-Behavior (SGB) Model that is both a formal description of an avionics system's logic and behavior and a representation of a system that can be understood by avionics designers, pilots, and training developers. The second was the development of a usability inspection method based on an approximate model, RAFIV, of pilot interactions with the Flight Management System (FMS). The main purpose of this report is to integrate the two models and provide a context in order to better characterize the accomplishments of this research program. A major focus of both the previous and this Cooperative Agreement was the development of usability evaluation methods that can be effectively utilized during all phases of the design, development, and certification process of modern avionics systems. The current efforts to validate these methods have involved showing that they generate useful analyses of known operational and training problems with the current generation of avionics systems in modern commercial airliners. This report is organized into seven sections. Following the overview, the second section describes the Goal-Situation-Behavior model and its applications. The next section summarizes the foundations of the RAFIV model and describes the model in some detail. The contents of both these sections are derived from previous reports referenced in footnotes. The fourth section integrates these two models into a complete design evaluation and training development framework. The fifth section contains conclusions and possible future directions for research. References are in Section 6. Section 7 contains the titles and abstracts of the papers paper describing in more detail the results of this research program.

Palmer, Everett↗

IVHM Framework for Intelligent Integration for Vehicle Health Management

Integrated Vehicle Health Management (IVHM) systems for aerospace vehicles, is the process of assessing, preserving, and restoring system functionality across flight and techniques with sensor and communication technologies for spacecraft that can generate responses through detection, diagnosis, reasoning, and adapt to system faults in support of Integrated Intelligent Vehicle Management (IIVM). These real-time responses allow the IIVM to modify the affected vehicle subsystem(s) prior to a catastrophic event. Furthermore, this framework integrates technologies which can provide a continuous, intelligent, and adaptive health state of a vehicle and use this information to improve safety and reduce costs of operations. Recent investments in avionics, health management, and controls have been directed towards IIVM. As this concept has matured, it has become clear that IIVM requires the same sensors and processing capabilities as the real-time avionics functions to support diagnosis of subsystem problems. New sensors have been proposed, in addition to augment the avionics sensors to support better system monitoring and diagnostics. As the designs have been considered, a synergy has been realized where the real-time avionics can utilize sensors proposed for diagnostics and prognostics to make better real-time decisions in response to detected failures. IIVM provides for a single system allowing modularity of functions and hardware across the vehicle. The framework that supports IIVM consists of 11 major on-board functions necessary to fully manage a space vehicle maintaining crew safety and mission objectives. These systems include the following: Guidance and Navigation; Communications and Tracking; Vehicle Monitoring; Information Transport and Integration; Vehicle Diagnostics; Vehicle Prognostics; Vehicle Mission Planning, Automated Repair and Replacement; Vehicle Control; Human Computer Interface; and Onboard Verification and Validation. Furthermore, the presented framework provides complete vehicle management which not only allows for increased crew safety and mission success through new intelligence capabilities, but also yields a mechanism for more efficient vehicle operations.

Paris, Deidre↗

A Framework for Integration of IVHM Technologies for Intelligent Integration for Vehicle Management

As a part of the overall goal of developing Integrated Vehicle Health Management (IVHM) systems for aerospace vehicles, the NASA Faculty Fellowship Program (NFFP) at Marshall Space Flight Center has performed a pilot study on IVHM principals which integrates researched IVHM technologies in support of Integrated Intelligent Vehicle Management (IIVM). IVHM is the process of assessing, preserving, and restoring system functionality across flight and ground systems (NASA NGLT 2004). The framework presented in this paper integrates advanced computational techniques with sensor and communication technologies for spacecraft that can generate responses through detection, diagnosis, reasoning, and adapt to system faults in support of IIVM. These real-time responses allow the IIVM to modify the effected vehicle subsystem(s) prior to a catastrophic event. Furthermore, the objective of this pilot program is to develop and integrate technologies which can provide a continuous, intelligent, and adaptive health state of a vehicle and use this information to improve safety and reduce costs of operations. Recent investments in avionics, health management, and controls have been directed towards IIVM. As this concept has matured, it has become clear the IIVM requires the same sensors and processing capabilities as the real-time avionics functions to support diagnosis of subsystem problems. New sensors have been proposed, in addition, to augment the avionics sensors to support better system monitoring and diagnostics. As the designs have been considered, a synergy has been realized where the real-time avionics can utilize sensors proposed for diagnostics and prognostics to make better real-time decisions in response to detected failures. IIVM provides for a single system allowing modularity of functions and hardware across the vehicle. The framework that supports IIVM consists of 11 major on-board functions necessary to fully manage a space vehicle maintaining crew safety and mission objectives: Guidance and Navigation; Communications and Tracking; Vehicle Monitoring; Information Transport and Integration; Vehicle Diagnostics; Vehicle Prognostics; Vehicle mission Planning; Automated Repair and Replacement; Vehicle Control; Human Computer Interface; and Onboard Verification and Validation. Furthermore, the presented framework provides complete vehicle management which not only allows for increased crew safety and mission success through new intelligence capabilities, but also yields a mechanism for more efficient vehicle operations. The representative IVHM technologies for IIVH includes: 1) robust controllers for use in re-usable launch vehicles, 2) scaleable/flexible computer platform using heterogeneous communication, 3) coupled electromagnetic oscillators for enhanced communications, 4) Linux-based real-time systems, 5) genetic algorithms, 6) Bayesian Networks, 7) evolutionary algorithms, 8) dynamic systems control modeling, and 9) advanced sensing capabilities. This paper presents IVHM technologies developed under NASA's NFFP pilot project. The integration of these IVHM technologies forms the framework for IIVM.

Paris, Deidre E.↗

Intelligent Vehicle Health Management

As a part of the overall goal of developing Integrated Vehicle Health Management systems for aerospace vehicles, the NASA Faculty Fellowship Program (NFFP) at Marshall Space Flight Center has performed a pilot study on IVHM principals which integrates researched IVHM technologies in support of Integrated Intelligent Vehicle Management (IIVM). IVHM is the process of assessing, preserving, and restoring system functionality across flight and ground systems (NASA NGLT 2004). The framework presented in this paper integrates advanced computational techniques with sensor and communication technologies for spacecraft that can generate responses through detection, diagnosis, reasoning, and adapt to system faults in support of INM. These real-time responses allow the IIVM to modify the affected vehicle subsystem(s) prior to a catastrophic event. Furthermore, the objective of this pilot program is to develop and integrate technologies which can provide a continuous, intelligent, and adaptive health state of a vehicle and use this information to improve safety and reduce costs of operations. Recent investments in avionics, health management, and controls have been directed towards IIVM. As this concept has matured, it has become clear the INM requires the same sensors and processing capabilities as the real-time avionics functions to support diagnosis of subsystem problems. New sensors have been proposed, in addition, to augment the avionics sensors to support better system monitoring and diagnostics. As the designs have been considered, a synergy has been realized where the real-time avionics can utilize sensors proposed for diagnostics and prognostics to make better real-time decisions in response to detected failures. IIVM provides for a single system allowing modularity of functions and hardware across the vehicle. The framework that supports IIVM consists of 11 major on-board functions necessary to fully manage a space vehicle maintaining crew safety and mission objectives: Guidance and Navigation; Communications and Tracking; Vehicle Monitoring; Information Transport and Integration; Vehicle Diagnostics; Vehicle Prognostics; Vehicle mission Planning; Automated Repair and Replacement; Vehicle Control; Human Computer Interface; and Onboard Verification and Validation. Furthermore, the presented framework provides complete vehicle management which not only allows for increased crew safety and mission success through new intelligence capabilities, but also yields a mechanism for more efficient vehicle operations. The representative IVHM technologies for computer platform using heterogeneous communication, 3) coupled electromagnetic oscillators for enhanced communications, 4) Linux-based real-time systems, 5) genetic algorithms, 6) Bayesian Networks, 7) evolutionary algorithms, 8) dynamic systems control modeling, and 9) advanced sensing capabilities. This paper presents IVHM technologies developed under NASA's NFFP pilot project and the integration of these technologies forms the framework for IIVM.

Paris, Deidre E.↗