1、 AEROSPACE STANDARD Health and Usage Monitoring System Data Interchange Specification SAE Technical Standards Board Rules provide that: “This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is entirely voluntary, and its applicability and
2、 suitability for any particular use, including any patent infringement arising therefrom, is the sole responsibility of the user.” SAE reviews each technical report at least every five years at which time it may be reaffirmed, revised, or cancelled. SAE invites your written comments and suggestions.
3、 Copyright 2006 SAE International All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without the prior written permission of SAE. TO PLACE A DOCUM
4、ENT ORDER: Tel: 877-606-7323 (inside USA and Canada) Tel: 724-776-4970 (outside USA) Fax: 724-776-0790 Email: CustomerServicesae.org SAE WEB ADDRESS: http:/www.sae.org Issued 2006-06 AS5395 RATIONALE An open system architecture is a requirement for more affordable, capable vehicle Health and Usage M
5、onitoring System (HUMS). Open systems architecture will provide the operators with the capability to more rapidly field new health and usage monitoring technologies in the field. This document provides a standard definition for the health and usage data that is interchanged between on-board and off-
6、board system. The definition of standard HUMS data items would benefit developers, suppliers, integrators, and maintainers. Standard data items, which represent “fine-grained“ HUMS information, would be defined by functional characteristics such as Name, Description, Range, Resolution, and Units. Th
7、ese standard items could provide a foundation for the development and realization of data exchange within a HUMS Open System Architecture. FOREWORD At the first RITA HUMS Conference held in Philadelphia, PA in October of 1997, it was agreed that the definition of standard HUMS data items would benef
8、it developers, suppliers, integrators, and maintainers. Standard data items, which represent “fine-grained” HUMS information, would be defined by functional characteristics such as Name, Description, Range, Resolution, and Units. These standard items could provide a foundation for the development an
9、d realization of data exchange within a HUMS Open System Architecture. At present DIS is prioritized with PC-card implementation being first and RITA HUMS Advanced Multipoint Interface Specification (RHAMIS) being next. The Release 6.0 of DIS shall include RHAMIS implementation. DIS Release 5.1 addr
10、esses PC-card implementation. Note that there are RITA HUMS names listed in Section 3 of this document, which might not be used in PC-card implementation. However, it was agreed upon for Draft Release 2.0 to standardize HUMS parameter names and discrete names. Presently unused RITA names shall remai
11、n part of the Specification for use with the following RHAMIS implementation. There is a pending SAE number AS5395, for Data Interchange Specification SAE AS5395 - 2 - The major contributors to the contents of this DIS Release 5.1 are Smiths Industries, Goodrich Co., and the RITA principles (Bell He
12、licopter, Boeing and Sikorsky Aircraft) Robab Safa Boeing Military Aircraft and Missiles Vehicle Management Systems P.O. Box 16858, M/S P32-33 Philadelphia, PA 19142 voice: (610) 591-6154 fax: (610) 591-9008 email: robab.safa- RITA HUMS DIS MILESTONES This revision of DIS - Release 5.1 results from
13、meetings held between 1997 and 2002 between RITA principles and vendors. Below are milestones, which led to DIS Release 5.1 Version 1.0 released internal to RITA March 31,1997 Framework released to industry for comments September 15, 1997 Industry Conference in Philadelphia October 29-30, 1997 Draft
14、 Version 1.5 released to industry November 26, 1997 Draft Version 2.0 released to industry February 13, 1998 Industry conference in Philadelphia March 11-12, 1998 BF Goodrich DIS submittal May 19, 1999 Smiths Industries DIS submittal August 30, 1999 Industry conference in Philadelphia September 22-2
15、3, 1999 DIS meeting in Las Vegas January 25, 2000 DIS meeting in Virginia Beach May 1, 2000 Version 3.0 released internal to RITA May 2000 Draft Version 4.0 released for comments August 28, 2000 Industry conference at Sikorsky October 23-24, 2000 Letter of Commitment to Smiths Industries and BF Good
16、rich October 2000 DIS Meeting in Washington DC May 2001 DIS Meeting in Arlington, Texas February 2002 DIS Meeting in Montreal, Canada June 2002 SAE AS5395 - 3 - TABLE OF CONTENTS 1. SCOPE.7 1.1 Classification8 1.2 Intended Audience .8 1.3 Document Ownership.8 1.4 Relationship to Other RITA Documents
17、 .9 1.5 Document Organization .9 1.6 RITA Compliance.10 1.6.1 Airborne Unit Design Requirements.10 1.6.2 Airborne Unit Design Guidelines.10 1.6.3 RITA Open System Architecture 10 2. APPLICABLE DOCUMENTS .11 2.1 General 11 2.2 Government Document 12 2.2.1 Specifications, Standards, and Handbooks .12
18、2.2.2 Other Government Documents, Drawings, and Publications.12 2.3 Non-Government Publications .13 2.4 Order of Precedence14 3. FUNCTIONAL REQUIREMENTS 14 3.1 Overview 14 3.2 Data Interchange File.15 3.2.1 HUMS to External Systems15 3.2.2 HUMS Internal Systems.16 3.3 Transport Medium16 3.3.1 Electr
19、ical Characteristics16 3.3.2 Mechanical Characteristics 16 3.4 Information Representation17 3.4.1 RITA HUMS Operational Data Files.18 3.4.2 RITA HUMS Data Records 19 3.4.3 Data Structures 38 3.4.4 Data Items43 3.5 Error Checking Methods and Their Reliability75 3.6 Data Security76 4. IMPLEMENTATION .
20、76 4.1 EIA-485 76 4.2 PCMCIA PC-Card 76 4.2.1 Transport Medium76 4.2.2 Data Storage76 4.2.3 Logbook Usage Files .77 4.2.4 Rotor Track and Balance .86 4.2.5 Flight Data89 SAE AS5395 - 4 - 4.2.6 HUMS Data 89 4.2.7 Index File91 4.2.8 Initialization File92 APPENDIX A GLOSSARY93 APPENDIX B OBJECT MODEL R
21、EFERENCE 95 APPENDIX C CANDIDATE OPEN INTERFACE SYSTEM MODULES102 APPENDIX D AIRCRAFT COORDINATE SYSTEM.124 FIGURE 1 RITA HUMS Interfaces.8 FIGURE 2 RITA Open System Architecture 11 FIGURE 3 HUMS Data Interchange Model .15 FIGURE 4 HUMS to External System15 FIGURE 5 HUMS Components .16 FIGURE 6 RITA
22、 HUMS Information Representation .17 FIGURE 7 HUMS Component Model 46 FIGURE 8 Absolute Measurement of Rotor Lead/Lag.61 FIGURE 9 Absolute Rotor Track62 TABLE 1 Operational Data Files18 TABLE 2 RITA HUMS Data Record Names (RHUMSDSN) 20 TABLE 3 Exceedance Data Record 21 TABLE 4 Exceedance Parameters
23、21 TABLE 5 Vibration Alert Data Record22 TABLE 6 Vibration Alert Parameters .22 TABLE 7 HUMS Equipment Failure Data Record .23 TABLE 8 Rotor Start Data Record.23 TABLE 9 Rotor Stop Data Record .24 TABLE 10 Rotor Brake Start Data Record 24 TABLE 11 Rotor Brake Stop Data Record.25 TABLE 12 Take Off Ti
24、me Data Record .25 TABLE 13 Landing Time Data Record 26 TABLE 14 External Load Start Data Record .26 TABLE 15 External Load Stop Data Record27 TABLE 16 APU Start Data Record 27 TABLE 17 APU Stop Data Record 28 TABLE 18 Engine Start Data Record 28 TABLE 19 Engine Stop Data Record.29 TABLE 20 Single E
25、ngine Flight Start Data Record29 TABLE 21 Single Engine Flight Stop Data Record30 TABLE 22 HUMS Recording Session Data Record 30 TABLE 23 Version Data.30 TABLE 24 Proprietary Data Record.31 TABLE 25 Power Assurance Data Record 31 TABLE 26 Event Data Record 32 TABLE 27 Event Parameters.32 TABLE 28 RT
26、B Condition Indicator Records.33 TABLE 29 RTB Harmonic Indicator Data 33 TABLE 30 RTB Track Indicator Data.34 SAE AS5395 - 5 - TABLE 31 RTB Blade Indicator Data.34 TABLE 32 Fligiht Data Record.35 TABLE 33 Flight Data Parameters Value35 TABLE 34 HUMS Data Record36 TABLE 35 HUMS Data Parameters Value3
27、6 TABLE 36 Proprietary HUMS Data Record .36 TABLE 37 Index Record 37 TABLE 38 Initialization Record37 TABLE 39 HUMS Initialization Parameters .38 TABLE 40 RITA HUMS Standard Data Structures 39 TABLE 41 HUMS Equipment Failure Data Structure 39 TABLE 42 Power Assurance Parameter .40 TABLE 43 Polar Fre
28、quency Point Fields .40 TABLE 44 Rectangular Frequency Point Fields 40 TABLE 45 Polar Frequency Vector Fields .41 TABLE 46 Rectangular Frequency Vector Fields 41 TABLE 47 Polar Frequency Series Fields .41 TABLE 48 Rectangular Frequency Series Fields 42 TABLE 49 Absolute Time Point Fields.42 TABLE 50
29、 Relative Time Point Fields42 TABLE 51 Time Series Fields43 TABLE 52 VERTYPE Definition.44 TABLE 53 Data Storage Types .45 TABLE 54 Input/Output Signals.47 TABLE 55 UTC Data Type Fields63 TABLE 56 VERTYPE Definition.63 TABLE 57 Input/Output Signals - Discrete 64 TABLE 58 Discrete Status Words70 TABL
30、E 59 Configuration Parameters 71 TABLE 60 VERTYPE Definition.75 TABLE 61 Data Storage Types - PC Card Implementation.77 TABLE 62 Logbook File Record Labels.77 TABLE 63 Exceedance Data Record 78 TABLE 64 Vibration Alert Data Record79 TABLE 65 HUMS Equipment Failure Data Record .80 TABLE 66 Cumulative
31、 Usage Start Data.81 TABLE 67 Usage Start Record82 TABLE 68 Cumulative Usage Stop Data .83 TABLE 69 Usage Stop Record 83 TABLE 70 HUMS Recording Session Data Record 84 TABLE 71 Proprietary Data Record.84 TABLE 72 Power Assurance Record.85 TABLE 73 Event Data Record .86 TABLE 74 RTB Condition Indicat
32、or Record.87 TABLE 75 RTB Harmonic Indicator Data 87 TABLE 76 RTB Track Indicator Data.88 TABLE 77 RTB Blade Indicator Data.88 TABLE 78 Flight Data Record .89 TABLE 79 HUMS Data Record89 SAE AS5395 - 6 - TABLE 80 Proprietary HUMS Data Record .90 TABLE 81 Index File Record .91 TABLE 82 Initialization
33、 File92 SAE AS5395 - 7 - INTRODUCTION Health and Usage Monitoring Systems (HUMS) are becoming more important within the rotorcraft industry. These systems typically include data acquisition, analysis, and information processing to give an indication of the integrity of aircraft components and subsys
34、tems. Information gathered in flight is collected and stored for transfer to a ground station for analysis, report generation, and maintenance action indication. The addition of HUMS to rotorcraft can provide benefits such as increased safety, more efficient maintenance, increased rotorcraft lifetim
35、e, and reduced cost over the life of the rotorcraft. Although HUMS provide many positive advantages, existing systems are proprietary solutions (“closed” systems) lacking component interchangeability and interoperability. “Open” systems have been identified as a means to reduce cost and increase cap
36、abilities of rotorcraft HUMS by the United States government, rotorcraft manufacturers, and HUMS suppliers. As a result, the Rotorcraft Industry Technology Association (RITA) has proposed open system architecture as a solution to the problem. One aspect of the complete open system architecture is da
37、ta interchange. This document will provide the requirements for HUMS data interchange within open system architecture. It is not the intent of this document to specify a HUMS architecture which implements all requirements presented in this document. Instead, the intent is to provide a standard for d
38、esired HUMS components, which may be a part of any HUMS architecture. This will provide a consistent, common approach for integration of HUMS components into an architecture, which facilitates interchangeability and interoperability. One concern is the partitioning of functionality within HUMS. It i
39、s possible that one supplier may completely implement a function in the airborne system while another supplier may split the implementation between the airborne system and ground station. This document is designed to accommodate HUMS architectures regardless of the segmentation of functions within a
40、 given implementation. 1. SCOPE: This document establishes the Rotorcraft Industry Technology Association (RITA) Health and Usage Monitoring System Data Interchange Specification. The RITA HUMS Data Interchange Specification will provide information exchange within a rotorcraft HUMS and between a ro
41、torcraft HUMS and external entities. SAE AS5395 - 8 - 1.1 Classification: The RITA HUMS Data Interchange Specification will be used for exchange of information between the following entities. a. Between HUMS ground stations and external systems b. Between airborne HUMS processors and HUMS ground sta
42、tions c. Between airborne HUMS processors and external airborne systems The RITA HUMS interfaces covered by this document are shown in Figure 1 and are indicated by thick, bold arrows. ExternalSystemsEngineeringSupportMaintenanceSupportLogisticsSupportHUMS GroundStationHUMS ProcessorsHUMSSensors(Dig
43、ital)Legend:RITA HUMSDigital InterfaceExternal SystemsHUMS Sensors(Analog)HUMS ModuleHUMS ModuleFIGURE 1 - RITA HUMS Interfaces 1.2 Intended Audience: This document is intended for rotorcraft manufacturers, system integrators, system developers, operators, and HUMS suppliers. 1.3 Document Ownership:
44、 The Rotorcraft Industry Technology Association shall maintain this document. SAE AS5395 - 9 - 1.4 Relationship to Other RITA Documents: Five other documents are also part of the RITA HUMS specification suite. These documents are: a. RITA HUMS Accelerometer Interface Specification (AS5391 pending) b
45、. RITA HUMS Blade Tracker Interface Specification (AS5392 pending) c. RITA HUMS Rotational System Indexing Sensor Interface Specification (AS5393 pending) d. RITA HUMS Advanced Multipoint Interface Specification (AS5394) e. RITA HUMS Digital Sensors and Airborne HUMS Processors The Accelerometer and
46、 Rotational System Indexing Sensor specifications pertain to the Analog Sensor interface also shown in Figure 1, indicated by the thick, white arrows. The Advanced Multipoint and Blade Tracker specifications fall under the digital interface category. These specifications were agreed to by industry c
47、onsensus and are evolving as new sensors are developed to these specifications. 1.5 Document Organization: This document is divided into the following key sections: a. Introduction b. Applicable Documents c. Functional Requirements d. Implementation e. Appendices The functional requirements section
48、presents the general concepts required to achieve HUMS data interchange. A model that consists of a transport medium, a transport protocol, and data representation is introduced and used as the foundation for HUMS data interchange. The implementation section maps the functional requirements to speci
49、fic transport mediums, protocols, and data representations. SAE AS5395 - 10 - 1.5 (Continued): The object model appendix provides a method to organize or provide a structure to the process of listing individual HUMS parameters. The object model provided is a draft and represents one approach to defining a HUM system. One goal of this specification is to arrive at a HUMS industry consensus on the form of an object model for HUMS. The candidate open interface system module appendix provides definitions of objects within the model. It describes their func
