Search Results

An IVHM Reference Model contains relations between Symptoms, Failure Modes, Troubleshooting Tests and Corrective Actions. Since it also encodes the specific vehicle variants for which these items are applicable, it can be used to create vehicle variant specific fault isolation plans for a pattern of symptoms on a specific vehicle. This paper will discuss the methodology through which a diagnostic reasoner can use a fault model, vehicle reported symptoms and vehicle configuration data to produce a vehicle fault specific troubleshooting plan. This paper will also discuss how a wide variety of Diagnostic Work Plans can be automatically created for a platform and its variants and how these plans can be adapted by Service Engineering authors to further improve their content.

An emerging emphasis for the design and development of vehicle condition-based maintenance (CBM) systems amplifies its use for conducting vehicle maintenance based on evidence of need. This paper presents a systems engineering approach to creating an integrated vehicle health management (IVHM) architecture which places emphasis on the system's ultimate use to meet the operational needs of the vehicle and fleet maintainer, to collect data, conduct analysis, and support the decision-making processes for the sustainment and operations of the vehicle and assets being monitored. The demand for a CBM system generally assumes that the asset being monitored is complex or that the operational use of the system demands complexity, timely response or that system failure has catastrophic results. Ground vehicles are such complex systems, which are the emphasis of this paper. Developing the system architecture of such complex systems demands a systematic approach.

The term Integrated Vehicle Health Management (IVHM) describes a set of capabilities that enable sustainable and safe operation of components and subsystems within aerospace platforms. However, very little guidance exists for the systems engineering aspects of design with IVHM in mind. It is probably because of this that designers have to use knowledge picked up exclusively by experience rather than by established process. This motivated a group of leading IVHM practitioners within the aerospace industry under the aegis of SAE's HM-1 technical committee to author a document that hopes to give working engineers and program managers clear guidance on all the elements of IVHM that they need to consider before designing a system. This proposed recommended practice (ARP6883 [1]) will describe all the steps of requirements generation and management as it applies to IVHM systems, and demonstrate these with a “real-world” example related to designing a landing gear system.

The aerospace ecosystem is a complex system of systems comprising of many stakeholders in exchanging technical, design, development, certification, operational, and maintenance data across the different lifecycle stages of an aircraft from concept, engineering, manufacturing, operations, and maintenance to its disposal. Many standards have been developed to standardize and improve the effectiveness, efficiency, and security of the data transfer processes in the aerospace ecosystem. There are still challenges in data transfer due to the lack of standards in certain areas and lack of awareness and implementation of some standards. G-31 standards committee of SAE International has conducted a study on the available digital data standards in aircraft asset life cycle to understand the current and future landscapes of the needed digital data standards and identify gaps. This technical paper presents the study conducted by the G-31 technical committee.

Health Ready Components are essential to unlocking the potential of Integrated Vehicle Health Management (IVHM) as it relates to real-time diagnosis and prognosis in order to achieve lower maintenance costs, greater asset availability, reliability and safety. IVHM results in reduced maintenance costs by providing more accurate fault isolation and repair guidance. IVHM results in greater asset availability, reliability and safety by recommending preventative maintenance and by identifying anomalous behavior indicative of degraded functionality prior to detection of the fault by other detection mechanisms. The cost, complexity and effectiveness of the IVHM system design, deployment and support depend, to a great extent, on the degree to which components and subsystems provide the run-time data needed by IVHM and the design time semantic data to allow IVHM to interpret those messages.

The operating environment of aircraft causes accumulation and build-up of contamination on both the narrowest passages of the ECS (Environmental Control System) i.e: the heat exchangers. Accumulated contamination may lead to reduction of performance over time, and in some case to failures causing AOG (Aircraft on Ground), customer dissatisfaction and elevated repair costs. Airframers/airlines eschew fixed maintenance cleaning intervals because of the high cost of removing and cleaning these devices preferring instead to rely on on-condition maintenance. In addition, on-wing cleaning is t impractical because of installation constrains. Hence, it is desirable to have a contamination monitoring that could alert the maintenance crew in advance to prepare and minimize disruption when contamination levels exceed acceptable thresholds. Two methods are proposed to achieve this task, The effectiveness of these methods are demonstrated using analytical and computational tools.

Suppliers and integrators are working with SAE’s HM-1 standards team to develop a mechanism to allow “Health Ready Components” to be integrated into larger systems to enable broader IVHM functionality (reference SAE JA6268). This paper will discuss how the design data provided by the supplier of a component/subsystem can be integrated into a vehicle reference model with emphasis on how each aspect of the model is transmitted to minimize ambiguity. The intent is to enhance support for the analytics, diagnostics and prognostics for the embedded component. In addition, we describe functionality being delegated to other system components and that provided by the supplier via syndicated web services. As a specific example, the paper will describe the JA6268 data submittal for a typical automotive turbocharger and other engine air system components to clarify the data modeling and integration processes.

Many avionics and aircraft equipment manufacturers use DO-160 [Ref. 1] Section 22 to test their equipment for indirect effects of lightning without understanding why they are testing to specific values. Many aircraft manufacturers struggle with determining the level of indirect lightning that will be acceptable for their vehicle and what level of requirements they need to pass down to the avionics and aircraft equipment manufacturers. Organizations like SAE and RTCA, Inc. work to collect data on lightning and spend countless hours assimilating the information and developing documents to help engineers use the information. They struggle with knowing what data is pertinent and how it will be received and used by the engineering community.