This content is not included in your SAE MOBILUS subscription, or you are not logged in.
Contiguous Aircraft/System Development Process Example
- Aerospace Standard
Published February 05, 2020 by SAE International in United States
Downloadable datasets availableAnnotation ability available
This AIR provides a detailed example of the aircraft and systems development for a function of a hypothetical S18 aircraft. In order to present a clear picture, an aircraft function was broken down into a single system. A function was chosen which had sufficient complexity to allow use of all the methodologies, yet was simple enough to present a clear picture of the flow through the process. This function/system was analyzed using the methods and tools described in ARP4754A/ED-79A. The aircraft level function is “Decelerate Aircraft On Ground” and the system is the braking system. The interaction of the braking system functions with the aircraft are identified with the relative importance based on implied aircraft interactions and system availabilities at the aircraft level. This example does not include validation and verification of the aircraft level hazards and interactions with the braking system. However, the principles used at the braking system level can be applied at the higher aircraft level. The methodologies applied here are an example of one way to utilize the principles defined in ARP4754A/ED-79A. The function chosen was the braking system. Other formats may be used to accomplish the documentation, so long as the principles outlined in ARP4754A/ED-79A are followed.
This example contains references to documentation that a company may use to assure itself of the safety of its products but does not include the documentation that the Original Equipment Manufacturer (OEM) would be required to submit at the aircraft level for aircraft certification. Some of these documents are submitted to the regulatory agencies for the purpose of certification (e.g. the Wheel Brake System FHA). Other documents are internal to the company and not required to be submitted for certification. No implication is made that these documents should be submitted to a regulatory agency and none should be implied, although all documents should be available for submission if requested by the regulatory agency. Safety and Certification are not synonymous terms. The example shows the systems engineering process as applied to the development of an aircraft, including some processes that are beyond certification requirements.
Figure 1 depicts the flow of activities within this example. This figure provides a guide to the structure of this AIR and should allow the reader to quickly find specific areas within the example using the cross references.
Figure 1 includes the top aircraft level tasks to provide the reader a reference point. The detailed example in Section 3 of this AIR covers only the activities related to the braking system. Figure 1 presents a sequence of activities found in a typical development program. In a real development program, the development process is usually far more complex. For example, in a real development program, development of the different levels (aircraft, system and item) often occurs concurrently, rather than serially as depicted in example flow.
The top row of Figure 1 represents the activities that will occur within the aircraft development. The middle row represents the activities that occur within the wheel brake system development. The bottom row represents the activities that are covered for the subsystem-level Brake System Control Unit (BSCU) development, as well as the integration and verification activities at the higher levels.
The Figure 1 example flow also shows where major artifacts from the System Safety Process (ARP4761) will be utilized. The example flow shows how the sections and artifacts are laid out and represents the step by step process detailed in ARP4754A/ED-79A. In a real development program, the System Safety Process occurs concurrently with ARP4754A/ED-79A, constantly receiving inputs from the ARP4754A/ED-79A process and providing feedback to ARP4754A/ED-79A processes.
Figure 1 also shows a box titled Integral Processes to illustrate to the reader that the integral processes are utilized throughout the development process. The reader is encouraged to use this example flow diagram to help navigate the example. This will allow the reader to either read the example in its entirety or use it as a quick reference guide in order to quickly find the desired section.
This document provides additional supporting material for the implementation of the processes described in ARP4754A/ED-79A.
Data Sets - Support Documents
|Unnamed Dataset 1|
|Unnamed Dataset 2|
|TABLE 9-1||AIRCRAFT DEVELOPMENT DELIVERABLES|
|Unnamed Dataset 4|
S-18 Aircraft and Sys Dev and Safety Assessment Committee
The SAE S-18 Committee is active in the development of guidelines, including processes, methods and tools, to accomplish safety assessment of airplanes and related systems and equipment.
* Redlines comparisons are available for those standards listed in the Revision History that contain a radio button. A redline comparison of the current version against a revision is accomplished by selecting the radio button next to the standard and then selecting 'compare'. At this time, Redline versions only exist for some AMS standards. SAE will continue to add redline versioning with ongoing updates to SAE MOBILUS.