11.12.2012 Views

Military Occupational Classification and Structure - U.S. Army

Military Occupational Classification and Structure - U.S. Army

Military Occupational Classification and Structure - U.S. Army

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.

Table 10–97L–2<br />

St<strong>and</strong>ards of grade TOE/MTOE<br />

Number of positions*<br />

Line Duty position Code Grade 1 2 3 4 5 6 7 8 9 10 Explanatory notes<br />

1 INTERPRETER/TRANS-<br />

LATOR<br />

2 INTERPRETER/TRANS-<br />

LATOR<br />

97L1L SPC 1 1 1 2 2 2 3 3 3 1. Grades of additional positions will be in same pattern.<br />

2. Grading pattern will be used for all positions not specifically<br />

97L2L SGT 1 1 1 2 2 2 2 2 3 4<br />

identified in any other line.<br />

3. Grade SFC authorized in all linguist teams with four or more<br />

subordinate soldiers when no commissioned or warrant officer<br />

provided for.<br />

4. Driver positions will be graded SPC.<br />

3 INTPR/TLTR SGT 97L3L SSG 1 1 1 2 2 2 2 2<br />

4 SR INTPR/TLTR SGT 97L4L SFC 1 1 1 1<br />

5 INTPR/TLTR SGT 97L3L SSG Principal Sr Intpr/Tltr NCO in (MTOE only) Lang Spt <strong>and</strong>/or<br />

MOS Spt Sec of MI Bn (Ling).<br />

6 PLATOON SERGEANT 97L4L SFC Principal NCO in MI Plt when MOS 97L is predominant MOS.<br />

7 DETACHMENT SER-<br />

GEANT<br />

97L4L SFC Principal NCO in MI Det Hq Sec with 75 or less soldiers when<br />

MOS 97L is predominant MOS.<br />

8 CH INTPR/TLTR SGT 97L5L MSG Principal NCO in S3 Sec of MI Bn (Ling).<br />

9 FIRST SERGEANT 97L5M 1SGT Principal NCO in MI Co Hq Sec with 75 or more soldiers.<br />

Notes:<br />

1 Blank spaces in this column indicate not applicable.<br />

2 When TOE/MTOE organizations are supported by an augmentation TDA, augmentation (Aug) <strong>and</strong> base paragraphs will be graded in the aggregate.<br />

3 When no grading guidance is provided by this table for coding TOE/MTOE, TRADOC MSCs <strong>and</strong> Non-TRADOC specified proponent (TOE Combat Developers) will coordinate<br />

with appropriate Branch Personnel Proponents (listed in AR 600–3) to support additional grading of manpower requirements.<br />

Table 10–97L–3<br />

St<strong>and</strong>ards of grade TDA<br />

Number of positions*<br />

Line Duty position Code Grade 1 2 3 4 5 6 7 8 9 10 Explanatory notes<br />

Reserve Component only<br />

1 INTERPRETER/TRANS-<br />

LATOR<br />

2 INTERPRETER/TRANS-<br />

LATOR<br />

97L1L SPC 1 1 1 2 2 2 3 3 3 1. Grades of additional positions will be in same pattern.<br />

2. Grading pattern will be used for all positions not specifically<br />

97L2L SGT 1 1 1 2 2 2 2 2 3 4<br />

identified in any other line.<br />

3 INTR/TLTR SGT 97L3L SSG 1 1 1 2 2 2 2 2<br />

4 SR INTR/TLTR SGT 97L4L SFC 1 1 1 1<br />

5 PLATOON SERGEANT 97L4L SFC Principal NCO in MI Plt when MOS 97L is predominant MOS.<br />

6 DETACHMENT SER-<br />

GEANT<br />

97L4L SFC Principal NCO in MI Det Hq Sec with 75 or less soldiers when<br />

97L is the predominant MOS.<br />

7 FIRST SERGEANT 97L5M 1SG Principal NCO in MI Co Hq Sec with 75 or more soldiers.<br />

Notes:<br />

1 *Blank spaces in this column indicate not applicable.<br />

2 When TDA organizations are supported with additional <strong>and</strong>/or dual line TDA positions, the additional line(s) <strong>and</strong> base paragraph will be graded in the aggregate.<br />

3 When no grading guidance is provided by this table for coding TDA, MACOM Manpower Managers will coordinate with the appropriate Branch Personnel Proponents<br />

(listed in Ar 600-3) to support additional manpower grading requirements.<br />

Table 10–97Z–1<br />

Physical requirements<br />

Skill level Task numbers Tasks<br />

5 1, 2 1. Occasionally writes <strong>and</strong> compiles data.<br />

2. Frequently provides verbal briefings.<br />

864 DA PAM 611–21 • 31 March 1999

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

Saved successfully!

Ooh no, something went wrong!