This content is not included in
your SAE MOBILUS subscription, or you are not logged in.
Will the Real Solution Please Stand Up
Technical Paper
2009-01-3106
ISSN: 0148-7191, e-ISSN: 2688-3627
Annotation ability available
Sector:
Language:
English
Abstract
This technical paper and presentation addresses the need for more refined, pervasive and highly engaged technical leadership in the system safety discipline. Systems engineering disciplines have been led to believe that by following a single industry standard, generic plans, inflexible processes, proven methods and techniques a system with low safety risk will evolve with little rework. The truth is there is no prescriptive one size fits all approach, or a convention that will anticipate and cover all needs. In several domain areas, especially modern military and commercial airborne systems, diverse technology and functionality have been evolving with such high complexity and criticality that collective processes will not work unless seasoned leaders allow creativity and innovation to be part of the safety culture. Leaders must have intuitive engineering and operations judgment to determine how to best allocate effective resources to meet system safety goals and objectives. This means allowing the safety culture to evolve to the point where system safety engineers are empowered to seek performance based and functional solutions and inclusion of the human systems integration domain in error reductions, rather than following outdated hazard based models designed for federated systems before automation, high complexity and safety criticality was controlled by software and collaborative and highly integrated systems.
Recommended Content
Technical Paper | Aircraft Level Steering Runaway Failure Analysis |
Technical Paper | ISO-26262 Implications on Timing of Automotive E/E System Design Processes |
Technical Paper | How to Integrate Model-Based Systems Engineering across Automotive EE Domains |
Authors
Topic
Citation
Hendrix, B., "Will the Real Solution Please Stand Up," SAE Technical Paper 2009-01-3106, 2009, https://doi.org/10.4271/2009-01-3106.Also In
References
- Human Factors in Technology Bennett Edward The MITRE Corporation 1963
- SAFEWARE, System Safety and Computers Leveson Nancy 1995
- Lean Software Strategies, Proven Techniques for Managers and Developers Middleton Peter Sutton James 2005
- Human Factors in Aviation Operations 21st Conference of European Association for Aviation Psychology (EAAP) Fuller Ray 1995
- A Methodology Framework for Root Cause Analysis of Human Error Pedrali M. Cojazzi G. 1995
- Research Techniques in Human Engineering Chapanis Alphonse John Hopkins University 1958
- Structural Probabilistic Methodology for Fatigue Reliability Havrisik D. The University of Alabama in Huntsville 1999
- Joint Software System Safety Handbook (JSSSH) Gill Janet Brown Mike Alberico David et al. DoD Industry Team 1999
- FZM-9253 Lockheed Martin Aeronautics Software System Safety and Safety-Critical Software Guidebook Hendrix B. Kilgore K. 2006
- GAO/NSIAD-98-95BR, United States General Accounting Office, Military Aircraft Safety: Serious Accidents Remain at Historically Low levels March 23 1998
- Standard Practice 882D System Safety, Rev 1 2008
- ANSI/GEIA-STD-010-2009, Standard Best Practices for System Safety Program Development and Execution
- SAE ARP4761 Guidelines and Methods for Conducting the Safety Assessment Process on Civil Airborne Systems and Equipment 1996
- SAE ARP4754 Certification Considerations for Highly Integrated and Complex Aircraft Systems 1996
- IEEE STD-1228-1994 Software Safety Plans 1994
- IEC 61508 Functional Safety of Electrical/Electronic/Programmable Electronic Safety-Related Systems 1998
- DEF-STAN-00-56 Safety Management Requirements for Defence Systems
- G-48 System Safety Committee Meeting #123, International System Safety Conference (ISSC) Huntsville, Al August 5, 2009