1、Public Lessons Learned Entry: 4588 Lesson Info: Lesson Number: 4588 Submitting Organization: KSC Submitted by: Jenni Palmer Subject: Automated Management of the Technical Baseline: Abstract: During the Constellation Program, the process for identification and management of technical products within
2、the Technical Baseline was a manual process within the Windchill environment. The Technical Baseline contents were used to document the current spacecraft configurations, flight-to-ground interfaces, and other information impacting the design of Kennedy Space Centers Ground Systems. Windchill was th
3、e designated Product Data Life-Cycle Management (PDLM) tool provided under the Constellation Program. The manual process was difficult and time consuming. Description of Driving Event: The Driving Event for this effort was the requirement to track and manage all products related to the Technical Bas
4、eline within Windchill. The Technical Baseline serves as a snapshot in time of those items in the Technical Baseline. To meet the requirements of the Systems Engineering and Integration (SE&I) Technical Baseline, the following steps were required: 1. Create a technical baseline in the GOP Windchill
5、Library 2. Manage the data input by SE&I in the GOP DM Project 3. Add products to a baseline in the GOP Library 4. Roll the current baseline to the new baseline in the GOP Library 5. Initiate review/approval/release of technical baseline in the GOP Data Management (DM) Library Each time the Technica
6、l Baseline was rolled to the next revision of the Baseline in Windchill, there was no automation for this effort. All documents that were part of the Technical Baseline (and not just those products that were revised or updated) had to be manually uploaded or transferred electronically to the new bas
7、eline within Windchill. This was extremely time consuming and inefficient. Documents had to be manually moved from the Project side of Windchill to the Data Management Library side of Windchill, one document at a time. Additionally, the Technical Baseline was revised by Management Directive (MD), wh
8、ich was also a manual process. MDs were issued for each revision to the Technical Baseline under Constellation, which required an update to the MD each time, and presentation and approval at the Project Review Board (PRB). Once approved, the MD was manually released and uploaded to the Baseline. The
9、 MD contained a list of all those products that were revised for that revision to the Baseline. For efficient management of the Systems Engineering and Integration (SE&I) Technical Baseline, an automated tool or an additional module integrated within Windchill is required to track and maintain the T
10、echnical Baseline and requirements Lesson(s) Learned: A tool or module should be procured or developed that will provide automation of the Technical Baseline process and manage data integrity. Additionally, all users of the tool should receive appropriate training. Recommendation(s): Develop an auto
11、mated tool or procure a module that provides more efficient management of the Technical Baseline and integration with Windchill (the official data repository). Evidence of Recurrence Control Effectiveness: N/A Documents Related to Lesson: N/A Provided by IHSNot for ResaleNo reproduction or networkin
12、g permitted without license from IHS-,-,-Mission Directorate(s): Exploration Systems Additional Key Phrase(s): Configuration and Data Management Review boards Project planning, development, and management Additional Info: Project: Constellation Approval Info: Approval Date: 2012-11-06 Approval Name: mbell Approval Organization: HQ Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-
