REG NASA-LLIS-1831--2004 Lessons Learned Human Engineering should be considered a Systems Engineering and Integration function.pdf

《REG NASA-LLIS-1831--2004 Lessons Learned Human Engineering should be considered a Systems Engineering and Integration function.pdf》由会员分享，可在线阅读，更多相关《REG NASA-LLIS-1831--2004 Lessons Learned Human Engineering should be considered a Systems Engineering and Integration function.pdf（3页珍藏版）》请在麦多课文档分享上搜索。

1、Lessons Learned Entry: 1831Lesson Info:a71 Lesson Number: 1831a71 Lesson Date: 2004-3-17a71 Submitting Organization: KSCa71 Submitted by: Damon StambolianSubject: Human Engineering should be considered a Systems Engineering and Integration function Abstract: At the Orbiter Space Plane (OSP) System D

2、esign Review there was a lack of evidence that Human Factors contributions were being made to all applicable areas within the System, in particular, ground operations. For example, Human Engineering methods to evaluate access to the spacecraft were not shown, both in the way of platforms for hard to

3、 reach areas of the spacecraft and access to the spacecrafts individual subsystems for repairs and testing. Integrating Human Engineering methods into a systems approach at the beginning of the design development is vital to making the operations safer and easier for the maintainer and operator, as

4、well as improving turnaround time and processing. To ensure that Human Engineering is not overlooked each system should have its own Human Engineering section to confirm that this particular system has been addressed by Human Engineering. Within this section, useful parts of MIL-STD-1472 and other a

5、pplicable Human Engineering documents that apply to this system should be listed.Description of Driving Event: At the Orbiter Space Plane (OSP) System Design Review there was a lack of evidence that Human Factors contributions were being made to all applicable areas within the System, in particular,

6、 ground operations. Contractor products did not adequately consider Human Engineering functions. Even though the development was in the early stages, proposed tools and methods used for developing tasks analysis and usability testing between operators and hardware should have been presented. For exa

7、mple, Human Engineering methods to evaluate access to the spacecraft were not shown, both in the way of platforms for hard to reach areas of the spacecraft and access to the spacecrafts individual subsystems for repairs and testing. Addressing these simple Human Engineering aspects of spacecraft pro

8、cessing would have given some indication that they were planning on integrating Human Engineering into a systems approach. Integrating Human Engineering methods into a systems approach at the beginning of the design development is vital to Provided by IHSNot for ResaleNo reproduction or networking p

9、ermitted without license from IHS-,-,-making the operations safer and easier for the maintainer and operator, as well as improving turnaround time and processing. Lesson(s) Learned: Human Engineering contributions are best considered if integrated during the design process. Failure to involve Human

10、Engineering at the System level ultimately leads to design that are less then optimal from a maintainability, supportability, and operability standpoint.Recommendation(s): 1. Future Programs should place more emphasis on Human Engineering effects for design, development, and operation. 2. An effecti

11、ve approach would be to include Human Engineering under Systems Engineering and Integration (SE&I). 3. Ensure data products are in place up front to address Human Engineering Functions at the Systems level. 4. To ensure that Human Engineering is not overlooked within each system, e.g., Mechanical, E

12、lectrical, Fluids, etc., each system should have its own Human Engineering section to confirm that this particular system has been addressed by Human Engineering. Within this section, useful parts of MIL-STD-1472 and other applicable Human Engineering documents that apply to this system should be li

13、sted.Evidence of Recurrence Control Effectiveness: OSP Program was working to recognize and integrate Human Engineering as a Program-level entity, but this was never realized. Request For Proposal inputs added emphasis to Human Engineering functions and were a step in the right direction for future

14、contractor work. Documents Related to Lesson: Mil-Std-1472, Human EngineeringMission Directorate(s): N/AAdditional Key Phrase(s): a71 Missions and Systems Requirements Definition.Human factors impact on mission designa71 Engineering Design (Phase C/D).Human Factors/HabitabilityProvided by IHSNot for

15、 ResaleNo reproduction or networking permitted without license from IHS-,-,-a71 Mission Operations and Ground Support Systems.Ground support systemsAdditional Info: a71 Project: Oribiter Space Plane Program (OSP)Approval Info: a71 Approval Date: 2008-04-11a71 Approval Name: mbella71 Approval Organization: HQProvided by IHSNot for ResaleNo reproduction or networking permitted without license from IHS-,-,-