10.11.2014 Views

NAVAL AVIATION SYSTEMS - NASA Wiki

NAVAL AVIATION SYSTEMS - NASA Wiki

NAVAL AVIATION SYSTEMS - NASA Wiki

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.

Lessons Learned:<br />

1) Too Little Too Late. Many programs seen to be unaware of the HSI requirement until a milestone review is<br />

imminent and an HSI Plan is needed. Documentation drills serve no one. Assessors at various levels will no<br />

longer accept obvious hurried, inadequate HSI Plans. Contact the NAVAIR HSI Coordinator as early as possible<br />

to obtain the latest guidance and support.<br />

2) Team Effort. HSI is consistent with current team concepts. Program- or IPT-level HSI working groups are one<br />

of the main integration mechanisms. Design efforts and documentation efforts should be team activities. Your<br />

HSI team should constitute both management and technical personnel.<br />

3) I'm Human, I Can Do HSI. The disciplines of HSI are legitimate, scientifically-based technical disciplines with<br />

supporting theories, empirical data, analytical techniques, methodologies, and professional guidelines that take<br />

advanced academic degrees and many years of experience to master. Although fleet user representation on design<br />

teams is desirable, it cannot replace experienced, proficient professionals. After all, it would be ludicrous for the<br />

government to ask Aviation Power Plant Specialists or Maintenance Officers to evaluate engine design concepts<br />

and designs, then accept their opinions wholesale. Yet, we seem to do this routinely with HSI matters.<br />

POC: LCDR Fran Piccione, AIR-4.1C, (301) 342-2241<br />

70

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

Saved successfully!

Ooh no, something went wrong!