This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| ARP4754A | |
|---|---|
| Title | ARP4754A |
| Status | Active |
| Organization | Society of Automotive Engineers |
| Year | 2010 |
| Domain | Aerospace systems engineering |
ARP4754A
ARP4754A is an aerospace systems development guideline published as an aerospace recommended practice that addresses system-level development processes for civil and military Boeing and Airbus platform programs and suppliers such as Collins Aerospace, Honeywell Aerospace, and Thales Group. It provides a framework used by certification authorities like the Federal Aviation Administration and the European Union Aviation Safety Agency alongside industry bodies such as the Radio Technical Commission for Aeronautics and the International Civil Aviation Organization. The document aligns with safety evidence expectations from National Transportation Safety Board investigations and program management practices employed by integrators like Lockheed Martin and Northrop Grumman.
ARP4754A defines a lifecycle for systems development that complements guidance from RTCA, Inc. publications and harmonizes with engineering processes used by contractors on programs such as the F-35 Lightning II and the Airbus A320neo. The standard emphasizes traceability of system requirements, architecture, verification, and validation activities applied across product lines at companies including Safran and General Electric Aviation. ARP4754A is frequently referenced in compliance matrices prepared for authorities including the Civil Aviation Authority (United Kingdom) and the Transportation Safety Board of Canada.
The evolution leading to ARP4754A traces to earlier community efforts and documents produced by groups such as SAE International and RTCA; successors reflect lessons from incidents investigated by the National Transportation Safety Board and program reviews of platforms like the Boeing 737 MAX and the Airbus A380. Drafts and revisions involved contributors from organizations including Pratt & Whitney, Raytheon Technologies, MITRE Corporation, and university research centers such as Massachusetts Institute of Technology and Cranfield University. The "A" revision consolidated industry feedback from stakeholders including certification authorities in the United States and European Union, and from working groups connected with EUROCAE.
ARP4754A addresses system life-cycle processes applicable to airborne systems and equipment on programs such as the Dassault Falcon business jet and the Boeing 787 Dreamliner, specifying activities for concept, development, and certification phases overseen by organizations like NASA and program offices at BAE Systems. Its objectives include demonstrating system-level compliance with safety objectives derived from functional analyses used on programs like the C-130 Hercules and providing structured evidence for certification submissions to authorities such as the Civil Aviation Safety Authority (Australia). The standard targets suppliers ranging from avionics firms such as Garmin to prime integrators like Embraer.
The guidance in ARP4754A covers process models for requirements capture, system architecture, allocation, integration, verification, and validation, mirroring methods applied in systems engineering curricula at institutions like Stanford University and Imperial College London. It prescribes activities such as system requirements flowdown and trade studies practiced by engineering teams at Rolls-Royce Holdings and Bombardier. The processes reference lifecycle artifacts and models used with tools from vendors such as IBM and Siemens, and align with configuration management and change control techniques adopted by General Dynamics and Thales Alenia Space.
ARP4754A is intended to be used with related documents including guidance from RTCA papers such as DO-178C for airborne software and DO-254 for complex electronic hardware, and to interoperate with process standards like ISO 9001 and AS9100. It is often applied in conjunction with safety assessment standards like ARP4761 and certification considerations from the Federal Aviation Administration advisory circulars and EASA guidance material. Systems engineers reference methods from academic references associated with the International Council on Systems Engineering and compliance frameworks used by Boeing programs.
Implementation of ARP4754A on programs requires tailoring to program scale and contractual constraints seen on programs by Sikorsky Aircraft and Textron Aviation, and coordination with certification authorities including Transport Canada Civil Aviation and Japan Civil Aviation Bureau. Certification evidence often includes traceability matrices, verification reports, and safety assessments submitted alongside compliance artifacts prepared by contractors such as Leonardo S.p.A. and systems integrators like Ivor Weeks-era teams (industry subject-matter contributors). Tool qualification, supplier oversight, and configuration control practices are monitored by certification authorities and internal quality organizations modeled after Boeing and Airbus program quality assurance.
ARP4754A has influenced systems engineering practices across aerospace supply chains including primes such as Lockheed Martin, midsize firms like Leonardo, and niche avionics suppliers such as Viasat. The guideline has shaped training curricula at institutions including Embry–Riddle Aeronautical University and professional development programs by SAE International committees. Its adoption has affected program risk management and has been cited in industry white papers from Raytheon and Pratt & Whitney as a foundational element for aligning development with certification expectations of authorities such as the Federal Aviation Administration and European Union Aviation Safety Agency.
Category:Aerospace standards