SAE AS 4831A-2003 Software Interfaces for Ground-Based Monitoring Systems《地基监控系统用的软件接口》.pdf

《SAE AS 4831A-2003 Software Interfaces for Ground-Based Monitoring Systems《地基监控系统用的软件接口》.pdf》由会员分享，可在线阅读，更多相关《SAE AS 4831A-2003 Software Interfaces for Ground-Based Monitoring Systems《地基监控系统用的软件接口》.pdf（22页珍藏版）》请在麦多课文档分享上搜索。

1、AEROSPACE STANDARDAS4831REV.AIssued 2001-09Revised 2003-02Superseding AS4831Software Interfaces for Ground-Based Monitoring SystemsFOREWORDThis SAE document seeks to improve the situation whereby current ground-based engine monitoring systems (EMS) cannot readily be integrated into one computing env

2、ironment.Following a consensus by the SAE E-32 Committee on the need for some form of standardization in these systems, ARD50002 was written. It reviewed the situation, laid out several methods of standardization which addressed the problems to varying degrees, and was the vehicle for canvassing the

3、 industry for user views.The result was a clear mandate for standardization and a decision on the degree to which this process should be taken. The consensus was that it is the interfaces between the major functional elements in the EMS which should be standardized, so that elements from different m

4、anufacturers can work together.This document describes the first steps into this standardization.Reaffirmed 2009-10SAE 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 volunta

5、ry, and its applicability and 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 writ

6、ten comments and suggestions. Copyright 2009 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 permis

7、sion of SAE. TO PLACE A DOCUMENT 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 SAE values your input. To provide feedbackon this Technical Report, please visit http:/www.sae.org/tech

8、nical/standards/AS4831ASAE AS4831 Revision A- 2 -TABLE OF CONTENTS1. SCOPE .42. REFERENCES .42.1 Applicable Documents 42.1.1 SAE Publications 42.2 Glossary42.2.1 Acronyms 42.2.2 Definitions .53. ECM SYSTEM OVERVIEW73.1 Introduction .73.2 Input Interface .73.3 Output Interface 73.4 End-User Tools .93

9、.5 OEM Host System 93.5.1 Input Interface .93.5.2 OEM ECM Host System .93.5.3 OEM Output Reports 103.5.4 Output Interface 104. INPUT INTERFACE SPECIFICATIONS .104.1 Introduction .104.2 The Input Interface114.3 The Input Interface Structure 124.3.1 General Input File Format Requirements134.3.2 Delimi

10、ter Section.134.3.3 Format Section134.3.4 Values Section 144.4 The Input Interface Keys.154.5 Requirements of the OEM Host System for the Input Interface155. OUTPUT INTERFACE SPECIFICATIONS .155.1 Introduction .155.2 Requirements and Structure of the OEM Host System for the Output Interface.165.3 Th

11、e Output Interface Keys 176. EXAMPLE FILES186.1 Input Files .186.1.1 Example of Flight Data Input - One Data Set186.1.2 Example of flight Data Input - Multiple Data Set .19SAE AS4831 Revision A- 3 -TABLE OF CONTENTS (Continued)6.1.3 Example of APU Data Input 206.1.4 Example of a Maintenance Action C

12、ode Input206.1.5 Example of Engine Installation and Removal216.2 Output Files.216.2.1 Example of Flight Data Output216.2.2 Example of Alert Output22SAE AS4831 Revision A- 4 -1. SCOPE:To establish a specification for software input and output interfaces for condition monitoring and performance progra

13、ms used to monitor equipment from multiple manufacturers.The purpose of standardizing these interfaces is to improve operational flexibility and efficiency of monitoring systems as an aid to cost effectiveness (e.g., easier implementation).2. REFERENCES:2.1 Applicable Documents:The following publica

14、tions form a part of this document to the extent specified herein. The latest issue of SAE publications shall apply. The applicable issue of other publications shall be the issue in effect on the date of the purchase order. In the event of conflict between the text of this document and references ci

15、ted herein, the text of this document takes precedence. Nothing in this document, however, supersedes applicable laws and regulations unless a specific exemption has been obtained.2.1.1 SAE Publications: Available from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001.AIR1873 Guide to Limited E

16、ngine Monitoring Systems for Aircraft Gas Turbine EnginesAIR4175 A Guide for the Development of Ground Station for Condition MonitoringARD50002 A Discussion of Standardization Concepts for Condition Monitoring and Performance Analysis Software2.2 Glossary:2.2.1 Acronyms:ACARS: Aircraft Communication

17、s, Addressing, and Reporting SystemACMS: Aircraft Condition Monitoring SystemADAS: Aircraft Data Acquisition SystemAIMS: Aircraft Information Management System/Aircraft Integrated Monitoring SystemAPU: Auxiliary Power UnitASCII: American Standard Code for Information InterchangeCM: Condition Monitor

18、ingDBMS: Database Management SystemDMU: Data Management UnitECM: Engine Condition MonitoringECS: Environmental Control SystemEMS: Engine Monitoring SystemGUI: Graphical User InterfaceOEM: Original Equipment ManufacturerSQL: Structured Query LanguageSAE AS4831 Revision A- 5 -2.2.2 Definitions:ACCESS

19、METHODS: Methods of accessing data stored in a computer, e.g., indexed, keyed, random, relational or sequential.ALERT: A warning or notification issued based on the analysis of the data, indicating a possible negative change within an engine.ANNOTATION DATA: Narrative text annotating operational exp

20、erience derived from the pilot, maintenance technicians, or engine performance analysts.BASELINE: A set of data defining standard basic operating conditions and performance for a nominal/new engine.BINARY DATA: Variable length strings of binary information, which can represent bit map graphics, comp

21、uter object code, compressed textual data, or digitally recorded data.CHARACTER: A single unit of display or textual data stream (e.g., one letter or one number).COMPRESSION: Mathematical reduction of any volume of digital data (e.g., in a historical plot or time-series data stream).CONFIGURATION DA

22、TA: Data describing where and when engines and modules are installed and removed. The data can be accompanied by hours and cycles information.CONTINUOUSLY RECORDED DATA: Typically, data recorded during exceedance conditions, for a brief duration in real time, encompassing several seconds of multiple

23、 channel engine and/or airframe sensor readings, or data recorded as the operation is in progress, for a length of time dictated by the configuration of the recording system.DATA TYPE: Specific characteristics about representation/storing of data in the computer environment. Following types are cove

24、red: binary, character, field free text, integer, and real number.DERIVED RESULTS OR QUANTITIES: Results from simulation or performance analysis of engine operational measurements which depict the health status or trends in operational performance.EXCEEDANCE: (A flag which indicates that) the value

25、of a parameter has gone above a high or below a low predefined threshold-value for a predefined minimum duration.FILE: A collection of data stored in computer-compatible form, with a name assigned.HOST (OEM Host SYSTEM): It is the core of the ECM software which provides non-analytical and optional f

26、unctions.SAE AS4831 Revision A- 6 -2.2.2 (Continued):INPUT DATA: Presentation of acquired data to the condition monitoring and performance program. Types of input data includes but not limited to: annotation data, configuration data, manual records, snapshot.INTEGER: A representation of a positive o

27、r negative whole number.INTERFACE: The link between two software programs or modules.MAIDEN POINT: The value of a set of parameters in a historical plot, based on data acquired immediately following the installation of the engine (same as initial point).MANUAL RECORDS: Data which are not recorded au

28、tomatically.OUTPUT DATA: Presentation to the user of a coherent set of textual data (measured and/or calculated).PARAMETER: Data from one single signal source.PLOT: A two dimensional graph of two or more parameters.REAL NUMBER: A representation of a fractional number to some degree of precision and

29、some exponential range. The range of real number representation must be sufficient to represent all data elements stored in the database.RECORD: A group of related data in a defined format.REPORT: OEM direct program results (Plots, Barcharts, Alerts)SMOOTHED DATA: Output data where scatter is reduce

30、d by a mathematical process.SNAPSHOT: A set of data recorded, from a specific time, or as a result of a specific predetermined condition or event in the operation of an aircraft or an engine.TABLE: A list of alphanumeric characters which is related either in columns or rows.TREND: A movement in a pl

31、ot or value of one parameter plotted against time.SAE AS4831 Revision A- 7 -3. ECM SYSTEM OVERVIEW:3.1 Introduction:Figure 1 shows the different components and interfaces of an ECM System. The components are: Input contains the user generated input data to be supplied to an ECM Host System. Standard

32、ization is required. Input Interface defines a single generic format enabling data entry to any OEM Host System. Standardization is required. The OEM Host System containing the CM program and the OEM database, provides and performs all calculations as defined by the OEM. Output Interface defines a s

33、ingle generic format enabling for data transfer out of any OEM Host System. Standardization is required. Output contains the OEM Host System generated data which is supplied to the user, where - each OEM host system provides a standard reporting package in the typically available formats(Alerts, Plo

34、ts, Bar Charts, etc.).- the OEM host system outputs data for customizable use by the airline. This additional output for customized use needs to be standardized. End-User Tools are developed and/or provided by the user to access the data stored in the user storage media which might retain and manage

35、 condition monitoring data from multiple manufacturers and perform any subsequent calculations or modifications to the data.3.2 Input Interface:The standardization of the input interface and format establishes the minimum input required by the OEM Host System while providing the user with the flexib

36、ility to input additional data for their own specific needs (including manual data entry, ground-based data selection, ACARS, etc.). The specifications for the Standard Input Format are described in this document, Section 4.3.3 Output Interface:The OEM Host System must supply an Output interface cap

37、able of generating files for all output data that results from processing either new input data or from reprocessing previously stored data. This Output interface must also provide assess to all input parameters and key values. The specifications for the Standard Output Format of these files can be

38、found in Section 5 of this document.SAE AS4831 Revision A- 8 -FIGURE 1SAE AS4831 Revision A- 9 -3.4 End-User Tools:The End-User Tools are those software packages which access the User Storage Media to display, calculate, or manage the stored data. The User Storage Media is the data management system

39、 that the user chooses to store and manage their condition monitoring data. This media can be commercially available software or user developed software. The maintenance and support of the User Storage Media is the responsibility of the user.Examples of these tools are: Oracle Reports, Excel or user

40、 developed tools.OEM Host system(s) can also be used for this functionality.3.5 OEM Host System:An OEM Host System provides the functionality to read and store input data, executes the OEM analytical calculations, and provides results for output.3.5.1 Input Interface: The Input Interface provides th

41、e OEM Host System with the capability to read user generated files and store them into the Host System database. The OEM Host System must supply an Input Interface capable of reading the Standard Input Format as specified in chapter 4 of this document. The Input Interface may also support reading ot

42、her formats such as OEM legacy input formats.3.5.2 OEM ECM Host System: The OEM Host System is the core of the ECM Software system which usually provides the following: non-analytical functions, e.g.:a. integration with the analytical functionsb. data management of all input and outputc. user interf

43、ace (GUI or non-GUI interface)d. reports (definition and generation)e. multiple user accessf. security key analytical functions, e.g.:a. data normalizationb. trend recognitionc. smoothingd. alertse. compressionf. maideningSAE AS4831 Revision A- 10 -3.5.3 OEM Output Reports: The output reports usuall

44、y provides a set of default reports based on the OEM standards and supports flexible functionality to provide user-definable formats and presentations of any data available in the OEM database for the following output media and output types:Output Media: printer screenfile E-MailOutput Types: semi-g

45、raphical plot table alert/notifiergraph delimited data3.5.4 Output Interface: The OEM Host System must supply an Output Interface capable of generating files in the Standard Output Format as specified in Section 5 of this document. The user is responsible for the tools to utilize this data in suppor

46、t of user specific requirements.4. INPUT INTERFACE SPECIFICATIONS:4.1 Introduction:This section includes a more detailed specification of the standard for the interfaces into any OEM Host System. The Input Interface must provide the functionalities described in this document. This standard may be re

47、vised due to future technology development.SAE AS4831 Revision A- 11 -4.2 The Input Interface:The Input Interface must provide the functionality to enter all data required by any of the OEM Host Systems and any data needed by the user. The user is responsible for segregating the input data and trans

48、ferring it to the appropriate host system. Examples of data to be entered are:a. Data from the operating aircraft (aircraft/engine records)1. engine start records2. takeoff records3. exceedance records4. stable cruise records5. APU reports6. ECS reports7. Annunciated faultsb. Test cell data1. Produc

49、tion test cell results, new engines2. Test Cell results before/after overhaulc. Data from previous processed points1. calculated deltas2. other derived data necessary for the processd. Configuration data1. engine installation/removal2. module installation/removal3. new/modified engine configuration definition4. new/modified aircraft configuration definition5. hours/cycle informatione. Annotation data (comments to events in the history of the engine)1. component changes (e.g., control units, temperature probes)2. comments to, f