05.01.2013 Views

Helmet-Mounted Displays: - USAARL - The - U.S. Army

Helmet-Mounted Displays: - USAARL - The - U.S. Army

Helmet-Mounted Displays: - USAARL - The - U.S. Army

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Test and Evaluation 10<br />

Clarence E. Rash<br />

John C. Mora<br />

Melissa H. Ledford<br />

Introduction<br />

Inherent to any design program is the need to test and evaluate<br />

operational performance. Such testing should begin during the earliest<br />

phases of development. <strong>The</strong> end goal should be to fully qualify the system<br />

at first flight. Unfortunately, in many past programs, waivers were<br />

requested for performance failures which were identified and known for<br />

some time. Despite the belief of program managers, the easiest and most<br />

cost-effective time to solve a problem is when it is first discovered.<br />

At the very least, testing and evaluation should be a required action at<br />

all major program milestones. Detailed test plans should be predeveloped<br />

but be flexible enough to accommodate the recognized complexity of HMD<br />

systems. It is not to be expected that one grand HMD test and evaluation<br />

plan will serve for all HMD designs. However, there are some basic testing<br />

tenets and system parameters which should be considered, if not required,<br />

for a thorough testing plan.<br />

As applicable, testing should consist of a bench (laboratory) phase and<br />

a field phase. Also, as applicable, testing should be at the subsystem, as<br />

well, as the system level. For the <strong>Army</strong> aviation HMD design, the basic<br />

subsystems are: image source, display optics, helmet, and tracker.<br />

Laboratory<br />

261

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!