NAVAIR INSTRUCTION 4120.11 From: Commander, Naval Air ...
NAVAIR INSTRUCTION 4120.11 From: Commander, Naval Air ...
NAVAIR INSTRUCTION 4120.11 From: Commander, Naval Air ...
- No tags were found...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>NAVAIR</strong>INST <strong>4120.11</strong><br />
Subj:<br />
POLICY FOR PREPARATION AND STANDARDIZATION OF <strong>NAVAIR</strong><br />
INTERACTIVE ELECTRONIC TECHNICAL MANUALS (IETMS)<br />
d. Enclosure (2) is a description of the various IETM<br />
functional capabilities and a guide for using the<br />
functionality matrix. Enclosure (3) is the matrix itself. It<br />
is designed to serve as a program manager’s “shopping list”<br />
for technical data functional capabilities.<br />
e. Common Look and Feel across IETM types is important to the<br />
fleet customer. Enclosure (4) describes screen layouts,<br />
navigation and other basic “look and feel” requirements for<br />
<strong>NAVAIR</strong> IETMS.<br />
f. Amplifying information describing XML, MIL-STD-3001, and<br />
S1000D is provided in enclosure (5).<br />
4. Responsibilities.<br />
a. Program Managers shall:<br />
(1) Select the appropriate IETM development specification<br />
based on an analysis of functional requirements and cost<br />
benefits.<br />
(2) Ensure that contract requirements for new acquisitions,<br />
major updates to existing IETMs, and legacy conversions are<br />
assembled using enclosures (1) through (3).<br />
(3) Implement Navy Marine Corps Internet (NMCI)<br />
requirements with respect to desired IETM functionalities.<br />
(Those that require executable files will not be acceptable<br />
in an NMCI environment and will require certification<br />
testing for each and every upgrade).<br />
(4) Acquire all new IETMS in accordance with the “Look and<br />
Feel” requirements set forth in enclosure (4).<br />
(5) Assess legacy IETMs against the Common Look and Feel<br />
and develop migration plans to achieve the level of<br />
standardization reasonable for their program and customer<br />
Consider economic feasibility and the fleet goal for<br />
standardization. Complete and submit migration plans, with<br />
estimated completion dates, to <strong>NAVAIR</strong> 6.8 within six months<br />
of promulgation of this instruction. Submit annual updates<br />
to the plan, delineating progress and/or changes.<br />
3