REG NASA-LLIS-1610--2005 Lessons Learned - Systems Engineering Balancing the Requirements Between Scientific and Engineering Data.pdf

《REG NASA-LLIS-1610--2005 Lessons Learned - Systems Engineering Balancing the Requirements Between Scientific and Engineering Data.pdf》由会员分享，可在线阅读，更多相关《REG NASA-LLIS-1610--2005 Lessons Learned - Systems Engineering Balancing the Requirements Between Scientific and Engineering Data.pdf（3页珍藏版）》请在麦多课文档分享上搜索。

1、Lessons Learned Entry: 1610Lesson Info:a71 Lesson Number: 1610a71 Lesson Date: 2005-01-01a71 Submitting Organization: ARCa71 Authored by: Donald R. MendozaSubject: Systems Engineering: Balancing the Requirements Between Scientific and Engineering Data Abstract: A senior individual with decades of ex

2、perience on many space flight projects, including several X-vehicle programs, has made the observation that the engineering data is consistently reduced in favor of other aspects of the mission (performance, scientific data, simplicity). Description of Driving Event: A senior individual with experie

3、nce in many space flight projects, including several X-vehicles, had several observations regarding the relatively low priority (as compared to the science data) the Agency places on engineering data and instrumentation. The observation is that most missions do not include sufficient instrumentation

4、 for engineering. Thus, much data that could contribute to the understanding of margins and strengthen future designs (or even improve the current mission design) is never captured. Because little engineering data is available, its not possible to use analogy confidently in new designs so NASA must

5、start over each time. Worse, post mission analysis does not have sufficient data to determine the contributing factors to either the missions success or failure, meaning lessons learned and knowledge capture is inadequate. Many factors contribute to the failure to collect engineering data. Usually,

6、the engineering data needs of future missions have not yet been defined and thus are not a requirement to the current mission. Contractors are resistant to include more instrumentation for engineering data due to the additional weight, power requirements and complexity; scientific data collection an

7、d performance are given priority. Lesson(s) Learned: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-1. All missions, successful or unsuccessful, need an adequate amount of engineering instrumentation in order to be useful for the future.2. Contracto

8、rs have no incentive to provide engineering data as collecting it adds weight and complexity and may not contribute to the success of mission (unless there is a problem). Thus, the risk management aspects of the data may not be appreciated since it only comes into play if the current mission has a p

9、roblem or in helping design future missions.Recommendation(s): 1. All projects should be required to document how their mission will feed engineering data to future missions.2. All projects should develop a list of instrumentation priorities (including a minimum instrumentation set for launch and op

10、erations) and a process to manage them. Prior to engineering instrumentation being reduced, the impacts on future missions and on trouble-shooting the current mission need to be weighed against the costs (weight, power requirements).Evidence of Recurrence Control Effectiveness: N/ADocuments Related

11、to Lesson: NPR 7120.5Mission Directorate(s): a71 Exploration Systemsa71 Sciencea71 Aeronautics Researcha71 Space OperationsAdditional Key Phrase(s): a71 Policy & Planninga71 Program and Project Managementa71 Risk Management/Assessmenta71 Safety & Mission AssuranceAdditional Info: Provided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval Info: a71 Approval Date: 2006-04-18a71 Approval Name: dkruhma71 Approval Organization: HQProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-