REG NASA-LLIS-4584-2012 Lessons Learned - Establishing a Configuration Status Accounting (CSA) Tool.pdf

1、Public Lessons Learned Entry: 4584 Lesson Info: Lesson Number: 4584 Submitting Organization: KSC Submitted by: Jenni Palmer Subject: Establishing a Configuration Status Accounting (CSA) Tool Abstract: In the Constellation Program (CxP), the consideration for utilizing a Configuration Status Accounti

2、ng (CSA) tool was not taken into account during the early parts of the program development cycle. This resulted in Projects under CxP performing CSA using a manual process that was subject to errors and resulted in inaccurate data reporting. The CSA tool should be in place early in the lifecycle (by

3、 the requirement development/approval phase) so as to ensure traceability from the approval of the requirements through implementation and operations of the final product. Description of Driving Event: Given the lack of a Configuration Status Accounting (CSA) tool established early in formulation, t

4、here was a possibility that the Ground Operations Project (GOP) would be hindered in its ability to effectively status and account for information and configuration. The lack of accurate information may result in faulty, inaccurate data reporting. NASA Policy requires that: The Configuration Managem

5、ent Plan (CMP) shall describe how information is released into the CSA System including Program/Project/Element authorization for release, and metadata required to solicit authorization. Identification of the current approved configuration documentation and identification number associated with each

6、 Configuration Item (CI) typically consisting of the following: a. Records and reports the status of proposed engineering changes from initiation to final approval and implementation. b. Records and reports the results of configuration audits to include the status and final disposition of identified

7、 discrepancies. c. Records and reports the status of all Change Requests that affect the configuration of a CI. d. Records and reports implementation status of authorized changes. e. Provides the traceability of all changes from the original baseline configuration documentation of each CI. f. Report

8、s the effectivity and installation status of configuration changes to all CIs at all locations. Lesson(s) Learned: Establish a robust automated process early in programs and projects to support automated configuration management and status accounting. Do not use a manual process. Recommendation(s):

9、Procure and/or develop a Configuration Status Accounting (CSA) tool early in the Program/Project that can be utilized throughout the lifecycle, not just at the operations/sustainment stage. Also, governance of tools must be specified and understood prior to tool use. Evidence of Recurrence Control E

10、ffectiveness: N/A Documents Related to Lesson: N/A Mission Directorate(s): Exploration Systems Additional Key Phrase(s): Program Management.Configuration and Data Management Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Additional Info: Project: Constellation Approval Info: Approval Date: 2012-11-02 Approval Name: mbell Approval Organization: HQ Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-