20.11.2012 Views

ATTP 5-0.1 Commander and Staff Officer Guide - Army Electronic ...

ATTP 5-0.1 Commander and Staff Officer Guide - Army Electronic ...

ATTP 5-0.1 Commander and Staff Officer Guide - Army Electronic ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Annex P<br />

[CLASSIFICATION]<br />

ANNEX P (HOST-NATION SUPPORT) TO OPLAN/OPORD [number] [(code name)]—[issuing<br />

headquarters] [(classification of title)]<br />

4. (U) Sustainment. Identify priorities of sustainment for host-nation support key tasks <strong>and</strong> specify<br />

additional instructions as required. Outline support limitations that are due to lack of host-nation water<br />

agreements, operational impact, status of any current negotiations, <strong>and</strong> prospects for availability of the<br />

required support on a emergency basis. Refer to Annex F (Sustainment) as required.<br />

a. (U) Logistics. Identify unique sustainment requirements, procedures, <strong>and</strong> guidance to support<br />

host-nation support teams <strong>and</strong> operations. Specify procedures for specialized technical logistics<br />

support from external organizations as necessary. Use subparagraphs to identify priorities <strong>and</strong> specific<br />

instructions for maintenance, transportation, supply, field services, distribution, contracting, <strong>and</strong><br />

general engineering support. Refer to Annex F (Sustainment) as required.<br />

b. (U) Personnel. Identify host-nation support unique personnel requirements <strong>and</strong> concerns,<br />

including global sourcing support <strong>and</strong> contracted linguist requirements. Use subparagraphs to identify<br />

priorities <strong>and</strong> specific instructions for human resources support, financial management, legal support,<br />

<strong>and</strong> religious support. Refer to Annex F (Sustainment) as required.<br />

c. (U) <strong>Army</strong> Health System Support. Identify availability, priorities, <strong>and</strong> instructions for medical<br />

care. Refer to Annex F (Sustainment) as required.<br />

5. (U) Comm<strong>and</strong> <strong>and</strong> Signal.<br />

a. (U) Comm<strong>and</strong>.<br />

(1) (U) Location of the <strong>Comm<strong>and</strong>er</strong>. State the location of host-nation support area leaders.<br />

(2) (U) Succession of Comm<strong>and</strong>. State the succession of comm<strong>and</strong> if not covered in the unit’s<br />

st<strong>and</strong>ard operating procedures.<br />

(3) (U) Liaison Requirements. State the host-nation support liaison requirements not covered<br />

in the base order.<br />

b. (U) Control.<br />

(1) (U) Comm<strong>and</strong> Posts. Describe the employment of host-nation support-specific<br />

comm<strong>and</strong> posts (CPs), including the location of each CP <strong>and</strong> its time of opening <strong>and</strong> closing.<br />

(2) (U) Reports. List host-nation support-specific reports not covered in st<strong>and</strong>ard operating<br />

procedures. Refer to Annex R (Reports) as required.<br />

c. (U) Signal. Address any host-nation support-specific communications requirements or reports.<br />

Refer to Annex H (Signal) as required.<br />

ACKNOWLEDGE: Include only if attachment is distributed separately from the base order.<br />

[<strong>Comm<strong>and</strong>er</strong>’s last name]<br />

[<strong>Comm<strong>and</strong>er</strong>’s rank]<br />

The comm<strong>and</strong>er or authorized representative signs the original copy of attachment. If the<br />

representative signs the original, add the phrase “For the <strong>Comm<strong>and</strong>er</strong>.” The signed copy is the<br />

historical copy <strong>and</strong> remains in the headquarters’ files.<br />

[page number]<br />

[CLASSIFICATION]<br />

P-4 <strong>ATTP</strong> 5-<strong>0.1</strong> 14 September 2011

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!