REG NASA-LLIS-1446-2003 Lessons Learned Accident Investigations Database Collaborative Tool PBMA (Process Based Mission Assurance).pdf

1、Lessons Learned Entry: 1446Lesson Info:a71 Lesson Number: 1446a71 Lesson Date: 2003-08-31a71 Submitting Organization: JSCa71 Submitted by: David LengyelSubject: Accident Investigations/Database/Collaborative Tool PBMA (Process Based Mission Assurance) Abstract: Experience with PBMA indicates that it

2、 was oversold and it did not deliver expected capabilities. It is unlikely, however, that a software system for action item tracking and investigative data configuration management can be selected that will be wholly satisfactory to the entire board.Description of Driving Event: For the Columbia acc

3、ident investigation, the PBMA tool was oversold to rapidly assembled Board and Task Force members and did not deliver capabilities as expected. For example, record keeping, cataloging, tracking/status, search & retrieval, and metrics data were not immediately available in PBMA, resulting in an overa

4、ll frustration and delays with the capability for getting data out of PBMA into the hands of the users. This tool was often found to be incompatible with other tools and its security system was overly complex.Lesson(s) Learned: For large accident investigation support, is unlikely that you can selec

5、t a software system for action item tracking and configuration management of investigative data that will make everyone happy at the same time.Recommendation(s): Consider the following criteria when selecting a software management system for accident investigation support: Provided by IHSNot for Res

6、aleNo reproduction or networking permitted without license from IHS-,-,-a71 allows for the easy upload and download of very large files 100 to 300MB.a71 is flexible and compatible enough to adapt to new requirementsa71 the advantages and disadvantages are sufficiently vetted by the Boarda71 the syst

7、em can be adequately tested in the Boards environment before full buy-ina71 is not overly complex, so that investigators dont have to spend many hours traininga71 remote access consistent with the Boards organization and nothing morea71 factor of security is consistent with investigations need for s

8、implicity and rapid startupa71 has good keyword search capabilitya71 avoid systems that will immediately require customizationa71 use a Commercial Off the Shelf (COTS) solution when possiblea71 electronic tools must be able to store and manipulate 3-D engineering models.Evidence of Recurrence Contro

9、l Effectiveness: TBD NASA ResponseDocuments Related to Lesson: Agency Contingency Action Plan for Space Flight OperationsMission Directorate(s): a71 Space Operationsa71 Exploration SystemsAdditional Key Phrase(s): a71 Accident Investigationa71 Administration/Organizationa71 Computersa71 Configuratio

10、n Managementa71 Information Technology/Systemsa71 NASA Standardsa71 Policy & Planninga71 Safety & Mission AssuranceAdditional Info: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval Info: a71 Approval Date: 2004-06-16a71 Approval Name: Ronald Montaguea71 Approval Organization: JSCa71 Approval Phone Number: 281-483-8576Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-