1.0 INTRODUCTION AND DESCRIPTION
1.1 Purpose of This Document
1.2 Document Organization
1.3 Definition of Terms Used in This Document
1.4 Related Documents
2.0 MAINTENANCE CONCEPT
2.1 Maintenance Definition
2.2 Objectives of an OMS
2.3 Regulatory Aspects
2.4 Availability Aspects
3.0 OMS DESCRIPTION
3.1 OMS Architecture
3.2 OMS Functional Requirements
3.3 OMS User Interface Requirements
3.4 Interfaces with Other Airplane Systems
4.0 CMS DESIGN CONSIDERATIONS
4.1 Fault and Failure Data Processing
4.2 CMS Storage Requirement
4.3 CMS Operational Monitoring
4.4 Reliability
4.5 CMC Interface with Member Systems
4.6 Software Loading
4.7 Failure Data Retrieval
5.0 OMS MEMBER SYSTEM BITE
5.1 General
5.2 BITE Non-Volatile Memory (NVM)
5.3 System BITE Communication with CMC
5.4 Use of BITE in Shop Maintenance
5.5 Detailed BITE Requirements
5.6 Interface Fault Detection/Classification
5.7 Power Interruption Reporting
6.0 OMS COMMUNICATIONS PROTOCOL
6.1 General Requirements
6.2 Protocol Architecture
6.3 Physical and Link Layer Protocols
6.4 Network Layer Protocol
6.5 Transport, Session, Presentation and
Application Layers
6.6 Application Program
7.0 ONBOARD MAINTENANCE DOCUMENTATION
7.1 Purpose of Onboard Maintenance Documentation
7.2 ELS Overview
7.3 OMS to ELS Functional Interface
7.4 OMD Data Content
7.5 OMS to ELS Human Interface
8.0 AIRPLANE CONDITION MONITORING SYSTEM
8.1 General
8.2 ACMS Functions
8.3 Onboard Programmability
8.4 Report Access
8.5 Ground Based Support Software
8.6 Consideration of ACMS Requirements in
Early Design
ATTACHMENTS
1 Onboard Maintenance System
2 Databus Specific Requirements for OMS
Communications Protocol
3 Glossary
APPENDICES
A Example - OMS Main Menu
B Example - Present Leg Failures Display
C Example - Failure History System Menu
D Example - Failure History System Display
E Example - Failure History Flight Leg Menu
F Example - Failure History Flight Leg Display
G Example - OMS Communications Protocol
Application Data
H Examples of OMS Messages on ARINC 629
I Examples of OMS Messages on Buses Other Than
ARINC 629
J1 State Transition Diagrams
J2 Fault Status Reporting Commands
J3 Initiated Test Commands