The 2012 NASA Spacecraft Fault Management Workshop continues the efforts begun at the 1st NASA Spacecraft Fault Management Workshop (April 2008), to characterize and coalesce the systems engineering discipline of FM. Whereas the 1st NASA Spacecraft Fault Management Workshop concentrated on identifying problems and challenges that currently plague the field (see 1st NASA Spacecraft Fault Management Workshop White Paper Report), the 2012 NASA Spacecraft Fault Management Workshop will work to identify solutions to these challenges. Invited talks will highlight non-NASA views of FM (for example, the Air Force and the European Space Agency).
The goals of the 2012 NASA Spacecraft Fault Management Workshop are to:
- Capture insights into how best to assess the appropriateness of a FM approach/architecture for a mission,
- Develop a FM Technology Roadmap,
- Discuss via a panel how FM fits into the Systems Engineering engine and the Software Engineering discipline, and
- Solicit your input on the NASA Fault Management Handbook that is under development.
DAY 1 (Tuesday, 4/10) will focus on recent developments, progress and successes in the field of FM. To begin, the draft NASA Fault Management Handbook will be presented and discussed, and opportunity given for community feedback. There also will be case studies consisting of peer presentations on new technology developments, on recent mission "success stories," and on recent FM architecture trade studies.
DAY 2 (Tuesday, 4/11) will consist of two parallel break-out sessions, described below, focusing on architecture suitability and on technology needs. Technical and instructional material for these breakout sessions will be presented in plenary talks on days 1 and 2. The Architecture Trade Study breakout session will involve an assessment of the appropriateness and suitability of FM architectures for NASA missions. Participants will work in groups to complete an evaluation of several FM architectures; participants will evaluate the architectures against mission needs and quality attributes so as to assemble an FM architecture trade-space. The Technology Roadmap breakout session will focus on capturing FM capability needs and identifying technology gaps. Participants will work in groups to discover FM objectives and to establish requirements needed to assemble a technology roadmap.
DAY 3 (Tuesday, 4/12) will begin with a terminology summit to move toward consensus on and understanding of the definitions for the core terms of this field, and to lay the foundation for improved communications among members of this community. The day concludes with presentations summarizing the results and work products from the Architecture Trade Study and Technology Roadmap breakout sessions, and closing remarks.