INCH-POUND

MIL-STD-6016C
31 March 2004
Superseding
MIL-STD-6016B
1 August 2002

DEPARTMENT OF DEFENSE
INTERFACE STANDARD
TACTICAL DATA LINK (TDL) 16
MESSAGE STANDARD

MAIN SECTION 1 - INTRODUCTION

AMSC N/A AREA: INST

DISTRIBUTION STATEMENT D: Distribution authorized to DOD and U.S. DOD

contractors for administrative or operational use. Other requests for this
document shall be forwarded to Defense Information Systems Agency, Standards
Management Branch (DISA/GE332). See distribution warning on page 1-iii.
 MIL-STD-6016C

THIS PAGE IS INTENTIONALLY LEFT BLANK

1-ii
 MIL-STD-6016C

DISTRIBUTION WARNING

WARNING - This document contains technical data whose export is

restricted by the Arms Export Control Act (Title 22, U.S.C., Sec. 2751
et seq.) or Executive Order 12470. Violations of these export laws
are subject to severe criminal penalties. Disseminate in accordance
with provisions of DOD Directive 5230.25.

1-iii
THIS PAGE IS INTENTIONALLY LEFT BLANK
 Section 1 Table of Contents

Paragraph
1. SCOPE 1
1.1 PURPOSE OF DOCUMENT............................................1
1.2 BACKGROUND.....................................................3
1.3 DOCUMENT STRUCTURE.............................................5
1.3.1 Sections and Appendices......................................5
1.3.2 MIL-STD-6016 Appendices......................................6
1.4 POLICY 14
1.5 CONCEPT 15
1.6 DEVELOPMENT OF STANDARDS......................................16
1.7 APPLICATION OF STANDARDS......................................17
1.8 CONFIGURATION CONTROL.........................................18
THIS PAGE IS INTENTIONALLY LEFT BLANK
 SECTION 1

1. SCOPE

1.1 PURPOSE OF DOCUMENT

1.1.1 The purpose of MIL-STD-6016 is to describe the approved

standards to achieve compatibility and interoperability between
command and control and communications systems and equipment of United
States (U.S.) and coalition military forces employed or intended to be
employed in joint tactical operations. This publication is to be
complemented by Chairman Joint Chiefs of Staff Manual (CJCSM) 6120.01,
Joint Multi-Tactical Data Link (TDL) Operating Procedures (JMTOP),
which will provide for planning and common procedures to be used by
forces in the joint tactical environment using Link 16 as the basis
for information exchange.

1.1.2 The requirements defined by this document are expressed in

generic rather than platform specific terms, i.e., for Command and
Control (C2) and nonC2 Joint Tactical Information Distribution System
(JTIDS)/Multifunctional Information Distribution System (MIDS) Units
(JUs).

1.1.3 The requirements defined by this document refer to the

"Host" computer system that provides processing of tactical data.
Within each platform it may be known as the "Mission Computer",
"Advanced Data Processor (ADP)", "Central Tactical System", "Tactical
Data System", "Combat Direction System" or other title. In some
platforms, some of these requirements may be conducted within the
terminal interface unit.

1.1.4 Human Machine Interface (HMI) capabilities are defined

where they are necessary to ensure interoperability between Link 16
platforms. The HMI capabilities defined include the type of data
input, initiation of events, operator alerts and the severity of the
alerts, and where provision for display to an operator is required.
More stringent HMI requirements may be contained in individual service
appendixes.

1.1.5 It is not within the scope of this document to specify the

technical software coding design of host processing systems or of the
Link 16 Terminal design and its interfaces. These details are
specified in separate documentation.
 1.2 BACKGROUND

1.2.1 Joint Chiefs of Staff (JCS) Memorandum SM-205-71, 1 April

1971, established a program to ensure the joint interoperability of
tactical command and control systems in support of the Ground and
Amphibious Military Operations (GAMO) Program. The Joint
Interoperability of Tactical Command and Control Systems (JINTACCS)
Program was established by JCS Memorandum SM-184-78, 7 March 1978, to
replace the GAMO Program, although directives that were pertinent to
the GAMO Program are considered applicable to the JINTACCS Program.
The JTIDS/MIDS program was established as a Joint Service Program to
develop and acquire a secure, jam-resistant communications system with
inherent capabilities to support information distribution, relative
navigation, and identification that would support both intra- and
inter-Service information exchanges between tactical command and
control facilities/systems. JCS Memorandum SM-362-75, 2 July 1975,
stipulates the relationship between the Joint Tactical Information
Distribution System/Multifunctional Information Distribution System
(JTIDS/MIDS) and GAMO (now the JINTACCS) Programs. JTIDS/MIDS may
provide either primary or alternate transmission means through which
appropriate tactical data systems are interconnected. The JCS had
directed the GAMO Executive Agent (EA) (SM-575-77, 27 June 1977) to
develop the message standard for the JTIDS/MIDS, which included the
development of a JTIDS Technical Interface Concept (JTIC) and a JTIDS
Technical Interface Design Plan - Test Edition (JTIDP-TE), as well as
the responsibility to plan, schedule, conduct, and evaluate joint
testing of the JTIDP in order to validate its compatibility and
interoperability for the JCS.

1.2.2 JCS and the Services determined that the requirement for
the JINTACCS Program would be extended beyond FY 1985, the year the
program originally was to be completed. JCS Memorandum SM-750-82, 6
December 1982, was issued to ensure that the program responsibilities
would be accomplished. SM-750-82 tasked the Chief of Staff, U.S. Army
as the EA responsible for managing the development and the testing of
joint message standards for the JTIDS/MIDS. In addition, this
memorandum expanded the previous tasking by including a requirement to
develop the Link 16 Interface Management Plan to show phased
implementation of the Link 16 Interface for systems/platforms that are
specified by the Services in the JTIC.

1.2.3 On 5 July 1984, the Deputy Secretary of Defense signed

Department of Defense (DoD) Directive 5154.28, which established the
Joint Tactical Command, Control and Communications Agency (JTC3A)
under the Defense Communication Agency (DCA), and assigned to it
responsibility for the development and maintenance of a joint
architecture, interface standards, and interface definitions for
tactical/mobile C3 systems. All program activities and resources of
the Joint Tactical Communication Office and the JINTACCS Program were
transferred to the JTC3A. JTC3A on 1 February 1992 was changed to the
Joint Information Engineering Organization (JIEO) in the Defense
Information System Agency (DISA), formerly DCA.

1.2.4 The Joint Multi-TADIL Standards Working Group (JMSWG),

chaired by JIEO, directed on 10 May 1996, that the JTIDP-TE, a test
document, be superseded by MIL-STD-6016, Tactical Digital Information
Link (TADIL) J Message Standard, in order to establish an approved
operational baseline.
 1.3 DOCUMENT STRUCTURE

1.3.1 Sections and Appendices

1.3.1.1 MIL-STD 6016C consists of six sections and 24

appendices.

1.3.1.2 The following subparagraphs describe the content of the

sections of this document:

a. Section 1 addresses the purpose, scope, and structure of this

document and its relationship with other documents.

b. Section 2 defines the applicable documents for the current

issue of this document and their order of precedence.

c. Section 3 describes and defines the conventions used within

this document, provides the parameters defined in this document,
provides definitions of the terminology used, defines the operator
alert categories used within this document, and summarizes the
technical characteristics of the JTIDS/MIDS system.

d. Section 4 defines common requirements referenced by the

appendices.

e. Section 5 defines the detailed requirements for construction

of Link 16 fixed format messages. In six parts, separate from the
main volume, it contains:

(1) Specific J-series word descriptions (Parts 1-3).

(2) Link 16 Transmit tables and the Value and Source Code
Symbols used in the Transmit tables (Part 4).
 (3) Link 16 Receive tables (Part 5). For each Link 16
message, the Receive tables provide the messages uses, how to
discriminate each message use, the transactions involved for each
message use, and the data field processing and display requirements
for each message use.

(4) Link 16 System Implementation (Part 6).

f. Section 6 lists the applicable Interface Change Proposals

(ICPs) that were incorporated into this update of the Standard. It
also contains information of a general or explanatory nature which may
be helpful, but is not mandatory.

1.3.1.3 The major technical functions/subfunctions covered by

this standard are contained within separate appendices. The format
and content of each Appendix is described in Paragraph 1.3.2 of this
section.

1.3.2 MIL-STD-6016 Appendices

1.3.2.1 The following is a list of Appendices contained within

this document along with a brief description of the functions/sub-
functions covered by each Appendix:

a. Appendix A, Functional Area Requirements Specification

(FARS). This appendix is to be developed (TBD).

b. Appendix B, Data Element Dictionary (DED), contains the data

elements used in Link 16.
 c. Appendix C, Precise Participant Location and Identification
(PPLI) And Status, describes the processing required to transmit and
receive the J2.x Precise Participant Location and Identification
(PPLI) messages and J13.x Platform and System Status messages that
convey network participation status, positional, identification and
other operational information to support link functions.

d. Appendix D, Surveillance, defines the requirements necessary

to exchange surveillance information with other compatibly equipped
platforms. This Appendix also defines the surveillance data reception
requirements for nonC2 units.

e. Appendix E, Data Update Request, defines the processing

requirements for transmission, reception, and responses to the J7.1
Data Update Request message.

f. Appendix F, Threat Warning, defines the transmission and

reception requirements necessary to exchange the J15.0 Threat Warning
message.

g. Appendix G, Electronic Warfare Information Exchange, defines

the transmission and reception requirements necessary to support
electronic warfare functions.

h. Appendix H, Amplification, provides the transmission and

reception requirements to provide C2 JUs the ability to report
amplification data (via J6.0 Amplification messages) relating to
tracks being reported on the Surveillance Network Participation Group
(NPG).

i. Appendix I, Engagement Coordination, defines the transmission

and reception requirements to provide C2 JUs the ability to coordinate
engagements for the most efficient use of resources.
 j. Appendix J, Terminal Free Text, provides the protocols
necessary to exchange non J-Series Terminal Free Text messages, e.g.,
J-Voice.

k. Appendix K, Weapons Coordination and Management, provides the

transmission and reception requirements for C2 JUs to command other
units, report weapons and engagement status, and indicate pairings.

l. Appendix L, Coordination of Aircraft Control, provides the

transmission and reception requirements necessary for C2 JUs to
digitally establish control over assigned aircraft or aircraft
requesting control, for C2 JUs to digitally transfer control of
aircraft to other C2 units, and for C2 JUs to digitally terminate
control of aircraft.

m. Appendix M, Control, provides the transmission and reception

requirements to perform the near real-time direction of weapons
systems and supporting platforms for the accomplishment of assigned
missions.

n. Appendix N, Formatted Text, provides the transmission and

reception requirements necessary for text messages (via J28.2(0) Text
messages).

o. Appendix O, Antisubmarine Warfare, provides the transmission

and reception requirements necessary to report lines-of-bearing
(ambiguous and resolved) and/or range to a detected submarine or
surface vessel derived from Antisubmarine Warfare (ASW) sensors.

p. Appendix P, Track Management, defines the transmission and

reception requirements for a C2 JU to accomplish track management. The
track management function contains the following sub-functions:

(1) Data Exchange and Management.

 (2) Track Identification.

(3) Status Changes.

(4) Special Codes.

(5) Change Data Order (CDO) Authority.

q. Appendix Q, Imagery, is to be developed (TBD).

r. Appendix R, Pointers, provides the transmission and reception

requirements necessary for C2 JUs to select a geographic position and
transmit it to one or more other C2 JUs with up to 20 characters of
associated text. It also provides the protocols required for C2 JUs to
receive geographical positions and text from other C2 JUs.

s. Appendix S, Airfield and Weather, provides the transmission

and reception requirements to report airfield status (via J13.0
Airfield Status messages) and weather conditions over targets (via
J17.0 Weather Over Target messages).

t. Appendix T, Association, provides the transmission and

reception requirements to associate entities and to exchange Desired
Mean Point of Impact (DMPIs) (via J7.7 Association messages).

u. Appendix U, Resolution of Dual Designations and Target/Track

Correlation/Decorrelation, provides the transmission and reception
requirements for C2 JUs to resolve air and surface track dual
designations. This appendix also provides the transmission and
reception requirements for controlling units to report target/track
correlations to units under their control.
 v. Appendix V, Network Management, contains the process for
designing the network through terminal initialization parameters and
coordination with other network participants to ensure the whole
system is working effectively.

w. Appendix W, Minimum Implementation, identifies the minimum

data exchange requirements which must be implemented by Service/Agency
systems participating on the Link 16 Interface.

x. Appendix Y, Interface Change Proposal (ICP) Repository,

maintained separately by DISA, contains a database of active ICPs and
ICPs that have been issued a Configuration Control Board Decision
(CCBD). The ICP Repository is located on the TADIL Data System (TDS)
web site and therefore is not contained in this document.

y. Appendix Z, National/Service Proprietary Annexes, is reserved

for national/service proprietary messages. The annexes contain the
transmit/receive tables for these messages. This appendix and the
annexes are TBD.

1.3.2.2 Unless otherwise specified within the Appendix, each

Appendix function is divided into five specific transactions which
make up a Transaction Package consisting of:

a. Preparation transaction. The preparation portion of the

transaction package describes what capability the host system shall
provide the operator to allow them to initiate or modify messages on
the link.

b. Transmission transaction. The transmission portion of the

transaction package describes the requirements placed on the host
system to transmit messages on the link either after an operator
action to enable the message for transmission, automatically based on
outside stimuli, or automatically as required for receipt compliance.
 c. Reception transaction. The reception portion of the
transaction package describes the processing the host system is
required to perform to receive a Link 16 message from the terminal and
the required display or alert processing required to notify the
operator of the receipt of the message.

d. Purging/Deletion transaction. The purging/deletion

transaction portion of the transaction package describes the
processing required to remove a record from the host system database
either via a timeout (purging) or by deleting the entry in the
database.

e. Special Considerations. Transactions or rules not covered by

Paragraph 1.3.2.2.a through Paragraph 1.3.2.2.d.

1.3.2.3 Each transaction will occur as a result of a stimulus,

which may generally be considered as:

a. The receipt of a particular type of message that meets the

discriminators for a specific message use from the link.

b. A system event - usually associated with the establishment or

detection of a particular condition within the host system. This
event may occur automatically (e.g., a timeout), by operator action,
or by a combination of the two.

c. A periodic event - an entirely automatic event that examines

data in the database, and on the basis of certain specified
parameters, decides whether information is eligible for transmission.

d. From another transaction - by this means a number of

transactions can be linked to define one complete set of processing
requirements within a platform for a required activity.
 1.3.2.4 Following the list of stimuli for a transaction is a
list of constraints applicable to the transaction. Constraints may
cause alerts, which are defined in Section 3.5, Operator Alerts.
Constraints may also cause the processing to stop, or may stimulate
other transactions. Constraints that are marked “None” shall be
interpreted as meaning that no constraint shall be placed on the
processing of this transaction.

1.3.2.5 Where appropriate, each function/sub-function of the

Appendix contains Reporting Responsibility (R2) rules which augment the
requirements set forth by Section 4.11.3, Reporting Responsibility
Rules for Air, Surface, and Land Tracks, Section 4.11.4, Reporting
Responsibility Rules for Points, Lines, and Areas, Section 4.11.5,
Reporting Responsibility Rules for Ballistic Missile Tracks, Section
4.11.6, Reporting Responsibility Rules for Electronic Warfare
Surveillance, and Section 4.11.7, Reporting Responsibility Rules for
Subsurface Tracks.

1.3.2.6 The processing aspects of a transaction specify the

actions to be taken as a result of the stimulus and detail the
conditions for the transmission of messages. The requirements for
providing information to an operator and any operator input
capabilities are also identified.

1.3.2.7 Any database processing requirements specific for each

function/sub-function are also described in the transaction.

1.3.2.8 In addition to the sets of transactions described above

for each sub-function, each Appendix also includes an introductory
section that outlines the operational capability provided by the
function, and how the requirements are met by the various sub-
functions. This section is for overall understanding of the
function/sub-function. The introduction section also provides
definitions of terms and concepts that will be addressed within the
Appendix. The information contained in the introduction section is
required in order to understand and process each function/sub-function
contained in the Appendix.
 1.4 POLICY

1.4.1 Applicable statements of policy are contained in DoD

directives and correspondence. Essentially, interoperability,
compatibility, and commonality in the degree necessary to provide for
flexible, effective, and economical operation of tactical forces will
be achieved. Commonality, compatibility, and interoperability are
objectives. Interoperability in joint tactical operations is
absolutely essential for operational effectiveness.
 1.5 CONCEPT

1.5.1 MIL-STD-6016 complies with basic DoD policies and has been
developed in consonance with the following concepts:

a. Tactical command and control, and communications systems

standards are developed only for systems and equipment applicable to
functional areas in which the need for interoperability and
compatibility has been validated as essential by the JCS.

b. These standards apply to operational and future tactical

systems and use system characteristics previously approved for Service
use where such characteristics meet the joint requirements.

c. This document establishes certain standards and criteria for

message formats and transmission characteristics that will be used in
the design and/or procurement of systems and equipment. Additionally,
these standards will be used in computer program development and when
new system designs are implemented within existing systems.

d. An interface between tactical systems should exploit the

maximum capability of sensors and processors to provide precise
information exchange in support of tactical operations.

e. Message format standards and information exchange criteria in

those standards are designed to support established doctrine and known
requirements. They will be responsive to revision, as indicated.
 1.6 DEVELOPMENT OF STANDARDS

1.6.1 MIL-STD-6016 was developed based on information produced

by and coordinated with the U.S. Army (USA), U.S. Navy (USN), U.S. Air
Force (USAF), U.S. Marine Corps (USMC), the National Security Agency
(NSA), and the Defense Intelligence Agency (DIA), as documented in the
JTIC dated April 1982 (amended and approved by the JCS on 5 May 1983).
Additionally, coordination was accomplished with international
standards under guidance of the JCS.

1.6.2 Within the Joint Staff, standardization is accomplished by

the Director for Command, Control and Communications Systems, J-6.
Through the Director, J-6, the Defense Information Systems Agency
(DISA) develops standards and criteria, as necessary.

1.6.3 During the development of tactical standards, it is

necessary to consider the relationship to other national standards and
international standards. DISA develops these standards in
consultation with other activities of the DoD, including DISA, DIA,
and NSA/CSS, to ensure compatibility between U.S. tactical and
strategic systems and equipment. Formal coordination is obtained,
where necessary, through actions of the JCS. International
applications are considered during the development and revision of
standards through consultation with various national and international
agencies. North Atlantic Treaty Organization (NATO) STANAG 5516 and
STANAG 5616 reflect these standards for Link 16.
 1.7 APPLICATION OF STANDARDS

1.7.1 MIL-STD-6016 is used by the Services, commands, and

applicable DoD Agencies in developing and acquiring new systems,
computer programs, and equipment as required, and for updating
existing systems for use on the Link 16 Interface. The application of
the minimum requirements for information exchange on Link 16 is
provided in the following paragraphs:

a. Application of Requirements: The mandatory requirements

contained in Appendix A, Functional Area Requirements Specification,
apply to all systems, existing and future, that elect to exchange
information via Link 16. The applicability of these requirements is
directed toward digital data exchange in a joint environment where
systems of two or more Services/DoD Agencies are involved. These
requirements should be used as guidelines for internal service or
system data links when no external interface exists.

b. Exceptions to Minimum Requirements: Exceptions to the

minimum requirements for information exchange will be considered and
approved or denied on a case-by-case basis by DISA.

c. Requests for exceptions will be submitted by the individual

Service/DoD Agency to DISA for approval or resolution. Action on the
request will be in accordance with Chairman Joint Chiefs of Staff
Instruction (CJCSI) 6610.01, TADIL Standardization Policy and
Procedures and with JIEO Plan 3200, Department of Defense Information
Technology (IT) Standards Management Plan. The request will identify
the specific tactical data system, the items for which the exception
is requested, and the reason for requesting the exception.

d. The channel for submission of requests for exceptions is the

same as that for submitting recommended changes to these standards.
 1.8 CONFIGURATION CONTROL

1.8.1 MIL-STD-6016 will be maintained as a baseline for

configuration management of the Link 16 Interface in accordance with
the DISA Terms of Reference (TOR) for the Tactical Data Link (TDL)
Configuration Control Board (CCB).

1.8.2 The Director, DISA is responsible for configuration

management of MIL-STD-6016. S/A requests for changes must be
prepared, submitted, and processed in accordance with the TOR.
Approved changes will be promulgated to all participants by DISA. The
application or waiver of a standard to a specific equipment or system
is the responsibility of the Secretary of Defense.