Abstract
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, 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 design and development for safety, operability, maintainability, reliability and testability. To be most effective, IVHM must be designed 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.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.