ARINC REPORT – Page 6 OMS DESCRIPTION OMS Architecture The OMS should consist of the following equipment:?. Buy ARINC DESIGN GUIDANCE FOR ONBOARD MAINTENANCE SYSTEM from SAI Global. Avionics maintenance practices continue to improve through On-Board Maintenance System (OMS) recording. This standard defines the OMS.

Author: Gusida Kigakora
Country: Samoa
Language: English (Spanish)
Genre: Sex
Published (Last): 17 September 2017
Pages: 397
PDF File Size: 12.71 Mb
ePub File Size: 7.53 Mb
ISBN: 509-8-30651-144-9
Downloads: 81708
Price: Free* [*Free Regsitration Required]
Uploader: Grohn

Onboard Maintenance Systems for Modern Aviation

If there is not any fault history to be reported for the block requested by the CMC, the member system should transmit a null history message. To avoid delays and their associated costs, maintenance personnel must also be able to isolate the malfunctioning LRU quickly and confidently.

OMS message communications are classified into the following communication types: On ARINCthe data may be transmitted even in the case the system is not able to update the data contents. The length field should indicate the length in octets bytes of the data in the value field. August 30, ASN.

If the information is to be printed, retrieved, or downlinked, the following information should be added: Power transients should not cause false fault indications.

Onboard Maintenance Systems Design & Development – Performance

The specific requirements on ARINC buses are specified in attachment 2 section 1 and those on other buses, which are utilizing OSI services, are specified in attachments 2 section 2. This should be accomplished using the results of the normal continuous operational monitors which are part of the basic operational function of each member system LRU.

Type class and number identifies the type class and number per section 6. Identifier is a name identifying the message.

ARINC has more than 3, employees at over locations worldwide. If an existing fault is cleared, this also should be reported to the CMC immediately. No external fault or failure should cause false internal fault or failure indications.

This data should include information such as system status including redundancy status for fault tolerant systems and other specified parameter values.

Indeterminate – System cannot currently determine whether the fault exists. Components of the set are included in the definition of the named set. Specific design consideration should be given to system areas such as: It should be considered an engineering tool for collecting data to help understand hard to diagnose faults and identify possible design deficiencies. These reports should have xrinc following attributes under user-control: Thus the term fault isolation will be used in this document to cover isolation of both faults and the broader category of failures.


The printer should be capable of reproducing any text and graphics screens displayed aricn the operator. The CMC will also initiate automatic tests within the member system by means of test request 264 s to the member system. Flexibility should be maximized to allow current and future growth potential. A standard way of describing these protocols is also evolving, which should make future protocols less ambiguous.

The time interval from the initiation of engine shutdown e. Hardware and Software Configuration Identification 6224 operator may select specific tests, as provided for by the OMS menu and instruction displays.

Receive fault and failure data from other members. This means that it should arjnc possible to adapt a protocol developed for one bus to other buses with little or no change in the upper layers.

With the projected usage of multilevel functional redundancy to keep systems operational, degradation status reports are needed. The Event function may be initiated by a manual Event button activation or may be triggered by the OMS on the occurrence of a predetermined set of conditions.

The CMC should supply the following data for use by member systems: This document is intended to provide a better mutual understanding among the designers and users of the specified OMS including all its member systems, with a view toward achieving an optimum balance between critical factors such as BITE effectiveness, operator interface simplicity, cost, and system complexity.

The bits should be assigned, starting with the most significant bit MSB as follows: Articles needing additional references from March All articles needing additional references All articles with unsourced statements Articles with unsourced statements from January Articles needing additional references from February This specific report is intended for use in cases where one flight deck effect is to be correlated with multiple faults.


A MAT on the flight deck should provide a central station for maintenance activities, such as coordination with the flight crew or checks of displays and controls.

The need for special ground support equipment should be minimized. The member systems should transmit hardware and software configuration identification data to the CMC upon request. No supporting carry-on documentation, such as cue cards, operations notes, or other documents should be needed to use the OMS to access airplane systems BITE or maintenance documentation. The location of the MAT should support airline needs for quick turnaround and extended maintenance.

Failure indication or flight-deck effect, if any Failed function Failed LRU, part number and serial number, or interface A machine user e. Sufficient protection should be provided to preclude inadvertent alteration of this software. Some messages may use either of the other addresses.

Aircraft identification Flight number and city arrinc or route number Failures should aric identified as hard or intermittent.

Thus the OMS functional requirements are broken down into the following categories: Any reporting LRU should not be required to arijc to multiple users at the same time. The system should have the capability to collect data over specified periods of time referenced to a specific event. Nonetheless, designers zrinc avoid adding complexity for shop maintenance aricn good economic justifications. The CMC should transmit the specific test request to the specific member system. Request a specific member system to perform 6224 tests such as the replacement verification test, the system operational test, system functional test, alignment and rigging.

Specifications for system operation on an in-service airplane should allow for reasonable degradation due to continued use, and tolerance variation due to environmental differences in temperature, pressure, humidity, vibration, and similar factors. The Series describes the form, fit, and function of avionics equipment installed predominately on transport category aircraft.