OPERATION OR EXERCISE

AUTODIN. However, ship observations use a free format. Refer again to figure 1-12. The message body follows a USMTF GENADMIN message format used for an outgoing Aviation Enroute Weather Forecast (AVWX). We use this as an example only. Consult NAVMETOCCOMINST 3140.1 for complete content and examples of USMTF GENADMIN forecast formats. Passing instructions, such as "PASS TO EMBARKED MOBILE TEAM," may be included following the SSIC. Passing instructions are used only for exceptional cases not covered by the use of office codes. OPERATION OR EXERCISE.—Immediately following the classification line, an optional line is used to indicate that the message concerns a naval or joint exercise, or an actual military operation. The indicator OPER/, used for operations, is followed by the operation code word, the operation plan number, the primary operation sub-plan nickname, and the secondary sub-plan nickname (if used), all set off by slants. MESSAGE ID.—The USMTF message type abbreviation line, beginning with the set identifier MSGID/, is used to identify the message type, such as GENADMIN. It is followed by the message originator’s short title, and optionally by the originators serial number, and the month, all set off by slants. The Message ID set is mandatory. SUBJECT.—The subject line is a mandatory entry beginning with the set identifier SUBJ/, and followed by the subject of the text of the message. REFERENCE.—References, entered following the REF/ set identifier, are optional. References may be any identifiable message, document, correspondence, conference, meeting, or telephone conversation that is pertinent to the message. Each reference cited must be followed by an AMPN/, or amplification data line providing the title of the reference. Figure 1-13 CONFERENCE REF/A/CON/CDR 82ND AB DIV/20SEP98// AMPN/AIRBORNE COMMANDERS CONFERENCE, FT BENNING GA// MEETING REF/A/CON/COMNAVWEPS CTR/02NOV98// AMPN/JOINT ORDNANCE WORKING GROUP MEETING, DAHLGREN VA// DISCUSSION/CONVERSATION (other than by telephone) REF/A/CON/CINCFOR/l1MAR98// AMPN/BETWEEN MAJ SMITH CINCFOR(FCJ3J) AND CDR JONES USACOM(J36)// TELEPHONE REF/A/TEL/COMSPAWARSYSCOM/08DEC98// AMPN/TELCON BETWEEN SPAWAR/LCDR SMITH AND NPMOC/LT JONES// DOCUMENT (publication, instruction, regulation, etc.) REF/A/DOC/JCS J7/15AUG98// AMPN/JCS PUB 1-01, CHAP II, PARA 3.// REF/A/DOC/DOD/14MAR98// AMPN/DIR 5000.1, SUBJECT: MAJOR AND NON-MAJOR DEFENSE ACQUISITION PROGRAMS, PG 3, PARA D3.// LETTER (correspondence, memorandum, E-mail, etc.) REF/A/LTR/COMNAVMETOCCOM N411/09DEC98/ AMPN/TASKING LTR TO NLMOC, SUBJ: TESS EVAL SER N411/123// REF/A/LTR/NLMOD PATUXENT RIVER/11NOV98// AMPN/E-MAIL FROM NLMOC/CAPTSMITH/LT JOHNSON, SUBJ:RAINFALL MEASUREMENTS// VOICE MESSAGE REF/A/VMG/NAVY PC188/151232ZNOV98// AMPN/PIREP RCVD BY NLMOF JACKSONVILLE ON 271.6MHZ// RECORD MESSAGES (Other than MTF formatted messages) REF/A/MSG/JCS J7-JETD/240700ZMAR98/ / AMPN/ALERT ORDER: OPERATION DEAL CARDS (U)// Figure 1-13.—Examples of GENADMIN references. 1-23