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.
|Published (Last):||24 August 2012|
|PDF File Size:||3.9 Mb|
|ePub File Size:||10.36 Mb|
|Price:||Free* [*Free Regsitration Required]|
Users have expressed a desire to provide a feature in applicable member systems to be able to trap arihc data on such events. The second and those following are visiblestring of text to be displayed. The system should be able to distinguish between different types of invalid data and provide that information as part of the report.
Airline data notes are both created and controlled by the airline. If the destination address is any of the airnc, the wordstring should be further processed in accordance with section 6. Ground tests should be enabled by selections via the OMS user interface. It describes the requirements for all the elements of the OMS, including a central maintenance computer or CMC function and all the member systems which interface with it.
Aircraft identification Flight number and city pair or route number Failures should be identified as hard or intermittent. The systems should be able to control user-access to selected displays based on access privileges.
The following user-initiated functions should be aarinc Report characteristics should include the following: The GBSS should perform data entry and syntax checking, generating error messages where appropriate. The ACMS should provide a method to mark the data which is invalid.
The user-defined application should be loadable by aric ACMS via data loader or data link. Upon receiving this aarinc, member systems should transmit Initiated test Inhibited Command Response. ARINC also developed the standards for the trays and boxes used to hold standard line-replaceable units like radios in aircraft.
Onboard Maintenance Systems Design & Development – Performance
This should be considered in the areas of degree of automation, design for ease of selection of required tests, minimization of required xrinc support equipment, and personnel safety provisions. Diagrams would not normally be used for ramp turnaround, but are useful for overnight maintenance when an airplane has to be removed from service and repaired in order to dispatch.
They should be tagged with the information that a power interruption has occurred. It also provides for more consistent screen formats from one system to another. Type number identifies arinnc assigned context-specific type number, c. The amount of data on the bus should be minimized.
A period of time could be a snapshot, or a duration of time with a begin and end point. No false indications of fault or failure should be produced when no fault or failure exists.
This is commonly used where the named set is used in multiple places. When an Srinc is performing one of the following operations, it shall consider any listed CMC request for any of the other listed operations as unexpected messages.
Onboard Maintenance Systems for Modern Aviation
The display format should be consistent with that for other OMS functions. BITE includes the fault detection and performance monitoring function of the operational system because these operational monitors are the primary source of fault data for the BITE maintenance function. The following user-initiated functions should be provided: 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.
Event function activation The CMC should receive coded data from all member systems. The CMC should provide an Event command as either a broadcast or an equipment specific signal on the digital bus.
Retrieved from ” https: It monitors and records selected airplane data related to airplane maintenance, performance, troubleshooting, and trend monitoring. Request a specific member system to perform ground tests such as the replacement verification test, the system operational test, system functional test, alignment and rigging.
Specific design consideration should be given to system areas such as: Others think of BITE as only the simple push to test function. Therefore, rainc addition to the actual maintenance function, the OMS should provide service reports on systems where sensors are airnc for normal operation, or where the addition of suitable sensors is economically feasible for this purpose.
Indeterminate – System cannot currently determine whether the fault exists. System is continuously monitoring the faultand can always determine, at least to some level of confidence, whether the fault exists. The member system will run the appropriate test or tests adinc will send operational status and test results data to the CMC display. Correlate fault and failure data with flight deck effects.
If GSE is used, this should not require any equipment removal. Too high a degree of complexity might result in a system which is not available for maintenance use during the introduction of a new fleet.
For certain airplane systems, it may be appropriate to divide or combine some of the above flight phases. This will be particularly applicable to fault tolerant systems in which a first failure does not affect flight operations immediately.
The LRUs not transmitting acknowledgment see attachment 2 section 1. It is responsible for establishing, maintaining, and termination network connections and routing and relaying transmissions.
Type class and number identifies the type class and number per section 6. If the information is to be printed, retrieved, or downlinked, the following information should be added: Open or grounded Signal fail, for other detected failures such as reasonableness or comparison monitors 5.
Sort and consolidate fault and failure data.
The member system can use this code to determine how to continue execution of the test.