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: Meztilkis Goltill
Country: Gambia
Language: English (Spanish)
Genre: Art
Published (Last): 26 October 2014
Pages: 333
PDF File Size: 12.70 Mb
ePub File Size: 16.93 Mb
ISBN: 180-7-77555-197-1
Downloads: 78069
Price: Free* [*Free Regsitration Required]
Uploader: Moogurr

The detailed provisions needed of the OMD are described in section 7. The type identifier has the following three elements: All fault and failure aginc recorded by the CMC should be tagged with the appropriate information.

On the other buses, member system LRUs should send a message indicating an unexpected message was received.

Onboard Maintenance Systems Design & Development – Performance

The Transport Layer is responsible for providing a reliable, transparent transfer of data between end points, and provides end-to-end error recovery and flow control. Changes in states of faults i. Thus the term fault isolation will be used in this document to cover isolation of both faults and the broader category of failures.

The full aribc of an ACMS are described in section 8. The type field should be the identifier field for the data unit.

Member systems LRU inputs and outputs should be covered by a wrap around test to the wrinc necessary to meet integrity requirements. Lynde Bradley Arthur A.

An abbreviated list follows. It should be considered an engineering tool for collecting data to help understand hard to diagnose faults and identify possible design deficiencies.

Where provided, the data in BITE memory should be easily accessible in order to read fault information. Type characteristic defines the characteristic per section 6. The second octet is an integer identifying the test continue option.


Onboard Maintenance Systems for Modern Aviation

Views Read Edit View history. An event could be a given point in the flight profile and be routine in nature, or be on an exception basis triggered by internal logic, crew-alert events, or the manual event button on the flight deck. This will have the effect of reducing time and logistics needs for airplane maintenance.

It further describes the capability to provide onboard maintenance documentation OMD and the requirement for total integration of these functions. The Data Link should be treated as an outside communications interface terminal such as a control and display terminal for the OMS.

Storage should be provided for a minimum of faults.

The member system activity report does not require acknowledgement. Specific attention should be focused on areas of equipment, such as engines, auxiliary power units, or environmental control system devices such as airconditioning packs.

Using this as a base technology, ARINC expanded its contributions to transport communications as arknc as continuing to support the commercial aviation industry and U. When this unique identification is received by the ELS, the ELS upon command should display or print the following information: The desire of some airlines to require flight crew arnc prior to release of maintenance or failure data for downlinking should be provided for by OMS. Additional BITE tests at power-up should be used in order to meet integrity requirements when continuous monitoring is not practical.

The time interval from the initiation of engine shutdown e. Procedures Formats for reports Procedural information Special instructions applicable to specific locations or conditions Any information the airline considers to be useful to have onboard the airplane 7.

Arnic permit electronics to be rapidly replaced without complex fasteners or test equipment. It establishes, manages, and terminates connections sessions between corresponding applications.

Through the MAT, the operator can view faults, either current or historical; initiate aircraft, system, or LRU specific tests; and view the results of any tests conducted. The tools should provide the following features: To provide ACMS including such functions as redundancy status, auto-exceedance monitoring, and performance monitoring.


ARINC – Wikipedia

Indeterminate – System cannot currently determine whether the fault exists. Next 4 octets are ISO 5 characters indicating departureAirport. Receive fault and failure data from other members.

Sort and consolidate fault and failure data. The OMS should also provide for receipt of uplinked data requests from the ground. Whatever the detailed definition of flight phases, they should be consistent throughout the whole airplane. Individual monitoring may be accomplished using self-monitoring by each LRU or by a central LRU monitoring less sophisticated peripheral equipment.

This specific report is intended for use in cases where one flight deck effect is to be correlated with multiple faults. To provide a cost-effective, user friendly means of airplane maintenance. Value True False Meaning erased not erased 6. This section needs additional citations for verification. Subordinate selections should permit operator selection of the airplane system, the category of ground test, and the specific test.

The OMS should display information in plain English and provide a simple, intuitive user input capability. Member systems should also transmit this message during execution of a test if the test must be terminated by the member system due to the occurrences of an inhibit condition.

Failure monitors should be designed with tolerance and time filters compatible with intended functions and the operating environment.