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):||23 October 2013|
|PDF File Size:||10.65 Mb|
|ePub File Size:||10.76 Mb|
|Price:||Free* [*Free Regsitration Required]|
This function should meet the following requirements: The CMC should begin to monitor immediately after its power-up self test and continue until it is shut down. An example is described in figure I-5 in Appendix H. Once the transmitter knows that the data has been received, the data does not have to be sent again. 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.
The detailed provisions needed of the OMD are described in section 7. ARINC signal output faults should be detected, classified and reported as: Specific design consideration should be given to system areas such as: This will have the effect of reducing time and logistics needs for airplane maintenance.
Numbers 0 through 30 coded in rightmost five bits: The CMC should also have access to the member systems LRU shop fault data for engineering use both on the flight deck as well as in the shop. Correlate fault and failure data with flight deck effects. Components of the set are included in the definition of the named set. The next most significant octet contains the second character of the string, and so on until the end of the string.
Onboard Maintenance Systems for Modern Aviation
Alignment and Rigging Tests? Sufficient protection should be provided to preclude inadvertent alteration of this software. Customization of user-defined specific functions user-defined application should not require recertification. The CMC should format and display this page when selected by a user.
Normally, this is met by the operational monitoring within the system. Subsequent numbered blocks should contain the next most recent fault record, etc.
If the destination address is any of the following, the wordstring should be further processed in accordance with section 6. They are intended to set forth the desires of the airlines pertaining to components or equipment is concerned and general design, construction and test criteria, in order to insure satisfactory operation and the necessary interchangeability in airline service.
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. The blocks of data will, in general, not be text screens as done on existing airplanes, but rather transmissions of values of specified parameters.
It is important that both flight crews and ground crews are able to identify improper operations of airplane systems according to established priorities and needs.
This will improve the effectiveness of airplane maintenance by reducing the number of spares needed and the number of dispatch delays and cancellations. Ground tests should be enabled by selections via the OMS user interface. Subordinate selections should permit operator selection of the airplane system, the category of ground test, and the specific test.
The Presentation Layer performs transformations on data to provide a standardized application interface and to provide common communications services The Application Layer provides services directly to the users of the OSI environment. Additional BITE tests at power-up should be used in order to meet integrity requirements when continuous monitoring is not practical. Last 4 octets are ISO 5 characters indicating destinationAirport.
Archived from the original on These reports should have the following attributes under user-control: The data displayed should include a failure history aric at least the last 64 flight legs or a total of failures, including the maintenance action taken if recorded. Messages cannot begin with a context-specific type.
Onboard Maintenance Systems Design & Development – Performance
A member system is any system which interfaces with the CMC – either directly or through a communications gateway. The following data identification are examples for consideration in OMD design.
A typical fault-tolerant system status page should display the actual health status of the system. 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 arimc simplicity, cost, and system complexity.
The first word following the label word should be the system status word. Faults should not be stored during this phase.
These functions are also designed to facilitate maintenance troubleshooting procedures arimc those systems where automatic means would not be cost effective. The OMS designer should ensure that the proper manual troubleshooting procedures are automatically made available from applicable OMD data. August 30, ASN.