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.
|Published (Last):||6 January 2009|
|PDF File Size:||18.69 Mb|
|ePub File Size:||5.37 Mb|
|Price:||Free* [*Free Regsitration Required]|
Each member system LRU should report when it has recovered from a power interruption.
When this unique identification is received by the ELS, the ELS upon command should display or print the following information: These algorithms could be sued to determine the occurrence of events which, in turn, could initiate further activity such as: As equipment becomes more reliable and the time between maintenance actions increases, there will be less need for maintenance personnel to check atinc performance arinf perform troubleshooting. The data to be passed from the aircraft to the ground should include failure data, failure history data, reports from the ACMS, and other appropriate aircraft maintenance status data.
Thus the OMS functional requirements are broken down into the following categories: Member systems having access to flight deck effect data as defined in section 4. Event Monitoring The ACMS should be able to monitor a selected set of aircraft data for use in Boolean logic and arithmetic calculations.
August 30, 8.
Onboard Maintenance Systems for Modern Aviation
The CMC arjnc provide the requests and data to the member system in order to accomplish the test or tests. Short Form for lengths between 0 and octets: Value Adinc False Meaning erased not erased 6. 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 will be the responsibility of the OMS designer to determine the criteria for the transition between flight legs.
Interactive Fault Location Tests? From Wikipedia, the free encyclopedia. A typical fault-tolerant arnc status page should display the actual health status of the system. Some of these attributes may be modifiable by the user.
A standard way of describing these protocols is also evolving, which should make future protocols less ambiguous. The systems should be able to control user-access to selected 6244 based on access privileges.
The data to be stored for each fault is defined in section 5. The time interval from reducing power to idle at a specified altitude e.
If any of transport, session, presentation and application layers are used, the protocol should be afinc accordance with ARINC Initiated Test Arihc bit should be set to 1 for 3 seconds after the test is completed. The flight phase logic may be computed in the CMC or alternatively retransmitted from an external source.
This information should include: See Appendix G for examples. The basic protocols should be as mature as possible and should be unambiguously described in order to ensure that system works right the first time.
An easy method to input alpha-numeric data should be provided. Input signals and user-defined parameters could be used in event monitoring, report generation, data recording and data display. A protocol developed for one type of bus e. Ground tests should be enabled by selections via the OMS user interface. Software Resets Watchdog timeout Processor traps e. Fault – Tolerant Design In airplane systems incorporating fault-tolerant designs, internal faults will not manifest themselves in a loss of functionality until the fault tolerance of the system is exhausted and failure occurs.
Stored Event data should be available from each member system when requested by the CMC.
A period of time could be a snapshot, or a duration of time with a begin and end point. The seven layers of the reference model are described below: The Series comprises a set of aviation standards for aircraft, including fiber optics used in high-speed data buses.
ARINC – Wikipedia
System is designed to transmit a flight leg header and two fault records per block. However, even the best and most carefully designed OMS cannot replace the need for well designed aircraft systems or appropriate aircraft maintenance.
This information should be derived from a common source, such as an onboard arind. Analog signal excluding discrete input faults should be detected, classified and reported as: The OMS designer should ensure that the proper aarinc troubleshooting procedures are automatically made available from applicable OMD data.
The same or similar test should be capable of being initiated by the CMC without the need for cycling circuit breakers. The member systems should transmit hardware and software configuration identification data to the CMC upon rainc.
OMS message communications are classified into the following communication types: Detailed troubleshooting procedures enabling isolation to a single LRU Required tools Access including: This should give the user the capability to specify the algorithms needed for event monitoring and to control other ACMS functions.