MIL-STD-3014 CHANGE 3

Abstract

This standard defines a format for digital data files used for mission-level programming of weapon systems. The term format applies to the organization of data information in the file and the definition of approved data types. <br>a. This standard defines, first, a hierarchical or "nested" file architecture, which allows a broad and open-ended variety of data types to be combined and used for a variety of purposes. <br>b. Second, this standard is supported by online registries that catalogue and define standard formats to be used for some common-use data elements, for which a common data format is of benefit. <br>c. Third, this standard is supported by online registries that catalogue and identify unique data types required by specific acquisition programs. As a unique data type registry, this standard supports the use of data types whose definitions are proprietary, classified, or have very limited application. The registry serves to identify such data types without the need to define them, and prevents indeterminacy and confusion caused when different applications choose the same identifier for different types of data. <br>d. Finally, this standard is supported by online registries that identify organizations and acquisition systems that produce, transfer, or act upon mission data files. <br>This standard does not establish requirements for content of mission data files, accuracy of data, or its applicability for any specific weapon system. Those characteristics are the responsibility of the organizational entity that generates the data and formats it for use in a weapon system. <br><strong>Purpose</strong>. <br>The purpose of this standard is to provide a common lexicon with which all combat systems can exchange digital mission data for weapon systems, in order to deliver the desired effects to the enemy as rapidly, economically, effectively, and flexibly as possible. <b><u>Intended Use:</u></b> This standard is intended to be used to standardize military digital data applications for weapon system interfaces and applies to all systems that generate, modify, transport, or use digital mission plans for autonomous weapon systems. <br>