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 />
RECOMMENDED PROCESS FOR ETM/IETM CONTRACTING<br />
The matrix is intended to allow ETM programs to define their<br />
requirements in language that is accepted and understood by<br />
industry. For a competitive bid, it’s anticipated that the<br />
bidders would provide completed matrices back with pricing<br />
information that would enable "apples to apples" evaluation. Once<br />
pricing has been completed, the acquisition officer can review<br />
the pricing provided by the offerors with the intent that<br />
comparisons can be made from the completed matrices. These can<br />
serve as a basis for fact-finding as well.<br />
This tool can help the acquisition manager evaluate the cost<br />
benefit associated with ETMs and trade off higher cost<br />
functionality requirements with those of lower cost.<br />
USE OF THE FUNCTIONALITY MATRIX<br />
The matrix is intended to serve as a "shopping list" for desired<br />
capabilities for various types of typical technical data. Some of<br />
the functionalities for specific data types are mutually<br />
exclusive and therefore grayed out. For example, in the<br />
navigation functionality, it is anticipated that one method or<br />
functionality would be used for all data types. There are also<br />
some conditional relationships by definition that need to be<br />
considered by the acquisition manager e.g. IPB/IPC (Illustrated<br />
Parts Breakdown/Illustrated Parts Catalog) data would have to be<br />
acquired in order to impart the Parts Ordering functionality (See<br />
attachments).<br />
For the purposes of this document and its attachments, “tech<br />
data” refers to the data traditionally found in technical<br />
manuals and publications (not necessarily including engineering<br />
or program data).<br />
The matrix is broken out into two separate sheets representing<br />
different ETM strategies. There is one matrix each for page<br />
oriented publications, and Interactive Electronic Publications<br />
(IETP).<br />
Page oriented publications are presented in a linear or document<br />
oriented manner. The data author largely predefines the<br />
sequence of the data presentation. Page oriented publications<br />
can be designed for traditional printing or for electronic<br />
display. Electronically displayed page oriented publications<br />
are sometimes called Electronic Technical Manuals (ETM) or<br />
Electronic Technical Publications (ETP).<br />
3 Enclosure (2)
Change language