Skip to Main Content
Understanding Integrated Vehicle Health Management (IVHM) requires arriving at a common definition, one that captures all facets of the system. IVHM should not be treated as a standalone subsystem, added on to the vehicle. Nor should a group of sensors and related instrumentation system be considered IVHM. From a software perspective, IVHM is more than just fault models, algorithms and sensor processing software. While IVHM utilizes these components to perform its intended function, a true IVHM system incorporates a philosophy, methodology and process that focuses on design and development for safety, operability, maintainability, reliability and testability. To be most effective, IVHM must be "designed in" to the target system (i.e., the vehicle and its supporting infrastructure) from the beginning of the program, and not "added on" along the way. IVHM principles must permeate the culture and mindset of the organization, being held in similar regard to safety. IVHM must be elevated to the status of a system engineering discipline. To do so requires a conscious effort be made by all those involved in the program.
Digital Avionics Systems Conference, 2005. DASC 2005. The 24th (Volume:2 )
Date of Conference: 30 Oct.-3 Nov. 2005