Index Manuals JOINT OPERATION PLANNING AND EXECUTION SYSTEM VOLUME II PLANNING FORMATS AND GUIDANCE (1999)
|
|
CJCSM 3122.03A
31 December 1999
JOINT OPERATION PLANNING
AND EXECUTION SYSTEM
VOLUME II
PLANNING FORMATS
AND GUIDANCE
JOINT STAFF
WASHINGTON, D.C. 20318-0400
CHAIRMAN OF THE JOINT
CHIEFS OF STAFF
MANUAL
J-7
CJCSM 3122.03A
DISTRIBUTION: A, B, C, J, and S
31 December 1999
CH 1 6 September 2000
JOINT OPERATION PLANNING AND EXECUTION SYSTEM, VOLUME II
(PLANNING FORMATS AND GUIDANCE)
References: See Enclosure E.
1. Purpose. This manual sets forth administrative instructions and
formats to govern the development of joint operation plans submitted for
review to the Chairman of the Joint Chiefs of Staff (hereafter referred to
as “Chairman”). Unless otherwise indicated, the formats and procedures
in this document are mandatory for the Joint Staff, all combatant
commands, Services, and combat support agencies responsive to the
Chairman of the Joint Chiefs of Staff.
2. Cancellation. CJCSM 3122.03, 1 June 1996, is canceled.
3. Applicability
a. This manual applies to the commanders of combatant commands,
subunified commands, defense combat support agencies, joint task
forces, and their subordinate component commands. It may also be
applied when significant forces of one Service are attached to forces of
another Service or when significant forces of one Service support forces
of another Service.
b. This manual will be followed except when, in the judgment of the
commander, exceptional circumstances dictate otherwise. If conflicts
arise between the contents of this manual and the contents of Service
publications, this manual will take precedence for the activities of joint
forces unless the Chairman of the Joint Chiefs of Staff has provided more
current and specific guidance to the contrary.
c. Commanders of forces operating as part of a multinational (alliance
or coalition) military command should follow multinational procedures
ratified by the United States. For procedures not ratified by the United
States, commanders should follow the multinational command's
procedures where applicable.
CJCSM 3122.03A
31 December 1999
4. Definitions. See Glossary and Joint Publication 1-02, Department of
Defense Dictionary of Military and Associated Terms. In particular, this
version of JOPES, Vol II, introduces the joint definition of “Planned Risk.”
5. Procedures. Enclosures A through D prescribe JOPES operation plan
(OPLAN), operation plan in concept format concept plan (CONPLAN), and
functional plan (hereafter referred to as “FUNCPLAN”) formats and
procedures for their development. The format for OPORDs is in JOPES
Volume I, Enclosure P.
6. Releasability. This manual is approved for limited release. DOD
components (to include the combatant commands) and other Federal
agencies may obtain copies of this manual through controlled Internet
access only (limited to ".mil" and ".gov" users) from the CJCS Directives
home page--http://wwwdtic.mil/doctrine/jel.htm. Joint Staff activities
may access or obtain copies of this manual from the Joint Staff LAN.
7. Summary of Changes. This manual is a significant change to its
predecessor, CJCSM 3122.03, 1 June 1996. Where applicable, as an aid
to completing these formats, reference has been made to applicable
doctrinal publications.
8. Effective Date. This manual is effective upon receipt.
For the Chairman of the Joint Chiefs of Staff:
C. W. FULFORD, JR
Lieutenant General, U.S. Marine Corps
Director, Joint Staff
Enclosures:
A -- Administrative Guidance
B -- Restricted Access Policy
C -- Format and Content of OPLAN
D -- Format and Content of CONPLAN (With and Without a TPFDD)
and FUNCPLANs
E -- References
GL -- Glossary
2
CJCSM 3122.03A
31 December 1999
DISTRIBUTION
Distribution A, B, C, and J plus the following:
Copies
Secretary of State ------------------------------------------------------------------2
Secretary of Defense ------------------------------------------------------------- 30
Director, Central Intelligence Agency ----------------------------------------- 20
Commandant, United States Coast Guard ----------------------------------- 10
Director, US Element NORAD -------------------------------------------------- 10
Director, Federal Emergency Management Agency ------------------------- 20
Director, Joint Warfighting Center -------------------------------------------- 20
President, National Defense University --------------------------------------- 20
Commander, Marine Corps Combat Development Command ------------ 20
Commandant, Naval War College---------------------------------------------- 20
Director, Joint C2 Warfare Center--------------------------------------------- 20
Commandant, Armed Forces Staff College ----------------------------------- 20
Obtain additional copies from the Military Service assigned
administrative support responsibility by DOD Directive 5100.3, 1
November 1988, "Support of the Headquarters of Unified, Specified, and
Subordinate Joint Commands."
By Military Services:
Army:
US Army AG Publication Center
2800 Eastern Boulevard
Baltimore, MD 21220-2898
Air Force:
Air Force Publications Distribution Center
2800 Eastern Boulevard
Baltimore MD 21220-2896
Navy:
CO, Navy Aviation Supply Office
Distribution Division (Code 03443)
5801 Tabor Ave
Philadelphia, PA 19120-5000
Marine Corps: Marine Corps Logistics Base
Albany, GA 31704
Coast Guard: Coast Guard Headquarters, COMDT (G-REP)
2100 2nd Street, SW
Washington, DC 20593-0001
i
CJCSM 3122.03A
31 December 1999
(INTENTIONALLY BLANK)
ii
CJCSM 3122.03A CH 1
6 September 2000
LIST OF EFFECTIVE PAGES
The following is a list of effective pages for CJCSM 3122.03A. Use this
list to verify the currency and completeness of the document. An "O"
indicates a page in the original document.
PAGE
CHANGE
1 thru 2
O
i thru ii
O
iii thru iv
1
v thru xvi
O
A-1 thru A-8
O
A-9 thru A-14
1
A-15 thru A-20
O
B-1 thru B-4
O
C-1 thru C-656
O
D-1 thru D-2
O
E-1 thru E-2
O
GL-1 thru GL-10
O
GL-11 thru GL-54
1
iii
CJCSM 3122.03A
31 December 1999
TABLE OF CONTENTS
Page
ENCLOSURE A - ADMINISTRATIVE GUIDANCE
Purpose
A-1
General
A-1
Identification of Plans and Orders
A-1
Format and Content of OPLANs, CONPLANs (with and without
TPFDD), and OPORDs
A-3
Use of References
A-5
Organization of PLANs
A-5
Administrative Instructions
A-6
Information Security Markings
A-8
Distribution of OPLANs, CONPLANs, and FUNCPLANs…………A-15
Release of OPLAN Information
A-18
Conflicting Guidance
A-19
ENCLOSURE B - RESTRICTED ACCESS POLICY
Purpose
B-1
General Procedures
B-1
Security
B-1
Capabilities of the Restricted Access System
B-1
Responsibilities
B-2
ENCLOSURE C - FORMAT AND CONTENT OF OPLAN
(NOTE: The Manual Appendix designators listed below correspond
to Annex formats for the plan. See page C-25 for the plan table of
contents.)
Purpose
C-1
Format and Content
C-1
Changes and Related Documents
C-1
Planning Guidance - Basic Plan and
CINC's Strategic Concept
C-29
APPENDIX A
PLANNING GUIDANCE, ANNEX A - TASK ORGANIZATION
C-41
Planning Guidance for Appendix 1 to Annex A
Time-Phased Force and Deployment List
C-45
Planning Guidance for Appendix 2 to Annex A
Shortfall Identification
C-47
Planning Guidance for Appendix 3 to Annex A
Force Module Identification
C-49
Planning Guidance for Appendix 4 to Annex A
Deterrent Options
C-51
Planning Guidance for Tab A to Appendix 4 to Annex A
Deterrent Options Layout
C-53
vii
CJCSM 3122.03A
31 December 1999
APPENDIX B
PLANNING GUIDANCE, ANNEX B - INTELLIGENCE
C-55
Planning Guidance for Appendix 1 to Annex B
Priority Information Requirements
C-67
Planning Guidance for Appendix 2 to Annex B
Signals Intelligence
C-69
Planning Guidance Tab A to Appendix 2 to Annex B
Communications Intelligence Collection Requirements
C-73
Planning Guidance Tab B to Appendix 2 to Annex B
Operational Electronic Intelligence Collection
C-77
Planning Guidance for Appendix 3 to Annex B
Counterintelligence
C-79
Planning Guidance Tab A to Appendix 3 to Annex B
Counterintelligence Target List
C-83
Planning Guidance Tab B to Appendix 3 to Annex B
Multidiscipline Counterintelligence Threat Report
C-85
Planning Guidance Tab C to Appendix 3 to Annex B
Designation of Theater CI Executive Agency
C-87
Planning Guidance Tab D to Appendix 3 to Annex B
Umbrella CI Force Protection Source Operation
Proposal
C-89
Planning Guidance for Appendix 4 to Annex B
Targeting
C-91
Planning Guidance Tab A to Appendix 4 to Annex B
Target List (Conventional)
C-97
Planning Guidance Tab B to Appendix 4 to Annex B
Target List (N0-Strike)
C-99
Planning Guidance Tab C to Appendix 4 to Annex B
Target List (Restricted)
C-101
Planning Guidance for Appendix 5 to Annex B
Human-Resource Intelligence
C-103
Planning Guidance Tab A to Appendix 5 to Annex B
HUMINT Operations Cell (HOC)
C-107
Planning Guidance Tab B to Appendix 5 to Annex B
EPW/Civilian Detainees
C-109
Planning Guidance for Appendix 6 to Annex B
Intelligence Support to IO
C-111
Planning Guidance for Appendix 7 to Annex B
Imagery Intelligence
C-115
Planning Guidance for Appendix 8 to Annex B
Measurement and Signature Intelligence
C-119
Planning Guidance for Appendix 9 to Annex B
Captured Enemy Equipment
C-123
viii
CJCSM 3122.03A
31 December 1999
Planning Guidance Tab A to Appendix 9 to Annex B
Specific Prioritized Intelligence Collection
Requirements
C-129
Planning Guidance Tab B to Appendix 9 to Annex B
Equipment Released for Operational Purposes
C-131
Planning Guidance for Appendix 10 to Annex B
National Intelligence Support Team
C-133
APPENDIX C
PLANNING GUIDANCE, ANNEX C - OPERATIONS
C-135
Planning Guidance for Appendix 1 to Annex C
Nuclear Operations
C-143
Planning Guidance Tab A to Appendix 1 to Annex C
Target List
C-151
Planning Guidance for Appendix 2 to Annex C
Nuclear, Biological, and Chemical Defense Operations;
Riot Control Agents and Herbicides
C-153
Planning Guidance for Appendix 3 to Annex C
Information Operations
C-159
Planning Guidance for Tab A to Appendix 3 to Annex C
Military Deception
C-167
Planning Guidance for Tab B to Appendix 3 to Annex C
Electronic Warfare
C-191
Planning Guidance for Tab C to Appendix 3 to Annex C
Operations Security
C-197
Planning Guidance for Tab D to Appendix 3 to Annex C
Psychological Operations
C-203
Planning Guidance for Tab E to Appendix 3 to Annex C
Physical Attack/Destruction
C-213
Planning Guidance for Tab F to Appendix 3 to Annex C
Computer Network Attack
C-217
Planning Guidance for Tab G to Appendix 3 to Annex C
Defensive Information Operations
C-225
Planning Guidance for Appendix 4 to Annex C
Special Operations
C-235
Planning Guidance for Appendix 5 to Annex C
Personnel Recovery (PR) Operations
C-243
Planning Guidance for Appendix 6 to Annex C
Rules of Engagement (ROE)
C-251
Planning Guidance for Appendix 7 to Annex C
Reconnaissance
C-253
Planning Guidance for Appendix 8 to Annex C
Air Base Operability
C-259
Planning Guidance for Appendix 9 to Annex C
Combat Camera
C-263
ix
CJCSM 3122.03A
31 December 1999
Planning Guidance Tab A to Appendix 9 to Annex C
COMCAM Customer Support Requirements
C-271
Planning Guidance for Appendix 10 to Annex C
Non Combatant Evacuation
C-275
Planning Guidance for Appendix 11 to Annex C
Escape and Evasion Operations
C-281
Planning Guidance for Appendix 12 to Annex C
Counterattack
C-285
Planning Guidance for Appendix 13 to Annex C
Explosive Ordnance Disposal
C-289
Planning Guidance for Tab A to Appendix 13 to Annex C
Forces List
C-293
Planning Guidance for Appendix 14 to Annex C
Amphibious Operations
C-295
Planning Guidance for Appendix 15 to Annex C
Force Protection
C-299
Planning Guidance Tab A to Appendix 15 to Annex C
Combating Terrorism
C-303
Planning Guidance Tab B to Appendix 15 to Annex C
Physical Security
C-307
Planning Guidance Tab C to Appendix 15 to Annex C
Base Defense
C-311
Planning Guidance for Appendix 16 to Annex C
Critical Infrastructure Protection
C-313
APPENDIX D
PLANNING GUIDANCE, ANNEX D - LOGISTICS
C-317
Planning Guidance for Appendix 1 to Annex D
Petroleum, Oils, and Lubricants Supply
C-329
Planning Guidance Tab A to Appendix 1 to Annex D
Estimate of POL Support Requirements
C-333
Planning Guidance for Appendix 2 to Annex D
Water Supply
C-335
Planning Guidance for Appendix 3 to Annex D
Mortuary Affairs
C-339
Planning Guidance for Appendix 4 to Annex D
Sustainability Analysis
C-345
Planning Guidance for Appendix 5 to Annex D
Mobility and Transportation
C-349
Planning Guidance Tab A to Appendix 5 to Annex D
En Route Support Requirements
C-357
Planning Guidance Tab B to Appendix 5 to Annex D
Reception, Staging, Onward Movement, and
Integration (RSOI)
C-363
Planning Guidance Tab C to Appendix 5 to Annex D
Primary and Alternate Ports
C-365
x
CJCSM 3122.03A
31 December 1999
Planning Guidance for Appendix 6 to Annex D
Civil Engineering Support Plan
C-369
Planning Guidance Tab A to Appendix 1 to Annex D
Suggested Construction Standards for Military
Construction and Civil Engineering Support of
Joint Operations
C-377
Planning Guidance for Appendix 7 to Annex D
Nonnuclear Ammunition
C-379
Planning Guidance Tab A to Appendix 1 to Annex D
Munitions Matrix
C-383
Planning Guidance for Appendix 8 to Annex D
Logistics Automation
C-387
APPENDIX E
PLANNING GUIDANCE, ANNEX E - PERSONNEL
C-393
Planning Guidance for Appendix 1 to Annex E
Enemy Prisoners of War, Civilian Internees,
and other Detained Persons
C-399
Planning Guidance for Appendix 2 to Annex E
Processing of Formerly Captured, Missing,
or Detained US Personnel
C-403
Planning Guidance for Appendix 3 to Annex E
Finance and Disbursing
C-407
Planning Guidance for Appendix 4 to Annex E
Legal
C-411
Planning Guidance for Appendix 5 to Annex E
Military Postal Services
C-413
Planning Guidance Tab A to Appendix 5 to Annex E
Aerial Mail Terminals
C-417
Planning Guidance Tab B to Appendix 5 to Annex E
Military Post Offices
C-419
Planning Guidance for Appendix 6 to Annex E
Chaplain Activities
C-421
Planning Guidance Tab A to Appendix 6 to Annex E
Inter-Service Chaplain Support
C-427
Planning Guidance Tab B to Appendix 6 to Annex E
Host-Nation Religious Support
C-435
Planning Guidance for Tab C to Appendix 6 to Annex E
Commander-Staff Chaplain Relationships
C-443
APPENDIX F
PLANNING GUIDANCE, ANNEX F - PUBLIC AFFAIRS
C-445
Planning Guidance for Appendix 1 to Annex F
Personnel Requirements for JIBs and SUB-JIBs
C-453
xi
CJCSM 3122.03A
31 December 1999
Planning Guidance for Appendix 2 to Annex F
Equipment and Support Requirements for JIBs
and SUB-JIBs
C-455
Planning Guidance for Appendix 3 to Annex F
General Ground Rules for the Media
C-457
Planning Guidance for Appendix 4 to Annex F
DoD National Media Pool
C-459
APPENDIX G
PLANNING GUIDANCE, ANNEX G - CIVIL AFFAIRS
C-461
APPENDIX H
PLANNING GUIDANCE, ANNEX H - METEOROLOGICAL
AND OCEANOGRAPHIC OPERATIONS
C-469
APPENDIX J
PLANNING GUIDANCE, ANNEX J - COMMAND
RELATIONSHIPS
C-475
Planning Guidance for Appendix 1 to Annex J
Command Relationships Diagram
C-481
APPENDIX K
PLANNING GUIDANCE, ANNEX K - COMMAND, CONTROL,
COMMUNICATION, AND COMPUTER SYSTEMS
C-483
Planning Guidance for Appendix 1 to Annex K
Information Assurance (IA)
C-489
Planning Guidance Tab A to Appendix 1 to Annex K
Information Security (INFOSEC)
C-497
Planning Guidance for Appendix 2 to Annex K
Command, Control, Communications and
Computer Planning
C-499
Planning Guidance for Appendix 3 to Annex K
Satellite Communications Planning
C-515
Planning Guidance Tab A to Appendix 3 to Annex K
UHF SATCOM Network List
C-519
Planning Guidance Tab B to Appendix 3 to Annex K
SHF SATCOM Network List
C-521
Planning Guidance Tab C to Appendix 3 to Annex K
EHF SATCOM Network List
C-523
Planning Guidance Tab D to Appendix 3 to Annex K
Commercial SATCOM Network List
C-525
Planning Guidance for Appendix 4 to Annex K
Defense Courier Service
C-527
Planning Guidance for Appendix 5 to Annex K
Foreign Data Exchanges
C-529
Planning Guidance for Appendix 6 to Annex K
xii
CJCSM 3122.03A
31 December 1999
Frequency Spectrum Planning
C-531
Planning Guidance Tab A to Appendix 6 to Annex K
Electromagnetic Interference (EMI) Reporting
C-537
Planning Guidance Tab B to Appendix 6 to Annex K
JTF JCEOI Concept
C-541
Planning Guidance Tab C to Appendix 6 to Annex K
Spectrum Use Plan
C-545
Planning Guidance for Appendix 7 to Annex K
JTF C4 Deployment Checklist
C-547
APPENDIX L
PLANNING GUIDANCE, ANNEX L - ENVIRONMENTAL
CONSIDERATIONS
C-555
Planning Guidance for Appendix 1 to Annex L
Environmental Assessments
C-561
Planning Guidance for Appendix 2 to Annex L
Environmental Assessment Exemptions
C-563
Planning Guidance for Appendix 3 to Annex L
Joint Environmental Management Board
C-565
APPENDIX M
PLANNING GUIDANCE, ANNEX M - GEOSPATIAL
INFORMATION AND SERVICES (GI&S)
C-567
Planning Guidance for Appendix 1 to Annex M
GEOSPATIAL Information and Services
Requirements List
C-573
Planning Guidance for Appendix 2 to Annex M
GEOSPATIAL Information and Services
Transportation Requirements
C-575
Planning Guidance for Appendix 3 to Annex M
GEOSPATIAL Information and Services
Reports (Optional)
C-577
APPENDIX N
PLANNING GUIDANCE, ANNEX N - SPACE OPERATIONS
C-579
APPENDIX P
PLANNING GUIDANCE, ANNEX P - HOST-NATION
SUPPORT
C-585
Planning Guidance for Appendix 1 to Annex P
List of HNS Agreements
C-587
Planning Guidance for Appendix 2 to Annex P
HNS Reliability
C-589
Planning Guidance for Appendix 3 to Annex P
Presumed HNS
C-591
xiii
CJCSM 3122.03A
31 December 1999
APPENDIX Q
PLANNING GUIDANCE, ANNEX Q - MEDICAL SERVICES
C-593
Planning Guidance for Appendix 1 to Annex Q
Joint Patient Movement System
C-601
Planning Guidance for Appendix 2 to Annex Q
Joint Blood Program
C-605
Planning Guidance for Appendix 3 to Annex Q
Hospitalization
C-607
Planning Guidance for Appendix 4 to Annex Q
Returns to Duty
C-609
Planning Guidance for Appendix 5 to Annex Q
Medical Logistics (Class 8A) System
C-611
Planning Guidance for Appendix 6 to Annex Q
Force Health Protection
C-613
Planning Guidance for Appendix 7 to Annex Q
Medical Command, Control, Communications
and Computers
C-617
Planning Guidance for Appendix 8 to Annex Q
Host-Nation Medical Support
C-619
Planning Guidance for Appendix 9 to Annex Q
Medical Sustainability Assessment
C-621
Planning Guidance for Appendix 10 to Annex Q
Medical Intelligence Support to Military Operations
C-623
Planning Guidance for Tab A to Appendix 10 to Annex Q
Disease Threat by Geographic Area and Country
C-627
Planning Guidance for Appendix 11 to Annex Q
Medical Planning Responsibilities and Task
Identification
C-629
APPENDIX R
PLANNING GUIDANCE, ANNEX R - REPORTS (Classified;
not included in JOPES, Vol II; Table of Contents
placeholder only (Part of CJCSI CONPLAN 0300/0400
series)
C-631
APPENDIX S
PLANNING GUIDANCE, ANNEX S - SPECIAL TECHNICAL
OPERATIONS (To be provided under separate cover)
C-633
APPENDIX T
PLANNING GUIDANCE, ANNEX T - CONSEQUENCE
MANAGEMENT (CM)
C-635
APPENDIX U
PLANNING GUIDANCE, ANNEX U - NOTIONAL CP
DECISION GUIDE (Classified; not included in JOPES,
xiv
CJCSM 3122.03A
31 December 1999
Vol II; Table of Contents placeholder only (Part of CJCSI
CONPLAN 0300/0400 series))
C-643
APPENDIX V
PLANNING GUIDANCE, ANNEX V - INTERAGENCY
COORDINATION
C-645
Planning Guidance for Appendix 1 to Annex V
Humanitarian
C-647
Planning Guidance for Appendix 2 to Annex V
Economic
C-653
Planning Guidance for Appendix 3 to Annex V
Political
C-655
APPENDIX X
PLANNING GUIDANCE, ANNEX X - EXECUTION
CHECKLIST
C-657
APPENDIX Z
ANNEX Z - DISTRIBUTION
C-659
ENCLOSURE D - FORMAT AND CONTENT OF CONPLAN (With
and Without a TPFDD) AND FUNCPLANS
Purpose
D-1
CONPLAN
D-1
CONPLAN with TPFDD
D-1
FUNCPLAN
D-1
Substantive Guidance
D-2
ENCLOSURE E - REFERENCES
E-1
GLOSSARY
Part I - Abbreviations and Acronyms
GL-1
Part II - Terms and Definitions
GL-11
NOTE: The letters I, O, W, and Y are intentionally omitted as appendix
designations. I and O are not authorized. W and Y may be used, if
required.
xv
CJCSM 3122.03A
31 December 1999
(INTENTIONALLY BLANK)
xvi
CJCSM 3122.03A
31 December 1999
ADMINISTRATIVE GUIDANCE
1. Purpose. This enclosure provides administrative instructions for
preparing operation plans, operation plans in concept format
(CONPLANs) with and without Time-Phased Force and Deployment Data
(TPFDD), and FUNCPLANs.
2. General. OPLANs, CONPLANs, and FUNCPLANs prepared by
commanders to fulfill tasks assigned in the Joint Strategic Capabilities
Plan (JSCP), or otherwise directed by the Chairman of the Joint Chiefs of
Staff (hereafter referred to as the Chairman), will conform to the
guidance, standardized formats, and content herein. To facilitate
communications concerning operation planning among military
headquarters, commanders will standardize the format and content of
other appropriate plans according to the instructions contained in this
enclosure.
3. Identification of Plans and Orders. The short title of each plan is
UNCLASSIFIED and denotes the supported commander, the type of plan,
and the Plan Identification Number (PID). The basic PID is a command-
unique four-digit number and a two-digit suffix. As specified by the
JSCP, the suffix represents the fiscal year of the JSCP for which the plan
is written or reprinted; for example, USCINCEUR OPLAN 4999-99. The
supported command assigns a PID for the life of the plan. To the
maximum extent possible, PID changes should be limited to those
dictated by security/ operations security (OPSEC) requirements. All PID
changes must be coordinated with the Joint Staff. The four-digit block
assignments are shown below:
PLAN IDENTIFICATION
RESPONSIBLE
NUMBER BLOCK
COMMAND OR AGENCY
0001 through 0999
CJCS
1000 through 1999
USCINCCENT
2000 through 2999
USCINCJF
3000 through 3399
CINCNORAD
3400 through 3999
USCINCSPACE
4000 through 4999
USCINCEUR
5000 through 5999
USCINCPAC
6000 through 6999
USCINCSO
7000 through 7499
COMFORSCOM
7500 through 7999
USCINCSOC
8000 through 8999
USCINCSTRAT
9000 through 9599
USCINCTRANS
9600 through 9699
Reserved
9700 through 9799
COMDT COGARD
A-1
Enclosure A
CJCSM 3122.03A
31 December 1999
a. The four-digit number in the PID does not change when the OPLAN
is revised or converted into an OPORD. Also, the four-digit number is
not reused when the requirement for the plan is canceled. The two-digit
suffix is assigned to the OPLAN, and is used throughout. This includes
new plans and complete reprints of plans. When an OPLAN is revised in
part or approved for a subsequent period of the JSCP, there is no
requirement to change the suffix throughout the plan. However, changes
and related documents will reference the fiscal year of the JSCP to which
the change or related document applies. (See formats in Model OPLAN,
Enclosure C.)
b. OPORDs prepared by the CINCs to fulfill Chairman requirements
will be assigned PIDs selected from the block of numbers allocated above
when the OPORD is not a conversion of an existing OPLAN. The
UNCLASSIFIED short title will be derived in the manner described in
subparagraph 3a above. Thus, an OPORD prepared by USJFCOM might
be designated USJFCOM OPORD 2000-92. (The two-digit suffix
represents the calendar year or fiscal year in which the order is
published.)
c. Supporting plans are assigned a PID identical to that of the
supported plan. However, when a supporting command or agency
prepares a single OPLAN to support two or more plans of other
commanders, the plan is assigned a PID without regard to the PIDs of the
supported plans. PIDs will be established by using the command-unique
four-digit number, followed by the two-digit fiscal year designation.
d. Use the following procedures to identify all OPLANs, CONPLANs,
FUNCPLANs and OPORDs loaded to the Joint Operation Planning and
Execution System (JOPES) database (DB):
(1) Basic Plan Files. The four-digit PID will be followed by a
numeral in the fifth character of the Plan Identification Field; e.g.,
USCINCPAC 50003. Letters A through P (except I, O, N) are reserved for
deterrent designators. The “5000” identifies the applicable Basic Plan
and the “3” indicates the last fiscal year of the JSCP for which the plan
was written. Show changes to the basic TPFDD in the two-character
change field following the plan number; e.g., 50003-01. Until changes
are made, the change field will reflect double zero.
(2) Multiple TPFDD Files for the Same Plan. Follow the four-digit
PID with a letter designator in the fifth character; (for example,
USCINCPAC 5000T). Letters T through Y (except X) will be used to
designate different options, other than deterrent options within a given
OPLAN. Specific fifth character options include: Nuclear = N and
Exercise = X. Letters Q and S are reserved for medical evacuation
A-2
Enclosure A
CJCSM 3122.03A
31 December 1999
(MEDEVAC), noncombatant evacuation operation (NEO), and other
retrograde TPFDDs respectively. The letter R is reserved for
redeployments. The first character of the change field will show the fiscal
year of the basic plan for which the TPFDD applies. The second
character indicates the number of the change to the TPFDD; e.g.,
“5000A-21” is Change 1 to version A, OPLAN 5000-92.
(3) Nuclear Option TPFDD. The four-digit PID is followed by an
“N” as the fifth character for a nuclear TPFDD which defines special
weapons deployment requirements.
(4) Exercise TPFDD. The four-digit PID is followed by an “X” as the
fifth character.
e. In planning, use code words from the GCCS NICKA System to
preserve the secrecy of intentions. Guidance is in DOD Regulation
5200.1-R.
4. Format and Content of OPLANs, and CONPLANs (With and Without
TPFDD).
a. The arrangement of information in OPLANs, CONPLANs, and
FUNCPLANs will conform to the formats shown in Enclosures C and D as
applicable. All annexes must be included in OPLANs. Paragraph and
subparagraph headings indicated in the model will always appear in
each plan. For other than OPLANs, when information or instructions on
the subject indicated are not required in the plan, that paragraph or
subparagraph will be annotated as “not applicable.1” Further
subdivisions, if required, should conform to the basic system of
paragraphing as illustrated in the models.
b. The formats shown in Enclosure C for plan annexes are
mandatory unless otherwise indicated. The format for the attachments
(appendixes, tabs, etc.) is preferred, but may be altered when
information or instructions must be included for which no provision is
made in the standard format. Additional annexes may be added when
necessary to permit distribution separate from the Basic Plan or when
information must be included where no provision is made in standard
annexes. When included, letter additional annexes consecutively using
the letters “W” and “Y.” If more than two additional annexes are
required, the third will be AA, the fourth will be BB, etc.. Do not use the
letters “I” and “O” as annex designations.
1 Address paragraphs only if applicable to crisis execution.
A-3
Enclosure A
CJCSM 3122.03A
31 December 1999
c. Annexes and other plan elements specified in the models are
assigned designations as listed in the model table of contents. When any
of these elements are not required, the element is annotated as “not
used” in the OPLAN table of contents. The remaining elements will retain
the prescribed designations.
d. As a minimum, include the following as part of a CONPLAN or
FUNCPLAN: Plan Summary, Basic Plan, Annexes A through D, J, K, V
(CJCS approved plans) and Z. The CINC will determine the requirement
for an Annex V in CINC - approved deliberate plans. Other annexes or
attachments will not normally be required. All annexes prepared will
conform to the content and format prescribed for those elements in an
OPLAN and will accompany the CONPLAN when forwarded to the
Chairman for review.
e. Formats shown in the model for tabular presentation of data may
be modified if required for automated preparation. Address TPFDD
submission by separate message as a formal record of transmittal
according to Joint Reporting Structure (JRS) instructions. When the
Chairman's comments make necessary TPFDD revision, incorporate
changes into the OPLAN deployment database networked by the Joint
Staff, J-3, JOPES Network Operations Control Center (JNOCC), within 90
days after the receipt of comments.
f. Supported commanders will allocate blocks of Unit Line Numbers
(ULNs) to their components organized by Service component. Supported
command component commanders will structure ULNs to identify forces
from their Services that are reflected on the supported commander’s
force list and require sourcing. Supported command components will
provide ULNs from their allocation to other Service-related supporting
commands’ counterparts, as needed, to develop additional required
forces (below-the-line, etc) not listed in the supported commander’s force
list. Supporting commands may use fragmentation during the sourcing
process provided the original ULN structure assigned by the supported
command component is retained.
(1) Each supported commander has an additional first character
for ULNs and Force Modules that can be used as desired. This dedicated
first character ULN/FM may be used for deployment of supported
commander headquarters, joint task forces, forces provided from the
Department of Defense or other US national organizations, or forces from
allied nations or coalition partners. ULN/FM identification (ID) first
position assignment list is found in CJCSM 3150.16, JOPESREP.
(2) To achieve maximum simplicity and flexibility for contingency
and exercise TPFDD construction, forces will be entered by Service
A-4
Enclosure A
CJCSM 3122.03A
31 December 1999
components and providing organizations using ULN and force module
assignments.
g. Force module reporting guidance is contained in CJCSM 3150.16,
JOPESREP.
5. Use of References. Standard references may be used instead of
reproducing information and instructions in OPLANs. However,
references used must be documents readily available to users of the
plan, and will be referred to by publication number, title, and current
date.
6. Organization of PLANs. Organize the OPLAN, CONPLAN, and
FUNCPLAN as shown in Enclosures C and D of this manual, subject to
additional information provided below:
a. Letter of Transmittal
(1) The letter of transmittal for strategic concepts or a new plan,
requiring approval by the Chairman, will state these documents are
effective for planning until approved by the Chairman. Upon approval, a
letter of notification of approval will be issued.
(2) When the transmitted plan replaces an existing plan or is a
complete reprint of a plan, the letter of transmittal will include retention
instructions. Upon approval by the Chairman, the letter of notification of
approval will provide disposition instructions for the superseded plan, its
changes, and related documents.
b. Security Instructions and Record of Changes. The security
instructions include the long and short titles of the plan. Complete titles
are usually classified because they associate the OPLAN number with a
planned operation, country, or other geographic area. Short titles are
UNCLASSIFIED and are the normal means of referring to OPLANs in all
forms of communication. The security instructions may be repeated
inside the front cover if desired. If the OPLAN contains classified
intelligence, only personnel appropriately cleared and indoctrinated may
have access to it. It must be marked, controlled, protected, and
processed in accordance with DOD Directive 5200.1R; Director of Central
Intelligence Directive (DCID) 1/7, “Security Controls on the
Dissemination of Intelligence Information”; DCID 1/19, “DCI Security
Policy for Sensitive Compartmented Information (SCI)”; DCID 1/21,
“Physical Security Standards for SCIFs”; DCID 1/14, “Personnel Security
Standards and Procedures Governing Eligibility for Access to SCI”; DCID
1/16, “Security Policy for Uniform Protection of Intelligence Processed in
Automated Information Systems and Networks.”
A-5
Enclosure A
CJCSM 3122.03A
31 December 1999
c. Table of Contents. The OPLAN table of contents must list all
annexes and attachments, including all of those listed in the sample
table of contents. The table of contents must indicate if an annex is not
used or is published separately.
d. Annexes, Appendixes, Tabs, Exhibits, and Maps. The Basic Plan
and each attachment must contain, on its last page, a list of any
included attachments. The Basic Plan should refer to each annex.
Information provided in the Basic Plan is not normally repeated in the
attachments.
e. Distribution List. The distribution list accounts for all copies of the
plan and informs users which headquarters and agencies hold the plan.
Because plans are highly sensitive documents, distribution should be the
minimum essential for planning. Care should be taken to provide the
plan (or appropriate extracts) to all US military command agencies
expected to support the planned operation. OPLANs are distributed
according to paragraph 9 below.
7. Administrative Instructions
a. Number OPLAN pages at the bottom center to indicate the page
order within each element of the plan. Thus, page C-1-A-3 denotes page
3 of Tab A to Appendix 1 to Annex C. Single space text.
b. Each separate element of a plan should bear the date of issue or
revision. Until a plan is revised, all elements should bear the same date
of issue.
c. The Basic Plan and each annex are signed or authenticated by an
appropriate officer. Use full signature blocks. Appendixes, tabs,
exhibits, and maps do not require signature or authentication except
when distributed separately from the Basic Plan. “For” signatures are
acceptable.
d. Paragraph titles are in upper and lower case and underlined (initial
capitals).
e. Subparagraph titles are in upper and lower case and underlined
(initial capitals).
f. All sub-subparagraphs and subtitles should be in upper and lower
case and underlined (initial capitals), except where forces, commands, or
agencies are identified or tasked; these are capitalized and underlined
(SOLID CAPITALS). When a paragraph is subdivided, it must have at
least two subdivisions.
A-6
Enclosure A
CJCSM 3122.03A
31 December 1999
(1) When paragraphs are subdivided, they must be numbered and
lettered as follows:
“1.”, “a.”, “(1)”, “(a)”, “1.”, “a.”, “(1)”, “(a)”.
g. In the text of OPLANs, capitalize place names (SOLID
CAPITALS) and, where necessary for clarity, include the appropriate
position reference according to CJCS Instruction 3900.01.
h. The first time a title or designation not contained in the JOPES
Volume I or II Glossary is used in an element of a plan, the title or
designation must be spelled out and followed immediately by the
approved abbreviation. Within that element of the plan, the abbreviation
alone can be used thereafter. OPLANs may contain glossaries and/or
indexes at the CINC's discretion.
i. To ensure accurate posting, number changes in sequence, and
include a list of substituting pages. Each revised page must have the
date and number of the change annotated in the upper outside margin,
one line below the document classification line. If a change requires
additional pages within an element, number the inserted page or pages
with the preceding original page number and a letter (e.g., A-7A and
A-7B between pages A-7 and A-8). Identify revised passages by a vertical
line in the left margin of the revised page. Pen-and-ink changes are
permissible for minor corrections such as changes to numbers, dates,
single words, and short phrases only. Include pen-and-ink changes and
page change instructions in the letter announcing the change, or attach
them as a separate cover page to the changed page.
j. Nothing in these instructions is intended to limit the use of
machine printouts for OPLANs. Where automated techniques do not
permit compliance with underlining, capitalization, or formatting as
shown in the models, use a clear and consistent system.
k. Signature Blocks. In Enclosure C, FORMAT AND CONTENT OF
OPLAN, an “/s” (for signature) above a “/t” (for typed name) indicates
that a signature is required.
l. References will be identified with the following information in this
order: classification of the reference identification information, reference
designation (if applicable), reference title, reference data, and reference
classification. For example:
(U) Joint Pub 4-02, Doctrine for Health Service Support in Joint
Operations, 26 April 1995 (U)
(U) CJCSI 3110.01C, Joint Strategic Capabilities Plans for Fiscal
Year 98 (JSCP FY98), 1 June 1998 (TS)
A-7
Enclosure A
CJCSM 3122.03A
31 December 1999
(U) Geneva Convention Relative to the Treatment of Prisoners of
War, 12 August 1949 (U)
8. Information Security Markings
a. General. Information security markings in OPLANs must conform
to the requirements of Chapter V, DOD Regulation 5200.1-R; DCID 1/7;
and DCID 1/19, as amplified below.
b. Classification Markings on Plan Elements
(1) Mark front and back covers and the letter of transmittal with
the overall classification of the plan. If applicable, the final paragraph of
the letter of transmittal must state the classification of the letter of
transmittal standing alone (including UNCLASSIFIED if applicable).
(2) Mark the first page of plan elements (for example, Security
Instructions, Record of Changes, Plan Summary, Classification
Guidance, Table of Contents, Basic Plan, and each Annex, Appendix,
Tab, and Exhibit) with the overall classification of that element.
UNCLASSIFIED plan elements must be so marked.
(3) Mark each interior page of the classified plan element with the
highest classification and SCI code word of the material contained on the
page (top and bottom of page). If the page does not contain classified
material, mark it as UNCLASSIFIED.
(4) Center classification markings at the top and bottom of the
page.
c. Control Markings.
(1) Place warning notices, when applicable, on the front and back
covers, the letter of transmittal, first pages of plan elements containing
information subject to the warning notice, and interior pages containing
such information. In the case of Restricted Data and Formerly Restricted
Data, place the primary marking without the caveat on interior pages
containing such information.
(2) Along with the “WARNING NOTICE -- Intelligence Sources or
Methods Involved” marking to be used on information containing certain
foreign intelligence, one or more of the additional markings listed below
may be required when extraordinary circumstances related to the
intelligence source or method require more specific dissemination
restrictions.
(See DOD Instruction 5230.22, DCID 1/7, and DCID 1/19
for additional information on the use of these markings.)
A-8
Enclosure A
CJCSM 3122.03A CH 1
6 September 2000
(a) DISSEMINATION AND EXTRACTION OF INFORMATION
CONTROLLED BY ORIGINATOR.
(b) NOT RELEASABLE TO CONTRACTORS OR
CONSULTANTS.
(c) CAUTION -- PROPRIETARY INFORMATION INVOLVED.
(d) NOT RELEASABLE TO FOREIGN NATIONALS.
(e) RELEASABLE TO.
d. Paragraph and Subparagraph Markings. In addition to the
parenthetical symbols “(TS),” “(S),” “(C),” and “(U)” used in classified plan
elements to indicate the security classification level of paragraphs and
subparagraphs, the following symbols must be used as appropriate to
indicate the paragraph or subparagraph contains information subject to
certain warning notices (see subparagraph 8c above):
(1)
“RD” for “Restricted Data.”
(2)
“FRD” for “Formerly Restricted Data.”
(3)
“ORCON” for “Dissemination and Extraction of Information
Controlled by Originator.” For example, “(S-WNINTEL) (ORCON).”
(4)
“PROPIN” for “Caution--Proprietary Information Involved.”
(5)
“CA” for “controlled access” in accordance with (IAW) CJCSI
3211.01B, “Joint Military Deception.”
(6)
“FP” for focal point information IAW CJCSM 3213.02A, “Joint
Staff Focal Point Communications Systems Procedures Manual.”
e. Protection of Movement Information
(1) Definitions. The following definitions apply to movement of
forces identified in JOPES plans through a TPFDD. These definitions are
necessary to provide guidance on the proper security of plans and
TPFDD data elements.
(a) Movement Data. Movement data consists of those
essential elements of information to schedule lift, obtain transportation
assets, manage movement of forces, and report in-transit visibility of
movements and associated forces (people, equipment, and supplies). As
a minimum, movement data must describe what forces are planned to
A-9
Enclosure A
CJCSM 3122.03A CH 1
6 September 2000
move or actual loads, where the movement segment is planned to
begin/end or actual movement location, and when the movement is
planned to occur or actual time of movement. (NOTE: All three groups
of data must be present to be considered movement data.)
(b) Aggregation. Movement data elements that can be
grouped to show multiple sequential segments of a force movement from
origin to POE, to POD, and to destination are considered to be
aggregated. Additionally, movement data elements for multiple
movements from either POE to POD or POD to destination that reflect a
flow of force movements into or within a supported commander’s AOR
are considered aggregated.
(c) Execution. Execution for a force movement is initiated
when a force is directed to accomplish movement by competent
authority. Subsequent direction by the supported commander to
supporting commanders (lift providers) normally begins the movement
process that includes transportation planning, scheduling of lift, and
movement of forces and transportation assets. Movement begins when
forces depart the origin or POE on a transportation asset.
(2) OPLAN Security. Security for OPLANs falls into two broad
categories, information security and operations security. Information
security addresses the proper classification of deployment plans and
associated data elements while operations security is focused on the
proper protection of unclassified movement data, especially when
aggregated in automated information systems.
(3) Information Security Classification Guidance
(a) General. Information security markings in OPLANs will
conform to the requirements of Chapter V, DOD Regulation 5200.1-R,
Information Security Program; Director of Central Intelligence Directive
(DCID) 1/7, Security Controls in the Dissemination of Intelligence
Information (For Official Use Only); and DCID 1/19, Security Policy
Manual for SCI Control Systems (UNCLASSIFIED), as amplified below.
(b) Classification Markings on Plan Elements. See CJCSM
3122.03A, Joint Operation Planning and Execution System, Volume II,
Planning Formats and Guidance, 8b, page A-8.
(c) Control Markings. See CJCSM 3122.03A, Joint Operation
Planning and Execution System, Volume II, Planning Formats and
Guidance, 8c, page A-8.
A-10
Enclosure A
CJCSM 3122.03A CH 1
6 September 2000
(d) Paragraph and Subparagraph Markings. See CJCSM
3122.03A, Joint Operation Planning and Execution System, Volume II,
Planning Formats and Guidance, 8d, page A-9.
(e) Unit-Maintained Deployment Data. Generic unit data
maintained at the unit level for the purpose of supporting deployment
operations is considered UNCLASSIFIED/FOR OFFICIAL USE ONLY if
not associated with an OPLAN. Unit deployment data in a TPFDD for an
OPLAN is classified in accordance with the supported commander’s
classification guidance.
(f) JOPES OPLAN Data Classification. JOPES data will
normally be at their highest classification during initial deliberate or
time-sensitive planning phases. Each supported command will publish
specific classification guidance before the initiation of any planning
activities against a specific OPLAN ID. This guidance can be published
by message or supplemental TPFDD Instructions.
(g) JOPES TPFDD Data Element Classification. The TPFDD is
classified at the same level as the OPLAN, using the classification
guidance issued by the supported commander. If in doubt, treat TPFDD
information as classified information. Contact the TPFDD validation
authority for clarification of TPFDD information classification if there is
any question on the level of classification.
(h) The following movement data, in singular or aggregated
form, becomes UNCLASSIFIED/FOR OFFICIAL USE ONLY at execution
for the purpose of transportation planning, scheduling, obtaining
transportation assets, managing movements, reporting movement status
and visibility of in-transit cargo/passengers. All other JOPES data
remain classified at the level specified by the supported commander
unless specifically released as UNCLASSIFIED/FOR OFFICIAL USE
ONLY by the supported commander.
Non-JOPES movements are addressed in applicable regulations.
ULN Number (ULN) 1
Unit Identification (UIC)
Unit Type Code (UTC)
Service Codes (SVC)
Non-Baseline Extension (load POCs)
Mission Number (MSN #)
A-11
Enclosure A
CJCSM 3122.03A CH 1
6 September 2000
Point of Departure/Departure Day 2
Point of Arrival/Arrival Day 3
Scheduled and Actual (Arrival and Departure)
Total Short Tons (STONS) - Bulk, Oversize, Outsize
Total Measurement Tons (MTONS)
Total Square Feet (SQ FT)
Transportation Control Number (TCN)
Number of Pieces
Length Width Height
Cargo Category Codes
Hazardous Material (HAZMAT)
Personnel Requiring Transportation (PAX)
Manifest/Nomenclature
Name, SSN, and Grade 4
(i) Actual destination information is normally released at
execution as UNCLASSIFIED/FOR OFFICIAL USE ONLY unless the
supported commander requires a higher classification level to protect
actual destination locations.
1 ULN is comprised of the five-character Force Requirement Number
(FRN) along with the fragmentation and insert codes that are each one
character.
2 Origin (RLD), POE (ALD), POD (LAD), Intermediate Location (ILOC)
3 POE (ALD), POD (EAD/LAD), Intermediate Location (ILOC)
4 Not resident JOPES TPFDD data but collected during the movement
manifesting process.
A-12
Enclosure A
CJCSM 3122.03A CH 1
6 September 2000
(4) A destination location that the supported commander desires
to maintain as classified can be protected by using an alias entry in the
TPFDD or in unclassified DTS AIS and released as UNCLASSIFIED/FOR
OFFICIAL USE ONLY.
(a) The supported commander defines procedures for the use
of alias names and reference to actual destination locations in the
OPLAN/OPORD and coordinates movement of TPFDD forces to alias
destination locations.
(b) Supported commanders can create alias destination
names for use in the TPFDD and movement AIS by contacting the Joint
Staff J33 to register a new GEOLOC as outlined in CJCSM 3150.15,
Standard Specified Geographic Location File Request, or by using an
existing GEOLOC.
(5) Future systems and procedures should allow for the display of
an actual destination and an alias destination that can be passed to
unclassified DTS Automated Information Systems (AIS) as
UNCLASSIFIED/FOR OFFICIAL USE ONLY.
f. Release of OPLAN Information
(1) CJCSI 5714.01A, Release Procedures for Joint Staff and Joint
Papers and Information, provides guidance concerning the release of
OPLAN information.
(2) Conflicts between procedural guidance contained herein and
directives received from international authorities or provisions of any
plan established by international agreement should be resolved by the
supported commander through the CJCS.
(3) If conflicts arise between procedural provisions in this
document and CJCSI 3100.01A, Joint Strategic Planning System, the
Joint Strategic Capabilities Plan (JSCP), Joint Pub 0-2, or the Unified
Command Plan (UCP), the provisions of those documents have
precedence.
g. Operations Security of Movement Data
(1) People and organizations associated with military operations
have a responsibility to protect planning and movement data so that they
do not inadvertently jeopardize execution of a military operation or force
protection for units supporting an operation. Operations security is
focused on the protection of unclassified information to enhance the
commander’s success in a military operation and maximize force
A-13
Enclosure A
CJCSM 3122.03A CH 1
6 September 2000
protection. The following JOPES operations security procedures are
implemented to meet these objectives.
(2) Unclassified movement data are UNCLASSIFIED/FOR
OFFICIAL USE ONLY. Appropriate markings must be displayed to
ensure proper handling. Guidance for handling UNCLASSIFIED/FOR
OFFICIAL USE ONLY data is found in DOD Regulation 5200.1-R.
(3) Lift providers release to commercial carriers only the minimum
unclassified movement data necessary to obtain and schedule
transportation assets, manifest cargo/passengers, and provide for asset
tracking through the carrier’s system.
(4) UNCLASSIFIED/FOR OFFICIAL USE ONLY movement data
must not be displayed in a generally accessible, unclassified medium
without approval from the supported commander. Normally, systems
and data are protected via access controls to ensure only those
authorized have access to movement data.
(5) Aggregated movement data must be protected to a greater
degree than movement data in a nonaggregated format. Aggregated
movement data in DTS AIS must use access controls (e.g., passwords,
voice recognition, or retinal scans.) to limit accessibility to authorized
users IAW DOD Directive 5200.28, Security Requirements for Automated
Information Systems (AIS), 21 March 1988. In addition, defined
technical measures to enhance the security of aggregated movement data
systems should be implemented to the maximum extent practical.
(6) Due diligence requires personnel to use prudent measures to
preclude unauthorized access to movement data. To accomplish
mission-related activities, electronic transmission (voice, data, or
facsimile) of UNCLASSIFIED/FOR OFFICIAL USE ONLY aggregated
movement data should be by approved secure communications systems
whenever practical.
h. Although DTS AIS are protected, they require continuous
upgrades. In the long term, CINCs will include, where appropriate,
protection measures for DTS AIS in their Integrated Priority Lists, Joint
Monthly Readiness Reviews, and Joint Warfighting Capabilities
Assessments. Services will continue to explore emerging protection
technologies to incorporate in service feeder systems and plan to
program resources accordingly.
A-14
Enclosure A
CJCSM 3122.03A
31 December 1999
g. New JOPES Data Elements. Before incorporating new JOPES data
elements into JOPES software, the J-3, Joint Staff, will place the data
element in one of the classification categories: TOP SECRET, SECRET, or
UNCLASSIFIED.
9. Distribution of OPLANs, CONPLANs, and FUNCPLANs. Except as
otherwise provided in subparagraph 9b below, the commander who
prepares an OPLAN determines its distribution. The distribution list is
contained in Annex Z and is required for all plan renditions. The
supported commander determines the requirement for distribution of
supporting plans. Subordinate commanders should distribute copies of
their plans to the Service components of the supported command and to
appropriate components of supporting commands.
a. Separate Distribution of Annexes. A complete OPLAN must
normally be distributed, except when separate distribution of annexes is
required for security reasons. These provisions also apply to COAs in
cases where annexes or other attachments have been prepared.
b. Distribution of the TPFDD. The supported command must notify
the JNOCC (info the Joint Planning and Execution Community [JPEC])
by newsgroup when it is ready to network a TPFDD. The JNOCC must
distribute the TPFDD in coordination with the supported command.
c. Plans Required by the Chairman of the Joint Chiefs of Staff.
OPLANs and CONPLANs required by the Chairman, including changes
thereto, must be submitted to the Secretary, Joint Staff, who will make
distribution to the Services, combatant commands, and Defense
Number of Operation Plans Required by the Joint Staff
for JPEC Review
Supported Command Plans
OPLANs
23
CONPLANs
18
FUNCPLANs
15
Other Plans
15
Supporting Command Plans
15
Table A-1
A-15
Enclosure A
CJCSM 3122.03A
31 December 1999
agencies. Required quantities are in Table A-1. If supporting plans are
requested for review, the number of copies submitted is the same as for
supported command plans. Follow-on minimum distribution by the
Joint Staff is shown in Table A-2.
Distribution of Plans
Functional
Supporting/
OPLANs
CONPLANs
Other Plans
Joint Staff
1 1
1 1
1 1
CSA
9
5
2
CNO
1
1
1
CSAF
1
1
1
CMC
1
1
1
USCG
1
1
1
Defense Agencies 2
6
6
6
OSD
1
1
1
Supporting Commands 3
3
3
3
NAOC
1
0
0
Total
23
18
15
1 CWPD produces 10 copies for the Joint Staff
2 DISA, DLA, NIMA, NSA, DIA, DTRA
3 Supporting Command - TRANSCOM, MSC, MTMC
Table A-2
(1) Plans submitted electronically must conform to the format
specified in this manual. CINCs authorize reproduction of electronically
submitted plans. Reproduction of electronically submitted plans must
be in accordance with Table A-3. Electronic files must be separated by
Plan Identification Number, Annex, Appendix, Tab, Exhibit, and
Attachment under the following naming convention:
1st through 4th Character: Plan Identification Number
5th Character: Annex Letter
6th and 7th Character: Appendix Number
8th Character: Tab Letter
9th Character: Exhibit Number
10th Character: Attachment Number
A-16
Enclosure A
CJCSM 3122.03A
31 December 1999
For example, the filename for Annex C to OPLAN 4999-99 would be
4999c.doc. The filename for Appendix 1 to Annex C to OPLAN 4999-99
would be 4999c01.doc. (Note: Both characters for the appendix must be
entered because there are, on many occasions, more than nine
appendixes to an annex.) The filename for Tab B to Appendix 1 to Annex
C to OPLAN 4999-99 would be 4999c01b.doc.
Reproduction of Plans
Functional
Supporting/
OPLANs
CONPLANs
Other Plans
Joint Staff
17
10
2
CSA
9
4
1
CNO
17
8
2
CSAF
17
8
2
CMC
6
5
2
DIA
2
2
2
DISA
2
2
2
DLA
1
1
1
DTRA
1
1
1
NIMA
1
1
1
NSA
2
1
1
TRANSCOM
3
1
1
MSC
1
1
1
MTMC
1
1
1
NAOC
3
0
0
USCG
3
1
1
OSD
1
1
1
Total
84
44
19
Table A-3
(2) Other plan elements must use the following naming convention
(the double underscore for the cover page, cover letter, and Plan
Summary will ensure they appear in logical order in a file list):
1st through 4th Character: Plan Identification Number
5th through 10th Character:
“__cvr” (for the plan cover page)
5th through 10th Character:
“__ltr” (for the plan cover letter)
5th through 9th Character:
“__ps” (for the Plan Summary)
5th through 10th Character:
“_bplan” (for the Basic Plan)
A-17
Enclosure A
CJCSM 3122.03A
31 December 1999
Examples: 4999-99 Plan Summary would be “4999__ps” (double
underscore); 4999-99 Base Plan would be “4999_bplan” (single
underscore).
d. Multinational Plans. The US Central Registry will distribute North
Atlantic Treaty Organization (NATO) plans to the Services and the Joint
Subregistry. US liaison officers to the military headquarters of
international treaty organizations should request that military plans
forwarded by those headquarters for US review be provided in the
quantity needed. Submit plans of the Inter-American Defense Board
and CINCUNC/CINCCFC for distribution as indicated in subparagraph
9c above for multinational plans.
e. Limits on Distribution
(1) OPLANs and CONPLANs and their related planning materials
must only be released under the provisions of CJCSI 5714.01. The
originator is release authority for all CINC-prepared OPLANs and their
supporting plans. Unless the originator specifically restricts release, the
information may be further disseminated by authorized holders to
agencies (other Defense components, executive branch agencies,
contractors, auditors, and Congress) not on original distribution if the
agencies have a valid need to know and hold the appropriate level of
security clearance, and if the release is within any limitations contained
in such documents. If the authorized holder is uncertain about the
appropriateness of releasing the information to a specific requester,
release approval should be requested from the originator. The
supported commander is the release authority for all TPFDD files;
however, Service component commands may release their own Service's
information. The supported commander may include release guidance
concerning the TPFDD in Annex A.
(2) CINCs may distribute appropriate OPLANs to US elements of
international military headquarters when such elements need the
information and possess facilities to protect the plans from disclosure to
foreign nationals.
(3) Do not distribute current and superseded OPLANs and related
documents prepared by supported, supporting, and subordinate
commanders to joint and Service colleges or Service schools.
(4) The Chief of Naval Operations may distribute to the
Commandant, US Coast Guard, plans employing US Coast Guard forces.
When such distribution is made, the US Coast Guard must be made
aware of the provisions of CJCSI 5714.01.
10. Release of OPLAN Information
A-18
Enclosure A
CJCSM 3122.03A
31 December 1999
a. CJCSI 5714.01 provides guidance concerning the release of JOPES
documents and information. CJCSI 5714.01 does not differentiate
between classified and unclassified JOPES documents and information.
b. Requests for OPLAN information that cannot be satisfied except by
departure from the provisions of the foregoing subparagraphs should be
referred to the Secretary, Joint Staff, who will process the request
according to CJCSI 5714.01.
11. Conflicting Guidance
a. CINCs who are also commanders of multinational commands or
who conduct coordinated planning on a multinational basis must report
to the Chairman any conflicts between the procedural guidance
contained herein and directives received from international authorities or
provisions of any plan established by international agreement.
b. The Chairman, US Section, Canada-United States Military
Cooperation Committee, must report to the Chairman any procedural
conflicts between plans developed by the committee and this guidance.
c. Should procedural conflicts arise between the provisions of this
document and CJCSI 3100.01, Joint Strategic Planning System, the
Joint Strategic Capabilities Plan (JSCP), Joint Pub 0-2, or the Unified
Command Plan (UCP), the provisions of those documents have
precedence. Procedural guidance approved after the publication of this
document that conflicts with provisions herein must be reflected as a
change in the next revision of this document.
A-19
Enclosure A
CJCSM 3122.03A
31 December 1999
(INTENTIONALLY BLANK)
A-20
Enclosure A
CJCSM 3122.03A
31 December 1999
ENCLOSURE B
RESTRICTED ACCESS POLICY
1. Purpose. This enclosure provides policy designed to allow a supported
command to build TPFDDs for OPLANs and CONPLANs using JOPES
ADP in a protected environment by limiting access to the designated
newsgroup and TPFDD.
2. General Procedures. Policy for the development of OPLANs and
CONPLANs (with/without TPFDD) is outlined in JOPES Volume I,
Planning Policy and Procedures. Restricted access administrative
policies designed to provide the level of planning security required by a
supported command are explained in the following paragraphs.
3. Security. A restricted access OPLAN is not necessarily classified
differently from any other plan. The initiator of the plan must assign the
classification. Some of the procedures for initiating and changing access
to a restricted access plan are classified SECRET NOFORN, and should
be protected as such. Obtain guidance for protecting such information
from current security directives. In instances requiring multinational
restricted access planning, supported commands must get permission
from the Chairman, using the applicable action to allow non-US planners
access.
4. Capabilities of the Restricted Access System
a. General Capabilities. Current policy allows the originator of an
OPLAN to limit access of the associated TPFDD by USERID using JOPES
ADP. Restricted access procedures are normally initiated at the Concept
Development Phase of Deliberate Planning before production of the
OPLAN.
b. Types of Restricted Access. There are two methods of employing
restricted access in JOPES ADP. The first restricts access to selected
users at a single, local, JOPES site (Limited Local). The second restricts
access to selected users at designated sites authorized by the plan
initiator (Limited Network). When the JPEC requires access to the
OPLAN, the database is networked to applicable sites for implementation.
The network FM (JNOCC) and TDBM should be granted access to all
restricted network plans.
c. Controlling Access. The most restricted type of restricted access
OPLAN is resident at the host site only. Therefore, the only method of
reviewing the data by other authorized JOPES users is by database select
to the initiator’s site. This requires specific permissions from the
initiator.
B-1
Enclosure B
CJCSM 3122.03A
31 December 1999
5. Responsibilities
a. Key Personnel. The two key personnel involved in the operation of
the restricted access capability are the user who originates the OPLAN
and the JOPES FM at the originator’s site.
b. Originator or Initiator. The originator or initiator is responsible for:
(1) Contacting the local site JOPES FM to ensure the correct
permissions are on file to enable the originator to initiate, change, or
delete a restricted access OPLAN. Each restricted access originator must
be a registered JOPES user and have permissions in the OPLAN
Administration functional category. Once registered, this permission
remains in effect until withdrawn by the originator’s commander.
(2) Contacting the individuals or organizations requiring access to
the restricted access OPLAN. The originator prepares a list of
appropriate USERIDs for entry into the system.
(3) Identifying restricted access PIDs to site FM and providing a
list of USERIDs having access.
c. Functional Management. The JOPES FM at the originator site
must:
(1) Ensure all applicable personnel, such as the plan originator
and the site GCCS System Security Officer, are familiar with the
procedures discussed in this enclosure.
(2) Grant permission to the identified user authorized to initiate a
restricted access OPLAN.
(3) Identify all restricted access OPLANs on the database and the
USERIDs of their originators. Restricted access originators should
include FMs on the access list to the restricted access OPLANs to ensure
adequate space in the host-site database is provided.
(4) Maintain the USERIDs of all personnel authorized to initiate,
change, or delete restricted access OPLANs. The FM can then add,
delete, and review USERIDs of authorized plan initiator users.
(5) Upon initiation of a restricted access OPLAN, either enter the
individual USERIDs or select USERIDs from existing JOPES permissions
file and transfer them in a single transaction to the new OPLAN.
(6) Periodically review the list of USERIDs authorized to initiate,
change, and delete restricted access OPLANs to ensure currency.
B-2
Enclosure B
CJCSM 3122.03A
31 December 1999
(7) Periodically review the database to ensure outdated restricted
access plans have been removed.
d. Status. After C-day/L-hour, the JNOCC will change the status of
the applicable OPLAN from limited to normal to provide general access by
the entire user community. This update must be accomplished quickly
to allow all supporting commanders, agencies, Services, and the Joint
Staff to rapidly familiarize themselves with the plan and provide required
support.
e. Supported Command. The supported command must:
(1) Establish control procedures to restrict the number of
individual users authorized to initiate, change, and delete restricted
access OPLANs.
(2) Ensure the site FM is granted access to all restricted access
OPLANs.
f. Restricted Access Database Deletion. The local restricted access
OPLAN can be deleted only by the plan originator or user site FM. For
network restricted access plans, the JNOCC FM performs the delete
function.
B-3
Enclosure B
CJCSM 3122.03A
31 December 1999
(INTENTIONALLY BLANK)
B-4
Enclosure B
CJCSM 3122.03A
31 December 1999
ENCLOSURE C
FORMAT AND CONTENT OF OPLAN
1. Purpose. This enclosure provides specific guidance for the format and
general content of OPLANs.
2. Format and Content. The model in this enclosure provides the format
of an OPLAN and outlines the information and instructions to be
included in each plan element. For specific doctrine, refer to the
referenced publications in each annex. For convenience in illustrating
format, the model is presented as a hypothetical USCINCEUR OPLAN.
3. Changes and Related Documents. Included in the model OPLAN are
formats illustrating the letters normally published to change or modify
the supported commander’s plan.1 The formats, filed in inverse order,
cover the following situations:
a. Review. A letter containing changes submitted for CJCS review is
transmitted to holders of the OPLAN. (See page C-11.)
b. Approval. A letter notification of CJCS approval notifies holders of
plan of approval actions. Although the format addresses approval of a
change to an OPLAN, it may also be used for notification actions on the
Basic Plan. (See page C-9.)
c. Approval Without Further CJCS Review. A letter change with
CJCS approval applies to situations in which the supported commander
is authorized to publish a change without seeking further CJCS
approval.
(See page C-7.)
d. Approval Without Change. A letter of notification of approval of a
plan for a subsequent fiscal year of the JSCP notifies holders of CJCS
approval of the plan, without change, for a subsequent fiscal year. Such
notification establishes no requirement to change PID suffixes
throughout the plan. (See page C-5.)
1 OPLAN 4999-99 is used throughout the Model OPLAN, indicating an original
OPLAN. Letters of change are for illustration only and contain applicable
OPLAN numbers.
C-1
Enclosure C
CJCSM 3122.03A
31 December 1999
(INTENTIONALLY BLANK)
C-2
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Cover)
CLASSIFICATION
UNITED STATES EUROPEAN COMMAND
28 February 1999
USCINCEUR OPLAN 4999-99 ( )
WARNING NOTICE
COPY _______ OF _______ COPIES
CONTROL NO. __________________
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-3
Enclosure C
CJCSM 3122.03A
31 December 1999
(INTENTIONALLY BLANK)
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-4
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Letter of Notification of CJCS Approval for a New FY)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
SUBJECT: Approval of USCINCEUR OPLAN 4999-99 for FY
( )
SEE DISTRIBUTION
( ) References: a. CJCS 301429Z Nov 88
b. USCINCEUR OPLAN 4999-99, 28 February 1999
1.
( ) Reference a is CJCS approval of Reference b.
2.
( ) Reference b, with Changes 1 through 4 incorporated, fulfills a
requirement established in paragraph
, JSCP FY ___. Reference b is
effective for execution planning and implementation when directed.
3.
( ) This letter must be filed in front of the plan. No other action is
required.
FOR THE COMMANDER IN CHIEF
s/
t/
Major General, USA
Director, J-5
DISTRIBUTION:
_____________
_____________
_____________
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-5
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
(INTENTIONALLY BLANK)
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-6
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Letter Change With CJCS Approval)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
SUBJECT: Change 4 to USCINCEUR OPLAN 4999-99 ( )
SEE DISTRIBUTION
( ) References: a. MCM 91-89, 31 July 1989, “Review of Change 4 to
USCINCEUR OPLAN 4999-99”
b. USCINCEUR OPLAN 4999-99, 28 February 1999
1.
( ) Change 4 to USCINCEUR OPLAN 4999-99 is attached. Change 4
fulfills a requirement established in paragraph
, JSCP FY
_______.
2.
( ) Reference a is CJCS approval of this change. Reference b, with
Changes 1 through 4 incorporated, is effective for execution planning
and implementation when directed.
3.
( ) Page changes are to be made as follows (superseded pages are to
be destroyed in accordance with security regulations).
Remove Pages
Insert Pages
______________
____________
______________
____________
FOR THE COMMANDER IN CHIEF
s/
t/
Major General, USAF
Director, J-5
DISTRIBUTION:
_____________
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-7
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
(INTENTIONALLY BLANK)
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-8
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Letter Notification of CJCS Approval)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
SUBJECT: Approval of Change 3 to USCINCEUR OPLAN 4999-99 ( )
SEE DISTRIBUTION
( ) References: a. MCM 89-89, 22 June 1989, “Review of Change 3 to
USCINCEUR OPLAN 4999-99”
b. Change 3 to USCINCEUR OPLAN 4999-99,
1 April 1989
c. USCINCEUR OPLAN 4999-99, 28 February 1999
1.
( ) Reference a is CJCS approval of reference b. Reference c, with
Changes 1 through 3 incorporated, is effective for execution planning
and implementation when directed.
2.
( ) The supporting plans listed in subparagraph 3e, Plan Summary,
must be modified to incorporate reference b. Changes to supporting
plans must be forwarded to this headquarters for review within 45 days
of the date of this letter.
3.
( ) This letter must be filed in front of the plan.
FOR THE COMMANDER IN CHIEF
s/
t/
Major General, USAF
Director, J-5
DISTRIBUTION:
_____________
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-9
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
(INTENTIONALLY BLANK)
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-10
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Letter Change for CJCS Review)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
SUBJECT: Change 3 to USCINCEUR OPLAN 4999-99 ( )
SEE DISTRIBUTION
( ) REFERENCE: USCINCEUR OPLAN 4999-99, 28 February 1999
1.
( ) Forwarded herewith is Change 3 to USCINCEUR OPLAN 4999-99.
It fulfills a requirement established in paragraph _____, JSCP FY
2.
( ) This change is effective for planning purposes only until approved
by the Chairman.
3.
( ) Page changes are to be made as follows (superseded pages are to
be destroyed in accordance with security regulations):
Remove Pages
Insert Pages
______________
____________
______________
____________
______________
____________
4.
( ) Make the following pen-and-ink change(s): Page ___, paragraph
______. Change classification from “S” to “U.”
5.
( ) This change was coordinated with USCINCTRANS, USCINCPAC,
and USCINCSTRAT during preparation.
6.
( ) Supporting plans listed in subparagraph 3e, Plan Summary, must
be reviewed and modified upon CJCS approval of this change.
7.
( ) File this letter in front of the plan.
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-11
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
8.
( ) Without attachment, this letter is (CLASSIFICATION).
FOR THE COMMANDER IN CHIEF
s/
t/
Major General, USAF
Director, J-5
1 Enclosure
Page Changes to USCINCEUR
OPLAN 4999-99
DISTRIBUTION:
______________
______________
______________
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-12
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Letter of Transmittal)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
SUBJECT: USCINCEUR OPLAN 4999-99 ( )
SEE DISTRIBUTION
(Annex Z)
1.
( ) USCINCEUR OPLAN 4999-99 ( ), which provides for the defense of
Western Europe in general war, is attached.
2.
( ) USCINCEUR OPLAN 4999-99 fulfills a requirement established in
paragraph _____, JSCP FY
, and is effective for planning purposes only
until approved by the Chairman. USCINCEUR OPLAN 4999-FY must be
retained for possible implementation pending CJCS approval.
3.
( ) Elements of USCINCEUR OPLAN 4999-99 were coordinated with
USCINCTRANS, USCINCPAC, USJFCOM, and USCINCSTRAT during
preparation.
4.
( ) The supporting plans listed in subparagraph 3e, Plan Summary,
must be prepared and forwarded to this headquarters for review within
60 days after CJCS approval of USCINCEUR OPLAN 4999-99.
5.
( ) Without attachment, this letter is (CLASSIFICATION).
FOR THE COMMANDER IN CHIEF
s/
t/
Major General, USAF
Director, J-5
DISTRIBUTION:
_____________
1 Enclosure
USCINCEUR OPLAN 4999-99 ( )
i
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-13
Enclosure C
CJCSM 3122.03A
31 December 1999
(INTENTIONALLY BLANK)
ii
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-14
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Security Instructions and Record of Changes)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
USCINCEUR OPLAN 4999-99 ( )
SECURITY INSTRUCTIONS AND RECORD OF CHANGES ( )
1.
( ) The long title of this plan is USCINCEUR OPLAN 4999-99, Defense
of Western Europe in General War ( ). The short title is USCINCEUR
OPLAN 4999-99 ( ).
2.
( ) This document is classified (overall classification) to protect
information revealing operation plans of US military forces. Information
in USCINCEUR OPLAN 4999-99 must be disseminated only to those
agencies and personnel whose official duties specifically require
knowledge of the plan, including those required to develop supporting
plans.
3.
( ) This document contains information affecting the national defense
of the United States within the meaning of the Espionage Laws, title 18,
United States Code, sections 793 and 794. The transmission or
revelation of information contained herein, in any manner, to an
unauthorized person is prohibited by law.
4.
( ) Reproduction of this document, in whole or in part without
permission of this headquarters, is prohibited, except as required for the
preparation of supporting plans.
iii
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-15
Enclosure C
CJCSM 3122.03A
31 December 1999
RECORD OF CHANGES1
______________________________________________________________________
CHANGE
COPY
DATE OF
DATE
NUMBER
NUMBER
CHANGE
POSTED
POSTED BY
________________________________________________________________________
____________________________________________________________________
________________________________________________________________________
____________________________________________________________________
______________________________________________________________________
______________________________________________________________________
1 May be a separate page, if desired.
iv
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-16
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Plan Summary)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
USCINCEUR OPLAN 4999-99 ( )
PLAN SUMMARY ( )
1.
( ) Purpose. Describe the purpose to be achieved by implementing
the plan, including war termination objectives and the desired end state.
Refer to the task assignment in the JSCP that is fulfilled by the plan. If
this is a supporting plan, indicate what plan it supports and include,
when applicable, plans prepared by commanders of allied forces.
2.
( ) Conditions for Implementation
a.
( ) Politico-Military Situation. Summarize the politico-military
situation in which implementation of the plan should be considered.
b.
( ) Statement. Include a statement substantially as follows:
“This
summary provides military decision makers with a brief
recapitulation of the major aspects of this plan. It is based on
planning factors and estimates available at the time of preparation
and is subject to modification in the context of a specific contingency.
The information contained herein must be updated before use in
adopting COAs in a particular situation.”
c.
( ) Legal Considerations. Summarize any legal considerations that
may affect plan implementation (Status of Forces, Rules of
Engagement, International Agreements, Law of Armed Conflict, etc.).
3.
( ) Operations To Be Conducted
a.
( ) Force Requirements. Summarize the major combat force
requirements in terms of assigned, attached, or supporting forces and
augmentation required from other sources.
b.
( ) Deployment. Deployment is an operational imperative.
v
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-17
Enclosure C
CJCSM 3122.03A
31 December 1999
Summarize the concept for strategic and theater movements to
place forces, equipment, and supplies in the operational area.
Concept must cover the movement from point of origin to final
destination. Address deployment priorities, proposed requirement
and routing for strategic air mobility assets/air bridges (in
coordination with USTRANSCOM) and sea lanes, and the need for
frequency and/or requirements channels. Priority for deployment
must specify forces or capabilities having priority for deployment
ahead of other movement requirements. Priority for deployment
may be identified in terms of specific force required delivery dates
or specific dates when a functional capability is required in
theater. When supporting multiphased operations, priorities must
be identified for each phase of the operation. Additionally, the
requirement for operating frequency and/or requirement channels
to support operations and the sustainment of forces and
equipment must be considered and included in the plan. Include
special guidance for transportation operations that would not
normally be encountered, such as the need for joint logistics over-
the-shore (JLOTS) operations, assault by airdrop of troops and
equipment, or the need for building or improving assault landing
fields or support facilities. Also include the use of maritime pre-
positioning ships (MPS) and afloat pre-positioning ships following
discharge of cargo and prior to revision of the common-user pool
as theater shipping resources. Address how distribution in the
operational area will be accomplished and how distribution items
from outside the operational area will be integrated in the theater
distribution system. When applicable, include deployments and
OPSEC measures expected to be carried out before implementation
of the plan.
c.
( ) Employment. Indicate the general nature of combat operations
to be conducted, including psychological operations (PSYOP), theater
nuclear operations, information operations (IO), and Special Technical
Operations (STO), when applicable. These operations should be
discussed in the context of the following five phases of
operations:
(a) prehostilities, (b) lodgment, (c) decisive combat and
stabilization, (d) follow through, and (e) posthostilities and
redeployment. Include in this discussion a summary of the
commander’s overall intent, intent for each phase, and concept of
operations for each phase. This discussion should contain a concise
expression of the desired end state and end state for each phase. It
may include how postures of units at each end state facilitate
vi
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-18
Enclosure C
CJCSM 3122.03A
31 December 1999
transition to the next phase. A discussion of the commander’s
estimate of the enemy’s intent may also be included. The
commander’s intent is not, however, a summary of the concept of
operations.
d.
( ) Supporting Plans. List any requirements for supporting plans
to be prepared by subordinate and supporting commands or agencies.
e.
( ) Collateral Plans. List deliberate plans that could be
implemented before, during, or after the subject plan.
4.
( ) Key Assumptions. List assumptions deemed essential to the
success of the plan, including the degree of mobilization and mobility
(sea and air lift) assumed.
5.
( ) Operational Constraints. List major factors that may impede
accomplishment of the mission.
6.
( ) Time To Commence Effective Operations. Include a table showing
the required time-phased, incremental buildup of deterrent and
warfighting forces in the objective area. Clearly indicate which
warfighting forces must be available in the operational area before
effective operations can begin. Show the elapsed time, following an order
to implement the plan, when each significant level of combat force
required by the plan could begin effective operations in the objective
area. Note that the lowest level of force reported must be the smallest
force increment that could initiate effective operations. List successively
higher force levels up to the maximum level called for in the Basic Plan.
List any assumptions applied in preparing this table that are not
specified in the plan. In determining the time to commence effective
operations, consider forces to be deployed or employed to be at normal
conditions of readiness; that is, no preparations except those permitted
by JSCP and necessary C2W measures. Also consider the following
additional factors, as appropriate.
a.
( ) Time required to carry out PSYOP, IO measures, and Special
Technical Operations as specified in the relevant PSYOP, IO, and STO
plans.
b.
( ) Time for preparation and transmission of necessary orders.
vii
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-19
Enclosure C
CJCSM 3122.03A
31 December 1999
c.
( ) Reaction time, including all necessary preparations for
movement and, if necessary, staging.
d.
( ) Availability and capabilities of transportation resources and
facilities.
e.
( ) Time en route to the operational area, using lift made available
in CJCSI 3110.11, “Supplemental Instruction to the JSCP”, where
appropriate, and considering possible restrictions on the use of
deployment routes.
f.
( ) Possible enemy action against forces in transit.
g.
( ) Reception and throughput capabilities of overseas terminals,
where appropriate.
h.
( ) Time for marry up (MU) of forces and equipment deployed by
separate movement modes, including MU with pre-positioned
equipment, when appropriate.
i.
( ) Availability and capability of transport systems within the
operational area, where required.
j.
( ) Time required in the operational area for final preparation of
forces, including movement to the objective area before employment.
7.
( ) Command Relationships. Summarize the command arrangements
to be employed on execution.
8.
( ) Logistic Appraisal. Provide an estimate of logistic feasibility as
described in Annex D of this publication.
9.
( ) Personnel Appraisal. Provide an estimate of personnel feasibility
as described in Annex E of this publication.
10. ( ) Consolidated Listing and Impact Assessment of Shortfalls and
Limiting Factors. Provide a consolidated listing and impact assessment
of force, movement, and support shortfalls and limiting factors that
impact significantly on the conduct of operations. Identify shortfalls in
joint and multinational doctrine, interoperability, and training in this
paragraph. Specify the tasks that cannot be accomplished in view of the
shortfalls. Include specific documentation of each significant shortfall
and limiting factor and the efforts to resolve it in the appropriate annex
to the plan. Address additional forces, including combat support and
combat service support, recommended by the supported commander to
reduce risk but not allocated by the Services in the Plan Summary. Do
not include such forces in Appendix 2 to Annex A of the plan.
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-20
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Classification Guidance)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
USCINCEUR OPLAN 4999-99 ( )
CLASSIFICATION GUIDANCE ( )
( ) The classification guidance prepared by the CINC’s staff provides
users with subjects requiring protection, specifies the level of protection,
and establishes the period during which the protection must be
continued. As an example, an illustrative model of the required format is
shown below:
SUBJECT REQUIRING PROTECTION
PROTECTION REQUIRED DURING
COA
EXEC
POST
DEVEL
PLNG IMPL
IMPL
Operation code word
(TS)
(S)
(C)
(C)
Concept of operations
(TS)
(S)
(C)
(C)
Classification guide
(C)
(C)
(U)
(U)
Date operation begins
(TS)
(TS)
(U)
(U)
Participating units
(TS)
(C)
(U)
(U)
Employment of nuclear weapons
(TS)
(TS)
(U)
(U)
Combat rescue support
(C)
(C)
(C)
(U)
Target area weather information
(S)
(S)
(S)
(U)
Residual capabilities operations
N/A
N/A
N/A
N/A
ix
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-21
Enclosure C
CJCSM 3122.03A
31 December 1999
(INTENTIONALLY BLANK)
x
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-22
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Table of Contents)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
USCINCEUR OPLAN 4999-99 ( )
TABLE OF CONTENTS ( )
CONTENTS
PAGE
Letter of Transmittal
i
Security Instructions and Record of Changes
iii
Plan Summary
v
Classification Guidance
ix
Table of Contents
xi
Planning Guidance - Basic Plan and CINC’s Strategic Concept
1
ANNEX A, TASK ORGANIZATION
A-1
Appendix 1 - Time-Phased Force and Deployment List
A-1-1
Appendix 2 - Shortfall Identification
A-2-1
Appendix 3 - Force Module Identification
A-3-1
Appendix 4 - Deterrent Options
A-4-1
Tab A - Deterrent Options Layout
A-4-A-1
ANNEX B, INTELLIGENCE
B-1
Appendix 1 - Priority Information Requirements
B-1-1
Appendix 2 - Signals Intelligence
B-2-1
Tab A - Communications Intelligence Collection
Requirements
B-2-A-1
Tab B - Operational Electronic Intelligence Collection RequirementsB-2-B-1
Appendix 3 - Counterintelligence
B-3-1
Tab A - Counterintelligence Target List
B-3-A-1
Tab B - Multidiscipline Counterintelligence Threat Report .. B-3-B-1
Tab C - Designation of Theater CI Executive Agency
B-3-C-1
Tab D - Umbrella CI Force Protection Source Operation
Proposal
B-3-D-1
xi
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-23
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
CONTENTS
PAGE
Appendix 4 - Targeting
B-4-1
Tab A - Target List (Conventional)
B-4-A-1
Tab B - Target List (No-Strike)
B-4-B-1
Tab C - Target List (Restricted)
B-4-C-1
Appendix 5 - Human-Resource Intelligence
B-5-1
Tab A - HUMINT Operations Cell (HOC)
B-5-A-1
Tab B - EPW/Civilian Detainees
B-5-B-1
Appendix 6 - Intelligence Support to IO
B-6-1
Appendix 7 - Imagery Intelligence
B-7-1
Appendix 8 - Measurement and Signature Intelligence
B-8-1
Appendix 9 - Captured Enemy Equipment
B-9-1
Tab A - Specific Prioritized Intelligence
Collection Requirements
B-9-A-1
Tab B - Equipment Releasable for Operational Purposes
B-9-B-1
Appendix 10 - National Intelligence Support Team
B-10-1
ANNEX C, OPERATIONS
C-1
Appendix 1 - Nuclear Operations
C-1-1
Tab A - Target List
C-1-A-1
Appendix 2 - Nuclear, Biological, and Chemical Defense
Operations; Riot Control Agents and Herbicides
C-2-1
Appendix 3 - Information Operations
C-3-1
Tab A - Military Deception
C-3-A-1
Tab B - Electronic Warfare
C-3-B-1
Tab C - Operations Security
C-3-C-1
Tab D - Psychological Operations
C-3-D-1
Tab E - Physical Attack/Destruction
C-3-E-1
Tab F - Computer Network Attack
C-3-F-1
Tab G - Defensive Information Operations (D-IO)
C-3-G-1
Appendix 4 - Special Operations
C-4-1
Appendix 5 - Personnel Recovery (PR) Operations
C-5-1
Appendix 6 - Rules of Engagement
C-6-1
Appendix 7 - Reconnaissance
C-7-1
Appendix 8 - Air Base Operability
C-8-1
Appendix 9 - Combat Camera
C-9-1
Tab A - COMCAM Customer Support Requirements
C-9-A-1
Appendix 10 - Noncombatant Evacuation Operations
C-10-1
Appendix 11 - Escape and Evasion Operations
C-11-1
Appendix 12 - Counterattack
C-12-1
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-24
Enclosure C
CJCSM 3122.03A
31 December 1999
xii
CLASSIFICATION
CONTENTS
PAGE
Appendix 13 - Explosive Ordnance Disposal
C-13-1
Tab A - Forces List
C-13-A-1
Appendix 14 - Amphibious Operations
C-14-1
Appendix 15 - Force Protection
C-15-1
Tab A - Combating Terrorism
C-15-A-1
Tab B - Physical Security
C-15-B-1
Tab C - Base Defense
C-15-C-1
Appendix 16 - Critical Infrastructure Protection
C-16-1
ANNEX D, LOGISTICS
D-1
Appendix 1 - Petroleum, Oils, and Lubricants Supply
D-1-1
Tab A - Estimate of POL Support Requirements
D-1-A-1
Appendix 2 - Water Supply
D-2-1
Appendix 3 - Mortuary Affairs
D-3-1
Appendix 4 - Sustainability Analysis
D-4-1
Appendix 5 - Mobility and Transportation
D-5-1
Tab A - En route Support Requirements
D-5-A-1
Tab B - Reception, Staging, Onward Movement,
and Integration
D-5-B-1
Tab C - Primary and Alternate Ports
D-5-C-1
Appendix 6 - Civil Engineering Support Plan
D-6-1
Tab A - Suggested Construction Standards for
Military Construction and Civil Engineering
Support of Joint Operations
D-6-A-1
Appendix 7 - Nonnuclear Ammunition
D-7-1
Tab A - Munitions Matrix
D-7-A-1
Appendix 8 - Logistics Automation
D-8-1
ANNEX E, PERSONNEL
E-1
Appendix 1 - Enemy Prisoners of War, Civilian
Internees, and Other Detained Persons
E-1-1
Appendix 2 - Processing of Formerly Captured,
Missing, or Detained US Personnel
E-2-1
Appendix 3 - Finance and Disbursing
E-3-1
Appendix 4 - Legal
E-4-1
Appendix 5 - Military Postal Service
E-5-1
Tab A - Aerial Mail Terminals
E-5-A-1
Tab B - Military Post Offices
E-5-B-1
Appendix 6 - Chaplain Activities
E-6-1
Tab A - Inter-Service Chaplain Support
E-6-A-1
xiii
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-25
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
CONTENTS
PAGE
Tab B - Host-Nation Religious Support
E-6-B-1
Tab C - Commander-Staff Chaplain Relationships
E-6-C-1
ANNEX F, PUBLIC AFFAIRS
F-1
Appendix 1 - Personnel Requirements for JIBs and Sub-JIBs
F-1-1
Appendix 2 - Equipment and Support Requirements for
JIBs and Sub-JIBs
F-2-1
Appendix 3 - General Ground Rules for the Media
F-3-1
Appendix 4 - DOD National Media Pool
F-4-1
ANNEX G, CIVIL AFFAIRS
G-1
ANNEX H, METEOROLOGICAL AND OCEANOGRAPHIC
OPERATIONS
H-1
ANNEX J, COMMAND RELATIONSHIPS
J-1
Appendix 1 - Command Relationships Diagram
J-1-1
ANNEX K, COMMAND, CONTROL, COMMUNICATIONS, AND
COMPUTER SYSTEMS
K-1
Appendix 1 - Information Assurance
K-1-1
Tab A - Information Security
K-1-A-1
Appendix 2 - Command, Control, Communications,
and Computer Planning
K-2-1
Appendix 3 - Satellite Communications Planning
K-3-1
Tab A - UHF SATCOM Network List
K-3-A-1
Tab B - SHF SATCOM Network List
K-3-B-1
Tab C - EHF SATCOM Network List
K-3-C-1
Tab D - Commercial SATCOM Network List
K-3-D-1
Appendix 4 - Defense Courier Service
K-4-1
Appendix 5 - Foreign Data Exchanges
K-5-1
Appendix 6 - Frequency Spectrum Planning
K-6-1
Tab A - Electromagnetic Interference (EMI) Reporting
K-6-A-1
Tab B - JTF JCEOI Concept
K-6-B-1
Tab C - Spectrum Use Plan
K-6-C-1
Appendix 7 - JTF C4 Deployment Checklist
K-7-1
ANNEX L, ENVIRONMENTAL CONSIDERATIONS
L-1
Appendix 1 - Environmental Assessments
L-1-1
Appendix 2 - Environmental Assessment Exemptions
L-2-1
Appendix 3 - Joint Environmental Management Board
L-3-1
ANNEX M, GEOSPATIAL INFORMATION AND SERVICES
M-1
xiv
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-26
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
CONTENTS
PAGE
Appendix 1 - Geospatial Information and Services
Requirements List
M-1-1
Appendix 2 - Geospatial Information and Services
Transportation Requirements
M-2-1
Appendix 3 - Geospatial Information and Services
Reports (Optional)
M-3-1
ANNEX N, SPACE OPERATIONS
N-1
ANNEX P, HOST-NATION SUPPORT
P-1
Appendix 1 - List of HNS Agreements
P-1-1
Appendix 2 - HNS Reliability
P-2-1
Appendix 3 - Presumed HNS
P-3-1
ANNEX Q, MEDICAL SERVICES
Q-1
Appendix 1 - Joint Patient Movement System
Q-1-1
Appendix 2 - Joint Blood Program
Q-2-1
Appendix 3 - Hospitalization
Q-3-1
Appendix 4 - Returns to Duty
Q-4-1
Appendix 5 - Medical Logistics (Class 8A) System
Q-5-1
Appendix 6 - Force Health Protection
Q-6-1
Appendix 7 - Medical Command, Control,
Communications, and Computers
Q-7-1
Appendix 8 - Host-Nation Health Support
Q-8-1
Appendix 9 - Medical Sustainability Assessment
Q-9-1
Appendix 10 - Medical Intelligence Support to
Military Operations
Q-10-1
Tab A - Disease Threat by Geographic Area and Country .. Q-10-A-1
Appendix 11 - Medical Planning Responsibilities
and Task Identification
Q-11-1
ANNEX R, REPORTS
R-1
ANNEX S, SPECIAL TECHNICAL OPERATIONS
(To be provided under separate cover)
S-1
ANNEX T, CONSEQUENCE MANAGEMENT
T-1
ANNEX U, NOTIONAL CP DECISION GUIDE
(Classified section; not enclosed in JOPES Vol II (Part of CJCSI
CONPLAN 0300/0400 series))
U-1
xv
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-27
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
CONTENTS
ANNEX V, INTERAGENCY COORDINATION
V-1
Appendix 1 - Humanitarian
V-1-1
Appendix 2 - Economic……………………………………………………V-2-1
Appendix 3 - Political
V-3-1
ANNEX X, EXECUTION CHECKLIST
X-1
ANNEX Z, DISTRIBUTION
Z-1
NOTE: The letters I, O, W, and Y are intentionally omitted as appendix
designations. I and O are not authorized. W and Y may be used, if
required.
xvi
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-28
Enclosure C
CJCSM 3122.03A
31 December 1999
PLANNING GUIDANCE - BASIC PLAN AND
CINC’S STRATEGIC CONCEPT
1. Purpose. This enclosure provides specific guidance for the format and
content of the Basic Plan and CINC’s Strategic Concept to be used for the
development of OPLANs, CONPLANs, or FUNCPLANs. The Strategic
Concept format must be used to forward the CINC’s concept of
operations for CJCS concept review under a letter of transmittal.
2. Format and Content. This model illustrates the format for a Basic
Plan or CINC’s Strategic Concept for OPLANs. For example, the model
format was prepared to support development of the notional OPLAN,
USCINCEUR OPLAN 4999-99, contained in the following enclosure of
this publication.
a. The format was prepared to support US unilateral planning.
However, it should be used to the maximum extent possible in the
preparation of bilateral and multinational plans when appropriate.
b. The format was developed using administrative guidelines
normally associated with the preparation of formal written
correspondence. Minor administrative alterations (for example, page
headers and footers, page numbering, underlining, etc.) may be required
if the concept of operations is to be transmitted as an Automatic Digital
Network (AUTODIN) or a Global Command and Control System (GCCS)
newsgroup message/file.
C-29
Enclosure C
CJCSM 3122.03A
31 December 1999
(INTENTIONALLY BLANK)
C-30
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Basic Plan/CINC’s Strategic Concept)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
USCINCEUR OPLAN 4999-99 ( )
DEFENSE OF WESTERN EUROPE IN GENERAL WAR ( )
( ) References: List any maps, charts, or other documents essential to
comprehension of the Basic Plan.
1.
( ) Situation
a.
( ) General. Describe the general politico-military environment
that would establish the probable preconditions for execution of the
plan. When submitting a CINC’s Strategic Concept include, as an
opening statement in this subparagraph, a reference to the tasking
from the JSCP or other tasking document. Summarize the competing
political goals that could cause the conflict. Identify primary
antagonists. State US policy goals and the estimated goals of other
parties. Outline political decisions needed from other countries to
achieve US policy goals and conduct effective US military operations
to attain US military missions.
b.
( ) Area of Concern
(1)
( ) Area of Responsibility. Describe the commander’s area of
responsibility. A map may also be included as an attachment.
(2)
( ) Area of Interest. Describe the general area of interest
covered by the CINC’s Strategic Concept and/or Basic Plan. This
description should address all air, ground, and sea areas that
directly affect the operation. A map may also be included as an
attachment.
(3)
( ) Operational Area. Describe the specific areas covered in
each option contained in the CINC’s Strategic Concept or Basic
Plan. Maps may also be included as attachments.
c.
( ) Deterrent Options. Delineate deterrent options desired to
include those categories specified in the current JSCP. Specific units
1
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-31
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
(type of units for CINC’s Strategic Concept format) and resources
must be prioritized in terms of LAD relative to C-day. Include possible
diplomatic, informational, or economic deterrent options
accomplished by non-DOD agencies that would support US mission
accomplishment.
d.
( ) Enemy Forces. Identify the opposing forces expected on
execution and appraise their general capabilities. When preparing the
Basic Plan, refer the reader to Annex B for details; however, provide
the information essential to a clear understanding of the magnitude of
the hostile threat. When preparing a CINC’s Strategic Concept,
provide all information essential to a clear understanding of the
magnitude of the hostile threat. When applicable, identify the
enemy’s strategic and operational centers of gravity for both the
CINC’s Strategic Concept and the Basic Plan.
e.
( ) Friendly Forces
(1)
( ) Identify friendly centers of gravity, both strategic and
operational, that require protection for the successful
accomplishment of the mission.
(2)
( ) Describe the operations of unassigned forces, other than
those tasked to support this operation, that could have a direct
significant influence on the operations envisaged in this plan.
(3)
( ) List the specific tasks of friendly forces, commands, or
government agencies that would directly support OPORD execution
(e.g., USTRANSCOM, USSTRATCOM, Defense Intelligence Agency
(DIA)).
f.
( ) Assumptions. List all assumptions, including common
assumptions contained in the JSCP or other tasking, on which the
plan is based. State expected conditions over which the commander
has no control. Include assumptions that are directly relevant to the
development of this plan and supporting plans and assumptions that
express conditions that, should they not occur as expected, would
invalidate the entire plan or its concept of operations. Include
additional assumptions relevant to specific aspects of the operation in
appropriate annexes. Specify the mobility (air and sea lift), the degree
of mobilization assumed (i.e., total, full, partial, selective, or none),
2
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-32
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
and the applicability of the Presidential Selected Reserve Callup
Authority.
g.
( ) Legal Considerations. List those significant legal considerations
on which the plan is based.
2.
( ) Mission. State concisely the task and purpose to be accomplished
on execution. This statement should answer the following questions:
who, what, when, where, why, and (occasionally) how. State the mission
of the commander originating the plan (for example, the mission may be
the task assigned by the Chairman or it may be deduced from the
Commander’s Estimate based on a task assigned by the Chairman). If
the plan being prepared is a supporting plan, indicate the plan that it
supports and include, when applicable, plans prepared by commanders
of allied forces.
3.
( ) Execution
a.
( ) Concept of Operations. For most OPLANs, CONPLANs,
FUNCPLANs, and the CINC’s Strategic Concept, include the entire
concept of operations in this section. However, some OPLANs
necessarily encompass alternative COAs for accomplishing the
mission, and others require considerable detail to convey adequate
guidance for the development of supporting plans. Accordingly, the
entire concept may be placed in Annex C.
(1)
( ) Commander’s Intent. Describe the commander’s overall
intent, and intent by phase. Described the desired end state. It
should be a concise expression of the purpose of each phase of the
operation. It may include how the posture of units at that end
state facilitates transition to future operations. It may also include
the commander’s assessment of the enemy commander’s intent.
The commander’s intent is not, however, a summary of the concept
of operations.
(2)
( ) General. Base the concept of operations on the
commander’s estimate of the situation. The estimate states how
the commander plans to accomplish the mission, including the
forces involved; the time phasing of operations; the general nature
and purpose of operations to be conducted; and the interrelated or
cross-Service support, coordination, and cooperation necessary for
successful execution. The commander’s estimate should include a
3
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-33
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
statement concerning the perceived need for Reserve force
mobilization based on plan force deployment timing and Reserve
force size requirements. The concept of operations should be
sufficiently developed to include an estimate of the level and
duration of conflict to provide supporting and subordinate
commanders a basis for preparing adequate supporting plans. To
the extent possible, the plan should incorporate the following
concepts of joint operation planning doctrine:
• Combatant commander’s strategic intent and operational
focus.
• Orientation on the strategic and operational centers of
gravity of the threat.
• Protection of friendly strategic and operational centers of
gravity.
• Phasing of operations, to include the commander’s intent for
each phase.
A graphic timeline may be used to assist in describing the various
options or phases covered in the concept to include items such as
warning and response times, major deployments, and employment
phases. The concept should show how the initiative will be
gained, security against enemy actions will be maintained, and
superiority and surprise will be achieved. In the Basic Plan,
reference should be made to Annex A for detailed force
requirements. Additionally, if commanders anticipate sustained
armed conflict during execution of the plan, the concept of
operations should outline the synchronized employment of air,
land, maritime, space, and special operations (SO) forces in a joint
campaign. Incorporate Special Technical Operations into the
overall concept in a separately published plan annex.
Acknowledging that details of campaigns cannot be determined
before armed conflict, sufficient detail should be provided to guide
force structure, organization, and development, and the planning
and conduct of preconflict operations.
4
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-34
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
Note on OPLAN Structure: For plans addressing situations that
could involve armed conflict, the next two paragraphs must
include a separate description for each phase of the operation.
These phases should include, as applicable, the following:
(a)
( ) Prehostilities.
(b)
( ) Lodgment.
(c)
( ) Decisive Combat and Stabilization.
(d)
( ) Follow Through.
(e)
( ) Posthostilities and Redeployment.
(3)
( ) Deployment. Deployment is an operational imperative.
Summarize the concept for strategic and theater to place forces,
equipment, and supplies in the operational area. Concept must
cover the movement from point of origin to final destination.
Address deployment priorities, proposed requirement and routing
for strategic air mobility assets/air bridges (in coordination with
USTRANSCOM) and sea lanes, and the need for frequency and/or
requirements channels. Priority for deployment must specify
forces or capabilities having priority for deployment ahead of other
movement requirements. Priority for deployment may be identified
in terms of specific force required delivery dates or specific dates
when a functional capability is required in theater. When
supporting multiphased operations, priorities must be identified
for each phase of the operation. Additionally, the requirement for
operating frequency and/or requirement channels to support
operations and the sustainment of forces and equipment must be
considered and included in the plan. Include special guidance for
transportation operations that would not normally be
encountered, such as the need for joint logistics over-the-shore
operations, assault by airdrop of troops and equipment, or the
need for building or improving assault landing fields or support
facilities. Also include the use of maritime pre-positioning ships
and afloat pre-positioning ships following discharge of cargo and
prior to revision of the common-user pool as theater shipping
resources. Address how distribution in the operational area will
be accomplished and how distribution items from outside the
5
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-35
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
operational area will be integrated in the theater distribution
system. When applicable, include deployments and OPSEC
measures expected to be carried out before implementation of the
plan.
(4)
( ) Employment. Describe the concept of how the forces are
employed in each of the phases contained in OPLAN structure
listed above. The concept should clearly outline plans for the use
of nuclear weapons and riot control agents, if any. Plans to
conduct supporting operations (e.g., IO, SO, search and rescue
(SAR), reconnaissance, and space) must be indicated in this
section for the CINC’s Strategic Concept or by reference to
appropriate appendixes of Annex C for the Basic Plan. Summarize
any specific Reserve Component augmentation requirements for
plan execution. When a nuclear appendix or deception tab is not
prepared for Annex C, a statement to that effect must be made in
this paragraph. A graphic timeline may be used to assist in
describing the various options and phases covered.
b.
( ) Tasks
(1)
( ) List the tasks assigned to each element of the supported
and supporting commands in separate numbered sub-
subparagraphs. Each task should be a concise statement of a
mission to be performed either in future planning for the operation
or on execution of the OPORD. The task assignment should
encompass all key actions that subordinate and supporting
elements must perform to fulfill the concept of operations,
including operational and tactical military deceptions. However,
do not link the actions to deception. If the actions cannot stand
alone without exposing the deception, they must be published only
in Tab A to Appendix 3 to Annex C to receive special handling.
(2)
( ) When the plan requires the establishment of a subordinate
joint force, tasks are assigned by the CINC to the component
commanders, supporting commanders, and subordinate joint force
commanders, as appropriate. State the support that each
component is expected to provide for another.
c.
( ) Coordinating Instructions. List the instructions applicable to
6
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-36
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
the entire command or two or more elements of the command that are
necessary for proper coordination of the operation but are not
appropriate for inclusion in a particular annex. Coordinating
instructions establish, in particular, the conditions for execution.
Explain terms pertaining to the timing of execution and deployments.
Also explain other operational terms that appear in the plan but are
not defined in Joint Staff publications.
4.
( ) Administration and Logistics
a.
( ) Concept of Support. In preparing the Basic Plan, the major
portion of guidance on Service support is normally contained in a
series of detailed annexes listed in the subsequent subparagraphs. To
provide a general understanding of the requirements for logistic
support, personnel policies, and administrative plans, this
subparagraph should provide broad guidance on how such support is
to be furnished. Additional subparagraphs refer to the annexes that
provide detailed guidance on each major aspect of support. When
preparing the CINC’s Strategic Concept, this subparagraph must state
the same broad guidance on how such support is to be furnished.
Instead of referring to specific annexes in the subsequent
subparagraphs, this subparagraph must provide additional summary
level guidance.
b.
( ) Logistics. In preparing a Basic Plan, refer to Annex D. When
preparing the CINC’s Strategic Concept, state the policies, guidance,
and procedures to support all options for operations contained in the
CINC’s Strategic Concept. Logistic phases must be concurrent with
operational phases. This subparagraph should address sustainment
priorities and resources; base development and other civil engineering
requirements; host-nation support; and inter-Service responsibilities.
Identify the priority and movement of major logistic items for each
option and phase of the concept. Identify strategic and theater ports
for resupply. Outline transportation policies, guidance, and
procedures for all options. Identify logistic and transportation
assumptions and include them with other plan assumptions in
subparagraph 1f. Identify detailed planning requirements and
subordinate taskings.
c.
( ) Personnel. In preparing a Basic Plan, refer to Annex E. When
preparing the CINC’s Strategic Concept, state the policies, guidance,
7
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-37
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
concept, and procedures to support all options contained in the
CINC’s Strategic Concept. Identify detailed planning requirements
and subordinate taskings. Assign tasks for establishing and
operating joint personnel facilities, managing accurate and timely
personnel accountability and strength reporting, and making
provisions for staffing them. Discuss the administrative management
of participating personnel, the reconstitution of forces, command
replacement and rotation policies, and required individual
augmentation to command headquarters and other operational
requirements.
d.
( ) Public Affairs. In preparing the Basic Plan, refer to Annex F.
e.
( ) Civil Affairs. In preparing the Basic Plan, refer to Annex G.
f.
( ) Meteorological and Oceanographic Services. In preparing the
Basic Plan, refer to Annex H.
g.
( ) Geospatial Information and Services. In preparing the Basic
Plan refer to Annex M.
h.
( ) Medical Services. In preparing the Basic Plan, refer to Annex
Q. When preparing the CINC’s Strategic Concept outline the policies
and guidance for medical care and support. Identify planning
requirements and subordinate taskings for hospitalization and
evacuation. Address critical medical supplies and resources. Assign
tasks for establishing joint medical authorities and provisions for
staffing them. Identify medical assumptions and include them in
subparagraph 1f, Assumptions. Refer to wartime host-nation support
agreements or provisions to support in Annex P.
5.
( ) Command and Control
a.
( ) Command
(1)
( ) Command Relationships. When preparing a Basic Plan,
refer to Annex J. When preparing the CINC’s Strategic Concept,
state the organizational structure expected to exist during plan
implementation. Indicate any changes to major command and
control organizations and the time of the expected shift. Identify
all command arrangement agreements (CAAs) and memorandums
8
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-38
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
of understanding (MOUs) used and those that require
development.
(2)
( ) Command Posts. List the designations and locations of
each major headquarters involved in execution. When
headquarters are to be deployed or the OPLAN provides for the
relocation of headquarters to an alternate command post, indicate
the location and time of opening and closing of each headquarters.
(3)
( ) Succession to Command. Designate in order of succession
the commanders responsible for assuming command of the
operation in specific applicable circumstances.
b.
( ) Command, Control, Communications, and Computer (C4)
Systems. Provide a general statement concerning the scope of C4
systems and procedures required to support the operation. Highlight
any C4 systems or procedures requiring special emphasis. When
preparing a Basic Plan, refer to Annex K for details.
s/
t/
General, (Service Branch)
Commander in Chief
Annexes
(Listing of Annexes is not required when preparing CINC’s Strategic
Concept.)
A -- Task Organization
B -- Intelligence
C -- Operations
D -- Logistics
E -- Personnel
F -- Public Affairs
G -- Civil Affairs
H -- Meteorological and Oceanographic Operations
J -- Command Relationships
K -- Command, Control, Communications, and Computer Systems
L -- Environmental Considerations
9
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-39
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
M -- Geospatial Information and Services
N -- Space Operations
P -- Host-Nation Support
Q -- Health Services
R -- Reports (Classified; placeholder; not included in JOPES, Vol II.
(Annex R reports are found only in CJCSI CONPLAN
0300/0400 series.))
S -- Special Technical Operations (To be provided under separate
cover)
T -- Consequence Management (Classified; placeholder; not included
in JOPES, Vol II. (Part of CJCSI CONPLAN 0300/0400 series.))
U -- Notional CP Decision Guide (Classified; placeholder; not included
in JOPES, Vol II. (Part of CJCSI CONPLAN 0300/0400 series.))
V -- Interagency Coordination
X -- Execution Checklist
Z -- Distribution
10
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-40
Enclosure C
CJCSM 3122.03A
31 December 1999
APPENDIX A
PLANNING GUIDANCE, ANNEX A - TASK ORGANIZATION
(See Supplement, JOPES Volume II)
1. Purpose. This appendix provides guidance for the preparation of the
task organization annex to the OPLAN.
2. General. The task organization annex depicts in-theater US forces
under the command of the combatant commander, augmentation and
supporting forces, and Reserve Component forces required to move and
deploy the force, and reinforce the combatant commanders. It also
depicts the TPFDD requirements for other US forces to meet situations
described in the OPLAN or CONPLAN (with TPFDD). Additionally, the
annex lists force and strategic lift shortfalls needed to support the JSCP
apportioned forces.
3. Source. Major combat forces are derived from the JSCP or other such
direction. The JSCP identifies the apportioned major combat forces and
strategic transportation for the CINC. These apportioned resources
represent the combatant commander’s share of the total US military
capabilities expected to be available during the planning cycle. Tasks
assigned in the Unified Command Plan and Joint Pub 0-2, Unified Action
Armed Forces (UNAAF), generally use in-place forces already assigned to
the combatant commander.
4. Planning Guidance
a. Task Organization. List those apportioned forces that are included
in the Plan and are also directly subordinate to the headquarters
originating the plan and any organization that directly supports the
combatant commander.
b. Time-Phased Force and Deployment Data
(1) The TPFDD contains the complete file of data constituting in-
place, deterrent, and warfighting forces with their accompanying
supplies, plus nonunit-related equipment and personnel and associated
movement data.
(2) Forces listed in the TPFDD do not represent the total number
of forces required to execute an OPLAN. Rather, they represent JSCP-
apportioned forces identified in the JSCP.
(3) The force list in the original TPFDD may cover a deployment
period of up to 90 days (or more if desired).
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
C-41
Enclosure C
CJCSM 3122.03A
31 December 1999
(4) Nuclear munitions, if required by the forces named in
subparagraph 4b(2) above, must be maintained in separate TPFDDs.
(5) Deployment of forces must be based on the tactical,
operational, and strategic situation existing at the time and the desires
of the combatant commander.
(6) The TPFDD files are made up of selected information drawn
from data provided by the combatant command components, Services,
Defense agencies, USTRANSCOM components, and other force providing
organizations. The data, when compiled and integrated into the TPFDD,
represent an initial, best estimate of movement requirements of forces,
accompanying and nonunit-related equipment, and personnel.
c. Shortfalls. Appendix 2 should contain force and logistics shortfalls
directly related to providing support for deployment, reinforcement, and
sustainment phases. Also report transportation shortfalls either
supported by strategic lift or organic resources. Normally, late arrivals to
the AOR are due primarily to late availability of units, insufficient lift,
and/or supporting infrastructure. A shortfall is the difference between
the CINC-required deliver date (CRD) in the TPFDD and the date on
which the unit will arrive at its destination. It can be expressed as a
lack of apportioned forces identified as a plan requirement.
d. Force Module Identification. Identify JSCP-tasked force modules,
that group combat, combat support, combat service support,
sustainment elements, and other force packages as needed by the
supported commander, in Appendix 3. Given the overriding importance
of prompt response, OPLANs must include a wide variety of options to
facilitate early, flexible political decisions. At the same time, deterrent
options (Appendix 4) with their corresponding force modules must be
available for flexible, effective response to fast-building crises. In
summary, joint operation planning must account for a wide spectrum of
crisis conditions to provide flexible options for National Command
Authorities (NCA) consideration.
e. Requirements Summary. These tables for depicting aggregate
totals of personnel and equipment are required for each option
contained in the OPLAN are in Appendix 5. Completion of these tables
will require extensive coordination between the supported commander
and the supporting commanders. The refinement process requires
coordination between the headquarters initiating the OPLAN,
USTRANSCOM, and the Services (including the US Coast Guard).
Appendix A
C-42
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Task Organization Annex)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
ANNEX A TO USCINCEUR OPLAN 4999-99 ( )
TASK ORGANIZATION ( )
ORGANIZATION1
COMMANDER
US Army, Europe
CG USAREUR
US Naval Forces, Europe
CINCUSNAVEUR
US Air Forces in Europe
COMUSAFE
Special Operations Command, Europe
COMSOCEUR
MAAGs and Missions
HQ MAAGs and Missions
USEUCOM Joint Intelligence Center
COMJIC
Defense Communications Agency Europe
COMDCAEUR
National Security Agency/Central
DIRNSA/CHCSS
Security Service (Support)
1 At minimum, the task organization lists all major elements directly
subordinate to the headquarters originating the plan. In addition, list (and
designate as “support”) all organizations that directly support the operation,
although not under the COCOM of the supported commander. Organizations
to be established specifically to implement the plan, such as JTFs, should
appear in the task organization.
A-1
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Appendix A
C-43
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
The level of detail in the task organization should only be that necessary
to convey a clear understanding of the significant forces committed to the
operation.
t/
General
Commander in Chief
Appendixes
1 -- Time-Phased Force and Deployment List1
2 -- Shortfall Identification
3 -- Force Module Identification
4 -- Deterrent Options
OFFICIAL
s/
t/
Major General
Director, J-5
1 Listed as example. Provide as requested.
A-2
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Appendix A
C-44
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Time-Phased Force and Deployment List Annex)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
APPENDIX 1 TO ANNEX A TO USCINCEUR OPLAN 4999-99 ( )
TIME-PHASED FORCE AND DEPLOYMENT LIST ( )
UNIT
ULN
TYPE
FORCE AUTH
PORT OF DEBARKATION OR OCEAN AREA_____
FRN FRAG INS CODE SERV DESC PERS ULC SOURCE ORIGIN MODE LOC NAME CNTRY LAD PRI AD
Abbreviations:
ULN: Unit Line Number - Uniquely identifies a force requirement within the TPFDL. It is made up of:
FRN: Force Requirement Number - Alphanumeric code that uniquely identifies a force requirement in a plan.
FRAG: Fragmentation Number - Alpha designator for a subordinate unit, fragmentation, or increment of the requested force.
INS: Insert Code - Alphanumeric designator for inserting subordinate units, fragmentations, or increments used to retain original
fragmentations of forces when a planned movement requires additional subdivision.
UTC: Unit Type Code - Alphanumeric code from the TUCHA file for the type unit described. If not in TUCHA, may be a nonstandard
code.
SERV: Service - The parent Service code of the force requirement.
FORCE DESC: Force Description - The short type name of the force requirement.
AUTH PERS: Authorized Personnel - The authorized personnel strength associated with the UTC.
ULC: Unit Level Code - The unit level code associated with the UTC.
SOURCE: Source - The agency designated to provide the force requirement.
ORIGIN: Origin - For planning, the station at which the unit is located (in-place) or will most likely become available for deployment.
PORT OF DEBARKATION OR OCEAN AREA:
MODE: Mode - The code for the preferred mode of transportation for movement to the POD or ocean area.
LOC NAME: Location Name - The name of the geographical location of the POD or ocean area or the term “IN-PLACE” for in-
place units.
CNTRY: Country - The country or state name associated with the location name.
LAD: Latest Arrival Date - The latest day be which the force described must arrive at the POD or ocean area and complete
unloading.
PRI: Priority - The described sequence of arrival on the LAD at the POD. Leave blank if the unit is in-place. Entry is optional if
the unit is going to an ocean area or is on-call to the POD.
AD: Priority Add-On - Alphabetic code used to insert a force requirement into the priority arrival sequence without resequencing
already assigned priorities. Leave blank if unit is in-place. Entry optional if unit is on-call to the POD.
NOTE: Printed TPFDL is not required to be included with the plan when the TPFDD is on magnetic media or printouts are made available.
Classified By:
Reason:
Declassifiy On:
Sample TPFDL
A-1-1
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Appendix A
C-45
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
(INTENTIONALLY BLANK)
A-1-2
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Appendix A
C-46
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Shortfall Identification Appendix)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
APPENDIX 2 TO ANNEX A TO USCINCEUR OPLAN 4999-99 ( )
SHORTFALL IDENTIFICATION ( )
List in TPFDD file format, shortfalls of forces required to support JSCP-
apportioned forces. This appendix may be distributed to the Joint Staff
and USCINCTRANS via data file format. Include a printed shortfall
TPFDD file if an automated product is not available. Supporting
commander should identify shortfalls in a force module in the PID.
A-2-1
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Appendix A
C-47
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
(INTENTIONALLY BLANK)
A-2-2
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Appendix A
C-48
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Force Module Identification Appendix)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
APPENDIX 3 TO ANNEX A TO USCINCEUR OPLAN 4999-99 ( )
FORCE MODULE IDENTIFICATION ( )
Identify major force modules included in the plan.
FORCE MODULE ID
DESCRIPTION1
XYZ
3d Armored Cavalry Regiment
A-3-1
CLASSIFICATION
1Single-line description of force module - should be same as force module single-line title in
JOPES TPFDD. Force module titles in this appendix and in OPLAN TPFDD will identify force
modules as required in the JSCP (e.g., FDO, Deploy Decisive Force Option).
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Appendix A
C-49
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
(INTENTIONALLY BLANK)
A-3-2
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Appendix A
C-50
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Deterrent Options Appendix)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
APPENDIX 4 TO ANNEX A TO USCINCEUR OPLAN 4999-99 ( )
DETERRENT OPTIONS ( )
( ) References: List documents that have a significant bearing on the
implementation and conduct of deterrent options.
1.
( ) Purpose.
(See Supplement, JOPES Volume II)
2.
( ) Assumptions. List assumptions on which designated deterrent
options are based.
3.
( )
(See Supplement, JOPES Volume II)
Tabs
A -- Deterrent Options Layout
A-4-1
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Appendix A
C-51
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
(INTENTIONALLY BLANK)
A-4-2
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Appendix A
C-52
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Deterrent Options Layout Tab)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
TAB A TO APPENDIX 4 TO ANNEX A TO USCINCEUR OPLAN 4999-99 ( )
DETERRENT OPTIONS LAYOUT ( )
Sample Layout:
MAJOR FORCES/
DURATION
APPROVAL
OPTIONS *
SUPPLIES
OF ACTION
AUTHORITY
REMARKS **
Short, free-text
Unit name, type
Duration of the
Government, command,
Any pertinent
description of the
forces, or supplies
action in relation
Service agency, or head-
remarks
option
to D-day
quarters with approval
authority
_______________________
* Include 3-character alphanumeric Force Module Index
** Include any required diplomatic actions, e.g., FRG authority to forward deploy troops.
Classified By:
Reason:
Declassify On:
A-4-A-1
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Appendix A
C-53
Enclosure C
CJCSM 3122.03A
31 December 1999
CLASSIFICATION
(INTENTIONALLY BLANK)
A-4-A-2
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Appendix A
C-54
Enclosure C
CJCSM 3122.03A
31 December 1999
APPENDIX B
PLANNING GUIDANCE, ANNEX B - INTELLIGENCE
1. Purpose. Provide substantive guidance on intelligence and
counterintelligence (CI) functions and the relationships of combatant
commands and Defense agencies in operation planning.
2. References:
a.
Appendix U, References, CJCSM 3122.01, JOPES,
Volume I, Planning Policies and Procedures.
b.
Joint Pub 2-0 Series on intelligence doctrine.
c.
Executive Order 12333.
d.
Director of Central Intelligence (DCI) Directive 5/1.
e.
Agreements between US Government agencies
concerning intelligence resources, production
responsibilities, and sharing of intelligence.
f.
If applicable, multinational operation plan (OPLAN)
intelligence annexes.
g.
If applicable, bilateral and multilateral agreements
concerning intelligence sharing, resources, and
production responsibilities.
h.
DIAM 58 Series.
i.
DIAM 56-3
j.
NSCID #5
k.
DOD Directive 5240.1, “DOD Intelligence Activities”
l.
DOD Directive 5105.21
m. DOD Directive 5137.1
n. DOD Directive 5105.60
o. SM 621-57
p. SM 13-67
q. SM 111-88
Appendix B
C-55
Enclosure C
CJCSM 3122.03A
31 December 1999
3. General Guidance
a. Documents listed in paragraph 2 of this annex identify in detail the
responsibilities of the several elements of DOD intelligence.
b. Planning must identify the required intelligence efforts, continuing
from the Priority Information Requirements (PIR) through the entire
intelligence cycle. Consider variations in intelligence needs during
different phases and resulting changes in the intelligence effort. Identify
the collection, exploitation, and dissemination assets, personnel, units,
and organizations required to provide intelligence, surveillance, and
reconnaissance to leadership, combat forces, and supporting units.
4. Specific Guidance
a. Organization for Intelligence
(1) The relationships of the Service intelligence elements, the
unified and component command intelligence elements, DIA, CIA,
NSA/CSS, NIMA, and the Service Cryptologic Elements are summarized
in references i, m, and p.
(2) For guidance pertaining to relationships between CIA and the
unified commands, see references d, j, n, and o.
b. Planning and Direction. Establish the Commander’s Priority
Information Requirements (PIR). Using the PIR as guidance, intelligence
personnel then perform the necessary planning for how best to provide
the information needed to satisfy these requirements.
c. Processing and Exploitation. Identify the level of processing effort
the command will require. Include communications and logistic support
necessary to deliver/transmit collected information to units engaged in
processing and exploitation.
d. Analysis and Production. Outline intelligence production priorities
to ensure intelligence meets the CINC’s and Joint Task Force
Commanders’ Priority Intelligence Requirements (PIR), supports
operations planners, and delivers required intelligence to engaged and
supporting operational forces.
e. Dissemination and Integration. Establish procedures to satisfy the
requirements of vertical, horizontal, and lateral dissemination of
intelligence. Clearly describe the communications pathways and
datalinks through which near-real-time (NRT) intelligence data and
Appendix B
C-56
Enclosure C
CJCSM 3122.03A
31 December 1999
finished intelligence products will be disseminated to decision makers,
planners, and combat forces.
f. Evaluation and Feedback. Ensure that intelligence personnel at all
levels assess how well each phase of the intelligence cycle is being
performed. Evaluation and feedback are continuously performed during
all other phases of the intelligence cycle.
Appendix B
C-57
Enclosure C
CJCSM 3122.03A
31 December 1999
(INTENTIONALLY BLANK)
Appendix B
C-58
Enclosure C
CJCSM 3122.03A
31 December 1999
(Format, Intelligence Annex)
CLASSIFICATION
HEADQUARTERS, US EUROPEAN COMMAND
APO AE 09128
28 February 1999
ANNEX B TO USCINCEUR OPLAN 4999-99 ( )
INTELLIGENCE ( )
( ) References: a. Geospatial products, data, and services support
required for an understanding of this annex. Reference
Annex M (Geospatial Information and Services).
b. Documents providing intelligence required for
planning, including related annexes (such as Annex H).
c. Multinational agreements on intelligence
responsibilities.
d. Pertinent national, command, and Service policy
statements.
e. Pertinent multinational forces’ OPLANs.
f. Pertinent publications on joint intelligence doctrine.
g. CJCSI 3900.01, 21 March 1994, “Position Reference
Procedures.”
1.
( ) Situation
a.
( ) Characteristics of the Area. Summarize the physical, economic,
political, medical, social, religious, and psychological aspects and
conditions of the operational area as they may influence the concept
of the plan. Do not repeat information included in the general
situation discussed in the Basic Plan. Include sufficient analysis of
the operational area to permit development of appropriate supporting
plans. Include complete information or reference documents and
reports containing required intelligence.
b.
( ) Hydrographic, Amphibious, Topographic, and Weather
B-1
CLASSIFICATION
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Appendix B
C-59
Enclosure C
////////////////////////////////////////// |
||
|
|
|