SECTION 1 -- INFORMATION STANDARDS

4.1 INTRODUCTION

4.1.1 Purpose

This section identifies the information standards that are applicable to all Automated Information System (AIS) programs in the DOD. Information standards pertain to process models, data models, data definitions, and data exchanges among systems.

4.1.2 Scope

This section provides implementation direction that affects the definition, design, development, and testing of AIS programs. It is applicable at all organization levels and environments (e.g., tactical, strategic, sustaining base, and interfaces to weapons systems).

The relationship of the Information Standards to the TAFIM is illustrated in
Figure 4-1. Relationship of TAFIM to Information Standards

To support the identification of information and information interchange requirements, the DOD has selected the IDEF modeling methodology. DOD Directive 8320.1-M requires IDEF0 (Integrated Definition for Function Modeling) in accordance with FIPS Pub 183 and IDEF1X (Integrated Definition for Information Modeling) in accordance with FIPS Pub 184 as the presentation standard for activity and data modeling, respectively. The IDEF Modeling methodology defines an unambiguous set of the following components:

Information Standards define an architecture at the logical level. The process model is a view of the activities, both automated and manual, that an organization must perform to achieve its mission. Modeling an organization's processes and data begins at the highest logical level, is decomposed into lower logical levels and is communicated in a format that the users, particularly the subject matter experts, can easily understand and use.

To satisfy the data definition and documentation standards, the DOD has created the Defense Data Repository System (DDRS). The DDRS is used to collect and integrate individual data models into a DOD data model and to document content and format for data elements. It is the DOD-wide integration point for standard data element definitions.
Figure 4-2. Objective Information Standards TA

The definition and documentation of data exchange mechanisms are provided by various messaging standards, such as the Variable Message Format (VMF), the U.S. Message Text Format (USMTF), and the National Imagery Transmission Format (NITF). Each message standard provides a means to define message form and functions (i.e., transfer syntax), which includes the definition of the data elements that are contained in each message. Other techniques provide direct database to database exchange of data as a service in formats that are invisible to the user. The data elements, which are currently defined in the various message standards, are not mutually consistent or based on any process or data models either within a message system or across message systems. These definitions will be converged to the set that is developed through the process and data modeling efforts accomplished under this standard.

4.2 MANDATES

4.2.1 Process Model

System acquisition and development begins with the identification of the need for a system to rectify a capability deficiency and the development of an Operational Requirements Document (ORD). Prior to beginning system development, the ORD shall be modeled using the IDEF0 methodology (FIPS Pub 183) to a level of detail sufficient to identify each entity in the data model that is involved in an activity. The activity model shall form the basis for data model development or refinement. The activity model will be validated against the requirements document and doctrine and approved by the combat developer. The process model that is contained in the DOD Enterprise Model shall be used as a reference for extending activity models for specific programs.

As activity models are developed, security levels and caveats shall be considered. It must be possible to classify an entire model or to classify only certain activities and inputs, controls, outputs, and mechanisms (ICOM) within a model. Activities and ICOMs must have provision for hierarchical (e.g., SECRET, TOP SECRET) and non-hierarchical (e.g., US ONLY, RELROK) security classification levels for the case where the model is unclassified, but the data is classified. It must be possible for a model to assume a range of security classification levels during its life cycle development as requirements are refined. It must be possible to classify a previously unclassified model when it is re-used within a different context.

4.2.2 Data Model

The basis for data modeling shall be the C2 Core Data Model, which is part of the DOD Enterprise Data Model. Information requirements that are derived from activity models will be used to extend the C2 Core Data Model. Computer Automated Software Engineering (CASE) tools that support IDEF1X diagrams shall be used to extend the model with additional logical entities, attributes, and relationships. The IDEF1X syntax and diagramming conventions shall be in accordance with FIPS Pub 184. Data model development shall proceed in accordance with DOD 8320.1-M-X.

The data models shall be used in software requirements analyses and design activities as a logical basis for physical database design.

As data models are developed, security levels and caveats shall be considered. It must be possible either to classify an entire model or to classify only certain entities, attributes, relationships, or metadata within a model. It must be possible for a model to support a range of security classification levels. It must be possible to classify a previously unclassified model.

4.2.3 Data Definitions

The DDRS, which is managed by the Defense Information Systems Agency (DISA), is a central database that includes data standards in terms of standard entities, data elements and data models. System developers shall use the DDRS as a baseline to identify data elements for extending data models and for implementation. DOD Directive 8320.1-M provides the procedures for Data Administration. DOD 8320.1-M-1 provides data element standardization procedures. A classified version of the DDRS is being developed to support standardization of classified data elements and domains.

4.2.4 Data Exchange

4.2.4.1 Data Exchange Applicability

This section covers the exchange of information among mission area applications within the same system or among different systems. The exchange of information among applications shall be based on the logical data models developed as the result of identifying information requirements through activity or process models. The data model identifies the logical information requirements, which shall be developed into physical database schemas and standard data elements. The standard data elements shall be exchanged using the data management and data interchange services of application platforms. The intent is to exchange information directly between information systems without the constraint of formatted messages, subject to security classification considerations.

The message sets described below are only intended to provide an interim means of transferring information until a single methodology using standard data is approved. DISA is the proponent for information exchange using standard data.

4.2.4.2 VMF Messages

VMF messages shall be used for information transfer between systems requiring bit- oriented message formats in communication bandwidth constrained environments (e.g., over CNR). VMF messages are specified in the VMF Technical Interface Design Plan (TIDP) for Task Force XXI. A standard set of 41 VMF messages is currently available.

4.2.4.3 USMTF Messages

USMTF messages shall be used for information transfer between systems interoperating over higher bandwidth communications systems, such as LANs. USMTF messages are listed in JCS Publication 6-04. USMTF messages are character based and limited to the teletype character set. USMTF messages will also be used when required for Joint interoperability.

4.2.4.4 TADIL-J Messages

TADIL-J (i.e., Link 16) messages shall be used for information transfer with Airborne Weapon platforms that use the Joint Tactical Information Distribution System (JTIDS). TADIL-J supports time-critical data dissemination, such as air tracks. The use of TADIL-J for JTIDS communications is consistent with DOD interoperability mandates. TADIL-J is specified in the JTIDS TIDP Test Edition.

4.2.4.5 NITF Imagery

NITF Standard (NITFS), as specified in MIL-HDBK-1300, shall be used as the suite of standards for data format and compression algorithms for digital imagery and imagery- related products. MIL-HDBK-1300 identifies the following standards: MIL-STD-2500 (NITF Version 2 file format); MIL-STD-2301 (CGM for NITFS); and MIL-STD-188- 196, MIL-STD-197, and MIL-STD-198 (image compression).

MIL-HDBK-1300 identifies two methods of communication for NITF imagery and related material. The methods are FTP-based file transfer (see Section 3.2.1.4) and Tactical Communications Protocol 2 (TACO2). This TA mandates that only FTP-based file transfers shall be used.

Return to C4I Technical Architecture Table of Contents