1  General Information

1.1  Administrative Information

Title: / Update MIL-STD-6016 Reference and Implementation / No: / TBD / Version / A
Submitter: / Steve Weiss / Phone: / (505) 853-0998
E-mail: / / Organization: / DMOC
Product: / SISO-STD-002

1.2  Version History

Version / Date / Description
2006 / 2006-07-10 / Initial release?

1.3  References

Doc. No. / Title
MIL-STD-6016D / Tactical Digital Information Link (TADIL) J Message Standard

1.4  Additional Analysts Contact Information

Name / Organization / E-mail / Phone

2  Analysis

2.1  Summary Description

Some simulation systems currently limit all their outgoing Link 16 J messages to three J-words.

This is causing interoperability problems with systems that comply with MIL-STD-6016C and later standards.

SISO-STD-002 needs to require compliance with MIL-STD-6016C and later standards.

2.2  Problem Analysis

Some simulation systems currently limit all their outgoing Link 16 messages to three J-words.

The current SISO-STD-002 standard references MIL-STD-6016B which does not specifically prohibit limiting all Link 16 messages to three J-words.

MIL-STD-6016C and later versions specifically prohibits arbitrarily limiting the number of J-words to a 3 or 6 word structure as stated in paragraph 3.1.2.1.b.(1):

“When building a message for transmission, the host shall include as many available words as allowed by the initialized Network Participation Group (NPG) packing limit and shall not be arbitrarily limited to a 3 or 6 word structure.”

Simulation systems exclusively outputting three word Link 16 messages are causing interoperability problems with real world and simulation systems which are compliant with the MIL-STD-6016C and later standards.

2.3  Impact Analysis

Unless SISO-STD-002 is changed to require compliance with MIL-STD-6016C and later standards, some simulation systems will continue to limit all Link 16 messages to three J-words, thereby perpetuating interoperability problems with real world systems and simulation systems which are compliant with the MIL-STD-6016C and later standards.

Since MIL-STD-6016E exists, and MIL-STD-6016D is widely fielded, SISO-STD-002 should reference at least MIL-STD-6016D.

3  Proposed Changes

3.1  Update reference

Update MIL-STD-6016 reference in Section 2 to MIL-STD-6016D.

3.2  Add wording to require compliance with the MIL-STD-6016D or later standards

Append the following sentence to end of paragraph 5.1.1.2:

“Systems shall output Link 16 messages IAW MIL-STD-6016D or later standards, and shall not arbitrarily limit all Link 16 messages to three J-words.”

3.3  Add wording to require Packing Structure appropriate to message length

In paragraph 5.1.1.5, add a colon after the first “shall”, make the rest of the paragraph the first of two bullets, and add the following as the second bullet:

“Set the Packing Structure, located in the Time Slot Type field of the Link 16 message header, appropriate to the message length IAW MIL-STD-6016D or later standards (e.g. Do not send a J13.2, Air Platform and System Status message, for an aircraft with stores aboard, which is longer that three J-words, in a Standard Double Pulse (STD DP) Packing Structure, which is limited to three J-words.”

Page 1 of 2

SISO Problem / Change Request (PCR) form – REV 5