Field Organizations Unit Status Reporting · Field Organizations Unit Status Reporting *Army...

Army Regulation 220–1

Field Organizations

Unit StatusReporting

HeadquartersDepartment of the ArmyWashington, DC15 November 2001

UNCLASSIFIED

Report Documentation Page

Report Date 15 Nov 2001

Report Type N/A

Dates Covered (from... to) -

Title and Subtitle Field Organizations: Unit Status Reporting

Contract Number

Grant Number

Program Element Number

Author(s) Project Number

Task Number

Work Unit Number

Performing Organization Name(s) and Address(es) Department of the Army Headquarters Washington, DC

Performing Organization Report Number

Sponsoring/Monitoring Agency Name(s) and Address(es)

Sponsor/Monitor’s Acronym(s)

Sponsor/Monitor’s Report Number(s)

Distribution/Availability Statement Approved for public release, distribution unlimited

Supplementary Notes

Abstract

Subject Terms

Report Classification unclassified

Classification of this page unclassified

Classification of Abstract unclassified

Limitation of Abstract UU

Number of Pages 166

SUMMARY of CHANGEAR 220–1Unit Status Reporting

This revision--

o Incorporates applicable provisions of the Army’s disengagement planningguidance. (Throughout)

o Requires hardware procurement in support of unit status reporting to followthe standard bottom-up process and to be based on the specific software andinfrastructure requirements of individual units. (Chap 1)

o Requires the Deputy Chief of Staff for Operations and Plans to issue timelyguidance for status reporting to units conducting peacetime operationaldeployments and to provide disengagement planning guidance. (Chap 1)

o Requires the Deputy Chief of Staff for Operations and Plans to develop andimplement a training program for the Army Status of Resources and TrainingSystem and Personal Computer Army Status of Resources and Training System.(Chap 1)

o Requires that Training and Doctrine Command coordinate with the majorcommands and recommend to Headquarters, Department of the Army the squads,crews, teams, and/or systems that should be reported in unit status report(USR)training data and the manning and qualification standards and criteriafor these entities. (Chap 1)

o Requires that Reserve component units report changes to the measuredresource/status area levels that do not affect the overall category level.(Chap 2)

o Clarifies policy on additional guidance and assistance from MACOMs availableto deployed personnel and deployed units for determining the availability ofunits, personnel, and equipment. (Chap 3)

o Changes C5 reporting approval authority (consistent with criteria andlimitations established by the Joint Chiefs of Staff) from U.S. ArmyHeadquarters to the major commands. (Chap 3)

o Clarifies procedures for determining personnel availability and availablestrength and addresses unique requirements for the U.S. Army Reserve. (Chap4)

o Clarifies military occupational specialty qualified criteria for Armylinguists in conjunction with transition to the Army Language Master Plan andestablishes mandatory status reporting requirements for linguists. (Chap 4)

o Adds reporting requirement for unit personnel gains; modifies requirementsfor reporting stabilized personnel; and moves the requirements for reportingtemporary duty personnel and special duty personnel to chapter 4 toconsolidate data reporting requirements for HQDA-level personnel turbulencecalculations. (Chap 4)

o Revises instructions and establishes categories for the nuclear, biological,and chemical equipment reporting in accordance with emerging policyguidelines from the Joint Staff. (Chap 5)

o Establishes a 30-day materiel conditions status report period for all units,with provisions for requests for temporary exemptions for Reserve componentunits unable to comply because of full-time manning shortages.(Chap 6)

o Revises the process and procedures for determining and reporting unittraining level; includes new metrics to determine the percent of the mission-essential task list trained; improves the methodology for determining thenumber of days required for training; and adds a requirement for AA-levelunits to use a training level review process to enhance the credibility oftraining level determinations. (Chap 7)

o Establishes “fully manned and combat capable” as an additional reportablecategory for squad/crew/team/system manning and qualification. (Chap 7)

o Establishes the training level review process that allows AA-level units toassess the credibility of their training level determinations on the basis ofthe frequency of the units’ execution of applicable doctrinal trainingevents. (Chap 7)

o Revises the guidance for determining the training level under uniqueconditions and provides flexibility in reporting nuclear, biological, andchemical training days. (Chap 7)

o Updates deployment tempo reporting and aligns categories to mirror thosemandated for personnel tempo reporting. (Chap 7)

o Enables major commands to establish the pre-mobilization training standardsor objectives for Reserve component unit reporting. (Chap 7)

o Revises the use of the deployed mission accomplishment estimate so that thedata entry in ASORTS will reflect the wartime mission status of reportingunits under all circumstances. (Chap 8)

o Requires unit commanders to report authorized stockage list status data,including logistical standards for sustained military operations, in the unitstatus report. (Chap 8)

o Establishes special instructions for when a unit is called up, mobilized, ordeployed/employed. (Chap 9)

o Clarifies instructions for composite reporting and discusses the unit statusassessments made both by the major combat unit level and by subordinateelements. (Chap 10)

o Requires commanders of major combat units to identify and submit their 90-daystatus projections and, in order of priority, their top three significantissues. (Chap 10)

o Clarifies major command responsibilities for providing unit status reportingsupport and assistance to percent effective (PCTEF) reportable Reservecomponent units while they are on active duty and/or are deployed. (Chap 11)

o Establishes special training level criteria for major combat units preparingfor, conducting, or recovering from peacetime operational deployment. (Chap11)

o Establishes new requirements for percent effective reporting (PCTEF) by Armyunits before and during peacetime operational deployment. (Chap 11)

o Authorizes MACOMs to approve requests from reporting units to reporttemporarily, in extremely exceptional circumstances, using derivative unitidentification code procedures. (Chap 11)

o Adds guidance for multi-component unit status reporting and identifies uniquecharacters in the UICs assigned to multi-component units that denote thecomponent. (Chap 12)

HeadquartersDepartment of the ArmyWashington, DC15 November 2001

Field Organizations

Unit Status Reporting

*Army Regulation 220–1

Effective 1 December 2001

H i s t o r y . T h i s p r i n t i n g p u b l i s h e s ar e v i s i o n o f t h i s p u b l i c a t i o n . B e c a u s e t h ep u b l i c a t i o n h a s b e e n e x t e n s i v e l y r e v i s e d ,t h e c h a n g e d p o r t i o n s h a v e n o t b e e nhighlighted.S u m m a r y . T h i s r e g u l a t i o n o n U . S .Army unit status reporting has been re-vised to include pertinent information onunit readiness reporting requirements aswell as instructions on the completion andsubmission of reports. This regulation es-tablishes a single-source document for ob-t a i n i n g a n a s s e s s m e n t o f t h e s t a t u s o fArmy units in terms of their personnel,

equipment, and training. It implements in-structions in the Chairman of the JointChiefs of Staff Manual 3150.02.

Applicability. This regulation applies tot h e A c t i v e A r m y , t h e A r m y N a t i o n a lG u a r d o f t h e U n i t e d S t a t e s , a n d t h eUnited States Army Reserve. During mo-bilization, chapters and policies containedin this regulation may be modified by theproponent.

Proponent and exception authority.The proponent of this regulation is theDeputy Chief of Staff for Operations andPlans. The proponent has the authority toapprove exceptions to this regulation thata r e c o n s i s t e n t w i t h c o n t r o l l i n g l a w a n dregulation. The Deputy Chief of Staff forOperations and Plans may delegate thisauthority, in writing, to a division chiefwithin the proponent agency who holdst h e g r a d e o f c o l o n e l o r t h e c i v i l i a nequivalent.

Army management control process.This regulation contains management con-t r o l p r o v i s i o n s , b u t i t d o e s n o t c o n t a i nc h e c k l i s t s f o r c o n d u c t i n g m a n a g e m e n tcontrol reviews. Alternative management

control reviews are used to accomplish as-sessment of management controls.

S u p p l e m e n t a t i o n . S u p p l e m e n t a t i o n o fthis regulation and establishment of formsother than DA forms are prohibited with-out prior approval from Headquarters, De-p a r t m e n t o f t h e A r m y ( D A M O – O D R ) ,WASH, DC 20310–0440.

Suggested Improvements. Users areinvited to send comments and suggestedimprovements on DA Form 2028 (Recom-m e n d e d C h a n g e s t o P u b l i c a t i o n s a n dB l a n k F o r m s ) d i r e c t l y t o H Q D A t oHQDA (DAMO–ODR), Washington, DC20310–0440.

Distribution. This regulation is availablein electronic media only and is intendedfor command levels A, B, C, D, and E fort h e A c t i v e A r m y , t h e A r m y N a t i o n a lGuard of the United States, and the U.S.Army Reserve.

Contents (Listed by paragraph and page number)

Chapter 1Overview, page 1Purpose • 1–1, page 1References • 1–2, page 2Explanation of abbreviations and terms • 1–3, page 2Responsibilities • 1–4, page 2Concept • 1–5, page 4Unit status levels • 1–6, page 4Personal Computer/Army Status of Resources and Training System • 1–7, page 4

Chapter 2General Instructions, page 5The unit status report • 2–1, page 5Units required to submit unit status reports • 2–2, page 5

*Supercedes AR 220–1 dated 1 September 1997

AR 220–1 • 15 November 2001 i

UNCLASSIFIED

Contents—Continued

Units excused from submitting unit status reports • 2–3, page 6Types of reports • 2–4, page 7Reporting channels • 2–5, page 8Actions by higher commanders • 2–6, page 13Security classification and declassification of reports • 2–7, page 14Retention of reports • 2–8, page 14Release of and access to GSORTS/ASORTS information • 2–9, page 14Authorized level of organization • 2–10, page 15

Chapter 3Instructions for Reporting Units, page 15General • 3–1, page 15C-level definitions • 3–2, page 15Standard rules and procedures • 3–3, page 16C-5 reporting instruction • 3–4, page 16Level 6 reporting • 3–5, page 18Reporting data • 3–6, page 18Regular reports prepared by battalion-, squadron-, and smaller-size units • 3–7, page 18

Chapter 4Personnel Data, page 19General • 4–1, page 19Determine required strength • 4–2, page 19Determine assigned strength percentage • 4–3, page 19Determine available strength percentage • 4–4, page 19Determine available military occupational specialty qualified percentage • 4–5, page 20Determine available senior-grade percentage • 4–6, page 21Calculate personnel level (P-level) • 4–7, page 21Determine personnel turnover percentage • 4–8, page 22Instruction for completing sections A and B of DA Form 2715 • 4–9, page 22Mandatory personnel reporting remarks • 4–10, page 23

Chapter 5Equipment-on-Hand Data, page 28General • 5–1, page 28Equipment authority • 5–2, page 29Reportable equipment • 5–3, page 29Applying substitutes and in-lieu-of equipment in determining quantity of reportable equipment on hand • 5–4,

page 29Evaluating component part availability • 5–5, page 30Reserve component equipment • 5–6, page 30Equipment not on site • 5–7, page 31Loans from Army pre-positioned stocks • 5–8, page 31How to determine pacing items • 5–9, page 31Calculate the S-level • 5–10, page 31Completing equipment-on-hand portions of DA Form 2715, sections A and B • 5–11, page 33Mandatory entries for all reporting units • 5–12, page 34NBC equipment reporting • 5–13, page 39

Chapter 6Equipment Serviceability Data, page 44General • 6–1, page 44Determine reportable equipment • 6–2, page 44Basis for the R-level computation • 6–3, page 44Determine available hours/days • 6–4, page 44

ii AR 220–1 • 15 November 2001


Determining the equipment serviceability level (R-level) • 6–5, page 44Complete the ES portion of sections A and B of DA Form 2715 • 6–6, page 45Mandatory remarks for equipment serviceability • 6–7, page 46Serviceability of selected NBC equipment items • 6–8, page 48

Chapter 7Training Data, page 48General • 7–1, page 48Assessing the unit’s proficiency in its mission-essential tasks and determining the T–METL • 7–2, page 49Estimating training days and determining the T–Days status level • 7–3, page 53Squad/crew/team/system manning and qualification data • 7–4, page 54Determining the unit T-level • 7–5, page 59The training level review process • 7–6, page 59Reporting training data on DA Form 2715 • 7–7, page 62Assessing the availability of critical resources required for training • 7–8, page 63Reporting resource constraints • 7–9, page 64Training level under unique conditions • 7–10, page 64Unit deployment tempo • 7–11, page 66Tailored reporting for Reserve component units • 7–12, page 69

Chapter 8Mission Accomplishment Estimate, page 69General • 8–1, page 69Purposes of the MAE • 8–2, page 70Instructions for determining the MAE • 8–3, page 70Determining the MAE for hospital units • 8–4, page 71Reporting ASL status data in the MAE section • 8–5, page 71MAE bands of effectiveness • 8–6, page 71C-level and corresponding MAE ranges • 8–7, page 72Commander’s subjective MAE evaluation and C-level comparison • 8–8, page 72

Chapter 9Overall Unit Level and Special Instructions for Remarks Entries for Regular Reports, page 72Overall unit level • 9–1, page 72Joint reporting data • 9–2, page 74Army-unique data • 9–3, page 75Commander’s remarks • 9–4, page 77READY and REASN remarks • 9–5, page 77Preparation of general remarks • 9–6, page 79Higher command remarks • 9–7, page 80Special instructions when a unit is called up, mobilized, deployed, or employed • 9–8, page 80Validation reporting • 9–9, page 80

Chapter 10Composite Reports, page 81General • 10–1, page 81C–5 composite report instructions • 10–2, page 81Reserve component training level • 10–3, page 81Reporting personnel/EOH status during partial deployments • 10–4, page 82Determining composite C-levels • 10–5, page 82Completing composite reports—general • 10–6, page 85Section A of DA Form 2715 • 10–7, page 85Section B of DA Form 2715 • 10–8, page 86Mandatory remarks for composite report • 10–9, page 86

iiiAR 220–1 • 15 November 2001


Chapter 11Unit Status Reporting Before, During, and After Deployment, page 87General • 11–1, page 87Concept • 11–2, page 87PCTEF reporting • 11–3, page 88Deployed reporting procedures for FF-level and AA-level units • 11–4, page 90Crisis and wartime reporting channels • 11–5, page 93Derivative UIC reporting procedures • 11–6, page 93Instructions for completing the deployed USR • 11–7, page 95

Chapter 12Multi-Component Unit Reporting, page 101General • 12–1, page 101Concept for multi-component unit status reporting • 12–2, page 102Reporting procedures for multi-component AA-level units • 12–3, page 102Special instructions, if any, for completing multi-component units status reports • 12–4, page 102

Appendixes

A. References, page 103

B. Equipment Readiness Codes, page 105

C. Pacing Items of Equipment, page 110

D. Personnel Availability Criteria, page 114

E. Reason Codes, page 115

F. Exempt/Non-Type Classified Items, page 121

Table List

Table 2–1: Report submission timelines, page 6Table 3–1: C–5 reporting, page 17Table 3–2: Relationships between report types and report forms/sets/remarks, page 18Table 4–1: Level for available, MOSQ, and senior-grade strengths, page 22Table 5–1: Equipment-on-hand criteria (high-density individual LINs, 21 or more items, includes pacing items),

page 30Table 5–2: Equipment-on-hand criteria (low-density individual LINs, 20 or less items, includes pacing items),

page 31Table 5–3: Standardized individual basic load equipment, page 40Table 5–4: NBC equipment categories, page 40Table 5–5: Determining the NBC equipment category S-level when the total number of wartime-required NBC

equipment items in a specified category is 21 or more, page 42Table 5–6: Determining the NBC equipment category S-level when the total number of wartime-required NBC

equipment items in a specified category is 20 or less, page 42Table 6–1: Level for percentage of equipment fully mission capable, page 45Table 7–1: Translating the T–METL percentage into a T–METL status level, page 53Table 7–2: T–Days/T–NBC/T–Pre MOB, page 53Table 7–3: Squad/crew/team/system manning and qualification criteria, page 55Table 7–4: Training level review part 1: training event and time/frequency requirements, page 61Table 7–5: Training level review part 2: training tempo percentages and training level review, page 61Table 9–1: Reason codes for C–5 reporting, page 74Table 10–1: Composite level criteria (PER, EOH, and ES), page 82Table 11–1: Special USR training level criteria for major combat units, page 92Table 11–2: Reporting requirements for units assigned peacetime operational deployments, page 92Table 11–3: USR support/oversight responsibilities for PCTEF-reportable RC units, page 99Table B–1: ERC Codes, page 107

iv AR 220–1 • 15 November 2001


Table C–1: Pacing items by unit type, page 111Table D–1: Determining personnel availability decision matrix (for use in determining if soldiers in various situations

should be considered available), page 114Table E–1: Primary reason overall level not C-1, page 116Table E–2: Reason codes associated with PCTEF reporting, page 116Table E–3: Reason codes for personnel, page 117Table E–4: Codes for equipment on hand, page 118Table E–5: Codes for equipment serviceability, page 118Table E–6: Training codes, page 120Table E–7: NBC supply/serviceability and training status codes, page 121Table F–1: LINs exempt from reporting, page 122

Figure List

Figure 2–1: Unit status reporting channels, Active Army and Army Reserve, page 9Figure 2–2: Unit status reporting channels, Army National Guard, page 10Figure 2–3: Unit status reporting channels, ARSOF, page 11Figure 2–4: Unit status reporting channels, multi-component units, page 12Figure 2–5: Unit status reporting channels during wartime or crisis, page 13Figure 4–1: Section A, Joint reporting requirements, personnel set, page 23Figure 4–2: Section B, PERSDATA, PROFIS, FEMALE, and ACTGURES sets, page 23Figure 4–3: Section D, 2PSPER, page 24Figure 4–4: Section D, 2RQPER, page 25Figure 4–5: Section D, 2ADDSKIL, page 26Figure 4–6: Section D, 2 LANGAGE, page 27Figure 4–7: Section D, PSPER NON-AVAILABLE, page 28Figure 5–1: Section A, Joint reporting requirements, EQSUPPLY set, page 33Figure 5–2: Section B, Army reporting requirements, EQOHDATA, page 34Figure 5–3: Section D, 2PIESTAT, page 35Figure 5–4: Section D, 2ERCFOUR, page 36Figure 5–5: Section D, 2EOHSHRT, page 37Figure 5–6: Section D, borrowed, loaned, and sub/ILO report, page 38Figure 5–7: Section D, MES equipment report, page 39Figure 5–8: NBC equipment shortage report, page 41Figure 5–9: NBC S-level calculation, page 43Figure 6–1: R-levels for all reportable equipment, page 45Figure 6–2: Section A, Joint reporting requirements, EQCONDN set, page 46Figure 6–3: Section B, Army reporting requirements, EQMCRDAT set, page 46Figure 6–4: Section D, 2PIERRAT, page 47Figure 6–5: Section D, 2ERCERRT, page 48Figure 7–1: Determining T-METL based on METL tasks evaluated, page 51Figure 7–2: T-METL status calculations, page 52Figure 7–3: Section B, Army reporting requirements, TRAINDAT set, page 54Figure 7–4: Submitting squad/crew/team/system status data, page 58Figure 7–5: Determining the training tempo percentage, page 61Figure 7–6: Section A, Joint reporting requirements, TRAINING set, page 62Figure 7–7: Section D, TRRAT GENTEXT remarks, page 63Figure 7–8: Environmental factors report, page 66Figure 7–9: DEPTEMPO calculations, page 68Figure 8–1: READYSEG set, MAE, page 70Figure 9–1: Section A, Joint reporting requirement, page 73Figure 9–2: Section B, Army reporting requirement, page 76Figure 9–3: Section C, READY remarks, page 78Figure 9–4: Section C, REASN remarks, page 79Figure 10–1: Composite level calculation, separate infantry brigade (mechanized), page 83

vAR 220–1 • 15 November 2001


Figure 10–2: Composite level calculation, separate infantry brigade, page 84Figure 11–1: Deployed report worksheet, part I, page 96Figure 11–2: Deployed report worksheet, part II, page 98Figure 11–3: PCTEF reporting decision tree for Army units, page 100Figure 11–4: PCTEF reporting decision matrix for Army units, page 101

Glossary

vi AR 220–1 • 15 November 2001

Chapter 1Overview

1–1. Purposea. This regulation establishes the Army’s unit status reporting system. It explains, in detail, what status information

Army units are required to report, how reports are prepared, and how reports are submitted.b. The Army’s unit status report (USR) is a part of the Global Status of Resources and Training System (GSORTS).

GSORTS is an internal management tool for use by the Chairman, Joint Chiefs of Staff (CJCS), the Joint Staff, theServices, the unified commands, and the combat support agencies. GSORTS is the single automated reporting systemwithin the Department of Defense that is the central registry of all operational units of the U.S. Armed Forces andcertain foreign organizations. As a unit readiness system, GSORTS indicates the level of selected resources andtraining required to undertake the mission(s) for which a unit was organized or designed. GSORTS provides thisinformation on measured units at a specific point in time. This information supports, in priority order, crisis responseplanning; deliberate or peacetime planning; and management responsibilities to organize, train, and equip combat-readyforces for the unified commands. Chairman of the Joint Chiefs of Staff Manual (CJCSM) 3150.02 requires thecommanders of all reporting units to report their units’ status in the areas of personnel, equipment on hand, equipmentserviceability, and training. The Army requires additional data that increases the value of the USR as a resourcemanagement and operations tool for Headquarters, Department of the Army (HQDA). The supplemental data requiredby the Army was determined by HQDA in coordination with the Army’s major commands (MACOMs) to enable thecommanders of reporting units to more clearly portray the effects of resource application in their units. Commanders ofreporting units submit their USR information through their respective MACOM, or through the National Guard Bureau(NGB) for Army National Guard of the United States (ARNGUS) units, and HQDA to the Joint Staff. The informationalso is made available to interested commands and commanders-in-chief (CINCs). The information and data containedin the USR enables commanders and staffs at all levels to analyze and address key unit status indicators. At installationlevel and below, the USR assists commanders to identify resource shortfalls so that cross-leveling actions can beinitiated, if appropriate, to alleviate the shortfall. At HQDA and at the MACOM level, USRs provide information thatcan be used as the basis for resourcing requests and decisions. For joint planners and CINCs, the USR provides animportant assessment of the ability of individual units to undertake their assigned wartime missions. The USR is not aunit report card and should not be used to evaluate or compare the accomplishments of subordinate units ortheir commanders.

c. The Army’s USR system is intended to enable the commanders of reporting organizations to uniformly determineand accurately report an overall unit status level or category level (C-level) that indicates the degree to which a unit hasachieved prescribed levels of fill for personnel and equipment, the training status of those personnel, and themaintenance status of the equipment. The C-level is based on objective and subjective assessments in the followingareas—

(1) Personnel (PER). The personnel status of the unit (that is, the P-level) based on the number and type of requiredpersonnel assigned to the unit that are available for the execution of the reporting unit’s wartime mission. (See chap 4.)

(2) Equipment on hand (EOH). The equipment status of the unit (that is, the S-level) based on the quantity and typeof required equipment that is available for the execution of the reporting unit’s wartime mission. (See chap 5.)

(3) Equipment serviceability (ES). The serviceability status of the unit’s equipment (that is, the R-level) based on theoperational readiness condition of the unit’s on-hand and available equipment. (See chap 6.)

(4) Training. The training status of the unit (that is, the T-level) based on the commander’s assessment of unittraining proficiency on mission-essential tasks and the commander’s estimate of the number of training days required toachieve or sustain full mission-essential task list (METL) proficiency. For selected squads, crews, teams, and systems,commanders at all levels determine and report the number of these elements/systems that meets established standardsand criteria for manning and qualification and for information and analysis at higher levels. (See chap 7.)

d. Additionally, the Army’s USR system provides information to HQDA that—(1) Assists the portrayal of Army-wide conditions and trends.(2) Assists the identification of factors that degrade unit status.(3) Assists the identification of resource shortfalls, if any, by comparing the actual levels of personnel and

equipment assets in units with the wartime requirements.(4) Assists HQDA and intermediate commands to allocate resources.(5) Assists senior decisionmakers to judge the employability and deployability of reporting units.e. Reports submitted in accordance with this regulation satisfy—(1) The requirements of the Army portions of the Chairman of the Joint Chiefs of Staff Instruction (CJCSI) 3401.02

and CJCSM 3150.02.(2) HQDA requirements for timely operational management information.(3) Unit status information requirements established by section 117, title 10, United States Code.f. Because USRs in GSORTS are part of the Joint Staff/Department of Defense (DOD) readiness reporting system,

reporting criteria and guidelines are standardized for all Services to the extent possible. A major goal of GSORTS is to

1AR 220–1 • 15 November 2001

provide useful and accurate information to the war-fighting CINCs regarding the status of the units they will receive intheater, to include accurate estimates of how long it will take for those units to become fully METL trained. Theprescribed standard that each reporting unit commander must use as the basis for determining unit status or forestimating required training days is the wartime mission requirement for which the reporting unit was organized ordesigned. The procedures and standards for measuring and reporting unit status are fixed by JCS and Service policyand cannot be modified by the reporting units without authorization.

(1) Accordingly, for USR purposes, the determination of the unit’s resource and training status levels and the overallunit status level will be accomplished only by measuring current resource and training status levels against assignedwartime mission requirements. Furthermore, unit status determinations will be based only on the unit’s designedwartime organization as established by the applicable modification table of organization and equipment (MTOE) or thetable of distribution and allowance (TDA).

(2) When deployed as a task force (TF) or other ad hoc organization for peacetime operational requirements (that is,smaller-scale contingencies (SSC), military operations other than war (MOOTW), and stability and support operations(SASO)), commanders of reporting units will continue to report (in the USR) the status of resources and training fortheir units measured against the wartime mission requirement and based on the actual MTOE/TDA unit organizationthat has a mission assigned by the Joint Strategic Capabilities Plan (JSCP). Ad hoc organizations are those forces/elements that have been tailored and oriented toward a specific operational requirement developed in support of aJSCP-assigned mission. Even if the TF or ad hoc unit is operating under a derivative unit identification code (DUIC)and is reporting its status in accordance with DUIC reporting procedures established in paragraph 11–6, the status ofresources and training will be reported by the parent UIC organization from which the subordinate elements came, andthese reports will reflect the status of resources and training measured against the wartime requirements.

(3) In accordance with CJCSI/CJCSM policy requirements, the category level (C-level) reported in the USR is notused to indicate a unit’s ability to accomplish or sustain currently assigned peacetime operational requirements.Commanders of units that have been assigned or that are currently conducting a peacetime operational deployment willuse the “percent effective” (PCTEF) data field to report their assessments of the readiness of their units to undertakethe peacetime operational deployment in accordance with the provisions of paragraph 11–3.

(4) Guidance for unit status reporting contained in the Army’s disengagement plan has been incorporated intoprovisions of AR 220–1 where applicable. This guidance requires that commanders of Army units, in coordination withtheir MACOM, will consider the timelines established for the recovery, reconstitution, and redeployment of their unitswhen determining the availability of personnel, equipment, and subordinate elements for USR purposes. (See para3–3.) Additionally, commanders of major combat units that are preparing for, conducting, or recovering from peace-time operational deployments will use the policy guidance in paragraph 11–4f to determine their units’ training levels.

1–2. ReferencesRequired and related publications and prescribed and referenced forms are listed in appendix A.

1–3. Explanation of abbreviations and termsAbbreviations and special terms used in this regulation are explained in the glossary.

1–4. Responsibilitiesa. Deputy Chief of Staff for Operations, and Plans (DCSOPS) will—(1) Develop policies, standards, and procedures for reporting unit status.(2) Collect unit status data, make audit checks for accuracy, and maintain automated historical records.(3) Ensure that required reports are submitted to JCS in a timely manner.(4) Process and distribute unit status data in a usable format to requesting Department of the Army agencies and

commands.(5) Establish and maintain an automated methodology for collecting, reviewing, and analyzing unit status data.(6) Develop and issue guidance for the use of unit status data during mobilization, contingency operations, the

deliberate planning process, and post mobilization.(7) Act as focal point for developing procedures to use unit status data as part of the Army Readiness Management

System (ARMS) and to improve the status of Army units.(8) Consider the impact on unit status when making planning, programming, and budgeting decisions.(9) Keep the Army leadership apprised of the status of Army units.(10) Task Army staff agencies and MACOMs to provide supplemental data, analyses of unit status data, and

recommendations on how to improve unit status levels.(11) Incorporate unit status reporting into exercises.(12) Approve unit inactivation, activation, conversion, reorganization, and similar actions to minimize adverse

impact to unit readiness status.(13) Ensure that hardware procurement required to process status reports and monitor unit status data follows the

standard bottom-up process and is based on the specific software and infrastructure requirements of individual units.

2 AR 220–1 • 15 November 2001

Top-down push of automatic data processing (ADP) hardware will be accomplished in highly exceptional situationsonly.

(14) Issue timely guidance after the initiation of an SCC that identifies unit status reporting requirements foremployed/deployed units, to include personnel and equipment availability criteria and guidance for disengagement.

(15) Develop and implement a training program for the Army Status of Resources and Training System (ASORTS)and the Personal Computer Army Status of Resources and Training System (PC–ASORTS).

b. Army staff principals, to include the Chief, U.S. Army Reserve (CAR) and the Director, Army National Guard(DARNGUS) will—

(1) Assign specific staff responsibilities for monitoring and using unit status data within their respective areas ofresponsibility.

(2) Use unit status data to identify problem areas and perform analyses to determine root causes and possiblesolutions.

(3) Set and meet milestone dates for correcting problem areas.(4) Consider problems identified in unit status reports and the status of Army units when developing plans and

programs.(5) Assist the Office of the Deputy Chief of Staff for Operations and Plans (ODCSOPS) in the development of

procedures for using unit status data as part of the ARMS and improving the status of Army units.(6) Review unit status reporting policy guidance and submit recommended changes, as appropriate.c. Commanders of Army major commands and Chief, National Guard Bureau (CNGB) will—(1) Assign specific staff responsibilities for supervising and coordinating the Unit Status Reporting System within

their commands.(2) Ensure that subordinate units comply with unit status reporting requirements, to include the submission of

accurate reports in a timely manner.(3) Monitor the status of assigned units, and analyze and correct noted problem areas.(4) Report unresolved unit status conditions to the appropriate Army staff agency.(5) Manage resources to improve the status of assigned units.(6) Consider problems identified in unit status reports and the status of assigned units when developing plans and

programs.(7) In coordination with HQDA ODCSOPS, manage unit inactivations, activations, conversions, reorganizations, and

similar actions to minimize the impact on unit status.(8) Review unit status reporting policy guidance and submit recommended changes as appropriate.(9) Incorporate unit status reporting into exercises.(10) Assist U.S. Army Training and Doctrine Command (TRADOC) and HQDA to determine the squads, crews,

teams, and/or systems that should be reportable in USR training data and the manning and qualification criteria thatshould be established for these elements and/or systems.

d. Commander, U.S. Army Training and Doctrine Command (TRADOC) will—(1) Recommend to HQDA (DAMO–FMF), the equipment readiness code (ERC) criteria for this regulation based

upon unit primary mission tasks and criticality of equipment to accomplish those tasks. (As a general policy, allequipment listed on the unit’s table of organization and equipment (TOE) is considered the minimum mission-essentialequipment required for the unit to execute its primary combat tasks and provide sustainment capability.)

(2) Establish the criteria for pacing items to be listed as a guideline in appendix C for use by the U.S. Army ForceManagement Support Agency (USAFMSA) in appropriate requirements and/or authorization documents, such as theTOE, MTOE, and TDA.

(3) Provide input to determine minimum TOE wartime personnel requirements for combat support/combat servicesupport (CS/CSS) functions through the manpower requirements criteria (MARC) program. (These requirements areincluded in the MTOE required strength column against which readiness is measured.)

(4) Recommend to HQDA, ODCSOPS (DAMO–TR), the squads, crews, teams, and/or systems that should bereported in USR training data and the manning and qualification criteria for these elements and systems.

e. Commander, U.S. Army Force Management Support Agency will—(1) Develop and document, in coordination with the TRADOC proponent, TOE, MTOE, and TDA for Army units.(2) Use guidelines, outlined in appendix C, to determine equipment pacing items for type units and identify them in

the appropriate requirements and authorization documents (MTOE, TOE, and TDA). As a general policy, all equipmentlisted on the unit TOE is considered the minimum mission-essential equipment to allow the unit to execute its primarycombat tasks and provide sustainment capability.

(3) Determine minimum TOE wartime personnel requirements for CS/CSS functions through the manpower require-ments criteria (MARC) program in conjunction with the TRADOC proponent. These requirements are included in theMTOE required strength column against which readiness is measured.

f. Unit commanders will—

3AR 220–1 • 15 November 2001

(1) Maintain the highest unit status level possible with the resources provided.(2) Review the status reports of subordinate units for accuracy and for compliance with applicable requirements.(3) Distribute unit equipment and resources against mission-essential requirements on a priority basis.(4) Train to the highest level possible with the resources that are available.(5) Update unit status between regular reports, as required.(6) Ensure that the unit has the necessary computer hardware, software, and trained personnel to process and submit

the USR and related ASORTS reports.

1–5. Concepta. Designated MTOE and TDA units will submit recurring unit status reports in accordance with the guidance

contained in this regulation. These reports reflect the reporting unit commander’s assessment of the unit’s overall statusdetermined by using established procedures to compare selected personnel, equipment, and training factors to wartimerequirements. These reports are reviewed by commanders at higher levels and are placed into the ASORTS database.Currently, ASORTS is not electronically linked to any other unit-level system, and no such linkages are planned. Theprimary purpose of the ASORTS database is to report and maintain unit status information; however, ASORTS alsoserves as the master database to record unit identification codes (UICs). Instructions and procedures for UIC registra-tion will be addressed in a separate DA publication.

(1) Unit status reports are designed to measure the status of resources and training in a unit at a specific point intime. The report should not be used in isolation when assessing overall unit readiness; it is only one aspect in thebroader concept of strategic readiness.

(2) Unit status reports provide a timely single source document for assessing key elements of a unit’s status.However, these reports do not contain all of the information needed to manage resources. They identify potentialproblem areas, but in many cases these problem areas must be examined using more detailed personnel, logistical, andtraining management systems to determine causes and solutions.

(3) When a unit is called up, mobilized, or deployed, peacetime reporting procedures are modified. (See para 9–8.)b. The Army’s unit status objective is to develop and maintain units at the best status level possible, considering

contingency requirements and available resources. To conserve resources, early deploying units that support contin-gency plans are normally maintained at the highest resource levels. Other units are resourced at lower levels inconsonance with their deployment timelines and the assigned authorized level of organization (ALO). (ALOs arediscussed in chapter 2.) No unit is expected to attain a unit status level that exceeds the level at which it is resourced.For example, a unit resourced at ALO 3 is not expected to achieve an overall C-level better than C-3 because of theALO-related constraints on its personnel and equipment authorizations.

1–6. Unit status levelsa. The status of each of the three measured resource areas (personnel, equipment-on-hand, and equipment servicea-

bility) and the training status are determined by using the criteria provided in this regulation. Each commander alsodetermines an overall unit status level by considering the status of the unit’s measured resource areas and trainingstatus and by applying his professional judgment. Remarks will be submitted to clarify category levels.

b. The MTOE or TDA is the unit’s basic authorization document. This document will be the basis for USR systemcomputations.

c. The commander has the authority to report unit status against the current MTOE/TDA or, with MACOMapproval, a new MTOE/TDA (prior to its effective date (e-date)), if, in the opinion of that unit commander, the unitmost closely resembles the new MTOE. However, reporting against future MTOE will not result in a degraded overallreadiness status level below C-3. (Note that unit commanders require NGB approval to report unit status against newMTOE/TDA prior to e-date.) Once a commander reports the unit’s status based on the new MTOE/TDA, he or shemust continue to do so and will not revert to reporting against the earlier structure, unless specifically directed by theMACOM or NGB.

d. Numerous automated systems are available to assist in the preparation of USRs. These systems create and updatetheir databases from The Army Authorization Documents System (TAADS) database, which enables centralizedmanagement. The logistic systems are the Distribution Execution System (DES), Requisition Validation (REQVAL)System, LOGTAADS file, Standard Property Book System-Redesign (SPBS-R), and the Unit Level Logistics System(ULLS). The personnel system is the Standard Installation Division Personnel System (SIDPERS). These systems,whenever possible, should be used. Each command is responsible for the accuracy of these automated systems.

e. In case of a conflict between the hard-copy-approved TAADS and the LOGTAADS provided to SPBS-R, thepaper copy MTOE/TDA will be used until the differences have been resolved.

1–7. Personal Computer/Army Status of Resources and Training Systema. PC/ASORTS is the primary means for preparing and submitting unit readiness reports. The system provides an

automated means for personnel at any Army unit, to input, update, and/or calculate USR data as required by governing

4 AR 220–1 • 15 November 2001

regulations. PC/ASORTS allows for more accurate and less data entry for each report that is generated. The system isinteractive and provides immediate feedback and error detection as data is entered.

b. Reporting instructions contained in this regulation will describe the manual system using DA Form 2715 (UnitStatus Report). PC/ASORTS has automated many of the manual functions, and all pages of DA Form 2715 arereplicated on the PC/ASORTS menu screens.

c. The reports generated using the PC/ASORTS software may be classified in accordance with paragraph 2–7. Thecomputer where this software is resident and the magnetic media (hard drives and floppy disks) must be accredited,marked, and protected in accordance with AR 380–19.

Chapter 2General Instructions

2–1. The unit status reporta. Reporting units use PC/ASORTS or DA Form 2715 to report the status of resources and training.b. Chapters 3 and 9 provide additional instructions for reporting units. The chapters applicable to each measured

resource area (that is, PER, EOH, and ES), to the unit training status, and to special reporting situations (that is,mission accomplishment estimate (MAE), composite reporting, deployed unit reporting, and so forth) provide usefulexamples and specific instructions for entering data on DA Form 2715 that are directly related to the subject matteraddressed in that chapter. Report types are explained in paragraph 2–4.

2–2. Units required to submit unit status reportsa. MTOE units, such as battalions, separate companies, separate detachments, or equivalent size units (parent units),

that are organic to a division, regiment, separate brigade, or special operations forces (SOF) group/regiment/commandare required to submit USRs. These units are identified by a unit identification code (UIC) ending in “AA.”

(1) MTOE units not organic to a division, regiment, separate brigade, or SOF group/regiment/command that arecompany-size units or larger and are parent units (AA-level UIC) are required to submit USRs. Parent-level detach-ments and parent-level MTOE units that are deployable under any joint operations plan will submit reports.

(2) MACOMs can designate additional units/elements or detachments as reporting units. Reports from such desig-nated units will be forwarded to HQDA.

b. Combat support (CS), combat service support (CSS), and certain medical detachments (identified by an AA-levelUIC) that are like-type units may, with MACOM approval, submit a single consolidated report under a designated AA-level UIC. Such consolidated reports must be identified to HQDA and the units covered by the consolidated reportmust be identified by UIC in that unit’s READY/(GENTEXT) remarks.

c. Divisions, regiments, separate brigades, special operations forces groups/regiments/commands, divisional brigadesoperating separately, and armored cavalry regiments will prepare composite reports. These units are normally identifiedby a UIC ending in “FF.”

d. Multi-component units, regardless of component (Active component (AC), Army National Guard of the UnitedStates (ARNGUS), and U.S. Army Reserve (USAR)) will submit a single consolidated report through the componentheadquarters exercising command and control. AA-level and FF-level reports will be submitted in accordance with theinstructions in table 2–1.

e. ARNGUS units (AA-level) will continue to report through ARNGUS reporting channels in accordance with theapplicable policy guidance and instructions in table 2–1.

f. TDA units that are deployable and/or apportioned to a joint operations plan will report against the unit’s currentTDA authorization.

g. MTOE headquarters units whose subordinate units report individually will submit a report for the unit headquar-ters only if it is a separate company or unit of equivalent size.

h. Training divisions and brigades will submit a report annually in October. Company-size or larger (AA-level) unitssubordinate to an USAR training division or brigade will submit one report annually in October.

i. Units that are parent (AA-level) units and organized at ALO Z will submit one report annually in October. ALO Zunits are authorized to report C–5 status without prior approval. (See para 2–10 for additional information regardingALO.)

j. All USAR TDA medical (including augmentation) units with an “AA” UIC will submit reports.k. Army pre-positioned stocks (APS) with a UIC ending in “FF” will submit a composite report. MTOE unit sets

within the APS with UICs ending in “AA” will submit a quarterly unit status report, monthly validations, and changereports, as necessary. (See para 2–4c.)

5AR 220–1 • 15 November 2001

Table 2–1Report submission timelines

Type report Active component (AC) Reserve component (RC) Army pre-positioned stocks (APS)

Regular—Provides key status ofAA-level units

AC units submit as of 15th ofmonth. 96-hour reporting (Seenote 2.)

RC units submit as of the 15thday of January, April, July, andOctober. 96-hour reporting (Seenote 2.)

APS units submit as of 15th dayof January, April, July, and Octo-ber. 96-hour reporting (See note2.)

Initial—1st regular report Newly activated AC units submitas of the 15th of month after ac-tivation. 96-hour reporting (Seenote 2.)

Newly activated RC units submitas of the 15th of month after ac-tivation. 96-hour reporting (Seenote 2.)

APS units submit as of the 15thday of January, April, July, andOctober after establishment. 96-hour reporting (See note 2.)

Composite— Provides key sta-tus of FF-level units

AC units submit as of the 15thof month. 96-hour reporting(See note 2.)

RC units submit as of the 15thday of January, April, July, andOctober. 96-hour reporting (Seenote 2.)

APS units submit as of the 15thday of January, April, July, andOctober. 96-hour reporting (Seenote 2.)

Change— Required whenC–level changes are identified

AC units submit upon occur-rence. 24-hour reporting. (Seenote 1.)

RC units submit upon occur-rence. 24-hour reporting. (Seenote 1.)

APS units submit upon occur-rence. 24-hour reporting. (Seenote 1.)

Change—(See note 5.) Re-quired when changes to a re-source area level or to the train-ing level (not affecting the C-lev-el) are determined

AC units submit upon occur-rence. 24-hour reporting. (Seenote 1.)

RC units submit when the nextmonthly report is due, unless aregular report is due. 96-hourreporting. (See notes 2 and 5.)

APS units report when the nextmonthly report is due, unless aregular report is due. 96-hourreporting. (See notes 2 and 5.)

Validation— Submitted by RCunits and APS units

RC units submit as of the 15thday of February, March, May,June, August, September, No-vember, and December (if sta-tus has not changed since thelast report was submitted). 96-hour reporting (See note 2.)

APS units report as of the 15thday of February, March, May,June, August, September, No-vember, and December (if statushas not changed since the lastreport was submitted). 96-hourreporting (See note 2.)

Deployed— Submitted by AA &FF units deployed away fromhome station and when di-rected. (See chapter 11.)

AC units report as of the 15thday of month. 96-hour reporting(See note 2.)

RC units report as of the 15thday of month. 96-hour reporting(See note 2.)

Notes:1 24-hour reporting means that the report is due to HQDA within 24 hours of the as-of date.2 96-hour reporting means that the report is due to HQDA within 96 hours of the as-of date.3 Called-up or mobilized units submit a regular report within 24 hours of the arrival of the advance party at the mobilization station.4 Augmentation carrier units or units activated under a carrier UIC do not submit reports.5 RC units will report any changes to the measured resource area levels or to the training level that do not affect the overall C-level in the next monthlyreport due (that is, either in a change report submitted as of the 15th of February, March, May, June, August, September, November, or December, or in aregular report submitted as of the 15th of January, April, July, or October).

2–3. Units excused from submitting unit status reportsa. In highly unusual cases (for example, complex unit relocation or other special situation when exceptional

circumstances degrade or temporarily prevent the unit commander from accurately assessing the status of his or herunit), units or elements of units may be excused from recurring reporting requirements. Forward all requests forexemption through the responsible MACOM to HQDA, Force Readiness Division, ATTN: DAMO–ODR, 440 ArmyPentagon, Washington, DC 20310–0440. HQDA Force Readiness Division will coordinate the request for exemptionwith J–3, JCS for concurrence prior to granting final approval. Units will continue to submit required reports until theyreceive final approval of their request for exemption. Change and validation reports will be submitted as required bytable 2–1.

b. Units submitting composite reports will include exempted units in their reports. The following rules apply—(1) To determine composite C-level, use the data submitted by the excused unit in its most recent regular or change

report.(2) Composite strength figures will include data from excused subordinate units.(3) Units will explain in the READY/GENTEXT remarks, (DA 2715, section C) when one or more subordinate

elements are excused from reporting. The ability of the parent unit to link up with the subordinate element(s) will beaddressed.

c. c. Units are not automatically excused from material condition status reporting, as required in AR 700–138, even

6 AR 220–1 • 15 November 2001

if they have been granted an exemption from unit status reporting under provisions of AR 220–1. A separate requestfor exemption from equipment reporting requirements under AR 700–138 is required. Approval authority is HQDA,DALO–SMR, for units of battalion size and larger. The MACOM is the approval authority for units smaller thanbattalion size.

2–4. Types of reportsThere are six types of reports: regular, initial, change, composite, validation, and deployed. All units required to submitUSRs in accordance with paragraph 2–2 of this regulation will report monthly (includes validation and change reportssubmitted by RC units during months when regular reports are not due). (Table 2–1 provides report submissiontimelines.)

a. Regular report.(1) Provides key status indicators for all AA-level units, to include status changes in AA-level RC units that do not

meet criteria requiring the immediate submission (that is, within 24 hours) of a change report. (See para 2–4c.)(2) Submitted to HQDA by all AA–level UIC units within 96 hours of the 15th of each month for AC units and

within 96 hours of the 15th of January, April, July, and October for RC units and Army pre-positioned stocks (APS).Note that a regular report also is used by RC AA-level units and APS to report status changes to resource areas notaffecting the C-level that are determined during the monthly reporting periods preceding regular report submission.

(3) All portions of sections A and B of DA Form 2715 must be completed.(4) Applicable portions of sections C and D (remarks) must be completed.(5) APS initial and regular reports will be submitted for equipment on hand and equipment serviceability data only

in accordance with chapters 5 and 6, respectively.b. Initial report.(1) The first unit status report submitted to HQDA by a unit is the initial report.(2) Units submitting an initial report will place an “A” in the transaction type field in section A: OVERALL set; and

section B: EQOHDATA, EQMCDAT, TRAINDAT set; READY & REASN remark to distinguish the initial reportfrom subsequent regular reports.

c. Change report.(1) A change report is required when a change occurs to the overall level (C-level) of an Army reporting unit (AC

and RC reporting units; AA-level and FF-level reporting units). When the overall C-level changes, a change reportmust be submitted within 24 hours of the occurrence of the change by all Army reporting units to report the C-levelchange.

(2) A change report also is required when a change occurs to a resource area level (PER, EOH, or ES) or to thetraining level, even if the C-level does not change. AC units will submit a change report within 24 hours of theoccurrence of such changes. RC units and APS will report changes to resource area levels or to the training level notaffecting the C-level by submitting a change report when the next monthly report is due (that is, on the 15th of themonth), unless the next monthly report due is a regular report, which also can be used to report such changes.

(3) A change report is prepared and submitted in accordance with the instructions in table 2–1. Units will advisetheir MACOMs when they have to submit a change report.

d. Composite report.(1) Composite reports are submitted by major combat units with UICs ending in “FF” (that is, divisions, regiments,

separate brigades, and combat units of equivalent size, and special forces groups/regiments/commands) within 96 hoursof the as-of date.

(2) The composite report provides an assessment of the status of the major combat unit based on the status of itssubordinate elements.

(3) Both Active component (AC) and Reserve component (RC) FF-level major combat units and FF-level APS willsubmit composite reports.

e. Validation report.(1) Validation reports are submitted by RC (ARNGUS and USAR) units and APS units in order to meet the

requirement for monthly reporting when there is no change in unit status from the last report submitted.(2) The validation report cannot be used if there is any change in the unit’s overall status (C-level), change in the

status level of any resource area (personnel, EOH, and ES), or change to the unit training level.(3) The validation report is specifically designed to recognize the reduced time and resources available to RC units

for both training and administration. RC units and APS submit regular reports on a quarterly basis and validationreports during months when quarterly reporting is not required and no status changes have occurred that requiresubmitting a change report.

f. Deployed report.(1) Units may use the deployed report format when deployed away from home station for operational requirements

or for training exercises. (See chapter 11.) CINCs/MACOMs may require deployed/employed units to submit a regularreport instead of a deployed report.

7AR 220–1 • 15 November 2001

(2) The deployed report allows the commander to continue to assess and report the status of resources and trainingin the deployed unit measured against the unit’s ability to perform the mission for which it was organized or designedwhile, concurrently, subjectively assessing and reporting the unit’s ability to undertake the current peacetime opera-tional deployment by reporting a percent effective level.

(3) Special instructions for when a unit is called-up, mobilized, deployed, or employed are provided in chapter 9.Detailed instructions for deployed reporting are provided in chapter 11.

2–5. Reporting channelsa. Reporting units will submit their unit status report by sending either a PC\ASORTS file or DA Form 2715 to the

installation or division level. The reports are converted to U.S. message text format (MTF) at the installation/divisionlevel and forwarded through the chain of command to the responsible MACOM for AC units, to the U.S. ArmyReserve Command (USARC) for USAR units, and through the responsible State adjutant general to the NGB forARNGUS units. The reports are then transmitted to HQDA where, in turn, they are transmitted to JCS. (See figs 2–1,2–2, 2–3, and 2–4; crisis and wartime reporting channels are depicted in fig 2–5.)

b. Units that are organic to major (FF-level) organizations required to submit a composite report (see para 2–4d andchap 10 of this regulation) and that are at installations or locations separate from their parent unit will submit their unitstatus reports through their parent unit for inclusion in the composite report. The operations and/or readiness elementsof all installations are required to provide support to tenant units in submitting their unit status reports. Reportingprocedures will be specified in memorandums of understanding or agreement when appropriate.

c. Company- or detachment-size units based in the continental United States (CONUS), organic to a parent unit butpermanently assigned to a location or installation separate from the parent unit, will report through the installation towhich assigned unless the reporting unit is an AC unit located on an installation under the control of a RC headquartersor is a subordinate unit/element of a multi-component unit. (AC reporting units that are located on installationscontrolled by a RC headquarters will report through their actual AC chain of command and provide a copy of theirreport to the installation for information only. Subordinate units/elements of multi-component units will report throughthe multi-component unit, regardless of the component exercising command and control). The composite report that issubmitted by the parent unit will not include these separate subordinate units, unless these units are expected to deploywith the parent unit. A copy of the unit status report will be provided to the parent unit for information only.

d. Multi-component reporting units will submit a single unit status report through the applicable higher headquarterswithin their respective component in accordance with the reporting channels depicted at figure 2–4. Organizations andelements not at the AA-level will submit appropriate feeder reports to the responsible AA-level reporting unit.

e. ARNGUS reporting units (FF- and AA-level) of integrated divisions will submit their USRs through theirrespective State adjutants general and provide copies to the integrated division headquarters for review.

f. APS custodians will submit their unit status reports to the Army Materiel Command (USAMC), which willforward the reports to HQDA.

8 AR 220–1 • 15 November 2001

Figure 2–1. Unit status reporting channels, Active Army and Army Reserve

9AR 220–1 • 15 November 2001

Figure 2–2. Unit status reporting channels, Army National Guard

10 AR 220–1 • 15 November 2001

Figure 2–3. Unit status reporting channels, ARSOF

11AR 220–1 • 15 November 2001

Notes:1 Units/elements that are not required to prepare and submit USRs will submit feeder data using the reporting channels outlined above.2 The “higher level headquarters within compo” is the headquarters at the next higher level in the same component as the reporting unit. For AC units, this isnormally the MACOM, installation/division, or brigade; for ARNG units, this is normally the State Adjutant General (TAG); for USAR units, this is normally theUSARC.3 For ARNG units, the MACOM is NGB. Only AC MACOMs can provide USR data “for info” directly to Unified Commands. NGB will provide an informationcopy of USR to FORSCOM.

Figure 2–4. Unit status reporting channels, multi-component units

12 AR 220–1 • 15 November 2001

Figure 2–5. Unit status reporting channels during wartime or crisis

2–6. Actions by higher commandersa. Commanders above the level of the reporting unit will not change the reported status levels of subordinate units

except to correct computation errors or administrative defects. The USR is intended to reflect the assessment of thecommander and will not be changed in any manner that will distort the report.

b. Next higher commanders (at installation/state, division level, or below) will review reports of subordinate unitsfor accuracy. They may provide additional information regarding the status of subordinate units on the (NARR) remark(DA Form 2715, section D).

c. Commanders above installation or division level who wish to submit comments on the status of reporting unitswill send them through the chain of command by separate communication.

d. For USR purposes, the State adjutant general will be considered the installation commander for ARNGUS units.USAR major subordinate commands (MSCs) will be considered installation commanders for USAR units. For CON-US-based AC/USAR Army special operations forces (ARSOF) units, the U.S. Army Special Operations Command(USASOC) will be considered the installation equivalent. U.S. Army Special Forces Command (USASFC) and U.S.

13AR 220–1 • 15 November 2001

Army Civil Affairs and Psychological Operations Command (USACAPOC) will be considered the USAR MSCequivalents. ARSOF units based outside the continental United States will submit USRs per current memoranda ofunderstanding/agreement.

2–7. Security classification and declassification of reportsa. The originator will ensure that the appropriate security classification, authority for classification, and the duration

of classification are assigned to each report.b. When referencing the entire Army, ARNGUS, USAR, or other large groupings (that is, a listing of 10 or more

AA-level units); current or projected C-levels; the mission accomplishment estimate (MAE); the status level of ameasured resource area; and/or references to deployability, employability, or inability to accomplish an assignedmission also will be SECRET.

c. The classification of the USR is based on the number/size of the units represented in the USR, not on the numberof reports. The security classification of squad/crew manning and qualification data reported in the USR is derivedsimilarly. The overall C-level, the level for any measured resource area and for any portion of the USR that reflectscurrent or projected unit status measurement or assessment, to include squad/crew manning and qualification data;MAE; and/or references to deployability, employability, or inability to accomplish an assigned mission will beclassified as follows—

(1) SECRET for any major combat units of divisions, separate brigades, special operations forces groups, regiments,and commands, divisional brigades (operating separately), armored cavalry regiments or larger units (FF-level UIC).

(2) SECRET for 10 or more battalion-sized, company-sized, or separate companies/detachments (AA-level UIC).(3) CONFIDENTIAL for one to nine battalions, two to nine company-sized or separate companies/detachments

(AA-level UIC).(4) UNCLASSIFIED for individual (that is, one) AA-level company, battery, troop, or detachment level. Reports

will be marked “For Official Use Only” (FOUO) and must be transmitted by secure means in accordance with AR380–19.

(5) Any request for C–5 status will be classified CONFIDENTIAL.(6) Reports associated with specific operations or exercises will be classified either with the classification of the

operation or exercise, or with the criteria established above, whichever results in the higher classification.d. Reports will be declassified as follows—(1) Information classified by authority of a system security classification guide (SCG) or similar authority will be

declassified in accordance with the SCG instructions.(2) Reports and levels described in subparagraphs a, b, c, and e above will be marked with a specific declassifica-

tion date. Classification will be downgraded, one level each 4 years. The intent is to make all data UNCLASSIFIEDwithin 8 years.

e. This regulation may be cited as the classification authority for USRs and all associated data.

2–8. Retention of reportsa. USRs will be retained on file for no less than 2 years at the installation and composite reporting level and for not

less than 6 months at individual reporting units. USRs will be destroyed in accordance with AR 380–5.b. Commanders at all levels may direct the retention of reports for a longer period of time. Storage of reports in

either paper or electronic form is permitted.c. Currently, HQDA retains unit status reports and the associated comments submitted by Army units to HQDA

after 1989. The Presidio Archive Center in California maintains data submitted earlier than 1989 on tape and inBernoulli disk format. Submit all requests for USR data that is not in the possession of the unit to HQDA, ForceReadiness Division (ATTN: DAMO–ODR), 440 Army Pentagon, Washington, D.C. 20310–0440.

2–9. Release of and access to GSORTS/ASORTS informationa. JCS Policy. The Joint staff, Services, unified commands, and combat support agencies may release GSORTS data

to members of DOD having a valid need to know and the appropriate clearance. Services may only release informationon their units and only that amount of information required to satisfy the requirement. JCS approval is required prior tothe release of any GSORTS data to any non-DOD requester or to any foreign agency.

b. HQDA requires Army units to obtain approval to release USR information outside of Army channels, to includerelease to both DOD and non-DOD agencies and to their sub-elements (that is, to other Services, Joint organizations,Members of Congress, and so forth). USASOC is authorized to release USR information to SOCOM. Requests forother approvals to release Army USR information outside of Army channels will be made in writing and will beforwarded to HQDA, ATTN: ODCSOPS Force Readiness Division (DAMO–ODR), 440 Army Pentagon, Washington,D.C. 20310–0440. ODCSOPS Force Readiness Division will obtain concurrence from J–3, Joint Staff, before approv-ing release of GSORTS/ASORTS information to non-DOD agencies.

14 AR 220–1 • 15 November 2001

2–10. Authorized level of organizationThe authorized level of organization (ALO) is an alphanumeric character that identifies the percentage of requiredpersonnel and equipment authorized to a unit. The authorized personnel percentage is based on the TOE requirement,while the equipment authorizations are specified by item, based on the personnel authorizations. The equipmentauthorization is 100 percent of requirements, except for personal items (weapons, protective masks, and so forth). If thepersonnel authorizations are decremented to the point where equipment could not be properly maintained/supported,then equipment authorizations may be decremented from 100 percent of that required. The determination of ALOs forArmy units is directly related to the policies contained in AR 71–32. A chart establishing the current percentages forthe various ALOs resides on the Force Management Bulletin Board (FMBB), which can be accessed at the followingWeb address: www.usafmsardd.army.mil.

Chapter 3Instructions for Reporting Units

3–1. Generala. USR system output. By completing the unit status report, unit commanders develop and report assessments of

their units’ ability to accomplish the wartime missions for which the units were organized or designed. Additionally,commanders of units assigned to conduct peacetime operational deployments use the percent effective (PCTEF) levelto report the status of their units’ ability to execute their current missions.

b. Tactical level capability. There are five overall status levels (C-1, C-2, C-3, C-4, and C-5) and level 6. Theselevels reflect the status of war-fighting resources required by the unit and the commander’s training assessment.Together, they indicate the unit’s tactical-level capability.

3–2. C-level definitionsa. CJCSM 3150.02 establishes five C-levels to show how well the reporting unit meets prescribed levels of

personnel strength, equipment availability, and unit training for the wartime mission.b. The C-1 level indicates that the unit possesses the required resources and is trained to undertake the full wartime

mission(s) for which it is organized or designed. The status of resources and training will neither limit flexibility inmethods for mission accomplishment nor increase vulnerability of unit personnel and equipment. The unit does notrequire any compensation for deficiencies.

c. The C-2 level indicates that the unit possesses the required resources and is trained to undertake most of itswartime mission(s) for which it is organized or designed. The status of resources and training may cause isolateddecreases in flexibility in methods for mission accomplishment, but it will not increase the vulnerability of the unitunder most envisioned operational scenarios. The unit would require little, if any, compensation for deficiencies.

d. The C-3 level indicates that the unit possesses the required resources and is trained to undertake many, but notall, portions of the wartime mission(s) for which it is organized or designed. The status of resources or training willresult in a significant decrease in flexibility for mission accomplishment and will increase the vulnerability of the unitunder many, but not all, envisioned operational scenarios. The unit would require significant compensation fordeficiencies.

e. The C-4 level indicates that the unit requires additional resources or training to undertake its wartime mission(s),but it may be directed to undertake portions of its wartime mission(s) with resources on hand.

f. The C-5 level indicates that the unit is undergoing a service-directed resource action and is not prepared, at thistime, to undertake the wartime mission(s) for which it is organized or designed. HQDA employs the force developmentprocess with the goal of “standing-up” units at the overall level of C–3 or higher. In many cases, actions affecting unitstatus can be synchronized so that transitioning units can shorten the time period in C-5 status or avoid C-5 statusentirely. (Refer to para 1–6c.) C-5 units are restricted to the following—

(1) Units that are undergoing activation, inactivation, or conversion.(2) Units that have their levels for authorized personnel and/or equipment established so that, even when filled to the

authorized level, the established level does not allow the unit to achieve level 3 or higher. (Units that are manned orequipped below ALO-3 level may meet these criteria.

(3) Units that are not manned or equipped but are required in the wartime structure (that is, COMPO 4 units).(4) Units placed in cadre status by HQDA.g. Level 6 indicates that one or more of the individual resource areas are not measurable, or, by Service direction,

are not measured. (For example, the equipment serviceability (ES) of a unit cannot be measured because a civiliancontractor performs maintenance for the unit or the unit is an opposing force (OPFOR) unit at a training center that hasno organic reportable equipment). Level 6 is not used as an overall category level. Although unmeasured resource areas

15AR 220–1 • 15 November 2001

are not reportable for USR purposes, commanders remain responsible for accountability and management of any Armypersonnel and equipment.

3–3. Standard rules and proceduresa. Calculation of resource levels. Units will calculate all resource levels against the established wartime require-

ments (cadre column for cadre units, TOE type B column for type B units, MTOE authorized column for APS, andMTOE/TDA required column for all other units), as stated in applicable authorization documents. The only exceptionto this basic rule is the ES determination that is calculated against EOH.

b. Activation/reorganization (within 12 months of e-date).(1) The objective of the Army force development process is to modernize the force without significantly degrading

unit readiness. Therefore, force development actions must be synchronized with and complemented by the availabilityof sufficient modernization equipment. Decisions regarding out-of-cycle reorganization and modernization must con-sider the potential of those actions to adversely affect the readiness of the units involved. In other than highlyexceptional circumstances, reorganization should not occur unless the personnel and equipment that are required tosupport the new organization are reasonably available. The force validation process exists to ensure that, under normalcircumstances, units are activated and reorganized at the C-3 level or higher.

(2) Parent (AA-level) units that activate/reorganize incrementally will report against their current full wartimestructure. (For example, a support battalion that activates one company at a time would report against its full battalionstructure.) When the AA unit more closely resembles the new organization than the old organization regardingstructure, manning, and equipment, the unit will obtain approval from the responsible MACOM (NGB for ARNGUSunits) to report as the new organization.

(3) Major combat (FF-level) units that activate/reorganize incrementally will include the additional subordinate unitsthat would be part of their force structure under a full wartime structure (less forward deployed brigades or battalions).

c. Availability of units (both personnel and equipment).(1) Parent units at the AA- and FF-levels will consider deployed subordinate units/elements available when the

subordinate units/elements are on operational deployments within any of the parent unit’s area of operations designatedby HQDA/MACOM in support of the Joint Strategic Capability Plan (JSCP).

(2) Subordinate units/elements (that is, non AA-level or FF-level units) deployed outside of all of the parent unit’sareas of operations will be considered non-available if, in the opinion of the parent unit commander, the deployedsubordinate units/elements could not rejoin the parent unit in an assigned area of operations as required by timelinesestablished by the time phased force deployment data (TPFDD) tables constructed for specific JCS-approved operationsplan (OPLAN) schedules. (For example, subordinate units/elements could not rejoin the parent unit at home station andmeet the available to load date (ALD) or could not join the parent unit in an area of operations in time to meet therequired delivery date (RDD).) Commanders of reporting units/elements that are deployed will obtain guidance fromtheir MACOMs to assist them in making this determination.

(3) Parent units at the AA- and FF-levels that are deployed outside of their designated areas of operations will beconsidered non-available if, in the opinion of the parent unit commander, redeployment to meet OPLAN schedulerequirements is not feasible. Commanders of such units will consider the specific guidance provided by theirMACOMs regarding timelines for disengagement, recovery, post-deployment training, reconstitution, and redeploymentwhen determining personnel and equipment availability for USR purposes.

(4) Parent units and subordinate units/elements away from home station to participate in training will be consideredavailable.

d. Rounding rule for decimals. Use the rounding rule for decimals when you use a table or accomplish calculationsin accordance with status level guidelines provided in this regulation: round numbers ending in 0.5 or more to the nexthigher whole number and round numbers less than 0.5 to the next lower whole number.

(1) When calculating percentages, perform the required division and multiply the number by 100; then round off tothe nearest whole number.

(2) When converting hours to days, divide the number of hours by 24 and round to the nearest whole number.

3–4. C-5 reporting instructiona. HQDA-related unreadiness. Units not ready because of HQDA actions or programs will report C-5 in accordance

with the instructions in table 3–1 below.

16 AR 220–1 • 15 November 2001

Table 3–1C–5 reporting

Item Inactivate Activate Conversions Other

Orders X X Xe-date set X X XApproval authorization MACOM note 1 MACOM note 1 MACOM note 1 HQDAEarliest report 365 days prior to e-date 30 days after e-date C-4 note 2Latest report 90 days prior to e-date 30 days after e-date N/A N/AMaximum duration note 3 note 3 note 4Report until Inactivation C-3 C-3

Notes:1 MACOM approval of C-5 reporting must comply with the criteria and policy guidance in paragraph 3–4.2 The first possible report date.3 For Active Army, 1 year; for Reserve component, 3 years.4 Reviewed by MACOMs monthly to ensure compliance with established milestones by their C–5 reporting subordinate units and to identify requirements forextension requests.

b. Activations/reactivations. MACOMs will direct units undergoing activation/reactivation at an overall level of lessthan C-3 (that is, C-4) to report C-5 until they attain a minimum level of C-3 in all resource areas (PER, EOH, and ES)and for the training level. Using C-5 begins when the unit initially activates or reactivates, and continues until it hasachieved and can report an overall status level of C-3. After achieving and reporting a C-3 status level, the unit mustreport C-4 and cannot reporr C-5 if unit status subsequently deteriorates below the C-3 level (that is, falls to C-4). Themaximum time that a unit may report C-5 is 1 year for AC units and 3 years for RC units.

c. Inactivations/discontinuations. MACOMs may direct units programmed for inactivation/discontinuation to reportC-5 when the unit reaches level 4 in any measured area level (except authorized 6s) and is within 365 days of theeffective date (e-date) of inactivation/conversion. The unit must possess orders directing the action or be on a HQDA-approved command plan (RC only) and have a confirmed e-date prior to reporting C-5. (Note that TDA units do notinactivate; they discontinue.)

(1) All units will report C-5 at 90 days from e-date and will continue to report until the unit has been inactivated/discontinued.

(2) C-5 inactivating/discontinuing units may be excluded from composite reports if they are within 180 days of theire-date. The unit rendering the composite report will continue to report the number of C-5 units in their READYSEGset, section B. This allows for continued accountability of C-5 units. C-5 reporting units will continue to report inaccordance with this regulation.

d. Conversions. MACOMs will direct units undergoing conversion to report C-5 when they reach level 4 in anyresource area or for the training level, as a result of the conversion. They will continue to report C-5 until they againachieve at least a level 3 in all resource areas and for the training level or on a date set by HQDA. The maximum timethat a unit may report C-5 is 1 year for AC units and 3 years for RC units. Conversions are defined as a major unitchange to another MTOE, or a complete change in the type of unit or branch.

e. Options for special units. Units that have their levels for authorized personnel and/or equipment established sothat, even when filled to the authorized level, the established level does not allow the unit to achieve a level 3 or higher(includes type B, medical, transportation, and cadre units), will report under one of the two options explained below—

(1) The unit may subjectively upgrade the overall C-level to a C-3 or higher C-level and report resource areas attheir computed levels if, in the commander’s judgment, the unit is resourced sufficiently to perform major portions ofits wartime mission. If the commander later decides not to upgrade subjectively, he must notify his MACOM andrequest to revert to C-5 status reporting.

(2) The unit may report C-5 overall and level 5 for the appropriate measured/resource area(s). Units that report C-5overall must also report the appropriate driving measured/resource area(s) as level 5.

f. HQDA-directed action or program. MACOMs will inform HQDA of units that they have approved to report C-5as a result of undergoing a HQDA-directed action or program. A C-5 level will be reported until the unit is able toreport C-3 or higher in all four measured areas. MACOMs, installations, and units will determine the effect of HQDA-directed program/actions prior to e-date. If a C-4 level will result, MACOMs may approve C-5 reporting, or request achange to the e-date from HQDA, or continue the action at a C-4 level. MACOMs must review the status of unitsdesignated C-5 every 3 months to determine if a C-5 level is still warranted and to evaluate actions being taken toimprove the status of the unit.

g. Units reporting C-5. Units reporting C-5 must provide reasons in their READY/GENTEXT remarks indicatingwhy the unit is C-5, to include a brief description of the reason or action that caused the level 5 to occur in a measuredarea. Also state the anticipated date of resolution (for example, the fielding date if a modernization program is pending)or authority for continued C-5 reporting. A unit that reports level 5 in any measured area must also report C-5 overall.

17AR 220–1 • 15 November 2001

In addition the code “N” must be used in field 6 (REASN) of the OVERALL set of DA Form 2715, section A. Unitsmust provide e-date of MTOE/TDA of the initial action.

h. MACOMs reporting C-5 . MACOMs must submit a request to HQDA for their units to continue to report C–5beyond the time limits established for C-5 reporting in table 3–1. Requests will be forwarded to HQDA, ForceReadiness Division, (ATTN: DAMO–ODR), Washington, D.C. 20310–0400. DAMO–ODR will coordinate with JCSregarding the request.

3–5. Level 6 reportinga. When it is not possible to determine personnel or equipment levels (for example, maintenance records are

accidentally destroyed or the unit maintenance system does not provide the required records), report level 6 andconsider the area when determining the overall unit level. Level 6 may not be used for the READY (section A, field 5,OVERALL set). When level 6 is reported in a resource area, a level 6 cannot be reported in field 6 of the OVERALLset. Use regular procedures for other measured areas and provide narrative comments in the remarks section of thereport on the unit’s ability to accomplish assigned missions.

b. Units submitting composite reports will omit subordinate units reporting level 6 from specific resource areacomputations when the unit commander determines that this will produce a more accurate reported level.

3–6. Reporting dataa. Reporting units use DA Form 2715 to prepare unit status reports. Data on these forms are converted to MTF

format for transmission to MACOMs, HQDA, and JCS. The relationship between report types and data fields is shownat table 3–2.

Table 3–2Relationships between report types and report forms/sets/remarks

DA Form 2715 Regular reports Change reports

DA Form 2715 Regular reports Change reportsSection A (JCS data) Section A (all sets) Section A (all sets)Section B KA1 (item/rpt type) KA2 (item/rpt type)Army data All sets All setsSections C and D READY, 2PSPER, 2PIESTAT,

2ERCFOUR, 2EOHSHRT,NBCEQPT, 2PIERRAT,2ERCERRT, TRRAT, PSPER,GENTEXT remarks, 2RQPER,2ADDSKIL. Others as required

Appropriate remarksAppropriate remarkswith changed data

b. DA Form 2715, section A, is used to report standard JCS data. All units submitting readiness reports, to includecomposite reports, use these data elements.

c. DA Form 2715, section B, is used to report Army-unique data. This part of the form provides essentialsupplemental data to help Army agencies analyze a unit’s status. Army-peculiar data is reported, but it is currently notstored by JCS.

d. DA Form 2715, section C, is used to report unit commander’s READY and REASN GENTEXT remarks.e. DA Form 2715, section D, is used to report all measured/resource area remarks and free text remarks.f. NARR GENTEXT remark is used by the reporting unit’s next higher commander to comment on any data field

(ASPER, MSPER).

3–7. Regular reports prepared by battalion-, squadron-, and smaller-size unitsa. General instructions. This section provides general instructions for preparing DA Form 2715, sections A and B,

for units of battalion- and squadron-size and smaller. (See figs 9–1 and 9–2.) Instructions for completing resource-area-related entries are covered in chapters 4 through 7.

b. SORTUNIT set, section A, field 1, ANAME (name of unit). No entry is allowed in this field because it isautomatically generated by PC/ASORTS.

c. SORTUNIT set, section A, field 2, unit identification code (UIC). The “W” is preprinted. Enter the UIC of yourhigher headquarters. If unknown, leave blank.

d. SORTUNIT set, section A, field 3, SEQNO (report number). Leave blank if DA Form 2715 is to be sent toanother headquarters for conversion to MTF. Headquarters submitting reports in PC/ASORTS format will enter a three-character number showing the report number in which the unit report will be submitted.

e. SORTUNIT set, section A, field 4, DTG (date, time, group when report was submitted). No entry is allowed in thisfield because it is automatically generated by PC/ASORTS.

18 AR 220–1 • 15 November 2001

f. SORTUNIT set, section A, field 5, SCLAS; OVERALL set, section A, and ARMYRPT SET, section B; field 1,CLASSIFICATION . Enter “C” for CONFIDENTIAL for battalion- and squadron-size units. Enter “U” for UNCLASSI-FIED for smaller size units. Enter “S” for SECRET if the report contains secret data owing to association with aclassified plan, operation, or exercise. (See para 2–8 for further guidance.)

g. RPTDUIC set, section A. field 1, UIC (unit identification code). Enter UIC of unit being described by the data inthe report.

h. RPTDUIC set, section A, field 2, NOCHG (no change indicator field). All reserve units and APS will enter“VALID” in this field to validate previously reported unit data when the unit is submitting a monthly validation report.Enter “OVALL” for the quarterly regular reports and change reports.

i. OVERALL set, section A, field 2; and PERSDATA set, EQOHDATA set, EQMCRDAT set, and TRAINDAT set,field 1, TRANS TYPE. Enter “A” (initial), “C” (regular or change), or “D” (delete). Normally, the entry will be “C,”meaning a recurring or change report is being submitted.

Chapter 4Personnel Data

4–1. GeneralThe personnel resource area is one of three resource areas (that is, PER, EOH, and ES), along with the training status,that is a factor in determining a unit’s overall C-level. The personnel factor (P-level) is calculated by determiningassigned strength, then assessing the available strength, the available qualified military occupational specialty (MOS)strength, or MOSQ strength, and the available senior grade strength against wartime requirements. In the computationof personnel data, commanders are directed not to move soldiers from one unit to another, breaking up cohesive groupssolely to cross-level for unit status reporting purposes.

4–2. Determine required strengthUse your unit’s MTOE/TDA to determine required strength (cadre column for cadre units, TOE type B column fortype B units, and MTOE/TDA required column for all other units). For MTOE organizations, additions provided byaugmentation TDA for non-TOE missions are excluded from required strength computations.

4–3. Determine assigned strength percentagea. Assigned strength percentage (ASPER) equals assigned strength divided by required strength. Assigned strength

for Active Army units equals the accountable strength of the latest personnel control number (PCN) (AAA–162, unitpersonnel accountability report), adjusted to the “as-of” date of the status report by adding gains and subtracting lossesoccurring since the date of the unit strength RECAP, part II. (See table 2–1 of chap 2 for additional information.)

b. Reports from SIDPERS ARNG and TAPDB–2 USAR will be used to obtain assigned strength data for RC units.Assigned strength for USAR units includes Active Guard and Reserve (AGR) and AC personnel assigned on a separateTDA who would deploy with the unit if it was mobilized on the “as-of” date of the report. Inactive National Guard(ING) personnel will not be included in strength computations or figures in this report.

c. Army medical units (to include main and forward support battalions assigned medical personnel) that arescheduled to receive Army Medical Department (AMEDD) Professional Filler System (PROFIS) personnel (in accord-ance with AR 601–142) will include them in assigned strength computations as follows—

(1) Compute assigned percentage on the basis of assigned personnel and PROFIS personnel who are designated, byname, for assignment to the reporting unit under alert, deployment, or combat conditions. Individual personnel attachedto another unit under TCS orders for deployment will be counted as assigned, but not available by the parent unit. Thedeploying/mobilizing unit will not count these soldiers as assigned, but it will count them as available.

(2) Commanders will use the current PROFIS roster from the Office of The Surgeon General (OTSG) MedicalOccupational Data System (MODS)-approved PROFIS automated database to identify PROFIS individuals designatedfor required MTOE positions. The PROFIS roster must be updated monthly and must be dated within 30 days of theUSR “as-of” date. Personnel will not be identified in more than one unit.

(3) USAR AMEDD units with personnel assigned and attached to the national AMEDD augmentee detachment(NAAD) will count those personnel as assigned and available for alert and deployment.

4–4. Determine available strength percentagea. Available strength percentage (AVPER) equals available strength divided by required strength. Available strength

is the portion of a unit’s assigned and attached strength available for deployment or employment with the unit toaccomplish its wartime mission. Individual personnel attached to another unit under temporary change of station (TCS)orders or deployment will be counted as assigned but not available by the parent unit. The deploying/mobilizing unitwill not count these soldiers as assigned, but it will count them as available. Available strength may exceed assignedstrength in units with attached personnel. RC personnel attached to another unit will be counted and reported by the

19AR 220–1 • 15 November 2001

parent unit as assigned and available for deployment and mobilization; the unit of attachment will not count and reportattached soldiers as assigned or available. Soldiers in multi-component units who are available at home station areconsidered available.

b. AA-level and FF-level units will consider deployed subordinate units/elements available when the subordinateunits/elements are on operational deployments within any of the parent unit’s joint strategic capability plan (JSCP)designated areas of responsibility (AORs) and will provide mandatory AVPER remarks to address these situations. Ingeneral, subordinate units/elements deployed outside the parent unit’s AORs are considered as not available. However,commanders of such units will consider the specific guidance provided by their MACOMs regarding timelines fordisengagement when determining personnel availability for USR purposes. Subordinate units/elements away from homestation participating in training exercises will be considered available. Commanders with units/elements deployedwithin the JSCP AOR will provide the number of soldiers deployed in the mandatory personnel reporting remarks asAVPER remarks.

c. Appendix D provides criteria for determining personnel availability. PROFIS and NAAD personnel will beconsidered available if they meet the requirements of paragraph 4–5c(1). Soldiers stabilized in accordance with theArmy stabilization policy will be considered available.

d. Chapter 11 establishes USR requirements for units before, during, and after deployment. Commanders of AA-level units that have subordinate elements or individual soldiers absent from their units because of a peacetimeoperational deployment will use the reason codes in table E–2 in accordance with the instructions in paragraph 11–3 toreport the percent of their units’ personnel that is operationally deployed

4–5. Determine available military occupational specialty qualified percentagea. Available military occupational specialty (MOS) qualified (MOSQ) personnel percentage (MSPER) is based on a

comparison of available MOS-qualified personnel and required MOS-qualified personnel. Available MOSQ strengthcannot exceed available strength.

b. Determine the number of MTOE/TDA personnel spaces required by rank (commissioned officer, warrant officer(WO), and enlisted) and by military occupational specialty code (MOSC).

c. Determine the number of personnel included in the available strength of the unit by rank and MOSC. Match thequalified available personnel against requirements. Personnel are considered MOS-qualified for purposes of the unitstatus report as follows—

(1) Match officers to officer spaces on a one-for-one basis. Officers may be considered MOS-qualified, insofar asskill level is concerned, when they have completed an officer basic course, and the commander feels that they have theminimum skills needed to perform the wartime duties of their assigned position; AMEDD officers must be qualified intheir area of concentration (AOC) for their positions. Additionally, AMEDD officers in clinical specialties, includingPROFIS, will not be considered qualified for a position unless they have been awarded the AOC and additional skillidentifier (ASI), if required, for the specific position to which they are assigned. (See AR 601–142 for substitutioncriteria.) Furthermore, for clinical positions that normally require licensure or other authorizing documentation,AMEDD officers must be credentialed and demonstrate current clinical competency for the specific position per AR40–68. For AMEDD officers, the SQI and ASI will be considered in determining the MOSQ level. If shortages of SQIsand ASIs are degrading readiness, remarks are required in the 2ADDSKIL section of the report.

(2) Using the first four characters of the MOSC, consider warrant officers MOS-qualified when they can be used intheir primary MOSC (PMOSC), secondary MOSC (SMOSC), additional MOSC (AMOSC), or a MOSC that can besubstituted for the above in accordance with AR 600–100.

(3) Using the first three characters of the MOSC, consider enlisted soldiers MOS-qualified when they can be used intheir PMOSC, SMOSC, AMOSC, or a MOSC that can be substituted for the above, and the commander feels that theypossess the minimum skills required to perform their wartime duties for their assigned positions. Use utilizationguidance as outlined in AR 614–200, paragraphs 3–10a(10) and d(7), for considering soldiers as MOSQ.

(4) Using the nine characters of the MOSQ, consider enlisted soldiers in MOSCs 91B and 91W MOS as qualifiedwhen they meet the criteria in paragraph 4–5c(3), above, and in AR 40–68.

d. If a special qualification indicator (SQI) or ASI is specified in authorization documents, it will not be consideredin determining a unit’s MOS level, except in the case of AMEDD units and personnel, where it will be considered.

(1) However, if a commander considers the SQI, or ASI, to be essential to the completion of assigned wartimemissions, and the soldier in this position does not have the required skill, this issue will be considered objectively indetermining a unit’s training and overall category level.

(2) If shortages of SQI and ASI soldiers are degrading the readiness of a reporting unit, this will be addressed in the2ADDSKIL or section D of the report.

e. During the transition period (AC: 2001–2004; RC: 2001–2006) for implementing the Army Language Master Plan(ALMP), reporting units with officer and enlisted language requirements will determine language proficiency (MOSQ)and report linguist status in accordance with the following guidelines—

(1) Linguists will be considered MOSQ, provided they meet the Army minimum language proficiency standard inaccordance with AR 611–6, in any language other than English. This standard is measured by maintaining a current

20 AR 220–1 • 15 November 2001

(within 12 months) score of 2 in listening and 2 in either reading or speaking on the defense language proficiency test(DLPT) or oral proficiency interview (OPI) in any foreign language.

(2) Soldiers in career management fields (CMFs) 18, 37, or 38, area of concentration 180, functional area (FA)/branch 38 or 39, are not required to demonstrate proficiency in any language in order to be considered MOSQ.

(3) The proficiency status of assigned linguists by language identification code (LIC) and the unit’s current assignedlanguage requirements will be reported in the 2LANGAGE section of the USR. This data is reported in the USR forinformation and analysis at higher levels, to include HQDA. Completion of the 2LANGAGE report is mandatory forall reporting units with officer or enlisted language requirements, to include ARSOF MOSs/CMFs/FAs. (See para4–10d and fig 4–6.)

(4) If a commander considers the LIC to be essential to the completion of assigned wartime missions and the soldierin this position does not have the required skill, this may be considered in determining a unit’s training and overallcategory level.

f. RC personnel awaiting initial active duty training (IADT) and prior service personnel in MOS-producing trainingwill not be considered MOS-qualified until they have successfully completed the required training.

g. Personnel who have successfully completed a MOS awarding program may be counted as MOSQ for unit statusreporting purposes. This includes soldiers who have submitted a proper request for the granting of a MOS based oncivilian-acquired skills in accordance with AR 601–210, paragraph 7, DA Pam 600–3, or similar guidance. RCpersonnel who have not been officially awarded the MOS owing to administrative delays may be counted as MOSQ.RC prior service personnel in MOS-producing training will not be considered MOSQ until they have successfullycompleted the required training.

(1) However, for personnel who have completed MOS training but have not been granted the security clearancerequired for award of the MOS, the commander may consider a soldier MOS-unqualified for the assigned position.

(2) For personnel assigned to a position or site requiring a security clearance, the commander may consider a soldierin such a position MOS-unqualified pending receipt of the final required security clearance.

h. Personnel who are over strength in a specific skill will not be counted as MOS qualified. Any personnel holding aPMOS that is surplus to reporting unit requirements and who have been awarded an SMOSC, AMOSC, or a substituteMOSC that matches a unit required vacancy will be counted against that vacancy as MOS qualified. For example, if aunit requires four cooks and has six MOS-qualified cooks in its available strength, count only four against therequirement for cooks. Additionally, if any of the cooks have an SMOSC or AMOSC of truck driver, and if truckdriver required vacancies exist, then count the two remaining cooks as available MOS-qualified drivers.

i. PROFIS personnel will be considered MOS qualified per criteria in paragraph 4–5c(1).

4–6. Determine available senior-grade percentagea. Available senior-grade percentage (SGPER) is based on a comparison of the number of available commissioned

officers, WOs, and noncommissioned officers (NCOs) (grades E–5 through E–9) to required senior-grade personnel.b. PROFIS personnel will be counted when determining available SGPER, but only if MOSQ criteria are satisfied in

accordance with paragraph 4–5c(1).

4–7. Calculate personnel level (P-level)Calculate the personnel level by using table 4–1 and the outline below.

a. Step 1. Identify your unit’s required strength.b. Step 2. Identify assigned strength.c. Step 3. Compute assigned strength percentage. Assigned strength percentage=Assigned strength/Required strength

X 100.d. Step 4. Identify available strength.e . S t e p 5 . C o m p u t e a v a i l a b l e s t r e n g t h p e r c e n t a g e . A v a i l a b l e s t r e n g t h p e r c e n t a g e = A v a i l a b l e s t r e n g t h / R e q u i r e d

strength X 100. Determine P-level using table 4–1.f. Step 6. Identify available MOS-qualified strength.g. Step 7. Compute available MOSQ percentage. Available MOSQ percentage=Available MOSQ personnel/Required

strength X 100. Determine P-level using table 4–1.h. Step 8. Identify available senior-grade strength.i. Step 9. Compute available senior-grade percentage. Available senior-grade percentage=Available senior-grade/

Required senior-grade x 100. Determine P-level using table 4–1.j. Step 10. Determine your unit’s overall P-level. The lowest P-level determined in steps 5, 7, and 9 above is your

overall personnel P-level unless HQDA and/or the MACOM directs or approves use of a P-level of P–5.

21AR 220–1 • 15 November 2001

Table 4–1Level for available, MOSQ, and senior-grade strengths

P–LEVEL Available MSOQ/senior–grade

1 100–90% 100–85%2 89–80% 84–75%3 79–70% 74–65%4 69% or less 64% or less

4–8. Determine personnel turnover percentagea. Personnel turnover percentage (APERT) provides an indicator of unit turmoil (degradation of unit capability).

Compute personnel turnover percentage by comparing the total number of departures during the 3 months precedingthe as-of date of the report against assigned strength on the as-of date. Total of personnel departed (90 days) divided byAssigned strength X 100.

b. Reassignments of personnel within the reporting unit are not included in turnover computations.

4–9. Instruction for completing sections A and B of DA Form 2715a. Section A, PERSONNEL set (fig 4–1).(1) PRRAT (field 1, personnel level). Use the computed P-level from step 10. APS always report “6.”(2) PRRES (field 2, reason personnel level not 1). If PRRAT field is not P–1, enter the personnel code from

appendix E that shows the main reason the personnel level is not 1; otherwise, leave blank. APS always reports “P78.”If the PRRAT corresponds to the ALO for the unit (that is ALO 3 and P3), “P65” is an appropriate reason code for notachieving a P-level of 1.

b. Section B, PERSDATA set (fig 4–2).(1) ASPER (field 2, assigned strength percentage). Use percentage calculated in step 3. Enter “0” for APS.(2) AVPER (field 3, available strength percentage). Use percentage calculated in step 5. Enter “0” for APS.(3) MSPER (field 4, available MOS-qualified percentage). Use percentage calculated in step 7. Enter “0” for APS.(4) SGPER (field 5, available senior-grade percentage). Use percentage calculated in step 9. Enter “0” for APS.(5) APERT (field 6, personnel turnover percentage).(a) GAINS (field 6, # gains). Enter the number of gains from the last 90 days. (Note that this data is required for use

at HQDA-level and is not used by the unit to determine personnel turnover.)(b) LOSSES (field 6, # losses). Enter the number of losses from the last 90 days.(c) APERT (field 6, T/O percentage). Use percentage calculated in paragraph 4–8.(6) SDPER, (field 8, special duty personnel). All MTOE units will enter the number of total man-days positions in

the unit were vacant during the reporting period because of BMM and TD requirements. The SDTOTAL must be thesum of each individual service member’s BMM or TD time, in days, during the reporting period. The term “specialduty” (SD) is defined as the performance of duty with a unit or organization other than the one to which a soldier isassigned, while continuing to be accounted for and administered by the unit of assignment. SD applies to personnel ineither borrowed military manpower (BMM) or troop diversion (TD) categories. Examples of and distinctions betweenthese two categories of SD are provided and explained in AR 570–4.

(a) BMM includes all soldiers assigned to MTOE units who have been temporarily assigned duties within TDAactivities where a MACOM-approved manpower requirement exists but for which no manpower space has beenauthorized. Additionally, BMM may be employed in those cases in which manpower spaces have been authorized, butthe positions are vacant.

(b) TD includes all soldiers (not qualifying as BMM) from units (TDA or MTOE) tasked to perform recurring dutieswith an organization or unit other than that to which they are assigned while they continue to be administered by theunit of assignment. The manpower requirements may or may not have been approved at the MACOM level.

(7) GENTEXT remark (section D). Units can submit additional detailed data and remarks on any field above, toprovide focus on specific problem areas or additional information. Example of how data will be entered on the sectionD FREE GENTEXT remark format is as follows: security classification—enter C, transaction type—enter A, label—enter MSPER, then enter text. Information should be concise and able to stand alone. (Note that unit commanders alsomust assess the impact of SD personnel on their unit’s ability to train to the T–1 level and provide narrative remarksregarding SD personnel as a resource constraint in accordance with paragraph 7–9, if applicable.)

c. Section B, PROFIS set.(1) For PROFREQ (field 1, professional fillers required), enter the number of PROFIS personnel a unit requires. For

PROAVAL (field 2, professional fillers available), enter the number of PROFIS available.(2) Enter “0” for APS.d. Section B, FEMALE set.(1) For FEMASGD (field 1, female assigned), enter the total number of female personnel assigned to the unit.

22 AR 220–1 • 15 November 2001

(2) For FEMPREG (field 1, female pregnant), enter the total number of female personnel pregnant (prenatal andpostpartum).

(3) Enter “0” for APS.e. Section B, ACTGURES set.(1) For AGRASGD (field 1, number of guardsmen and reservists), enter the number of RC personnel on active duty

assigned to a unit(2) Enter “0” for APS.

Figure 4–1. Section A, Joint reporting requirements, personnel set

Figure 4–2. Section B, PERSDATA, PROFIS, FEMALE, and ACTGURES sets

4–10. Mandatory personnel reporting remarksa. 2PSPER (personnel grade strength of the unit). Section D provides personnel strength by grade. All reporting

units will submit 2PSPER data. Personnel data will be entered as shown in figure 4–3. Required, authorized, assigned,and available strength will be entered after the appropriate preprinted grade for each component as applicable. If nopersonnel are assigned in a particular grade, leave blank. All units aggregate strength, and senior-grade breakout datawill be generated by PC/ASORTS from the 2PSPER Set. Commanders with soldiers deployed within the JSCP AORwill enter that mandatory remark here (as AVPER remarks) in accordance with paragraph 4–4b. Commanders withsoldiers deployed outside the JSCP AOR, but available to meet deployment timelines and counted as available, willspecify location and number of soldiers deployed.

23AR 220–1 • 15 November 2001

Figure 4–3. Section D, 2PSPER

b. 2RQPER (military occupational specialty shortage report), section D. Section D provides a list of critical MOSs.The unit commander has the option to report either three-digit or five-digit MOS codes. Listing specific critical MOSsis mandatory for units that are P4 in personnel. The 2RQPER remarks are optional for units reporting P3 or better, orare organized at ALO 4–9. (See fig 4–4.)

24 AR 220–1 • 15 November 2001

Figure 4–4. Section D, 2RQPER

(1) Commanders should consider MOSs of key positions when listing MOSs in 2RQPER. Key positions are thosepositions the commander has determined require a unique nature of training or skill level and are essential to the abilityof the unit to perform its wartime mission. Examples may include, but are not limited to, surgeons in hospitals, pilotsin aviation units, fire direction center chiefs in artillery units, and master gunners in infantry and armor units.

(2) The number of officer areas of concentration (AOC) or warrant officer/enlisted MOS cited is up to thecommander, but it will not exceed a total of 10. If additional space is required, create a label: MSPER GENTEXTremark (section D. FREE GENTEXT remark) for specific MOS comments (for example, a shortage of 11B 2/3severely hampers the ability to train at squad/fire team level).

c. 2ADDSKIL (additional skill identifier/SQI shortage report), section D. Additional skill identifiers (ASI) andspecial qualification identifiers (SQI) are reported on the 2ADDSKIL report. List all ASI shortages first, followed bySQI shortages. Both ASIs and SQIs include the required, authorized, and assigned strength. Enter the two-digit ASIcode in the ASI/SQI field. For SQI, enter the letter “S” in the first position ASI/SQI field followed by the appropriateSQI code, as follows (see fig 4–5)—

25AR 220–1 • 15 November 2001

Figure 4–5. Section D, 2ADDSKIL

(1) The three enlisted numerical SQI codes will be reported in the second position of the ASI/SQI field for USRpurposes only: SQI 2 enter “B,” SQI 4 enter “J,” SQI 7 enter “S.”

(2) The six warrant numerical SQI codes will be reported in the second position of the ASI/SQI field for USRpurposes only: SQI 1 enter “H,” SQI 2 enter “I,” SQI 5 enter “L,” SQI 6 enter “O,” SQI 7 enter “Q,” SQI 8 enter “X.”

d. 2LANGAGE (language skill identifiers report), section D. Language identification codes (LIC) are reported on the2LANGAGE report. For each authorized LIC (AUTHLIC) (two-digit LIC code) and MOS (LICMOS) (the three-digitDMOSC) cited, include the required (LICREQ), assigned (LICASGD), and qualified (LICQUAL) at level 2 proficien-cy, or as documented on the MTOE for ARSOF MOSs/CMFs/FAs. (See fig 4–6.) For parent units (AA-level UIC),which have personnel that require a language that is coded on the unit’s MTOE requirements document (using two-character language code), the following comments are required—

(1) For each language on the unit MTOE (using two-character language code LIC), the unit will report the numberof personnel required, the number of personnel assigned, and the number of personnel qualified by LIC and MOS. Ifthe unit has more than one language requirement, the commander will list his or her languages in descending order,MOST CRITICAL first.

(2) Consider service members (SMs) LIC-assigned (LICASGD) if they have received a certificate of attendance orhave graduated from a DOD-approved language course of instruction (for example, DLI, FSI, USAJFKSWCS); havecompleted the defense language proficiency test (DLPT) and/or oral proficiency interview (OPI); or have received aninteragency language roundtable (ILR) proficiency level score of 1 or higher in all tested areas in the languagematching the MTOE position to which the SM is assigned.

(3) Consider SMs LIC-qualified (LICQUAL) if they have successfully completed the defense language proficiencytest (DLPT) and/or oral proficiency interview (OPI), or received an interagency language roundtable (ILR) proficiencylevel score in all tested areas in the language that matches the MTOE position to which the SM has been assigned forthe last 12 months.

26 AR 220–1 • 15 November 2001

Figure 4–6. Section D, 2 LANGAGE

e. PSPER non-available report: GENTEXT remark, section D. All units will report the number of personnel notavailable for deployment/mobilization and or employment with the unit to accomplish its wartime mission. Thepersonnel categories for reporting include—

(1) Legal processing (LP)(2) Medically non-available/hospitalized/convalescent leave (includes HIV positive) (MN)(3) Absent without leave (AW)(4) Assigned, not joined (AN)(5) Leave/TDY (LT)(6) Deployed (DP)(7) Temporary change of station (TC)(8) Parenthood (PH)(9) Minimum training for deployment not completed (TN)(10) Dental (DN)(11) P3/P4 profile(12) Temporary profile (TP)(13) HIV testing (HT)(14) No DNA record, uncorrected (DA)(15) Family care plan (FP)(16) Conscientious objector (CO)(17) Less than 7 days until ETS/ (7E)(18) Lautenberg Amendment (LA)(19) Missing/prisoner of war (MP)

27AR 220–1 • 15 November 2001

(20) Sole surviving family member (SS)(21) RC and multi component units(22) Unsatisfactory participation (UP)(23) Simultaneous membership program (SM)

Note. Commanders of reporting units will use the decision matrix provided at appendix D to determine the appropriate category andthe correct availability status of soldiers in their units. (Also see example at fig 4–7.)

Figure 4–7. Section D, PSPER NON-AVAILABLE

Chapter 5Equipment-on-Hand Data

5–1. Generala. The unit status report provides indicators of a unit’s equipment-on-hand (EOH) status by developing an S-level

that is calculated by comparing the fill of selected equipment to wartime requirements. A level is determined for all ofan MTOE/TDA unit’s primary items of equipment, to include individual pacing items (ERC P), principal weaponssystems and equipment (ERC A), and support items of equipment (ERC B/C). While not a factor in determining theunit’s overall S-level, the EOH status of ERC B/C equipment items and the NBC S-level is determined and reported inthe USR and may be considered by commanders of reporting units when determining whether the unit’s overall C-levelshould be subjectively upgraded or downgraded.

b. APS units will calculate the S-level by comparing the fill level to the authorized column in the MTOE.c. The unit’s overall EOH S-level is equal to the lower of the ERC A/P or ERC P computations.

28 AR 220–1 • 15 November 2001

5–2. Equipment authoritya. The HQDA intent is to enable commanders to use the automated tools available in The Army Authorization

Documentation System (TAADS) to determine equipment authorizations. This capability is being refined over time.Because TAADS does not have the EOH calculation capability currently, TAADS feeds requirements data into theStandard Property Book System-Redesign (SPBS-R) for EOH development. SPBS-R accommodates unit status report-ing against the current automated authorization document or future authorization document (future e-date). The LOGTAADS updates to the SPBS-R will be the only way to modify the requirements column of an automated authorizationdocument.

b. As change documents are published and provided to units confusion often develops as to which authorizationdocument the unit should use for calculating EOH status. Commanders must decide which document, the current orfuture MTOE, the unit most closely resembles in order to report unit status accurately. However, units will not reportearly against a new MTOE if the overall S-level will be degraded. Once a commander begins to report against a newMTOE (future e-date), the previous MTOE will not be used for unit status reporting unless directed by the MACOM.

c. When a discrepancy is noted between the MTOE approved TAADS paper copy, and the LOG TAADS providedto SPBS-R, units will report EOH status against the paper copy of the current MTOE until discrepancies are resolved.M A C O M s w i l l i n f o r m H Q D A , D E P U T Y C H I E F O F S T A F F F O R O P E R A T I O N S A N D P L A N S , A T T NDAMO–FMF, 5000 ARMY PENTAGON, WASHINGTON DC 20310- 5000 of discrepancies requiring resolution.

5–3. Reportable equipmentAll of the equipment on a unit’s MTOE or TDA is reportable. Refer to the unit MTOE or TDA to determine thecategory of each item of equipment and the required quantity. Use the following instructions to determine how each ofthese items will be reported—

a. For MTOE units, equipment that is designated readiness code ERC A or P is used to determine the EOH resourcearea level.

b. For TDA units, equipment on the unit TDA and designated in AR 700–138, appendix B will be considered asERC A/P until TDAs are equipment-readiness coded. All other items on the unit TDA will be considered ERC B/C.

c. Pacing items will be determined from the guidance in appendix C. ERC B/C items will be addressed inEQOHDATA set, block 17b, but will not be included in the S-level (ESRAT) computations.

d. Any equipment that has not been designated as exempt from reporting (appendix F) must be reported. Additionsand deletions to table F–1, appendix F, must be approved by HQDA (DAMO–FMF). MACOMs are not authorized toexempt LINs from reporting.

e. Authorized stock levels of CTA items will be as directed by the MACOM. Units with equipment centrally stored/consolidated at local level (CIF, USPFO, and so forth) and specifically earmarked for that unit will consider thatequipment on hand for computation purposes. Units not required by MACOM to maintain certain items of CTAequipment will not consider that equipment in computations of EOH. For EOH computation purposes, CTA authoriza-tions will equal required.

5–4. Applying substitutes and in-lieu-of equipment in determining quantity of reportable equipmenton hand

a. Quantity on hand is determined from the unit property book.b. HQDA-authorized substitute, in-lieu-of (ILO), or MACOM non-type classified items (NTCI), will be counted as

equipment on hand for reporting purposes in accordance with criteria established in this paragraph. Authorizedsubstitute, in-lieu-of, or non-type classified items must comply with AR 71–32. The listing of authorized substitutes isin SB 700–20. NTCI must meet the requirements listed in appendix F, paragraph F–3. Additionally, in the opinion ofthe commander, the substitute or in-lieu-of item must be able to perform the MTOE/TDA mission in the place of therequired item. Availability of trained personnel and repair parts, trained operators and maintenance personnel, andammunition and compatibility all affect the suitability of the item for mission accomplishment.

c. Substitute items are listed in SB 700–20, appendix H.(1) HQDA authorized substitutes are selected on the basis of their ability to fulfill the operational requirements of

the MTOE/TDA required item of equipment and logistical support ability. Recommended changes to SB 700–20,appendix H, may be submitted to HQDA, OFFICE OF THE DEPUTY CHIEF OF STAFF FOR LOGISTICS ATTNDALO–SMR, 500 ARMY PENTAGON, WASHINGTON D.C. 20310–0500.

(2) When authorized substitutes are approved for issue on a greater than one-for-one basis, calculate an adjustedquantity of fill for the required MTOE/TDA LIN; then, compute the percentage of fill and determine the level for therequired MTOE/TDA LIN, using instructions in paragraph 5–11 as applicable. For example, a unit’s MTOE/TDArequired column quantity for 10-kilowatt generators is 25. The unit has no 10-kilowatt generators; however, it hasthirty 5-kilowatt generators on hand. The percentage of fill for 10-kilowatt generators is calculated as follows:substitute two 5-kilowatt generators for each 10-kilowatt generator. Dividing 30 by 2, we find the adjusted quantity offill for 10-kilowatt generators is 15. Divide 15 by 25 (15 25=.60) and multiply by 100 (10 X .60=60). Percent fill forthe 10-kilowatt generator LIN is 60 percent. The unit has only 60 percent of the generators required. This LIN is ratedS–4 (table 5–1).

29AR 220–1 • 15 November 2001

Table 5–1Equipment-on-hand criteria (high-density individual LINs, 21 or more items, includes pacing items)

Level Equipment Aircraft

1 100–90% 100–90%2 89–80% 89–80%3 79–65% 79–60%4 64% and below 59% or below

d. In-lieu-of items are those items that do not have a valid substitute relationship reflected in SB 700–200, appendixH, but that the commander wishes to use in place of a required item of equipment. The following criteria must be usedwhen determining suitability of an item as an in-lieu-of item—

(1) Item must have the same characteristics as the authorized item.(2) Item can be used in conjunction with other items (for example, a tractor can haul an authorized substitute

trailer).(3) Item is supportable. Required repair parts must be available. Repair capability must be within the unit/

organizational scope or available through other means (in theater contractor support or DS maintenance team). Asource of supply for replacement of the major end item must be available.

(4) Item will be deployed with the unit to accomplish the wartime mission if authorized item is not available.e. If a modernization item/system of equipment is added to authorization documents to replace a current vintage

item of equipment, but the new item (or an authorized substitute from SB 700–20) is not fielded, the older item/systemwill be designated as in lieu of the new item for USR purposes. These items/systems will be designated as in lieu of ona system-for-system, function-for-function, or capability-for-capability basis. MACOMs will ensure that subordinateunits properly apply the in-lieu-of policy. For example, if a unit has Redeye weapon systems in-lieu-of Stingerweapons, each Redeye system on hand will be reported for one Stinger and all its associated LINs. After applying thisin-lieu-of rule, the Stinger and each associated LIN will then be rated by dividing the total number of on-hand, in-lieu-of items/systems by the number required to take the place of the newly authorized item/system. Similarly, an M60series tank will be counted as in-lieu-of all LINs associated with an M1 series tank.

f. APS substitute and in-lieu-of items will be approved by HQ, AMC (except class VIII, which will be approved byOTSG/USAMEDCOM).

g. If a commander elects not to include the authorized substitute in the EOH computation, or to include an in-lieu-ofnon-type classified item in the computation, the FF-level commander or first O–6-level commander in the chain ofcommand must approve this decision. Commanders will list (section D, borrowed and loaned equipment, label:ESRAT/GENTEXT remarks) the LIN of substitute items not counted or in-lieu-of or non-type classified items notcounted against EOH computations.

h. If the commander determines that there are problems of capability/compatibility caused by the use of authorizedsubstitutes or in-lieu-of items, a comment must be made in the section C, READY/REASN remarks. Considerationshould be given to both MTOE and CTA equipment. Further, commanders identifying a compatibility problem (withhigher, supported, or supporting units interoperability) or a problem that degrades the unit’s combat capability mustcomment in section C, READY/REASN remarks. (An example would be a wheeled-vehicle maintenance unit assignedto support an armored unit.)

5–5. Evaluating component part availabilitya. Reportable LINs having several components, such as sets, kits, or outfits (SKO), and/or medical materiel

equipment sets (MMS/MES/DES/DMS/VES), will be reported as on hand if property records show the LIN has beenissued and at least 75 percent of each SKO non-expendable and durable items are present and serviceable. Do notcount the set as on hand, if more than 25 percent of the non-expendable and/or durable components are unserviceable,missing, or depleted or require supply action under AR 735–5 (for example, report of survey).

b. ALL RC units will exclude all expendable and durable MMS/MES/DES/DMS/VES component items that have ashelf life of less than 60 months (shelf-life codes of A–H, J–M, P–R, or 1–9). AC and echelon III and IV medical unitswill exclude all expendable and durable items with a shelf life of less than 60 months that are part of the SurgeonGeneral’s centralized contingency programs. The list of this materiel is available in SB–8–75–S7 and can be accessedon http://www.armymedicine.army.mil/usamma.

5–6. Reserve component equipmentRC units will include all reportable equipment at equipment concentration sites (ECS), displaced equipment trainingcenters (DETC), regional maintenance training sites (RMTS), regional training sites medical (RTS–MED), unit trainingequipment sites (UTES), maneuver area training equipment sites (MATES), and weekend training sites (WETS). Thisis subject to the provisions of paragraph 5–7.

30 AR 220–1 • 15 November 2001

5–7. Equipment not on sitea. Assigned equipment that is part of an established plan that ensures the equipment will be deployed to meet the

unit in theater will be counted as available for EOH computations. A system must be established to keep thecommander informed as to the fill and maintenance status of this equipment.

b. Assigned equipment outside the operational control of the reporting unit (for example, on loan) but specificallyearmarked for the unit and returnable in time to meet the unit’s requirement to deploy in accordance with the rules andprocedures established in paragraph 3–3c will be counted as on-hand equipment. Equipment not returnable in time tomeet the unit’s requirement to deploy will be reported as on-hand by the unit physically in control of the equipment.Note that the policy guidance contained in paragraph 3–3c concerning the availability of units is applicable to bothpersonnel and equipment.

c. Active Army OCONUS DEPMEDS hospitals (decrement) and RC hospital DEPMEDS (RCHD) will reportmedical assemblages and ASIOE stored in decrement or RCHD storage as on hand, if the unit has received a Reservecomponent decrement feeder data report detailing LINs stored against the unit’s UIC. Decrement/RCHD UIC LINreports will be provided on a yearly basis (01 October) to the appropriate unit and parent MACOM. Change reportswill be provided if sustainment or modernization actions occur that affect readiness. The commander will use MESEQUIPMENT REPORT, label PROFREQ, section D to report the date of the decrement/USAMMA RCHD feeder datareport on which the EOH computations are based.

5–8. Loans from Army pre-positioned stocksArmy pre-positioned stocks (APS) equipment deployed/loaned as a unit set, partial set, or task force package will bereported by the using unit(s) that signed for the equipment. The deploying unit will include the transferred/loanedequipment in its EOH computations. The EOH for APS will be reduced to reflect the transfer/loan.

5–9. How to determine pacing itemsPacing items are coded ERC P on the unit MTOE/TDA. TRADOC, with HQDA approval, establishes pacing items inaccordance with guidance in appendix C. Appendix C normally takes precedence when there are discrepancies betweenit and unit documentation. Units may not independently change reporting items, but they must inform the appropriateMACOM when discrepancies exist. MACOMs will review discrepancies and initiate correction of unit documents.Units will report the appropriate pacing items while waiting for administrative errors on unit documentation to becorrected by USAFMSA.

5–10. Calculate the S-levelCalculate the S-level using table 5–1 or table 5–2 and the steps outlined below. Round to the nearest whole number.(See para 3–3d.)

Table 5–2Equipment-on-hand criteria (low-density individual LINs, 20 or less items, includes pacing items)

LINs S–1 S–2 S–3 S–3 S–4

(Equipment) (Aircraft)20 20–18 17–16 15–13 15–12 Less than

13–Equipment12–Aircraft

19 19–17 16–15 14–12 14–11 Less than12–Equipment11–Aircraft



16 16–15 14–13 12–10 12–10 Less than 1015 15–14 13–12 11–10 11–9 Less than



13 13–12 11–10 9 9–8 Less than9–Equipment8–Aircraft

31AR 220–1 • 15 November 2001

Table 5–2Equipment-on-hand criteria (low-density individual LINs, 20 or less items, includes pacing items)—Continued

LINs S–1 S–2 S–3 S–3 S–4

12 12–11 10 9–8 9–7 Less than8–Equipment7–Aircraft

11 11–10 9 8–7 8–7 Less than 710 10–9 8 7 7–6 Less than


9 9 8–7 6 6–5 Less than6–Equipment5–Aircraft

8 8 7–6 5 5 Less than 57 7 6 5 5–4 Less than


6 6 5 4 4 Less than 45 5 4 3 3 Less than 34 4 3 2 2 1 or 03 3 – 2 2 1 or 02 2 – 1 1 01 1 – – – 0

a. Step 1. Identify your unit’s ERC A/P (MTOE units) or AR 700–138, appendix B (TDA units) LINs and requiredquantities.

b. Step 2. Identify quantities of equipment on hand to be counted against the required quantities above. Ensureauthorized substitutes and in-lieu-of items are counted (para 5–4).

c. Step 3. Determine the S-level for each ERC A and P LIN.(1) If the number of items required under a LIN is 21 or more, calculate a percent fill for that LIN. Then use table

5–1 to determine the S-level for that LIN. Percent fill=Equipment on hand/Equipment required X 100.(2) If the number of items required under a LIN is 20 or less, use table 5–2 to determine an S-level for that LIN.

When counting substitute items on a greater than one-for-one basis, refer to paragraph 5–4c.d. Step 4. Based on the results of step 3, record the following: Total number of reportable ERC A and P LINs=____

Number LINs S-1=____. Number LINs S-2=____. Number LINs S-3=____. Number LINs S-4=____.e. Step 5. Convert the number of LINs at each S-level to a percentage. (PC/ASORTS does not apply rounding rule.)

Number S-1 LINs ÷ total ERC A&P LINs X 100=____ percent. Number S-2 LINs ÷ total ERC A&P LINs X100=____ percent. Number S-3 LINs ÷ total ERC A&P LINs X 100=____ percent. Number S-4 LINs ÷ total ERCA&P LINs X 100=____ percent.

f. Step 6. Calculate a separate equipment fill S-level for pacing items (para 5–10). (Disregard if no pacing items.)(1) Identify those LINs that are pacing items.(2) Based on step 3, identify which of the pacing items has the lowest calculated S-level. That is the S-level for

pacing items.g. Step 7. Compute the unit S-level.(1) S-1. If the percentage of S-1 LINs (step 5) is equal to or greater than 90 percent, the unit S-level is S–1 unless a

pacing item (step 6) is less than S-1. Then the unit S-level is equal to the pacing item S-level.(2) S-2. If the percentage of S-1 LINs is less than 90 percent, but the total of the percentages of S-1 LINs and S-2

LINs (step 5) is equal to or greater than 85 percent, the unit S-level is S-2, unless a pacing item (step 6) is lower thanS-2. Then the unit S-level is equal to the pacing item S-level.

(3) S-3. If the percentage of S-1 LINs plus the percentage of S-2 LINs is less than 85 percent, but the total of thepercentages of S-1 LINs, S-2 LINs and S-3 LINs (step 5) is equal to or greater than 80 percent, the unit S-level is S-3,unless a pacing item (step 6) is S-4. Then the unit S-level is equal to S-4.

(4) S-4. If the percentage S-4 LINs is greater than 20 percent, then the unit S-level is S-4.h. Step 8. Identify your unit ERC B/C (MTOE units) LINs or those LINs not listed in AR 700–138 appendix B

(TDA units), and their required quantities.

Note. Ensure exempt LINs below an S-3 level of fill (such as obsolete LINs) are subtracted. APS MTOE LINs that are TAT/NAPare exempt, regardless of S level. (See appendix F.)

i. Step 9. Identify quantities of ERC B and ERC C equipment on hand to count against the required ERC B/Cquantities above. Ensure that authorized substitutes and approved in-lieu-of items are counted. Any LIN not countedagainst a required quantity in this step or in step 2 is considered excess to the authorization document for unit statusreporting EOH computations.

32 AR 220–1 • 15 November 2001

j. Step 10. Determine an S-level for each ERC B/C LIN. Use the same methodology as for ERC A/P LINs in step 3.k. Step 11. The S-level for ERC B/C LINs will be entered in ERC B and C, equipment field, block 17b. Total

number of reportable ERC B and C LINs=____. Number LINs S-1=____. Number LINs S-2=____. Number LINs S-3=____. Number LINs S-4=____.

5–11. Completing equipment-on-hand portions of DA Form 2715, sections A and Ba. Section A—EQSUPPLY set, DA Form 2715 (fig 5–1).(1) ESRAT, S-level (FLD 1). Enter the S-level determined in step 7, paragraph 5–10. If no reportable equipment,

enter “1,” or if HQDA/MACOM has directed/authorized use of a S-5 level, enter “5.”

Note. For units with pacing items, the S-level cannot be higher than the lowest pacing item S-level.

(2) ESRES, reason S-level not 1 (FLD 2). If ESRAT (field 1) does not contain a “1,” enter the equipment-on-handcode from appendix E that shows the main reason the S-level is not “1.” Otherwise, leave blank.

Figure 5–1. Section A, Joint reporting requirements, EQSUPPLY set

b. Section B–EQOHDATA set, DA Form 2715 (fig 5–2).(1) EHRDN, (FLD 2, total number of ERC A&P LINs). Use data from step 4. If none, leave blank. Sum of fields 3,

4, 5, and 6.(2) EHRD1, (FLD 3, number of LINs rated 1). Use data from step 4. If none, leave blank.(3) EHRD2, (FLD 4, number of LINs rated 2). Use data from step 4. If none, leave blank.(4) EHRD3, (FLD 5, number of LINs rated 3). Use data from step 4. If none, leave blank.(5) EHRD4, (FLD 6, number of LINs rated 4). Use data from step 4. If none, leave blank.(6) PIRAT, (FLD 7, lowest pacing item S-level). Use data from step 6. If a unit has no pacing items, leave blank.

33AR 220–1 • 15 November 2001

Figure 5–2. Section B, Army reporting requirements, EQOHDATA

c. DA Form 2715, section B, ERC B and C equipment (fig 5–2).(1) EHRDNBC (FLD 1, total number of ERC B and C LINs). Use data from step 11. If none, leave blank. Sum of

fields 2, 3, 4, and 5.(2) EHRDBC1 (FLD 2, number of LINs rated S-1). Use data from step 11. If none, leave blank.(3) EHRDBC2 (FLD 3, number of LINs rated S-2). Use data from step 11. If none, leave blank.(4) EHRDBC3 (FLD 4, number of LINs rated S-3). Use data from step 11. If none, leave blank.(5) EHRDBC4 (FLD 5, number of LINs rated S-4). Use data from step 11. If none, leave blank.

5–12. Mandatory entries for all reporting unitsa. Pacing item status report, section D, 2PIESTAT (fig 5–3) (disregard if unit has no pacing items). Units with

pacing items will identify the status of all pacing items on the 2PIESTAT report in the following format: PILIN (LIN,an alpha character and five numbers), PIREQ (three digits), PIAUT (three digits), and PIOH (three digits).

34 AR 220–1 • 15 November 2001

Figure 5–3. Section D, 2PIESTAT

b. Equipment that is S-Level 4, section D, 2ERCFOUR (fig 5–4) (disregard if no S-4 LINs). All commanders ofbattalion-size and smaller units with S-4 LINs will list all ERC-A S-4 LINs. (TDA units, see para 5–3b.) If pacingitems are S-4, they must be listed again in this field. LINs will be listed in descending order of critical need, with themost critical listed first. Follow format as shown on section D, 2ERCFOUR, ERCA4LN (LIN number), ERCAREQ(three digits), ERCAAUTH (three digits), ERCAOH (three digits).

35AR 220–1 • 15 November 2001

Figure 5–4. Section D, 2ERCFOUR

c. Equipment shortage report, section D, 2EOHSHRT (fig 5–5).

(1) For units with no S-4 LINs that want to give visibility to additional EOH shortages, use the 2EOHSHRT set.Units that have no S-4 LINs but have an EOH level below S-1 must, as a minimum, address those key ERC Aequipment items (in addition to pacing items listed) that prevent attainment of an S-level equal to S-1. Only ERC A, S-2, and S-3 LIN items will be listed using the formatted 2EOHSHRT set.

36 AR 220–1 • 15 November 2001

Figure 5–5. Section D, 2EOHSHRT

(2) Narrative remarks may also be provided to clarify a unit’s EOH status. This is the only place (the LABEL/GENTEXT remarks set) where equipment status of any ERC may be addressed. Units with shortages of ERC B (S-4)LINs, which the commander has deemed combat-essential, will be addressed in GENTEXT label EQLIN. The ERRESis used to address why the unit is not S-1. The EQLIN is used to address S-4 ERC B/C LINs or other ERC B/C LINsthat the commander deems combat essential.

d. Borrowed and loaned equipment report, label: ESRAT, section D (fig 5–6).

(1) Equipment borrowed from another unit with the intent and/or purpose of being used by the gaining unit fordeployment will be reported by LIN and quantity-borrowed.

(2) Equipment loaned to another unit, and not recoverable by the loaning unit in time to meet the unit’s deploymenttimeline (see para 3–3c), will be reported by LIN and quantity-loaned.

(3) ERC A or P equipment in transit or deployed, and not recoverable by the reporting unit in time to meet theunit’s deployment timeline (see para 3–3c), will be reported by LIN and quantity-deployed.

(4) In-lieu-of items that meet the criteria outlined in paragraph 5–4 and are applied against a prime LIN will bereported in the borrowed and loaned equipment report. Units will list the in-lieu-of LIN, the prime LIN, and quantitythe in-lieu-of LIN is applied against. Non-type classified items used as an in-lieu-of LIN will be reported using theMACOM-designated local LIN that identifies the item in the property book.

37AR 220–1 • 15 November 2001

Figure 5–6. Section D, borrowed, loaned, and sub/ILO report

e. MES equipment report, Label. PROFREQ, section D, (fig 5–7). Any MES that has been issued, but has beencalculated at less than S-3 level (in accordance with 5–5b), will be listed as follows: MESLIN/ percent fill non-expendable/percent fill durable/percent fill expendable less potency and dated items/projected date MES will be S-3 orbetter (YYMMDD)/reason MES is not S-3 or better.

38 AR 220–1 • 15 November 2001

Figure 5–7. Section D, MES equipment report

5–13. NBC equipment reportinga. In accordance with revised GSORTS procedures, the unit’s NBC S-level will be determined first by calculating

the percentage of the reporting unit’s NBC equipment items that are needed to meet the unit’s wartime requirements(that is, the required quantity specified on the unit’s MTOE/TDA) that is operationally ready (READY)/serviceable ineach applicable category of the six NBC equipment categories specified for unit assessment; second, determining acategory S-level for each applicable category based on these percentage calculations; and then by selecting the lowest(worst-case) category S-level as the NBC S-level for the reporting unit. Commanders of reporting units should note thatthis procedure to determine the NBC S-level is highly exceptional in that it requires the consideration of equipmentserviceability factors while procedures and calculations used for other S-level determinations in the USR are based onthe quantity of required equipment on hand. JCS and OSD have established this exceptional procedure in order toimprove fidelity and to maximize inter-Service consistency in NBC reporting. It is important for commanders ofreporting units to understand that the NBC S-level is derived from a unique S-level calculation methodology andresults in a separate report in GSORTS that is focused specifically on the unit’s NBC equipment status. The NBC S-level does not affect the reporting unit’s overall S-level determinations. Also note that reporting units are required todetermine and report the serviceability of selected NBC equipment items in the ERRAT remarks in accordance withparagraph 6–8 of this regulation.

b. All commanders will report the required (REQ), authorized (AUTH), and serviceable (READY) quantities for allcontingency NBC equipment items—

(1) Required by MTOE, TDA, and/or CTA (M20 SCPE is non-reportable (LIN C79000)).(2) Required by HQDA message, DAMO–ZA, subj: Go-to-War CTA/CL II CDE, dtg 102000Z FEB 98 (table 5–3).(3) Listed in PCASORTS.

39AR 220–1 • 15 November 2001

Table 5–3Standardized individual basic load equipment

Equipment Required level

M256A1 detector kit 1 kit per squadM9 detector paper 1 per five individuals/1 per major piece of equipment (prime movers

and mission essential trailers)M8 detector paper 1 book per individualM291 decon kit 2 kits per individualM295 decon kit 1 kit per individualC2/C2A1 filters1 2 per M40, M42, M45 protective mask; 4 per M43, M48, and M49

protective maskM40/M42 hoods1 2 per M40/ M42, protective maskCP helmet covers 2 per individualBDO/JSLIST 2 per individualChem prot gloves 2 pair per individualChem prot overshoes 2 pair per individual

Notes:1 Units equipped with M17-, M24-, and M25-series protective masks will substitute the appropriate filters and hoods.

(4) Per section 6.46, AR 71–32, Force Development and Documentation—Consolidated Policies. (Units may stock a5 percent overage of the MTOE, TDA, or CTA authorization of those NBC defense items specified by the MACOMcommander in order to enhance readiness by facilitating ready exchange or replacement of items that are defective orof incorrect size.)

c. Comments on all unserviceable and non-operational MTOE/TDA equipment will be reported on the 2ERCERRT,ERRES (section D).

d. NBC equipment shortage report, label: ITAEM, section D.(1) For the purpose of USR reporting, NBC items are grouped into six equipment categories: protective masks

(MASK), chemical and biological detection equipment (DET), decontamination equipment (DECON), individualprotective equipment (IPE), radiological detection equipment (RAD), and CB medical supplies (MED). (See table 5–4and fig 5–8.)

Table 5–4NBC equipment categories

Category Equipment

CAT 1 (MASK) All CB protective mask and the M41 protective assessment test sys-tem (M41 PATS): ground, GP (M17 series & M40 series), combatvehicle (M25 series & M42 series), aviation (M24 series, M43 se-ries, M45, M48, M49) and M40 second skins; include the require-ment for optical inserts if they are necessary for mask readiness(that is, vision less than 20/40).

CAT 2 (DET) M8 alarms, M8A1 alarms, M22 ACADA, CAM/ICAM, M93/M93A1NBCRS, M31 BIDS, M21 RASCAL, M272 water test kit,M274 NBC marking kit, and M34 CB agent sampling kit

CAT 3 (DECON) M12A1 PDDA, M17 LDS, M21/22 MDS, M13 DAP and M11 deconapparatus and M295 equipment decon kits required per ambulance(1 box per) and collective protective shelter (3 boxes per).

CAT 4 (IPE) Protective suit (BDO, JSLIST), chem prot gloves, chem prot over-shoes, CB mask filters, CB hoods, CP helmet covers, M256A1 kits,M8 paper, M9 paper, M295 equipment decon kit, and M291 individ-ual decon kit.

CAT 5 (RAD) IM–174, AN/PDR–75, AN/PDR–77, AN/VDR–2, PP–1578, IM–93,AN/UDR–13 pocket radiac, AN/PDR–27 and DT–236.

CAT 6 (MED) Medical NBC defense materiel, MES chemical agent patient treat-ment, LIN: M23673 and MES chemical agent patient decontamina-tion, LIN M25865

40 AR 220–1 • 15 November 2001

Figure 5–8. NBC equipment shortage report

(2) Reason codes for deficiencies by NBC equipment category are listed in appendix E.(3) For the purpose of the NBC S-level calculation, reporting units either will divide the total number of serviceable

NBC items in each category by the total number of wartime required NBC items for that category, and multiply by 100to determine the percentage of wartime-required NBC items that are serviceable (READY) for each category, or, whenthe total number of wartime-required items for a specified category is 20 or less, they will use table 5–6 to determinethe NBC equipment category S-level. NBC equipment within the categories identified in table 5–4 that has exceeded itsshelf-life, been hand-receipted to support a deployment tasking, or is suitable only for training will not be reported asserviceable.

(4) All units will calculate a S-Level (that is, S-1, S-2, S-3, or S-4) for each of the six NBC equipment categories. Ifa unit is not authorized any equipment in a particular NBC equipment category, then that category percentage is notapplicable to the NBC S-level calculations for that unit.

(a) Determine the number required for each item listed in each of the applicable NBC equipment categoriesdescribed in table 5–4.

(b) Add the numbers of individual item wartime requirements by category to determine the total numbers of wartimerequired items for each category.

(c) Determine the number of serviceable (READY) items for each category.1. Units will count as serviceable (READY) all CDE basic load equipment that is centrally stored and/or consoli-

dated at local level (DOL, USPFO, and so forth) if the equipment is specifically earmarked for the unit. This does notmean the equipment must be stored in unit sets; instead, it may be merely designated for the unit.

2. Units will determine the readiness of medical NBC defense materiel that is configured in MES, in accordancewith paragraph 5–5b. Individual service member medical chemical defense materiel, which is authorized by CTA8–100, is centrally managed by DA DCSOPS and the Surgeon General. This materiel has been assembled intodivision-ready brigade (DRB) sets, which can support 5,000 individual service members. The sets are pre-positioned at

41AR 220–1 • 15 November 2001

Installation Medical Supply Activities (IMSA) in CONUS and at the Medical Logistics Battalions OCONUS. Unitswill not include this materiel in their computation of this readiness area.

(d) For each NBC equipment category, divide the total number of serviceable (READY) items in each NBCequipment category by the total number of wartime required items, unless the total number of wartime required NBCitems in the NBC equipment category is 20 or less. Units then determine the NBC S-level for each NBC equipmentcategory, using table 5–5 for NBC equipment categories with 21 or more wartime-required NBC equipment items andtable 5–6 for NBC equipment categories with 20 or less wartime-required NBC equipment items.

(e) A unique situation may exist if a fraction of the unit is designated force support package 1 (FSP1) and isrequired to maintain class II/IX CDE (table 5–3) at the installation while the remainder of the unit’s class II/IX CDEitems are maintained by USAMC. Procedures for centrally stored and/or consolidated NBC equipment that wereoutlined previously in this paragraph will be followed for the class II/IX CDE items maintained by USAMC. To reportthe class II/IX CDE items for the fraction of the unit designated FSP1, place the following comment in section D–NBCequipment shortages remarks: “IPE S-Level for FSP1 is S___(number 1–4 obtained from table 5–5 or table 5–6, asappropriate), IPE % and is on hand at the installation.”

Table 5–5Determining the NBC equipment category S-level when the total number of wartime-required NBC equipment items in aspecified category is 21 or more

Percent of required items (by category) on-hand and serviceable NBC equipment category S–level

90–100% S–180–89% S–265–79% S–30–64% S–4

Table 5–6Determining the NBC equipment category S-level when the total number of wartime-required NBC equipment items in aspecified category is 20 or less

# Required items # Ready items for S–1 # Ready items for S–2 # Ready items for S–3 # Ready items for S–4

20 20–18 17–16 15–13 Less than 1319 19–17 16–15 14–12 Less than 1218 18–17 16–14 13–12 Less than 1217 17–16 15–14 13–11 Less than 1116 16–15 14–13 12–10 Less than 1015 15–14 13–12 11–10 Less than 1014 14–13 12–11 10–9 Less than 913 13–12 11–10 9 Less than 912 12–11 10 9–8 Less than 811 11–10 9 8–7 Less than 710 10–9 8 7 Less than 79 9 8–7 6 Less than 68 8 7–6 5 Less than 57 7 6 5 Less than 56 6 5 4 Less than 45 5 4 3 Less than 34 4 3 2 Less than 23 3 – 2 Less than 22 2 – 1 01 1 – – 0

(f) After using either table 5–5 or table 5–6 (above) to determine the S-level for each applicable NBC equipmentcategory, select and report the lowest (worst case) NBC equipment category S-level as the unit’s NBC S-level. (See fig5–9 for NBC calculation examples.)

42 AR 220–1 • 15 November 2001

Figure 5–9. NBC S-level calculation

43AR 220–1 • 15 November 2001

Chapter 6Equipment Serviceability Data

6–1. GeneralUnits determine and report in the USR an equipment serviceability (ES) level (R-level) in accordance with theprovisions of this chapter. The unit’s R-level indicates how well the unit is maintaining its on-hand equipment.Determine the R-level for all reportable unit equipment on hand, as defined in paragraph 6–2. Determine a separate R-level for each on-hand ERC-P pacing item. Calculate the R-level by comparing the aggregate fully mission-capable(FMC) rate for all reportable equipment on hand regardless of the ERC. The unit’s overall R-level is equal to the lowerof these R-levels. FMC, as determined by the “Not ready if” column of the preventative maintenance checks andservices (PMCS) in the technical manual (TM) 10/20 series, is the criteria for USR computations.

6–2. Determine reportable equipmentAll equipment LINs listed in the maintenance master data file (MMDF), AR 700–138, appendix B, that are authorizedon the MTOE/TDA, and/or on hand (to include excess) on the last day of the report period will be reported inaccordance with the Army Materiel Status System (AMSS) and the installation materiel condition status report(IMCSRS), DA Form 1352 (Army Aircraft Inventory, Status and Flying Time), DA Form 2406 (Materiel ConditionStatus Report), and DA Form 3266–1 (Army Missile Materiel Readiness Report). The MMDF can be accessed on theLOGSA homepage Web site, http://www.logsa.army.mil. This MMDF will take precedence. (Do not include Reservecomponent hospital decrement or the Active Army DEPMEDS hospital decrement equipment in calculations).

6–3. Basis for the R-level computationa. During peacetime, the R-level computation will be based on available and possible hours/days, as determined

from AMSS feeder reports, or IMCSRS, DA Forms 1352, 2406, or 3266–1, with the same cut-off date as the USR forAC and the most current data for RC. The materiel condition status report (MCSR) covers a 1-month period.MACOMs and NGB may request temporary exemption of RC units that cannot comply with the monthly MCSRrequirement owing to shortages of full-time maintenance technicians. The MCSR period for exempted RC units will be90 days.

b. During call-up, mobilization, deployment, or employment, an “as-of” time procedure will be used.c. The ES computation procedures for reportable medical equipment sets/assemblages are specified in AR 40–61.

6–4. Determine available hours/daysa. Aircraft and some missile systems are rated in hours. In most instances, equipment items rated in hours are unit

pacing items and will require a stand-alone computation. Units that have a mix of equipment rated in hours and dayswill convert the available hours for equipment rated in hours to available days. Then add the days to the equipmentrated in days in the “all on-hand reportable equipment” calculation. Compute each pacing item separately, whetherrated in hours or days.

b. Equipment to be included in R-level computations for all on-hand reportable equipment and for pacing (ERC P)items will include substitute and in-lieu-of equipment. Substitute and in-lieu-of items of equipment included in the R-level computation must meet the requirements for substitute and for in-lieu-of items per paragraph 5–4. If a substituteor in-lieu-of item is not reportable under AR 700–138, but it is counted against a required and/or authorized LIN that isreportable in accordance with AR 700–138, take available hours/days for this equipment from DD Form 314 (Preven-tive Maintenance Schedule and Record) or the AMSS feeder report. However, annotate these items only in the remarksblock on DA Form 1352, DA Form 2406, and DA Form 3266–1 that are submitted to the USAMC Logistics SupportActivity (LOGSA).

c. Compute the available days for all on-hand reportable equipment by adding the individual equipment itemavailable days on the DA Form 2406 and DA Form 3266–1.

d. Compute the available hours or days for each pacing item of equipment on the DA Form 1352, DA Form 2406,or DA Form 3266–1. Do not combine days and hours.

6–5. Determining the equipment serviceability level (R-level)a. Step 1. Assemble the following references (as appropriate to the particular unit): DA Form 1352 (Aircraft), DA

Form 2406 (Ground Equipment Less Missiles), DA Form 3266–1 (missiles), MTOE or TDA for the unit, and the UnitLevel Logistics System (ULLS–A/G), printout, if available.

b. Step 2. Identify all LINs and list their possible time and available time in hours or days as appropriate.(1) Ensure that all reportable items are included in the list (in accordance with AR 700–138), including ERC A,

ERC B, and ERC C.

44 AR 220–1 • 15 November 2001

(2) Identify all ERC P LINs to include those not in AR 700–138.(3) If item is an aircraft, note with “A/C.”c. Step 3. If you have a mix of equipment rated in hours and days, convert both the possible and available hours to

possible and available days. (Divide hours by 24 and then round to the nearest whole number.)d. Step 4. Note which items are pacing items.e. Step 5. Compute a total of all possible equipment days or hours for each LIN.f. Step 6. Compute a total of all available (actual) equipment days or hours for each LIN.g. Step 7. For each pacing item, divide the total available equipment days or hours by total possible equipment days

or hours. Multiply by 100 and round to the nearest whole number.h. Step 8. Using table 6–1, determine an R-level for each pacing item. Identify which pacing item has the lowest R-

level.

Table 6–1Level for percentage of equipment fully mission capable

Level Equipment other than aircraft Aircraft

1 100–90% 100–75%2 89–70% 74–60%3 69–60% 59–50%4 less than 60% less than 50%

i. Step 9. Add all possible days for all reportable equipment. Do the same for available days.

j. Step 10. Divide the total available equipment days by total possible equipment days. Multiply by 100 and round tothe nearest whole number.

k. Step 11. Using table 6–1, determine an R-level for total reportable equipment.

l. Step 12. Compare the R-level for all reportable equipment (step 11) to the lowest pacing item R-level (step 7).The overall R-level is the lowest of the two levels. (See example in fig 6–1.)

Figure 6–1. R-levels for all reportable equipment

6–6. Complete the ES portion of sections A and B of DA Form 2715a. DA Form 2715, section A, EQCONDN set (fig 6–2).

(1) ERRAT, R-level (FLD 1). Enter the lower of the aggregate on-hand reportable equipment R-level or individualpacing item R-level (step 12). If no reportable equipment, enter “1.” If HQDA/MACOM has directed/authorized theuse of R–5, enter “5.”

(2) ERRES, reason R-level not 1 (FLD 2). If ERRAT (FLD 1) does not contain a “1,” enter the appropriate reasoncode from appendix E. The code should be as descriptive as possible. As an example, R31, damaged/inoperative-radar,is more descriptive than R21, damaged/inoperative-equipment.

45AR 220–1 • 15 November 2001

Figure 6–2. Section A, Joint reporting requirements, EQCONDN set

b. Section B, EQMCRDAT set, DA Form 2715 (fig 6–3).

(1) PERRY, percentage of on-hand equipment fully mission capable (FLD 2). Enter the aggregate FMC percentagecomputed for all on-hand reportable equipment. If no reportable items, do not enter anything.

(2) PIEMC, percentage pacing items on hand fully mission capable (FLD 3). Enter the computed percentage of thelowest pacing item. If the unit has no pacing items required, do not enter anything.

Figure 6–3. Section B, Army reporting requirements, EQMCRDAT set

6–7. Mandatory remarks for equipment serviceabilitya. Pacing items operational percentage report, 2PIERRAT set, section D (fig 6–4). Units with pacing items will

identify the ES percentage of all pacing items in a pacing item field (disregard set if no pacing items). Follow theformat on the 2PIERRAT set; for example: PILIN, PINAME, PIEQRPCT.

46 AR 220–1 • 15 November 2001

Figure 6–4. Section D, 2PIERRAT

b. Operational percentage report, 2ERCERRT set, section D (fig 6–5). Commanders of battalion-size or smallerunits with an R-level not equal to R–1 will list the five most critical reportable LINs that reduce their R-level belowR–1. If pacing items belong in this top-five category, they must be listed again. LINs will be listed in descending orderof criticality. Follow the formats shown on 2ERCERRT set, section D, for example: ERCALIN (or appropriate ERCcoded item to include B or P LINs), CERCANAM, ERPCT (two digit), and an S or M to designate whether theproblem is primarily owing to a maintenance work stoppage caused by a supply shortage (S) or a backlog ofmaintenance requirements (M).

47AR 220–1 • 15 November 2001

Figure 6–5. Section D, 2ERCERRT

c. FREE GENTEXT remark, label: ERRAT. Narrative remarks also will be provided to clarify a unit’s equipmentserviceability status. Create a FREE GENTEXT remark with the label: ERRAT, using the FREE GENTEXT remark,section D.

6–8. Serviceability of selected NBC equipment itemsa. All commanders will use the FREE GENTEXT remark, label ERRAT, to report the serviceability status of

selected NBC equipment items. This status report will indicate the number of the selected items on hand, the numberof those items that are serviceable, and the percentage of the on-hand items that are serviceable. This status report isprovided for information only and is not a factor in the calculation of the unit’s R-level.

b. The status of the following NBC items will be reported: M8A1–A32355; M22 ACADA–A33020; CAM /ICAM–C05701; M40 mask—M12418; M45 mask—M12736; M42 mask—M18526; M43 mask—M18594.

Chapter 7Training Data

7–1. Generala. This chapter establishes the process that commanders of all Army reporting units (AA-level and FF-level) will

use to uniformly and accurately determine and report the training readiness status of their units. This training readinessstatus will be expressed as the training level (T-level) in the USR. The unit T-level indicates the commander’sevaluation of the current ability of the unit to employ its weapon systems and equipment effectively and to performthose critical tasks required by the wartime mission(s) for which the unit was organized or designed. The commanders

48 AR 220–1 • 15 November 2001

of reporting units determine their units’ T-levels by applying two separate unit training metrics that translate theirMETL assessments into two distinct training status levels (that is, T–METL and T–Days). The lower (worst case) ofT–METL and T–Days status levels is reported as the unit’s training level in the USR. Additionally, a training levelreview process (TLRP) is provided to assist commanders of AA-level units to review the credibility of their T-leveldeterminations in light of their unit’s training tempo. Unless their units are specifically exempted by the MACOM,commanders of all AA-level reporting units will use the TLRP. The following training data, if applicable, is determinedand reported in the USR.

(1) T–METL. The unit training status level that reflects the percentage of the METL for which unit personnel aretrained, as evaluated in accordance with Army doctrine for training assessments and calculated in accordance with theinstructions provided by paragraph 7–2.

(2) T–Days. The unit training status level that reflects the number of training days estimated by the unit commanderthat are needed by the unit to reach full METL proficiency (that is, a fully trained status in all METL tasks) asdetermined in accordance with paragraph 7–3. The actual number of estimated training days is also reported.

(3) Manning and qualification data. The manning and qualification data for the unit’s required squads/crews/teams/systems in accordance with the standards and criteria established by paragraph 7–4, if applicable. This data is reportedfor information and analysis at higher levels.

b. In addition to the training constraints addressed in paragraph 7–9, commanders of reporting units will considerdata on the factors listed below when addressing the status of training resources that may degrade the unit’s ability toachieve the highest training level (T-1)—

(1) Squad/crew/team/system manning and qualification. (See para 7–4.)(2) Personnel turnover percentage. (See para 4–8.)(3) Special duty (SD) personnel. (See para 4–9.)c. Commanders of reporting units estimate (based on the results of the training assessment process conducted in

accordance with chapters 3 and 5, FM 25–101) and report in the USR the number of days required by the unit to trainto full METL proficiency in accordance with paragraph 7–3 (estimating training days). Full METL proficiency is thecommander’s assessment (in accordance with FM 25–101) that the unit is trained to “T” in all METL tasks; that is,each task can be successfully performed to standard by the unit and only sustainment training is needed.

Note. The T–1 status level does not necessarily connote “full METL proficiency.” USR T-level methodology (that is, that T-level isworst case of T–METL and T–Days) does not require that all METL tasks must be rated as “trained” for a T–1 level determination(that is, that USR T-level metrics establish that T-1 units must have a T–METL percentage of 85 percent or greater and must require14 training days or less to achieve “full METL proficiency.”) “Full METL proficiency” is the training benchmark to which requiredtraining days are estimated. It is not a prerequisite for operational deployment or the standard for the T-1 level.

d. This training assessment process also is used to determine the pre-mobilization training status of Reservecomponent (RC) units. (See para 7–12, tailored reporting for Reserve component units.) The estimate is all-inclusive,reflecting the total unit training days requirement as of the USR date. It includes the commander’s estimate of thenumber of days of pre-mobilization training that is required (applicable to RC units in accordance with para 7–12) andthe number of days required to train on NBC tasks to achieve full METL proficiency. (See para 7–10, training levelunder unique conditions.) This estimate also is reported to inform the Joint Staff, CINCs, the CSA, and othersresponsible for crisis response planning; deliberate or peacetime planning; and management requirements to organize,train, and equip combat-ready forces of the commander’s personal assessment of the time required for his or her unit tobecome fully trained for its wartime mission.

7–2. Assessing the unit’s proficiency in its mission-essential tasks and determining the T–METLa. The training assessment process for Army units is established by FM 25–100 and FM 25–101. Commanders will

use these and other applicable Army doctrinal training publications, as appropriate. (See para 7–2c.)(1) Commanders at all levels will determine their units’ ability to execute the METL by using the Army standards

found in the applicable mission training plans (MTPs) (or, if none exists, developed from other doctrinal trainingliterature in accordance with FM 25–101) to evaluate the demonstrated proficiency of subordinate elements, leaders,and soldiers.

(2) The commander’s assessment compares the unit’s wartime mission requirements with the unit’s current level oftraining proficiency, which includes performance under realistic battlefield conditions such as noise, smoke, NBCsituations, and so forth. The basis for this assessment will include, but is not limited to, in-depth analysis of criticalindividual and collective tasks performed during those mission-related activities and core training events and exercisesthat are required for training or completion in order for the unit to attain or sustain full METL proficiency. FM 25–101discusses the doctrinal training events and exercises for battle focused training. The following are examples—

(a) External evaluations (EXEVALs).(b) Training densities at combat training centers (CTCs).(c) Performance during emergency deployment readiness exercises (EDREs).(d) Performance during field training exercises (FTXs).(e) Performance during command post exercises (CPXs).

49AR 220–1 • 15 November 2001

(f) Performance during live fire exercises (LFXs).(g) Performance during operational readiness exercises (OREs).(h) Performance during other training events in the unit’s combined arms training strategy (CATS), if applicable.b. Commanders of reporting units will use the following references—(1) FM 25–100 and FM 25–101. These doctrinal publications establish the process for Army commanders to

develop and evaluate the unit’s METL. Commanders will determine their unit’s METL based on war plans and externaldirectives. War plans consist of the unit’s anticipated wartime missions, operations plans, and contingency plans.External directives may include: WARTRACE mission guidance letters, mobilization plans, installation wartimetransition and deployment plans, and force integration plans.

(2) Mission training plan (MTP). Commanders will use the applicable MTP standards of proficiency to evaluateteams, squads, platoons, and company-size and battalion-size units. Where no MTP exists, leaders will develop tasklists using the following sources: TO&E; tactical standing operating procedures (TSOP); readiness standing operatingprocedures (RSOP); and state wartime contingencies for ARNGUS.

(3) Combined arms training strategy (CATS). If there is an approved CATS for the unit, commanders will use theCATS to determine their doctrinal training event requirements. The doctrinal training event requirements derived fromCATS will be compared to executed training events when determining T–METL and T–Days and in the training levelreview process.

(4) DA Pam 350–38 and DA Pam 350–39, Standards in Weapons Training (commonly referred to as STRAC).Commanders will use STRAC for proficiency standards for assigned individual and crew-served weapons. Note thatthe training readiness condition levels and categories (TRC) percentage standards for aggregate weapons qualificationin STRAC are not applicable to the full/minimum manning levels established for determining squad/crew/team/systemmanning and qualification for USR purposes.

(5) AR–350–1. This regulation prescribes Department of the Army guidance for managing and conducting militarytraining.

(6) AR 611–6. Commanders will use this regulation to determine the qualification status of Army linguists (foreignlanguage speakers). Army linguists will be considered qualified if they have maintained a current (within 12 months)score of 2 in listening and 2 in either reading or speaking on the defense language proficiency test (DLPT) or oralproficiency interview (OPI) in a foreign language.

(7) AR 40–68. Commanders will use this regulation to determine the qualification status of soldiers with MOS 91W.c. The commander will conduct a METL assessment for USR purposes as of the 15th of each month for Active

Army component units, as described in paragraph 7–2a. For RC units, this assessment process may be less formalduring months when regular reports are not submitted; however, it must be accomplished in sufficient detail to enablethe commander of the reporting RC unit to confirm that no changes to the T-level have occurred during the reportingperiod. The METL development process is explained and illustrated in chapter 2 of FM 25–101. The trainingassessment process for METL tasks is explained and illustrated in chapter 5 of FM 25–101.

d. After determining the number of METL tasks for which his or her unit is currently evaluated as either “trained”(T), “needs practice” (P), or “untrained” (U) in accordance with doctrinal standards and procedures, the unit com-mander will determine the T–METL status level using the following methodology. This methodology considers thedegree of training proficiency achieved for each of the METL tasks by providing relative “weighted” values in theT–METL-status level calculation process to those METL tasks evaluated as “trained” (T), “needs practice” (P), and“untrained” (U). T, P, and U are weighted as follows: T-weight is 3; P-weight is 2; and U-weight is 1. Calculate theT–METL status level in accordance with the following procedures—

(1) Multiply the number of tasks evaluated as “trained” by 3 to obtain a weighted T-factor (weighted T-factor= #tasks “trained” X 3).

(2) Multiply the number of tasks evaluated as “needs practice” by 2 to obtain a weighted P-factor (weighted P-factor=# tasks “needs practice” X 2).

(3) Multiply the number of tasks evaluated as “untrained” by 1 to obtain a weighted U-factor (weighted U-factor=#tasks “untrained” X 1).

(4) Add the weighted T-factor, the weighted P-factor, and the weighted U-factor to obtain the weighted TPU-factor(weighted TPU-factor=weighted T-factor + weighted P-factor + weighted U-factor).

(5) Multiply the total number of METL tasks by 3 to obtain the METL weight, which is also the total pointspossible (TPP) (METL weight or TPP=# METL tasks X 3).

(6) Divide the weighted TPU-factor by the METL weight (or TPP) multiplied by 100 to determine the T–METLpercentage; (T–METL percentage=weighted TPU factor divided by METL weight) (or TPP) X 100. (See fig 7–1 forformula explanation, fig 7–2 for calculation examples, and para 3–3d for rounding instructions.)

50 AR 220–1 • 15 November 2001

Figure 7–1. Determining T-METL based on METL tasks evaluated

51AR 220–1 • 15 November 2001

Figure 7–2. T-METL status calculations

52 AR 220–1 • 15 November 2001

(7) Compare this T–METL percentage to the criteria in table 7–1 to determine the T–METL status level.

Table 7–1Translating the T–METL percentage into a T–METL status level

T–METL percentage determined T–METL status level

85% or greater T-165% to 84% T-250% to 64% T-3Less than 50% T-4

7–3. Estimating training days and determining the T–Days status levela. The commander’s assessment of the unit’s proficiency in executing its METL (accomplished in accordance with

para 7–2) identifies the specific mission-essential tasks, battle tasks, collective tasks, and/or subtasks that requireadditional training before they can be performed to standard.

b. On the basis of his or her assessment, the commander will estimate the number of training days needed by theunit to achieve METL proficiency (trained to standard in all tasks) and the training events that must be conducted toaccomplish the training or re-training required in accordance with the following guidelines—

(1) Assess the unit’s proficiency in executing its METL in accordance with chapters 3 and 5, FM 25–100/101.(2) Identify the specific mission-essential tasks, battle tasks, collective tasks, and/or subtasks assessed as “P” or “U”

(or “No Go,” if applicable).(3) For each task assessed as “P” or “U” (or “No Go”, if applicable), develop a training plan to raise the current

training level to a fully trained or “T” status (or “Go,” if applicable).

Note. In developing this training plan, consider only personnel and equipment assigned to the unit. Do not assume that existingpersonnel and equipment shortages will be filled or that additional training resources (ranges; ammunition; and training aids such asdevices, simulators, and simulations) that are not currently available to the unit or allocated in deployment/mobilization plans willbecome available before training starts. Assume that continuous training (that is, 24 hours a day, 7 days a week) will be conductedin accordance with logical and reasonable restrictions and breaks required for reasons of safety and/or to accomplish essentialadministrative and logistics requirements.

(4) Doctrinal training strategies, events, and methodologies for achieving full METL proficiency for many unitMETL tasks are detailed in ARTEP/MTP manuals. Unit commanders should use these doctrinal publications as a basisfor determining the required days to train to full METL proficiency and modify the timelines based on their ownexperience and first-hand knowledge of their units’ unique capabilities and training challenges.

(5) For commanders of units without ARTEP/MTP manuals or with unique mission-essential tasks, FM 25–100/101lists other METL supporting references to assist them in identifying doctrinal training requirements.

(6) In determining training time, do not include the time needed to conduct a field training exercise or commandpost exercise at levels of command higher than the reporting unit. (Also, see para 7–10 for guidance on determiningand reporting NBC training requirements and the NBC T-level and para 7–12 for guidance on determining andreporting the pre-mobilization training status level.)

(7) Determine the number of training days required to achieve full METL proficiency in accordance with paragraphs(3) through (6), above, and adjust the results, if necessary, based on the commander’s knowledge of the unit’s uniquecapabilities and challenges.

(8) Use the estimated number of training days needed to reach full METL proficiency to enter table 7–2 and identifythe T–Days status level associated with this estimate.

Table 7–2T–Days/T–NBC/T–Pre MOB

Estimated training days Level

0–14 115–28 228–42 343 or more 4

Notes:1 Commanders of major combat units assigned peacetime operational deployments who submit composite reports will use the instructions contained in par-agraph 11–3 and table 11–1 to determine their unit’s T-level.2 Table 7–2 is used to determine the status level associated with the commander’s estimate of the overall training days required (T–Days) in accordancewith paragraph 7–3 and also the NBC training status level (T–NBC) in accordance with paragraph 7–10 and the pre-mobilization training level(T–PRE–MOB) in accordance with paragraph 7–12.

53AR 220–1 • 15 November 2001

c. Note that any additional time required for a unit to train for operations under NBC conditions or to reach the levelof pre-mobilization training focus prescribed by the MACOM for RC units is included in this estimate that reflectsoverall training days. Report the estimate of the overall training days required in the USR as follows—

(1) Enter the number of estimated overall training days in TWRC1 (FLD 2A), TRAINDAT set, section B (fig 7–3).

Figure 7–3. Section B, Army reporting requirements, TRAINDAT set

(2) For units reporting APS, PC/ASORTS/ASORTS will automatically enter “50.”

7–4. Squad/crew/team/system manning and qualification dataa. Units to report. All AC and RC MTOE and TDA units will report squad/crew/team/system manning and

qualification data if they are either required to man any of the elements (that is, squads, crews, or teams) or areequipped with any of the weapons systems listed in table 7–3 or in PCASORTS. APS will not report this data.

b. Report consolidation. All FF-level units are required to consolidate and report, within their composite USR,squad/crew/team/system manning and qualification data reported by subordinate units/elements.

c. Additional reported data. MACOMs and FF-level units may direct subordinate units/elements to report manningand qualification data for additional MTOE/TDA squads/crews/teams/systems in the USR.

d. Squad/crew/team/system manning criteria. For the purpose of the squad/crew/team/system manning portion of theUSR, a soldier can man a required squad/crew/team/system position if he or she meets availability requirements inaccordance with paragraph 4–4 and appendix D of this regulation, and also if he or she is either assigned or attached tothe reporting unit or is battle-rostered for the required position in accordance with policy guidelines for battle-rosteringestablished at the major unit level (FF-level) or at higher levels. For the purposes of the squad/crew/team manningportion of the USR, personnel deployed for training or operational missions will be considered available if their unitsare determined to be available in accordance with paragraph 3–3c.

Note. The squad/crew/team manning status level must be established before squad/crew/team qualification can be determined.

(1) Fully manned squad/crew/team. The fully manned squad/crew/team standard is based on the manning require-ment for specific elements or systems established by MTOE and/or Army training doctrine. The fully manned standard

54 AR 220–1 • 15 November 2001

is established by TRADOC systems managers (USASOC for SOF-unique elements/systems) and is intended to reflect arobust manning level for the specified element/system and to provide the requisite number of soldiers to perform allcritical war-fighting tasks to standard within a continuous operations (24 hours) environment. Fully manned squad/crew/team standards are provided in table 7–3.

(2) Minimally manned squad/crew/team/system. Minimum squad/crew/team/system manning standards also are es-tablished by TRADOC systems managers (USASOC for SOF-unique elements/systems) and are intended to reflect theminimum number of soldiers needed to perform most critical war-fighting tasks to standard within a continuousoperations (24 hours) environment while accepting some risk in sustained mission accomplishment and/or forceprotection. Minimum manning standards are provided in table 7–3.

e. Squad/crew/team qualification criteria. After the manning status level has been established, commanders willdetermine the qualification status of their units’ squads/crews/teams/systems using the standards and criteria providedin table 7–3 in accordance with the following criteria—

(1) Qualified individuals. Qualified individuals are the fully qualified personnel by MOS and duty position who arerequired for any size squad/crew/team/system to be considered as either “qualified” or “combat capable.” Note thatqualified individuals first must have met the squad/crew/team/system manning criteria established to determine the“full” and the “minimum” manning levels by sub-paragraph 7–4d.

(2) Fully manned and qualified (FMQ). For the squad/crew/team/system to be considered fully manned andqualified, it first must meet the full manning criteria in sub-paragraph 7–4d and the applicable full manning standard intable 7–3. Subsequently, the members of the squad/crew/team/system who met the full manning criteria and who werecounted in order to meet the full manning standard must also meet the qualification requirements by number (that is,the number of qualified soldiers is equal to or greater than the number of soldiers required to meet the full manningstandard) and position (that is, all individual position qualification requirements are met) that are prescribed in table7–3 for that type squad/crew/team/system.

(3) Combat capable. For the squad/crew/team/system to be considered combat capable, it first must meet or exceedthe minimum manning criteria in sub-paragraph 7–4d and the applicable minimum manning standard in table 7–3.Subsequently, the members of the squad/crew/team/system who were counted in order to meet the minimum manningstandard must also meet the qualification requirements by number (that is, the number qualified solders is equal to orgreater than that required for minimum manning) and position (that is, all individual position qualification requirementsare met) that are prescribed in table 7–3 for that type squad/crew/team. Fully manned squads/crews/teams/systemshaving fewer than the number of qualified soldiers required for FMQ status, but having a sufficient number of qualifiedsolders to meet combat-capable criteria, are considered fully manned and combat capable. Note that the number ofcombat-capable squads/crews/teams/systems that are fully manned and the number of combat-capable squads/crews/teams/systems that are minimally manned are reported in separate data fields. (See sub-para 7–4g.)

(4) Exceptions. Note that, for USR purposes, TRC percentage standards in STRAC for aggregate weapons qualifica-tion are not applicable to the full/minimum number of individuals that must be qualified. Also note that the manningstatus of the squad/crew/team/system must be first determined in accordance with paragraph 7–4d before the qualifica-tion status of the squad/crew/team/system can be established. Therefore, for example, although a squad can be mannedwith more soldiers than the number determined to be qualified, the opposite of that situation is not possible.

Table 7–3Squad/crew/team/system manning and qualification criteria

Type squad/crew/team/system Qualified individuals Full/minimum manning level Notes

M1 TC and gunner 4/3 2M2 Vehicle CDR and gunner 3/NA1 2M3 w/dismounts Vehicle CDR and gunner 5/4 2 and 3M3 w/o dismounts BC and gunner 4/NA1 2Infantry squad(ABN/AASLT/RGR)

Squad LDR 9/7 3

Infantry squad (light) Squad leader 9/7 3Infantry squad (M2) Squad leader 9/7 3RECON squad Squad leader 5/4 3HMMWV scout squad Squad leader/gunner 3/NA1 3TOW section/squad SEC/SQD leader and gunner 3/NA1 4Combat engineer squad Squad leader 8/6 5Wheeled engineer squad Squad leader 7/6 5Combat engineer vehicle Crew 4/3MLRS Section chief and gunner 3/2 6Howitzer, M119/M102 Section chief and gunner 7/6 7Howitzer, M109A3/4/5 Section chief and gunner 9/8 7Howitzer, M109A6 Section chief and gunner 9/7 7Howitzer, M198 Section chief and gunner 10/9 7Mortar, 120 mm Squad leader and gunner 4/NA1 8

55AR 220–1 • 15 November 2001

Table 7–3Squad/crew/team/system manning and qualification criteria—Continued


Mortar, 107 mm (4.2 in) Squad leader and gunner 4/NA1 8Mortar, 81 mm Squad leader and gunner 5/3 7Mortar, 60 mm Squad leader and gunner 3/NA1 8Stinger/Avenger Team chief and gunner 2/NA1 9BSFV Vehicle CDR and gunner 5/4 10M6 Linebacker Vehicle CDR and gunner 3/NA1 11Patriot Crew 28/NA1 12AH–64A/D Pilot and co-pilot/gunner 2/NA1 13AH–1 Pilot and co-pilot/gunner 2/NA1 13OH–58A/C/D Pilot and co-pilot/gunner 2/NA1 13 and 14UH–60 Pilot and co-pilot 4/NA1 14CH–47 Pilot and co-pilot 4/NA1 14EH–60 Pilot and co-pilot 5/NA1 14UH–1H Pilot and co-pilot 3/NA1 14MEDEVAC Pilot and co-pilot/crew chief/

flight medic4/NA1 14

SFODA Detachment CDR 10/6 15SOTA Team leader 4/3 15CA TPT Team leader 6/4 15CA THST Team leader 4/3 15CA TST Team leader 4/3 15PSYOP DEV DET Detachment CDR 12/8 15TAC PSYOP DET Detachment CDR 13/8 15TAC PSYOP team Team leader 5/3 15UAV TBD TBD 16MAV/IAV TBD TBD 16Fox TBD TBD 16

56 AR 220–1 • 15 November 2001

Table 7–3Squad/crew/team/system manning and qualification criteria—Continued


LAV TBD TBD 16

Notes:1 “NA” indicates that minimum manning standards and criteria are not applicable to the squads/crews/teams/systems listed.2 M1/M2/M3 crew: TC/BC and gunner meet crew qualification standards in accordance with STRAC.3 Infantry/recon/scout squad/team: Must have a qualified squad leader (commander’s judgment based on soldier’s ability to perform the leader/individualtasks that support the unit’s METL). Must have soldiers (see full/minimum requirements in table 7–3 for number of soldiers required) who meet the standardsfor “individual” weapon qualification in accordance with STRAC. Must be able to man assigned crew-served weapon (that is, Dragon, M60/M2 machine gun,and MK–19 grenade machine gun) with qualified gunners in accordance with STRAC.4 TOW crew: Crew meets qualification standards in accordance with STRAC paragraph 5–6.5 Combat engineer squad/team: Crew is qualified in accordance with TC 5–150, Engineer Qualification Tables.6 MLRS section: Section chief and gunner must satisfactorily complete the launcher section evaluation, including tasks found in artillery table 2 (crew certifi-cation), in accordance with appendix I, FM 6–60, within the past 6 months. As part of a platoon- or larger-sized unit, the section must live fire 80 percent ofits METL-related fire mission tasks to ARTEP MTP standards twice annually for AC units and once annually for RC units. Eighth U.S. Army (EUSA) excep-tion applies.7 Howitzer section: Section chief, gunner, and crew must meet qualification/proficiency standards established by FM 6–50 and STRAC. Training require-ments include satisfactorily completing the cannon section evaluation and achieving at least 700 out of 1,000 points in accordance with appendix G, FM6–50, within the past 6 months for AC units and within the past year for RC units. The section chief and gunner must satisfactorily complete the gunner’squalification test and achieve at least 66 out of 92 points in accordance with appendix C, FM 6–50, within the past 6 months for AC units and within the pastyear for RC units. As part of a platoon or larger unit, the section must live fire 80 percent of its METL-related fire missions to ARTEP MTP standards annual-ly. For M109A6 (paladin units) incorporate the four paladin skills required in appendix B, FM 6–50, pages 4 and 29–32. Upon approval of the cannon sectionevaluation in FM 3.09.70 (paladin operations), use those new tasks for determining qualification. Note that commander, EUSA, by exception, may determineFA qualification status for USR reporting owing to range availability constraints and short-tour personnel turnover impact.8 Mortar crew (60 mm, 81 mm, 107 mm, 120 mm): Squad leader and gunner must pass the mortar gunner’s exam with the minimum score of 70 percent ineach event, and section leaders and FDC personnel must pass each event on the FDC exam within the past 6 months. Crew must meet the qualificationstandards in accordance with STRAC, paragraph 5–7.9 Stinger and Stinger/Avenger teams: Teams must meet the qualification standards in accordance with STRAC, paragraphs 4–5 and 4–7. Stinger andStinger/Avenger teams will be reported separately.10 Bradley Stinger fighting vehicle (BSFV): Vehicle commander and gunner are qualified on a Bradley table VIII within the past 6 months. Stinger team chiefand gunner meet qualification standards in accordance with STRAC, paragraph 4–8.11 M6 Linebacker: BC and gunner are qualified on a Bradley table VIII within the past 6 months. Stinger qualification TBD.12 Criteria for Patriot TBD.13 AH–64/AH–1/OH–58D crew: Assigned aviators must be readiness level (RL) one, per the appropriate aircrew training manual (ATM). Crews must meetthe gunnery qualification standards in accordance with STRAC and the FM 1–140 (helicopter gunnery). There is no requirement for aviation crewmen toqualify together as a crew.14 CH–47/UH–60/EH–60/UH–1H/OH–58A/OH–58C crew: Assigned aviators must be crew-qualified within the past 12 months. Crew meets the qualificationstandards in accordance with STRAC. MEDEVAC crews must have aviators, crew chief, and flight medic to be a qualified crew.15 Special forces operational detachment alpha/special operations team–alpha/civil affairs tactical planning team/civil affairs tactical HQ support team/ civilaffairs tactical support team/PSYOP development detachment/tactical PSYOP detachment/tactical PSYOP team: Meets individual and team training certifi-cations established by USASOC.16 Standards and criteria are under development by TRADOC. In coordination with the MACOMs (USASOC for SOF-unique elements/systems), TRADOCwill recommend adding new squads/crews/teams/systems to the above listing and will update the squad/crew/team/system manning and qualification crite-ria, as required.

f. Deployed units or detachments. Reporting units not having sufficient communications with deployed subordinateunits or detachments will assume no changes in manning and qualification have occurred within the deployedsubordinate unit(s) or detachment(s) since the initial deployment away from home station or parent organization.

g. Reporting procedures.

(1) Unit will report its applicable squads/crews/teams/systems by selecting item #11 ITAVS of the USR menu inPC/ASORTS. This item selection will enable the reporting unit to enter the data required for the squads/crews/teams/systems listed in table 7–3 and any additional squad/crew/team/system types that the unit has been directed to report bythe FF-level or higher-level unit. (See example at fig 7–4.) Commanders should include appropriate remarks forclarification.

57AR 220–1 • 15 November 2001

Figure 7–4. Submitting squad/crew/team/system status data

(a) First data field. The total number of reportable squads/crews/teams/systems (listed in table 7–3) that are requiredby MTOE.

Note. This number reflects the unit’s wartime requirements and will not change unless driven by a change to the unit’s MTOE. (Thistotal includes squads/crews/teams/systems that may be fully manned, minimally manned, partially manned, or unmanned.)

(b) Second data field. The total number of reportable squads/crews/teams/systems (listed in table 7–3) that areauthorized. This total includes squads/crews/teams/systems that may be fully manned, minimally manned, partiallymanned, or unmanned.

(c) Third data field. The number of fully manned and qualified (FMQ) squad/crews/teams/systems that meets thecriteria and standards established in the preceding sub-paragraphs and in table 7–3 for the full manning level and forwhich each soldier who is counted in order to meet the full manning level also meets the qualification requirementsprescribed for his position. (See para 7–4e(2).)

(d) Fourth data field. The number of fully manned and combat-capable (FMCC), reportable squads/crews/teams/systems that meets the criteria and standards established in the preceding sub-paragraphs and in table 7–3 for the fullmanning level and that also have the minimum number of qualified soldiers required to meet the qualification standardsestablished for the “combat-capable” status. (See para 7–4e(3).)

(e) Fifth data field. The number of reportable squads/crews/teams/systems that are fully manned but unqualified(FMU) in accordance with the manning and qualification criteria and standards established in the preceding sub-paragraphs and table 7–3.

(f) Sixth data field. The number of minimally manned and combat-capable (MMCC), reportable squads/crews/teams/systems that meets the criteria and standards established in the preceding sub-paragraphs and in table 7–3 for theminimum manning level and that also has the minimum number of qualified soldiers required to meet the qualificationstandards established for the “combat-capable” status. (See para 7–4e(3).)

(g) Seventh data field. The number of minimally manned but unqualified (MMU), reportable squads/crews/teams/systems that meets the criteria and standards established in the preceding sub-paragraphs and in table 7–3 for theminimum manning level but that does not have the minimum number of qualified soldiers required to meet thequalification standards established for the “combat-capable” status. (See para 7–4e(3).)

(h) Eighth data field. The number of partially manned/combat-ineffective (PMCI), reportable squads/crews/teams/systems that is manned with one or more soldiers but does not meet the criteria and standards established in thepreceding sub-paragraphs and in table 7–3 for the minimum manning level. Partially manned squads/crews/teams areconsidered combat ineffective.

(i) Ninth data field. The number of unmanned (UNMAN) (zeroed-out) squads/crews/teams/systems. Unmannedsquads/crews/teams are defined as those that are authorized by MTOE/TDA but to which no soldiers are assigned orfor which weapon systems and equipment have been placed in administrative storage in accordance with AR 750–1.

(2) The value in the first data field reflects the MTOE war-fighting requirement. The value in the second data fieldreflects the MTOE/TDA authorization, which may or may not correspond to the number of squads/crews/teams/systems

58 AR 220–1 • 15 November 2001

assigned. The value in the second data field should equal the sum of data fields 3 through 9 for each reportable squad/crew/team/systems (unless there are reportable squads/crews/teams/systems in excess of the MTOE/TDA authorizationactually assigned to the unit). Since deployed or detached squads/crews/teams are considered available for thisreporting requirement if their units are considered available in accordance with paragraph 3–3c, only MTOE changes orunavailable units would generate different totals.

h. Classification guidance. (See para 2–7.)

7–5. Determining the unit T-levelAfter the commander of the reporting unit has determined the T–METL status level of his unit in accordance withparagraph 7–2, figure 7–1, and table 7–1 and the T–Days status level of his unit in accordance with paragraph 7–3 andtable 7–2, the lower (worst case) of these two status levels will be selected and reported as the unit T-level.Commanders of AA-level units will review the results of their unit T-level determinations for doctrinal credibility byusing the training level review process described in paragraph 7–6. Note that commanders of major combat units thatsubmit composite reports with operationally deployed units/elements must determine the T-level of the major combatunit in accordance with table 11–1 and the instructions for deployed reporting contained in chapter 11.

7–6. The training level review processa. Concept.(1) The unit training level reported in the USR is intended to reflect the current status of a unit’s training

proficiency relative to that required by the unit in order for it to undertake the full wartime mission(s) for which it wasorganized or designed. Army’s training level metrics (that is, T–METL and T–Days) were updated to assist the unitcommander to more accurately, objectively, and uniformly assess his unit’s current training status measured againstwartime requirements by more closely linking this assessment to Army training doctrine. However, the evaluation ofu n i t M E T L p r o f i c i e n c y b y e a c h u n i t c o m m a n d e r r e m a i n s t h e m o s t c r i t i c a l e l e m e n t o f t h e U S R t r a i n i n g - l e v e ldetermination.

(2) Army doctrine for battle-focused training establishes that training events are the common building blocks thatsupport an integrated set of METL-related training requirements. The training level review process (TLRP) is based onthe notion that, with few exceptions, for each Army unit there is a menu of doctrinally based training events that theunit must accomplish on a recurring basis in order for the unit to achieve or maintain full METL proficiency, and alsothat commanders can significantly enhance the credibility of their training level determinations by routinely confirmingthat their units have executed to standard a high percentage of critical training events in accordance with the trainingtime/frequency requirements established by applicable Army training doctrine.

(3) The extent to which units are able to execute their doctrinally required training event requirements is a functionof both training opportunity and training resource constraints (including time available), programmed and non-programmed. However, in accordance with GSORTS guidelines, USR training levels are intended to indicate clearly aunit’s actual training requirements to achieve full METL proficiency, regardless of the causes of training deficienciesor the accommodations made owing to the reality of longstanding or unavoidable constraints. Although Army trainingstrategies seek to optimize the impact of resource application on unit training proficiency despite constraints, GSORTSmandates that this proficiency must be measured and reported in the USR relative to the full training requirement andnot just relative to the proficiency level resourced or expected. The pre-mobilization training status level reported byReserve component units is intended to reflect the effectiveness of actual resource execution. (See para 7–12.)

b. Purpose. The training level review process is a common-sense check by commanders of AA-level units to reviewthe results of their T-level determinations in light of their units’ accomplishment of critical training event requirements.

c. General.(1) Commanders of AA-level units will review their unit T-level determinations for doctrinal credibility by using

table 7–4 to compare the training event requirements accomplished by their units with the training time/frequencystandards established for those training event requirements, then by using table 7–5 to determine the training tempolevels associated with their unit’s training event accomplishments (based on the percentage of applicable training eventrequirements accomplished within the established time/frequency standards), and then by comparing their T-leveldeterminations with the training tempo levels.

(2) A unit’s training event accomplishments for applicable events should be determined from its training records.The time/frequency standards established for training event execution in table 7–4 are consistent with the minimumtraining event frequency requirements that are doctrinally prescribed or generally expected (assuming a normal level ofskill decay and personnel turbulence) for most Army units to achieve and maintain a high level of training proficiency(that is, the T-1 level). Not all Army units (especially RC units) are resourced (includes training time) to achieve ormaintain the T-1 level, and no units are expected to achieve status levels beyond those that have been resourced. Thetraining level review process was neither designed nor intended to suggest that either full METL proficiency or the T–1level can be attained or sustained with less training than that established by doctrine, even if the required training is notfully resourced and training strategies have been adjusted accordingly in recognition of the existing constraints.

(3) If CATS specifies other training frequency standards for units to achieve or maintain full METL proficiency thanthose established in table 7–4, the unit commander should apply the training frequency standards derived from CATS.

59AR 220–1 • 15 November 2001

Commanders also can add training event requirements to those listed in table 7–4 based on CATS, or on other doctrinalpublications if CATS is not applicable. However, additions or adjustments should not result in the masking of unittraining deficiencies, even if these deficiencies are the direct result of longstanding or well-known resource constraints.

d. Procedures.(1) Step 1. Identify and select applicable training event requirements.(a) Commanders should identify all applicable training event requirements from the menu of training events in table

7–4. Training events that are applicable for Army units by type and size also are discussed and described in doctrinalpublications, to include those addressed in paragraph 7–2c.

(b) Applicable training event requirements also may be either prescribed for training by commanders at higher levelsor identified by the unit commander in accordance with FM 25–101.

(c) Applicable training events identified or determined for use in the TLRP should reflect recurring trainingrequirements that directly support the achievement and sustainment of full METL training proficiency. The eventsidentified may be fully or partially resourced for training execution or totally unresourced.

(d) Specific training exercises are discussed (that is, objectives, execution, duration, participants, and so forth) inappendix C, FM 25–101. The 7 to 10 training event requirements that are the most applicable to the reporting unit andthat are most critical to achieving full METL proficiency should be selected for use in the review process. This range isestablished because it provides sufficient events to accommodate performance aberrations (that is, a T-1 level is notprevented merely because the performance criteria for a single event is not met) while maintaining simplicity incalculations. Selecting fewer than 7 events, or including additional (more than 10), but significantly less critical,training events in the process can distort results. Similar or interchangeable training events may be grouped togetherlogically to represent one training event requirement. For example, a tank battalion conducting BBS, JANUS, andARTBASS could group these events together as command and staff training to meet the criteria for selecting from 7 to10 of the unit’s most critical training events. Similarly, a CSS unit with very few crew-served weapons could grouptogether weapons qualification for both individual and crew-served weapons, if concurrently trained, as one trainingevent for purposes of the TLRP.

(2) Step 2. Determine the unit’s training tempo for the applicable training event requirements selected. Commandersof reporting units should use the unit’s training records to determine the time in months since the unit last conducted/executed each applicable training event requirement selected during step 1.

(3) Step 3. Determine the percentage of the applicable training event requirements selected that were executed tostandard within the time/frequency guidelines specified in table 7–4.

(a) If CATS or other doctrinal requirements for training time/frequency are more demanding, then commandersshould use the more demanding standard. Do not use a less demanding standard for training time/frequency, unlessCATS is not applicable and the less demanding standard is doctrinally supported and clearly and unequivocallyrepresents the unit’s actual training requirement to achieve and/or sustain full METL proficiency for its wartimemission(s). The use of less demanding training frequency standards must be approved or prescribed at the MACOMlevel.

(b) Consider intensity, duration, participation of key personnel, and so forth, in accordance with doctrinal standardsto determine whether training events were executed to standard.

(c) Based on the number of training events selected in step 1 and the number meeting established standards for bothfrequency and quality of execution (steps 2 and 3), use figure 7–5 to determine the applicable percentage.

(4) Step 4. Review the doctrinal credibility of the USR training level determination.(a) Using the percentage determined in step 3, enter table 7–5 and identify the training tempo level that is associated

with that percentage.(b) Compare this training tempo level with the unit’s T-level determined for unit status reporting in accordance with

paragraph 7–5. The training tempo level should be equal to or better than the unit’s T-level for the T-level determina-tion to have doctrinal credibility. (For example, the TT-1 level indicates doctrinal credibility for T-levels T-1 throughT-4; the TT–2 level indicates doctrinal credibility for T-2, T-3, T-4, and so forth.) Analyze the reasons for discrepan-cies, if any.

(5) Step 5. Take appropriate actions.(a) If the results of step 4 indicate that the unit’s TT-level does not indicate doctrinal credibility for the command-

er’s T-level determinations, then the commander must add appropriate comments (use free GENTEXT remarks entitledTRRAT) to explain the discrepancy. In his or her comments the commander should specify the training accomplishedin lieu of the doctrinally prescribed training events and/or should describe the situations or circumstances that enablethe unit to attain or sustain the level of training proficiency reported in the USR, despite its inability to accomplish thedoctrinally prescribed training event requirements.

(b) There are certain exceptional situations and circumstances that may enable certain Army units to achieve orsustain a higher level of training proficiency that that indicated by their training tempos. These situations andcircumstances are best explained by the commanders of the reporting units and, when documented in the USR,facilitate periodic requirements for analysis of unit training readiness and training resource allocation issues at higherlevels.

60 AR 220–1 • 15 November 2001

e. Exceptions and exemptions.(1) The MACOMs are delegated authority to exempt their subordinate reporting units from using the TLRP if it is

not applicable to the unit’s training requirements. Units that do not have a minimum of seven critical training eventrequirements should be considered for exemption.

(2) The MACOMs are also delegated authority to modify the training event frequency requirements established intable 7–4 based on their analysis of the wartime mission requirements of specific units.

(3) MACOMs will inform HQDA, (ATTN: DAMO–TR) of the exemptions and/or exceptions approved or pre-scribed at their level.

Table 7–4Training level review part 1: training event and time/frequency requirements

Menu of doctrinal training events Time/frequency standard (in maximum number of months since event was lastexecuted)

Individual weapons training/qualification 6 monthsCrew-served weapons training/qualification 6 monthsCFX/MAPEX/TEWT/TOCEX/STAFFEX 12 monthsSTX/LANES/drills 6 monthsGunnery (major weapon systems) 6 monthsSimulator training (that is, COFT, SIMNET, flight simulators, andso forth)

6 months

EDRE/DEPEX/MOBEX/ORE 6 monthsBCST/CPX/LCX/FCX/FTX 9 monthsCALFEX/LFX 6 monthsNTC/JRTC/CMTC/EXEVAL 18 monthsOther events In accordance with CATS/doctrinal publications

Table 7–5Training level review part 2: training tempo percentages and training level review

Percent of applicable training events accom- Training tempo (TT) level Training levels for which credibility is indicatedplished to standard within the established time/frequency standards

85% or more TT-1 T-1, T-2, T-3, and T-470%–84% TT-2 T-2, T-3, and T-455%–69% TT-3 T-3 and T-4Less than 55% TT-4 T-4

Figure 7–5. Determining the training tempo percentage

61AR 220–1 • 15 November 2001

7–7. Reporting training data on DA Form 2715a. Training T-level. TRRAT, TRAINING set, section A (fig 7–6).

(1) TWRC1 (FLD 2A): Enter the estimated number of training days needed to reach full METL proficiencydetermined in accordance with paragraph 7–3. (See fig 7–3.)

(2) TMETL (FLD 2B): Enter the T–METL percentage determined in accordance with paragraph 7–1. (See exampleat fig 7–3.)

(3) The unit’s overall training level (T-level) is the worst case of T–Days and T–METL status levels and is reportedin FLD 1, TRRAT, section A, joint reporting requirements, TRAINING set. (See fig 7–6.)

Figure 7–6. Section A, Joint reporting requirements, TRAINING set

b. Reasons training level not T–1. Complete TRRES (FLD 2), TRAINING set, section A (reasons training level isnot T-1) (fig 7–6). If TRRAT (FLD 1), TRAINING set does not contain a “1,” enter the training code from appendix Ethat shows the main reason the training level is not 1. If the training level is T-1, leave blank.

c. Reason for training level change. If a unit’s training level decreases from that submitted in its last report, thereason for the decrease will be addressed in the TRRAT GENTEXT remarks (fig 7–7).

d. Reporting TRRES. AWS will always report “6” for the TRRAT (FLD 1) and code “T–50” for the TRRES (FLD2).

62 AR 220–1 • 15 November 2001

Figure 7–7. Section D, TRRAT GENTEXT remarks

e. T-5 level. If HQDA or a MACOM directs or approves use of a T-5 level per paragraph 3–5, enter “43” or higherin TWRC1 (FLD 2A), TRAINDAT set, section B (fig 7–3), and a “5” in the TRRAT (FLD 1), TRAINING set, sectionA (fig 7–6).

f. Special circumstances. Enter “XX” in TWRC1 (FLD 2A, TRAINDAT set) if number of days to achieve fullMETL proficiency exceeds “99” or the number of days to achieve full METL proficiency cannot be determined owingto special circumstances (for example, inactivations, activations awaiting equipment fielding). “XX” will automaticallyequate to T–4 or T–5. As appropriate or directed, comments on days to train or special circumstances are required inthe TRRAT GENTEXT remarks set when this option is used.

7–8. Assessing the availability of critical resources required for trainingThe commander must determine if the unit has sufficient personnel and equipment (counting pooled and borroweditems) in order to train to perform the wartime mission(s) assigned. The commander will consider the following factorsin this assessment—

a. Personnel availability.(1) The commander will review the unit’s personnel strength report to determine if the strength level is above or

below 70 percent.(2) The commander will calculate the number of soldiers not available for training whose absence falls into one of

the following categories or sub-categories—(a) Special duty requirement (borrowed military manpower and troop diversion). (See para 4–9b(6)).(b) Deployment and schooling. (See appendix D.)(3) The commander will review the military occupational specialty (MOS) qualification and fill status and the

turnover rate for the unit that were determined during personnel calculations completed in accordance with instructions

63AR 220–1 • 15 November 2001

in chapter 4. The commander should also consider the time required to train soldiers who require foreign languageskills to the Army’s minimum proficiency level.

b. Equipment availability.(1) The commander will review the unit’s on-hand equipment status determined in accordance with the instructions

in chapter 5.(2) The commander will determine the availability of the required unit equipment for training using—(a) The operational status of the unit’s equipment determined in accordance with the instructions in chapter 6.(b) The location of the unit’s equipment determined in accordance with instructions in chapter 5.(c) The suitability of the unit’s on-hand equipment to support the unit’s METL.

7–9. Reporting resource constraintsa. Units will enter in TRAINDAT set, section B, fields 3 through 13, the degree to which resource constraints are

preventing the unit from maintaining a training tempo necessary to achieve and sustain the highest training status level(that is, the T–1 level). (See fig 7–3.)

b. In each of these fields, if the resource area has an insignificant impact on training, enter “A”; if the resource areahas a minor impact, enter “B”; if the resource area has a major impact, enter “C”; and if the factor prohibits trainingtempo necessary to achieve or maintain the T–1 level, enter “D.”

(1) ITAVS (FLD 3) Assigned strength shortfall. Enter assigned strength shortfall indicator. When an overall assignedstrength shortfall, lack of key MOS-qualified personnel, and lack of full-time manning support (RC only) hindertraining, commanders will comment in training remarks.

(2) ITSDR (FLD 4) Special duty requirements. Enter special duty requirements indicator. Assess the impact of thediversion (includes BMM and TD) of unit personnel to meet special duty requirements.

(3) ITAFT (FLD 5) Availability of funds. Enter availability of funds indicator. Higher commanders will commentwhen assistance is needed from the next higher headquarters.

(4) ITAEM (FLD 6) Availability of equipment or materiel. Enter availability of equipment or materiel indicator. Thiscategory includes NBC equipment and is not limited to equipment authorized in a unit’s MTOE or TDA.

(5) ITAQL (FLD 7) Availability of qualified leaders. Enter availability of qualified leaders indicator. Emphasizethose leaders most needed for training in the unit’s METL (for example, platoon leaders, platoon sergeants, and squadleaders). This entry must be left blank if ITAVTRNG (FLD 8) is used.

(6) ITAVTRNG (FLD 8) Status of aviator training. For units with aircraft pacing items, enter the unit aviator T-level(numeric value 1, 2, 3, or 4) derived in accordance with TC–1–210, chapter 6. The availability of non-aviator leaders inthese aviation units will be addressed in training remarks. When a unit has aviators but no aircraft pacing items,include the aviator T-level in training remarks. While an important factor in determining the unit’s T-level, the unit’saviator T-level may not be the sole driving factor in determining the overall T-level for aviation units. This entry mustbe left blank if ITAQL (FLD 7) is used.

(7) ITATF (FLD 9) Availability of training areas/facilities/training aids, devices, simulations, and simulators. Enteravailability of training areas and facilities indicator. Consider quality, size, and accessibility of training areas availableto the unit and local/national restrictions on those training areas. Also consider availability of training aids, devices,simulators, and simulations.

(8) ITAFL (FLD 10) Availability of aviation fuel. Enter the availability of fuel indicator. Consider need for bothfield and garrison training.

(9) ITATA (FLD 11) Availability of ammunition. Enter indicator for availability of ammunition (does not includewartime basic load). Consider both training standard and training unique ammunition, including sub-caliber rounds fortraining devices.

(10) ITATM (FLD 12) Availability of time/flying hours. Consider the impact of competing activities that detract fromtraining time to the extent that they reduce training readiness (such as school support activities and umpire details forother units). Also consider the impact of available flying hours on training.

(11) APS reporting. Always enter “A” for fields 3 through 12.c. Use narrative remarks on resource constraints. In those cases where fields 3 through 13 do not contain the letter

“A” (“1” for aviation units in FLD 8), or where SD personnel restrict the ability of the unit to train to the T–1 level,the impact of the resource constraints and/or SD personnel will be addressed in section D, TRRAT GENTEXT remarkssection, of the USR (fig 7–7). (Note that SD personnel status data is reported in the USR in accordance with para 4–9.)

7–10. Training level under unique conditionsa. Army units are required to report NBC training days and the chemical and biological defense resource and

training (CBDRT) level in accordance with CJCSM 3150.02. Army training doctrine establishes that NBC is acondition under which a unit must operate and be able to perform its mission. Army unit commanders are directed tointegrate NBC training into their unit’s overall training program, and the NBC training requirement is not treated as aseparate and distinct task. In other words, for Army units, NBC training days required are included in the total number

64 AR 220–1 • 15 November 2001

of required training days; therefore, the TWRC1 data entry, which reflects the total number of required training days,cannot be less than the data entry for NBC training days required (TNGDYREQ).

(1) Commanders at all levels assess their units’ ability to execute wartime mission(s) by assessing the demonstratedproficiency of subordinate units, leaders, and individual soldiers in or during the exercises and events discussed inparagraph 7–2b. An NBC environment is an assumed training condition associated with the unit’s METL, whereapplicable.

(2) In addition to the above factors, commanders will also consider the availability of chemical personnel (MOS54B/74A) and the availability and serviceability of chemical equipment when determining the CBDRT level of theunit.

b. To report the chemical and biological defense resource and training (CBDRT) level—(1) Step 1.Determine NBC training days (NBC TNGDYREQ). The commander may determine that—(a) The days required for NBC training purposes cannot be isolated or separately determined from those training

days required to reach full METL proficiency because the unit must train on all of its METL tasks under NBCconditions. In this case, the commander will report a number for NBC TNGDYREQ that is equal to that entered forTWRC1. Example 1: The commander estimated and reported in accordance with paragraph 7–3 that 14 days arerequired to reach full METL proficiency (that is, TWRC1 is 14) and, in step 1 above, that the NBC training daysr e q u i r e d c a n n o t b e d i s t i n g u i s h e d f r o m t h e o v e r a l l t r a i n i n g d a y s r e q u i r e d . T h e c o m m a n d e r w i l l r e p o r t N B CTNGDYREQ as 14 days and will use this number to determine the NBC T-level in step 2 below.

(b) The days required to train under NBC conditions or on NBC specific tasks because of training or equipmentshortcomings may be isolated or separately determined from those training days determined to be required to reach fullMETL proficiency. In this case, the commander will report these NBC training days as his NBC TNGDYREQ, whichmust be a number greater than zero (0) and must be fewer than the total number of overall training days reported inTWRC1. In another example, the commander may have determined in accordance with paragraph 7–3 that 17 trainingdays are required to reach full METL proficiency, and in step 1 above, that 3 of those 17 days are required solelybecause of NBC training requirements. If so, the commander will report the NBC TNGDYREQ as 3 and will use thisnumber to determine the NBC T-level in step 2 below.

(c) The unit does not require any training days for NBC training to achieve full METL proficiency. In this case, thecommander will report his NBC TNGDYREQ as zero (0).

(2) Step 2. Determine the NBC training level. Using the NBC TNGDYREQ determined in step 1, use table 7–2 todetermine the unit’s CBDRT-level (T–NBC). Use section D, Environmental factors report (fig 7–8), with pre-printedlabel, RICDA, to report “1, 2, 3, or 4,” determined from table 7–2.

(3) Step 3. Determine if remarks are mandatory. If NBC TNGDAYSREQ is not zero, then remarks explaining thereasons why training time is needed are mandatory. For example, “Unit requires 3 NBC training days to conductdecontamination training,” or “Unit is an infantry company that must train all tasks under NBC conditions to attain fullMETL proficiency.”

c. HQDA may direct selected units to report their training levels under severe weather conditions. (See fig 7–8.)

65AR 220–1 • 15 November 2001

Figure 7–8. Environmental factors report

7–11. Unit deployment tempoa. Background: HQDA requires a management tool to identify units with predicted annual unit deployment tempo

(DEPTEMPO) exceeding 120 unit days. This data is required to fulfill joint staff reporting requirements, and to advisesenior Army leaders of Army DEPTEMPO trends. Additionally, with certain exceptions, the FY 2000 National DefenseAuthorization Act (now codified as section 487, title 10, United States Code) mandated that all Services must reportthe Active Army and Reserve component units participating at the battalion level in contingency operations, majortraining events, and other named exercises to the Office of the Secretary of Defense annually as part of the AnnualDefense Report (ADR). The availability of reliable DEPTEMPO and projected DEPTEMPO data is absolutely criticalto force employment and force structure decisions made at both Service and Joint/OSD levels. Commanders of AA-level units possess the training, exercise, and operational mission schedules in sufficient detail to track DEPTEMPOevents and to develop reliable DEPTEMPO projections. It is imperative that commanders of all reporting unitsaccurately determine and report DEPTEMPO.

b. DEPTEMPO is determined using personnel tempo (PERSTEMPO) data. PERSTEMPO measures individualdeployment rates and MOS deployment rates. DEPTEMPO is the number of days in a month that a unit would have todeploy as a whole to replicate the effects of actual unit, subordinate unit, and individual soldier deployments. The newcongressional and Army definition of deployment is as follows: “A member of the armed forces is considered to bedeployed or in a deployment on any day on which, pursuant to orders, the member is performing service in a trainingexercise or operation at a location or under circumstances which make it impossible or infeasible for the member tospend off-duty time in the housing in which the member resides when on garrison duty at the member’s permanentduty station.” Deployment, as defined above, does not include a member who—

(1) Is performing service as a student or trainee at a school (including any government school).(2) Is performing administrative, guard, or detail duties in garrison at the member’s permanent duty station.

66 AR 220–1 • 15 November 2001

(3) Is unavailable either because of hospitalization at the member’s permanent duty station or in the immediatevicinity of the member’s permanent residence, or because of disciplinary action taken against the member.

c. All Army MOTE and Active and Reserve component units and TDA units deployable or apportioned to a jointoperations plan that submit an AA-level USR will determine and report DEPTEMPO data in each of four categories(A, B, C, and D), if applicable, and also a DEPTEMPO total to indicate the unit’s level of deployment activity duringthe reporting period. This information also may indicate why the unit is not fully trained on its METL tasks; the resultsof unit DEPTEMPO determinations, however, may not correlate to the unit commander’s assessments of the percent ofMETL trained or the number of required training days that are determined on the basis of wartime requirements.

d. The four DEPTEMPO categories have been adjusted to mirror those prescribed in the recently enacted legislationthat established the PERSTEMPO reporting requirements within the ADR, as discussed in paragraph 7–10a above.DEPTEMPO data in the new “mission support TDY” category (category D) are not included in the calculation of totalunit DEPTEMPO. The DEPTEMPO categories are as follows—

(1) Category A. All deployments directed by joint deployment orders (such as those supporting the multi-nationalforce observer, MFO–Sinai); deployments in support of all humanitarian missions; deployments supporting militaryassistance to civilian authority (such as those in response to forest fires, hurricanes, and civil unrest); deploymentsupporting counter-drug operations; and U.N. staff and special forces team deployments.

(2) Category B. Overnight training in support of joint training exercises (CINC/JCS directed), such as Bright Starand Intrinsic Action.

(3) Category C. Overnight training on-post or at sub-installation training areas (local training areas off-post) and/orovernight training off-post at a combat training center. (Note that RC soldiers in AT, IDT, or ADSW status (traditionaltitle 32 personnel) are not included.)

(4) Category D. Mission support TDY. (Duties that include meetings, conferences, staff visits, staff augmentation,and medical appointments.)

(5) Total. The sum of categories A, B, and C for both the current month and annual projection.e. To determine DEPTEMPO for USR purposes, the unit commander can use the PERSTEMPO application report,

which calculates DEPTEMPO automatically, or he or she may manually calculate DEPTEMPO. Manually calculatedDEPTEMPO data should match the PERSTEMPO application report if all mandated entries are submitted correctly tothe PERSTEMPO database at the unit level. DEPTEMPO is determined as follows—

(1) Multiply the number of soldiers deployed times the number of days for each deployment during the currentreporting period to determine deployment man-days (for example, 20 soldiers X 10 days deployed=200 man-days; 3soldiers X 8 days deployed=24 man-days). Separate these man-days by deployment category (that is, A, B, C, or D).Add the man-days in each deployment category to determine the total deployed man-days for each category.

(2) Divide the total number of man-days in each deployment category by unit assigned strength and round to thenearest whole number. (For example, notional unit X has an assigned strength of 250. Man-days determined forcategory A is 450. DEPTEMPO for category A is 450 divided by 250=1.8, rounded to nearest whole number=2.DEPTEMPO (by category) = total deployed man-days (by category) divided by the unit assigned strength. (Results arerounded to nearest whole number.)

(3) Add the whole numbers for categories A, B, and C together to determine the unit DEPTEMPO total. (Forexample, if category A=2; category B=5; category C=2; DEPTEMPO total is 2 + 5 + 2 = 9.) (Note that category DDEPTEMPO data is not used in the calculation of the unit DEPTEMPO total.) A DEPTEMPO calculation example isprovided at figure 7–9.

67AR 220–1 • 15 November 2001

Figure 7–9. DEPTEMPO calculations

f. The DEPTEMPO calculation should not include personnel absent from the unit because of the followingobligations—

(1) Professional development schooling (for example, MOSQ, Airborne, BNCOC, PLDC, and so forth).(2) Administrative duties, such as guard duty, details, staff duty officer, charge of quarters, and so forth.g. The following are reporting requirements—(1) All MTOE AC and RC units and TDA units deployable, deployed, or apportioned to a joint operations plan that

submit an “AA” level USR will include both current and projected annual DEPTEMPO data in their reports. Deployedunits are not excused from reporting.

(2) In the appropriate PC/ASORTS data fields, enter both current and (projected) annual unit DEPTEMPO, both byDEPTEMPO category and total. All DEPTEMPO data entries must be rounded to the nearest whole number; decimalswill not be used.

(a) Current DEPTEMPO is that DEPTEMPO accrued during the USR reporting period. For AC units that submitregular reports monthly, 31 days is the maximum total DEPTEMPO for a USR reporting period. For RC units thatsubmit regular reports quarterly, 92 days is the maximum total DEPTEMPO for a USR period. PC/ASORTS will notaccept total current DEPTEMPO greater than the number of days in the reporting period. DEPTEMPO will be reportedmonthly by AC units and quarterly by RC units. To preclude any confusion regarding the period addressed in thereport, RC units that have been activated will continue to report DEPTEMPO quarterly in their USRs submitted inJanuary, April, July, and October.

68 AR 220–1 • 15 November 2001

(b) Projected annual total DEPTEMPO is that total DEPTEMPO projected for the next 12 consecutive calendarmonths. Unit long-range training calendars normally will be the primary reference to determine projected annualDEPTEMPO. Projected annual DEPTEMPO maximum is 365 days. (See example at fig 7–9.)

(c) In all deployed unit status reports, current and projected annual DEPTEMPO will be included consistent with theperiodic reporting requirements for DEPTEMPO (that is, the monthly requirement for AC units and the quarterlyrequirement for RC units). (See chap 11.) Enter DEPTEMPO using the ITATM GENTEXT format within the remarkssection.

1. DEPTEMPO data within deployed unit status reports will consist of two entries, each consisting of five dataelements. The “current” DEPTEMPO data entry will begin with “CDEPTEMPOS” and end with “CDEPTEMPOE.”The projected “annual” DEPTEMPO data entry will begin with “PDEPTEMPOS” and end with “PDEPTEMPOE.”Both the current and projected annual DEPTEMPO entries will be in the following format: CAT A days/CAT B days/CAT C days/CAT D days/total days (A+B+C). Current DEPTEMPO entries will use two digits (use zeros whenrequired; for example, 04 or 09).

2. Projected annual DEPTEMPO entries will use three digits (use zeros when required; for example, 049 or 009).Both current and projected annual total DEPTEMPO entries must equal the sum of the respective component categories(that is, categories A, B, and C) of total DEPTEMPO.

7–12. Tailored reporting for Reserve component unitsa. Reserve component commanders submitting an FF- or AA- level unit status report also are required to report a

pre-mobilization training readiness level that is determined based on the pre-mobilization training goals/guidancespecified in MACOM directives. For example, an RC infantry unit may have been directed by its MACOM to train toproficiency at the platoon level. After notifying HQDA (ATTN: DAMO–ODR), MACOM commanders may specify intheir directives those subordinate RC units that are exempted from this reporting requirement because pre-mobilizationtraining goals are either not applicable or inappropriate.

b. The pre-mobilization training readiness level is calculated to indicate the number of days of training that isrequired by the RC unit to reach proficiency measured against the pre-mobilization level of training focus establishedby the MACOM (for example, the platoon level). The pre-mobilization level of training focus considers the unit’straining strategy and the resources available to the unit.

c. RC unit commanders estimate the number of training days required to achieve the pre-mobilization training statusprescribed by the MACOM, using the same process and methodology discussed in paragraph 7–3. The determination ofthis pre-mobilization training status level is based on the commander’s assessment of training proficiency in the tasksrequired for the level of pre-mobilization training focus; therefore, it may not correspond to the unit T-level that isdetermined in accordance with paragraph 7–5.

(1) As an example, a RC battalion has just completed annual training. The level of training focus for maneuver unitswas platoon level in core critical tasks. The commander determines that his maneuver platoons achieved a 90-percentlevel of proficiency and estimates that 7 additional days of training are required by the platoons to become fullyproficient. Additionally, in accordance with paragraph 7–3, the commander estimates that 40 days of training arerequired by the battalion to achieve full METL proficiency for the battalion’s wartime mission and that, in accordancewith paragraph 7–5, the battalion’s training level is T–3 (that is, the worst case of T–METL and T–Days status-leveldeterminations).

(2) In this example the commander would record “3” in TRRAT (FLD 1), TRAINING set, section A (fig 7–6) toindicate the unit T-level, and “40” in TWRC1 (FLD 2A), TRAINDAT set, section B (fig 7–3). In the TRRATGENTEXT remarks field labeled: PREMOB–LVL “1” PREMOB–DYS, “07” would be entered to reflect the pre-mobilization training readiness. The commander then will enter the number of days to train in PREMOB–DYS field ofthe “Misc. new AR 220,” which is item 10 of the USR menu on the PC/ASORTS/ASORTS unit status reportingsoftware.

Note. The estimate of the number of pre-mobilization training days required (that is, 7 days) is included in the number of overalldays required to attain full METL proficiency (that is, 40) and is not additive to the total of overall training days required. Also notethat the pre-mobilization training status level (T–PREMOB) of “1” is determined from table 7–2.

(3) Provide other pertinent comments on training status as appropriate in the free GENTEXT remarks entitledTRRAT.

Chapter 8Mission Accomplishment Estimate

8–1. Generala. The mission accomplishment estimate (MAE) is the reporting unit commander’s subjective assessment of the

unit’s ability to execute that portion of the wartime mission that it would be expected to perform if alerted/committed

69AR 220–1 • 15 November 2001

within 72 hours of the “as-of” date of the report. The commander expresses this estimate in terms of the percentage ofthe wartime mission that the unit could accomplish if it were alerted/committed.

b. Commanders of deployed units also will use the MAE to assess and to report the unit’s effectiveness in executingits wartime mission, unless the unit has been assigned a derivative UIC for USR purposes. DUIC units will not reportMAE. (See para 11–6.)

c. This chapter provides instructions for determining the MAE by commanders of reporting units and explains itsrelationship to the unit’s overall C-level.

8–2. Purposes of the MAEThe MAE provides a definitive estimate of a unit’s ability to perform its wartime mission. The C-level and the MAEreflect the reporting unit commander’s assessments of the overall status of his or her unit and its ability to accomplishassigned wartime missions within a set time period. MAE does not apply to APS or DUIC units.

8–3. Instructions for determining the MAEa. Commanders of all reporting units will determine the MAE for the unit and record the MAE in the READYSEG

set, field 1, of section B (fig 8–1). To reduce administrative requirements and for simplicity, commanders will use thesame criteria for all types of units.

Figure 8–1. READYSEG set, MAE

b. When determining the MAE, the commander must consider critical resources such as personnel, equipment,training, and repair parts availability. The commander should consider the status of these resources in light of otherimportant factors that affect the unit’s ability to accomplish its wartime mission. Those factors include but are notlimited to—

(1) Readiness factors (such as mobility; operating tempo (OPTEMPO); exercises; unit morale and leadership; C3I;and measured areas of equipment, personnel, and training).

(2) Sustainability of the unit (includes the availability of spares and repair parts, including ASL, to support the unit’sMETL, if applicable).

(3) Current status of modernization in the unit.(4) Force structure design.c. The USR does not provide (nor is it practical to specify) the quantitative and qualitative factors that may affect a

unit’s ability to accomplish its wartime mission; therefore, the commander must examine critically all appropriate unitreadiness indicators and carefully consider significant factors when determining the unit’s MAE. For example—

(1) A transportation company may have an overall level of C-4 owing to EOH shortfalls, but the commander maydecide (after considering the specific equipment shortages, the availability of repair parts, and workload factors) thatthe unit can actually perform 75 percent of its wartime mission.

(2) An MTOE hospital at S–4 EOH may be able to deploy and operate 70 percent of its hospital beds and 60percent of its operating tables. If, in this example, the commander determines and reports a MAE of 60 percent, thencommanders at higher levels will have important additional information regarding the unit’s actual overall capabilitythat is not reflected clearly by the unit’s C-level status.

70 AR 220–1 • 15 November 2001

d. Commanders will assume that the following actions/events will continue at planned or demonstrated rates, unlessdefinite indications of change have been identified or established—

(1) Re-supply actions.(2) Consumption and attrition rates.(3) Operating tempo (OPTEMPO).

8–4. Determining the MAE for hospital unitsTo determine the MAE of hospitals—

a. Commanders will estimate the overall ability of a hospital unit based on the unit’s wartime mission, all factorsconsidered in determining the unit’s C-level, and other factors (qualitative and quantitative) not previously considered.

b. Commanders of MTOE hospitals will determine the number of operational beds, by type, and the number ofsurgical tables that could be supported by available unit personnel and equipment. The MAE percentage is based on thepercentage of hospital beds, by type, and operating tables the unit can support compared to the number required. TheMAE will reflect the lower percentage of the two (beds or operating tables).

c. Commanders will use the FREE GENTEXT remarks, section D, using the label “MAE.” These remarks shouldrefer to the MAE percentage and reflect required versus operational capability based on available personnel andequipment. Use the following format: Required versus operational intensive care/intermediate care/minimal care/ beds/operating tables.

d. Commanders also must explain the MAE percentage and limiting factors. For example: “Four of six operatingtables can be operated with current personnel strength; therefore, MAE is 67 percent” (4 of 6 equals 67 percent).

e. Commanders will list the required and operational (required/operational)data that the MAE was based on, asfollows: hospital MAE is XXX intensive care beds: XXXX/XXXX minimal care beds: XXXX/XXXX operating roomtables: XXX/XXX

8–5. Reporting ASL status data in the MAE sectionCommanders of reporting units will report prescribed ASL status data in their comments in the MAE section of theUSR (DA Form 2715) in accordance with the following instructions—

a. Commanders of AA-level units that are authorized class IX ASL will report as follows—(1) The ASL status data required will be submitted in GENTEXT comments in the following format: total ASL on-

hand quantity=_____ total safety level (SL) + operating level (OL) quantity=_____ percentage of fill=_____.(2) The information needed by the reporting AA-level unit commander in order to report the above ASL status data

in the USR will be extracted from the Standard Army Retail Supply System (SARSS) monthly spares readiness report(preformatted report number PCNAJU–358). The required data for the USR will be automatically calculated by SARSS2 and provided to the appropriate unit commanders on the 10th of each month in the SARSS monthly spares readinessreport.

b. In accordance with paragraph 8–1 of this regulation, commanders of AA-level units will assess the impact ofASL class IX shortages, if any, on their units’ ability to accomplish their assigned wartime missions, if alerted orcommitted, and they also will include this assessment in their GENTEXT comments in the MAE section of the USR.

c. Commanders of AA-level reporting units that are not authorized a class IX ASL in peacetime (for example, RCunits) are not required to submit ASL status data in the MAE section of their USRs.

d. Commanders of FF-level units will consolidate the class IX ASL status data reported by their subordinate AA-level units and will report the aggregate ASL status in the MAE section of the USR as follows—

(1) Report the aggregate ASL status as a percentage of fill that reflects the quantity of ASL items required (SL +OL) by subordinate reporting units to support operations actually on hand and available to those subordinate units.

(2) Determine this percentage by first adding separately both the actual ASL on-hand quantities and the ASLquantities prescribed for operating and safety levels (SL + OL) reported by the AA-level units; then by dividing theASL on-hand total by the operating and safety level quantity total and multiplying the results by 100.

e. In accordance with paragraph 8–1 of this regulation, commanders of FF-level units will assess the impact of ASLclass IX shortages, if any, on their units’ ability to accomplish their assigned wartime missions, if alerted or committed,and they also will include this assessment in their GENTEXT comments.

f. Commanders of FF-level reporting units that are not authorized a class IX ASL in peacetime (for example, RCunits) are not required to submit this ASL status data in the MAE section of their USRs.

8–6. MAE bands of effectivenessa. The 90 to 99 percent band. Report in this band when it is estimated that the unit possesses required resources and

training and is in position (or has the necessary mobility) to undertake (for a period of 72 hours) the full wartimemission for which it has been organized and designed. The status of personnel, equipment, supplies, consumables, andunit position does not decrease probability of mission success or increase vulnerability of the unit. The unit does notneed extraordinary measures or extensive outside mobility assets to compensate for deficiencies.

b. The 80 to 89 percent band. Report in this band when it is estimated that the unit possesses required resources and

71AR 220–1 • 15 November 2001

training and is in position (or has the necessary mobility) to undertake (for a period of 72 hours) the full wartimemission for which it has been organized and designed. The status of personnel, equipment, supplies, consumables, andunit position does not decrease probability of mission success or increase vulnerability of the unit under mostenvisioned operational scenarios. Increases in vulnerability are acceptable relative to mission criticality. Unit mayexperience isolated decreases in flexibility in methods of mission execution. The unit does not need extraordinarymeasures or extensive outside mobility assets to compensate for deficiencies.

c. The 70 to 79 percent band. Report in this band when it is estimated that the unit possesses required resources andtraining and is in position (or has the necessary mobility) to undertake (for a period of 72 hours) the full wartimemission for which it has been organized and designed. The status of personnel, equipment, supplies, consumables, andunit position will decrease probability of mission success or increase vulnerability of the unit under many, but not all,operational scenarios. The unit will experience significant decreases in flexibility and increases in vulnerability inmany, but not all, operational scenarios. The unit may need extraordinary tactics, procedures, operating tempo(OPTEMPO), or extensive outside mobility assets to compensate for deficiencies.

d. The 50 to 69 percent band. Report in this band when it is estimated that the unit possesses required resources andtraining and is in position (or has the necessary mobility) to undertake (for a period of 72 hours) the full wartimemission for which it has been organized and designed. If the situation allows, the unit may be directed to undertakeportions of its mission with resources at hand. The status of personnel, equipment, supplies, consumables, and unitposition decreases probability of mission success or increases vulnerability of the unit under all envisioned scenarios.Mission success is possible for certain isolated scenarios, but flexibility is severely restricted. The unit cannotcompensate for deficiencies even with extraordinary tactics, procedures, OPTEMPO, or extensive outside mobilityassets.

e. Below 50 percent band. Report in this band when the unit is undergoing a service-directed resource action and isnot prepared, at this time, to undertake the crisis or wartime missions for which it has been organized and designed.Units who meet the criteria for C-5 reporting may report in this band. This band will also be used for units that are soshort of personnel or equipment, or so deficient in training that they are unable to perform at least 50 percent of theirassigned wartime missions.

8–7. C-level and corresponding MAE rangesa. C-1. Recommended MAE range: 90 percent to 99 percent.b. C-2. Recommended MAE range: 80 percent to 89 percent.c. C-3. Recommended MAE range: 70 percent to 79 percent.d. C-4. Recommended MAE range: 0 percent to 69 percent. (The commander of a C–4 unit might report MAE less

than 70 percent.)e. C-5. Recommended MAE range: 0 percent to 50 percent.f. Level 6. Level 6 is not used as an overall category level.

8–8. Commander’s subjective MAE evaluation and C-level comparisonCommanders will compare the MAE determined with the overall C-level using the MAE ranges provided in paragraph8–7. If the MAE determined by the commander does not correspond to the unit’s overall C-level, then the commandershould consider upgrading/downgrading the C-level. However, commanders must ensure that their actions to upgrade/downgrade the unit’s C-level will result in a more accurate portrayal of actual unit status that neither masks norexaggerates readiness deficiencies.

Chapter 9Overall Unit Level and Special Instructions for Remarks Entries for Regular Reports

9–1. Overall unit levela. To determine the READY, field 5, OVERALL set, section A (fig 9–1), the commander should review levels

attained in the measured resource areas, C-level definitions, and the MAE assessment. He or she should also considerdeficiencies, resources, and other unit readiness factors that were not previously considered or addressed.

(1) The start point for determining the overall status of a unit is the lowest level attained in a measured resource/status area (that is, PER, EOH, ES, or training). If no resource/status area is level 5, the commander can upgrade ordowngrade the unit’s overall level (that is, the C-level) if the calculated level does not accurately reflect the actualstatus of the unit’s ability to accomplish its wartime/mission requirements. If one or more of the resource/status areas islevel 5, then the unit must report C-5. The commander cannot change a calculated resource/status area level.

(2) Status of prescribed load list (PLL) items, authorized stockage list (ASL) items, basic loads, common table ofallowances (CTA) items, equipment regardless of readiness code (ERC A, ERC B, or ERC C), and special skillrequirements (SQI, LIC, or ASI) are examples of other factors that should be considered in selecting an overall C-level.Units staffed and equipped at ALO 2 or lower may be unable to achieve C-1. No unit is expected to attain a unitstatus level that exceeds the level at which it is resourced.

(3) If the MAE selected does not correspond to the overall C-level determined, then the commander should considerupgrading/downgrading the unit’s C-level.72 AR 220–1 • 15 November 2001

Figure 9–1. Section A, Joint reporting requirement

73AR 220–1 • 15 November 2001

b. Reserve component units will report the training level reflecting the status of METL proficiency to accomplishthe wartime mission and the pre-mobilization training status level. The wartime mission training level will bedetermined in accordance with paragraph 7–5, and the pre-mobilization training status level will be determined inaccordance with paragraph 7–12. The wartime mission C-level is determined by using the lowest level attained in themeasured resource areas (includes the wartime mission training level determined in accordance with paragraph 7–5).The pre-mobilization C-level is determined in the same manner as the wartime mission C-level, except that the pre-mobilization T-level (PREMOB–LVL) is used in lieu of the wartime mission T-level in the determination process.Enter the pre-mobilization overall C-level in the READY GENTEXT remarks labeled: PREMOB–OVALL.

c. The overall NBC level is determined and reported to reflect the ability of the reporting unit to perform its wartimemission under chemical and biological conditions. It corresponds to the lowest (worst case) status level resulting fromthe commander’s specific determinations of the unit’s NBC equipment status (the NBC S-level) in accordance withparagraph 5–13 and the unit’s NBC training status (the NBC T-level or T–NBC) in accordance with paragraph 7–10.PC/ASORTS software automatically compares the data entered by the reporting unit for the NBC S-level and for theNBC T-level and selects the lowest (worst case) of these two status levels to populate the data field for the overallNBC level (that is, TREAD “CBDRT” in the READY field of the OVERALL set). While the NBC S-level and theNBC T-level are not factors in determining the unit’s S-level and T-level, respectively, commanders of reporting unitsshould consider the unit’s NBC level when determining whether the unit’s C-level should be upgraded or downgraded.

9–2. Joint reporting dataa. Overall set.(1) Field 1, classification, and field 2, TRANS TYPE. These fields are described in paragraph 3–7.(2) Field 4, RICDA (date of report). Enter the “as-of” date of the report or date of change, if applicable. In positions

1 through 4 of field 4, enter the calendar year. In positions 5 and 6 of field 4, enter the number of the month. Inpositions 7 and 8 enter the day. For example, enter 15 October 2001 as “20011015” (YYYYMMDD).

(3) Field 4, TREAD (type of report). Units submitting a regular report (AA-level) or a FF-level composite reportmust enter “OVALL” in the TREAD field to create an acceptable report.

(4) Field 5, READY (overall unit rating). Use the overall C-level in accordance with paragraph 9–1a. However, if aresource/status area level is 5, the overall level must be C–5.

(5) Field 6, REASN (primary reason overall C-level not 1). If READY (field 5) does not contain a “1,” enter theprimary reason code from appendix E that shows the primary factor that prevents a C–1 overall level. However, if thelevel in the READY field is the result of an upgrade or downgrade, place an “X” in REASN field. If READY is a “5,”then REASN must be “N.”

(6) Field 7, SECRN (secondary reasons overall level is not 1). Enter a code from appendix E that represents thesecondary factor preventing a higher overall level. The REASN code for the secondary factor may be from the sameresource area as the primary factor, but it cannot be the same code. If READY is a “5,” enter a code from table 9–1 inthe REASN field.

Table 9–1Reason codes for C–5 reporting

Code Definition

If the unit is C–5 because of a recent activation:P08 Organization recently activated (if PER is the driving factor)S18 Organization recently activated (if EOH is the driving factor)R06 Organization recently activated (if ES is the driving factor)T24 Organization recently activated (if TR is the driving factor)

If the unit is C–5 because of pending inactivation:P06 Organization inactivating (if PER is the driving factor)S17 Organization inactivating (if EOH is the driving factor)R80 Organization inactivating (if ES is the driving factor)T25 Organization inactivating (if TR is the driving factor)

If the unit is C–5 because of a reorganization (MTOE change):P74 Unit reorganizing (if PER is the driving factor)S91 Unit reorganizing (if EOH is the driving factor)RBE Unit reorganizing (if ES is the driving factor)T47 Unit reorganizing (if TR is the driving factor)

If the unit is C–5 because of a low ALO:P65 Service constraint (if personnel less than 70 percent authorized)S93 Service constraint (if not authorized enough equipment to attain

S–3)RBK Service constraint (if ES is R–5)

74 AR 220–1 • 15 November 2001

Table 9–1Reason codes for C–5 reporting—Continued

Code Definition

T54 Service constraint (if training rating is T–5)

If the unit is C–5 because of not being manned:P78 Unit not mannedS94 Notional unit, no equipment authorizedRBG Notional unitT54 Notional unit

If the unit is C–5 because of DEPMEDS:P78 Unit not manned and/or equippedS13 Equipment in administrative storage/pre-positionedRBK Equipment not available due to service constraintT31 Shortage equipment

(7) Field 8, TERRN (tertiary reasons overall level is not 1). Enter a code from appendix E that represents thetertiary factor that prevents a higher overall level. It may be from the same resource area as either the primary orsecondary factor, but it cannot be the same code.

b. Forecast set.(1) Field 1, CARAT (forecast category level change). If a unit’s overall C-level is less than 1, a forecast change of

the overall level (higher or lower) and the forecast date to achieve this level (CADAT, field 2 of FORECAST set) isrequired.

(a) If a unit’s overall C-level is 1, but the commander is aware of a potential change, he or she must report theforecasted level and estimated date.

(b) If a unit’s overall C-level is 1, and the commander is not aware of a C-level change, leave blank.(2) Field 2, CADAT (forecast date of change in overall level). If CARAT (field 1, FORECAST set) contains an

entry, enter the date of projected change. If CARAT is blank, leave blank.c. Category limit set.(1) Field 1, LIM (category level limitation). Enter reported unit’s ALO, numeric. For APS reporting, it is not

required. Leave blank.(2) Field 2, RLIM (reason for organization less than 1). Enter “P” or “S” if a unit’s ALO is different from 1. If the

primary area decremented as a result of assigned ALO is personnel, enter a “P”; if the primary area decremented isequipment, enter an “S.” If “1” is entered in LIM field, leave RLIM blank.

9–3. Army-unique dataa. DA Form 2715. Section B, DA Form 2715, was completed using instructions in the previous chapters. This form

provided additional data on the four resource areas to help Army agencies analyze a unit’s status and allocateresources. (See fig 9–2.)

75AR 220–1 • 15 November 2001

Figure 9–2. Section B, Army reporting requirement

76 AR 220–1 • 15 November 2001

b. ARMYRPT set.(1) Field 2, report type. Enter KA1 for regular reports or KA2 for change report(2) Field 3, ALO (authorized level of organization). Enter the number reflecting the reporting unit’s ALO. If a unit

submitting a report is not assigned an ALO, then, for unit status reporting purposes, determine an ALO based on theparent unit’s ALO.

(3) Field 4, RICDA (date of report). Enter the “as-of” date of the report or date of change, if applicable. In position1 thru 4 of field 4, enter the calendar year. In position 5 and 6 of field 4, enter the number of the month. In position 7and 8, enter the day. For example enter 15 October 2001 as 20011015 (YYYYMMDD).

(4) READYSEG set .(5) Field 1, MAE. Enter MAE percentage derived from chapter 8. For APS reporting, leave blank.(6) Field 2. Enter the “OO.” For APS reporting, leave blank.(7) Fields 3, 4, and 5. Enter the unit’s MTOE/TDA number, e-date, and command and control number (CCNUM).

All AA-level units must submit this data.

9–4. Commander’s remarksa. To support and amplify data submitted in sections A and B of the unit status report, provisions have been made

for the submission of remarks using sections C and D of DA Form 2715. The report provides for both mandatory andoptional remarks.

b. Remarks should be as concise as possible. Authorized abbreviations as documented in AR 310–50 should be usedwhen appropriate. Remarks should not contain information that is in other portions of the report. For example, “Unit isC-2 owing to a shortage of personnel” is a redundant remark since this information is already contained in section A ofthe report. Remarks should provide information and details that will help to resolve the problems that degrade theunit’s status.

c. Remarks concerning the degradation of a unit’s status because of MTOE/TDA changes will be specific. They willinclude the most critical personnel and equipment changes from the old MTOE/TDA that are causing the degradation.

9–5. READY and REASN remarksa. READY and REASN GENTEXT remarks relate to the overall level of a unit. READY/REASN remarks must be

concise, to the point, and stand alone.(1) Ready remarks are mandatory for all reporting units and should focus on the unit’s ability to accomplish its

wartime mission. (See fig 9–3.)

77AR 220–1 • 15 November 2001

Figure 9–3. Section C, READY remarks

(2) REASN remarks are required only if the overall unit level is subjectively upgraded or downgraded.

(3) When the unit’s overall level differs from the lowest resource area level, both READY and REASN remarks arerequired. An “X” is entered in the OVERALL set, section A, field 6 (REASN). Commanders must clearly state whythey feel the calculated levels are not truly representative of the unit’s status. (See fig 9–4.)

78 AR 220–1 • 15 November 2001

Figure 9–4. Section C, REASN remarks

b. HQDA requests no information with a classification higher than CONFIDENTIAL unless the commanderdetermines SECRET information is needed to clarify a situation affecting the unit’s overall C-level. If information of ahigher classification is used, the USR must be classified with the highest classification.

c. READY/REASN remarks report, section C, consists of the following fields—(1) Transaction field. Enter “A” for READY or REASN remark during normal reporting. PC/ASORTS will update

the transaction type field with an “A.”(2) Label field. Enter “READY” in the label field if READY remarks are being submitted, or enter “REASN” in the

label field if REASN remarks are being submitted.

9–6. Preparation of general remarksa. Specific resource area remarks have been discussed in the applicable chapter for each resource area. This section

discusses the mandatory remark entries as they relate to all the measured resource areas. These remarks should clarifyand support data submitted in sections A and B of the report. Units that do not attain a C-level equal to 1 in ameasured resource area (P, S, R, or T) must submit remarks on that area explaining the primary reasons C–1 was notattained. To facilitate automated analysis of the remarks section of the unit status report, sections C through D and theUIC (UIC of reported unit) and date of report (RICDA) fields will be system-generated from data entered in sections Aand B of DA Form 2715.

b. The following entries are mandatory for each remark—(1) Security classification. Enter appropriate security classification in sections A, B, C, and D.(2) Transaction type field. In section D, for all reports where transaction type is required, always enter “A.”c. For labeled sets, use one of the following, depending on the area being addressed—(1) Section D “2PSPER” of DA Form 2715 (Personnel Strength by Grade), already overprinted (section D), is

79AR 220–1 • 15 November 2001

mandatory to submit available personnel strength. PC/ASORTS will calculate the aggregated strength and include thestrength in the completed system-generated report.

(2) Section D “2RQPER” of DA Form 2715 (Military Occupational Specialty Shortage Report), with remarks, isrequired for units reporting P–4.

(3) Section D “2PIESTAT” of DA Form 2715 (Pacing Item Status Report) is mandatory for the submission of allpacing item equipment status.

(4) Section D “2ERCFOUR” of DA Form 2715 (Equipment That Is S-level 4) is mandatory for all reporting units tosubmit ERC–A equipment line items that are at a level of S–4.

(5) Section D “2EOHSHRT” of DA Form 2715, (Equipment Shortage Report) is mandatory if ERC–A equipmentshortfalls prevent attainment of EOH S-level of S–1.

(6) Section D “2PIERRAT” of DA Form 2715, (Pacing Item Operational Percentage Report) is mandatory to submitthe operational percentage of all pacing items.

(7) Section D “2ERCERRT” of DA Form 2715, (Operational Percentage Report) is mandatory if “ERRAT” is lessthan 1.

(8) Section D “TRRAT” of DA Form 2715, (TRRAT GENTEXT remarks form) is mandatory for all reporting unitshaving linguist MOSs to submit language information.

(9) Section D “2Language” (GENTEXT remarks form) is mandatory for all reporting units having MOSs with “L”identifiers to submit language shortages.

9–7. Higher command remarksRemarks by higher commanders will be entered on free NARR/GENTEXT remark, section D. (See para 2–6 for furtherinstructions.)

9–8. Special instructions when a unit is called up, mobilized, deployed, or employeda. Units alerted, called up, mobilized, or deployed will follow slightly different procedures when submitting unit

status reports. These changes are necessary to meet special requirements and to increase the utility of the report, and, insome cases, they also will reduce reporting requirements. The term deployed, as used in this section, does not apply tounits forward-stationed in peacetime. The special instructions below supplement the USR policy guidelines containedin chapter 2.

(1) After mobilization/federalization, and within 24 hours of the arrival of the advance party at the mobilizationstation, RC units will submit a regular report to the mobilization station. This regular report establishes the RC unit’sstatus at mobilization/federalization. Subsequently, RC units will submit a regular and/or change reports in accordancewith the USR submission requirements prescribed in chapter 2 for AC units.

(2) After deployment, AC and RC units will submit a deployed report on the 15th of each month to indicate theunit’s status while deployed.

(3) After redeployment and within 24 hours of the unit’s closure at the home station (AC units) or the redeploymentmobilization station (RC units), AC and RC units will submit a regular report to indicate the unit’s status followingredeployment. Subsequently, AC units and those RC units still on active duty will submit a regular report on the 15thof each month.

(4) Upon demobilization and termination of federal status, RC units will comply with USR submission requirementsin chapter 2 that are applicable to RC units.

b. Change reports in accordance with paragraph 2–4c and table 2–1 will continue to be required of all units (AC andRC), and USR submission timelines for active component units in table 2–1 become applicable to RC units uponmobilization/federalization.

9–9. Validation reportingAll Reserve component units (USAR and ARNGUS) and APS must submit a validation report monthly, unlessapplicable changes to unit status (see policy guidance in chapter 2) or the report submission timelines established bytable 2–1 require the submission of a change report or a regular report, respectively. To create a validation report, theunit will complete the SORTUNIT set and the RPTDUIC set of section A only. The word “VALID” must be entered infield 2 of RPTDUIC set.

Note. Reason codes must be placed in the SECRN field of the OVERALL set if the overall unit level is C–5 and the REASN fieldindicates an “N.”

80 AR 220–1 • 15 November 2001

Chapter 10Composite Reports

10–1. Generala. These reports provide an assessment of the status of a major combat unit and its ability to accomplish assigned

wartime missions, based on the condition of subordinate units/elements and their ability to operate together. Divisions,regiments, separate brigades, or special operations groups/regiments/commands, divisional brigades operating separate-ly, armored cavalry regiments, and Army pre-positioned sets (APS) with UICs ending in “FF” will submit compositereports.

b. Commanders of major combat units assigned or currently conducting peacetime operational deployments will usethe instructions and criteria in the applicable chapters of this regulation to determine and report the levels of measuredresource areas (that is, P, S, R, and T) and the C-level in their composite reports. Chapter 11 provides policy guidanceand instructions for PCTEF reporting and for using special criteria to determine the training level.

c. Composite reports are based on the calculation of the average status level within the major combat unit for eachof the three resource areas (PER, EOH, and ES) for which a unit status level is determined and reported by organicAA-level units (do not consider the band, adjutant general (AG), and finance units). Apply the rounding rule describedin paragraph 3–3d, if necessary. These calculations determine the average status level (by resource area) for organicreporting units and establish the status levels for personnel, EOH, and ES for the major combat unit.

d. A composite training level (T-level), mission accomplishment estimate (MAE), and overall C-level will bedetermined using the procedures outlined in the applicable chapters of this regulation; also, commanders of majorcombat units should consider any additional factors that are essential to the ability of the major combat unit to operateas an effective combat force. For example, to determine the T-level from T–METL and T–Days, the commander of amajor combat unit should consider the training proficiency of his staff, the need to conduct training exercises at themajor combat unit level (for example, the brigade level, division level) and the availability of critical training resources(for example, ranges, training areas, simulators, facilities) required by subordinate units, especially if multiple subordi-nate elements have requirements for the same limited training resource. Even if all AA-level units are T–1, thecommander of the major combat unit could determine that the composite T-level is T–2, T–3, and so forth, because ofhis consideration of additional factors and circumstances that were not considered by his subordinate commanders.Similarly, the commander of a major combat unit could determine a higher T-level than that reported by most of hissubordinate elements because of the ability of the major combat unit to resolve or mitigate the training issues cited bythe commanders of the subordinate units. The training level reported in the USR for the major combat unit should belinked to a sound training plan, developed in coordination with commands at higher levels, for achieving or sustainingfull METL proficiency at the major combat unit level. Assessments, estimates, and assumptions used to develop thetraining plan should be accurate and/or reasonable in light of the major combat unit’s wartime mission requirementsand unique operational environment. Major combat units also are required to consolidate and report, within theircomposite report, squad/crew/team/system manning and qualification data reported by their subordinate units. Subordi-nate units/elements, to include personnel and equipment, will be considered available in accordance with the standardrules and procedures for the availability of units established in paragraph 3–3c.

10–2. C–5 composite report instructionsa. Units submitting composite reports will include subordinate units reporting level C-5 in measured resource area

or status level computations. When computing composite resource/status levels, include these units as level C-4. If thenumber of C-5 subordinate units degrades the status of the parent unit below a C-3 overall unit status level, the parentunit will designate the appropriate resource area and the unit’s overall level as C-5 (must be approved by an MACOM).The number of subordinate units reporting C-5 will be recorded on DA Form 2715, remarks section, READYSEG set,field 2, section B.

b. C-5 inactivating/discontinuing units may be excluded from composite reports if they are within 180 days of theire-dates. The major combat unit rendering the composite report will continue to report the number of C-5 units in theirREADYSEG set, section B. This allows continued accountability of C-5 units. C-5 reporting units will continue toreport in accordance with this regulation.

10–3. Reserve component training levela. Commanders of Reserve component units submitting a composite report will report the unit’s training level (T-

level) and the pre-mobilization training status level, if applicable. The training level (T-level) is applicable to all unitsand reflects the training proficiency of the units for their wartime missions and tasks. The pre-mobilization trainingstatus level reflects the training proficiency of the unit to accomplish the missions and tasks prescribed by theMACOM for pre-mobilization training. If pre-mobilization training is not applicable to the RC unit, then the MACOMmay exempt the RC unit from the requirement to determine and report its pre-mobilization training status level. Thepre-mobilization training status level will be calculated in accordance with paragraph 7–12.

b. The pre-mobilization C-level is calculated in accordance with paragraph 10–5 in the same manner as the C-level,except that the composite pre-mobilization training status level is used instead of the composite T-level that reflects

81AR 220–1 • 15 November 2001

w a r t i m e m i s s i o n p r o f i c i e n c y . E n t e r t h e p r e - m o b i l i z a t i o n C - l e v e l i n t h e R E A D Y G E N T E X T r e m a r k s l a b e l e d :PREMOB–OVALL.

10–4. Reporting personnel/EOH status during partial deploymentsa. Commanders of major combat units required to submit composite reports will determine and report a separate

status level for personnel and EOH if they have subordinate units/elements considered non-available for USR purposes.(Refer to chap 3, para 3–3c for policy guidance regarding the availability of subordinate units/elements for USRpurposes.) This requirement to report separate status levels for personnel and EOH is intended to enable the com-mander of a major combat unit to provide an accurate assessment of the unit’s actual personnel and equipment statusand to enable HQDA to assess the wartime capability of the major combat unit (based on the assumption that non-available personnel and equipment have been reunited with the major combat unit) during partial deployments.

b. The first status level for personnel and EOH will be determined in accordance with the guidance and instructionscontained in chapters 3, 4, and 5. The availability of subordinate units (including personnel and equipment) that aredeployed for operations out of their areas of operation (or of units that cannot meet their wartime mission requirementsbecause of deployments) is addressed in paragraphs 3–3, 4–4, and 5–7. In general, personnel attached to deployed unitsare considered non-available and equipment loaned to deployed units is considered not on-hand to the reporting unit. Indetermining the availability of personnel and equipment and whether separate status reporting is required for deployedsubordinate units/elements, the commanders of partially deployed major combat units should consult with theirMACOM for guidance or assistance regarding the applicability of the criteria and standards provided in the aforemen-tioned paragraphs to their units’ specific deployment situation.

c. A second subjective level, with comments, is made by the reporting major combat unit commander to describe theunit’s wartime mission capability if non-available personnel and/or equipment are assumed to have been reunited withthe major combat unit.

(1) The second personnel level will be entered in the “PRRAT2” field of the “Misc New AR 220” remark (item 10)of the USR menu on the PCASORTS / ASORTS unit status reporting software.

(2) The second EOH level will be entered in the “ESRAT2” field of the “Misc New AR 220” remark (item 10) ofthe USR menu on the PCASORTS/ASORTS unit status reporting software.

d. If, for USR purposes, subordinate units/elements are considered available, then commanders of partially deployedmajor combat units are not required to determine and report a separate status level for personnel and EOH.

10–5. Determining composite C-levelsa. An upgrade or downgrade of the computed overall level should be considered if the commander believes that it

does not accurately represent the status of the unit. Measured resource areas/status levels and a C–5 level cannot bechanged.

b. Determine composite C-levels and resource area status levels using the outline below and table 10–1. Examplesshowing step-by-step calculations are provided at figures 10–1 and 10–2.

Table 10–1Composite level criteria (PER, EOH, and ES)

Level At least 50 percent of units at: Average of units

1 1 1.54 or less2 2 or better 1.55 to 2.443 3 or better 2.45 to 3.344 Cannot meet criteria to be level 3

82 AR 220–1 • 15 November 2001

Figure 10–1. Composite level calculation, separate infantry brigade (mechanized)

83AR 220–1 • 15 November 2001

Figure 10–2. Composite level calculation, separate infantry brigade

84 AR 220–1 • 15 November 2001

10–6. Completing composite reports—generala. Section A: SORTUNIT set, field 5, OVERALL set, field 1 and section B: ARMYRPT set, field 1 (classification).

Enter “S.” All major combat unit USRs will be classified SECRET.b. On DA Form 2715, transaction code field in sections A and B, enter “C” for recurring or change reports. Code A

is entered for initial reports only. Code D is entered to delete all unit status data.

10–7. Section A of DA Form 2715a. SORTUNIT set.(1) Field 1, ANAME (name of unit). No entry is allowed in this field because it is automatically generated by

SORTS.(2) Field 2, unit identification code (UIC). The “W” is preprinted. Complete this entry with the UIC of the

submitting unit’s MACOM.(3) Field 3, SEQNO (sequence number/report number). Enter the report number, showing the batch report number in

which this report appears among other reports being submitted by the reporting/submitting organization.(4) Field 4, DTG (date time group when report was submitted). In positions 1 and 2 enter the day of month. In

positions 3, 4, 5, 6 and 7 enter the applicable ZULU time (hours in positions 3 and 4; minutes in positions 5 and 6; Zin position 7). In positions 8 and 9 enter the number of the month. In positions 9 and 10 enter the last two digits of thecalendar year. For example, enter 15 October 1995, 09:45 ZULU as 150945Z1995 (DDHHMMMMYYYY).

(5) Field 5, SCLAS; OVERALL set, section A, field 1, classification; ARMYRPT set, section B, field 1, classification.Enter “C” for CONFIDENTIAL for battalion- and squadron-size units. Enter “U” for UNCLASSIFIED for smaller sizeunits. Enter “S” for SECRET if the report contains secret data because of association with a classified plan, operation,or exercise. (See para 2–7 for further guidance.)

b. RPTDUIC set.(1) Field 1, unit identification code (UIC). Enter UIC of unit being described by the data in the report.(2) Field 2, NOCHG (no change indicator). All reserve units will enter “VALID” in this field to validate previously

reported unit data when the unit is submitting a monthly validation report. Enter “OVALL” for the quarterly regularreports and change reports.

c. OVERALL set.(1) Field 2; PERSDATA set, EQOHDATA set, EQMCRDAT set, TRAINDAT set. Field 1, TRANS type (type of

transaction submitted). Enter “A” (initial), “C” (regular or change), or “D” (delete). Normally, the entry will be “C,”meaning a recurring or change report is being submitted.

(2) Field 3, RICDA (date of report). Enter the “as-of” date of the report or date of change, if applicable. In position1 thru 4 of field 4, enter the calendar year. In position 5 and 6 of field 4, enter the number of the month. In position 7and 8, enter the day. For example, enter 15 October 2001 as 20011015 (YYYYMMDD).

(3) Field 4, TREAD (type of report). Units submitting a composite report must enter “OVALL” in this field to createan acceptable report.

(4) Field 5, READY (overall unit rating) . Use the overall C-level from step 8 in paragraph 10–5b. However, if aresource area level is C-5, then the overall level must be 5.

(5) Field 6, REASN (primary reason overall level not 1). If READY (field 5) does not contain a 1, enter the primaryreason code from appendix E that shows the primary factor that prevents a C-1 overall level. However, if the level inthe READY field is the result of an upgrade or downgrade, place an “X” in REASN field, or if READY is 5, thenREASN must be N.

(6) Field 7, SECRN (secondary reason overall level not 1). Enter a code (from appendix E) representing thesecondary factor that prevents a higher overall level. This code may be from the same resource area as the primaryfactor, but it must be a different code. If the overall level (READY field 5) has been subjectively changed (X reportedin the REASN, field 6), report one of the following codes: PUP for personnel, SUP for equipment on hand, RUP forequipment readiness, or TUP for training.

(7) Field 8, TERRN (tertiary reason overall level not 1). Enter a code (from appendix E) that represents the tertiaryfactor that prevents a higher overall level. It may be from the same resource area as either the primary or secondaryfactor but cannot be the same code. If these instructions do not apply, leave TERRN (field 8) blank.

d. PERSONNEL set.(1) Field 1, PRRAT (personnel level). Use data from step 6 in paragraph 10–5b, or if HQDA/MACOM has directed/

authorized use of a P–5 level, enter “5.”(2) Field 2, PRRES (reason personnel level is not 1). If PRRAT field does not contain a 1, enter the personnel code

(from appendix E) that shows the main reason the personnel level is not 1; otherwise, leave blank.

85AR 220–1 • 15 November 2001

e. EQSUPPLY set.(1) Field 1, ESRAT (equipment on-hand level). Use data from step 6 of paragraph 10–5b. However, if HQDA/

MACOM has directed/authorized use of an S–5 level, enter “5.”(2) Field 2, ESRES (reason equipment on-hand level is not 1). If ESRAT field does not contain a 1, enter the

equipment-on-hand code (from appendix E) that shows the main reason the equipment on-hand level is not 1;otherwise, leave blank.

f. EQCONDN set.(1) Field 1, ERRAT (equipment serviceability). Use data from step 6 in paragraph 10–5b. However, if HQDA/

MACOM has directed/authorized use of an R–5 level, enter “5.”(2) Field 2, ERRES (reason equipment serviceability level is not 1). If ERRAT field does not contain a 1, enter the

equipment readiness code (from appendix E) that shows the main reason the equipment readiness level is not 1;otherwise, leave blank.

g. TRAINING set.(1) Field 1, TRRAT (training level). Use data from step 6 In paragraph10–5b. However, if HQDA/MACOM has

directed/authorized use of a T–5 level, enter “5.”(2) Field 2, TRESS (reason training level is not 1). If TRRAT field does not contain a 1, enter the training code

(from appendix E) that shows the main reason the training level is not 1; otherwise, leave blank.h. FORECAST set.(1) Field 1, CARAT (projected overall level). If READY (field 5, OVERALL set) is not 1, then CARAT must be

reported. The reported forecast level in the CARAT (field 1) must be higher than the current reported READY. If,READY is 1, leave blank.

(2) Field 2, CADET (projected date of change in overall level). If CARAT field contains an entry, enter the date ofprojected change. If CARAT field is blank, leave CADET blank.

i. CATLIMIT set.(1) Field 1, LIM (category level limitation). Enter reported unit’s ALO, numeric. APS reporting is not required.

Leave blank.(2) Field 2, RLIM (reason for organization less Than 1). Enter “P” or “S” if a unit’s ALO is different from 1. If the

primary area decrements as a result of assigned ALO is personnel, enter a “P,” if the primary area decrements isequipment, enter an “S.” If 1 is entered in LIM field, leave RLIM blank.

10–8. Section B of DA Form 2715a. Exceptions. Section B is completed generally the same as for battalion- and smaller-size units. The exceptions

described in the paragraphs below apply.b. ARMYRPT se.t(1) ARMYRPT, field 3, ALO (authorized level of organization). Enter reporting unit’s ALO, numeric. If a unit

submitting a composite report is not assigned an ALO, for unit status reporting purposes determine an ALO based onthe average ALO assigned to all organic units (round to the nearest whole number).

(2) ARMYRPT set, field 4, RICDA (date of report). Enter the “as-of” date of the report or date of change. Inpositions 1 through 4 of field 4, enter the calendar year. In positions 5 and 6 of field 4, enter the number of the month.In positions 7 and 8 enter the day. For example, enter 15 October 2001 as 20011015 (YYYYMMDD).

(3) PERSDATA set, PROFIS set, FEMALE set, and ACTGURES set. Strength calculations for each set must includeall personnel within the major combat unit, including those not assigned to reporting subordinate units (for example,four-man chemical detachments).

c. EQMCRDAT set. Leave blank.d. READYSEG set.(1) MAE, field 1. Enter MAE percentage for the composite unit derived in accordance with chapter 8. For APS

reporting, leave blank.(2) C-5, field 2. Enter the number of C-5 units, including those units exempted from the composite calculations. For

APS reporting, leave blank.(3) Fields 3, 4, and 5. Enter the unit’s MTOE number, EDATE, and CCNUM, if applicable.e. EQOHDATA set and ERC B and C equipment. Leave blank.f. TRAINDAT set. The composite unit commander will use the same procedures established in chapter 7 of this

regulation to assess the composite unit’s training status and training resource requirements.

10–9. Mandatory remarks for composite reporta. READY and REASN GENTEXT remarks (section C) also apply to composite reports. READY remarks are

required by all reporting units and should focus on the unit’s ability to accomplish its wartime mission. REASNremarks are required if the overall unit level differs from the lowest resource area level (subjective upgrade ordowngrade). Mandatory remarks also are required from commanders of major combat units using the special training

86 AR 220–1 • 15 November 2001

level criteria that incorporate the Army’s disengagement planning guidance and from those who have PCTEF-reportable subordinate units/elements. See chapter 11 for specific policy guidance and instructions. When a unit’soverall level is subjectively upgraded or downgraded, both READY and REASN remarks are required. (See para 10–4for specific guidance.)

b. Resource area remarks (section D) described in this paragraph relate to composite reports. As with regularreports, these remarks should clarify and support data submitted in sections A and B. Units that do not attain a level of“1” in a measured resource area must submit remarks on that area explaining the primary reasons C-1 was not attained.(See chap 9 and the related chapters for additional guidance for mandatory remarks.)

c. Units submitting composite reports will ensure that the information provided in the composite 2PSPER set(section D) accurately reflects the aggregate strength figures of all subordinate organic units. (Do not include attachedunits.)

d. All composite units will also report a composite NBC equipment status and NBC T-level in accordance withparagraphs 5–13 and 7–10).

e. The commander’s top three significant issues, in order of priority, should be submitted as a READY GENTEXremark. These issues are briefed routinely to the CSA.

f. All major combat units (those with UICs ending in “FF”) will provide a 90-day projected C level (overallreadiness) based on the commander’s assessment of his subordinate organic units’ projected levels. These projectionfigures will be reported in the composite report as a READY GENTEXT remark.

Chapter 11Unit Status Reporting Before, During, and After Deployment

11–1. Generala. Joint regulations require military units to report via the Status of Resources and Training System (SORTS) for all

operational environments. SORTS data is the major source of unit information used for operational planning necessaryfor adequate and feasible military responses to crises and time-sensitive situations. Accordingly, Joint guidelinesrequire commanders of SORTS reporting units to assess their unit’s status against the wartime mission(s) that the unitwas designed to undertake as well as against any peacetime operational deployments that the unit is assigned toexecute. Commanders of SORTS reporting units determine and report the unit’s C-level to indicate the unit’s wartimemission status and the unit’s percent effective (PCTEF) level to indicate the unit’s ability to execute currently assignedpeacetime operational deployments. For USR purposes, peacetime operational deployments requiring a PCTEF reportare those involving the movement of an Army reporting unit or its reportable subordinate elements away from theirhome station(s) to accomplish operational requirements as directed by a higher headquarters. Peacetime operationaldeployments encompass broad mission types, such as small-scale contingencies (SSC), military operations other thanwar (MOOTW), and stability and support operations (SASO), and they include a wide range of activities such aspeacekeeping, humanitarian relief, and support to civil authorities. They do not include unit deployments to accomplishtraining or to participate in training exercises.

b. In peacetime, the Army is the reporting authority for SORTS. During a crisis and in wartime, the Armycomponent command assumes responsibility for Army organizations under the operational control of the combatantcommand for which it is the component command. Once a unit is deployed in response to a crisis or operational plan(OPLAN) execution, the CJCS will determine (by coordinating with the Services and CINCs concerned) any changesto the frequency, content, or level of reporting. The policy and reporting procedures for the deployed USR establishedin this chapter are applicable to deployed units when the Army is the reporting authority. The deployed USR providesthe CJCS, CINCs, and the Army Staff with the minimum information required to execute their responsibilities toemploy, resource, and support deployed units.

11–2. Concepta. Pre-deployment.(1) PCTEF. AA- and FF-level units, in whole or in part, will report PCTEF in accordance with paragraph 11–3.

Units directed to report in accordance with paragraph 11–6 will submit PCTEF independent of their parent unit.(2) Training level (T-level). When required or directed, FF-level units will use special criteria to determine their T-

levels in accordance with paragraph 11–4.(3) Units reporting in accordance with paragraph 11–6. CINCs and JCS, in coordination with HQDA, will

determine if or which ad hoc organizations with derivative UICs (DUIC) (that is, task forces, companies, detachments,and other units/elements for which no structures exist) will submit unit status reports for a given deployment.

b. Deployment.(1) Deployed reporting.(a) All deployed AA- and FF-level reporting units are required to continue unit status reporting, unless specifically

87AR 220–1 • 15 November 2001

exempted by HQDA in accordance with paragraph 2–3. CINCs, in coordination with HQDA, will determine if orwhich ad hoc organizations with derivative UICs (DUIC) (that is, task forces, companies, detachments, and other units/elements for which no structures exist) will submit unit status reports for a given deployment.

(b) AA- and FF-level units on operational deployments will submit a deployed report. AA- and FF-level unitsdeployed on training exercises may submit a deployed report, when specifically approved by the MACOM.

(c) When operationally deployed in accordance with paragraph 11–1, or authorized to submit a deployed report,commanders of units with UICs ending in “AA” and “FF” will—

1. Assess the unit’s ability to execute the wartime mission(s) for which the unit was organized or designed in thefour measured resource areas (that is, P, S, R, and T) and determine the C-level.

2. Subjectively assess and report the unit’s effectiveness in executing the current mission(s) for which deployed byentering a PCTEF level in the PCTEF field of the deployed USR. This PCTEF level will not necessarily correlate withthe unit’s C-level.

(d) For units reporting in accordance with paragraph 11–6, submit report as directed.(2) PCTEF reporting. PCTEF will be reported in the deployed USR in accordance with paragraph 11–3. When

required to report a PCTEF, owing to a pending peacetime operational deployment in accordance with paragraph 11–3below, commanders of units with UICs ending in “AA” and “FF” will report a PCTEF in their regular or compositereports, respectively.

(3) Training level (T-level). FF-level units, with operationally deployed units/elements, will use the special traininglevel criteria in accordance with paragraph 11–4f.

c. Redeployment.(1) USR reporting. AA- and FF-level units will resume regular USR reporting in accordance with table 2–1.(2) PCTEF. The PCTEF reporting window closes for all reporting units (AC and RC) when all operationally

deployed reportable units/elements have returned from the operational deployment.(3) Training level (T-level). FF-level units will continue to submit a T-level in accordance with paragraph 11–4f.(4) Units reporting in accordance with paragraph 11–6. Units will submit a deployed report upon closure at home

station indicating that this is the final report.d. Exception reporting. If an AA-level unit cannot meet its status reporting requirements because of operational

constraints, or because of extremely exceptional circumstances (for example, catastrophe, major natural disasters, andso forth), then the MACOM may authorize the unit to report temporarily using the reporting criteria and proceduresestablished in this regulation for derivative UIC (DUIC) units in accordance with paragraph 11–6. MACOMs willnotify HQDA (ATTN: DAMO–ODR) when they exercise this authority. Notification to HQDA will include the unitidentification (by UIC), the effective period the unit has been authorized to use DUIC reporting procedures, and theexceptional circumstances warranting the temporary use of DUIC reporting procedures. MACOM authority to approvetemporary use of DUIC reporting procedures is not applicable to FF-level reporting requirements.

11–3. PCTEF reportinga. General. PCTEF will be reported by all Army SORTS reporting units that are assigned to conduct peacetime

operational deployments or that have subordinate PCTEF reportable units/elements assigned to conduct peacetimeoperational deployments. (See figs 11–3 and 11–4.)

(1) Reportable units/elements. PCTEF will be reported for deploying/deployed units/elements with command andcontrol systems as defined by Joint directive (see glossary). Essential aspects of the criteria that distinguish reportableArmy units/elements from non-reportable Army units/elements are the presence of a commander (normally a commis-sioned officer in the rank of captain or higher) and the necessary communications systems that will allow thecommander to provide regular (at least monthly) status reports or situation reports (SITREPs) routinely to the parentunit. In general, company-size and larger Army units/elements are considered by HQDA to meet these criteria. Both ofthese aspects of the criteria (an appropriate commander and the necessary communications systems for regular statusreporting) must be satisfied for the deploying/deployed unit/element to be considered reportable. All SORTS reportingArmy units (AA- and FF-levels) are considered to be PCTEF reportable units. A PCTEF may be(optional) determinedand reported for deploying/deployed Army units/elements that do not satisfy the criteria by the commander of theSORTS reporting Army unit, if desired and appropriate.

(2) Reporting units. AA-level and FF-level Army units will report a PCTEF level reflecting the ability of their“reportable” subordinate units/elements to accomplish the mission requirements of their assigned peacetime operationaldeployments. Units reporting in accordance with paragraph 11–6 also will report a PCTEF level. PCTEF reporting willbe accomplished while “reportable” unit/elements are in the “PCTEF reporting window.”

(3) PCTEF reporting window. SORTS reporting Army units will accomplish PCTEF reporting as follows—(a) AC reporting units are required to begin PCTEF reporting not later than 90 days prior to actual peacetime

operational deployment of reportable units/elements.(b) RC reporting units are required to begin PCTEF reporting not later than 30 days after the effective date that

reportable units/elements have been ordered to active duty for peacetime operational deployment.

88 AR 220–1 • 15 November 2001

(c) The PCTEF reporting window closes for all reporting units (AC and RC) when all reportable units/elements havere-deployed to home station.

(d) SORTS reporting units will begin reporting a PCTEF in their first USR required for submission in the PCTEFreporting window, unless earlier PCTEF reporting has been directed by HQDA or by the MACOM/NGB. PCTEFreporting will not be directed before the units/elements receive a formal warning order of operational missionassignment.

b. Determining and reporting a PCTEF level.(1) General. Commanders of SORTS reporting units will determine and report a PCTEF level as follows—(a) Commanders of SORTS reporting units will determine a PCTEF level that represents the ability of the reporting

unit as a whole or in part (if partially deployed) to accomplish the assigned peacetime operational deployment.(b) If the entire SORTS reporting unit is operationally deployed or pending operational deployment, then the PCTEF

level will reflect the commander’s subjective assessment of the ability of the entire unit to accomplish the peacetimeoperational deployment.

(c) If the SORTS reporting unit is partially deployed or if reportable subordinate units/elements are pendingdeployment, then the PCTEF level will reflect the commander’s subjective assessment of the ability of the reportablesubordinate unit/elements to accomplish the peacetime operational deployment.

(d) SORTS reporting units will report the PCTEF level in their deployed, regular, or composite USR in accordancewith table 2–1. While reportable units/elements are actually operationally deployed, commanders of SORTS reportingunits will submit a deployed report in accordance with paragraph 11–7. (Note that commanders of major combat units,FF-level units, continue to submit composite reports while deployed.) Commanders will use the GENTEXT remarks toexplain or clarify relevant circumstances related to the peacetime operational deployment.

(2) Additional guidelines and instructions related to PCTEF reporting.(a) AA-level reports.1. A PCTEF will be included in only one AA-level report. Parent units with peacetime operationally deployed

reportable subordinate units/elements or reportable subordinate units/elements pending operational deployment will notreport a PCTEF if these units/elements are required to submit a separate DUIC report in accordance with paragraph11–6.

2. Commanders of AA-level SORTS reporting units that have multiple reportable subordinate elements that arepending peacetime operational deployment or that are currently conducting peacetime operational deployment(s), willdetermine a PCTEF that represents the overall ability of the reportable subordinate units/elements to accomplish themission(s) for which they are deployed or pending deployment. (Do not consider those subordinate units/elements thathave been directed to submit a DUIC report in accordance with paragraph 11–6.) Explanatory GENTEXT remarks arerequired in all cases

(b) FF-level reports.1. A composite PCTEF level will be reported in FF-level (composite) reports even if all operationally deployed

units/elements are SORTS reporting units themselves (that is, AA-level units). A composite PCTEF is not required ifno AA-level units are actually operationally deployed or pending deployment. Note that DUIC reports may be retrievedfrom ASORTS by commanders of FF-level units for their composite reports.

2. If a major combat unit is supporting multiple operations or has multiple reporting units, then the commander ofthe major combat unit will determine and report a composite PCTEF in the FF-level report. In determining thiscomposite PCTEF level, the commander of the major combat unit will determine a PCTEF level for each operationaldeployment supported by evaluating the ability of the assigned subordinate reporting units to accomplish theiroperational deployment mission requirements. The commander will then consider the PCTEF determined for eachsupported peacetime operational deployment, the relative significance of each operational deployment, and the relativesize of the reportable subordinate units/elements (for example, subordinate AA-level units) supporting the operationaldeployment. Commanders will use GENTEXT remarks to list the PCTEF for each operational deployment and toclarify how the composite PCTEF level was determined.

(c) Derivative UIC (DUIC) reporting. DUIC units created for operational purposes with the requirement to submit aUSR will report a PCTEF by following reporting procedures established in this regulation for AA-level units. OtherDUIC units (for example, DUICs ending in AO, BO, CO, and so forth) will provide USR data to their parent (AA-level) unit so that the parent unit can report a PCTEF. Units/elements directed to report in accordance with paragraph11–6 will use the REASN codes in appendix E, table E–2 to indicate the unit’s deployment status.

(d) REASN codes.1. While fully or partially deployed, SORTS reporting units will use the REASN codes in appendix E, table E–2, to

indicate the deployment status of the unit and/or its subordinate elements or personnel. These REASN codes areprovided to enable commanders of SORTS reporting units to indicate the unit’s deployment status (including pendingdeployment status) and the percent of the overall unit capability that is deployed (to include individual personneldeployments). REASN codes are also provided to indicate that the peacetime operationally deployed units/elements (orpersonnel) are non-reportable and whether the reporting unit is supporting single or multiple operations.

2. When using these REASN codes, GENTEXT remarks will be used to explain the current or pending peacetime

89AR 220–1 • 15 November 2001

operational deployment, to discuss the commander’s PCTEF determination, and to clarify non-reportable or reportableunits/elements. (The remarks will be labeled in the SORTS and ASORTS database as label ID: MAE.)

(e) Supplemental instructions applicable to RC units. The responsible MACOM, USARC, NGB, or the gainingcommand (Army component command, when appropriate) will support and assist PCTEF-reportable RC units asrequired and appropriate. SORTS reporting (that is, AA-level) RC units will be provided support and assistance toprepare and transmit their USR. PCTEF-reportable RC units that are not SORTS reporting units will be providedsupport and assistance to prepare and transmit their USR data to their AA-level RC parent unit so that the parent unitcan report the PCTEF. The following guidelines also apply—

1. After a PCTEF-reportable RC unit has been alerted for peacetime operational deployment, but before the PCTEF-reportable RC unit has been mobilized/federalized, USR status reporting will continue to be accomplished in accord-ance with the provisions of chapter 2.

2. After a PCTEF-reportable RC unit has been mobilized/federalized for peacetime operational deployment, theresponsible active component MACOM (that is, FORSCOM, in most cases) will support and assist the RC unit toprepare and transmit its USR or its USR data. (Note that paragraph 9–8a establishes requirements for AA-level RCunits, after mobilization/federalization, to submit a regular report to the mobilization station within 24 hours of thearrival of the advance party at the mobilization station to establish the RC unit’s status at mobilization/federalization.)

3. When a PCTEF-reportable RC unit is deployed for peacetime operational deployment, the gaining command(Army component command, when applicable) will support and assist the RC unit to prepare and transmit its USR orits USR data. (Note that paragraph 9–8a establishes USR requirements for AC and RC units, after deployment, tosubmit a deployed report to indicate the unit’s status while deployed.)

4. When a PCTEF-reportable RC unit (for example, an AA-level company or a company with DUIC ending in AO,BO, CO, and so forth) is redeployed from a peacetime operational deployment, the responsible active componentMACOM (that is, FORSCOM, in most cases) will support and assist the RC unit to prepare and transmit its USR(applicable to AA–Level companies) or its USR data (applicable to companies with AO, BO, CO, and so forth,DUICs). (Note that paragraph 9–8a establishes that AC units and those RC units still on active duty, after redeploy-ment, will submit a regular report and/or change report in accordance with chapter 2 to indicate the unit’s statusfollowing redeployment.)

5. When a PCTEF-reportable RC unit is de-mobilized and its federal status is officially terminated, USR require-ments will revert to those established in chapter 2.

6. MACOMs/NGB may publish supplemental instructions to support the implementation of PCTEF reporting fortheir units; however, these supplemental instructions must be consistent with provisions of AR 220–1 and will becoordinated with HQDA prior to publication.

(f) PCTEF levels. Valid entries for PCTEF levels are numeric values: “1,” “2,” “3,” or “4.”1. Report “1” if the unit possesses the required resources and is trained to undertake the full mission assigned.2. Report “2” if the unit possesses the required resources and is trained to undertake most of the mission assigned.3. Report “3” if the unit possesses the required resources and is trained to undertake many, but not all, portions of

the current mission.4. Report “4” if the unit requires additional resources or training to undertake the current mission, but may be

directed to undertake portions of the current mission with resources on hand.

11–4. Deployed reporting procedures for FF-level and AA-level unitsa. The C-level and the levels for the four measured resource areas. The C-level and the levels for the four measured

resource areas will be determined in an abbreviated manner for status reporting by deployed units. Commanders ofdeployed units will report the unit’s status in the four measured resource areas (PER, EOH, ES, and training) based onthe mission for which the unit was organized or designed (that is, the unit’s wartime mission). Unit status informationwill reflect the unit’s currently approved MTOE and wartime METL. Composite reports (FF-level) will reflect pre-deployment organic units.

b. Overall category level. The C-level will be selected based on the lowest level determined for a measured resourcearea. The commander must consider the levels of all measured resource areas and the MAE percentage whendetermining whether or not to subjectively upgrade or downgrade the unit’s C-level.

c. Personnel.(1) Only assigned and/or available personnel will be reported. (See policy guidance in para 4–4 and appendix D.)(2) Assigned personnel data will reflect personnel currently assigned (that is, via permanent change of station

orders) to the parent-level unit, to include personnel assigned to the rear detachment DUIC. (See para 4–3.)(3) Available personnel includes all deployed personnel and those soldiers available for deployment who are in the

rear detachment, unless those soldiers could not join the unit to meet wartime operational requirements. Determinepersonnel availability in accordance with the provisions and criteria in paragraph 4–4 and appendix D.

d. Equipment on hand.(1) Only ERC P and A MTOE authorized items must be reported.(2) Equipment left in the rear detachment will be counted as “on-hand” if it meets the conditions specified in

90 AR 220–1 • 15 November 2001

paragraph 5–7. The key criteria are that the equipment remains under the operational control of the commander; thecommander retains visibility of that equipment; and that an established plan exists to deploy that equipment within thedeployed mission requirements.

(3) Equipment borrowed against MTOE authorizations will be counted as “on-hand,” as defined in paragraph 5–8.T h e b o r r o w i n g u n i t w i l l n o t r e p o r t e q u i p m e n t t h a t i s b o r r o w e d a g a i n s t m i s s i o n r e q u i r e m e n t s w i t h n o M T O Eauthorization.

e. Equipment serviceability.(1) Only ERC P and A equipment serviceability reporting is required. The percentage of on-hand equipment fully

mission capable (PERRY), and the percentage of pacing items on hand fully mission capable (PIEMC) will be basedon the status of equipment on the “as-of” date of the report, not a monthly average.

(2) The serviceability status of equipment left in rear detachments and reported as on hand will reflect the lastknown condition. If the commander of the deployed unit does not have the ability to maintain visibility of theserviceability status of equipment left in the rear detachment, then he will report only the deployed equipment and statein his remarks that the equipment serviceability rating is based only on deployed equipment.

f. Training.(1) Units submitting AA-level reports—(a) The unit’s training level is based on the percentage of its METL for which it is fully trained and the number of

training days required by the unit to attain full METL proficiency in accordance with paragraph 7–5. AA-level unitcommanders also are required to review their training level determinations for doctrinal credibility by comparing theirunits’ training event accomplishments with doctrinal training event requirements in accordance with paragraph 7–6.The status of squad/crew/team/system manning and qualification also is reported for information and analysis at higherlevels, if applicable in accordance with paragraph 7–4.

(b) The percentage of the METL trained and the number of training days required to reach full METL proficiencyare determined in accordance with the provisions of paragraphs 7–2 and 7–3, respectively.

(2) Major combat units submitting composite reports—(a) Policy guidelines. Commanders of major combat units will use the criteria in table 11–1 below to determine the

major combat unit’s T-level before, during, and after peacetime operational deployments in accordance with thefollowing policy guidelines—

1. Apply when the major combat unit or subordinate elements are operationally deployed during peacetime (asexplained in para 11–1), and the peacetime operational deployment(s) adversely affects the USR training level of themajor combat unit or adversely affects its ability to accomplish its wartime mission.

2. Apply no earlier than 90 days prior to the peacetime operational deployment if the training requirements for thepeacetime operational deployment(s) adversely affects the USR training level of the major combat unit or adverselyaffects its ability to accomplish its wartime mission(s).

3. Apply for no longer than 90 days following the return of units to home station(s) from peacetime operationaldeployment if (based on the criteria established in chapter 7) the major combat unit cannot report a T–1 training levelin the USR.

4. Apply as directed by the MACOM or by HQDA.(b) Supplemental instructions. The T-level criteria in table 11–1 below incorporate the Army’s 120-day disengage-

ment model and will be used in composite reports during the time period specified in separate implementinginstructions provided to the major combat unit by HQDA or by the MACOM. In the absence of separate implementinginstructions, major combat units will begin to use this T-level criteria in accordance with the above policy guidelinesno sooner than 90 days prior to the operational deployment of subordinate units/elements. Major combat units willcontinue to use this T-level criteria in accordance with the above policy guidelines for up to 90 days after the return ofunits/elements from operational deployment to avoid “instant un-readiness” and/or to accommodate the reconstitutionand/or transition of units/elements to their wartime mission requirements.

(c) REASN code. Commanders of major combat units authorized by the policy guidance in this regulation ordirected by supplemental instructions to apply the training level criteria in table 11–1 will enter REASN code “M” inthe special T-level field in the new AR 220–1 section of AR 220–1 (ASORTS). This entry indicates that the T-levelwas determined using the special training level criteria in table 11–1. GENTEXT remarks will be used to explainwartime mission impacts. The “M” REASN code and GENTEXT remarks will be used in composite reports submittedby deployed and non-deployed major combat units authorized or directed to use these special T-level criteria inaccordance with paragraphs a and b, above.

(d) Intent. The training level metrics established by table 11–1 are intended to accomplish the following training-level results. In determining the T-level to be reported in the USR, commanders of major combat units preparing for,conducting, or recovering from peacetime operational deployments will consider this intent and apply it in situationswhere the training level metrics established in table 11–1 do not fit the disengagement plan established for thepeacetime operational deployment assigned, as follows—

1. T–1. If the major combat unit can meet the T–1 training level criteria established in paragraph 7–5 for normal

91AR 220–1 • 15 November 2001

reporting (that is, the percent of METL trained is 85 percent or higher, and the major combat unit can accomplish fullMETL proficiency in 14 training days or less).

2. T–2. If the major combat unit can accomplish the unit training required to achieve full METL proficiency forwartime missions within the number of training days allotted in the disengagement plan in order to meet TPFDDtimelines.

3. T–3. If the major combat unit can accomplish most but not allunit training required to achieve full METLproficiency for wartime missions within the number of training days allotted in the disengagement plan in order tomeet TPFDD timelines.

4. T–4 . If the major combat unit cannot complete most unit training required to achieve full METL proficiency forwartime missions within the number of training days allotted in the disengagement plan in order to meet TPFDDtimelines.

Table 11–1Special USR training level criteria for major combat units

Estimated number of training days required to Additional criteria Training level to be reported in the USR1

achieve “full METL proficiency”1

1–14 days T–METL is 85 percent or higher2 T–1 2

1–14 days T–METL is less than 85 percent T–215–40 days None T–241–60 days None T–3Over 60 days None T–4

Notes:1 The actual number of estimated training days required for the major combat unit to achieve “full METL proficiency” is also reported. Also consider the intentof these special criteria as described in sub-paragraph (d) above.2 T–1 status determination also requires the commander to assess (in accordance with paragraph 7–2) that the T–METL percentage for the major combatunit is 85 percent or higher.

g. Mission accomplishment estimate (MAE). (See chapter 8.)h. Commanders remarks. The READY GENTEXT remark is the only remarks set required. Commanders are

specifically encouraged to address the impact of the deployed mission on the unit’s ability to execute its wartimemission. In addition, this remark set may be used to amplify or clarify any other aspects of the USR. This includes theimpact of environmental conditions, supply rates, key personnel shortages, and high operating and/or operations tempo(OPTEMPO). The deployed unit commander’s remarks are intended to provide a more accurate and detailed picture ofhis concerns to both the Army leadership and to resource managers.

i. Level-6. Report level-6 if the unit commander has no visibility of the status of the particular measured resourcearea.

j. Reporting requirements. Table 11–2 below outlines the reporting requirements for units assigned peacetimeoperational requirements.

Table 11–2Reporting requirements for units assigned peacetime operational deployments

Type deployment Deployment status AA–level unit FF–level unit DUIC unit (SORTS reporting)

Full Pending 2, 5, 9 3, 5, 9, 12 4, 5, 9Partial Pending 2, 6, (8 or 9) 3, 6, 9, 12 N/AFull Deployed 1, 5, 7, (10 or 11) 3, 5, 7, (10 or 11), 12 4, 5, 7, 10Partial Deployed 2, 6, (10 or 11) 3, 6, (10 or 11), 12 N/A

92 AR 220–1 • 15 November 2001

Table 11–2Reporting requirements for units assigned peacetime operational deployments—Continued

Type deployment Deployment status AA–level unit FF–level unit DUIC unit (SORTS reporting)

Full or partial Redeployed 2 3, 12 13

Notes:1 Will submit a deployed report (AA- or FF-level).2 Will submit a regular report.3 Will submit a composite report.4 Will submit a DUIC report in accordance with paragraph 11–6.5 Will report PCTEF indicating the ability of the reporting unit to execute the peacetime operational deployment assigned.6 Will report a PCTEF level indicating the ability of reportable subordinate element(s) to execute the peacetime operational deployment assigned. (A PCTEFlevel is not required in AA-level reports if the deploying/deployed elements are not reportable or in composite (FF-level) reports if no AA-level subordinateunits are either pending deployment or actually deployed.)7 Will use “JCRR1” code in TREAD field.8 In accordance with paragraph 11–3, use REASN code “A” (non-reportable units/elements pending deployment). FF-level units cannot use this code.9 In accordance with paragraph 11–3, use REASN code “B” (reportable units/elements pending deployment).10 Will use REASN codes “C,” “D,” “E,” “F,” “G,” and “H,” as appropriate, to reflect percent of capability deployed in support of a single operation (that is, oneSSC).11 Will use REASN codes “I,” “J,” “K,” “L,” “O,” and “Q,” as appropriate, to reflect percent of capability deployed in support of multiple operations (that is,multiple SSCs).12 In accordance with paragraph 11–4f, will use REASN code “M.” (AA-level units cannot use this code.)13 In accordance with paragraph 11–6g, will submit a final DUIC report.

11–5. Crisis and wartime reporting channelsFigure 2–5 illustrates the crisis and wartime submission channels for USR.

11–6. Derivative UIC reporting proceduresa. Non-deployed units temporarily using DUIC reporting procedures in accordance with paragraph 11–2d will

determine and report unit status based on their units’ ability to accomplish the missions for which the units wereorganized or designed (that is, the wartime mission) in the category level fields of READY, PRRAT, ESRAT, ERRAT,TRRAT, and MAE. Deployed/deploying DUIC units use the requirements of their deployed missions as the basis fortheir unit status assessments and do not report a MAE. Otherwise, the instructions and provisions for DUIC reportingprovided in the remainder of this paragraph are applicable to both deployed/deploying DUIC units and non-deployedunits temporarily using DUIC reporting procedures.

b. Commanders of deployed units with DUICs and DUIC units pending deployment will assess and report theirunits’ ability to accomplish the missions for which deployed or pending deployment in the category level fields ofREADY, PRRAT, ESRAT, ERRAT, and TRRAT.

(1) The C-level will be selected based on the lowest level determined for the four measured resource areas. Thelevels for the measured resource areas will be subjectively determined and will be based on the assumption that that re-supply actions, consumption and attrition rates, and the pace of operations will continue at demonstrated or plannedrates, unless concrete indicators of change are evident. Commanders of deployed units with DUICs and DUIC unitspending deployment will determine these levels after estimating the resources and training required to accomplish theoperational mission for which the unit with the DUIC was deployed or is pending deployment and then comparing thisestimate to the current status of resources and training in the unit. The category level definitions applicable to deployedDUIC reporting units and those pending deployment are as follows—

(2) DUIC level C-1 indicates that—(a) The unit possesses the required resources, is adequately trained and is in position (or has the necessary mobility)

to undertake the full mission for which it was deployed or is pending deployment.(b) The status of the unit’s personnel, equipment, consumable supplies, and training and the unit’s position do not

decrease the probability of mission success or increase the vulnerability of the unit.(c) The unit can accomplish its mission without the need for additional resources.(3) DUIC level C-2 indicates that—(a) The unit possesses the required resources, is adequately trained, and is in position (or has the necessary mobility)

to undertake most of the mission for which it was deployed or is pending deployment.(b) The status of the unit’s personnel, equipment consumable supplies, and training and the unit’s position will not

decrease the probability of mission success or significantly increase the vulnerability of the unit, although someincrease in vulnerability is acceptable relative to mission criticality. The unit may encounter isolated decreases in itsflexibility to accomplish mission-critical tasks.

(c) The unit will require little, if any, assistance to compensate for deficiencies.(4) DUIC level C-3 indicates that—

93AR 220–1 • 15 November 2001

(a) The unit possesses the required resources, is adequately trained and is in position (or has the necessary mobility)to undertake many, but not all, portions of the mission for which it was deployed or is pending deployment.

(b) The status of the unit’s personnel, equipment, consumable supplies, and training and the unit’s position willdecrease the probability of mission success or increase vulnerability of the unit. It is likely that the unit will encountersignificant decreases in its flexibility to accomplish mission-critical tasks.

(c) The unit may need significant assistance to compensate for deficiencies.(5) DUIC level C-4 indicates that—(a) The unit requires additional resources and/or training or needs mobility assistance to undertake the full mission

for which it was deployed or is pending deployment. If required by the situation, the unit may be directed to undertakeportions of its mission(s) with the resources on hand.

(b) The status of the unit’s personnel, equipment, consumable supplies, and training and the unit’s positiondecreases the probability of mission success and increases the vulnerability of the unit. Mission success is possible forcertain isolated scenarios.

(c) The unit cannot compensate for deficiencies, even with significant assistance.(6) DUIC level 6 indicates that the unit commander has no visibility of the status of a particular measured resource

area and, therefore, no ability to subjectively determine its level.c. The measured resource area levels for units with DUlCs will be determined by comparing the resource and

training requirements of the mission for which the unit is deployed or pending deployment to the current status ofresource and training in the DUIC unit as follows—

(1) Personnel. The unit commander will determine the unit’s personnel level (P-level) based on his/her subjectiveassessments regarding the quantity of available personnel and the mix of leaders and skills needed to execute theassigned mission. Using the assumptions and DUIC C-level descriptions provided in sub-paragraph b, the unitcommander will select the personnel level (that is, P-1, P-2, P-3, P-4, or P-6) that corresponds to the DUIC C-leveldescription that most accurately depicts the sufficiency of the number of available personnel in the unit to accomplishmission-critical tasks (for example, P-1 corresponds to the DUIC level C-1 description; P-2 corresponds to the DUIClevel C-2 description; P-3 corresponds to the DUIC level C-3 description; and so forth).

(2) Equipment on hand. The unit commander will determine the unit’s EOH level (S-level) based on his/hersubjective assessments regarding the adequacy of the unit’s on-hand equipment to execute the assigned mission (that is,the quantity and type of equipment, support items, classes of supply, and so forth, that are available to the unit). Usingthe assumptions and DUIC C-level descriptions provided in sub-paragraph b, the unit commander will select the EOHlevel (that is, S-1, S-2, S-3, S-4, or S-6) that corresponds to the DUIC C-level description that most accurately depictsthe status of the unit’s on-hand equipment relative to the equipment needed to accomplish mission-critical tasks. (Forexample, S-1 corresponds to the DUIC level C-1 description; S-2 corresponds to the DUIC level C-2 description; S-3corresponds to the DUIC level C-3 description; and so forth.)

(3) Equipment serviceability. The unit commander will determine the unit’s ES level (R-level) based on the his/hersubjective assessments regarding the adequacy of the unit’s operational equipment and the equipment sustainabilityneeded to execute the assigned mission (that is, the availability in the unit of required operational equipment, supportitems, repair parts, facilities, and so forth). Using the assumptions and DUIC C-level descriptions provided in sub-paragraph b, the unit commander will select the ES level (that is, R-1, R-2, R-3, R-4, or R-6) that corresponds to theDUIC C-level description that most accurately depicts the serviceability status and sustainability of the unit’s on-handequipment relative to the operational equipment and sustainability needed to accomplish mission-critical tasks. (Forexample, R-1 corresponds to the DUIC level C-1 description; R-2 corresponds to the DUIC level C-2 description; R-3corresponds to the DUIC level C-3 description; and so forth.)

(4) Training. The unit commander will determine the unit’s training level (T-level) based on his/her subjectiveassessments regarding the ability of unit personnel to collectively execute the assigned mission. Unique environmentalconditions also will be considered. Using the assumptions and DUIC C-level descriptions provided in sub-paragraph b,the unit commander will select the T-level (that is, T-1, T-2, T-3, T-4, or T-6) that corresponds to the DUIC C-leveldescription that most accurately depicts the training status the unit’s personnel relative to the training proficiencyneeded to accomplish mission-critical tasks (for example, T-1 corresponds to the DUIC Level C-1 description; T-2corresponds to the DUIC Level C-2 description; T-3 corresponds to the DUIC Level C-3 description; and so forth).

(5) Overall DUIC C-level. The overall DUIC C-level will be based on the lowest level determined for the fourmeasured resource areas (P, S, R, and T) that reflect the status of resources and training in the unit. Subjectiveupgrades of the C-level are not applicable, since the level for each of the four measured resource areas was subjectivelydetermined.

d. The READY GENTEXT remark set is required for this report. READY GENTEXT remarks must be concise andshould stand alone. Remarks in the READY set are mandatory for each resource area that is less than level-1. Thecommander will identify the resource area and specify the critical resources and training that the unit needs to meetmission requirements.

e. REASN codes and REMARKS associated with PCTEF reporting requirements are discussed in paragraph 11–3(above) and are provided and explained in appendix E, table E–2.

94 AR 220–1 • 15 November 2001

f. DUIC units are not required to report a MAE percentage.g. When directed, units will accomplish DUIC reporting as follows—(1) AC reporting units are required to begin DUIC reporting no later than 90 days prior to actual peacetime

operational deployment of reportable units/elements.(2) RC reporting units are required to begin DUIC reporting no later than 30 days after the effective date that

reportable units/elements have been ordered to active duty for peacetime operational deployment.(3) The DUIC reporting window closes for all reporting units (AC and RC) when all reportable units/elements have

returned from the peacetime operational deployment.(4) Upon redeployment, units will submit a DUIC report indicating that this is the final report.

11–7. Instructions for completing the deployed USRa. TREAD. Enter JCRR1. (See fig 11–1.)

95AR 220–1 • 15 November 2001

Figure 11–1. Deployed report worksheet, part I

96 AR 220–1 • 15 November 2001

b. READY. The entry in the READY field on the DEPLOYED USR is a commander’s subjective judgment of theunit’s ability to accomplish the wartime mission.

c. REASN (primary reason overall level not 1) . An entry in this field is required to reflect the lowest rated resourcearea level (P, S, R, or T) if overall (READY) is other than 1.

d. Personnel data sets.(1) PRRAT. (P-level). Enter 1, 2, 3, 4, or 6.(2) PRRES (reason P-level not 1). If PRRAT field does not contain a “1,” enter the personnel code from appendix E

that shows the main reason the P-level is not 1; otherwise, leave blank.(3) AVPER, PERDATA set (available strength percentage). Use the percentage calculated in paragraph 4–7, step 5.e. Equipment-on-hand data sets.(1) ESRAT (S-level). Calculate in accordance with paragraph 5–10, step 7. Enter 1, 2, 3, 4, or 6.(2) ESRES (reason S-level not 1). If ESRAT field does not contain a “1,” enter the equipment-on-hand code from

appendix E that indicates the primary reason the S-level is not 1; otherwise, leave blank.(3) PIRAT, EQOHDATA set (lowest pacing item S-level). Calculate in accordance with paragraph 5–10, step 6. If a

unit has no pacing items, leave blank.(4) EHRDN, EQOHDATA set (total number of ERC A&P LINs). Calculate in accordance with paragraph 5–10, step

4.f. Equipment serviceability data sets.(1) ERRAT (R-level). Enter 1, 2, 3, 4, or 6.(2) ERRES (reason R-level is not 1). If ERRAT field does not contain a “1,” enter the equipment readiness code

from appendix E that shows the main reason the R-level is not 1; otherwise, leave blank.(3) PERRY, EQMCRDAT set (percentage of on-hand equipment fully mission capable). Enter the aggregate FMC

percentage computed for on-hand reportable equipment based on the status of equipment on the “as-of” date of thereport, not a monthly average.

(4) PIEMC, EQMCRDAT set (percentage pacing item on-hand fully missio -capable). Enter the computed percent-age of the lowest pacing item based on the status of equipment on the “as-of” date of the report, not a monthlyaverage. If the unit has no pacing items, leave blank.

g. Training data sets.(1) TRRAT (T-level). Enter 1, 2, 3, 4, or 6.(2) TRRES (reason T-level not 1). If TRRAT field does not contain a “1,” enter the training code from appendix E

that shows the main reason the T-level is not 1; otherwise, leave blank.(3) TMETL, TRAINDAT set (percentage METL trained). Enter the percentage of METL trained, determined by the

commander in accordance with the instructions in paragraph 7–2.(4) TWRC1, TRAINDAT set (number of days required to train). Enter the number of days required to train to full

METL proficiency, determined by the commander in accordance with the instructions in paragraph 7–3.h. GRID (location). Enter the unit’s location using the 111-position universal transverse mercator (UTM). When

using the UTM, ensure the grid zone designation (3 digits), the 100,000-meter grid square designation (2 digits), andthe grid coordinates to the nearest 100 meters (6 digits) are entered.

i. MAE, READYSEG set (mission accomplishment estimate). Commanders will subjectively assess the unit’s abilityto execute the wartime mission. DUICs leave this field blank.

j. PCTEF (percent effective). Commanders will subjectively assess their unit’s ability to execute the currentpeacetime operational deployment and will enter a PCTEF level in accordance with paragraph 11–3.

k. READY GENTEXT remark set. Use this set (fig 11–2) to make comments regarding the unit’s ability toaccomplish the mission for which it was organized and designed—the wartime mission—and the mission for which ithas been deployed. DUIC units will comment only on the mission for which the DUIC unit has been deployed.Comments may address any of the field labels on the report or any other unit status factors the commander feels areappropriate. Ready remarks should be clear, concise, and pertinent.

97AR 220–1 • 15 November 2001

Figure 11–2. Deployed report worksheet, part II

98 AR 220–1 • 15 November 2001

l. Classification. Enter the same classification as the classification of the operation for which the unit is deployed orthe classification in accordance with paragraph 2–7, whichever is higher.

m. TRANS type field. Enter “A.”n. DEPTEMPO. (See para 7–11.)o. Notes.(1) The availability of personnel in units/elements conducting peacetime operational deployments is determined in

accordance with provisions in AR 220–1 that incorporate guidance in the Army disengagement plan.(2) The C-level of all units conducting peacetime operational deployments is based on the lowest level determined

for a measured resource area (that is, P, S, R, and T).(3) Table 11–3, below, outlines USR support/oversight responsibilities for PCTEF-reportable RC units assigned to

conduct peacetime operational deployments. (Also see para 11–3e.)

Table 11–3USR support/oversight responsibilities for PCTEF-reportable RC units

Circumstances and status of the PCTEF–report- Responsibility for prescribing the USR reporting Additional actions requiredable RC unit channels and for providing USR support/over-

sight

Unit has been alerted for peacetime opera-tional deployment, but it has not been mo-bilized/federalized.

No change to current responsibilities orprocedures in chapter 2, AR 220–1. (Seepara 2–5 and figs 2–1 and 2–2.)

None

Unit has been mobilized/federalized forpeacetime operational deployment, but ithas not been deployed.

Responsible AC MACOM(generallyFORSCOM) will assist and support thepreparation and transmission of the USR orUSR data.

Responsible AC MACOM will provide an infor-mation copy of any additional implementing in-structions to HQDA.

Unit is deployed for peacetime operationaldeployment

Gaining command (Army component com-mand, when applicable) will assist and sup-port the preparation and transmission ofthe USR or USR data.

Gaining command (Army component com-mand, when applicable) will provide an infor-mation copy of any additional implementing in-structions to HQDA.

Unit has redeployed from peacetime oper-ational deployment but has not demobilizedor terminated its federal status.

Responsible AC MACOM(generallyFORSCOM) will assist and support thepreparation and transmission of the USR orUSR data.

Responsible AC MACOM will provide an infor-mation copy of any additional implementing in-structions to HQDA.

Unit has demobilized and terminated itsfederal status

Responsibilities in AR 220–1, chapter 2,apply. (See para 2–5 and figs 2–1 and2–2.)

None.

(4) Figures 11–3 and 11–4 are provided to assist commanders of deployed/deploying units to properly implementPCTEF reporting requirements.

99AR 220–1 • 15 November 2001

Figure 11–3. PCTEF reporting decision tree for Army units

100 AR 220–1 • 15 November 2001

Figure 11–4. PCTEF reporting decision matrix for Army units

Chapter 12Multi-Component Unit Reporting

12–1. Generala. A multi-component unit is a unit that, on a single document, is authorized personnel from more than one

component or is structured with elements from more than one component. An “N” in the second character of a UICdenotes that the unit is multi-component. The fourth character of the derivative UIC denotes the component as follows:“X” for AC, “G” for ARNGUS, and “R” for USAR.

b. Currently, multi-component units include MTOE units under either AC command and control or under RCcommand and control.

c. Each component-specific element of a multi-component unit is assigned a derivative UIC. The parent unit and itsderivatives appear on the same MTOE document.

d. Multi-component units can be AA-level units (that is, battalions and separate companies with subordinate AC andRC units and elements) and units and elements below the AA-level (that is, company and detachment size elementswith AC and RC sub-elements or personnel). Multi-component organizations may contain subordinate units and

101AR 220–1 • 15 November 2001

elements that are multi-component themselves (for example, multi-component companies in multi-component battal-ions) as well as subordinate units and elements that are not (for example, ARNGUS dual-missioned elements that areassigned to multi-component battalions). FF-level organizations are composed of a number of AA-level units, eachorganized under its own MTOE/TDA; therefore, by definition, FF-level units are not multi-component units. However,FF-level units (for example, a division) can have subordinate multi-component units/elements (to include a multi-component division HHC).

e. Multi-component units were formed to enhance Total Force integration, improve the readiness/resource posture ofArmy units, optimize the unique capabilities of each component, and create mission-capable units.

f. Commanders of multi-component units determine training priorities, establish the unit’s METL, and develop thetraining plan. Assigned personnel and subordinate elements train and prepare to deploy as a unit to accomplish thewartime mission.

12–2. Concept for multi-component unit status reportinga. Each component-specific element (Active, ARNGUS, and USAR) will provide USR feeder data to the flag-

holding commander (AA-level UIC). The multi-component unit commander (flag holder) will submit a consolidatedUSR that shows the status of the entire unit. Unit status reporting will remain in compliance with unit status reportingpolicy and procedures contained in this regulation for other types of Army reporting units. USAR and ARNGUS feederdata will consist of quarterly regular reports, monthly validation reports, and periodic change reports, as required byunit status changes. ARNGUS elements will submit reports to the Adjutant General, with copies to the multi-component commanders, and to the NGB as directed by NGB–ARR. USAR elements will submit reports to HQ,USARC via Global Command and Control System (GCCS). Specific USR procedures for multi-component units willbe addressed in a coordinated memorandum of agreement or policy letter.

b. Unit status data for all personnel, elements, and units documented on the reporting unit’s MTOE (applicable toAA-level multi-component units), regardless of component, will be considered and included in the USR.

c. Unit status data for any subordinate units and elements that are not listed on the multi-component unit’s MTOEdocument (for example, ARNGUS dual-missioned elements) will be reviewed by the multi-component unit command-er, but they will not be included in any USR calculations or unit status determinations. Reporting multi-component unitcommanders may address resource or training status issues for such subordinate elements or units in their GENTEXTremarks.

12–3. Reporting procedures for multi-component AA-level unitsa. Commanders of multi-component reporting units (AA-level) will submit a single consolidated unit status report

for the entire unit (as documented on the MTOE) through the responsible higher headquarters, as required by chapter 2,table 2–1.

b. Commanders of multi-component units (AA-level) that have subordinate units or elements not listed on the multi-component unit’s MTOE will not include unit status data from these subordinate units in the USR for the multi-component unit. Commanders of these subordinate units/elements will submit their unit status data (USR or USRfeeder data) to their respective component command (that is, AC, ARNGUS, or USAR) In accordance with thereporting requirements in this regulation that are applicable to their component, and they will provide a copy of theirunit status data to the commander of the multi-component unit for information.

12–4. Special instructions, if any, for completing multi-component units status reportsa. Personnel status level determination. (See chap 4.)b. Equipment-on-hand status level determination. (See chap 5.)c. Equipment serviceability status level determination. (See chap 6.)d. Training status level determination. (See chap 7.)e. Overall category level determination. (See chap 3 and chap 9.)f. Reporting the percent effective and reporting while deployed. (See chap 11.)

102 AR 220–1 • 15 November 2001

Appendix AReferences

Section IRequired Publications

AR 40–68Quality Assurance Administration (Cited in para 4–5c)

AR 71–32Force Development and Documentation—Coordinated Policies (Cited in paras 2–10, 5–4b, 5–13a, and appendix B–1)

AR 135–91Service Obligations, Methods of Fulfillment, Participation Requirements, and Enforcement Procedures (Cited in tableD–1)

AR 310–50Authorized Abbreviations, Brevity Codes, and Acronyms (Cited in para 9–4b)

AR 380–5Department of the Army Information Security Program (Cited in para 2–8a)

AR 601–142Army Medical Department Professional Filler System (Cited in para 4–5c)

AR 700–138Army Logistics Readiness and Sustainability (Cited in paras 2–3c, 5–3b, 5–10, 6–2, 6–4b, and 6–5b)

DA Pam 350–38Standards in Weapons Training (Cited in para 7–2b and table 7–3)

DA Pam 350–39Standards in Weapons Training (Special Operations Forces) (Cited in para 7–2 and table 7–3)

FM 25–100Training the Force (Cited in paras 7–2 and 7–3) (Available at http://www.adtdl.army.mil/atdls.htm)

FM 25–101Battle Focused Training (Cited in paras 7–1c, 7–2, 7–3b, and 7–6.) (Available at http://www.adtdl.army.mil/atdls.htm)

Section IIRelated PublicationsA related reference is a source of additional information. The user does not have to read it to understand thispublication.

AR 11–2Management Control

AR 71–32Force Development and Documentation—Consolidated Policies

AR 140–10Army Reserve: Assignments, Attachments, Details, and Transfers

AR 350–1Army Training

AR 350–41Training in Units

103AR 220–1 • 15 November 2001

AR 380–19Information Systems Security

AR 570–4Manpower Management

AR 600–8–101Personnel Processing (In and Out and Mobilization Processing)

AR 600–20Army Command Policy

AR 600–43Conscientious Objection

AR 600–60Physical Performance Evaluation System

AR 600–100Army Leadership

AR 600–110Identification, Surveillance, and Administration of Personnel Infected with Human Immuno-deficiency Virus (HIV)

AR 601–210Regular Army and Army Reserve Enlistment Program

AR 611–6Army Linguist Management

AR 614–30Overseas Service

AR 614–200Enlisted Assignments and Utilization Management

AR 635–200Enlisted Personnel

AR 710–1Centralized Inventory Management of the Army Supply System

AR 710–2Inventory Management Supply Policy Below the Wholesale Level

AR 735–5Policies and Procedures for Property Accountability

AR 750–1Army Material Maintenance Policy and Retail Maintenance Operations

CJCSM 3150.02Global Status of Resources and Training System (GSORTS) (Available at http://www.dtic.mil/doctrine/cjcsmdirectives.htm

CJCSI 3401.02Global Status of Resources and Training System (Available at http://www.dtic.mil/doctrine/cjcsidirectives.htm

DA Pam 600–3Commissioned Officer Development and Career Management

104 AR 220–1 • 15 November 2001

DA Pam 710–2–1Using Unit Supply System (Manual Procedures)

FM 3.09.70Tactics, Techniques, and Procedures for M109A6 Howitzer (Paladin) Operations (Available at http://www.adtdl.army.mil/atdls.htm)

FM 6–50Tactics, Techniques, and Procedures for the Field Artillery Cannon Battery (Available at http://www.adtdl.army.mil/atdls.htm)

FM 6–60Tactics, Techniques, and Procedures for the Multiple Launch Rocket System (MLRS) Operations (Available at http://www.adtdl.army.mil/atdls.htm)

SB 8–75–S7Army Medical Supply Bulletin 20 July 2001 (Available at http://www.armymedicine.army.mil/usamma)

SB 700–20Army Adopted/Other Items Selected for Authorization/List of Reportable Items (Available at http://www.usapa.mil)

TC 1–210Air–Crew Training Program Commander’s Guide to Individual and Crew Standardization (Available at http://www.adtdl.army.mil/atdls.htm)

Section IIIPrescribed Forms

DA Form 2715Unit Status Report (Prescribed throughout)

Section IVReferenced Forms

DA Form 1352Army Aircraft Inventory, Status, and Flying Time

DA Form 2028Recommended Changes to Publications and Blank Forms

DA Form 2406Materiel Condition Status Report (MCSR)

DA Form 3266–1Army Missile Materiel Readiness Report

DD Form 314Preventive Maintenance Schedule and Record

Appendix BEquipment Readiness Codes

B–1. Generala. AR 71–32 establishes that only minimum mission-essential personnel and equipment will be included in TOE.

Codes are uniquely related to the unit mission and, more specifically, to the unit’s war-fighting capabilities specified indoctrine and TOE section I. Codes are used to distinguish equipment/systems directly related to primary mission tasks/functions and equipment needed to accomplish other unit tasks and functions that directly support primary missiontasks and functions. (For example, ammunition and fuel trucks that support the primary weapon/mission system andtechnology automation equipment in CSS units.)

105AR 220–1 • 15 November 2001

b. Tasks and functions that are less directly (or indirectly) related to the primary mission tasks also require codingdistinction. These may be tasks that are required to provide sustainment support for the organization at large. They areoften related to logistic or administrative functions (such as feeding, distribution of general supplies, maintenance, andsecondary means of communication) that may be essential but do not directly affect accomplishment of critical combattasks. Codes also distinguish between the relative essentiality of certain categories of equipment based on types ofmissions (combat, combat support, and combat service support) and risk related to time/distance factors.

c. Every equipment line item number (LIN) in a TOE/MTOE is annotated with an equipment readiness code (ERC).The annotation is a single alphabetic code in the ERC column of the TOE/MTOE (para B–2).

B–2. ERC definitionsa. ERC A or ERC P. Principal weapon/mission systems and equipment (including technology automation equip-

ment) that are critical to the accomplishment of primary doctrinal mission tasks and critical mission support items.Critical mission-support items are selected items of equipment required to refuel, rearm, power, move, recover, providemedical support, or provide direct command and control. ERC P equipment are ERC A items/systems that are alsodesignated as pacing items (appendix C).

b. ERC B. Auxiliary equipment (AE) that is essential to support ERC A or P equipment and provides mission-sustainment support. This category of equipment includes items/systems required to transport, maintain, supply,service, protect, enhance, or back up ERC A/P items.

c. ERC C. Auxiliary support equipment (ASE) is essential to unit sustainment and required to perform administra-tive or other support tasks that have little or no immediacy to sustainment of OPTEMPO.

d. Exceptions. These exceptions to the above criteria include individual and crew-served weapons, communicationequipment, critical technology automation equipment, and selected maintenance support equipment. Exceptions in thoseareas are specified in paragraph B–3. The exceptions recognize the unique risks involved in combat operationsconducted by maneuver forces and their greater need owing to the often continuous movement on the battlefield andimmediacy of need.

B–3. Coding guidelinesa. If a LIN is identified as ERC A or ERC P, all sub-components listed by separate LINs will be considered ERC A

(for example, a radio for an ERC P combat vehicle). However, items will not be counted as pacing items unless theyare specifically designated with a “P.”

b. Depending on the mission and nature of the unit, wheeled and tracked vehicles and their subsystems may becoded ERC B (AE). For example, a 1–1/4-ton truck with radios may be coded as ERC B in the headquarters andheadquarters company (HHC) of a mechanized battalion. (In a mechanized unit, tracked vehicles are normally theprincipal items used for command and control of tactical operations.) In a non-mechanized battalion, the same vehiclewould probably be coded ERC A.

c. In TOE/MTOE units an item’s readiness code assignment is based on how essential that item is to the primarymission of the unit. Similar items in a unit can have a different degree of essentiality. For example, within a TOE/MTOE, it may be appropriate to designate the commander’s radio as ERC A and the adjutant’s as ERC B.

B–4. Designating ERCsa. USAFMSA will use the guidelines in paragraphs B–1 through B–3 and table B–1 to assign readiness codes to

TOE equipment items.b. USAFMSA will code MTOE using codes in TOE. Use of an ERC on an MTOE that is different from that on the

TOE is not authorized without approval from HQDA (DAMO–FMF).c. Table B–1 provides equipment readiness code examples. This is not an all-encompassing list, but it does reflect

the need to discriminate by mission-essential equipment.d. ERC A items that are also pacing items will be identified by a “P” on TOE/MTOE.

B–5. Recommending changesSubmit recommended ERC changes for specific unit LINs, with justification, through channels to Commander,TRADOC, ATTN: ATCD–F, 415 Sherman Avenue, Fort Leavenworth, KS 66027–2300.

106 AR 220–1 • 15 November 2001

Table B–1ERC Codes

Equipment Type unit ERC

Communications equipmentFM, HF and single channel TACSAT voicecommand and control radios. Tactical oper-ations and intelligence nets for—

Maneuver brigades A

Combat divisions and corps AOther type major command A

HQ that direct tactical operations ACombat arms units (IN, AR, FA, SOF, EN,AD, AVN)MP units A

Specific radios of supporting commanders(required by doctrine in a command net)

Division support commander (DISCOM) A

Forward support battalion (FSB) com-mander

A

FM, HF, and single channel TACSAT ad-ministrative log net radios

Unit commanders A

S2/S3 officers ASupport operations sections (such as am-munitions, water, EOD, and fuel that re-spond to operation control cells (S2/S3))

A

CSS commanders ACOMMZ AMedical units used in medical operations incorps, divisions, and/or separate brigades

A

Casualty evacuation and critical medicalsupply operations

A

All other units BMobile subscriber equipment, Ancillaryequipment (that is, MSRT, phone)

All units B

MSE mission equipment Signal units corps and below PAll other units A

MSE mission equipment Signal units EAC AMulti-channel radio equipment Signal units A

All other units BCOMSEC equipment Matches ERC of supported equipment, but

no higher than ERC A. If COMSEC item isnot associated with another LIN, but is astand-alone (not TMDE), it will be ERC B

A

Selected TMDE for DS maintenance equip-ment

All units A

Radar All units whose primary mission is surveil-lance or air defense

A

All other units BAccessory equipment for radios and COM-SEC equipment

Match radio supported

ACounter-measure devices intended toprotect systems from enemy action

Match system supported

Position locating devices Combat arms ASpecial operations forces AAll other units B

Global positioning systems (GPS)Vehicle GPS (for example, PLUGGER,DAGR)

All units, all ERC P or A vehicles A

All units, all ERC B vehicles B

WeaponsMajor weapon systems, reconnaissance,and weapon platforms (unless specified aspacing items in appendix C)

All units A

Individual weapons Combat arms (IN, AR, FA, and so forth) AMP units ASpecial operations forces AAll units less EAD medical units AEAD medical units B

Crew-served weapons All units ABayonets Infantry units A

Special forces units AAll other units B

107AR 220–1 • 15 November 2001

Table B–1ERC Codes—Continued


All weapons, including individual weapons,crew-served weapons, and bayonets

Surveillance and target acquisition troop ofthe reconnaissance, surveillance, and tar-get acquisition squadron

A

VehiclesSimilar vehicles in a unit may require variable coding (for example, the commander’s vehicle may be coded ERC A and chaplain’s vehi-cle ERC B, even though they are both the same type vehicle.)Reconnaissance vehicles Combat arms units A or PPrincipal mission vehicles (See appendix Cfor ERC P criteria.)

All units A or P

Command and control vehicles All units ACombat tracked vehicles, combat wheeledvehicles

All units A

Tracked recovery vehicles Maintenance units ACombat arms units AAll other units B

Vehicles used primarily for transport ofPOL or ammunition (such as fuel tank trail-ers and cargo trailer)

All units A

Vehicles used to power ERC A radios All units AOther vehicles Code in accordance with mission require-

mentsAmbulances Medical units A or P

Non-medical units B

GeneratorsUnits in which they are the sole powersource for an ERC A/P item

A

All other units B

Night vision devicesUnits whose primary mission requires night surveillance:

Infantry AArmor AAviation units (units involved in aerial flightincluding air ambulance units

A

Military police ASpecial operations forces AMI ground surveillance ARadar units ACSS elements that routinely collocate/sup-port combat units

A

Combat engineers AField artillery bde/regt fire support sections,bn/sqd fire support sections, FIST, COLT,and STRIKER sections

A

All other units B

Unit maintenance equipmentAll units B

Camouflage netsAll units B

NBC defense equipmentIndividual protective mask All units ADecontamination apparatus Medical and chemical units whose primary

mission is decontamination, unless speci-fied as pacing items

A or P

All other units BAlarms/Detectors NBC/reconnaissance elements B

MP div., corps, and EAC units AAll other units B

Monitors NBC/reconnaissance elements ADecontamination units AMedical units AMP div., corps, and EAC units AAll other units B

Radiac meters NBC units AAll other units B

Dosimeters and chargers All units BCollective protection Medical units A

All other units B

108 AR 220–1 • 15 November 2001



Smoke generators Units whose primary mission is smoke gen-eration

A or P

All other units B

Technology automation equipmentDigital computer technology and supportequipment critical to mission accomplish-ment

All units less exceptions/clarifications below A

CSSCS All units AGCSS–Army MNT module All CSS units where supply, maintenance,

transportation, and/or distribution manage-ment is the primary doctrinal mission

A

GCSS–Army SSA module All CSS units where supply, maintenance,transportation, and/or distribution manage-ment is the primary doctrinal mission

A

GCSS–Army ammo All CSS units where supply, maintenance,transportation and/or distribution manage-ment is the primary doctrinal mission

A

GCSS–Army MGT module All CSS units where supply, maintenance,transportation, and/or distribution manage-ment is the primary doctrinal mission

A

GCSS–Army SPR module (ULLS–S4) All units (except CSSAMO) BGCSS–Army MNT module (ULLS–G) All units except CSSAMO) BGCSS–Army MNT module (ULLS–Avn) All units (except CSSAMO) AGCSS–Army SSA module MMC in logistic commands: COSCOM,

DISCOM, TSC,. HHC, area and corps sup-port group.

P

GCSS–Army ammo module MMC in logistic commands: COSCOM,DISCOM, TSC. HHC, area and corps sup-port group.

P

GCSS–Army IMM module MMC in logistic commands: COSCOM,DISCOM, TSC. HHC, area and corps sup-port group

P

GCSS–Army SPR module (SPBS–R) MMC in logistic commands: COSCOM,DISCOM, TSC, HHC, area and corps sup-port group

P

GCSS–A SPR module (SPBS–R) All other units BCTASC–II MMC in logistic commands: COSCOM,

DISCOM, TSC. HHC support group andAG co.

P

All tech auto In support of CSS STAMIS in CSSAMO inall units

A

MC4/TMIP Medical units ADTSS

TOPO engineer units PAll other units A

Petroleum handling equipmentPetroleum laboratories Petroleum lab units A

All other units BCollapsible POL storage bags, 10,000 gal.and larger

Quartermaster and transportation units A

All other units B

Carpenter, pioneer, and demolition setsDemolition sets Combat engineer, SOF, and ORD (Msl/

Mun) unitsA

All others BCarpenters sets In sections or organizations performing

construction missions requiring carpentryA

All others BPioneer sets Combat engineer and bridge companies A

All others B

Band instrumentsAll units Various codes

Field feeding equipmentMKT IDIV/IBCT AKCLFF–E IDIV/IBCT ASanitation center IDIV/IBCT ARefrigeration container IDIV/IBCT ACK IDIVI/IBCT A

109AR 220–1 • 15 November 2001



All other units BAll other mess equipment All units

Test, measurement, and diagnostic equipment (TMDE)Mission-critical TMDE (10 items or 10 per-cent of TMDE, whichever is greater)

Other maintenance organizations A

All other TMDE All units B

DS maintenance equipment in support of DS maintenanceAll units AOther maintenance organizations A

Appendix CPacing Items of Equipment

C–1. Generala. The majority of units have two pacing items. If more than four pacing items are on a unit’s MTOE/TDA,

USAFMSA will coordinate with the MACOM to reduce the number to four. The following criteria normally limit thenumber of pacing items in a unit to between one and four. Major equipment items will be designated as pacing items ifthey are—

(1) Key to a unit’s capabilities, as delineated in its requirement and authorization documents.(2) Central to a unit’s ability to perform its doctrinal mission (for example, a tank in a tank battalion).b. Pacing items receive special emphasis when determining equipment S- and R-levels, because of their major

importance to the unit. These items are subject to continuous monitoring and management at all levels of command.c. When two or more different items have a common characteristic that is the basis for pacing item determination,

all of these items will be coded ERC P. The similar items should be aggregated under a single reporting code for statusreporting in recognition of their interchangeability with respect to the critical capability: Note that the items must stillbe reported separately in material condition status reports. Also note that two or more items may be essentially thesame but identified by different LINs because they have different auxiliary equipment. For example, bulldozers areassigned different LINs because they have different attachments (such as, winch, angle blade, ripper); if the earth-moving capability is the essential characteristic for mission performance, all bulldozers in the unit will be codedERC–P.

d. If several similar LINs are listed in appendix H, SB 700–20 as substitutes for each other, they should be groupedunder one LIN for fully mission capable (FMC) computations. For example, if unit A has 2 trucks of type LIN X, 3trucks of type LIN Y, and 4 trucks of type LIN Z, and LINs X, Y, and Z are substitutes for each other in accordancewith SB 700–20, then, for USR purposes, unit A should compute FMC for these trucks based on the total quantity ofthe group (that is, 2 + 3 + 4=9 ).

e. When dissimilar units are grouped in a single battalion to enhance command and control, pacing items will bedesignated as if the subordinate elements were separate companies. (For example, in the main support battalion of aDISCOM, the number of designated pacing items will be kept to the lowest possible number consistent with the aboveguidance.)

f. Not all organizations will have equipment designated as pacing items. Many units (such as light infantry riflecompanies and personnel services companies) are principally organized around personnel resources—not key items ofequipment. For those organizations that have low-density, high-cost ERC A equipment, it may not be appropriate todesignate those items as pacing items.

C–2. Unit pacing itemsa. Units will report pacing items as identified on the unit MTOE/TDA.b. USAFMSA will code MTOE using ERC codes in TOE. Use of a pacing item on an MTOE that is different from

that on a TOE is not authorized without approval of HQDA (DCSOPS).c. Regardless of whether or not a unit has designated pacing items, all units can identify equipment problems by

calculating equipment C levels, using the remarks section of the report, and subjectively upgrading /downgrading theoverall C level as appropriate.

C–3. Exceptions to paragraph C–2a. If a unit is short an equipment item designated as a pacing item, but it has an authorized substitute (SB 700–20)

110 AR 220–1 • 15 November 2001

or an “in-lieu of” item (appendix F), that substitute item will be counted as a pacing item in place of the item the unitis short.

b. A unit that receives a modernization item as a replacement for a current pacing item will consider the new item tobe the pacing item, even if it has not yet been coded with a “P” in the ERC column. (For example, UH–60 helicoptersmay replace UH–1 helicopters, or M1A2 tanks may replace M1 tanks.) During transition, both old and new items maybe counted. If enough new items have not been received to meet the total authorization, then old items must be on handin the unit and be in use. (They cannot be turned in to a direct support maintenance unit or otherwise placed out of theunit commander’s control.)

c. TDA units will not report pacing items until such time as they are designated on their TDA or in consonance withparagraph 5–3.

C–4. Use of pacing items for preparing reportsPacing items are limiting factors in determining S and R-levels. For battalion-size and smaller units, these levels willbe no higher than the lowest pacing item level in EOH or ES respectively. Equipment percentages and/or levels forpacing items will be computed the same as for other reportable LINs. See table C–1 for pacing items of equipment bytype units.

Table C–1Pacing items by unit type

Type Unit Equipment

ArmorTank company/battalion TanksCavalry troop/squadron Aircraft

TanksHowitzersCFVAPC

InfantryInfantry battalion Dragon

TOWIFVITVCFVAPC

Air defenseAir defense artillery battalion Avenger

Patriot launcherPatriot radar setPatriot engagement control centerTHAAD launcherTHAAD radar setTHAAD engagement control centerBSFVLinebackerAN/TSQ–73Linebacker

Field artilleryField artillery battalion/battery Howitzers

MLRSTarget acquisition radar105–MM howitzer105–MM

AviationAviation battalion/company (includes medical aviation units) Mission-essential aircraft

Quick-fix systems

ChemicalChemical company Smoke generator

Decontamination apparatusNBC reconnaissance systems

EngineerEngineer battalion/company. These items are pacing items in allengineer battalions/companies. Below are specific types of battal-ions/companies that may have other specific items that are alsopacing items.

Bulldozers

111AR 220–1 • 15 November 2001

Table C–1Pacing items by unit type—Continued

Type Unit Equipment

TransportersGrizzlyAVLB/WolverineAPC/BradleyExcavatorsScrapersDump trucksGradersCranes

CSC Asphalt plantCrusher

Prime power battalion generating units substations,power line maintenance truck

TOPO battalion High volume map printerBridge company Bridges

BoatsPipeline construction company Pipeline haulersDiving teams Compressor

Three-man chamberQuarry teams Crush and screen plantsWell drilling teams Drilling machine

Support trucksAsphalt mixing teams Asphalt mixing plant

MedicalHospitals Operating room set

Central materialServices setIntensive care/post-op setPrimary X-ray setEMT/pre-op set

Medical logistics battalions/medical ADP equipmentMateriel management center ADP generator

Primary forkliftMedical company clearing TruckArea support Ambulance

Trauma treatment setMedical company/troop AmbulancesArmor/mechanized infantry Carrier CMD post

Trauma treatment setMedical company LID/ABN/AASLT Ambulance

Trauma treatment setAir ambulance in AASLT

Dental units Primary dental treatment setDental X-ray

Veterinary units Primary veterinary treatment setGround ambulance company/detachment Ground ambulance medical equipment setAir ambulance company/detachment Air ambulance

Air ambulance medical equipment setsPrimary FM radios in aircraft andflight operations

Medical command and control (MEDCOM/GRP/BDE/BATTALION) Primary AM net

MaintenanceMaintenance company (ORD), divisional Recovery vehicle

TruckWrecker

Maintenance company Primary mission ADPBase shop test facility

Military IntelligenceMI battalion/company Trailblazers

TeammateUAVGround control launch and recovery set)JSTAR (GSM)GBCSASASTrojan spiritCTTMITTTHMT

112 AR 220–1 • 15 November 2001


Type Unit Equipment

OL–279/TSQ–134OW–108/TSQ–134IPDS guardrail VImproved guardrail VGuardrail common sensorAN/ARW–84(V)4AN/ARW–84(V)5AN/ARW–84(V)6

OrdnanceOrdnance company RKT & MSL: ADP (DAS–SB,AN/MYQ–4A)Ordnance company Truck forkliftDS/GS/ammo Container handling

QuartermasterQM company POL fuel system supply pointQM company Water supply

Water purification equipmentTruckTank

S&S company, div and non-div Fuel systems supply point (FSSP)Water purification equipment systemWater supply equipment

SignalSignal battalion, hvy div AN/TTC–47(NCS)

AN/TRC–190 (LOS)AN/TRC–191 RAU)

Signal battalion, airborne or AN/TTC–50 (FES)AASLT div AN/TRC–190 (LOS)

AN/TTC–51 (DES)Signal battalion LID AN/TTC–47 (NCS)

AN/TRC–190 (LOS)AN/TRC–191 (RAU)

Corps area signal battalion AN/TYQ–35 (SCC)Corps area signal battalion AN/TTC–47 (NCS)

AN/TRC–190 (LOS)AN/TRC–191 (RAU)

Corps signal support battalion AN/TTC–4 (LEN)AN/TRC–190 (LOS)AN/TRC–191 (RAU)

Contingency corps signal battalion AN/TRC–190 (LOS)AN/TTC–50 (FES)AN/TTC–51 (DES)

Signal telecommunications battalion AN/TYC–39 MSG SWAN/TTC–39D

Theater TACSAT company AN/TSC–85B TACSATAN/TSC–93BTACSAT

Theater TROPO company (hvy) AN/TRC–170 radio terminal setTheater command operations company N/TRC–138 radio repeater setTheater minor node company AN/TTC–39A central office

AN/TRC–170 radio terminal setAN/TSC–93B TACSAT

Mission essential ADP LG CMDsCOSCOMsDISCOMsMMCsHHCSupport groupTAAC, AG company

TransportationTransportation truck company Task trucks(light, light-medium, medium, heavy, combat HET, and divisionalTMT) and related detachments

Task tractors

Task trailersTask semi-trailers

Transportation cargo transfer and terminal service companies anddetachments

All rough terrain forklifts

Container handlers and cranesTransportation watercraft amphibian units Self propelled watercraft

113AR 220–1 • 15 November 2001


Type Unit Equipment

Floating cranesAmphibians and air cushion vehicles

Transportation movement control units ADP22

Appendix DPersonnel Availability Criteria

D–1. GeneralThe unit status report personnel level will be based on that portion of a unit’s assigned strength available fordeployment/employment with the unit to accomplish its wartime mission. Specific guidance for use during contingencyoperations and mobilization is in AR 600–8–101 and AR 614–30.

D–2. Determining personnel availabilityUse the decision matrix in table D–1 to determine personnel availability for USR purposes. Not all categories willapply to every component.

Table D–1Determining personnel availability decision matrix (for use in determining if soldiers in various situations should be consideredavailable)

Categories Available

Legal processing (LP)Arrest and confinement NOPending military or civil court action NO1

Under investigation by a military/civil/criminal investigation activity NO1

Pending administrative/legal discharge or separation NO1

Medically non-available/hospitalized/convalescent leave (lesspostpartum), HIV positive, and medically unfit (MN)

NO2

Absent without leave (AW) NOAssigned, not joined (AN) NO3

Leave/TDY (LT) YES4

Deployed (DP) NO5

Temporary change of station (TC) NO6

Parenthood (PH) NO7 & 14

Prenatal NO120 days postpartum NOAdoption NO7

Minimum training for deployment not completed (TN) NO8

Dental (DN)No dental record NO9

No panograph NO9

Needs emergency dental care NO10

P3/P4 profile NO11

Temporary profile (precluding satisfactory duty performance) (TP) NOHIV testing (HT) NO11

No DNA record, uncorrected (DA) NO9 & 10

Family care plan (FP) NOConscientious objector (CO) NO13

Less than 7 days from ETS/(7E) NOLautenberg Amendment (LA) NO14

Missing/prisoner of war (MP) NO15

Sole surviving family member (SS) NO15

RC and multi-component unitsUnsatisfactory participation (UP) NO16

Simultaneous membership program (SM) NOARNGUSAssuming TTADS YESAssuming PRC YESUSARDesignated on critical list YESAssuming TTADS YES

114 AR 220–1 • 15 November 2001

Table D–1Determining personnel availability decision matrix (for use in determining if soldiers in various situations should beconsidered available)—Continued

Categories Available

Assuming PRC YES

Notes:1 Generally NO; however, can be YES if, in coordination with the servicing judge advocate, the unit commander determines that the pending action does notpreclude the soldier from deploying.2 Soldiers who will not deploy with the unit for various medical reasons fit into this category. It includes hospitalized soldiers, soldiers on convalescent leave(less postpartum), soldiers who have tested HIV positive, and those soldiers returned to the unit as fit from a PEB or MMRB whom the commander still con-siders medically unfit for deployment.3 A soldier is considered assigned not joined (AN) only if the soldier’s status is reported in accordance with rules outlined in AR 600–8–6, paragraph 3–5.4 YES; will be NO only if highly exceptional circumstances will prevent the soldier from being recalled from leave/TDY in order to meet the unit’s operationaldeployment requirements and also will prevent the soldier from rejoining the unit in order to meet the unit’s specific mission requirements. HQDA considers“within 30 days” as a reasonable criterion; however, MACOM commanders may establish more demanding criteria for their rapidly deployable, forward-sta-tioned, or special mission units.5 Usually NO; however, can be YES if, in the judgment of the commander, the individual can return and meet an operational deployment requirement. Whendetermining whether or not the soldier can return, the commander must consider the type of deployment the soldier is on, the proximity of the deployment,and who decides if the soldier returns to the parent unit. If YES is determined for deployed/mobilized personnel, then the parent unit must notify the unit ofattachment to preclude double counting of the soldier’s availability. (For USR purposes, only one unit can count an individual soldier as an available re-source on a given as-of date.) (See para 4–4 and note 6 below.)6 Individual soldiers who have proceeded on a TCS move will be considered assigned but not available to the home station.7 A military mother of a newborn is not available for four months after the child’s birth. (A single parent or one member of a military couple adopting a child isnot available for four months after the child is placed in the home.)8 Soldier has not completed OBC, WOBC, or IET requirement or its equivalent.9 Soldier is temporarily unavailable owing to inability to construct a temporary dental record and/or complete a panograph prior to deployment.10 During the deployment dental screening, a soldier may be designated non-available for deployment based solely on a dental emergency (such as traumaor oral infection). Once the dental emergency is remedied, the soldier’s status will be immediately changed to available.11 Personnel with permanent (P3/P4) profiles are considered not available unless cleared as deployable via the MOS medical retention board (MMRB) and/or are found fit by MEB/PEB (or medically cleared to mobilize (RC only)). Those soldiers returned to the unit as fit from a MEB/PEB or MMRB who the com-mander still considers as non-available for deployment should be returned for medical reevaluation, and only after that referral should the commander in-clude the soldier in the medically non-available (MN) category as non-available for deployment.12 Soldiers are non-deployable and unavailable for mobilization only if an HIV test cannot be administered prior to deployment.13 Soldiers who have submitted a conscientious objector application will continue to be available for deployment in connection with a contingency operationor selective/partial/full/total mobilization except as follows: soldiers with an approved conscientious objector (1–0) status will not be deployable and will beallowed to continue processing for discharge. The General Courts-Martial Convening Authority (GCMCA) may, at its discretion, excuse the soldier fromdeployment when the soldier has an application pending at the Department of the Army Conscientious Objector Review Board. Once a soldier submits aformal application for conscientious objector status under provisions of AR 600–43, the soldier’s eligibility for OCONUS deployments, not ordered in connec-tion with contingency operations or selective/partial/full mobilization, will be determined in accordance with AR 614–30, table 3–2.14 Soldiers known to have, or soldiers whom commanders have reasonable cause to believe have, a conviction of a misdemeanor crime of domestic vio-lence are non-available for missions that require possession of firearms or ammunition.15 The soldier may waive the deployment restriction in accordance with AR 614–30, table 3–2, rules 1e, 2, 12, and 16.16 The soldier is not available beginning on the date the soldier attained his or her ninth un-excused absence, or the date the soldier is determined to be anunsatisfactory participant for failing to attend or complete the entire period of annual training (AR 135–91, para 4–12.)

Appendix EReason Codes

E–1. Primary reason codes for overall level not C-1When filling out section A, overall set, field 6 (REASN), select a code from table E–1 indicating the primary reason aunit’s overall level is not C-1.

E–2. Reason codes associated with PCTEF reporting and peacetime operational deploymentUse the codes in table E–2 when required to enter PCTEF data in regular reports, composite reports, deployed reports,and DUIC reports in accordance with paragraph 11–3. Enter REASN code “M” in FF-level deployed reports andcomposite reports to indicate the commander’s use of the special training level criteria in accordance with paragraph11–4f.

E–3. Reason codes for other than P-1, S-1, R-1, T-1, NBC S-1, and NBC T-1Use codes from the tables E–3, E–4, E–5, and E–6 when completing section A, overall set field 7, secondary reason,field 8, tertiary reason, and in all measured resource area sets field 2, primary reason level not 1 (PRRES, ESRES,ERRES, TRRES). Use codes from table E–7 to indicate the reasons that the NBC S-level or the NBC T-level are otherthan level 1.

115AR 220–1 • 15 November 2001

Table E–1Primary reason overall level not C-1

Code Definition

P PersonnelS Equipment on handR Equipment readinessT TrainingN Unit is reporting C-5 because of a HQDA action or program.X Commander’s judgment. Explanatory remarks must be submitted on

a REASN card.Z Commander’s subjective judgment is used, and one or more of the

individual resource areas is not measured. Explanatory remarksmust be submitted.

6 One or more of the individual resource areas is not measured

Table E–2Reason codes associated with PCTEF reporting

Code Definition

A Non-reportable subordinate units/elements are pending peacetimeoperational deployment in accordance with paragraph 11–3. (Seenote 1 below.)

B The AA-level or FF-level unit (includes DUICs) or reportable subor-dinate units/elements are pending peacetime operational deploy-ment. (See note 1 below.)

C Less than 5 percent of the reporting unit’s capability is deployed insupport of a single operation.

D 5–15 percent of the reporting unit’s capability is deployed in supportof a single operation.

E 16–25 percent of the reporting unit’s capability is deployed in sup-port of a single operation.

F 26–35 percent of the reporting unit’s capability is deployed in sup-port of a single operation.

G 36–75 percent of the reporting unit’s capability is deployed in sup-port of a single operation.

H Over 75 percent of the reporting unit’s capability is deployed in sup-port of a single operation.

I Less than 5 percent of the reporting unit’s capability is SSC de-ployed/employed in support of multiple operations.

J 5–15 percent of the reporting unit’s capability is SSC deployed/em-ployed in support of multiple operations.

K 16–25 percent of the reporting unit’s capability is SSC deployed/em-ployed in support of multiple operations.

L 26–35 percent of the reporting unit’s capability is SSC deployed/em-ployed in support of multiple operations.

M The T-level was determined in accordance with special criteria formajor combat units in accordance with paragraph 11–4f.

O 36–75 percent of the reporting unit’s capability is deployed in sup-port of multiple operations.

Q Over 75 percent of the reporting unit’s capability is deployed in sup-port of multiple operations.

Notes:1 Use of REASN codes “A” and “B” are limited to a specified time period in accordance with paragraph 11–3.2 Explanatory GENTEXT remarks are required when a REASN code in table E–2 is used.

116 AR 220–1 • 15 November 2001

Table E–3Reason codes for personnel

Code Definition

P01 CasualtiesP02 Prisoner of warP03 Organization inactivatingP04 Organization recently activatedP05 Organization on deploymentP06 Personnel levies excessiveP07 Personnel shortage-assignedP08 MOS imbalancesP09 Not MOS qualifiedP10 Personnel non-availableP11 Personnel deployedP12 Personnel shortage—air defense MOSP13 Personnel shortage—armor MOSP14 Personnel shortage—artillery MOSP15 Personnel shortage—combat crewsP16 Personnel shortage—crew chiefP18 Personnel shortage—engineer MOSP19 Personnel shortage—enlistedP20 Personnel shortage—enlisted combat crewsP22 Personnel shortage—infantry MOSP26 Personnel shortage—maintenanceP28 Personnel shortage—NCO (SGT to SSG)P29 Personnel shortage—NCO (SGT to SGM)P30 Personnel shortage—senior NCO (SFC to SGM)P32 Personnel shortage—officerP34 Personnel shortage—LT to CPTP35 Personnel shortage—MAJ to COLP36 Personnel shortage—pilotP37 Personnel shortage—qualified to perform MOS duties to which as-

signedP38 Personnel shortage—signal MOSP39 Personnel shortage—warrant officerP40 Subordinate organization detachedP48 Personnel skill shortage—weapon system conversionP54 Personnel shortage—enlisted aircrewP59 Personnel shortage—missile maintenanceP60 Personnel shortage—aircraft maintenanceP64 Personnel shortage—linguistsP65 Personnel shortage—service constraint (low ALO, type B, or cadre)P66 Personnel not available—drug and alcohol abuseP67 Personnel shortage—medical health professionalsP68 Personnel shortage—medical service skillsP69 Personnel lack security clearanceP70 Skill shortage—nuclear weaponsP71 Personnel shortage—full-time supportP72 Personnel turnover—losses to unitP73 Personnel turbulence—internal reassignmentsP74 Unit reorganizingP76 Personnel supporting training mission (school support)P77 Training unit with wartime mission tasking capabilityP78 Unit not manned and/or equipped; required in wartime structureP81 Not MOS qualified—awaiting trainingPUP Reserved for use as secondary reason (SECRN), field (6–K–L), only

when the commander has reported an overall P-level that is differ-ent from the lowest resources area P-level.

117AR 220–1 • 15 November 2001

Table E–4Codes for equipment on hand

Code Definition

S03 Aircraft in storageS04 Aircraft not fully equippedS05 Aircraft on loanS06 Aircraft operational loss/combat lossS07 Equipment away for repairsS08 Equipment away on loanS11 Awaiting critical modificationS12 Component low-density end item unsatisfactoryS13 Equipment in administrative storage/pre-positionedS16 Obsolete equipmentS17 Organization inactivatingS18 Organization recently activatedS19 Radar equipment unavailableS20 Spare low-density end item unsatisfactoryS25 Shortage—communications equipmentS27 Shortage—major end itemS28 Shortage—engineering equipmentS29 Shortage—general supply equipmentS36 Shortage—special supply equipmentS37 Shortage—stock supplyS41 Shortage—test equipmentS42 Shortage—authorized equipmentS43 Shortage—vehicleS45 Shortage—aircraftS51 Shortage—missileS57 Shortage—support equipmentS64 Shortage—NBC equipmentS77 Shortage—generatorsS80 Shortage—weaponsS89 Shortage—RX items authorized for stockageS90 Shortage—pacing itemsS91 Unit reorganizingS92 Equipment not available owing to school support (training) missionS93 Equipment shortage—service constraint (low ALO, type B, cadre

unit)S94 Notional unit—not manned, not equippedS95 Unit undergoing major equipment conversion (equipment-on-hand

turbulence owing to force modernization)S99 Shortage—fire support equipmentSTW Training unit with wartime mission tasking capabilitySUP Reserved for use as secondary reason field (6–K–L) only; used only

when the commander has reported an overall S-level that is differ-ent from the lowest resource area S-level.

SXA Equipment in transit to deployed locationSXB Equipment in transit from deployed locationSXC Force modernization fielding delaySXD Unit lacks funds for stock funded equipmentSXX Equipment not available owing to partial deployment

Table E–5Codes for equipment serviceability

Code Definition

R00 Equipment serviceability degradation—fuel shortageR01 Aircraft grounded safety flightR02 Aircraft do not meet mobilization requirementR05 Not mission capable depot—programmed depot maintenanceR06 Unit recently activatedR07 Equipment conversion (equipment serviceability turbulence—force

modernization)R08 NBC equipment inoperable or not calibratedR09 Damage—battle/combatR11 Damaged/inoperative—aircraftR17 Damaged/inoperative—counter measures (electrical/mechanical)R21 Damaged/inoperative—equipmentR22 Damaged/inoperative—equipment communication

118 AR 220–1 • 15 November 2001

Table E–5Codes for equipment serviceability—Continued

Code Definition

R23 Damaged/inoperative—generatorsR24 Damaged/inoperative—equipment engineeringR25 Damaged/inoperative—equipment fire controlR27 Damaged/inoperative—IFFR28 Damaged/inoperative—launcher/missileR31 Damaged/inoperative—radarR32 Damaged/inoperative—radar fire controlR33 Damaged/inoperative—radar searchR35 Damaged/inoperative—system dataR39 Damaged/inoperative—system missile fire controlR45 Damaged/inoperative—vehicleR46 Damaged/inoperative—weaponR49 Equipment installationR51 Equipment obsoleteR52 Equipment removalR56 Inspection failedR58 Insufficient fundingR59 Installing field changes/alterations/modificationsR60 Maintenance—facilities inadequateR61 Maintenance—-in progressR62 Maintenance—scheduledR63 Maintenance—unscheduledR64 Modification—aircraftR71 Not mission capable supply (NMCS)—above unit maintenanceR79 Not mission capable supply—organizational maintenanceR80 Organization inactivatingR81 Organization in rotational deploymentR82 Overhaul—aircraftR83 Overhaul—equipmentR84 Overhaul—weaponsR85 Power failureR86 Radar unreliable/flight/ground checkR87 Repair—attached organizational equipmentR88 Repair—generatorsR90 Repair—equipmentR91 Repair—field maintenanceR92 Repair—lack proper tools to performR93 Repair—unit maintenanceR94 Repair—weaponsR95 NBC equipment incomplete or obsoleteR97 Modification—missileR99 Overhaul—missileRAT Not mission capable depot—major modifications requiredRBA Maintenance in progress—estimated complete less than 24 hoursRBB Maintenance in progress—estimated complete more than 24 hoursRBE Unit reorganizingRBF Combat essential (pacing) item inoperativeRBG Notional unit—not equipped not mannedRBH Equipment inoperative owing to school support (training) missionRBI Equipment inoperable owing to extensive trainingRBJ Equipment inoperable owing to extensive admin useRBK Equipment not available owing to service constraint (low ALO, type

B, cadre unit)RBP Shortage repair parts/spares (ASL/PLL)RBQ Inoperative—safetyRBS Damaged/inoperative—accidentRUP Reserve for use as secondary reason field (6–K–L) only when the

commander has reported an overall R-level that is different from thelowest resource area R-level.

119AR 220–1 • 15 November 2001

Table E–6Training codes

Code Definition

T01 Administrative deadline equipment (includes for safety)T02 Deadline rate of major communications/electronic items restricts

trainingT05 Inadequate—school quotasT07 Inadequate—training ammunitionT08 Inadequate—training areasT10 Incomplete—firing/proficiency testsT11 Insufficient—crews combat-readyT15 Insufficient—fundingT17 Insufficient—pilots combat-readyT18 Insufficient—training timeT21 MOS imbalancesT23 Operational commitmentsT24 Organization activatingT25 Organization inactivatingT26 Organization in rotational deploymentT27 Personnel not availableT28 Personnel turnover excessiveT29 Shortage—amphibious shippingT30 Shortage—crew chiefT31 Shortage—equipmentT32 Shortage—instructorT33 Shortage—instructor pilot/aircrewT34 Shortage—leadership position personnelT35 Shortage—senior NCOT36 Shortage—qualified officersT37 Shortage—personnelT38 Shortage—technical skill personnelT39 Squad/crew qualification lowT40 Tests—unsatisfactory readinessT41 Training incompleteT45 Aviator—training status degradedT46 NBC defensive training incompleteT47 Unit reorganizingT48 Notional unit—unmanned, unequippedT49 Training unit with wartime mission tasking capabilityT51 Training incomplete—major equipment conversionT53 Training incomplete—owing to school support missionT54 Training incomplete—owing to Service constraint (low ALO, type B,

cadre unit)T55 Training incomplete—subordinate organization(s) in standby statusT57 Training incomplete—fuel shortageT65 Training incomplete—nuclear weaponsT66 Training incomplete—special duty requirementsT68 Insufficient—flight hoursT84 Language indicator code imbalancesT85 DLPT scores below minimumsT86 DLPT re-test delay (6 months or more)TUP Reserved for use as secondary reason field (6–K–L) only; and used

only when the commander has reported an overall T-level that is dif-ferent from the lowest resource area T-level.

T57 Training incomplete—fuel shortage

120 AR 220–1 • 15 November 2001

Table E–7NBC supply/serviceability and training status codes

Code Definition

SRA Shortage—category 1 equipment (MASK)SRB Shortage—category 2 equipment (DET)SRC Shortage—category 3 equipment (DECON)SRD Shortage—category 4 equipment (IPE)SRE Shortage—category 5 equipment (RAD)SRF Shortage—category 6 equipment (MED)SRG Unserviceable/expired—category 1 equipment (MASK)SRH Unserviceable/expired—category 2 equipment (DET)SRI Unserviceable/expired—category 3 equipment (DECON)SRJ Unserviceable/expired—category 4 equipment (IPE)SRK Unserviceable/expired—category 5 equipment (RAD)SRL Unserviceable/expired—category 6 equipment (MED)SRM Shortage of support equipment (DECON site support material)SRN Shortage of general supply equipment (batteries, embark boxes,

sanitation solution, and so forth)SRO Shortage of repair partsSRP NBC equipment incomplete or obsoleteSRQ Critical equipment capability deficiencySRR Non-mission capable during recent NBC SMAT/LRE/evaluationSRS Shortage of MES chemical agent patient treatment, LIN M23673SRT Shortage of medical NBC defense materialSRU Shortage of MES chemical agent patient decontamination, LIN

25865

NBC training codesTRA Insufficient individual protective/survival measures trainingTRB Insufficient unit mission-oriented task trainingTRC Insufficient NBC team trainingTRD Insufficient NBC officer/specialist trainingTRE Insufficient MOPP conditioning trainingTRF Insufficient personnel completing the mask confidence exerciseTRG Shortage of training devices/assetsTRH Shortage of trained NBC team membersTRI Personnel shortage—NBC defense officerTRJ Personnel shortage—NBC defense specialistTRK Non-mission capable during recent NBC MCCARES/ORE/evalua-

tionTRL Environmental restrictions on trainingTRM High-temperature training restrictionsTRN Inadequate training ammunition—CS capsules/grenadesTRO Inadequate school quotasTRP New equipment—training not received

Appendix FExempt/Non-Type Classified Items

F–1. Generala. Each unit’s current authorization document (MTOE/TDA) serves as the base document for preparing the unit’s

reportable equipment list. This list is used during calculation of equipment S-levels as outlined in chapters 5 and 6.HQDA has identified certain categories of equipment that are exempt from unit status reporting for a specified time. Inaddition, commanders may designate selected items as on hand in lieu of required equipment items.

b. Exempt LINs are not reportable in the USR. Paragraph 5–3 discusses reportable equipment. In accordance withparagraph 5–3d, any equipment that has not been designated as exempt from reporting must be reported. Exempt LINsmust be approved by HQDA (DAMO–FMF).

c. HQDA authorized substitute, in-lieu-of (ILO), or MACOM non-type classified items (NTCI) will be counted asequipment on hand for reporting purposes in accordance with criteria established in paragraph 5–4. HQDA-authorizedsubstitute items are listed in SB 700–20, appendix H. In-lieu-of items are those items that do not have a valid substituterelationship reflected in SB 700–20, appendix H, but that the commander wishes to use in place of a required item ofequipment. When applying substitutes and ILO equipment, commanders must adhere to criteria established in para-graph 5–4dto determine quantity and reportable EOH for USR purposes.

121AR 220–1 • 15 November 2001

F–2. LINs exempted from unit status reporting computationsa. LINs designated as exempt will not be included in S-level computations until a sufficient quantity of that

equipment is on hand to attain an S–3 level of fill.b. A listing of LINs currently approved by HQDA for exemption is provided at table F–1, below. Updates to this

listing will be posted on the HQDA force management bulletin board at www.usafmsardd.army.mil/fmbb/. Theprocedures for requesting and processing LIN exemptions also are explained at this Web site.

c. All items designated as “to accompany troops/not authorized pre-positioning” (TAT/NAP) in APS MTOEs areexempt from reporting, regardless of S–Level.

F–3. Non-type classified itemsa. MTOE/TDA changes or modernization of items may not always meet MACOM-peculiar requirements. Equip-

ment procured to meet current mission requirements may be supported against EOH requirements if the non-typeclassified item (NTCI) meets the following requirements—

(1) It has the same characteristics as the authorized item.(2) It can be used in conjunction with other required items.(3) It is supportable. Required repair parts must be available. Repair capability must be within the scope of the unit/

organization or available through other means (such as in-theater contractor support or DS maintenance team). Asource of supply for replacement of the major end item must be available.

(4) It will be deployed with the unit to accomplish wartime missions if the authorized item is not available.b. NTCIs may be reported against Army standard equipment until type classification is completed. MACOMs are

responsible for initiating and monitoring type classification actions required to catalog/document the NTCI properly tothe unit’s MTOE, SB 700–20, and to ensure that it meets standard Army multi-command management informationsystem (STAMIS) supportability for ES.

F–4. Non-type classified items, stand-alone systemsa. The Army has decided not to document some technology-intensive equipment and very low-density NTCI

equipment on the unit MTOE because, in most cases, the technology is extremely perishable. In some instances, theseitems may have the effect of an ERC–A item on the unit’s ability to accomplish its mission.

b. NTCIs developed and procured for a “stand-alone” system/item must have an LIN assigned by the MACOM, andthey must meet the criteria for ERC A, as outlined in appendix B, before they are reported in the USR system.

c. All NTCI items that meet the criteria in paragraph F–4b, will be reported if the unit is short of the item and theabsence of the item has an adverse effect on the unit’s ability to accomplish its wartime mission. NTCI stand-alonesreported will not be included in the S-level or R-level calculations.

d. NTCI stand-alones will be reported on the GENTEXT label: ESRAT, section D. At a minimum, the local LIN,the noun nomenclature, and a brief description of the function of the item will be included in the remarks set.

Table F–1LINs exempt from reporting

LIN Units affected Expiration date Notes

A17680 All Army units Until revoked by HQDAA44539 All Army units Until revoked by HQDAA57322 All mil intel units (SRC 30/34) 16 Oct 2001A79585 All Army units Until revoked by HQDAA79653 All Army units Until revoked by HQDAA79721 UICs: W1KNAA, W4RFAA,

WAB3AA, WAX8AA, WAYCAA,WAYPAA, WC08AA, WC3EAA,WC43AA, WCX9A0, WCYMAA,WDHXAA, WDUVC0, WDX2AA,WDX9AA, WDYFC0,WFAKAA,WFJ4AA, WGLEAA, WH6BAA,WH6DE0, WHPPAA, WHT7AA,WJCHAA, WMZAA0, WMZAB0,WQRBAA, WQRCAA,WQRYAA, WTQZAA, WYDCAA

Until revoked by HQDA

B58567 All Army units 16 Oct 2001C05541 All Army units Until revoked by HQDAC18297 All Army units 16 Oct 2001C40499 All Army units Until revoked by HQDAC57780 All Army units Until revoked by HQDA

122 AR 220–1 • 15 November 2001

Table F–1LINs exempt from reporting—Continued


C59313 UICs: W1KNAA, W4RFAA,WAB3AA, WAX8AA, WAYCAA,WAYPAA, WC08AA, WC3EAA,WC43AA, WCX9A0, WCYMAA,WDHXAA, WDUVC0, WDX2AA,WDX9AA, WDYFC0,WFAKAA,WFJ4AA, WGLEAA, WH6BAA,WH6DE0, WHPPAA, WHT7AA,WJCHAA, WMZAA0, WMZAB0,WQRBAA, WQRCAA,WQRYAA, WTQZAA, WYDCAA


C62375 All Army units Until revoked by HQDAD99573 All Army units Until revoked by HQDAE45766 All Army units Until revoked by HQDAE45820 All Army units Until revoked by HQDAE45830 All Army units Until revoked by HQDAE56578 All Army units Until revoked by HQDAE94970 Units scheduled to receive the

common ground station (CGS)16 Oct 2001 1

E98103 All Army units Until revoked by HQDAF39378 SRC 422427LM QM Co. (supply

DS)SRC 42418l, QM Co (supplyGS)

16 Oct 2001

G74711 Units scheduled to receive theCGS

16 Oct 2001 1

H35404 All Army units Until revoked by HQDA 2I LINs All Army units Until revoked by HQDAJ31656 UICs: W1KNAA, W4RFAA,



J43027 All mil intel units (SRC 30/34) 16 Oct 2001J71611 All Army units Until revoked by HQDAJ87768 UICs: W1KNAA, W4RFAA,



J97569 All Army units Until revoked by HQDAJ98501 All Army units Until revoked by HQDAK14677 All Army units Until revoked by HQDAK14814 All mil intel units (SRC 30/34) 16 Oct 2001K28023 All Army units Until revoked by HQDAK47021 All Army units Until revoked by HQDAK78558 All Army units Until revoked by HQDAK87390 All Army units Until revoked by HQDAK87391 All Army units Until revoked by HQDAK87392 All Army units Until revoked by HQDAK87401 All Army units Until revoked by HQDAK87433 All Army units Until revoked by HQDAK87536 All Army units Until revoked by HQDAK87537 All Army units Until revoked by HQDAK87538 All Army units Until revoked by HQDAK87539 All Army units Until revoked by HQDAK87541 All Army units Until revoked by HQDAK87544 All Army units Until revoked by HQDA

123AR 220–1 • 15 November 2001



K87545 All Army units Until revoked by HQDAK87546 All Army units Until revoked by HQDAK87547 All Army units Until revoked by HQDAK87550 All Army units Until revoked by HQDAK87551 All Army units Until revoked by HQDAK87554 All Army units Until revoked by HQDAK87556 All Army units Until revoked by HQDAK87557 All Army units Until revoked by HQDAK87559 All Army units Until revoked by HQDAK87560 All Army units Until revoked by HQDAK87561 All Army units Until revoked by HQDAK87562 All Army units Until revoked by HQDAK87563 All Army units Until revoked by HQDAK87564 All Army units Until revoked by HQDAK87565 All Army units Until revoked by HQDAK87566 All Army units Until revoked by HQDAL84098 Units scheduled to receive the

CGS16 Oct 2001

M01100 All Army units Until revoked by HQDAM02109 All Army units Until revoked by HQDAM14381 All Army units Until revoked by HQDAM30411 All Army units Until revoked by HQDAM74849 All Army units Until revoked by HQDAM80413 All mil intel units (SRC 30/34) 16 Oct 2001N02758 All Army units Until revoked by HQDAN04456 All Army units Until revoked by HQDAN04596 All Army units Until revoked by HQDAN04732 All Army units Until revoked by HQDAN04982 All Army units Until revoked by HQDAN15518 All Army units Until revoked by HQDAN23721 All Army units Until revoked by HQDAP41172 All Army units Until revoked by HQDAP43177 All Army units Until revoked by HQDAP43211 All Army units Until revoked by HQDAR00993 All mil intel units (SRC 30/34) 16 Oct 2001R01061 All mil intel units (SRC 30/34) 16 Oct 2001R30308 Units scheduled to receive the

CGS16 Oct 2001 1

R30308 All Army units 1, 2R30895 All Army units Until revoked by HQDAR55200 All Army units Until revoked by HQDA 3R71504 All Army units Until revoked by HQDAR71604 All Army units Until revoked by HQDAS01373 All Army units Until revoked by HQDAS01441 All Army units Until revoked by HQDAT16000 All Army units Until revoked by HQDAT40405 All Army units Until revoked by HQDAT67663 All SRC 42 units (supply) 16 Oct 2001T71563 All mil intel units (SRC 30/34) 16 Oct 2001T75536 All Army units Until revoked by HQDAT89316 All Army units Until revoked by HQDAT93761 All Army units Until revoked by HQDAT95924 Units scheduled to receive the

CGS16 Oct 2001 1

U01275 All Army units Until revoked by HQDAU01295 All Army units Until revoked by HQDAU01305 All Army units Until revoked by HQDAV08699 All Army units Until revoked by HQDAV08721 All Army units Until revoked by HQDAV62406 All Army units Until revoked by HQDAV98788 All Army units Until revoked by HQDAW00869 WQUCAA, WV6NAA, WPEJAA,

WPG1AA,WV6FAA, WPPBAA,WPERAA, WPU8AA.

16 Oct 2001

W43758 All mil intel units (SRC 30/34) 16 Oct 2001W60351 All Army units Until revoked by HQDAY03104 All Army units Until revoked by HQDA

124 AR 220–1 • 15 November 2001



Z LINs All Army units Until revoked by HQDA 2

Notes:1 These LINS are exempt only if authorized in association with the common ground station (GCS) “LIN Z17435” being fielded to military intelligence units. Ifthe “Z” LIN for the CGS is not authorized, then these associated LINs are not exempt. Exemption is effective until CGS fielding is completed for the militaryintelligence unit.2 This exemption included all I LINs and all Z LINs for all units, unless specifically directed otherwise by HQDA or the MACOM.3 Includes radio sets AN//PRC–104A, AN/GRC–193A, and AN/GRC–213A.

125AR 220–1 • 15 November 2001

Glossary

Section IAbbreviations

AAActive Army

AASLTair assault

ACCBair cavalry combat brigade

ACSasset control subsystem

ADTactive duty training

AEBaerial exploitation battalion

AFUassault fire unit

ALOauthorized level of organization

AMEDDArmy Medical Department

AMIMArmy Modernization Information Memorandum

AMTPArmy mission training plan

ARArmy regulation

ARNGUSArmy National Guard of the United States

ARTEPArmy Training and Evaluation Program

ASIadditional skill identifier

ASIOEassociated support items of equipment

ASLauthorized stockage list

ATannual training

ATMair-crew training manual

126 AR 220–1 • 15 November 2001

attn/ATTNattention

authauthorized

avgaverage

AVLBarmored vehicle launch bridge

avnaviation

BASOPSbase operations

BIIbasic issue item

BMMborrowed military manpower

BOIPbasis of issue plan

CBWchemical and biological weapons

cdrcommander

CEWIcombat electronic warfare and intelligence

CFVcavalry fighting vehicle

chapchapter

CIFcentral issue facility

CINCCommander in Chief

CMFcareer management field

COHORTcohesive operational readiness training

COLcolonel

CScombat support

127AR 220–1 • 15 November 2001

CSScombat service support

CTCcombat training center

CTTcommander’s tactical terminal; also common task training

DADepartment of the Army

DARNGDirector, Army National Guard

DLIDefense Language Institute

DLPTdefense language proficiency test

DODDepartment of Defense

DOLdirector of logistics

ECSequipment concentration sites

e-dateeffective date

EOHequipment on hand

ERCequipment readiness code

EWelectronic warfare

FAfield artillery; also functional area

fld/FLDfield

FMCfully mission capable

FTNGDfull-time National Guard duty

GBCSground based common sensor

GCMCAgeneral court-martial convening authority

128 AR 220–1 • 15 November 2001

HETheavy equipment transporter

HHBheadquarters and headquarters battery

HHCheadquarters and headquarters company

HQHeadquarters

HQDAHeadquarters, Department of the Army

IADTinitial active duty for training

IFVInfantry Fighting Vehicle

ILOin lieu of

IPEindividual protective equipment

ITVimproved tow vehicle

JCSJoint Chiefs of Staff

KATUSAKorea augmentation to United States Army

LCSSLand Combat Support System

LIClanguage identification code

LIDlight Infantry division

LINline item number

LOGlogistics

LTOEliving table of organization and equipment

MABMobile Assault Bridge

MACOMmajor Army command

129AR 220–1 • 15 November 2001

MAEmission accomplishment estimate

MAJmajor

MARCmanpower requirements criteria

MEBDmedical evaluation board

MEDCOMMedical Command

MOSCmilitary occupational specialty code

MSEmateriel status evaluation or mobile subscriber equipment

mtdmounted

MTOEmodification table of organization and equipment

MTPmission training plan

NAPnot authorized pre-positioning

NBCnuclear, biological, chemical

NCOnoncommissioned officer

NETnew equipment training

NMCMnot mission capable maintenance

OBCofficer basic course

OCSofficer candidate school

ODCSINTOffice of the Deputy Chief of Staff for Intelligence

ODCSLOGOffice of the Deputy Chief of Staff for Logistics

ODCSOPSOffice of the Deputy Chief of Staff for Operations and Plans

130 AR 220–1 • 15 November 2001

ODCSPEROffice of the Deputy Chief of Staff for Personnel

OOCout of cycle

OPFORopposing forces

ordordnance

OREoperational readiness evaluation

OTSGOffice of The Surgeon General

PEBphysical evaluation board

PLLprescribed load list

PMCSpreventative maintenance checks and services

PMOSCprimary military occupational specialty code

PORpreparation of replacements for overseas movement

QTBquarterly training brief

REFORGERredeployment of forces to Germany

ROTCReserve Officer Training Corps

SARRSStandard Army Retail Supply System

SCGsecurity classification guide

SDspecial duty

SGTsergeant

SIDPERSStandard Installation/Division Personnel System

SIMASystems Integration and Management Activity, USAMC

131AR 220–1 • 15 November 2001

SOJTsupervised on the job training

SPself-propelled

SPBS–RStandard Property Book System—Redesign

SQIspecial qualifications identifier

SSGstaff sergeant

STAMISStandard Army Management Information System

TAADSThe Army Authorization Documents System

TAADS–RThe Army Authorization Documents System—Redesign

tactactical

TADSStraining aides, devices, simulators, and simulations

TATto accompany troops

TDtroop diversion

TECtraining extension course

TMDEtest measurement and diagnostic equipment

topotopographic

TOWtube launched, optically tracked, wire guided

TPUtroop program unit

TSGThe Surgeon General, United States Army

TTADStemporary tour of active duty

UAVunmanned aerial vehicles

132 AR 220–1 • 15 November 2001

ULLSUnit Level Logistics System

USARUnited States Army Reserve

USRunit status report

UTEunit training equipment

WETSweekend training site

WOwarrant officer

YTByearly training brief

Section IITerms

Active Guard/Reserve (AGR)Army National Guard of the United States and United States Army Reserve (USAR) personnel serving on active duty(AD) under section 672(d), Title 10, United States Code, and the Army National Guard of the United States(ARNGUS) personnel serving on full-time National Guard duty (FTNGD) under section 502(f), title 32, United StatesCode. These personnel are on FTNGD or AD (other than for training on AD in the Active Army) for 180 days or morefor the purpose of organizing, administering, recruiting, instructing, or training the Reserve components.

Annual trainingThe minimum period of annual active duty training or annual field training that a member performs each year to satisfythe annual training requirements associated with his or her Reserve component assignment. It may be performed duringone consecutive period or in increments of one or more days, depending on mission requirements.

Area of concentrationThe functional area orientation of officers.

Army training and evaluation programA program for collective training in units. It describes the collective tasks which the unit must perform to accomplishits mission and survive on the battlefield.

Assigned strengthThe assigned personnel strength of a unit includes all permanently assigned personnel plus those personnel carried on aseparate TDA providing full-time Reserve component support who will mobilize with the unit and personnel desig-nated to join an active component unit under PROFIS, the professional filler system. Personnel temporarily absent (forexample, leave and TDY) are included in assigned strength.

Authorization documentsHQDA- or proponent-approved records that reflect personnel and equipment requirements and authorizations for one ormore units. Authorization documents also provide unit organizational information. Such documents are MTOE andTDA.

Authorized level of organizationEstablishes the authorized personnel strength and equipment level for MTOE units. May be expressed in numerical orletter designated levels representing percentages of full TOE/MTOE manpower spaces, or reflecting type or cadreorganization levels of the base TOE. For example, ALO 1 is 100 percent, ALO 2 approximately 90 percent, ALO 3approximately 80 percent, and ALO 4 approximately 70 percent. A unit’s ALO is listed in section I of its MTOE.

133AR 220–1 • 15 November 2001

Authorized strengthThat portion of the required manpower that can be supported by the manpower available and that is reflected in theauthorized column of authorization documents.

Available daysApplies to assessing equipment’s ability to do its combat or support job. Available days are the days equipment is onhand in the organization and fully able to do its mission. The time that equipment is fully mission capable.

Available strengthThat portion of a unit’s assigned strength available for deployment and/or employment, as qualified in appendix E.

Borrowed military manpowerThe use of military manpower from an MTOE unit to perform duties within a TDA activity where a MACOM-approved manpower requirement exists, but for which no manpower space has been authorized. Additionally, borrowedmilitary manpower may be employed in those cases where, although manpower spaces have been authorized, thepositions are vacant.

Cadre unitOrganized at the cadre (nucleus) level to provide a base for expansion to ALO 1 in case of mobilization; for example, aunit that will have a training mission. Cadre type units will not be organized or used solely for non-wartime missions.Units organized at the cadre level of the TOE will be authorized only that equipment needed for cadre training.

Carrier unit identification codeProvides a means to assign personnel and account for equipment that arrives at the unit location before unit activation.Upon activation of the MTOE unit, HQDA (DAMO–FD) will discontinue the carrier UIC.

Category level (C–Level)Indicates the degree to which a unit has achieved prescribed levels of fill for personnel and equipment, the trainingstatus of those personnel, and the maintenance status of the equipment.

Centralized documentationA process for the consolidated development of force structure guidance by HQDA, and centralized building of TOE,BOIP, and MTOE documents by USAFMSA with MACOM involvement and validation.

Collective trainingTraining in institutions or in units to prepare cohesive teams and units to accomplish their combined arms missions.

Combined trainingTraining involving elements of two or more forces of two or more nations.

Command and controlThe exercise of authority and direction by a properly designated commander over assigned forces in the accomplish-ment of the mission. Command and control functions are performed through an arrangement of personnel, equipment,communications, facilities, and procedures employed by a commander in planning, directing, coordinating, and control-ling forces and operations in the accomplishment of the mission.

Command and control numberA six-position alphanumeric code that is used to identify authorization documents; for example, FC0188. The first twocharacters represent the MACOM, in this example FORSCOM. The third and fourth digits are the change numberwithin the fiscal year, and the fifth and sixth digits are the fiscal year in which the document becomes effective.

Command and control systemThe facilities, equipment, communications, procedures, and personnel essential to a commander for planning, directing,and controlling operations of assigned forces pursuant to the missions assigned.

Continental United States ArmyCommands, supports, and supervises United States Army Reserve units in specified geographical areas. The CONUSAreports directly to FORSCOM.

134 AR 220–1 • 15 November 2001

DeployThe relocation of forces, personnel, or equipment from home station to meet operational deployment requirements.

Deployment tempo (DEPTEMPO)The number that represents the amount of time (within one month) that a unit would have to deploy as a whole toreplicate the effects of all actual unit, subordinate unit, detachment, and individual soldier deployments for training andoperational missions.

E-date (effective date)A six-position numeric code that signifies the actual date that an authorization document is effective; for example,871001. The first two digits are the calendar year, the third and fourth are the month, and the fifth and sixth are theday.

E-date adjustmentThe revision of the effective date of the authorization document. During the course of activation, conversion, orreorganization, the MACOM, or proponent, may recognize that the approved e-date will cause a decrease in unit status.A new e-date will be recommended to HQDA. HQDA, on a case-by-case basis, issues authority to modify the e-date ofthose approved TAADS documents.

Emergency deployment readiness exerciseMinimum notice exercise to test unit deployment capabilities under contingency conditions.

Enhanced brigadeStandardized design of enhanced armor, mechanized, or infantry brigades as well as armored cavalry regiments.Enhanced brigades contain robust CS/CSS that allows easy integration into existing corps or division support structure.C4I systems are compatible and interoperable with corps and division systems. The enhanced brigade is capable offunctioning as part of a division or a separate brigade within the corps.

Equipment mission capableA logistic indicator that portrays how well a unit is maintaining that portion of its on-hand equipment that is both unitstatus and maintenance reportable. For USR reporting purposes, fully mission capable (FMC) equates to equipmentmission capable.

Equipment-on-handA logistic indicator depicting the organization’s fill of unit status reportable equipment. EOH is computed bycomparing reportable equipment on hand to wartime requirements.

Equipment serviceabilityA logistic indicator that portrays the combined impact of equipment shortages and maintenance shortfalls on a unit’sability to meet wartime requirements.

Equipment serviceability codeA one-digit code explaining an item’s importance to a unit’s combat, combat support, or service support mission. Thecodes are assigned to items on modification tables of organization and equipment. Since equipment can serve differentpurposes, the same item may have a different code on like or different type units. Equipment serviceability codes arefurther defined in appendix B.

Field, alphabeticA left-justified data field in which alphabetic characters (A through Z), special characters, and embedded blanks can bereported, followed by trailing blanks.

Field, alphanumericA left-justified data field in which alphabetic characters (A through Z), special characters, numeric characters, andembedded blanks can be reported, followed by trailing blanks.

Field, numericA right-justified data field in which Arabic numerals 0 through 9 can be reported, preceded by leading zones.

Full METL proficiencyThe unit training condition where each METL task can be performed to standard by the unit, and only sustainment

135AR 220–1 • 15 November 2001

training is needed. Full METL proficiency is the benchmark from which the number of training days required for unittraining is measured. It is not a deployment standard or the criteria for the T–1 level.

General support forcesTraining, logistic, security, and other support activities of the CONUS base, field activities, administrative headquar-ters, and forces provided for peacetime-peculiar activities. They are identified in Department of the Army ForceAccounting System by a three-position force planning code beginning with a “C.”

Left-justifyTo position data within the space allocation so that the left data character occupies the left position of the field (alphaand alphanumeric).

Line item numberA six-position alphanumeric number that identifies the generic nomenclature of specific types of equipment. StandardLIN consists of one alpha position followed by five numeric positions. Standard LIN are assigned by Army MaterielCommand (AMC) and are listed in SB 700–20.

Loaded deployability postureAll equipment and accompanying supplies of a unit’s first increment is loaded aboard aircraft and/or ships andprepared for departure to a designated objective area. Personnel are prepared for loading on minimum notice.

Main bodyPrincipal part of a tactical command or formation. It does not include detached elements of the command, such asadvanced party or close-out party.

Maintenance significant item/materielAn end item, assemblage, component, or system for which the maintenance support concept envisions the performanceof corrective maintenance services on a recurring basis.

Major combat unitA division, separate brigade, or armored cavalry regiment.

Major United States Army Reserve CommandA general officer command that is directly subordinate to a numbered continental United States Army.

Military occupational specialtyThe grouping of duty positions requiring similar qualifications and the performance of closely related duties.

Military occupational specialty codeThe five-character code used to identify MOS, skill level, and special qualifications.

Military qualification standardsA three-phased series of manuals for officers (MQS I, Pre-commissioning; MQS II, Lieutenant; and MQS III, Captain)that state military tasks, skills, knowledge, and professional military education expected of an officer at these levels.MQS I, the pre-commission manual, is the same for all pre-commission programs; MQS II and III are branch andspecialty specific.

Mission capableThe time that a piece of equipment or system is fully mission capable or partially mission capable. Fully mission-capable equipment is fully mission capable when it can perform all of its combat missions without endangering thelives of crew or operators. The terms “ready,” “available,” and “full mission capable” are often used to refer to thesame status; equipment is on hand and able to perform its combat missions. Partially mission-capable systems andequipment are safely usable and can perform one or more, but not all, primary missions because one or more of itsrequired mission-essential subsystems are inoperative for lack of maintenance or supply. For unit status reportingpurposes, the Army uses only FMC time.

Mission-essential task listA list (in order of precedence) of combat, combat support, and/or combat service support tasks derived from the unit’sassigned wartime mission(s). The METL is the basis for a unit’s annual training plan.

136 AR 220–1 • 15 November 2001

mission-support TDYDuties that include meetings, conferences, staff visits, staff augmentation, and medical appointments.

MobilizationThe act of preparing for war or other emergencies through assembling and organizing national resources. It is theprocess by which the Armed Forces, or part of them, are brought to a state of readiness for war or other nationalemergency. This includes assembling and organizing personnel, supplies, and materiel for active military service,federalization of Reserve components, extension of terms of service and other actions necessary to convert to a wartimeposture.

Mobilization stationThe designated military installation (active, semi-active, or inactive) or mobilization center to which a Reservecomponent unit is moved for further processing, organizing, equipping, training, and employing after mobilization andfrom which the unit may move to its port of embarkation.

Modification table of organization and equipmentA modified version of a TOE that prescribes the unit organization, personnel, and equipment needed to perform anassigned mission in a specific geographical or operational environment. In most cases, modification of the TOE is notnecessary; however, an MTOE is required to designate the authorized level of organization and provide other data suchas unit designation and effective date.

MOS diversion (MD)Personnel who are not available for deployment with their assigned units to meet wartime mission requirements inaccordance with the personnel availability criteria established in appendix D of this regulation. For USR purposes, thedetermination of a soldier’s availability is linked directly to the wartime mission requirements of his/her unit ofassignment and may not correspond to the soldier’s availability status for peacetime deployments based on administra-tive/personnel policy guidelines.

Non-available daysUsed in assessing the ability of equipment to perform its combat or combat support job. Non-available days are thedays the equipment was not able to perform its mission, the time the equipment is not mission capable.

Not mission capableEquipment that cannot perform one or more of its combat missions.

Not mission capable maintenanceEquipment that cannot perform its combat mission because of maintenance work that is needed or under way.

Not mission capable supplyEquipment that cannot perform its combat mission because of awaiting parts/supplies or a supply shortage.

Operating tempo (OPTEMPO)The annual operating miles or hours for the major equipment system in a battalion-level or equivalent organization.OPTEMPO is used by commanders to forecast and allocate funds for fuel and repair parts for training events andprograms.

Operations tempo (OPTEMPO)The rate at which units of the armed forces are involved in military activities, including contingency operations,exercises, and training deployments. (This definition of OPTEMPO is designated by Congress for the Annual DefenseReport.)

Pacing itemsMajor weapon systems, aircraft, and other items of equipment central to an organization’s ability to perform itsdesignated mission. These items are subject to continuous monitoring and management at all levels of command.Pacing items are identified in appendix C.

Parent unitIn MTOE units, a United States Army numbered unit of battalion or equivalent level. Also, unnumbered company,battery, troop, platoon, detachment, or team that is not an organic element of a battalion. Note that certain split units

137AR 220–1 • 15 November 2001

are treated as parent units for documentation in TAADS. TDA units are organized under a TDA with a unique TDAnumber assigned by DA, which includes TDA augmentation to an MTOE unit.

Peacetime operational deploymentFor USR purposes, peacetime operational deployments requiring a PCTEF report are those involving the movement ofan Army reporting unit or its reportable subordinate elements away from their home station(s) to accomplish opera-tional requirements as directed by a higher headquarters. Peacetime operational deployments encompass broad missiontypes such as small-scale contingencies (SSC), military operations other than war (MOOTW), and stability and supportoperations (SASO) and include a wide range of activities, such as peacekeeping, humanitarian relief, and support tocivil authorities. They do not include unit deployments to accomplish training or to participate in training exercises.

Personnel lossesActual losses to a reporting unit. Intra-command losses are not included. For example, losses to subordinate units thatdo not result in a loss to the reporting command are not counted as personnel losses.

Personnel tempo (PERSTEMPO)The amount of time members of the armed forces are engaged in their official duties, including official duties at alocation or under circumstances that make it infeasible for a member to spend off-duty time in the housing in which themember resides when on garrison duty at the member’s permanent duty station.

Possible daysThe number of calendar days an item was on hand—on the property book—during the DA Form 2406 report period.For an item you received during the reporting period, count the first day it was on-hand as a whole possible day. Donot count the last day an item is on hand—the day you lost it from your property book—as a possible day.

Port of embarkationA marine or air terminal at which troops, units, military sponsored personnel, unit equipment, and materiel board and/or are loaded aboard ships or aircraft as part of a deployment operation.

Professional filler system (PROFIS)The system designed to assign/attach active duty AMEDD personnel to Active Army mobilization table of organizationequipment required positions that are not authorized or not normally filled in accordance with AR 601–142.

ReadinessThe ability of U.S. military forces to fight and meet the demands of the National Military Strategy. Readiness is thesynthesis of two distinct, but interrelated levels: unit readiness and joint readiness. Unit readiness is the ability toprovide capabilities required by the combatant commanders to execute their assigned missions. This is derived from theability of each unit to deliver the outputs for which it was designed. Joint readiness is the combatant commander’sability to integrate and synchronize ready combat and support forces to execute his or her assigned missions.

Required columnThat portion of a unit’s TOE/MTOE/TDA that designates what personnel and equipment are necessary to meet fullwartime requirements.

Reserve componentAs used in this regulation, applies to ARNGUS and USAR units.

Reserve component on extended active dutyA Reserve component organization ordered to extended active duty rather than a short training tour or duty for alimited purpose—for example, to assist in quelling a civil disorder or to assist in disaster relief.

Senior gradeA personnel indicator that compares the available enlisted personnel (in grades SGT through CSM) and officers to fullwartime requirements.

Skill qualification testA performance-oriented test normally consisting of a hands-on component, job site component, and a skill component.The test measures individual proficiency in performing critical tasks related to the soldier’s primary MOS. Resultsprovide the basis for remedial individual training.

138 AR 220–1 • 15 November 2001

Special dutyThe performance of duty with an organization other than the unit to which assigned, while continuing to beadministered and accounted for by the unit of assignment. SD includes borrowed military manpower and troopdiversions.

Special operations forces groups, regiments, and commandsActive and Reserve special forces groups, psychological operations groups, special operations aviation regiments,Ranger regiments, and civil affairs commands.

State adjutant generalAn individual appointed by the governor of a State to administer the military affairs of the State. A State adjutantgeneral may be federally recognized as a general officer of the line provided he or she meets the prescribedrequirements and qualifications. However, he or she may be federally recognized as a general officer, Adjutant GeneralCorps, for tenure of office.

State area commandA mobilization entity within each State and territory that may be ordered to active duty when Army National Guardunits in that State or territory are alerted or mobilized. The STARC provides for command and control of mobilizedArmy National Guard of the United States units from home station until arrival at mobilization station. It is alsoresponsible for planning and executing military support for civil defense and land defense plans under the respectivearea commander. It also provides assistance to military family members.

Substitution itemAn item authorized for issue and considered acceptable for unit status reporting instead of a required standard item oflike nature and quality. SB 700–20 identifies items and procedures for making substitutions.

T–DaysThe unit status level determined by the number of training days required by the unit to achieve full METL proficiency.

T–Pre MobThe unit status determined by designated RC units to indicate the level of training proficiency achieved for pre-mobilization training requirements.

T–METLThe unit status level determined by the percentage of the METL trained by the unit to standard. The methodology todetermine the T–METL weights the assessments of individual tasks so that tasks determined to “need practice“ or to be“untrained“ receive relative value.

T–NBCThe unit status level determined by the number of training days required for NBC training to achieve or sustain fullMETL proficiency.

Table of distribution and allowanceTDA units are basically non-deployable units organized to fulfill missions, functions, and workload obligations of afixed support establishment in CONUS or overseas. TDA units are uniquely developed to perform a specific supportmission. They usually include civilian manpower, but an MTOE unit generally will not.

TDA augmentation documentAn augmentation TDA prescribes the additional organizational structure, personnel, and equipment needed to supportan added non-TOE mission assigned to an MTOE unit. An augmentation TDA may include civilian positions.

Table of organization and equipmentA table which prescribes the normal mission, organizational structure, and personnel and equipment requirements for atactical military unit, and is the basis for authorization documents.

TOE/MTOE, fullThe full strength and equipment of D and E series TOE; level 1 strength and equipment of G and later series TOE; andrequired column strength and equipment for units organized under MTOE. For TOE organizations, additions providedby TDA for non-TOE missions are excluded from the computation of full TOE. For units organized under type Bcolumns of TOE, the type B column is treated as full TOE/MTOE. For units organized under cadre columns of TOE,

139AR 220–1 • 15 November 2001

the cadre column is treated as full TOE/MTOE. For TDA organizations designated to report organization status, therequired column is treated as full TOE.

The Army Authorization Documents Systems—RedesignAn automated system that supports and centralizes the control of the development and documentation of organizationalstructures. It also supports requirements and authorizations for personnel and equipment needed to accomplish theassigned missions of Army units.

Training level (T-level)The overall unit training level indicating the degree of unit training proficiency in the wartime tasks for which the unitwas organized and designed. The T-level is measured against the unit’s all-inclusive training requirements to achieve orsustain full METL proficiency. It incorporates the unit’s pre-mobilization training requirements and NBC trainingrequirements, if applicable.

Troop diversionUse of soldiers, that does not meet the definition of borrowed military manpower, to perform recurring duties with anorganization or unit other than that to which they are assigned while continuing to be administered and accounted forby the unit of assignment.

Type B unitsType B MTOE units are configured to conserve U.S. Army manpower by substituting non-U.S. personnel in specifiedpositions of selected (generally combat service support; for example, terminal transfer units) MTOE. Units organized atlevel B of the TOE will be authorized level B equipment, as adjusted by force structuring constraints.

Unit identification codeA 6-character code assigned to a specific unit that can be used to identify that unit.

Unit readinessThe ability of a unit to perform as designed.

Unit statusThe measured resource/status levels in a unit at a specific point in time.

Wartime requirementsDoctrinally established requirements needed by type units to fully perform as designed and as part of the total force.The organization design (level 1) establishes wartime required fill levels for personnel and equipment.

Section IIISpecial Abbreviations and Terms

ABNairborne

ACActive component

ACRarmored cavalry regiment

ADPautomatic data processing

ADPEautomatic data processing equipment

ADRAnnual Defense Report

AEauxiliary equipment

140 AR 220–1 • 15 November 2001

AEPSArmy electronic product support

AGadjutant general

AGRActive Guard/Reserve

ALDavailable to load date

ALMParmy language master plan

AMOPSArmy Mobilization and Operations Planning System

AMOSCadditionally awarded military occupational specialty code

AMSSArmy Materiel Status System

ANassigned, not joined

AOCarea of concentration

AORarea of responsibility

APERTpersonnel turnover percentage

APCarmored personnel carrier

APSArmy pre-positioned stocks; Army pre-positioned sets

ARMSArmy Readiness Management System

ARSOFArmy special operations forces

ASASAll-Source Analysis System

ASEadministrative support equipment

ASORTSArmy Status of Resources and Training System

ASPERassigned strength percentage

141AR 220–1 • 15 November 2001

AVPERavailable strength percentage

AWAWOL category of personnel non-availability report

BCBradley commander

BDEbrigade

BMMEborrowed military manpower end

BMMSborrowed military manpower start

BNbattalion

BSFVBradley Stinger fighting vehicle

C4Icommand, control, communications, computers, and intelligence

CAcivil affairs

CARChief, Army Reserve

CATScombined arms training strategy

CBDRTchemical/biological defense resources and training

CCNUMcommand and control number

CDcommander’s discretion category of personnel non-availability report

CEVcombat engineer vehicle

cfmcubic feet per minute

CJCSChairman of the Joint Chiefs of Staff

CJCSICJCS Instruction

CJCSMCJCS Manual

142 AR 220–1 • 15 November 2001

CMDcommand

COconscientious objector category of personnel non-availability report

COMPOcomponent

COMSECcommunications security

CNGBChief, National Guard Bureau

CONUScontinental United States

CONUSAthe numbered armies in the Continental United States

COSCOMCorps Support Command

CPXcommand post exercise

CRcommander’s restriction category of personnel non-availability report

CRSChairman’s Readiness System

CSAChief of Staff, Army; also combat support agency

CTAcommon table of allowances

CTRcenter

cycubic yard; also calendar year

DARTdocumentation assistance review team

DCSINTDeputy Chief of Staff for Intelligence

DCSPRODeputy Chief of Staff for Programs

DCSLOGDeputy Chief of Staff for Logistics

DCSOPSDeputy Chief of Staff for Operations and Plans

143AR 220–1 • 15 November 2001

DCSPERDeputy Chief of Staff for Personnel

DECONdecontamination equipment category of NBC equipment report

DEPMEDSdeployable medical system

DEPTEMPOdeployment tempo

DESdistribution execution system

det/DETdetachment/detection equipment category of NBC equipment report

DETCdisplaced equipment training centers

DISCOMdivision support command

dpdeployed category of personnel non-availability report

DNdental category of personnel non-availability report

DRBdivision ready brigade

DUICderivative unit identification code

EDREemergency deployment readiness exercise

EMCequipment mission capable

ENengineer

EODexplosive ordnance disposal

ESequipment serviceability

EXEVALexternal evaluation

FMfrequency modulated; also family care plan category of personnel non-availability report

FMBBForce Management Bulletin Board

144 AR 220–1 • 15 November 2001

FMCCfully manned and combat capable

FMMPforce modernization master plan

FMQfully manned and qualified

FMUfully manned/unqualified

FORSCOMUnited States Army Forces Command

FOUOfor official use only

FSBForward Support Battalion

FSIForeign Service Institute

FSPforce support package

FTXfield training exercise

GCSSGlobal Command and Control System

GENTEXTgeneral text

GMTGreenwich mean time

GPSglobal positioning system

GRPgroup

GSORTSGlobal Status of Resources and Training System

HFhigh frequency

HIVhuman immunodeficiency virus

HMMWVhigh mobility multipurpose wheeled vehicle

HOhospitalized/convalescent leave category of personnel non-availability report

145AR 220–1 • 15 November 2001

HTHIV testing category of personnel non-availability report

hvyheavy

IFFidentification, friend or foe

ILRInteragency Language Roundtable

IMCSRinstallation materiel condition status report

IMSAinstallation medical supply activity

INInfantry

INGinactive National Guard

IOCinitial operational capability, Industrial Operations Command

JANAPjoint Army-Navy-Air Force publication

JSCPJoint Strategic Capabilities Plan

JSTARJoint Surveillance Target Attack Radar System

LALautenberg Amendment category of personnel non-availability report

LACVlight amphibious cargo vehicle

LADlatest arrival date

ldrleader

LETlight equipment transport

LFXlive fire exercise

LOGSAUSAMC Logistic Support Activity

LPlegal processing category of personnel non-availability report

146 AR 220–1 • 15 November 2001

LTlight, leave/TDY category of personnel non-availability report

MATESmobilization and training equipment site

MCSRmateriel condition status report

MEDmedicaments category of equipment of NBC equipment report

MEDEVACmedical evacuation

MCmission capable

MDMOS diversion

MESmedical/dental equipment set

METmedium equipment transport

METLmission essential task list

MFOmulti-national force observer

MIMilitary Intelligence

MITTmobile integrated tactical terminal

MLRSmultiple launch rocket system

MMCMateriel Management Center

MMCCminimally manned and combat capable

MMDFmaintenance master data file

MMRBMOS medical retention board

MMUminimally manned/unqualified

MOAmemorandum of agreement

147AR 220–1 • 15 November 2001

MODSMedical Occupational Data System

MOOTWmilitary operations other than war

MOPmemorandum of policy

MOSmilitary occupational specialty

MOSQmilitary occupational specialty qualified

MOUmemorandum of understanding

MPMilitary Police Corps, missing/prisoner of war category of personnel non-availability report

MRSAmateriel readiness support activity

MSBmain support battalion

MSCmajor subordinate command

MSPERmilitary occupational specialty qualified percentage

MTFmessage text format

MUSARCMajor United States Army Reserve Command

NAnon-applicable

NAADNational AMEDD Augmentee Detachment

NARRnarrative

NBCEQPTnuclear, biological, chemical equipment

NCANational Command Authority

NCSnet control station

NGBNational Guard Bureau

148 AR 220–1 • 15 November 2001

NMCSnot mission capable supply

NMSnational military strategy

NRLINnon-reportable line item number

NTCNational Training Center

NTCInon-type classified items

NVSnight vision sight

OADRoriginating agencies determination required

OCONUSoutside continental United States

OPoperating level

OPIoral proficiency interview

OPLANoperations plan

OPNSoperations

OPREDoperational readiness

OPTEMPOoperating tempo; also operations tempo

OTother (non-deployable report)

PCNpersonnel control number

PCSpermanent change of station

PCTEFpercent effective

PERLpre-positioned equipment requirement list

PERSTEMPOpersonnel tempo

149AR 220–1 • 15 November 2001

PGpregnancy category of personnel non-availability report

PHparenthood category of personnel non-availability report

PIpacing item

PLDCprimary leader development course

PMCIpartially manned/combat ineffective

PMOSprimary military occupational specialty

POEport of embarkation

POLpetroleum, oils, and lubricants

PPP3/P4 profile category of personnel non-availability report

PRCpresidential Reserve call-up

PROFISprofessional filler system

PSYOPSpsychological operations

pubpublication

PWEprimary weapons and equipment

RADradiological detection equipment category of NBC equipment report

RATTradio teletypewriter

RCReserve component

RCHDReserve component hospital (DEPMEDS)

RDDrequired delivery date

REASNreason

150 AR 220–1 • 15 November 2001

RECAPrecapitulation

REQrequired

REQVALrequisition validation system

RGRRanger

RICDAeffective date of the report

RLreadiness level

RMKSremarks

RMTCregional medical training centers

RMTSregional maintenance training sites

RSOPreadiness standing operating procedure

RTSregional training site

RTS–MEDregional training site-medical

S2Intelligence Officer (U.S. Army)

S3Operations and Training Officer (U.S. Army)

SAMsurface-to-air missile

SAMASStructure and Manpower Allocation System

SASOsupport and stability operations

SATshort and can accompany troops

SATSstandard Army training system

SBsupply bulletin

151AR 220–1 • 15 November 2001

SDTOTALspecial duty total

SECRNsecondary reason

SGPERsenior grade percentage

SKIspecial skill identified

SKOsets, kits, or outfits

SLsafety level

SMsimultaneous membership program category of personnel non-availability report

SMOSCsecondary military occupational specialty code

SMPsimultaneous membership plan

SOCOMSpecial Operations Command

SOFspecial operations forces

SORTSstatus of resources and training system

SOT–Aspecial operations team-alpha

SRSA–EUstrategic reserve storage activity—Europe

SRCstandard requirement code

SSCsmaller scale contingency

S&Ssupply and service

STARCState Area Command

STRACstandards in weapons training

TAACTheater Army Automation Center

152 AR 220–1 • 15 November 2001

tbdto be determined

TCtransportation corps; tank commander; also temporary change of station category for personnel non-availability report.

TCStemporary change of station

TDAtable of distribution and allowances

TDYtemporary duty

TERRNtertiary reason

TFtask force

TLRPtraining level review process

tm/TMteam; also technical manual

TMLterminal

TMTtransportation motor transport

TNtraining

TOEtable of organization and equipment

TPtemporary profile category of personnel non-availability report

TPPtotal points possible

TPFDDtime-phased force deployment data

TPFDLtime-phased force deployment list

TRADOCUnited States Army Training and Doctrine Command

TRCtraining readiness condition

TSOPtactical standing operating procedure

153AR 220–1 • 15 November 2001

TTteletypewriter

TT-leveltraining tempo level

UICunit identification code

UNMANunmanned

UPunsatisfactory participation/performance category of personnel non-availability report

USACAPOCUnited States Army Civil Affairs And Psychological Operations Command

USAFMSAU.S. Army Force Management Support Agency

USAJFKSWCSUnited States Army John F. Kennedy Special Warfare Center and School

USAMCUnited States Army Materiel Command

USAMMAUnited States Army Medical Materiel Activity

USAMMCEUnited States Army Medical Materiel Center Europe

USASFCUnited States Army Special Forces Command

USASOCUnited States Army Special Operations Command

USMTFUnited States message text format

USP&FOUnited States Property and Fiscal Officer

WWMCCSWorldwide Military Command and Control System

154 AR 220–1 • 15 November 2001

UNCLASSIFIED PIN 999999–999

USAPAELECTRONIC PUBLISHING SYSTEMOneCol FORMATTER .WIN32 Version 166

PIN: 999999–999DATE: 11-20-01TIME: 13:08:47PAGES SET: 160

DATA FILE: C:\wincomp\r220-1.filDOCUMENT: AR 220–1DOC STATUS: REVISION

Date post:	19-Oct-2018
Category:	Documents
Upload:	voquynh
View:	219 times
Download:	0 times