10.07.2015 Views

department of defense handbook guidance for acquisition ... - NAVAIR

department of defense handbook guidance for acquisition ... - NAVAIR

department of defense handbook guidance for acquisition ... - NAVAIR

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

MIL-HDBK-29612-1AC.5.6.1 Page-based (composed) data products. Human-readable or viewable documents indigital or hard copy <strong>for</strong>mat. These products display pages, illustrations, or other objects. Pagebasedtraining documents normally provide textual (prose) in<strong>for</strong>mation and/or graphics that, asdelivered, are suitable <strong>for</strong> use in an instructional environment (e.g., a hard-copy lesson plan,transparency, wall chart, graphic, etc.).C.5.6.2 Processable data files. Machine-readable data that users can input into and editusing multiple data applications to produce standard and custom documents. Examples <strong>of</strong>processable files are text files, graphic files, alphanumeric files, audio/visual files, and relationaldatabase files. Files available in standard data exchange <strong>for</strong>mats are more widely transportableamong dissimilar hardware and s<strong>of</strong>tware applications. Processable data files are the preferreddata type <strong>for</strong> most new deliverables. Acquisition managers should also be aware <strong>of</strong> neutral file<strong>for</strong>mats such as Portable Document Format (PDF). These types <strong>of</strong> files fall between composedand processable <strong>for</strong>mats - they are not fully processable, but they are much more versatile thanpage-based composed products, and are there<strong>for</strong>e becoming very popular, especially <strong>for</strong> legacydata.C.5.6.3 Legacy data files. Legacy data files provides in<strong>for</strong>mation presented in a <strong>for</strong>mat thatcon<strong>for</strong>ms to the data structures specified in existing service unique, legacy automated systemssometimes referred to as Government Off the Shelf (GOTS) automated systems and CommercialOff the Shelf (COTS) automated systems which have not con<strong>for</strong>med to data standards specifiedin the Defense Data Dictionary System (DDDS). Using legacy data, while not directlyfacilitating full interoperability <strong>of</strong> training data, has significant advantages over continuing topurchase printed data products. Most GOTS AND COTS systems manage data in a computerbasedRelational Data Base Management System (RDBMS). It is important that the RDBMS beOBDC compliant and that the data structure <strong>of</strong> the GOTS or COTS be mapped to the datastandards in the DDDS. This will facilitate its future conversion to standard digital data and itsuse by other organizations. The primary reason that legacy data is purchased is to facilitate itsuse or manipulation <strong>of</strong> digital data in existing systems and tools which convert it into in<strong>for</strong>mationsuitable <strong>for</strong> immediate use in an instructional environment. The decision on whether to convertany existing training data product (e.g., lesson plan, trainee guide, audio/visuals, etc.) to SDDwill be based on factors such as current life-cycle stage, volume <strong>of</strong> data, economic feasibility <strong>of</strong>conversion, and data usage and frequency <strong>of</strong> change. Since most military training organizationshave some legacy systems or use some COTS programs, the purchase <strong>of</strong> legacy type data will berequired until these are replaced by DDDS compliant systems. The GCO defines theorganization’s mix <strong>of</strong> existing legacy (GOTS/COTS) systems.C.5.7 Determine data <strong>for</strong>mat. The <strong>acquisition</strong> manager will need to identify the data<strong>for</strong>mat(s) <strong>for</strong> delivery, which is determined by the type <strong>of</strong> data deliverable described in paragraphC.5.6. The chosen <strong>for</strong>mats will affect interchange standards and the media used <strong>for</strong> datadelivery. The following data <strong>for</strong>mats are the <strong>for</strong>ms in which each <strong>of</strong> the types <strong>of</strong> data76

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

Saved successfully!

Ooh no, something went wrong!