TE-31_WCOPFOR_Commander_and_Staff_Command_Post_Operations_SOP.pdf

DRAFT 1 May 2015

WCOPFOR COMMANDER AND STAFF COMMAND POST OPERATIONS

STANDARD OPERATING PROCEDURES

1. PURPOSE: The purpose of this SOP is to outline the organization, duties and responsibilities of the World Class Opposing Force (WCOPFOR) military, contractor command post role players and contractor subject matter experts (SMEs) during the planning, preparation and execution of Mission Command Training Program (MCTP) WARFIGHTER Exercises (WFX).

2. REFERENCES.

a. TC 7-100 Hybrid Threat.

b. ATTP 5-0 Commander and Staff Guide.

3. PLANNING. During the planning phase (See Annex A for Planning Time Line), the WCOPFOR Commander and Staff execute the military decision making process

(MDMP) to produce a Competitive Operations Order. The WCOPFOR will execute this OPORD to fight the WARFIGHTER training audience. This activity is supervised by the WCOPFOR Commander and the contractor chief of staff. For training purposes, the U.S. Army MDMP process will be employed for order writing. While the US process will be employed, all operational terms, the battlefield framework and tactics will reflect Hybrid Threat operations as outlined in the TC 7-100 series of training circulars. For Administrative Instructions see Annex B and for Formatting see Annex C.

Responsibilities are outlined below.

a. WCOPFOR Commander.

(1) Develops and issues initial guidance.

(2) Approves mission statement and provides commander’s intent.

(3) Selects course of action (COA).

(4) Receives orders brief.

(5) Coordinates with the OG X-Ray Plans and Operations Division (POD) for the competitive order brief to COG-X-Ray or his representative.

b. The Contractor Chief of Staff.

(1) Supervises the staff (contractor and military) during conduct of MDMP.

(2) Ensures all War Fighting Functions are properly integrated into the competitive order.

(3) Supervises conduct of the WCOPFOR orders brief to the WCOPFOR commander, and if required, the orders brief to COG-X-Ray.

c. Contractor Operations Officer.

(1) Ensures contractor subject matter experts (SMEs) are present and provide their estimates for the MDMP process.

(2) Writes the base competitive order per the selected COA.

(3) Produces ANNEX A (Task Organization) for the competitive order.

(4) Produces Appendix 2 (Operations Overlay) to Annex C (Operations) for the Competitive Order.

(5) Produces any required Appendices in Annex C needed for the competitive order, unless indicated as a SME responsibility below.

(6) Incorporates all SME input into the order.

(7) Cross walks the base orders with all annexes and appendices to ensure consistency throughout the order.

(8) Provides the Exercise Simulation Directorate (ESD) Contractor POC the final approved order per required suspense.

d. Contractor Intelligence Officer.

(1) Writes the Scheme of Intelligence and Scheme of Reconnaissance and Surveillance sub paragraphs for the base order.

(2) Writes Annex B (Intelligence) and all required appendices for the competitive order.

(3) In coordination with the Special Purpose Forces SME, writes Annex L

(Reconnaissance and Surveillance) for the Order.

(4) Recommends priority information requirements PIRs for the order.

(5) Recommends and coordinates target types for the resulting High Value

Targets (HVT) list with the CDR and IFC.

(6) Inputs intelligence communications, computer, and space requirements for the Main Command Post and ISR cell room builds

e. Integrated Fires Command Commander (Contractor/military).

(1) Writes the Scheme of Fires paragraph for the base order.

(2) Writes Annex D (Fires) for the competitive order.

(3) Produces any required Appendices in Annex D needed for the competitive order, unless the appendix is indicated as a SME responsibility below.

f. Contractor Air Defense SME.

(1) In conjunction with the engineer SME and CBRN SME, writes the Scheme of Protection paragraph of the base order.

(2) Writes Appendix 1(Air and Missile Defense) and all TABs to Annex E (Protection).

g. Contractor Engineer SME.

(1) Writes the Scheme of Mobility/Counter-mobility sub paragraph of the Scheme of Movement and Maneuver paragraph to the base order.

(2) Writes Annex G (Engineer) and all appendices and tabs for the order.

(3) Will task organize OSC/DTG Engineer Forces into work teams and will be named using standard naming conventions.

(4) SHC and OSC Engineer Forces will not be task organized into Maneuver Forces.

h. Contractor CBRN SME.

(1) Writes the Scheme of Battlefield Obscuration sub paragraph of the Scheme of Movement and Maneuver paragraph to the base order.

(2) Writes Appendix 9 (Battlefield Obscuration) to Annex C (Operations) for the order.

i. Contractor Aviation SME.

(1) Writes the Airspace Coordinating Measures sub paragraph to coordinating instructions in the base order.

(1) Writes Appendix 10 (Airspace Command and Control) to Annex C (Operations) for the Order.

(2) Writes Appendix 5 (Air Support) to Annex D (Fires) for the order.

j. Contractor Information Warfare Officer.

(1) Writes the themes and messages sub paragraph to the coordinating instructions for the base order.

(2) In coordination with the PMESII representative to the MDMP process, writes Appendix 11 (Rules of Engagement) to Annex C (Operations) to the order.

(3) In coordination with the PMESII representative, writes Annex K (Civil Affairs Operations).

k. Contractor Special Purpose Forces SME.

(1) Writes Appendix 8 (Special Operations) to Annex C (Operations).

(2) In coordination with the contractor intelligence officer, writes Annex L

(Reconnaissance and Surveillance) to the order.

l. Contractor Sustainment SME.

(1) Writes the Sustainment paragraph to the base order.

(2) Writes Annex F (Sustainment) to the order.

m. Subordinate unit commanders (Military or designated contractor if an officer is not available).

Writes the subordinate command orders for sub elements of the competitive force. This order will include, at a minimum, the mission, scheme of maneuver (to include task and purpose for each brigade (If a division level order) or for each division (If an OSC level order) and the task organization for the command.

4. PREPARATION. The preparation phase of the exercise consists of establishing the higher and lower level command posts (Annex A), establishing the C4I system (Annex B), and ensuring the tactical plan is presented to and understood by the CONPOC, the contractor Work Area Commanders (WACs) and the Work Area Role Players (WARPs). Responsibilities are outlined below.

a. WCOPFOR Commander.

(1) In conjunction with the CONPOC and Work Area Commanders, conducts battlefield circulation (in the simulation) in the exercise AOR to ensure the disposition of forces in the simulation conform to the OPFOR scheme of maneuver.

(2) Ensures CP commanders and players are briefed and understand the

WCOPFOR OPORD.

b. Contractor Chief of Operations.

(1) Coordinates with the Exercise Support Division POC on the manning requirements for the exercise.

(2) Coordinates with the Exercise Support Division POC on the Room builds that include C4I requirements.

c. Contractor Operations Officer.

(1) Supports the MIL POC in coordinating with the Exercise Support Division POC on the manning requirements for the exercise.

(2) Supports the MIL POC in coordinating with the Exercise Support

Division POC on the Room builds that include C4I requirements.

d. Chief of Staff (all command posts).

(1) In conjunction with the chief of operations, ensures all CP players are familiar with the OPORD and their warfighting functions within the framework of that

OPORD.

(2) Ensures all CP players receive training on all C4I systems required for the exercise prior to STARTEX.

(3) Supervises the set up of the Main and Subordinate CPs prior to the training day for CP players.

e. Chief of Operations.

(1) Briefs OPORD to all CP players on Training Day.

(2) Ensures required references (OPORD, SOPs, and reporting requirements) are available on the C4I systems in all CPs.

f. Contractor Intelligence Officer.

(1) Briefs the Blue Forces Most Likely and Most Dangerous Course of Action.

(2) Briefs the Blue Forces Task Organization.

(3) Organizes and directs intelligence cell activities on exercise training days.

g. Common Operating Picture (COP) Operator (Ctr) - D/N

(1) Consolidates staff input (PowerPoint slides) into periodic Command Briefings.

(2) Provides “in-house” Archer expertise to staff sections.

(3) Prepares Emergency Contact Roster. (See Annex E)

h. Command Post Set Up. See Annex D.

i. All Warfighting Function Sections

All Warfigthing Functions will begin to build their Battle Update Briefs (See Annex J off of the MLCOA/MDCOA given by the INTEL section.

5. EXECUTION. The execution phase of the exercise consists of command and control of OPFOR units during the conduct of simulated combat operations.

a. WCOPFOR Commander

(1) Commands competitive forces during WFXs.

(2) Briefs VIP visitors to command post.

(3) Approves combat plans, orders and combat instructions.

(4) Establishes CCIR and target priorities.

(5) Briefs WCOPFOR plan and perceptions during the AAR.

b. Deputy Commander

(1) In absence of the commander, performs functions as above.

(2) Assists commander in AAR preparation.

c. Chief of Staff (All Command Posts)

(1) Responsible for all staff planning and coordination during WFX.

(2) In absence of commander/deputy, briefs VIP visitors to command post.

(3) Supervises preparation of all combat plans, orders and combat instructions.

(4) In absence of commander/deputy, approves combat plans, orders and combat instructions. (Only staff member who can sign for the WCOPFOR Commander/Deputy)

(5) Ensures current situational awareness is maintained across all war fighting functions.

(6) Conducts Shift Brief at being of each shift. (See Annex F)

(7) Coordinates actions between the CPs and red control. (MAIN CP only)

(8) Supervises preparation for and conduct of the commander’s battlefield update briefs. (1 per 12 hour shift or as required by the commander)

(9) Subordinate Command Post Files:

a. Use separate folders / binders to maintain as minimum copies of Division (Higher Headquarters) ORDER and FRAGORD, Brigade ORDER and FRAGO, Priority Intelligence Requirements (PIR), High Value Target List (HVTL), Commander Critical Intelligence Requirements (CCIRs) Engineer Log, and other documents deemed necessary for quick information.

b. Ensure admin supplies are available.

d. Chief of Operations.

(1) Ensures current situational awareness is maintained.

(2) Produces all combat plans, orders, FRAGOs and combat instructions.

(3) Assists chief of staff in incorporation of all war fighting functions during orders preparation.

(4) Plans future operations as directed.

(5) Briefs the status of ground maneuver units during the commander’s battlefield update briefs.

(6) Reports current situation to higher.

(7) Ensures critical events are posted in critical events log.

(8) Maintains and briefs current estimate of the situation.

e. Chief of Intelligence

(1) Directs the efforts of the main CP intelligence staff consisting of the Chief of Reconnaissance/Information, the Main CP ACE officer, and the Intelligence Targeting Specialist.

(2) Maintains current enemy situational awareness.

(3) Analyzes Intelligence feeds and input from subordinate CPs to project current and future enemy activities

(4) Provides timely and accurate information to WCOFPOR commander and staff for decision making process.

(5) Advises commander and staff on enemy capabilities and actions that threaten mission accomplishment.

(6) Briefs the Intelligence portion of the commander’s battlefield update briefs. (1 per 12 hour shift or as required by the commander).

(7) Ensures current enemy situation is reported to higher headquarters and subordinate CPs.

(8) Recommends PIR changes to the commander.

(9) Manages all collection assets and reallocates as required.

(10) Coordinates and directs intelligence input to the targeting process.

(11) Insures evaluations of intelligence section on-call staff members are completed.

e. Chief-Recon / Info:

a. Ensures current enemy situation is maintained and disseminated.

b. Plans future ISR operations as directed.

c. Reports current enemy situation to higher CPs, subordinate CPs and principle staff sections. (INTSUM)

d. Assists ACE officer in updating enemy unit locations on CP operations map.

e. Maintains the following information using the Crosshair and Ballista applications on the Archer REDCOP System

1) Current enemy situation.

2) Current enemy FLOT

3) Updated friendly units

f. Provides Main CP Operations section with assistance in updating friendly operations graphics.\

g. Serves as fusion cell for the current situation.

h Provides timely and accurate information to the CP Commander and staff for the decision making process.

i. Recommends PIR changes to the commander

j. Prepares Intelligence portions of Main CP briefings under the guidance of the Chief of Intelligence

k. Assists the Chief of Intelligence as required.

(13) Main CP ACE Officer

a. Provides timely and accurate information to the CP commander and staff for decision making process

b. Ensures current enemy situation is reported to higher headquarters.

c. Ensures intelligence portion of Main CP situation map is continuously updated using icons and push pins as follows:

1) Unit icons will be color coded to indicate unit nationality and echelon. In general, blue will be used to designate NATO units, and green will be used to designate enemy units from countries other than NATO. Other colors, except red, may be used as required to further identify unit associations. Red is reserved to designate friendly units.

2) Map icons will be printed for all known enemy units. Unused icon will be placed on the left side of the CP situation map in order to be readily accessible and to provide a means of tracking unlocated enemy units.

3) Color coded push-pins will be used to designate certain activities as follows:

a) BLUE = Aircraft Recon / Strike Boxes.

b) RED = Bridges in sector.

c) YELLOW = Chem strike area.

d) Green = Major obstacles, i.e., minefields, blocks obstacles.

4) Post color-code index on the map to inform CP visitors and provide situational awareness of colors used for icons and symbols.

5) Print required map icons and symbols such as numbers (10, 20, 30, etc.), grid zone indicators (PK, QK, etc.), Kill Zones, and Assembly Areas (AA) using MS Word or PowerPoint.

d. Post the following information on the left side of the main CP situation map:

1) Task Organization

2) Commander’s intent

3) Concept of operations

4) HPTL

5) PIR

6) CCIR

7) Battle Rhythm

8) Operational Weather Update’s.

e. Provide timely and accurate information to the CP Commander, the CP staff, and subordinate units.

f. Assist the chief of intelligence as required.

(14) Intelligence Targeting Specialist.

a. Provides Targets to the IFC as specified by the HVT list and the IFC

b. Tracks specific targeted areas as defined by the Target Planning Meeting and directed by the Chief of Intelligence

c. Serves as liaison for HUMINT from SPF and other sources, with emphasis on targetable information

d. Provides IMINT to the Chief-Recon and ACE Officer, with emphasis on targetable info.

f. Assists the Chief of Intelligence as required.

a. Information Warfare Officer.

i. Plans and integrates actions taken to achieve an information advantage as directed by the WCOPFOR Commander.

(a) Turn neutral elements to elements hostile to enemy Coalition Forces (CF).

(b) Provide false/misleading information on unit locations as part of deception plan.

ii. Provide Information to Influence enemy’s decision-making through his collected and available information.

iii. Tactical Tasks: Recommends actions that will Degrade, Disrupt, Deny, Deceive, Exploit, or Influence enemy

iv. Exploit Windows of Opportunity: Advises WCOPFOR Commander on opportunities to execute effective deception techniques.

b. IFC Commander

(1) Commands the Integrated Fires Command (IFC).

(2) Develops and recommends task organization of the IFC.

(3) In coordination with the Chief of Intelligence, nominates High Value Targets, High Payoff Targets, Target Priorities and Target Damage Criteria to the Commander for approval.

(4) Plans and coordinates the counter-fire fight for OSC/DTG.

(5) Conducts a Targeting/Synchronization Meeting. (See Annex G)

(6) Briefs the fires portion of the commander’s daily battlefield update brief. (See Annex F)

(7) In coordination with the Chief of Intelligence, plans and executes chemical warfare attacks and Surface to Surface Missile Strikes. (See Annex H Fire support request sheet).

(8) Prepares the fires portion of all plans, orders and FRAGOs.

(9) Coordinates with Commander of Air Defense assets for protection of critical fires assets.

(10) Coordinates with Chief of Air for joint attack of critical targets and limited Suppression of Enemy Air Defense (SEAD).

h. Chief Air Operations

(1) Plans and monitors all fixed wing and rotary wing operations. (See Annex I for FW/RW request sheet)

(2) Tasks air reconnaissance assets to assist the chief of Intelligence.

(3) Tracks air BDA.

(4) Maintains and briefs current air situation.

(5) In coordination with the IFC, establishes air corridors for ingress/egress of FW and RW missions.

(6) Prepares air portion of all plans, orders and FRAGOs.

i. Chief Air Defense

(1) Plans and monitors all air defense activities in the AOR.

(2) Directs positioning of all dedicated and constituent and supporting air defense assets to protect priority assets.

(3) Tracks enemy aircraft losses.

(4) Maintains and briefs current air defense situation.

(5) ICW chief of Intelligence identifies probable enemy air corridors.

(6) Prepares air defense portion of all plans, orders and FRAGOs.

j. Chief of Resources (Engineer)

(1) Plans and monitors all engineer activities in the AOR.

(2) Prioritizes all engineer actions to support commander’s scheme of maneuver.

(3) Tracks completion of mobility, counter-mobility and survivability efforts.

(4) Maintains and briefs current engineer situation.

(5) Maintains status of all major bridges in the AOR.

(6) Prepares engineer portion of all plans, orders and FRAGOs.

(7) FRAGORDs from subordinate command posts that transfer Engineer forces MUST be distributed to Red Control and all Work Areas.

k. Chief of Logistics

(1) Plans and monitors all logistics activities in the AOR.

(2) Prioritizes all engineer actions to support commander’s scheme of maneuver.

(3) ICW chief of operations, establishes MSRs.

(4) Maintains and briefs current rear service support operations.

(5) Prepares sustainment portion of all plans, orders and FRAGOs.

l. Infowar Operations

(1) Electronic Warfare Operations:

(a) Plans and positions assets in support of current and future operations.

(b) Monitors effects of Electronic Warfare systems on operations.

(c) Briefs Electronic Warfare system status at commander updates.

(d) Electronic Warfare systems include:

Communications Jamming Satellite Communications Command Post and Combat Systems Communications

RADARS/Targeting Counter AWACS jamming:

Counter fire Radar Jamming:

Air Defense Radar Jamming:

Combat Aviation SLAR/targeting GPS Jamming/Confusion UAV Jamming

(2) Information Operations and MISO (PSYOP): Writes or informs news writers of news items in support of applicable Information Operations.

(3) Computer Network Operations: This process is not currently affected by

WCOPFOR.

m. Chief-Recon / Info:

(1) Ensures current operations situation is maintained.

(2) Plans future operations as directed.

(3) Reports current situation to higher. (OPSUM) (4) Posts updated unit locations on Plans Map. A. Map Board:

1) Use and cut map icons from master sheet only as needed.

2) Post icons to map with push-pins, not tape.

3) Use color coded push-pins to designate certain activities:

a. BLUE = Aircraft Recon / Strike Boxes.

b. RED = Bridges in sector.

c. YELLOW = Chem strike area.

d. Green = Major obstacles, i.e., minefields, blocks obstacles.

e. Clear = Friendly units icons.

B. Print map numbers (10, 20, 30, etc.), grid zone indicators (PK, QK, etc.), Kill Zones, Assembly Areas (AA), and Phase Lines (PL) using MS Word.

C. Post color-code index on the map to inform CP Guest.

D. Draw PL’s, boundary lines and other delineators from grid coordinates off of Crosshair Viewer and the master list (coordinates) from WARSIM in BLACK, highlight critical rivers in BLUE, and ensure boundary lines are delineated by size unit on overlay:

E. Bridges should be numbered by Main CP and produced as a Shared Layer in Crosshair Viewer.

or

F. Post the following PowerPoint slides to the side of the operations map: Task Organization, commander’s intent, concept of operations, HPTL, PIR, CCIR, Battle Rhythm (if published), and Operational Weather Update’s.

(5) Information:

A. Maintains the following on Crosshair Viewer: 1)

Current enemy situation.

2) Updated friendly units via Ballista.

B. Provides timely and accurate information to the CP commander and staff for decision making process

C. Ensures current enemy situation is reported to higher headquarters.

D. Recommends PIR changes to the commander.

n. Common Operating Picture (COP) Operator (Ctr) - D/N

(1) Consolidates staff input (PowerPoint slides) into periodic Command

Briefings.

(2) Provides “in-house” Archer expertise to staff sections.

(3) Prepares Emergency Contact Roster. (See Annex E)

o. Responsibilities: Contractor SPF Operations Officer.

(1) Maintains SPF current situation.

(2) Tasks SPF Commander to reallocate SPF teams to locations that support the OSC/DTG Scheme of Maneuver.

(3) Identifies priorities to SPF Commander for direct action by SPF/CDOs.

(4) Attends targeting meeting to represent SPF elements.

(5) Maintains liaison with insurgent/criminal elements IOT ask/task those elements for supporting operations.

p. Shift Brief Description (Annex F)

During continuous operations, the CPs operates in shifts. To ensure Un-interrupted operations, staffs execute a briefing when shifts change. Depending on the situation, it may be formal or informal and include the entire staff or selected staff members. Normally it is done face-to-face among key CP leaders. The COS (XO) oversees the briefing, with participants briefing their areas of expertise. The briefing’s purpose is to inform the incoming shift of—

1) Administrative information (time cards, sick employees, training needed, etc...).

2) Current unit status (locations and slant report of units in the war fighting functions).

3) Significant activities that occurred during the previous shift (such as losses, BDA reported, unit movements, etc…).

4) Significant decisions and events anticipated during the next shift (FRAGOs issued and what they pertain to).

q. Battle Update Brief Format

(See Annex J)

r. White Cell Brief Format

(See Annex K (TBP))

s. After Action Review AAR

During a Pause Ex or End of Mission there will be a hot-wash or an AAR conducted. The following areas will be discussed using the ISSUE, DISCUSSION, and RECOMMENDATION format will be used:

1) Administration

2) Training Day

3) Pre-Start EX

4) Execution

ANNEX A (Planning Time Line) of WCOPFOR Command and Staff SOP

MDMP Higher Order Start Ex -180 days

Draft Higher Order due Start Ex – 150 days

Final Higher Order due Start Ex – 90 days

MDMP Competitive Order Start Ex – 90 days

Competitive Order due Start Ex – 60 days

DTG/BGT Orders due Start Ex – 30 days

ANNEX B (Administrative Instructions for FRAGORDs and correspondence) of WCOPFOR Command and Staff SOP

The following information pertains to administrative instructions for preparing all plans and orders (For Format see Annex C ). Unless otherwise stated, the term order refers to both plans and orders. The term base order refers to the main body of a plan or order without annexes.

Regardless of echelon, all orders adhere to the same guidance. Show all paragraph headings on written orders. A paragraph heading with no text will state “None” or “See [attachment type] [attachment letter or number].” In this context, attachment is a collective term for annex, appendix, tab, and exhibit.

The base order and all attachments follow a specific template for the paragraph layout. Every order follows the five-paragraph format. Title case, underline, and bold the titles of these five paragraphs— Situation, Mission, Execution, Sustainment, and Command and Control. The paragraph title begins with a capital letter and is bold and underlined. For example, “situation” is Situation. All subparagraphs and subtitles begin with capital letters and are underlined. For example, “concept of operations” is Concept of Operations.

When a paragraph is subdivided, it must have at least two subdivisions.

The tabs are 0.25 inches and the space is double between paragraphs. Subsequent lines of text for each paragraph may be flush left or equally indented at the option of the chief of staff or executive officer, as long as consistency is maintained throughout the order.

1. Title. Text.

a. Title. Text.

(1) Title. Text.

(a) Title. Text.

1 Title. Text.

Paragraph layout for plans and orders

PLACE AND DIRECTION DESIGNATIONS

Describe locations or points on the ground by—

• Providing the map datum used throughout the order.

• Referring to military grid reference system (MGRS) coordinates.

• Referring to longitude and latitude if available maps do not have the MGRS.

• Giving the distance and direction from a simple reference point. For example, “crossroads 1,000 meters southwest of church tower of NAPIERVILLE, LB6448.”

Designate directions in one of three ways:

• By using two locations or places. For example, direction ECKENTAL 18PV6690–

PEGNITZ 18PV6851.

• As a point of the compass. For example, north or northeast.

• As a magnetic, grid, or true bearing, stating the unit of measure. For example, 85 degrees (magnetic).

When first mentioning a place or feature on a map, print the name in capital letters exactly as spelled on the map and show its complete grid coordinates (grid zone designator, 100-kilometer grid square, and four-, six-, eight-, or ten-digit grid coordinates) in parentheses after it. When first using a control measure (such as a contact point), print the name or designation of the point followed by its complete grid coordinates in parentheses. Thereafter, repeat the coordinates only for clarity; use names, planning names, or codes.

Describe areas by naming the northernmost (12 o’clock) point first and the remaining points in clockwise order. Describe positions from left to right and from front to rear, facing the enemy. To avoid confusion, identify flanks by compass points, rather than right or left of the friendly force.

If the possibility of confusion exists when describing a route, add compass points for clarity. For example, “The route is northwest along the road LAPRAIRIE– DELSON.” If a particular route already has a planning name, such as main supply route SPARTAN, refer to the route using only that designator.

Designate trails, roads, and railroads by the names of places along them or with grid coordinates. Precede place names with trail, road, or railroad. For example, “road GRANT–CODY.” Designate the route for a movement by listing a sequence of grids from the start point to the release point. Otherwise, list the sequence of points from left to right or front to rear, facing the enemy.

Identify riverbanks as north, south, east, or west. In gap-crossing operations, identify riverbanks as either near or far.

Describe boundaries and phase lines by terrain features easily distinguishable from the ground or air or on a map. When designating boundaries between units, state which unit has responsibility and authority for the place, feature, or location to which the description refers. State each location along a boundary as either inclusive or exclusive to a unit. For example, “1st Brigade, exclusive crossroad

18PV621352.” List boundaries and phase lines from left to right or front to rear, facing the enemy.

NAMING CONVENTIONS

Units normally designate naming conventions for graphics. Otherwise, planners select them. For clarity, avoid multiword names, such as “Junction City.”

Simple names are better than complex ones. To ensure operations security, avoid assigning names that could reveal unit identities, such as the commander’s name or the unit’s home station. Do not name sequential phase lines and objectives in alphabetical order. For memory aids, use sets of names designated by the type of control measure or subordinate unit. For example, the division might use colors for objective names and minerals for phase line names.

EXPRESSING TIME

The effective time for implementing the plan or order is the same as the date-time group of the order. Express the date and time as a six-digit date-time group.

The first two digits indicate the day of the month; the last four digits indicate the time.

The letter at the end of the time indicates the time zone. Add the month or the month and year to the date-time group when necessary to avoid confusion. For example, a complete date-time group appears as 060140Z AUG 20XX.

NUMBERING PAGES

Use the following convention to indicate page numbers:

• Number the pages of the base order and each attachment separately beginning on the first page of each attachment. Use a combination of alphanumeric designations to identify each attachment.

• Use Arabic numbers only to indicate page numbers. Place page numbers after the alphanumeric designation that identifies the attachment. (Use Arabic numbers without any proceeding alphanumeric designation for base order page numbers.)

For example, the designation of the third page to Annex C is C-3. Assign each attachment either a letter or Arabic number that corresponds to the letter or number in the attachment’s short title.

Assign letters to annexes, Arabic numbers to appendixes, letters to tabs, and Arabic numbers to exhibit. For example, the designation of the third page to Appendix 5 to Annex C is C-5-3.

Separate elements of the alphanumeric designation with hyphens. For example, the designation of the third page of exhibit 2 to Tab B to Appendix 5 to Annex C is C-5-B-2-3.

Designated letters for dates and times

C-day The unnamed day on which a deployment operation commences or is to commence. The deployment may be movement of troops, cargo, weapon systems, or a combination of these elements using any or all types of transport. The letter “C” will be the only one used to denote the above. The highest command or headquarters responsible for coordinating the planning will specify the exact meaning of C-day within the aforementioned definition. The command or headquarters directly responsible for the execution of the operation, if other than the one coordinating the planning, will do so in light of the meaning specified by the highest command or headquarters coordinating the planning.

D-day The unnamed day on which a particular operation commences or is to commence. (JP 3-02)

F-hour The effective time of announcement by the Secretary of Defense to the Military Departments of a decision to mobilize Reserve units.

H-hour The specific hour on D-day at which a particular operation commences.

H-hour (amphibious operations) For amphibious operations, the time the first assault elements are scheduled to touch down on the beach, or a landing zone, and in some cases the commencement of countermine breaching operations. (JP 3-02)

L-hour The specific hour on C-day at which a deployment operation commences or is to commence.

L-hour (amphibious operations) In amphibious operations, the time at which the first helicopter of the helicopter-borne assault wave touches down in the landing zone. (JP 3-02)

M-day The term used to designate the unnamed day on which full mobilization commences or is due to commence.

N-day The unnamed day an active duty unit is notified for deployment or redeployment.

R-day Redeployment day. The day on which redeployment of major combat, combat support, and combat service support forces begins in an operation.

S-day The day the President authorizes Selective Reserve call-up (not more than 200,000).

T-day The effective day coincident with Presidential declaration of national emergency and authorization of partial mobilization (not more than 1,000,000 personnel exclusive of the 200,000 call-up).

W-day Declared by the President, W-day is associated with an adversary decision to prepare for war (unambiguous strategic warning). (JP 3-02)

C-, D-, and M-days end at 2400 hours, Universal Time (ZULU time). They are assumed to be 24-hours long for planning. Plans and orders state the letters used and their meanings. If a plan mentions more than one event, refer to the secondary event in terms of the time of the primary event. Refer to days preceding or following C-, D-, or Mday by using a plus or minus sign and an Arabic number after the letter. For example, D – 3 is three days before D-day; D + 7 is seven days after D-day. When using a time element other than days, spell it out. For example, D + 3 months.

Refer to hours preceding or following (H- or L-hour) by a plus or minus sign and an Arabic number after the letter. For example, H – 3 is three hours before H-hour; H + 7 is seven hours after H-hour. When using a time element other than hours, spell it out. For example, H + 30 minutes. E-45. Where it is necessary to identify a particular operation or exercise, place a nickname or code words before the letter, such as BALD EAGLE (D-day) or ANVIL EXPRESS (M-day).

ANNEX C (OPORD Format) of WCOPFOR Command and Staff SOP

OPERATION PLAN/ORDER [number] [(code name)] [(classification of title)] Number plans and orders consecutively by calendar year. Include code name, if any.

(U) References: List documents essential to understanding the OPLAN/OPORD. List references concerning a specific function in the appropriate attachments.

(a) List maps and charts first. Map entries include series number, country, sheet names, or numbers, edition, and scale.

(b) List other references in subparagraphs labeled as shown.

(U) Time Zone Used Throughout the OPLAN/OPORD: State the time zone used in the area of operations during execution. When the OPLAN/OPORD applies to units in different time zones, use Greenwich Mean (ZULU) Time.

(U) Task Organization: Describe the organization of forces available to the issuing headquarters and their command and support relationships. Refer to Annex A (Task Organization) if long or complicated.

1. (U) Situation. The situation paragraph describes the conditions of the operational environment that impact operations in the following subparagraphs:

a. (U) Area of Interest. Describe the area of interest. Refer to Annex B (Intelligence) as required.

b. (U) Area of Operations. Describe the area of operations (AO).

Refer to the appropriate map by its subparagraph under references, for example, “Map, reference (b).” Refer to the Appendix 2 (Operation Overlay) to Annex C (Operations).

(1) (U) Terrain. Describe the aspects of terrain that impact operations. Refer to Annex B(Intelligence) as required.

(2) (U) Weather. Describe the aspects of weather that impact operations. Refer to Annex B (Intelligence) as required.

c. (U) Enemy Forces. Identify enemy forces and appraise their general capabilities. Describe the enemy’s disposition, location, strength, and probable courses of action. Identify known or potential terrorist threats and adversaries within the AO. Refer to Annex B (Intelligence) as required.

d. (U) Friendly Forces. Briefly identify the missions of friendly forces and the objectives, goals, and missions of civilian organizations that impact the issuing headquarters in following subparagraphs:

(1) (U) Higher Headquarters’ Mission and Intent. Identify and state the mission and commander’s intent for headquarters two levels up and one level up from the issuing headquarters.

(a) (U) [Higher Headquarters Two Levels Up]. Identify the higher headquarters two levels up the paragraph heading (for example, Joint Task Force-18).

1 (U) Mission.

2 (U) Commander’s Intent.

(b) (U) [Higher Headquarters]. Identify the higher headquarters one level up in the paragraph heading (for example, 1st (U.S.) Armored Division).

1 (U) Mission.

2 (U) Commander’s Intent.

(2) (U) Missions of Adjacent Units. Identify and state the missions of adjacent units and other units whose actions have a significant impact on the issuing headquarters.

e. (U) Interagency, Intergovernmental, and Nongovernmental Organizations.

Identify and state the objective or goals and primary tasks of those non-Department of Defense organizations that have a significant role within the AO. Refer to Annex V (Interagency Coordination) as required.

f. (U) Civil Considerations. Describe the critical aspects of the civil situation that impact operations. Refer to Appendix 1 (Intelligence Estimate) to Annex B (Intelligence) as required.

g. (U) Attachments and Detachments. List units attached to or detached from the issuing headquarters. State when each attachment or detachment is effective (for example, on order, on commitment of the reserve) if different from the effective time of the OPLAN/OPORD. Do not repeat information already listed in Annex A (Task Organization).

h. (U) Assumptions. List assumptions used in the development of the

OPLAN/OPORD.

2. (U) Mission. State the unit’s mission—a short description of the who, what (task), when, where, and why (purpose) that clearly indicates the action to be taken and the reason for doing so.

3. (U) Execution. Describe how the commander intends to accomplish the mission in terms of the commander’s intent, an overarching concept of operations, schemes of employment for each warfighting function, assessment, specified tasks to subordinate units, and key coordinating instructions in the subparagraphs below.

a. (U) Commander’s Intent. Commanders develop their intent statement personally. The commander’s intent is a clear, concise statement of what the force must do and the conditions the force must establish with respect to the enemy, terrain, and civil considerations that represent the desired end state. It succinctly describes what constitutes the success of an operation and provides the purpose and conditions that define that desired end state. The commander’s intent must be easy to remember and clearly understood two echelons down.

b. (U) Concept of Operations. The concept of operations is a statement that directs the manner in which subordinate units cooperate to accomplish the mission and establishes the sequence of actions the force will use to achieve the end state. It is normally expressed in terms of decisive, shaping, and sustaining operations. It states the principal tasks required, the responsible subordinate units, and how the principal tasks complement one another. Normally, the concept of operations projects the status of the force at the end of the operation. If the mission dictates a significant change in tasks during the operation, the commander may phase the operation. The concept of operations may be a single paragraph, divided into two or more subparagraphs, or if unusually lengthy, summarized here with details located in Annex C (Operations). If the concept of operations is phased, describe each phase in a subparagraph. Label these subparagraphs as “Phase” followed by the appropriate Roman numeral, for example, “Phase I.” If the operation is phased, all paragraphs and subparagraphs of the base order and all annexes must mirror the phasing established in the concept of operations.

The operation overlay and graphic depictions of lines of effort help portray the concept of operations and are located in Annex C (Operations).

c. (U) Scheme of Movement and Maneuver. Describe the employment of maneuver units in accordance with the concept of operations. Provide the primary tasks of maneuver units conducting the decisive operation and the purpose of each. Next, state the primary tasks of maneuver units conducting shaping operations, including security operations, and the purpose of each. For offensive operations, identify the form of maneuver. For defensive operations, identify the type of defense. For stability operations, describe the role of maneuver units by primary stability tasks. If the operation is phased, identify the main effort by phase. Identify and include priorities for the reserve. Refer to Annex C (Operations) as required.

(1) (U) Scheme of Mobility/Counter-mobility. State the scheme of mobility/counter-mobility including priorities by unit or area. Refer to Annex G (Engineer) as required.

(2) (U) Scheme of Battlefield Obscuration. State the scheme of battlefield obscuration, including priorities by unit or area. Refer to Appendix 9 (Battlefield Obscuration) to Annex C (Operations) as required.

(3) (U) Scheme of Intelligence, Surveillance, and Reconnaissance.

Describe how the commander intends to use intelligence, surveillance, and reconnaissance (ISR) to support the concept of operations. Include the primary reconnaissance objectives. Refer to Annex L (Intelligence, Surveillance, and Reconnaissance) as required.

d. (U) Scheme of Intelligence. Describe how the commander envisions intelligence supporting the concept of operations. Include the priority of effort to situation development, targeting, and assessment. State the priority of intelligence support to units and areas. Refer to Annex B (Intelligence) as required.

e. (U) Scheme of Fires. Describe how the commander intends to use fires (lethal and nonlethal) to support the concept of operations with emphasis on the scheme of maneuver. State the fire support tasks and the purpose of each task. State the priorities for, allocation of, and restrictions on fires. Refer to Annex D (Fires) as required. If Annex D is not used, use subparagraphs for fires categories (for example, field artillery and command and control warfare) based on the situation.

f. (U) Scheme of Protection. Describe how the commander envisions protection supporting the concept of operations. Include the priorities of protection by unit and area. Include survivability. Address the scheme of operational area security, including security for routes, bases, and critical infrastructure. Identify tactical combat forces and other reaction forces. Use subparagraphs for protection categories (for example, air and missile defense and explosive ordnance disposal) based on the situation. Refer to Annex E (Protection) as required.

g. (U) Stability Operations. Describe how the commander envisions the conduct of stability operations in coordination with other organizations through the primary stability tasks. (See FM 3-07.) If other organizations or the host nation are unable to provide for civil security, restoration of essential services, and civil control, then commanders with an assigned AO must do so with available resources, request additional resources, or request relief from these requirements from higher headquarters. Commanders assign specific responsibilities for stability tasks to subordinate units in paragraph 3.i (Tasks to Subordinate Units) and paragraph 3.j (Coordinating Instructions). Refer to Annex C (Operations) and Annex K (Civil Affairs Operations) as required.

h. (U) Assessment. Describe the priorities for assessment and identify the measures of effectiveness used to assess end state conditions and objectives. Refer to Annex M (Assessment) as required.

i. (U) Tasks to Subordinate Units. State the task assigned to each unit that reports directly to the headquarters issuing the order. Each task must include who (the subordinate unit assigned the task), what (the task itself), when, where, and why (purpose). Use a separate subparagraph for each unit. List units in task organization sequence. Place tasks that affect two or more units in paragraph 3.j (Coordinating Instructions).

j. (U) Coordinating Instructions. List only instructions and tasks applicable to two or more units not covered in unit SOPs.

(1) (U) Time or condition when the OPORD becomes effective.

(2) (U) Commander’s Critical Information Requirements. List commander’s critical information requirements (CCIRs) here.

(3) (U) Essential Elements of Friendly Information. List essential elements of friendly information (EEFIs) here.

(4) (U) Fire Support Coordination Measures. List critical fire support coordination or control measures.

(5) (U) Airspace Coordinating Measures. List critical airspace coordinating or control measures.

(6) (U) Information Themes and Messages. List themes and messages.

(7) (U) Other Coordinating Instructions. List additional coordinating instructions and tasks that apply to two or more units as subparagraphs at this level as required.

4. (U) Sustainment. Describe the concept of sustainment, including priorities of sustainment by unit or area. Include instructions for administrative movements, deployments, and transportation—or references to applicable appendixes—if appropriate. Use the following subparagraphs to provide the broad concept of support for logistics, personnel, and Army health system support. Provide detailed instructions for each sustainment sub-function in the appendixes to Annex F (Sustainment) listed in table E-2.

a. (U) Logistics. Refer to Appendix 1 (Logistics) to Annex F (Sustainment) as required.

b. (U) Personnel. Refer to Appendix 2 (Personnel Services Support) to Annex F (Sustainment) as required.

5. (U) Command and Control.

a. (U) Command.

(1) (U) Location of Commander. State where the commander intends to be during the operation, by phase if the operation is phased.

(2) (U) Succession of Command. State the succession of command if not covered in the unit’s SOPs.

(3) (U) Liaison Requirements. State liaison requirements not covered in the unit’s SOPs.

b. (U) Control.

(1) (U) Command Posts. Describe the employment of command posts (CPs), including the location of each CP and its time of opening and closing, as appropriate. State the primary controlling CP for specific tasks or phases of the operation (for example, “Division tactical command post will control the air assault”). (2) (U) Reports. List reports not covered in SOPs. Refer to Annex R (Reports) as required.

c. (U) Signal. Describe the concept of signal support, including location and movement of key signal nodes and critical electromagnetic spectrum considerations throughout the operation. Refer to Annex H (Signal) as required.

ANNEX Titles

Annex A – Task Organization Annex B – Intelligence Annex C – Operations Annex D – Fires Annex E – Protection Annex F – Sustainment Annex G – Engineer Annex H – Signal Annex I – Not Used Annex J – Inform and Influence Activities Annex K – Civil Affairs Operations Annex L – Reconnaissance and Surveillance Annex M – Assessment Annex N – Space Operations Annex O – Not Used

Annex P – Host-Nation Support Annex Q – Spare Annex R – Reports Annex S – Special Technical Operations Annex T – Spare Annex U – Inspector General Annex V – Interagency Coordination Annex W – Spare Annex X – Spare Annex Y – Spare

Annex Z – Distribution

ANNEX D (Command Post Set UP) of WCOPFOR Command and Staff SOP

ANNEX D (Command Post Set UP) of WCOPFOR Command and Staff SOP

WCOPFOR Academy Doctrine Brief V1 (Knoedler) 8APR13

UNCLASSIFIEDUNCLASSIFIED

-2

John P. (45252)

WC-14

(43144)

Jerry J.

(43000)

WC-13

Tech Control

-3W WFX14

UNCLASSIFIEDUNCLASSIFIED

WAA/WC - 12

D

D

ANNEX E (Contact Information) of WCOPFOR Command and Staff SOP

Last Name

First Name

Room Number Cell Phone

Hotel

Smith Joseph 203 555-662-1111

ANNEX F Shift Brief Format

G2 Changes to enemy situation last 12 hours Significant Activities last 12 hours Current enemy situation Anticipated Enemy Action next 12 hours

G3 Significant OPFOR activities last 12 hours OPFOR combat capabilities (Snapshot) OPFOR Operations planned in next 12 hours Higher HQ FRAGOs last 12 hours (with synopsis of contents) Our FRAGOs last 12 hours (with synopsis of contents) Any FRAGOs working next 12 hours (with synopsis of intent) SPF

– any significant activity/reports

IFC

Significant Activities last 12 hrs OPROR Artillery capabilities (Snapshot) Significant operations over next 12 hrs

Air Significant Activities last 12 hrs OPFOR Air capabilities (Snapshot) Significant operations next 12 hrs

ADA

Significant Activities last 12 hrs OPFOR ADA capabilities (Snapshot) Significant operations next 12 hrs

Info War Significant Activities last 12 hrs OPFOR Infowar capabilities (Snapshot) Significant operations next 12 hrs

Engineer Significant Activities last 12 hrs OPFOR Engineer capabilities (Snapshot) Significant operations next 12 hrs

Sustainment Significant Activities last 12 hrs

OPFOR Sustainment capabilities (Snapshot) Significant operations next 12 hrs

At individual Section/Operator Level

Section Situation update FRAGOs published – with “what does that mean to us” FRAGOs working – with “so what does that mean to us” Machine anomalies “Hot topics” from last shift “Hot topics” for next shift

ANNEX G The Targeting Meeting:

Planning: During the planning phase, the WCOPFOR Commander and Staff execute the military decision making process (MDMP) to produce the competitive order. The WCOPFOR will employ this order to fight the WARFIGHTER training audience. The Chief of Integrated Fires will ensure Annex D is produced to include a target list worksheet clearly indicating the target, detect method, delivery means and a method of assessing results. Responsibilities are outlined below.

A. Chief of Staff

1. Leads the MDMP ensuring targeting is conducted during each step.

B. WFF Intelligence

1. Develops the SITEMP

2. Recommends High Value Targets

C. WFF Operations

1. Ensures Commander guidance and intent are followed

2. Develops Concept of Operation and scheme of maneuver

3. Works with Intel and IFC to develop High Payoff Target List

D. WFF Fires (IFC)

1. Recommends HPTL

2. Develops Target list worksheet

3. Develops Target Synchronization Matrix

E. WWF InfoWar

1. Develop Military Deception plans

2. Develop Information warfare plans

Preparation: A key to the successful conduct of the targeting meeting is preparation.

Eash representative must come to the meeting prepared to discuss available assets, capabilities, limitations, and battle damage assessment related to their WFF.

Participants must conduct prior coordination and be prepared to provide the following inputs.

A. WFF Operations must be prepared to provide:

1. Current friendly situation.

2. Maneuver assets available.

3. Current combat power.

4. Requirements from…