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

MIL-HDBK-29612-1AFIGURE 5. GCO Example - Continued.3.4 Data format requirements. While several military, commercial, and international standardsand specifications currently address formats for data creation, storage, and interchange, many of themilitary standards are being eliminated under the current acquisition reform effort, and others arebeing transitioned to performance specifications (MIL-PRF). The performance specifications definewhat the DoD needs in terms of form, fit, and function rather than how to build an item. Standards setboundaries for data acquisition and management. However, to achieve “best value” in data as well asin weapon systems, IDE data standards must be neither restrictive nor prescriptive. They must bedriven by existing and emerging commercial standards as well as by programmatic business needs.Where applicable and more advantageous, XYZ will adopt into its weapon system programs,commercial product data creation, storage, and interchange standards to meet its business needs.Specific data formats and delivery media shall be stated on individual CDRL items, CLINs, orExhibits. Proper safeguards will be used for classified information (DoD 5520.22M). Whendiscrepancies occur between this GCO and the CDRL/CLIN/Exhibit, the CDRL/CLIN/Exhibit shalltake precedence. In general, the formats and delivery media listed in paragraph 3.5 are recommendedfor each data type.3.5 Data format recommendations. Within each of the three major IDE data categoriesdiscussed in Section 3.1, one or more of the following data types will be digitally developed, delivered,and maintained within the XYZ IDE. The following sub-sections describe these data types andprovide the XYZ training program manager’s recommendations for format. On-line delivery/access isrecommended for all data types. However, very large data files that would overburden the network arestill recommended for delivery via physical media (e.g., magnetic tape) in accordance with MIL-STD-1840.a. Training management data. Training management and administrative data includesinformation that is not usually used for instructional materials configuration management,however, the data is updated and archived during the life cycle of the training program.b. Instructional data. Instructional data includes lesson plans, student guides, audio/visualaids, and other instructional material.c. Training life-cycle maintenance data. Life-cycle maintenance data includes instructionalperformance requirements, instructional media design, and other source information to beused in development of instructional materials. This source data is updated andmaintained for the life cycle of the training program.d. Administrative data. Includes program plans, budgets, and schedules, cost performancereports, program financial execution data, engineering management plans, generalcommunications, procurement data, etc. All XYZ administrative data will be available viaon-line access/delivery. On-line management status data will be analogous to thatavailable to contractor program managers. This data should be developed in MutuallyAgreeable Commercial Software (MACS) formats. When the Government is theoriginator of data, XYZ will electronically deliver GFI data into the IDE for Governmentand contractor use.84