NAVAL AVIATION SYSTEMS - NASA Wiki
NAVAL AVIATION SYSTEMS - NASA Wiki
NAVAL AVIATION SYSTEMS - NASA Wiki
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
CHAPTER XI: KEY TOPICS<br />
PART E: DATA MANAGEMENT<br />
Purpose: To address data management as a key issue impacting management decisions during the acquisition<br />
process. The non-availability of adequate and complete data is an impediment to the support of our fleet and our<br />
ability to support full and open competition of our weapon systems.<br />
Source Documentation:<br />
DoD 5000.2R - Mandatory Procedures for Major Defense Acquisition Programs<br />
(MDAPs) and Major Automated Information System (MAIS) Acquisition Programs<br />
DoD 5010.12-M Procedures for the Acquisition and Management of Technical Data<br />
NAVAIRINST 4200.21C of 29 Jun 1995, Data Requirements Review Board (DRRB)<br />
AMSDL (Acquisition Management System and Data Requirements control List) issued<br />
semi-annually in April and October.<br />
Responsibilities: All program managers are responsible for ensuring their data requirements comply with the<br />
policy of DoD 5000.2-R and NAVAIRINST 4200.21C, DRRB.<br />
AIR-1.3.3 is responsible for developing and maintaining command policies and procedures governing the<br />
acquisition and management of data. Upon request of program managers, AIR-1.3.3 will assist in the Program<br />
Planning Conferences (PPCs) (see Chapter XI, Part G of this Guide for information on the PPC) on issues relative<br />
to data acquisition. AIR-1/3/3 will also upon request from the program managers, Chair of Vice Chair the DRRBs<br />
IAW NAVAIRINST 4200.21C.<br />
Background: Acquisition of data and tailoring data requirements will be discussed as part of the PPC with the<br />
appropriate IPT members and user community involved. Sufficient time should be allowed to produce a quality<br />
Performance Based Statement of Work and the minimum data requirements to support the specific Mission Needs<br />
Statement or Operational Requirements Document. It is imperative the DoD reduce the cost of data acquisitions,<br />
one way is requesting data in contractor format versus unique DoD format (utilize the AMSDL). With realistic<br />
time schedules established, the rework of Procurement Initiation Documents can be reduced.<br />
POC: John Jones, AIR-1.3.3, 301-757-9090, Bldg 441<br />
52