CHAPTER 5
TACTICS, TECHNIQUES, AND PROCEDURES (TTPs)
TOPIC: Information Duplication.
DISCUSSION: Several elements of information were duplicated between the Technical Operational Data (TECHOPDAT), the Tactical Operational Data (TACOPDAT), and the Air Tasking Order Confrrmation (ATOCONF) U.S. Message Text Formats (USMTFs). Within the TECHOPDAT and TACOPDAT USMTF message format, the duties set is repeated. Within the TACOPDAT and the TECHOPDAT, significant elements of the "REFUEL" set were duplicated. As used in the Operation DESERT SHIELD AOR, significant radio frequency information was duplicated among all three USMTF message types.
The duplication of information among these messages created a significant, unnecessary workload. During the development of these messages, common information elements had to be checked for correctness. Following publication, the messages, needed to be cross-checked again for potential errors in transmission.
If differences appeared, the user was then faced with the problem of determing which information was correct. Additionally, the ATOCONF contained monthly, weeKly, and daily Special Instructions (SPINs). The SPINs frther duplicated information in the basic message or were used to publish changes to the basic information. The MSGCHANGEREP USMTF message format was not used for this purpose. The CENTAF Director of Operations Staff should assess the current set of operational data and tasking messages to identify what information is duplicated among the various message formats. Following that assessment, which message type shall contain the basic data to be incorporated by reference to other messages should be determined.
LESSON(S): If the same sets of information are contained in multiple message formats, originators of message traffic need to determine which message will be the repository for the information and refer to that message. Do not duplicate the basic information unless the user audience is separate for each of the messages that contain that information.
TOPIC: Technical Operational Data Changes.
DISCUSSION: Revisions and changes to the TECHOPDAT were made effective prior to all interface participants receiving new parameters. During Operation DESERT SHIELD, several different TECHOPDATs or changes to the TECHOPDAT were published. One of the sets used in the TECHOPDAT format is the "EFFECTIVE" set. This set stipulates when the new parameters for the data link will be in effect. Additionally, there is a "CANX" (cancellation) set. This set identifies the TECHOPDAT to be canceled as the new TECHOP- DAT becomes effective.
The implementation of the new TECHOPDAT or changes to the TECHOPDAT in effect were not properly coordinated. Some of the interface participants adopted new parameters or changed parameters before the entire interface had received the change or before all of the interface participants were ready to adopt the new parameters.
In some cases, the interface units thought that the CANX set determined to implement the new parameters. Their reasoning was the "old" parameters were canceled, use the "new" parameters now.
The ICU for a digital data interface must ensure that all of the link participants have received and understood the interface documents prior to implementation of the parameters and instructions contained in them. Complete distribution of these ocuments could take several days. There may be a need to transmit the TECHOPDAT, the TACOPDAT, and any changes to them via several different networks of communication. Each of the addressees must rndicate to the ICU that they have received the document or changes to the document and are prepared to implement the change.
AUTODIN message traffic was exceedingly slow. Some of the interface units received message traffic from 2 to 3 days after it was transmitted. Once the TECHOPDAT or TACOPDAT are transmitted, there needs to be a 3- to 4-day wait prior to shifting to the new parameters. This delay allows sufficient time for the message traffic to be received by the user units. Operations and technical personnel will have an opportunity to review the new information and properly prepare for coordinated implementation.
LESSON(S): The TECHOPDAT, the TACOPDAT, and any interim changes to them have to be distributed to all interface participants before they are implemented. Implementation of these interface documents prior to receipt by all participants reduces the effectiveness of the digital data-link interface.
Table
of Contents
Chapter
4: Interface Control Unit (ICU)
Appendix
A: Glossary of Acronyms and Terms
|
NEWSLETTER
|
| Join the GlobalSecurity.org mailing list |
|
|
|
