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

1、Lessons Learned Entry: 1447Lesson Info:a71 Lesson Number: 1447a71 Lesson Date: 2003-08-31a71 Submitting Organization: JSCa71 Submitted by: David LengyelSubject: Accident Investigations/Database/Collaborative Tool PBMA (Process Based Mission Assurance) Abstract: Unfamiliar database tools cause delays

2、 and use of multiple systems cause additional delay and tax the IT support staff.Description of Driving Event: Columbia accident investigation personnel were required to learn database tools with which they were unfamiliar, adding inefficiencies in Board and Task Force startup time.Lesson(s) Learned

3、: Database tools that most people are unfamiliar with will cause delays in initiating investigation. Multiple systems, implemented to satisfy specific needs, cause additional startup delay and tax the time of IT support staff.Recommendation(s): a71 Develop an appendix/annex to the Contingency Action

4、 Plan (CAP) and annually update the definition of critical tool requirements based on established selection criteria. A criteria-based tool selection process was not used resulting in a tool being procured whose capabilities were not fully understood by the primary Board and TF users.a71 Avoid real

5、time, verbal, or informal tool requirements as they will be treated by the developers as requirements that they can freely interpret and make judgments on without consultation with users, ultimately resulting in product deliveries that do not meet expectations.Provided by IHSNot for ResaleNo reprodu

6、ction or networking permitted without license from IHS-,-,-a71 Concentrate, when possible, on database systems that local Center IT and CM personnel are familiar with to minimize coordination, expedite implementation, and reduce potential system/transmission interface issues.a71 Recognize that all d

7、ata from the investigation will be archived.a71 Do not permit contractors to define and manage the Board and Task Forces IT requirements. This becomes a financial driver for them.a71 Separate database administrator function and general task force IT support (SRs, user configuration set-up, etc.).a71

8、 Identify a candidate database and data management tools that could be implemented quickly. The data management tool and approach should meet the anticipated availability, security, firewalls, capacity, and on-site/off-site access requirements for supporting a major mishap investigation without sign

9、ificant modification or development.a71 Make a data management tool/approach a part of the NASA CAP, and review annually at a minimum.a71 Avoid having the same information in too many places, as data will diverge.a71 Brief the Board Chairman and Board members upon arrival regarding their electronic

10、tools and advise them not to bring in new systems to be force-fit with systems initially laid in by NASA IT administrator. Evidence of Recurrence Control Effectiveness: TBD NASA ResponseDocuments Related to Lesson: Agency Contingency Action Plan for Space Flight OperationsMission Directorate(s): a71

11、 Space Operationsa71 Exploration SystemsAdditional Key Phrase(s): a71 Accident Investigationa71 Administration/Organizationa71 Computersa71 Configuration Managementa71 Information Technology/Systemsa71 NASA Standardsa71 Policy & Planninga71 Safety & Mission AssuranceProvided by IHSNot for ResaleNo r

12、eproduction or networking permitted without license from IHS-,-,-Additional Info: 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-,-,-