AFM 55-11                                                                                                                                                        20 MAY 1968

CHAPTER 3

POLICY AND PROCEDURES

1. GENERAL. ESTABLISHMENT AND MAINTENANCE OF THE AFOREP ARE BASED UPON THE FOLLOWING POLICIES AND PRINCIPLES

    A. CONTINUOUS EFFORTS ARE MACE TO STANDARDIZE AND COORDINATE INFORMATION REQUIREMENTS TO REDUCE REPORTING AND COMMUNICATIONS LOADS WHENEVER POSSIBLE. DURING PERIODS OF INCREASED TENSION AND READINESS, EVERY PRACTICAL EFFORT MUST BE MADE TO REDUCE REPORTING REQUIREMENTS, FREQUENCY AND KINDS CF INFORMATION ETC., TO ENSURE, THAT ESSENTIAL INFORMATION IS TRANSMITTED AND RECEIVED ON A TIMELY BASIS. INDIVIDUAL AFOREP REPORT INSTRUCTIONS PROVIDE THIS CONTROL. COMMANDS CAN CONTRIBUTE TO THIS EFFORT BY ESTABLISHING PROCEDURES FOR THE PERIODIC REVIEW OF ALL OPERATIONAL REPORTS. NEW REQUIREMENTS FOR INFORMATIONAL DATA MUST BE CLOSELY SCRUTINIZED TO DETERMINE HOW THIS REQUIRE­MENT CAN BE INCORPORATED INTO THE EXISTING SYSTEM, WITH MINIMUM PROLIFERATION OF REPORTING.

    B. ESSENTIAL OPERATIONAL INFORMATION REQUIREMENTS OF THE CSAF AND SUBORDINATE COMMAND LEVELS WILL BE SUPPORTED. THESE ESSENTIAL REQUIREMENTS WILL NOT BE COMPROMISED OR RESTRICTED, IN THE INTEREST OF STANDARDIZATION WITH OTHER SYSTEMS OR BY AVAILABLE COMMUNICATIONS CAPABILITIES. INFORMATION REQUIREMENTS ARE SUBJECT TO CONTINUOUS EVAL­UATION FOR ESSENTIALITY. COMMUNICATIONS CAPABILITIES PROVIDING THE NECESSARY CAPACITY AND RELIABILITY MUST BE PROVIDED.

    C. WHENEVER POSSIBLE REPORTING REQUIREMENTS OF THE AFOREP ARE IDENTICAL WITH THOSE OF THE JCS AND THE SPECIFIED AND UNIFIED COMMANDERS. TO BE EFFECTIVE, REPORTING SYSTEMS ESTABLISHED BY MAJOR COMMANDS MUST PROMULGATE THIS PRINCIPLE TO ENSURE OPERATIONAL REPORTING EFFICIENCY, TIMELINESS AND ACCURACY. PROVISIONS OF THE AFOREP ARE NOT INTENDED TO ABROGATE MAJOR COMMAND SYSTEMS EMPLOYING ADVANCED AUTOMATED, ONLINE PROCEDURES. IT IS EXPECTED THAT FUTURE CHANGES AND UPDATING OF MAJOR COMMAND SYSTEMS WILL INCORPORATE THIS CHANGE AS REQUIRED ON A PHASED ORDERLY BASIS. THE STANDARDIZATION OF REPORT NAMES, FORMATS, DATA ELEMENTS AND CODES IS ESSENTIAL FOR MAXIMUM INTERFACE OF THE JOINT REPORTING SYSTEM, AIR FORCE REPORTING SYSTEM, AND COMMAND SYSTEMS.

    D. MAJOR COMMANDS ARE RESPONSIBLE TO SUBMIT OR CAUSE SUBMISSION OF OPERATIONAL REPORTS. CERTAIN AFOREP REPORTS MAY BE GENERATED FROM MAJOR COMMAND DATA BASES, WHILE OTHERS NAT, AS PROVIDED IN THIS MANUAL AND AS DIRECTED BY THE COMMAND, BE SUBMITTED BY AN ALTERNATE FACILITY OR BY OPERATING UNITS SIMULTANEOUSLY TO ALL ADDRESSEES. CHANNELS AND PROCEDURES FOR SUBMISSION OF AFOREP AND MAJOR COMMAND REPORTS MUST BE CONSIDERED TO ENSURE RELIABILITY AND SURVIVABILITY OF THE REPORTING SYSTEMS.

    E. JOINT OPERATIONAL REPORT (JOPREP) TYPES ARE INCLUDED IN THE AFOREP FOR USE AS DIRECTED BY THE OSAF AND AS A MEANS TO INFORM AND TRAIN AIR FORCE REPORTS PERSONNEL FOR PARTICIPATION IN JOINT OPERATIONS. WHEN DIRECTED BY THIS HEADQUARTERS THESE REPORTS WILL BE SUBMITTED AS INDICATED IN THIS MANUAL AND AS INDICATED IN THE IMPLEMENTING DIRECTIVE. WHEN IMPLEMENTATION IS DIRECTED BY THE JOS THROUGH SPECIFIED/UNIFIED COMMAND CHANNELS, AIR FORCE UNITS WILL FOLLOW THE APPROPRIATE JOINT DIRECTIVE (COORDINATED BY THIS HEADQUARTERS) RATHER THAN THIS MANUAL. MINOR DIFFERENCES DUE TO OPERATING CONDITIONS AND REQUIREMENTS FOR INFORMATION1 MAY BE EXPERIENCED BETWEEN THE AFOREP AND JOINT IMPLEMENTING DIRECTIVES.

2. MANNING AND TRAINING OF REPORTS PERSONNEL.

    A. THE AVAILABILITY OF TRAINED REPORTS PERSONNEL IS VITAL TO OPERATIONAL REPORTING. ADEQUATE PERSONNEL MUST BE PROVIDED AND TRAINED IN ADVANCE OF THE REQUIREMENT TO INITIATE AND SUSTAIN EFFECTIVE REPORTING. AIR FORCE ORGANIZATIONS, PRIOR TO DEPLOYMENT OR EMPLOYMENT IN JOINT OPERATIONS, SUPPORT A NORMAL REPORTING LOAD. IT IS MUCH LESS AND DIFFERENT THAN THAT REQUIRED IN CERTAIN CONTINGENCY OPERATIONS, OR WHEN ACCESS TO ADVANCE, AUTOMATED, ONLINE COMMUNICATIONS ARE NOT AVAILABLE.

    B. IT IS ANTICIPATED THAT TOTAL REQUIREMENTS FOR TRAINED REPORTS PERSONNEL WILL VARY ACCORDING TO COMMAND LEVEL AND MISSION REQUIREMENTS. MAJOR COMMANDS AND SUBORDINATE COMMANDERS WILL EVALUATE REPORTS PERSONNEL MANNING IN ACCORDANCE WITH ASSIGNED MISSIONS AND COMMITMENTS AND INITIATE NECESSARY ACTION TO PROVIDE THE REQUIRED SPACE(S). DURING CERTAIN NORMAL OPERATIONS AND IN ACCORDANCE WITH COMMAND LEVEL AND MISSION REQUIREMENTS, IT MAY BE DESIRABLE TO COMBINE REPORT PERSONNEL MANNING REQUIREMENTS WITH THE NORMAL OR AUGMENTED CONTROLLER TEAMS.

3. EQUIPPING OF REPORT SECTION/CENTER.

A. TIMELY AND ACCURATE OPERATIONAL REPORTING REQUIRES PROPER EQUIPMENT AND FACILITIES IMMEDIATELY AVAILABLE TO THE REPORT SECTION. THESE REQUIREMENTS INCLUDE ADEQUATE COMMUNICATIONS LINES/CHANNELS, TELETYPE AND CARD TRANSCEIVER (AUTODIN) INPUT/OUTPUT DEVICES, MESSAGE COMPOSER, NORMAL AND SECURE TELEPHONE EQUIPMENT AND PUNCH CARD PREPARATION EQUIPMENT. OTHER CONSIDERATIONS INCLUDE A SECURE ADEQUATE WORKSPACE AREA, ENCODING AND DECODING DOCUMENTS, ADMINISTRATIVE EQUIPMENT AND SUPPLIES. REPORT CENTERS SUPPORTED BY ADP COMPUTER EQUIPMENT REQUIRE IMMEDIATE ACCESS TO A COMPUTER COMMUNICATION CONSOLE OR INPUT/OUTPUT DEVICE FOR ACCESS TO OR UPDATE OF THE DATA BASE. MAJOR COMMANDS AND COMMANDERS WILL EVALUATE REPORT CENTER EQUIPMENT AND FACILITY REQUIREMENTS TO ENSURE ADEQUACY, AND INITIATE ACTION TO PROVIDE AND IMPROVE THESE VITAL ASSETS AS REQUIRED.

B. THE LARGE AND INCREASING USE OF AUTOMATED REPORTS CAUSES EQUIPMENT AND FACILITIES FOR THE REPORT SECTION TO BECOME VASTLY MORE IMPORTANT. IT IS NATIONAL AND AIR FORCE POLICY TO MAKE MORE AND BETTER USE OF DATA AUTOMATION EQUIPMENT AND COMPUTERS. AT CERTAIN COMMAND LEVELS NOT AUTHORIZED SEPARATE COMMAND AND CONTROL COMPUTER EQUIPMENT, IT IS APPROPRIATE FOR COMMAND POST REPORT SECTIONS TO COORDINATE AND ARRANGE A LEVEL OF COMPUTER SUPPORT FROM DATA SERVICES OR OTHER AGENCIES TO IMPROVE OPERATIONAL REPORTING. DATA PROCESSING INSTALLATIONS ARE AUTHORIZED TO PROVIDE SUPPORT (PUNCH CARDS, PRINTOUTS, ETC.) UNDER DATA SYSTEM DESIGNATOR (DSD) AOIIT.

4. DEPLOYMENT PLANNING.

A. COMMANDERS WILL ENSURE THAT UNIT TASK FORCE DEPLOYMENT PLANS INCLUDE COMMAND POST AND REPORT SECTION PERSONNEL, EQUIPMENT AND SUPPLY REQUIREMENTS. THESE VITAL ASSETS MUST BE GIVEN PRIORITY ATTENTION AND NORMALLY SHOULD DEPLOY IN THE FIRST OR ADVANCED ELEMENTS OF THE UNIT DEPLOYMENT. DEPLOYMENT WILL BE IN ACCORDANCE WITH THE ASSIGNED MISSION AND APPROVED PLANS. COMMANDERS WILL EN-SURE THAT AIR-TRANSPORTABLE MOBILITY KITS OF EQUIPMENT, DOCUMENTS AND SUPPLIES CONSISTENT WITH THE MISSION AND PLANS ARE MAINTAINED READY FOR DEPLOYMENT AND USE IN THE FORWARD AREA/S.

    B. IN CERTAIN AREAS/LOCATIONS AND CONTINGENCIES THE DEPLOYMENT OF COMMAND AND CONTROL COMPUTER EQUIPMENT MAY BE REQUIRED. MAJOR COMMANDS WILL REVIEW CONTINGENCY COMMITMENTS AND PLANS TO EVALUATE THIS FOR POSSIBLE REQUIREMENT, INITIATE ACTION AND DEVELOP PLANS TO PROVIDE THE COMPUTER EQUIPMENT AND FACILITY SUPPORT. REQUIREMENTS AND PLANS FOR THE DEPLOYMENT OF COMMAND AND CONTROL COMPUTERS TO SUPPORT CONTINGENCY OPERATIONS WILL BE SUBMITTED TO THIS HEADQUARTERS FOR APPROVAL, PRIOR TO IMPLEMENTATION.

5. OPERATING IN A DEGRADED ENVIRONMENT.

    A. CONSIDERATION MUST BE GIVEN TO THE FOLLOWING FACTORS WHEN THE ALTERNATE COMMAND POST/OPERATIONS CENTER IS MANNED AND OPERATIONAL -

        (1) TYPE OF COMMUNICATIONS AVAILABLE.

        (2) AVAILABILITY OF AUTOMATED DATA PROCESSING EQUIPMENT

        (3) AVAILABILITY OF QUALIFIED REPORTS PERSONNEL.

    B. DEFICIENCY IN ANY OF THE ABOVE WILL REQUIRE ADJUSTMENTS TO BE MADE. REPORTS TRANSMITTED VIA PUNCHED CARD OR MAGNETIC TAPE MAY HAVE TO BE RETRANSMITTED BY TELETYPE TO AN ALTERNATE COMMAND POST/OPERATIONS CENTER THAT DOES NOT HAVE EQUIPMENT TO RECEIVE INFORMATION IN THIS FORM, NOR PROCESS IT IN THIS FORM. WHEN THE VOLUME OF REPORTS TO BE TRANSMITTED BECOMES GREATER THAN THE CAPACITY OF AVAILABLE COMMUNICATIONS OR REPORTS PERSONNEL, A JUDGEMENT MUST BE MADE ON THE RELATIVE IMPORTANCE OF INFORMATION/DATA TO BE ACCUMULATED AND TRANSMITTED. THE VARIANCE IN SITUATIONS WILL AFFECT THE RELATIVE IMPORTANCE OF INFORMATION WITHIN A REPORT, OR A REPORT WITHIN ONE OF THE CATEGORIES LISTED BELOW. THE FOLLOWING CATEGORIES OF INFORMATION HAVE BEEN ESTABLISHED TO PROVIDE A GUIDE IN DETERMINING THE RELATIVE IMPORTANCE OF REPORTS UNDER MOST SITUATIONS -

        (1) CATEGORY I - INFORMATION VITAL TO THE SECURITY OF THE UNITED STATES OR IT'S FORCES THIS INCLUDES ATTACK WARNING, ACTUAL ATTACK INFORMATION, OR INFORMATION THAT MAY INDICATE THAT AN ATTACK IS POSSIBLE. REPORTS IN THIS CATEGORY WOULD BE - CIRVIS, NUCLEAR/BIOLOGICAL/CHEMICAL ATTACK, OPREP-3 EVENT/INCIDENT.

        (2) CATEGORY II INFORMATION NECESSARY FOR - IMMEDIATE OPERATIONAL DECISIONS, MONITORING OF AIRCRAFT OR UNIT MOVEMENTS, MEASUREMENT OF THE SUCCESS OF MISSIONS, CORRECTIVE MEASURES, OR INCIDENTS/CONDITIONS AFFECTING THE COMBAT CAPABILITY OF AIR FORCE UNITS. REPORTS IN THIS CATEGORY WOULD BE

        (1) CATEGORY III - INFORMATION USEFUL IN MONITORING THE STATUS OF FORCES, IN PLANNING, AND IN ANALYSIS. REPORTS IN THIS CATEGORY WOULD BE -

    C. THE CSAF AND MAJOR COMMANDS MAY SUSPEND THE SUBMISSION OF SELECTED REPORTS WHEN COMMUNICATIONS ARE DEGRADED, OR THE PREPARATION OF RELATIVELY MINOR REPORTS IMPEDES THE PREPARATION OF MORE URGENT REPORTS. CONSIDERATION SHOULD BE GIVEN TO THE DISCONTINUANCE OF SELECTED REPORTS WITHIN CATEGORY III INITIALLY. AS THE RELATIVE IMPORTANCE OF REPORTS MAY FLUCTUATE DUE TO OPERATIONAL CONSIDERATIONS, EACH REPORT SHOULD BE EVALUATED INDIVIDUALLY BEFORE DISCONTINUING ANY REPORT. NOTIFICATION TO ALL NORMAL RECIPIENTS WILL BE MADE WHEN DISCONTINUING ANY REPORT.

6. INDIVIDUAL REPORT INSTRUCTIONS. INFORMATION AND REQUIREMENTS CONCERNING INDIVIDUAL REPORTS ARE PREPARED IN A STANDARD ARRANGEMENT AS INDICATED BELOW. ENTRIES ARE SELECTED TO COVER ALL ASPECTS NECESSARY FOR UNDERSTANDING AND SUBMISSION OF REPORTS. STANDARDIZED ARRANGEMENT OR FORMATTING OF REPORTING INSTRUCTIONS ENHANCES REFERENCE, USE AND THE TRAINING OF COMMAND POST/CENTER REPORTS PER­SONNEL THROUGHOUT THE AIR FORCE. COMMANDS PUBLISHING SUP­PLEMENTS TO THIS MANUAL OR SEPARATE MANUALS ARE ENCOURAGED TO INDICATE INDIVIDUAL REPORT REQUIREMENTS IN THE STANDARD FORMAT CONTAINED IN THIS MANUAL.

REPORT TITLE OR NAME

SHORT TITLE 
(ACRONYM FORMED FROM FULL TITLE OR NAME
OF THE REPORT)

6. USE OF FLAGWORDS.

    A. A STANDARD FLAGWORD WILL BE USED THROUGHOUT THE AIR FORCE AND THE WWMCCS TO IDENTIFY COMMAND POST TO COMMAND POST ELECTRICALLY TRANSMITTED MESSAGES AND OPERATIONAL REPORTS. THE FLAGWORD INDICATES TO COMMUNICATION TERMINAL PERSONNEL THAT THE MESSAGE OR REPORT WAS ORIGINATED BY A COMMAND POST/REPORTS CENTER AND IT IS TO BE ROUTED TO THE RECEIVING COMMAND POST/REPORTS CENTER DIRECT RATHER THAN THROUGH NORMAL DIRECTOR OF ADMINISTRATIVE SERVICES CHANNELS. THE FLAGWORD, ITS MEANING AND RESULTANT MESSAGE ROUTING, IS INTENDED TO EXPEDITE MOVEMENT OF COMMAND POST MESSAGES AND REPORTS BETWEEN COMMAND POSTS AND COMMUNICATIONS TERMINALS -- IT DOES NOT INDICATE A PRECEDENCE FOR TRANSMISSION BETWEEN COMMUNICATIONS TERMINALS OR WITHIN COMMUNICATIONS CHANNELS. JOPREPJIFFY TRAFFIC FROM/TO A COMMAND POST/REPORTS CENTER WILL BE PROCESSED IN ACCORDANCE WITH CHAPTER II.

    B. THE STANDARD UNCLASSIFIED FLAGWORD TO BE USED WITHIN THE AIR FORCE AND THE WWMCCS IS JOPREP JIFFY. THE FLAGWORD WILL BE ENTERED BY ORIGINATORS IN THE FIRST LINE OF THE MESSAGE OR REPORT TEXT AS ILLUSTRATED LATER IN THIS CHAPTER1 ON AUTOMATED REPORTS JOPREP JIFFY WILL BE ENTERED ON THE SECURITY CLASSIFICATION CARD IN THE SPACE ALOTTED FOR SPECIAL HANDLING INSTRUCTIONS.

7. DISTRIBUTION OF COMMAND DIRECTIVES. THE AIR FORCE COMMAND POST OPERATIONAL REPORTS REQUIREMENTS SECTION MAINTAINS A QUICK REFERENCE, WORKING LIBRARY OF MAJOR COMMAND OPERATIONAL REPORTING DIRECTIVES. ONE COPY OF THE MAJOR COMMAND PUBLICATIONS AND ALL CHANGES THERETO SUPPLEMENTING, SUPPORTING OR IMPLEMENTING THE PROVISIONS OF THIS MANUAL OR JOPREP PUBLICATIONS WILL BE FORWARDED TO THIS HEADQUARTERS, MARKED FOR AFXOXSD.

8. PRODUCTION. AUTHORITY IS GRANTED TO EXTRACT ANY PORTION OF THIS MANUAL FOR LOCAL REPRODUCTION AS INDICATED HEREIN OR AS DETERMINED BY THE MAJOR COMMAND. THE PROVISIONS OF AFR 205-1 APPLY.

9. SECURITY CLASSIFICATION OF REPORT. IT IS THE REPORT­ING COMMANDER'S RESPONSIBILITY TO ASSIGN THE APPROPRIATE SECURITY CLASSIFICATION IN ACCORDANCE WITH AFR 205-1 TO EACH INDIVIDUAL REPORT. IN ACCORDANCE WITH DOD DIRECTIVE 5200.1, OVERCLASSIFICATION AND UNNECESSARY CLASSIFICATION MUST BE SCRUPUOSLY AVOIDED. WHERE APPROPRIATE, SEPARATE CLASSIFICATIONS WILL BE ASSIGNED TO EACH PARAGRAPH OF A REPORT SO THAT RECIPIENTS CAN QUOTE PARTS OF A REPORT

WITHOUT OVERCLASSIFYING THEM. IN COMBAT OR COMBAT-RELATED OPERATIONS, MESSAGES WHICH CONTAIN SECRET OR CONFIDENTIAL INFORMATION MAY BE TRANSMITTED IN THE CLEAR OVER ANY WIRE CIRCUIT OR RADIO CHANNEL WHEN TIME CANNOT BE SPARED FOR ENCRYPTION AND THE INFORMATION CANNOT BE ACTED UPON BY THE ENEMY IN TIME TO INFLUENCE THE SITUATION IN QUESTION. SUCH MESSAGES WILL BE MARKED (SEND IN THE CLEAR) OVER THE SIGNATURE OF THE COMMANDER OR HIS AUTHORIZED REPRESENTATIVES (REF PARAGRAPH 7-78(4), AFR 205-1 AND PARAGRAPH 326, ACP 1210). IN GENERAL, REPORTS WILL BE CLASSIFIED IN ACCORDANCE WITH THE FOLLOWING GUIDELINES

    A. IF A REPORT INDICATES THE COMBAT CAPABILITY, OR LACK OF COMBAT CAPABILITY OF ONE OR MORE SQUADRONS, IT WILL BE CLASSIFIED A MINIMUM OF CONFIDENTIAL.

    B. IF A REPORT CONTAINS COMBAT LOSS, DAMAGE OR RESULTS OF A COMBAT MISSION, IT WILL BE CLASSIFIED A MINIMUM OF CONFIDENTIAL.

    C. IF A REPORT CONTAINS A COMPLETE INVENTORY OF NUCLEAR WEAPONS OF ONE/OR MORE DETACHMENTS/SQUADRONS, IT WILL BE CLASSIFIED SECRET - FORMERLY RESTRICTED DATA.

    D. IF A REPORT CONTAINS INFORMATION ON THE DEPLOYMENT OF COMBAT AIRCRAFT, UNITS, OR TROOPS, IT WILL BE CLASSIFIED IN THE REPORT THE SAME AS IT IS IN THE PLAN, BUT IN NO INSTANCE LESS THAN CONFIDENTIAL.

    E. UNIT NAMES AND LOCATIONS CLASSIFIED IN A PLAN WILL HAVE THE SAME CLASSIFICATION IN A REPORT.

10. IDENTIFICATION OF REPORTS. THE AFOREP IS DESIGNED TO ALLOW TRANSMISSION OF REPORTS BY MAIL, ELECTRICAL RECORD COMMUNICATIONS (TELETYPE, AUTODIN) OR VOICE. TO ENSURE EXPEDITIOUS HANDLING OF DATA, EACH COMMUNICATION CONTAINING OPERATIONAL REPORT DATA MUST BE IDENTIFIED. THE FOLLOWING IDENTIFIERS WILL BE USED TO CONSTRUCT THE FIRST LINE OF THE REPORT, THE REPORT IDENTIFICATION LINE. EACH IDENTIFIER WILL BE SEPARATED BY A VIRGULE (/).

    A. SECURITY CLASSIFICATION. THE FIRST ENTRY ON THE REPORT IDENTIFICATION LINE WILL INDICATE THE OVERALL CLASSIFICATION OF THE REPORT.

    B. FLAGWORD/S. ALL REPORTS PRESCRIBED BY THIS MANUAL WILL BE IDENTIFIED BY THE FLAGWORD JOPREP JIFFY. A 'FOR' ELEMENT IS NOT REQUIRED IN THE MESSAGE HEADING AS THE FLAGWORD IDENTIFIES THE RECIPIENT.

    C. REPORTING AGENCY. USE ABBREVIATION TO INDICATE THE COMMAND, ORGANIZATION OR UNIT SUBMITTING THE REPORT.

    D. SHORT TITLE AND NUMBER. IN ADDITION TO THE FLAG-WORD TO IDENTIFY REPORTS IN THE SYSTEM, THE SHORT TITLE WILL ALWAYS BE USED AS AN IDENTIFIER (REF PAR 5). THE SHORT TITLE WILL BE FOLLOWED BY THE REPORT NUMBER. THIS IS A THREE-DIGIT NUMBER ASSIGNED SEQUENTIALLY BY THE REPORT ORIGINATOR FOR EACH PARTICULAR TYPE OF REPORT. AFTER NUMBER 999 HAS BEEN REACHED, THE REPORT NUMBER WILL START OVER AT 001. VOICE REPORTS ARE NOT NUMBERED.

        (1) EXERCISE REPORTS WILL SHOW THE EXERCISE/ OPERATION NICKNAME IMMEDIATELY PRECEDING THE REPORT SHORT TITLE.

        (2) EXERCISE REPORTS WILL BE NUMBERED INDEPENDENTLY FROM REAL-WORLD REPORTS STARTING OVER AT 001 AT THE START OF EACH EXERCISE.

    E. AS-OF-TIME OR TIME OF OCCURENCE. THE (AS-OF) TIME IS THE CUT-OFF TIME SPECIFIED FOR A GIVEN REPORT. THE TIME OF OCCURENCE IS THE ACTUAL TIME THE EVENT(S) OCCURRED. IN EITHER INSTANCE, TIME WILL BE SHOWN IN ZULU (GMT) TIME PRECEDED BY THE DATE, AND FOLLOWED BY MONTH (ABBREVIATED) AND YEAR.

11. REPORT IDENTIFICATION EXAMPLES. EXAMPLES OF HOW TO IDENTIFY REPORTS

    A. ELECTRICALLY TRANSMITTED RECORD COMMUNICATIONS-FIRST LINE OF MESSAGE (EXAMPLE CLASSIFICATION)

(SECRET/JOPREP JIFFY/TACISITREP 007/15103CZ AUG 67)

    B. ELECTRICALLY TRANSMITTED EXERCISE RECORD COMMUN­ICATIONS - FIRST LINE OF MESSAGE. (EXAMPLE CLASSIFICATION)

(SECRET/JOPREP JIFFY/TAC/EXERCISE HIGH HEELS 67 SITREP 0O1/151030Z AUG 67)

    C. VOICE REPORTS

        (1) ACTUAL REPORT.

(THIS IS JOPREP JIFFY -OPREP-3 FROM ATC AS OF 0430 ZULU)

        (2) EXERCISE REPORT

(THIS IS A JOPREP JIFFY EXERCISE HIGH HEELS 67 OPREP-3 FROM ATC AS OF 0430 ZULU)

12. CORRECTION OF REPORTS. 1F, AFTER A REPORT HAS BEEN SUBMITTED, IT IS DISCOVERED THAT THE REPORT CONTAINED ERRONEOUS DATA, A CORRECTION WILL BE SUBMITTED. ONLY SECTIONS OR LINE NUMBERS TO BE CORRECTED NEED BE SUBMITTED--NOT THE ENTIRE REPORT. THESE CORRECTIONS WILL BE IDENTIFIED IN THE FOLLOWING MANNER ACCORDING TO MEANS OF SUBMISSION

    A. RECORD COMMUNICATIONS. FIRST LINE OF TEXT (EXAMPLE CLASSIFICATION)

(SECRET/JOPREP JIFFYITAC/SlTREP3I9/141400Z NOV 65/ CORRECTION 318.)

(IN THIS EXAMPLE THE NUMBER 319 REPRESENTS THE NEXT NUMBER IN THE SEQUENTIAL NUMBER SYSTEM, NOT THE NUMBER OF THE REPORT BEING CORRECTED. THE NUMBER 318 IDENTIFIES THE ORIGINAL REPORT REQUIRING CORRECTION. THE EXERCISE/OPERATION NICKNAME WILL BE ENTERED WHEN CORRECTING EXERCIS REPORTS).

NOTE - THE CORRECTION DESIGNATION WILL NOT BE USED FOR DAILY REPORTS UPDATED BY EXCEPTION OR FOR AS-REQUIRED REPORTS.

    B. VOICE REPORTS.

(THIS IS A JOPREP JIFFY REPORT FROM TAC. CORRECTION TO OPREP-4 007 AS OF 0430Z IS AS FOLLOWS.)

(THE EXERCISE/OPERATION NICKNAME WILL BE USED WHEN CORRECTING EXERCISE VOICE REPORTS.)

13. FORMAT FOR COMPUTER PROCESSED REPORTS. CERTAIN REPORTS INTENDED FOR DIRECT COMPUTER PROCESSING AND NORMALLY SUBMITTED VIA PUNCHED CARD TRANSCEIVER (AUTODIN) WILL USE CARDS IN THE FOLLOWING SIX BASIC TYPES OF FORMAT-(CERTAIN OLDER REPORTS IN THE AFOREP REQUIRE A SLIGHTLY DIFFERENT FORMAT THAN IS PRESENTED IN THIS PARAGRAPH. IN THE FUTURE WHEN COMPUTER PROGRAMMING MODIFICATIONS ARE COMPLETE ALL AFOREP COMPUTER PROCESSED REPORTS WILL USE THIS STANDARD FORMAT/CARD ARRANGEMENT.) THE FORMAT FOR EACH OF THE FOLLOWING CARD TYPES ARE USED IN THIS MANUAL-

    A. COMMUNICATIONS HEADER CARD. THIS FORMAT IS DEFINED IN JANAP 126, DATED 1 JULY 1964.

    B. CLASSIFICATION, IDENTIFICATION AND HANDLING CARD(S).  THIS CARD (THESE CARDS) SERVE(S) TO CONVENIENTLY CONVEY ANY NEEDED INFORMATION ABOUT THE REPORT TO THE HUMAN OPERATOR.

    C. REPORT HEADER CARD. THIS CARD IDENTIFIES THE REPORT.

    D. REPORT DETAIL CARD(S). THIS CARD TYPE WILL CARRY THE REPORT DETAILS OR DATA IN AS MANY CARDS AS REQUIRED. CERTAIN FIELDS ON THIS CARD TYPE ARE STANDARD FOR ALL REPORTS. OTHER DETAIL OR DATA FIELDS VARY IN SIZE AND ARRANGEMENT AS INDICATED FOR INDIVIDUAL REPORTS IN THIS VOLUME.

    E. REPORT END CARD. THIS CARD PROVIDES ANY TERMINAL IDENTIFYING INFORMATION THAT MAY BE REQUIRED SUCH AS EXERCISE INFORMATION.

    F. END OF TRANSMISSION CARD. THIS FORMAT IS DEFINED IN JANAP 128, DATED 1 JULY 1964.

14. TELETYPE FORMAT FOR PUNCH CARD REPORTS.

    A. PUNCH CARD REPORTING MAY BE REQUIRED FROM LOCATIONS NOT HAVING ACCESS TO CARD TRANSCEIVER OR ACCESS TO AUTODIN CIRCUITS. PUNCH CARD REPORTS MAY BE TRANSMITTED/RECEIVED VIA TELETYPE USING THE PROCEDURES AND EQUIPMENT LISTED IN THIS PARAGRAPH.

    B. THE TELETYPE FORMAT IS IDENTICAL TO THE CARD FORMAT COLUMNS 1-69, ON A ONE-CARD-FOR-ONE-LINE BASIS, WHEN SUBMITTING BY TELETYPE TAPE FOR AUTOMATIC CONVERSION TO PUNCHED CARDS, EXCEPT FOR THE FOLLOWING SPECIAL CONSIDERATIONS-

        (1) THE COMMUNICATIONS HEADER INFORMATION (CORRESPONDING TO COMMUNICATIONS HEADER CARD, REF PARA 13A) WILL BE AS SPECIFIED IN ACP 127 FOR TELETYPE MESSAGES. THE SAME APPLIES TO THE END-OF-MESSAGE INFORMATION (CORRESPONDING TO END OF TRANSMISSION CARD, REF PAR 13F).

        (2) THE TELETYPE REPORT HEADER LINE WILL CONTAIN IN POSITIONS 20-30 THE BLOCK OF DATA CONTAINED IN CARD COLUMNS 70-80 OF THE REPORT HEADER CARD. THIS PERMITS FULLY AUTOMATIC CONVERSION OF A REPORT FROM CARDS TO TELETYPE PAPER TAPE (BY MEANS OF THE IBM 063 CARD CONTROLLED TAPE PUNCH) AND FROM TELETYPE PAPER TAPE TO CARDS (BY MEANS OF THE IBM 047 TAPE-TO-CARD PUNCH).

        (3) THE MAXIMUM NUMBER OF CARDS/LINES IN ANY ONE MESSAGE WILL BE 500 (INCLUDING ALL SIX TYPES OF CARDS/LINES). IN ORDER TO SUBMIT DATA IN EXCESS OF 500 CARDS/LINES, IT IS NECESSARY TO DIVIDE THE DATA INTO SEPARATE REPORTS, EACH LIMITED TO 500 CARDS/LINES. EACH SUCH REPORT WILL CARRY ITS OWN DISTINCT REPORT NUMBER. ADDITIONALLY, IT MUST BE OBSERVED THAT TELETYPE MESSAGES IN EXCESS OF 90 LINES IN LENGTH ARE DIVIDED INTO PARTS OF 90 LINES OR LESS BY THE TELETYPE OPERATOR. SOME REPORTS MAY BE OF SUCH URGENCY THAT THEY MUST BE PROCESSED IMMEDIATELY UPON RECEIPT OF EACH SUCH PART, WITHOUT AWAITING RECEIPT OF ALL PARTS CONSTITUTING A MULTI-PART MESSAGE. SINCE THIS WOULD RESULT IN LOSS OF POSITIVE CONTROL OF THE COMPLETE MESSAGE, SUCH REPORTS MUST BE LIMITED TO A MAXIMUM OF 90 CARDS/LINES INSTEAD OF 500.

15. MANAGEMENT OF RECORDS. RECORD MAINTENANCE IS IN ACCORDANCE WITH AFM 181-4. DISPOSITION IS IN ACCORDANCE WITH AFM 181-5.