Interface This STX interfaces with STX 1: Plan and Prepare an MSB.

3. Training. a. Training Tips.

(1) Review FM 31-20, FM 25-101, FM 101-5, ARTEP 31-805-MTP, and unit SOPs. (2) Based on mission requirements, study applicable common task tests, MOSs, and OFS

(or MQS) manuals and make sure all necessary individual tasks can be performed to standard.

(3) Review notional materials for completeness and request additional information or guid- ance. The notional materials must support the desired STX scenario in detail. This

material should also reflect, as closely as possible without violating OPSEC, those con- ditions that exist in the SFODB’s area of operations.

(4) Make sure personnel receive training on staff organization and section responsibilities before conducting this STX.

(5) Conduct a visual reconnaissance of the training area and strive to approximate real- world conditions.

(6) Review the OPLAN developed during STX 1.

(7) Make sure support personnel who act as OPFOR (terrorist or insurgents) receive in- struction on the organization, level of training, and tactics of the forces they are to portray.

b. Training Enhancers.

(1) The SFODB should be augmented with the actual key personnel from the units (or type units) that would normally operate with the SFODB when executing FID mission sup- port. This SFODB should include not only the elements organic to the SF group but also those from units or agencies external to the SF group.

(2) If it is not possible to augment the SFODB with the actual key personnel from sup- porting elements, exercise supporting personnel should be carefully selected IAW their abilities to role play these key personnel. The exercise identities (or roles) of these “key” players will be determined by the external C³I, CS, and CSS relationships and SF battalion task organization established in the higher OPORD and the exercise scenario. (3) The exercise HQ provides the notional message traffic needed to simulate the SFODB’s

higher, lower, and adjacent unit relationships. The emphasis of this notional message traffic should be to cause the SFODB to execute its required FID mission support func- tions and to coordinate for the provision of the remainder.

(4) This STX should incorporate a level of threat from HN insurgents that the SFODB must defend against. This threat may range from terrorist attacks to full-scale insurgent operations. The SFODB’s defenses should be tested realistically based on the notional threat.

(5) Do not restrict staged terrorist or insurgent incidents to obvious bombings or ambushes. Strive to present these incidents in a realistic context. Incorporate indicators of poten- tial terrorist or insurgent activities into the intelligence portion of the exercise scenario. Ensure that through proper intelligence processing these indicators would lead the SFODB to the correct conclusions about future OPFOR activities and that the applica- tion of these conclusions to mission planning would cause the correct defensive meas- ures to be taken.

(6) Include training survivability tasks and OPSEC in all training based on an analysis of the threat existing in the unit’s area of responsibility.

(7) If using OPFOR, use multiple integrated laser engagement system (MILES) equipment. (8) Conduct STX 1 before conducting this STX.

(9) Consider developing multiechelon-echelon capabilities by involving subordinate SFODAs in the conduct of this STX. This may be done by—

(a) Concurrent execution of this STX for the SFODB and an STX for the SFODAs. (b) Concurrent execution of a CPX developed from this STX for the SFODB with an

STX for the SFODAs.

(c) Concurrent execution of this STX for the SFODB and CPXs or MAPEXs devel- oped from an STX for the SFODAs.

(10) Consider using a SFODB unassisted E&R to validate the SFODB’s plans and prepara- tions instead of normal redeployment for those SFODBs that have mastered the basic STX execution.

4. General Situation.

a. The SFODB has completed necessary operational planning and preparation needed to pro- vide FID mission support (STX 1). The SFODB has deployed to the HN and is about to be- gin providing mission support to its subordinate SFODBs. Initial resource requirements are available; however, availability is subject to changes IAW METT-TC. This STX begins with the SFODB en route to the location specified for the AOB.

b. During the provision of mission support, the SFODB must—

(1) Set up the AOB, including facilities, security, and organization.

(2) Process orders and plans from the higher HQ into company-level orders disseminated to the subordinate SFODAs.

(3) Process requests for CSS received from the SFODAs. (4) Process incoming and outgoing supplies and equipment.

(5) Receive, process, and transmit message traffic using organic communications capabilities. (6) Process information to develop intelligence products disseminated to subordinate

SFODAs and higher HQ.

(7) Process requests for CS received from subordinate SFODAs.

(8) Maintain liaison with HN and the higher in-country U.S. commander. (9) Control the execution of subordinate SFODA missions.

c. Those SFODBs that have a HN advisory assistance mission in addition to providing FID mission support should also practice STX 2.

d. The estimated time needed to conduct each STX task is a follows:

Event* Task Estimated Time Required

1 Establish an AOB 10 to 20 hours

2 Operate an AOB 40 to 60 hours

3 Prepare to Redeploy 3 to 5 hours

4 Conduct AAR 3 to 5 hours

Total Time 56 to 90 hours

*Events will be trained to standards, not time limitations. The time required to train an event will vary based on METT-TC factors and the training proficiency of the unit. The estimate is based on a 10-hour training day.