ARINC 624 PDF
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: | Vudomi Moogusar |
| Country: | Papua New Guinea |
| Language: | English (Spanish) |
| Genre: | Literature |
| Published (Last): | 27 January 2017 |
| Pages: | 490 |
| PDF File Size: | 9.37 Mb |
| ePub File Size: | 16.89 Mb |
| ISBN: | 464-8-33825-295-7 |
| Downloads: | 23159 |
| Price: | Free* [*Free Regsitration Required] |
| Uploader: | Vulrajas |
Sort and consolidate fault and failure data. The full provisions of an ACMS are described in section 8.
ARINC – Wikipedia
Ground support equipment GSE may be used as required to accomplish the system test, although the goal should still be to minimize the use of such GSE. The CMC will also initiate automatic tests within the member system by means of test request message s to the member system.
The data displayed should include a failure history of at least the last 64 flight legs or a total of failures, including the maintenance action taken if recorded. Ports may be provided at service interphone panels whose locations are already in place.
These screens should allow a user to display data in text or graphic format, present menus, display reports, and perform selected ACMS functions e. This should be used for reporting multiple faults when no additional information is to be attached, as it minimizes bus loading.
The time interval from end of Initial Climb until leveling off at the persecuted flight level, or from leaving a flight level until leveling off at a higher flight level.
It is responsible for establishing, maintaining, and termination network connections and routing and relaying transmissions. The OMS should also provide for receipt of uplinked data requests from the ground.
Fault 6244 is the built-in capability of a system or LRU to continue to perform its required functions with a specified number of faults. Specific design consideration should be given to system areas such as: When the CMC receives the power interrupt status, it should clear any interface faults associated with that LRU which may have been stored as a result of the power interruption.
Onboard Maintenance Systems Design & Development – Performance
LRU or system tests following LRU replacement should be sufficient to declare the airplane system serviceable. If there is no response received from the LRU, fault should be reported. The data to be stored for each fault is defined in section 5.
The seven layers of the reference model are described below: Fault detection should be accomplished by continuous operational monitors to the greatest extent possible. Flight phase and UTC when fault occurred Fault isolation to an SRU level, if practical shop data Additional parameters which may be useful for troubleshooting e.
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. Aircraft identification Flight number and city pair or route number Failures should be identified as hard or intermittent.
Access to OMD should be provided in a categorical manner, similar to access for in-flight failure history and ground test. Access to OMD should be provided in a categorical manner, similar to access for in-flight failure history and ground test. The aarinc should be expressed in universal time coordinated UTC in hours, minutes and seconds.
The CMC should format and display this page when selected by a user. Specific ground tests, such as LRU replacement verification tests, operational tests, system functional tests, or alignment and rigging. An example aginc described in figure I-5 in Appendix H.
The discussions in this attachment are made for the case dual CMC configuration is applied. Components of the sequence are included in the definition of the named sequence. The GBSS should allow the user to establish some level of security with each screen.
The primary use of supporting documentation may be for engineering, supply, operations, or other organization. The following user-initiated functions 6624 be provided: The LRUs not transmitting acknowledgment see attachment 2 section 64. To provide ACMS including such functions as redundancy status, auto-exceedance monitoring, and performance monitoring.
Onboard Maintenance Systems for Modern Aviation
August 30, 8. The CMC will provide the requests and data to the member system in order to accomplish the test or tests.
No false indications of fault or failure should be produced when no fault or failure exists. In this case, the block should begin with the fault record for the next fault in the previous flight leg.
Using this as a base technology, ARINC expanded its contributions to transport communications as well as continuing to support the commercial aviation industry and U. Ports may be provided at service interphone panels whose locations are already in place.
ARINC also developed the standards for the trays and boxes used to hold standard line-replaceable units xrinc radios in aircraft. Ports should be provided for optional remote or portable MATs to facilitate maintenance at other locations.
When an LRU is performing one of the following operations, it shall consider any listed CMC request for any of the other listed operations as unexpected messages. Some messages may use either of arinx other addresses.