# Presentation: 579912

## Use ofIntegrated Vehicle Health Managementin the Field of Commercial Aviation

***Gary Bird, Michael Christensen, Daniel Lutz, Philip A. Scandura, Jr.***
***Honeywell International, Phoenix, Arizona***
***First International Forum on***
***Integrated System Health Engineering and Management in Aerospace***
***November, 2005***
***Forum Topic Area: Applications to Commercial Aviation***
***Paper 12***

## Agenda

**Health Management Defined**
**Layered Approach to IVHM**
**Evolution of Commercial Aviation IVHM**
**History**
**Industry Standards**
**Generations**
**Next Generation Systems**
**Honeywell Primus Epic****®**** Aircraft Diagnostic and Maintenance System **
**Boeing 787 Crew Information System / Maintenance System**
**Intelligent Vehicles, Sense & Respond**
**Future Trends**

## Health Management Defined?

**Health Management Defined?**

**IVHM - Integrated Vehicle Health Management**

**ISHM - Integrated System Health Management**

**IHM - Integrated Health Management**

**SHM - Subsystem Health Management**

**HM - Health Management**

**BIT - Built-In Test**

**BITE - Built-In Test Equipment**

**FDIR - Fault Detection, Isolation & Recovery**

***Health Management Provides Users with an Integrated View of the Health State of the Overall “System”***

**VHM - Vehicle Health Management**

**On-Board Diagnostics (OBD) **

## Layered Approach to IVHM

**Vehicle Design and Assembly**

**Dispatch Preparation**

**Maintenance & Logistics**

**Mission Planning & Operations**

**Crew Alerting**

**Emergency Egress **

**Personnel Training**

## Evolution of Commercial Aviation IVHM

**Analog Systems (1950s, 60s, 70s) **
**Cockpit visual indications (e.g., warning lights, red lines on gauges, etc.)**
**“****Push-to-Test” or “Go/No-Go Test”**
**nothing more than a simple pushbutton that supplied current to the internal circuitry. If circuit continuity was detected, a green light would illuminate signifying a successful test. **
**Digital Systems (using hardware & software)**
**Early 1980s**
**Stand-alone LRUs using dedicated front panels with push-buttons and simple display capability (e.g., lights, alpha-numeric readouts)**
**Mid 1980s**
**Centralized display panels shared by several LRUs**
**Late 1980s / Early 90s**
**Centralized computers consuming heath and status data from several LRUs, performing simple fault consolidation and root-cause analysis**
**Later addition of trending and simple prognostics**

***Emergence of Standards***

- 1st Gen

- 2nd Gen

- 3rd Gen
- 4th Gen

## Industry Standards for Aircraft

**Aeronautical Radio, Inc. (ARINC) is a key standards provider for Commercial and Military Aircraft & Rotorcraft**
**VHM topics are within the scope of the Avionics Maintenance Conference (AMC) an air transport industry activity sponsored by ARINC**
**AMC objectives are to promote reliability and reduced operating cost in air transport avionics by improving maintenance and support techniques through the exchange of technical information**
**Well known and recognized standards include**
**ARINC Report 604-1: Guidance for Design and Use of Built-In Test Equipment (BITE); October 1988**
**ARINC Specification 624-1: Design Guidance for Onboard Maintenance System; August 1993**
**ARINC Report 644: Portable Maintenance Access Terminal (PMAT); May 1993**
**References**
**www.arinc.com/amc**

## Guidance for Design and Use of Built-In Test Equipment (BITE)
Purpose/Scope
The primary purpose of BITE is to assist maintenance personnel in the proper maintenance of avionics systems in a cost-effective manner. A description of a Centralized Fault Display System (CFDS) is included in this standard. The CFDS accumulates fault data, presents this data to a maintenance operator, and assists troubleshooting by performing diagnostic tests and performing verification testing after installation of a replacement unit.
Major Sections
Goals for BITE
Maintenance Concept
BITE System Concepts
Centralized Fault Display System Concept
Display Formats, Interfaces, Protocols, etc.
Version History
First release, ARINC 604 published 1985
Only supported character-based, block transmission protocol
Current release, ARINC 604-1 published 1988
Added bit-oriented, broadcast protocol

**Purpose/Scope**
**The primary purpose of BITE is to assist maintenance personnel in the proper maintenance of avionics systems in a cost-effective manner. A description of a Centralized Fault Display System (CFDS) is included in this standard. The CFDS accumulates fault data, presents this data to a maintenance operator, and assists troubleshooting by performing diagnostic tests and performing verification testing after installation of a replacement unit.**
**Major Sections**
**Goals for BITE**
**Maintenance Concept**
**BITE System Concepts**
**Centralized Fault Display System Concept**
**Display Formats, Interfaces, Protocols, etc.**
**Version History**
**First release, ARINC 604 published 1985**
**Only supported character-based, block transmission protocol**
**Current release, ARINC 604-1 published 1988**
**Added bit-oriented, broadcast protocol**

**Industry Standards - ARINC 604-1**

## Industry Standards - ARINC 604-1

**Aircraft equipped with maintenance systems based on ARINC 604-1**
**Boeing 757, 767**
**MCDP, Maintenance Control Display Panel - Rockwell Collins**
**MD-11, Boeing 717**
**CFDIU, Central Fault Display Interface Unit - Honeywell**
**Boeing 747-400**
**CMC, Central Maintenance Computer - Rockwell Collins**

## Design Guidance for Onboard Maintenance System
Purpose/Scope
Enables continued improvement of avionics maintenance practices through On-Board Maintenance System (OMS) recording. This standard defines the OMS, which incorporates fault monitoring, fault detection, BITE and airplane condition monitoring.
Major Sections
Maintenance Concept
OMS Description
CMC Design Considerations
OMS Member System BITE
OMS Communications Protocol
Onboard Maintenance Documentation
Airplane Condition Monitoring Function (ACMF)
Version History
First release, ARINC 624 published 1991
Only supported ARINC-429 databus
Current release, ARINC 624-1 published 1993
Added support for additional databuses (e.g., ARINC-629)
Incorporated lessons learned from previous ACMF implementations

**Purpose/Scope**
**Enables continued improvement of avionics maintenance practices through On-Board Maintenance System (OMS) recording. This standard defines the OMS, which incorporates fault monitoring, fault detection, BITE and airplane condition monitoring.**
**Major Sections**
**Maintenance Concept**
**OMS Description**
**CMC Design Considerations**
**OMS Member System BITE**
**OMS Communications Protocol**
**Onboard Maintenance Documentation**
**Airplane Condition Monitoring Function (ACMF)**
**Version History**
**First release, ARINC 624 published 1991**
**Only supported ARINC-429 databus**
**Current release, ARINC 624-1 published 1993**
**Added support for additional databuses (e.g., ARINC-629)**
**Incorporated lessons learned from previous ACMF implementations**

**Industry Standards - ARINC 624-1**

## Industry Standards - ARINC 624-1

**Aircraft equipped with maintenance systems based on ARINC 624-1**
**Boeing 777**
**CMF, Central Maintenance Function - Honeywell**
**Integrated into Aircraft Information Management System (AIMS)**
**Business Jets, Regional Jets, Rotorcraft**
**ADMS, Aircraft Diagnostic and Maintenance System - Honeywell**
**Integrated into Primus Epic****®**** ****system**
**Simplified variant of ARINC-604 & 624**
***(bit-oriented protocol with centralized OMS)***

## VHM Evolution for Commercial Aircraft

- Next Gen?

## Honeywell Primus EpicAircraft Diagnostic and Maintenance System

**Aircraft**
**Business Jets (Raytheon Hawker Horizon, Dassault F900EX/F2000EX/Falcon 7X, Gulfstream G450/G550, Cessna Sovereign)**
**Helicopters (Agusta AB-139)**
**Regional Jets (Embraer ERJ-170/190)**
**Aircraft Diagnostic and Maintenance System (ADMS)**
**Central Maintenance Function**
**Aircraft Condition Monitoring Function**
**Member Systems’ BIT **

**Features**
**Includes coverage of Honeywell and Third-Party systems**
**Provides Single Point Access to all systems  via “Point & Click” GUI**
**Performs Root Cause Diagnostics to Eliminate Cascaded Faults**
**Performs Correlation between Flight Deck Effects and System Faults**
**Configurable Via Database**
**Supports Printer, Data Link, & Floppy/CD-ROM**

## Boeing 787Crew Information System / Maintenance System

**Features**
**Leverages technologies from Boeing 777 CMC and Primus Epic ADMS**
**Performs onboard, real-time data collection, fault processing and display**
**Performs root cause diagnostics to eliminate cascaded faults**
**Performs correlation between Flight Deck Effects and system faults**
**E-enabled network to ground Maintenance Operations for extended diagnostic/prognostic analysis**
**Includes coverage of Honeywell and third-party systems**
**Provides single point access to all systems**

## Intelligent Vehicles, Sense & Respond

**Vehicles**
**Aircraft (Honeywell, General Electric, Pratt & Whitney)**
**Automotive (General Motors’ OnStar****®****)**
**Features**
**Performs onboard, real-time data collection, fault processing**
**Raw/Processed data transmitted to central data repository**
**Data utilized by Engineering and Business processes (e.g., warranty, reliability, product improvement, logistics)**
**Data made available to Customers to support their operations (e.g., fleet maintenance, fleet utilization planning)**

## Future Trends

**Advances in Commercial Aviation are focused on delivering value to the customer**
**Life-cycle cost reduction**
**Condition-based maintenance**
**Fleet services**
**IVHM systems are taking advantage of commercial technologies**
**Wireless communications**
**Web-enabled**
**Aircraft becoming a “node” on the network**
***Commercial usage of IVHM is typically in support of maintenance***
**NASA needs are of higher criticality - IVHM in support of **
**Vehicle automation**
**Vehicle reconfigurablity**
**Mission planning and execution**
***More R&D is needed to adapt commercial IVHM technologies to the applications of human spaceflight - NASA must drive this R&D***