UNLIMITED FREE
ACCESS
TO THE WORLD'S BEST IDEAS

SUBMIT
Already a GlobalSpec user? Log in.

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

Customize Your GlobalSpec Experience

Finish!
Privacy Policy

This is embarrasing...

An error occurred while processing the form. Please try again in a few minutes.

NASA-LLIS-1831

Lessons Learned – Human Engineering should be considered a Systems Engineering and Integration function

active, Most Current
Organization: NASA
Publication Date: 17 March 2004
Status: active
Page Count: 3
scope:

Abstract:

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, 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 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 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 applicable Human Engineering documents that apply to this system should be listed.

Document History

NASA-LLIS-1831
March 17, 2004
Lessons Learned – Human Engineering should be considered a Systems Engineering and Integration function
Abstract: 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...
Advertisement