Army Pamphlet 220-1

16 November 2011

UNCLASSIFIED

Field Organizations

Defense Readiness Reporting System-Army Procedures



SUMMARY

DA PAM 220-1
Defense Readiness Reporting System-Army Procedures

This new publication, dated 16 November 2011-

* Consolidates the basic processes and general procedures previously explained in AR 220-1 and AR 220-20 into one publication governing the Defense Readiness Reporting System-Army (throughout).

* Contains extensive new and updated information regarding how the commander's unit status report is prepared, reviewed, and submitted and how force registration actions are accomplished (throughout).



Part One

DRRS-Army Overview

Part One of this pamphlet provides an overview of the Defense Readiness Reporting System-Army (DRRS-Army), explaining key references, lexicon, and system components. Chapter 1 explains the purpose of the pamphlet and addresses the key references, abbreviations, and terminology. Chapter 2 describes each of the DRRS-Army components and explains how DRRS-Army functions.

Part One of this pamphlet provides an overview of the Defense Readiness Reporting System-Army (DRRS-Army), explaining key references, lexicon, and system components. Chapter 1 explains the purpose of the pamphlet and addresses the key references, abbreviations, and terminology. Chapter 2 describes each of the DRRS-Army components and explains how DRRS-Army functions.

Chapter 1

Introduction

1-1. Purpose

a. This Department of the Army pamphlet (DA Pam) explains and documents the basic processes and general procedures for Army unit status reporting and force registration. In conjunction with the supporting software application, the applicable User's Guide or Training Support Package, and online user reference materials, it provides the instructions and reference data necessary to carry out the policies established in AR 220-1 and supported by the DRRS-Army family of systems. Specifically, this DA Pam explains and documents the basic processes and general procedures for the following:

(1) Preparing and submitting the commanders unit status report (CUSR) (see part two ).

(2) Developing, reporting and updating force registration data (see part three ).

(3) Accessing information and data contained in the DRRS-Army database (see para 2-5 and chap 13 ).

(4) Classifying, downgrading, declassifying, and releasing DRRS-Army data (see chap 13).

(5) Determining the equipment on-hand status by component and by state or territory (see app E ).

(6) Accessing and using the online reference tables containing the codes authorized for use in the DRRS-Army database (see app I ).

b. While this publication explains and documents the basic processes and general procedures used by unit commanders and unit readiness officers who prepare and submit the CUSR and by unit identification code information officers (UICIOs) and force management officials who register units in the DRRS-Army database and update force registration data, AR 220-1 is the authoritative publication for unit status reporting and force registration policy. To enhance the utility of this publication to its intended users, selected policy provisions that are established in AR 220-1 are replicated in this publication. However, in the event that any provisions in this DA Pam conflict with those in the latest edition of AR 220-1, the provisions in AR 220-1 will take precedence. Additionally, this DA Pam is not intended to provide detailed instructions for every DRRS-Army data entry option or requirement; therefore, it must be used in concert with the supporting DRRS-Army software applications, the applicable User's Guide, Training Support Package, online tutorials and/or other user assistance materials that are available at or linked to the DRRS-Army portal.

c. Because much of the tabular reference data associated with unit status reporting and force registration falls under the purview of external agencies and, therefore, is subject to frequent revision and update, many reference tables are established and will be maintained solely at the DRRS-Army portal. Where so indicated, any updates or changes to the information and tabular data contained in this publication will be announced at the DRRS-Army portal, and the revised or updated information will be posted there, in advance of a formal revision to this publication. (See para 2-8 ).

1-2. References

Required and related publications and prescribed and referenced forms are listed in appendix A .

1-3. Explanation of abbreviations and terms

Abbreviations and special terms used in this pamphlet are explained in the glossary .

Chapter 2

The Defense Readiness Reporting System-Army

2-1. Overview

The DRRS-Army is a family of systems that features new and more powerful software applications than those available in the previous unit status reporting system-the Army Status of Resources and Training System (ASORTS). The DRRS-Army was developed by the Army Readiness Division (DAMO-ODR), Headquarters (HQDA), Deputy Chief of Staff, G-3/5/7 ( DCS, G-3/5/7 ) to accommodate the ongoing development of and Army compliance with readiness status reporting and force registration requirements established by the Office of the Secretary of Defense (OSD) and the Chairman, Joint Chiefs of Staff (CJCS) pursuant to their authorities and responsibilities under various provisions of Title 10, U.S. Code (10 USC ). Additionally, DRRS-Army was developed to provide the readiness status reporting and force registration capabilities necessary to support the ongoing implementation of Army Force Generation (ARFORGEN) concepts and supporting processes for manning, equipping, training Army units for progressive readiness to conduct full spectrum operations across the spectrum of conflict. The key components of DRRS-Army are the DRRS-Army database, the Net-centric Unit Status Report (NetUSR) application, the Force Registration application, the Force Projection application, the Army Readiness Management System (ARMS) application, the Ad Hoc Query tool, and the DRRS-Army Portal.

2-2. The Defense Readiness Reporting System-Army Database and Defense Readiness Reporting System-Army System Architecture

a. General. The DRRS-Army database formally replaced the ASORTS database as the Army's official unit status reporting database and the authoritative database of record and central registry for all approved Army units, organizations and installations. The DRRS-Army database is the Army's counterpart to the Global Status of Resources and Training System (GSORTS) database, established by the Joint Staff and maintained for it by the Defense Information System Agency (DISA). GSORTS is an automated Department of Defense (DOD) system used to provide the Secretary of Defense (SECDEF), CJCS, and other senior DOD officials with authoritative identification, location, and resource information on DOD units/organizations. GSORTS provides monitoring information to the National Military Command System. The Chairman Joint Chiefs of Staff Instruction ( CJCSI ) 3401.02 series and the Chairman, Joint Chiefs of Staff Manual ( CJCSM ) 3150.02 series provide guidance to all service headquarters regarding requirements for reporting the status of resources and training in its units to GSORTS. Department of Defense Directive ( DODD ) 7730.65 and various follow-on publications and memorandums promulgated by the Under Secretary of Defense for Personnel and Readiness (USD, P&R) establish and provide guidance to implement the DRRS-Enterprise a collaboration of independent service, joint and OSD readiness-focused information technology (IT) applications, combined with readiness-specific authoritative data, all related by a common ability to support readiness reporting and assessment requirements. The DRRS-Army updates GSORTS and supports the DRRS-Enterprise by providing the relevant information reported by Army units, to include the unit commander's measurements and assessments regarding the unit's ability to accomplish its core functions and provide designed capabilities and, when applicable, unit readiness for assigned missions. The authoritative DRRS-Army database resides at HQDA, United States Army Command and Control Support Agency (USACCSA), as do the associated reference files.

b. System Architecture. During FY07 at its initial operational capability, DRRS-Army consisted of NIPRNet and SIPRNet Web servers that were linked to a DRRS-Army database server, a large number of NIPRNet and SIPRNet standalone work stations for data providers, and authoritative databases for personnel data, logistics data, training data, and other data. Subsequently, distinct software applications have been developed; Web services have been enhanced; and additional authoritative data sources (ADS) have been linked to the system. The DRRS-Army system architecture will continue to evolve to keep pace with emerging requirements and advancing technology. Figure 2-1 illustrates the current DRRS-Army system architecture.



Figure 2-1. DRRS-Army System Architecture


c. Concept of operations for the DRRS-Army database. The DRRS-Army is a mission application of the Global Command and Control System (GCCS) that supports the DRRS enterprise, processes Army data to GSORTS and provides access by Army organizations to GSORTS data. The NetUSR application, the Force Registration application and the ARMS application are powerful software applications that support data entry requirements and facilitate data analysis while providing complete and accurate validation capabilities. The primary sources of data are the reporting units and the UICIOs and force management officials at Army installations and commands. Part Two of this publication explains the procedures for preparing and submitting the CUSR into the DRRS-Army database using the NetUSR application. Part Three explains the procedures for registering units and entering basic identify data element (BIDE) and Army basic identity data element (ABIDE) into the DRRS-Army database via the Force Registration application.

d. Authoritative data sources. There are several ADS that provide information and data to the DRRS-Army database. This information and data provide the basis for the assessments, measurements and data points in the CUSR and/or support the force registration process.

(1) The ADS from which the NetUSR application currently imports information and data into DRRS-Army are explained in paragraph 2-3 .

(2) While NetUSR does not currently import any data from the following data sources, data from these sources is entered into the DRRS-Army database via other means.

(a) Mobilization and deployment.The Mobilization and Deployment Information System (MDIS) and Department of the Army Mobilization Processing System (DAMPS) are internal mobilization databases owned by DCS, G-3/5/7 (DAMO-ODO and DAMO-ODM, respectively). They are managed internally by USACCSA.

(b) Installation status report database.The installation status report (ISR) database was established by the Assistant Chief of Staff for Installation Management (ACSIM)/Installation Management Command (IMCOM) to accommodate installation readiness reporting requirements that were established by OSD serial guidance memorandum #3. The ISR database contains authoritative data on installation mission essential tasks (IMETs) and other data fields from the ISR.

(3) Potential future data sources.

(a) Digital Training Management System.The DCS, G-3/5/7 (DAMO-TR) provides Army Staff (ARSTAF) oversight for this database, and is maintained by the Training and Doctrine Command (TRADOC) Combined Arms Center (CAC) Collective Training Directorate (CTD). Commanders are expected to use this system to update and maintain their training status data, to include the mission essential task list (METL) assessments that are required for reporting by AR 220-1 .

(b) Total Ammunition Management Information System - Redesigned.DCS, G-3/5/7 (DAMO-TR) provides staff oversight for this database, and it also is maintained by DCS, G-3/5/7 (DAMO-TR).

e. Access and registration. See the DRRS-Army portal.

2-3. Net-centric unit status report application

a. Purpose. The net-centric unit status report (NetUSR) application is the Web-based readiness status data input tool that supports the user requirements to implement the Army's unit status reporting process.

b. General nature of the software application. The NetUSR can import data from designated ADS, pre-populate selected data fields and then apply metrics and business rules to auto-calculate various measurements and assessments in support of unit status reporting requirements. The NetUSR replaced the Personal Computer-Army Status of Resources and Training System (PC-ASORTS) as the Army's official readiness reporting status data input tool in October 2006.

c. Authoritative Data Sources for the Net-centric Unit Status Report Application.

(1) Force Management System Web. The DCS, G-3/5/7 (DAMO-FM) provides staff oversight for this database, and it is maintained by the United States Army Force Management Support Activity (USAFMSA), a field operating agency of DAMO-FM. The NetUSR imports modification table of organization and equipment (MTOE) and table of distribution and allowances (TDA) data from this ADS. The FMSWeb also is the source for other information related to the personnel and equipment requirements, authorizations, and exemptions applicable to reporting units. AR 71-32, is the authoritative publication governing Army force management.

(2) Integrated Total Army Personnel Database. The Deputy Chief of Staff, G-1 ( DCS, G-1 ) provides staff oversight for ITAPDB, and this integrated database is maintained by the Human Resources Command (HRC). The NetUSR imports personnel status data from this ADS, to include information indicating the specialty, grade, position, and training status of individual Soldiers. AR 600-8-104 is the authoritative publication governing ITAPDB.

(3) Medical Operational Data System. The Office of the Surgeon General (OTSG) is the proponent for Medical Operational Data System (MODS) which is the authoritative database for the medical readiness information of Army personnel. The Medical Protection System (MEDPROS) is the Web module to MODS and is the primary tool to record, track, and report the medical readiness for Soldiers and units. NetUSR imports the medical readiness codes for individual Soldiers from MODS. AR 40-501 , is the authoritative publication governing the medical fitness standards reported into MODS via MEDPROS.

(4) Logistics Information Warehouse. The Deputy Chief of Staff, G-4 ( DCS, G-4 ) provides staff oversight for this database, and it is maintained by the Army Materiel Command's (AMC) Logistics Support Agency (LOGSA). The LIW updates and refines property book data received from the Property Book Unit Supply Enhanced (PBUSE). NetUSR imports property accountability data from LIW. AR 710-3 , is the authoritative publication governing the LIW.

(5) The current net-centric unit status report data sources are illustrated in figure 2-2.



Figure 2-2. Authoritative data


d. Access and registration.

(1) General. The ACOMs, ASCCs, DRUs, and Director, Army National Guard (DARNG)/Chief, National Guard Bureau, in coordination with IMCOM, if appropriate, will specify to HQDA (DAMO-ODR) the officials authorized to register NetUSR users for their subordinate organizations. Officials authorized to accomplish user registrations may include readiness officers, UICIOs (coordination with IMCOM is required for installation UICIOs), force managers, and so forth. Commanders of reporting units are required to formally designate to these authorized officials those personnel in their units who are authorized to register for the NetUSR user accounts available for their units. NetUSR user accounts allow system access and enable authorized users to import status data on the associated units from authoritative Army databases and to report readiness and capability assessments in the CUSR on behalf of the unit commander. Authorized officials with administrative privileges will register the NetUSR users designated by the unit commander. Administrative control (ADCON) authorities will provide management oversight of NetUSR user registration via ADCON channels. HQDA (DAMO-ODR) will monitor user registrations and audit user activity to ensure that management controls are effective.

(2) Procedures. The procedures for NetUSR registration are explained in the NetUSR Users Guide and also in the "user management" section of the software application. There are four levels and types of NetUSR registration that are available. Distinct criteria and access privileges are associated with each level and type.

(a) Level 1.NetUSR user (includes unit commanders and unit readiness officers).

(b) Level 2.Senior readiness officer (SRO) (includes designated readiness management officials at ACOMs, ASCCs, DRUs, DARNG/National Guard Bureau (NGB), installations, garrisons, and HQDA agencies).

(c) Level 3.Special SRO (includes designated readiness management officials at HQDA and selected ACOMs, ASCCs, and HQDA agencies (Department of Army Staff Agency (DASAs).

(d) Level 4.Senior administrator (includes designated administrators and management officials at HQDA).

2-4. The force registration application

a. Purpose. The force registration application is a Web-based force management data input tool that supports the user requirements to implement the Army's force registration process.

b. General nature of the software application. The Force Registration application enables Army force management officials and UICIOs to register currently existing and approved Army organizations and update BIDEs in the DRRS-Army database. During fiscal year 08 an improved force registration application replaced the BIDE entry tool that was available in PC-ASORTS.

c. Access and registration. See the DRRS-Army portal.

2-5. The Army Readiness Management System application

a. Purpose. The ARMS application is the official DRRS-Army business intelligence tool that provides visibility to selected Army readiness status and force registration data and information contained in the DRRS-Army database. It facilitates the detailed analysis of readiness trends and force registration issues. Via this Web browser, any approved SIPRNet user can gain access to the same readiness information that is available to action officers in the Army Readiness Division (DAMO-ODR) at HQDA who accomplish readiness data analysis and brief the senior Army leadership at the monthly Strategic Readiness Update (SRU).

b. General nature of software application. The ARMS operates as a Web browser application that can enable any approved SIPRNet user to have access to the same readiness information as action officers in the Army Readiness Division (DAMO-ODR) at HQDA. The ARMS Web browser application allows the user to view current, near real time, and historical information using graphical user interface screens to efficiently display information. The ARMS is an executive information system in that it begins at a summary level and allows a "drill down" to access detailed readiness information. This system displays comprehensive readiness information in the form of summary matrices and listings. The ARMS enables users to view the readiness of all Army reporting units at any point in time and it provides the ability to incorporate data queries directly into briefing products in MS-Word, MS-Excel, and MS-PowerPoint.

c. Army Readiness Management System Database. The ARMS database data has been extracted and formulated from the DRRS-Army database. The ARMS database is updated several times a day to capture reports as they come in to provide a "near real time" view of Army reporting units. The data refresh procedures support the Army functional area source data, both current and future data, and provides structures/views required for loading the Oracle system database.

d. Access and registration. To gain access to ARMS each user first must be approved by DAMO-ODR and then assigned an ARMS user ID and password. To request ARMS access, individuals should log on to the ARMS Web site (SIPRNet) and complete the online ARMS Access Request form or contact the ARMS POC in DAMO-ODR by e-mail or telephone. The request forms approved by DAMO-ODR will be stored in to the ARMS database. A military sponsor is required for all requests submitted by nonmilitary personnel.

e. Army Readiness Management System Web site and users guide. The ARMS Web site contains the ARMS Users Guide that provides step-by-step instructions for obtaining access to ARMS and explains the ARMS processing procedures. This Web site also includes online training modules and links to key references, manuals, and other training materials. The home page address is: http://aocpc2-arms.hqda.army.smil.mil/arms. (SIPRNet).

2-6. The Force Projection Application

a. Purpose. The Force Projection Application is the DRRS-Army software application that replaced the "Mobilization Operations Deployment/Employment Execution" (MOBODEE) system. While other commands with mobilization responsibilities are highly encouraged to use this application, it was designed for and is used primarily by the Force Command (FORSCOM), as the HQDA responsible agent for mobilization, deployment, redeployment, and demobilization planning and execution for the continental United States (CONUS), the Commonwealth of Puerto Rico, and the Virgin Islands.

b. General nature of the software application. This application provides information for the execution of mobilization in support of ongoing operations requiring the use of Reserve Component forces. Additionally, the Force Projection application provides data to support deployment operations to include validation requirements, strategic airlift schedules, and status of the deployment flow.

c. Access and registration. The procedures for using this application are published separately by FORSCOM and are not contained in this publication. Commands or agencies desiring to use the Force Projection application will coordinate directly with FORSCOM (AFOP-OCM) regarding access and registration.

2-7. The Ad Hoc Query Tool

a. Purpose. This DRRS-Army application allows users to query the DRRS-Army database.

b. General Nature of the Software Application. The Ad Hoc Query (AHQ) tool is a customized commercial off-the-shelf product that allows users to create custom queries and reports against data in the DRRS-Army database. The LogiXML Ad Hoc Reporting tool enables users to build custom queries that extract data from the database via a predefined set of functional groups (database views). The LogiXML Information reporting tool provides the capability to build reports.

c. Access and registration. See the DRRS-Army portal.

2-8. The Portal Application

a. Purpose. The Portal application provides a single sign-on enabled front-end to all DRRS-Army applications. Important planned or upcoming DRRS-Army events are announced at the Portal, to include new or updated reference tables and requirements to download, install and/or apply new patches or executable data files.

b. General Nature of the Software Application. Within the Portal, users have access to a number of "portlets" that provide high-level views into readiness data and key reference information. The "Announcements" section contains current announcements; the "Application Central" section contains links to all DRRS-Army applications; the "Resources" section contains the files currently available for downloading; the "Training Support" section contains user assistance materials, to include users guides, tutorials, FAQs, and instructions for access; and the "Help" section contains an adddress and toll free telephone contact information for the DRRS-Army Help Desk. The portlets are configurable by end users, allowing the most flexibility for the user community.

c. Access and registration.

(1) NIPRNET: https://netusr2.army.pentagon.mil.

(2) The secure internet protocol router network https://www.portal.drrsa.hqda.army.smil.mil.

(3) Check the NIPRNET, DCS, G-3/5/7 Army Readiness Portal, DAMO-ODR for any changes to the above address at https://g357.army.pentagon.mil/OD/ODR .

Part Two

Commander's Unit Status Reporting Procedures

Chapter 3

Overview

3-1. General instructions and criteria

a. Intent. The CUSR submitted in accordance with the provisions of AR 220-1 is intended to be a "commanders' report," reflecting the commander's personal judgments and assessments regarding the mission readiness of the unit. Accordingly, CUSRs are prepared by commanders or their designated representatives and are routinely submitted through ADCON channels to HQDA. The CUSR is not a performance report card and should not be used as a tool to evaluate or compare the accomplishments of organizations or those of their commanders. All commanders at all times are expected to submit timely, accurate and complete reports that neither exaggerate nor mask their units' readiness deficiencies. No commander is expected to report readiness levels that are inconsistent with resources made available to the unit. The ADCON authorities at higher levels will review reports to ensure that they comply with regulatory requirements.

b. Background and overview.

(1) The CUSRs are part of the Joint Staff's and OSD's readiness reporting systems. These systems establish criteria and guidelines that are standardized for all Services, to the extent possible. A major goal of these systems is to provide useful and accurate information to the combatant commanders (CCDRs) regarding the readiness status of the Army forces they will receive in theater, to include accurate measurements and assessments regarding their readiness to execute their assigned missions. The assigned mission level (A-Level), its associated metrics and mandatory comments are intended to support these information requirements (see para 3-5 ). The commander for each measured unit will continue to use the unit's core functions and designed capabilities and MTOE requirements as the basis for determining and reporting the C-Level, the measured area levels (PSRT) and for estimating required training days. The criteria and guidelines for determining and reporting the unit's readiness status for core functions or designed capabilities and assigned missions are fixed by Joint Chiefs of Staff (JCS), OSD, and Army policy and cannot be modified by subordinate units, organizations or commands without authorization.

(2) Accordingly, for CUSR purposes, when applicable, the determination of the C-Level and the measured area levels for personnel, equipment on-hand (available) and unit training proficiency will be accomplished only by measuring the current status of resources and training in the unit or organization against the unit's core functions or designed capabilities, and it will be based solely on the official structure established by the applicable formal requirements and authorizations document (MTOE or TDA) or, when these documents are not available and/or are not applicable, by force structure guidance issued by HQDA (DAMO-FMF) or the responsible Army command (ACOM)/Army service component command (ASCC)/direct reporting (DRU) and/or DARNG. To summarize, a unit's formally documented structure establishes the baseline for measuring its readiness and capability for its core functions or designed capabilities (units must use the same MTOE or TDA to determine requirements for both personnel and equipment) and the readiness and capability represented by the unit's currently effective task organization (includes organic units/elements that are not currently detached and any augmentations) are compared to this baseline (either objectively or subjectively) to assess and report the readiness status and capability for the unit's core functions or designed capabilities. If needed, commanders of reporting units should obtain guidance from their chain of command regarding their command authority over any augmentations or detachments.

(a) Additionally, when deployed as an ad hoc organization in support of current Army operational requirements (that is, an assigned mission), commanders of reporting units will continue to report (in the CUSR) the status of resources and training in their units and organizations measured against the requirements associated with the unit's core functions or designed capabilities based upon the formal requirements and authorizations document (MTOE or TDA). Ad hoc organizations are those forces/elements that have been tailored and oriented toward a specific contingency or current operational requirement. Even if the ad hoc entity is operating under a derivative unit identification code (DUIC) and is reporting its readiness status in accordance with DUIC reporting procedures, the status of resources and training also will be reported by the parent unit identification code (UIC) organization (the measured unit) from which the subordinate elements came and these reports will reflect the status of resources and training in the parent unit measured against the requirements associated with its core functions or designed capabilities. While organic elements are detached, the readiness of the parent units is degraded and the readiness levels reported by these parent units are expected to reflect this degradation.

(b) In accordance with the Army implementation of the CJCSI/CJCSM policy requirements, the C-Level reported in the CUSR is not used to indicate the reporting unit's ability to accomplish or sustain a currently assigned operational requirement. Commanders of reporting units focused on assigned missions will use the assigned mission level (A-level) data field and the supporting measurements (assigned mission manning {AMM} and assigned mission equipping {AME} levels) to report the readiness status assessments for their units' assigned missions in accordance with the provisions of AR 220-1 and appendix C of this publication. If the assigned mission requires and/or encompasses all of the unit's core functions and designed capabilities and replicates the associated conditions and standards, then the A-Level and the C-Level should be similar. See appendix C for details.

(3) As updates and changes to requirements and authorizations are published and provided to units, confusion often develops as to which requirements and authorization document (MTOE or TDA) the unit should use to calculate CUSR measurements. In general, reporting units will measure and report readiness status against their currently effective MTOE/TDA document. However, reorganizing units can report early against a future document if the unit more closely resembles that future document than the currently effective document, provided that the effective date (E-date) for the future document is within 1 year and the responsible ACOM, ASCC, DRU or (for nonmobilized Army National Guard (ARNG) units) DARNG, has specifically approved such action. Reporting units will not be approved to report early against a MTOE or TDA if the overall P-Level or S-Level would be degraded below P-3 or S-3 and the measured unit could report P-3 or S-3 or better under the currently effective document. Once a unit begins to report against a future MTOE or TDA (that is, in advance of the E-date), the previous document will not be used for further readiness status reporting unless specifically directed by the responsible ACOM/ASCC/DRU or DARNG. Additionally, units must use the same MTOE or TDA to determine their requirements for both personnel and equipment.

c. Use.

(1) The CUSR indicates the degree to which a unit or organization has achieved prescribed levels of fill for personnel and equipment, the operational readiness status of on-hand equipment, and the training proficiency status of the unit or organization. Accordingly, the CUSR is used by commanders at higher levels and senior Army leaders to synchronize operational planning and resource management. At HQDA and at ACOM/ASCC/DRU and/ or DARNG-level, CUSRs are used as the basis for resourcing requests and/or decisions. For joint planners and combatant commanders, the CUSR provides an important and uniform assessment regarding the ability of individual units and organizations to execute their core functions and provide the capabilities for which they are designed and, when applicable, the missions they have been assigned to plan, evaluate or prepare for, or that they have been formally ordered to execute and/or are currently undertaking. The commander's METL assessments in the CUSR are used by OSD for operational and resourcing decisions and to brief Congress using the three-tier (Y/Q/N) rating scale.

(2) In light of the reporting requirements established by Joint Staff (GSORTS) and OSD (DRRS), the Army requires additional data that increases the value of the CUSR as a resource management and operations tool for HQDA. The additional data required by the Army enables the commanders to more clearly portray the effects of resource application in their units, organizations and installations. The information and data contained in the CUSR enables commanders and staffs at all levels to analyze and address key unit status indicators. At the installation-level and below, the CUSR assists commanders in identifying resource shortfalls to facilitate cross-leveling actions, if appropriate, to alleviate the shortfall. Additionally, the CUSR provides information to HQDA that

(a) Assists in the portrayal of Armywide conditions and trends.

(b) Assists in the identification of factors that degrade the readiness status.

(c) Assists in the identification of resource shortfalls, if any, by comparing the actual levels of personnel and equipment assets in units and organizations with the requirements associated with the unit's core functions or designed capabilities that are established by the applicable formal requirements and authorizations documents (MTOEs or TDAs).

(d) Assists HQDA and intermediate commands in making resource allocation decisions.

(e) Informs senior decision makers' assessments regarding the employability and deployability of measured units.

d. Importance of commander comments.

(1) Precise and concise commander comments that describe the cause/effect relationship between resource deficiencies and overall unit readiness and capability are extremely important to explain or clarify any significant readiness issues. Commander comments are closely reviewed routinely by resource managers and senior leaders at higher headquarters, to include HQDA, to identify urgent concerns requiring immediate actions. See appendix H for illustrative examples.

(2) The commander of the reporting unit, organization, or installation is solely responsible for the accuracy of the information and data entered by his unit in the CUSR and for ensuring that resource deficiencies, if any, are clearly explained and are neither masked nor exaggerated.

e. Preparation, processing, and review.

(1) Commanders of the units, organizations, and installations that are required to report will use the NetUSR application to prepare the CUSR. Printed copies of NetUSR screens can be used for internal feeder reports and to preserve CUSR data in hard copy format for retention in unit files or for coordination. However, all CUSR data submitted by reporting units and organizations will be submitted electronically in the format generated by the NetUSR application. Reports are processed into the DRRS-Army database, which updates both Joint Staff and OSD systems and databases. The Global Status of Resources and Training System (GSORTS) is the authoritative Joint database of record used by the CJCS, the Joint Staff, the Services, the combatant commands, and the combat support agencies.

(2) Commanders of reporting units and organizations submit their CUSR information via ADCON channels that normally include the ACOM, ASCC, DRU, and, for ARNG/Army National Guard of the United States (ARNGUS) units that are not on active duty, the DARNG/NGB, through HQDA (DAMO-ODR) to the Joint Staff and OSD.

(3) The commander preparing the report must review the information and data applicable to his unit, organization or installation that is imported by the NetUSR application from official Army sources and databases (for example, personnel/human resource, medical, logistics, force management, and property accountability systems) and then report, in his judgment, the most accurate information and data in the CUSR. It is important to note that updated or corrected information and data reported into DRRS-Army via NetUSR by the commander does not update or correct that information residing with the official sources from which it was imported. While DAMO-ODR will notify official sources of potential data discrepancies identified via analysis of data reported by units via NetUSR, the commander is responsible to initiate appropriate actions using the process established by the official source to update or correct any discrepancies in the status information and data on his unit residing with that official source. Official sources for status information imported by NetUSR are identified and discussed in paragraph 2-2 .

(4) The NetUSR software application uses data downloads from Army authoritative data systems to enhance the accuracy of reports using the full report format (explained in para 3-2 ) and also to reduce the burden to reporting units. Accordingly, reporting units submitting reports that use the full report format must accomplish a current download of authoritative data using the DRRS-Army/NetUSR Web site when preparing their reports. This action ensures that accurate and current unit information from the authoritative data sources (for example, property, personnel and medical data, line item number (LIN) exemption data, and so forth.) is included in the CUSR. Therefore, all units preparing a CUSR that uses the full report format, regardless of COMPO, unit location or mobilization status, will accomplish an authoritative data extract not earlier than 15 days before the "as of date" of the report (RICDA). On a case-by-case basis when the extraordinary circumstances of specific units warrant such actions, the responsible ACOM, ASCC, DRU and DARNG/NGB (for ARNG units that are not on active duty status) are authorized to approve "non recurring" exceptions that expand the window for accomplishing an authoritative data extract for reports that use the full report format to not more than an additional 15 days (that is, the maximum period approved for expanding this window cannot be more than 30 days before the RICDA). The approving authority will notify HQDA (DAMO-ODR) regarding any exception approved for a reporting unit that is on active duty status (that is, a COMPO 1 or mobilized Reserve Component (RC) unit) prior to submitting the unit's report to HQDA. Note that DDRS-Army software will auto-reject any report that indicates the authoritative data supporting the report was downloaded earlier than 30 days before the RICDA. The ADCON authorities at higher levels will provide the necessary USR management oversight to ensure compliance with these data downloading requirements. Also note that units currently deployed outside continental United States (OCONUS) to accomplish operational requirements are authorized to use the abbreviated (short form) deployed report that does not require the unit to download an authoritative data extract.

3-2. Report formats, categories, aggregation/assessment methodologies, and submission requirements

a. General. Currently, there are two basic report formats (full and abbreviated) and four report categories (Regular, Deployed, Validation and Other) that Army MTOE and TDA units, organizations and installations will use to routinely and periodically report readiness status data and information into the DRRS-Army database via NetUSR. All reports employ one or more of the three methodologies (standard aggregation, composite aggregation, and subjective assessment) to aggregate status data and/or to determine overall assessments. Force registration data and updates entered into DRRS-Army via the Force Registration Application are addressed in Part III. This paragraph explains the report formats, categories and the aggregation/assessment methodologies that currently are supported by the NetUSR application and report submission requirements. NetUSR supports all of the report formats and categories and the aggregation/assessment methodologies that previously were supported by PC-ASORTS, except for a consolidated report. The readiness status reporting requirements established in AR 220-1 and further explained in this publication are accomplished by reporting units using the report formats in the report categories and the aggregation/assessment methodologies supported by NetUSR. All NetUSR report formats and categories and aggregation/assessment methodologies require the reporting units, organizations, and installations to enter and update their basic unit information (BUI), to indicate their METL task assessments, to provide the applicable overall status level determinations and require commander's comments to explain any readiness status deficiencies reported. These data entry requirements comprise the minimum reporting requirements directed by HQDA (DAMO-ODR) via AR 220-1 to meet OSD and Joint Staff requirements. All MTOE units and any deployed or deployable TDA units also are required to report to meet Joint Staff requirements for status reporting by operational forces.

b. NetUSR report formats.

(1) The full report format. This report format entails extensive and detailed readiness status data and information on the reporting unit and provides a comprehensive readiness status report. The full report format produces the most objective report, and the preponderance of the data fields in the full report format are established as mandatory requirements. The NetUSR application imports status data and information from official Army sources and/or that has been reported by subordinate elements to facilitate readiness status determinations in accordance with established criteria. The measured area levels that are required to be determined and reported (PSRT ISO the C-Level assessment and AMM and AME ISO the A-Level assessment) consider the status of individual Soldiers and specific equipment items, or they are a composite reflecting the levels reported by subordinate reporting units. In general, units and organizations that are located at their home stations or at training sites are required to submit report types that apply the full report format.

(2) The abbreviated report format. This report format, also known as the "short" report format entails the minimum data necessary to portray the general readiness status of the reporting unit and to satisfy Joint Staff and OSD requirements. The abbreviated report format produces a more subjective report than a full report, and a significant number of the data fields that are available in the full report format are either unavailable or optional for data entry in an abbreviated report. The abbreviated report format does not require that NetUSR import status data and information from official Army sources to determine the PSRT-levels and these measured area levels can be determined based on the commander's subjective assessments. However, the AMM and AME levels are determined and reported the same way as in a full report. In general, units and organizations that have structures and/or resource requirements that are not established by a formal requirements and authorization document will submit report types that use the abbreviated report format. Additionally, units and organizations that currently are deployed away from their home stations to meet operational requirements normally are authorized to submit report types that use the abbreviated report format in lieu of (ILO) the full report format. For exceptional situations, abbreviated reports can be authorized by HQDA or the responsible ADCON authority ILO full reports.

c. NetUSR report categories.

(1) Regular reports. Reports in this category include those reports that are routinely submitted by non-deployed units into the DRRS-Army database via NetUSR pursuant to the Army's normal mid-month readiness reporting cycle. Regular reports have an "as of date" or RICDA of the 15 th of the month. The RICDA indicates the effective date of the status data and information contained in the report. Note that only one report will be submitted with a RICDA indicating the 15 th of the month and that subsequent reports reflecting updates and changes must be submitted as a "Change report" with a RICDA other than the 15 th of the month. Accordingly, only one report per CUSR cycle can be a Regular report. Regular reports use the full report format and include those reports using the composite aggregation methodology that are required for submission by major units and major headquarters (that is, composite reports). Formats for Regular reports can vary from month to month but usually do not.

(2) Deployed. Reports in this category are submitted while a unit or organization is deployed away from its home station for an operational requirement. Deployed reports are required within 24 hours after the main body closes in theater (during reception, staging, onward movement, and integration (RSOI)) or at the deployed location and subsequently, as of the 15 th of each month while the unit or organization is deployed. Reports are due to HQDA not later than (NLT) 96 hours after the "as of date." Deployed reports use the abbreviated format and include reports from major units and major headquarters that use the composite aggregation methodology. Deployed reports allow the commander to continue to determine and report the status of resources and training for the unit's core functions or designed capabilities while, concurrently, determining and reporting the ability of the unit or organization to undertake the current operational requirement. Detailed guidelines for deployed reporting are provided in AR 220-1 , paragraph 10-5 and appendix C.

(3) Validation reports. Validation reports are submitted by RC (COMPO 2 and COMPO 3) reporting units (ARNG/ARNGUS and USAR) and by custodians of Army pre-positioned stocks (APS) when there is no change in readiness status from the last report submitted. Validation reports enable RC units and APS custodians to meet the Joint Staff requirement for a monthly report without unnecessarily burdening units when there are no significant changes to readiness status. A validation report cannot be used if there is any change to an overall level (that is, the C-Level, A-Level or the chemical, biological, radiological, and nuclear (CBRN) level) or to the overall Y/Q/N mission capability assessment for either the unit's core functions or designed capabilities or assigned mission. Additionally, Validation reports are not allowed if there is a change to the status level of any measured area that directly supports the C-Level determination (for example, the P-Level, the S-Level, the R-Level or the T-Level), to the status of any measurement that directly supports the A-level (that is, the AMM and AME levels), or to either of the two measurements that directly support the CBRN level, (that is, the CBRN T-Level or the CBRN-S level). Since Validation reports merely update the "as of date" of the readiness status information and data contained in the previous report, they assume the format and type of the previously submitted report. Validation reports must have an "as of date" or RICDA indicating the 15 th of the month.

(4) Other reports. This category of reports is comprised of all the NetUSR reports that are not included in the other three categories of reports (that is, regular, deployed, and validation) discussed previously in this paragraph. Other reports include the special reports specifically designed for use by garrisons and installations, by sub elements registered in the DRRS-Army database with sub unit UICs and DUICs, and by selected Generating Force (TDA) commands, units, and elements and reports that update or change previously reported data. Distinct criteria and submission requirements normally apply to the reports in this category.

(a) Change reports.Change reports must have an "as of date" (RICDA) other than the 15th of the month and are submitted to report a change or update to the previously reported readiness status data or information of a reporting unit. Status changes requiring the submission of a change report include: any change to an overall readiness status level (that is, C-Level, A-Level or CBRN-level) or overall capability assessment (Y/Q/N); any change to a measured area level (PSRT-levels, AMM level, AME level, CBRN S-Level or CBRN T-Level), even if the unit's overall readiness/capability assessment does not change; and any change in the unit's mission status. Change reports are required to be submitted within 24 hours of the event requiring the change report. When applicable, change reports can differ in format and type from the previous report or the change report can replicate most of the data contained in a previous report, except for the changed status data and the new "as of date."

(b) Special reports.Special reports include the first (initial) report submitted by a reporting unit, reports submitted by DUICs and sub elements that do not normally report, regular, or validation reports submitted by RC units during time periods when they are not prescribed, and reports submitted by a nondeployed unit using an abbreviated format. Special reports may have any "as of date" or RICDA, and report formats may vary depending on the special circumstances associated with the report or the guidance received from ADCON authorities at higher levels. The regular, validation, and/or deployed reports containing special information temporarily reported via NetUSR's "Adhoc" feature also may be characterized in reporting guidance as "special reports."

d. CUSR methodologies.

(1) Standard aggregation. This methodology to measure readiness status is routinely used by reporting units with AA-level UICs to determine and report the measured area levels for personnel and equipment on-hand (available). The measured area levels for personnel and equipment on-hand (available) are determined by aggregating the required or, in some special cases (that is, APS), the authorized quantities indicated in the unit's formal requirements and authorization document and comparing these totals with the total number of Soldiers or equipment items available and/or trained and qualified. Similarly, the equipment readiness level is determined by aggregating the quantities of on-hand (possessed) like-type equipment by type/category and comparing these totals with the total quantity of fully mission capable items in the reporting unit.

(2) Composite aggregation. This methodology to measure readiness status is routinely used by major units and major headquarters, and, by exception, by other reporting units to determine the measured area levels for personnel, equipment on-hand (available) and equipment readiness. These measured area levels are determined by aggregating the levels reported by subordinate measured units and/or elements, determining the averages for each measured area, and reporting this average (after required rounding and normalization actions) as the respective measured area level for the major unit, major headquarters or exceptional organization required to use the composite reporting methodology.

(3) Subjective assessment. This methodology to measure readiness status is used by all measured units in various report types to determine specified levels, to include measured area levels and overall levels. The specified levels are determined based on the commander's evaluation, consideration and application of personal judgments regarding various readiness status indicators and data points.

e. NetUSR reports. Table 3-1 outlines the key distinction between the reports that currently are available for use by the reporting units to which they are applicable and under the circumstances for which they are authorized.

Table 3-1. NetUSR reports
Report name Report description, purpose and authorized users
Regular report 1. Full report routinely submitted monthly by nondeployed COMPO 1 units, by nondeployed RC units while on active duty status, and by designated RC units when directed or following their formal alert for deployment. Other nondeployed RC units that are not on active duty status routinely submit this report quarterly. Users of this report typically are MTOE (Operating Force) and TDA (Generating Force) units with UICs ending in AA (that is, battalion, separate company/detachment/team, and sof forth). This report provides a detailed assessment of all measured resource areas (that is, P, S, R, T, CBRN-S, CBRN-T levels, and, if applicable, AMM and AME levels); the overall levels (C-Level, CBRN level and, if applicable, the A-Level); and Y/Q/N capability assessments for both individual METL tasks; and core functions or designed capabilities and, if applicable, assigned missions).
2. When the unit commander chooses or when directed by ADCON authorities at higher levels, deployed units (COMPO 1 and RC) can submit a regular report. Reporting an assigned mission level (A-Level) is mandatory in regular reports submitted by deployed units. NOTE: If a major unit or major headquarters is directed or elects to submit a regular report while deployed, then the organic, assigned, attached and operational control (OPCON) subordinate elements currently under its command authority also must submit regular reports.
Validation report Intraquarterly report routinely submitted by designated Generating Force units, APS custodians and by USAR and ARNG units that are not mobilized or on active duty status. May be submitted by the unit only if no changes to the measured area levels, the overall readiness levels, the Y/Q/N METL assessments, or the overall Y/Q/N capability assessments have occurred since the last report.
Deployed report Abbreviated report meeting the minimum information and status reporting requirements that is routinely submitted monthly by a DEPLOYED unit. The levels of the measured resource areas (PSRT) and the overall levels are subjectively assessed. However, the A-Level is determined in the same manners as a regular report and determining and reporting an A-Level is mandatory. Y/Q/N/ capability assessments for METL tasks and missions also are mandatory. Submitted by reporting units having UICs ending in either AA or FF. NOTE: Deployed units may elect or be directed to submit regular reports.
Composite report (full report format "Regular" report that is routinely prepared and submitted by major units and major headquarters (brigade level and above). It replicates the Regular report explained above, except that the composite aggregation methodology is used to determine the levels for personnel (P-Level), equipment on-hand (S-Level) and equipment readiness/serviceability (R-Level) and 90- day C-Level projections are required.
Composite - Type II
Cmdr's assessment
(abbreviated format)
Abbreviated special report submitted monthly by designated nondeployed COMPO 1 units/headquarters and by designated nondeployed RC major units/headquarters. Other nondeployed RC major units/headquarters designated to submit this report that are not on active duty routinely submit this report quarterly. Typical users of this report are MTOE (Operating Force) units/headquarters above battalion level with UICs ending in FF that lack a defined organizational structure and/or that do not have mission required forces habitually assigned or under OPCON during peacetime (that is, corps HQs, some modular support brigades, and so forth). This report provides the CDR's subjective assessment of the measured resource areas, the overall levels (except the A-Level), and Y/Q/N capability assessments for the METL. (NOTE: Normally, A-Levels are required only after missions and/or mission forces are formally assigned, unless directed otherwise.)
Installation status report Quarterly special report submitted by designated Army installations; measures the facility's infrastructure readiness based on physical capitalized infrastructure measurements contained in the ISR.
DUIC special report
(Nondeployed)
Abbreviated special report for nondeployed ad-hoc elements or entities that do not have a designed structure established by a formal authorization and requirements document (that is, MTOE or TDA) or subordinate elements having a subunit UIC (also known as "structured DUIC.") Typically, the element or entity is identified by a derivative UIC or its subunit UIC. Report is submitted monthly or as directed.
DUIC special report
(deployed)
Abbreviated special report for deployed ad-hoc elements or entities that do not have a designed structure established by a formal authorization and requirements document (that is, MTOE or TDA) or subordinate elements having a subunit UIC (also known as "structured DUIC"). Typically, the element or entity is identified by a derivative UIC or its subunit UIC. Report is submitted monthly or as directed.
Generating forces
short report
Modified special report submitted quarterly by nondeployable TDA (Generating force) units that have no authoritative data available in accordance with guidance from HQDA (DAMO-ODR).
DRU report A special report that, if required, will be prepared and submitted in accordance with separate and specific guidance from HQDA.
TRADOC report A special report prepared and submitted by TRADOC units in accordance with specific guidance published by TRADOC in a HQDA-approved supplement to AR 220-1 .

f. Report submission requirements and timeliness of data.

(1) "Real time" is considered to be valid information received at HQDA within 24 hours of actual status change. That status may be forecast up to 72 hours from the time of the assessment if the unit expects to receive additional resources if called upon to execute a particular mission. Resourcing expectations that are not based on a formal plan must be confirmed via command channels.

(2) Basic unit information timeliness. All Army reporting units must maintain the currency of their BUI and submit an update within 24 hours of any major change (see chap 4 ).

(3) Unit readiness assessment timeliness. Except for installations, the following applies to all units required to assess and report readiness status (that is, assessed units):

(a) In accordance with 10 USC 117 and per Joint Staff requirements, measured units must submit an assessment of their current readiness status on monthly basis or within 24 hours of a change. Commanders of Army reporting units are required to report their unit's status as of the 15 th of each month, and these monthly reports are due to HQDA (DAMO-ODR) within 96 hours of "as of" date and time of the report or not later than 2400 hours "Juliet" (local time) on the 19th of the month. The DRRS-Army database HQDA (DAMO-ODR) will close not earlier than 1700 hours "Romeo" (Eastern Standard Time) on the 20th of the month to ensure that all Army reporting units have adequate time to comply with submission requirements regardless of their time zone or location.

(b) The following events will necessitate a change report due within 24 hours of the event necessitating the change:

(1) As applicable, a change to the C-Level or the A-Level overall assessments.

(2) As applicable, a change in any of the individual measured resource area levels that support the C-Level and A-Level overall assessments.

(3) As applicable, the receipt by a unit of an execute order or prepare to deploy order.

(4) As applicable, the receipt of a mobilization order by a RC unit and the unit's arrival at the mobilization station or demobilization station.

(5) A change in status resulting in a "No" assessment for any of the METL tasks associated with the unit's core functions or designed capabilities or the assigned mission or a change in the unit's location, mission, or command relationship with the next higher unit.

(c) In any event, Army assessed units will perform measurements and assessments on a monthly basis. Tables 3-1 and 3-2 and outlines the frequency that reports are required.

Table 3-2. Report submission requirements and frequency
Report category Reporting requirements and/or frequency Notes
Regular reports Monthly (Note#4) Quarterly (Jan, Apr, Jul, and Oct) Quarterly (Jan, Apr, Jul, and Oct) Quarterly (Jan, Apr, Jul, and Oct) Notes #3
Validation reports N/A Feb, Mar, May, Jun, Aug, Sep, Nov & Dec N/A N/A Notes #4
Change reports As required As required As required N/A Note #5
Deployed reports Monthly N/A N/A Monthly Note #5

Notes:
1. "Active Duty" units include COMPO 1 units and RC units (ARNG and USAR) that currently are on active duty status. "Designated" TDA units are those TDA units for which special reporting provisions apply. (See AR 220-1, para 8-4).
2. "Other" TDA units are TDA units that are not Army garrisons, installations or those TDA units for which special provisions apply in accordance with AR 220-1 , paragraph 8-4."
3. The readiness status data in regular reports is as of the 15th of the month that reports are required (monthly or quarterly), and the reports are due to HQDA NLT 96 hours after this "as of date."
4. Validation reports are applicable to designated Generating Force units, APS ( COMPO 6) and RC (COMPO 2 and COMPO 3) MTOE units and organizations that are not on active duty status. RC units formally alerted for deployment are required to submit monthly Regular reports in accordance with the provisions of AR 220-1, paragraph 8-4.
5. Change reports are required to be submitted within 24 hours of the event requiring the change report. HQDA requires that "other" TDA units report any changes to readiness status levels or assessments in their next report when due. However, the ACOM, ASCC, DRU, or DARNG for non mobilized ARNG TDA units, may require change reports via their supplementary instructions.
6. The first deployed report is required within 24 hours after the main body closes in theater (during RSOI) or at the deployed location, and subsequent reports are due as of the 15th of each month while the unit is deployed. TDA units and organizations that are deployed must comply with the same monthly reporting requirements as deployed MTOE units (see AR 220-1, chap 10). While APS is issued, custodians may report level 6 and/ or C-5 in accordance with AR 220-1, paragraphs 4-6 and 4-8, respectively. The APS custodians also will report deployment indicator code "E" when equipment is issued.

3-3. Reporting channels

Army units routinely submit their CUSRs through the ADCON channels in effect at the time of report submission. While the fielding of NetUSR will facilitate CUSR preparation, it will not provide the capability for the commanders of reporting units that do not have access to SIPRNet to both prepare and submit their reports online. Accordingly, commanders of reporting units without SIPRNet access will continue to prepare their reports using the standalone application and then will process their reports using the ADCON channels indicated in figures 3-1 and 3-2 until this SIPRNet functionality is established. Additionally, where these figures indicate "ACOM/ASCC/DRU/NGB," it should be understood to mean the responsible ACOM/ASCC/DRU-level ADCON authority and NGB for non-mobilized ARNG units, as appropriate. Channels for typical report submission are illustrated in figures 3-1 and 3-2 . Reporting channels for Army installations are explained in chapter 12 .



Figure 3-1. Typical CUSR channels (Garrison Environment)





Figure 3-2. Typical CUSR channels (Deployment Environment)


3-4. Actions by commanders at higher levels

a. 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 CUSR is intended to reflect the personal assessment of the commander of the reporting unit and will not be revised in any manner that will distort the report.

b. Commanders at higher levels with CUSR management oversight responsibility will review the reports of subordinate units for accuracy and will enforce compliance with the reporting requirements established in AR 220-1 . They also may provide additional information regarding the readiness status of the subordinate units as follows:

(1) At the brigade level and below, authorities at higher levels may insert additional information in the upper echelon comments of the subordinate unit's report.

(2) At the division headquarters level and above, authorities at higher levels may insert additional information in the upper echelon comments of the subordinate unit's report, provide comments in their own composite reports (use the "oversight" label when available in NetUSR) or they may send their comments through the chain of command to HQDA by separate correspondence.

(3) For purposes of CUSR management oversight of ARNG/ARNGUS ( COMPO 2) reporting units not on active duty, the State Adjutant General or the Joint Force Headquarters (JFHQ)-State is normally designated as the intermediate level headquarters, unless there is an existing ARNG headquarters within the state (for example, a division headquarters) designated for this responsibility.

(4) For USAR ( COMPO 3) units not on active duty, the USAR major subordinate command (MSC) is normally designated as the intermediate level headquarters to review the reports of USAR units.

(5) For CONUS-based U.S. Army Special Operations Command (USASOC) units not on active duty, USASOC is normally considered as the intermediate level headquarters. USASOC units based outside the Continental United States will submit CUSRs for review and processing through their chain of command to USASOC.

(6) Figure 3-3 , below, is the CUSR management oversight decision tree that illustrates the implications of command authority and ADCON relationships on CUSR management oversight responsibilities. Also see AR 220-1, paragraphs 4-9 and 4-10.



Figure 3-3. CUSR Management Oversight Decision Tree


3-5. Overview of commander's unit status report assessments, measurements, and metrics (also see chap 9)

a. C-Levels. The C-Level assessment for the reporting unit is determined and reported by the unit commander to indicate the ability of the unit and its overall readiness to accomplish its core functions and to provide its designed capabilities. Valid entries for the C-Level are numeric values: "1," "2," "3," "4," or "5." The following GSORTS definitions apply.

(1) C-1. The C level 1 indicates that the unit possesses the required resources and is trained to undertake the mission for which it is designed (that is, accomplish core functions and provide designed capabilities). The status of resources and training will neither limit flexibility in methods for mission accomplishment nor increase vulnerability of unit personnel and equipment. The unit does not require any compensation for deficiencies.

(2) C-2. The C level 2 indicates that the unit possesses the required resources and is trained to undertake most of the mission for which it is designed (that is, accomplish core functions and provide designed capabilities). The status of resources and training may cause isolated decreases in flexibility in methods for mission accomplishment but will not increase the vulnerability of the unit under most envisioned operational scenarios. The unit would require little, if any, compensation for deficiencies.

(3) C-3. The C-3 indicates that the unit possesses the required resources and is trained to undertake many, but not all, portions of the mission for which it is designed (that is, accomplish core functions and provide designed capabilities). The status of resources or training will result in a significant decrease in flexibility for mission accomplishment and will increase the vulnerability of the unit under many, but not all, envisioned operational scenarios. The unit will require significant compensation for deficiencies.

(4) C-4. The C-4 level indicates that the unit requires additional resources or training to undertake its designed mission (that is, accomplish core functions and provide designed capabilities), but it may be directed to undertake some portions of its mission with resources on hand.

(5) C-5. The C-5 level indicates that the unit is undergoing a HQDA-directed resource action (for example, reconstitution) and is not prepared, at this time, to undertake the full spectrum mission for which it is designed (that is, accomplish core functions and provide designed capabilities). However, it may be capable of undertaking nontraditional or non standard missions.

(a) HQDA employs the force development process with the goal of "standing-up" units at the overall level of C-3 or better. In many cases, actions impacting on unit status can be synchronized so that transitioning units can shorten the time period in C-5 status or avoid C-5 status entirely (see AR 220-1 , para 3-5).

(b) The C-5 units are restricted to the following:

(1) Units that are reconstituting following deployment or that are undergoing activation, inactivation, conversion, or other HQDA-directed resource action.

(2) Units that are not manned or equipped but are required in the wartime structure (that is, COMPO 4 units).

(3) Units placed in cadre status by HQDA.

(4) Units specifically directed to report C-5 by HQDA (DAMO-ODR).

b. Assigned mission levels (also see app C). The A-level assessment for the reporting unit is determined and reported by the unit commander to indicate the ability of the unit and its overall readiness for the currently assigned mission. Valid entries for the A-Level are numeric values: "1," "2," "3," or "4." The following definitions apply.

(1) A1 indicates that the unit possesses the required resources and is trained to undertake the full assigned mission.

(2) A2 indicates that the unit possesses the required resources and is trained to undertake most of the assigned mission.

(3) A3 indicates that the unit possesses the required resources and is trained to undertake many, but not all, portions of the assigned mission.

(4) A4 indicates that the unit requires additional resources or training to undertake the assigned mission, but may be directed to undertake portions of the assigned mission with resources on hand.

c. Mission capability assessments. The following are the "three-tier" metrics for the measurements and assessments applicable to the missions of units

(1) Report "Yes" if the majority of supporting METL tasks is currently assessed as "Yes" and no supporting METL task is currently assessed as "No."

(2) Report "Qualified Yes" if the majority of supporting METL tasks is currently assessed as "Qualified Yes" and no supporting METL task is currently assessed as "No." Report `"No" if any of the supporting METL tasks are currently assessed as "No."

(3) Figure 3-4 outlines the methodology for the overall capability assessments that are applicable to both core functions or designed capabilities and assigned missions.



Figure 3-4. Overall unit readiness and mission capability assessments


d. Chemical, biological, radiological, and nuclear-levels. The overall CBRN level indicates the ability of the unit to operate in a CBRN hazardous area and requires assessment using the four-tier rating scale only. The equipment on hand (EOH) and training measured areas are evaluated separately by the commander and then used to determine an overall assessment of the unit's CBRN readiness.

e. Mission accomplishment estimates. The MAE is the measured unit commander's subjective assessment of the unit's ability to accomplish core functions and provide the designed capabilities that would be expected if alerted/committed within 72 hours of the "as of" date of the report. Only units/elements currently under the control (organic/assigned/attached/OPCON) of the commander should be considered in his estimate, unless gains to or losses from units/elements under their control within the next 72 hours have been formally programmed/ordered and confirmed. The MAE is an optional data point that can be used to inform the commander' s C-Level determination and the assessment of the unit's core functions or designed capabilities.

f. Measured areas.

(1) Four measured areas support the overall C-Level assessment of core functions or designed capabilities; two measured areas support the overall assigned mission (A-Level) assessment; and two measured areas support the overall CBRN level assessment.

(2) Measured areas supporting the overall C-Level assessment. Commanders determine and report four measured area levels indicating the current status of resources and training in the unit to support their overall C-Level assessments: personnel (P), equipment and supplies (S) on-hand/available, equipment readiness/serviceability (R), and unit training proficiency (T). These measured areas are referred to as "PSRT."

(a) Personnel (P-Level).Army measured units will measure personnel readiness using three metrics for personnel fill percentages that are based on the unit's strength requirements for its core functions or designed capabilities: total available personnel strength divided by the required strength, available duty military occupational specialty qualified strength (DMOSQ) divided by the required strength, and the available senior grade composite level determined by comparing the available and required strength in each of five senior grade categories. The applicable MTOE or TDA that reflects the unit's core functions or designed capabilities is the authoritative source for the unit's required strength. While Army measured units also are required to determine and report additional personnel data (for example, the assigned strength percentage, turnover percentage, and so forth), the personnel level is determined solely based on the results of these three P-Level metrics. See chapter 5 , paragraph 9-3 and AR 220-1 , chapter 9.

(b) Equipment and supplies on-hand/available (S-Level).Army measured units determine and report a S-Level by determining by LIN the on hand/availability status of designated critical equipment items (pacing items) and the on-hand/availability status of the other mission essential equipment items (equipment readiness code (ERC) A) that are listed on the unit's MTOE or TDA. Substitute items prescribed by HQDA via SB 700-20 and ILO substitutions determined by the commander are applied in accordance with the provisions of paragraph 9-3. Note that for this S-Level measurement, the on hand/availability status of equipment items is based on those equipment items currently in the unit's possession, under its control or, when applicable, available to it within 72 hours that can be used to accomplish/provide the core functions or designed capabilities. The S-Level measurement is not based solely on property accountability records, and it does not consider the operational readiness/serviceability of the equipment items. A discrete measurement is accomplished at the LIN level of detail by comparing the equipment items currently in the unit's possession, under its control or available to it within 72 hours to the required equipment items for the unit's core functions or designed capabilities, and a S-Level rating is determined for each measurement. The applicable MTOE or TDA that reflects the unit's core functions or designed capabilities is the authoritative source for the unit's equipment requirements. The unit' s S-Level rating is determined in accordance with a methodology that considers each of these by LIN S-Level measurements. See chapter 6 , paragraph 9-3 and AR 220-1, chapter 9.

(c) Equipment readiness/serviceability (R-Level).Army measured units will measure the operational readiness or serviceability of the critical equipment items that are in their possession, under their control or available to them within 72 hours, and that are designated by HQDA via the maintenance master data file (MMDF) as reportable for maintenance. Separate measurements will be accomplished for each maintenance reportable pacing item and for all maintenance reportable equipment currently in the unit's possession (aggregate). An R-Level rating is determined for each measurement, and, subsequently, the unit' s R-Level rating is determined in accordance with a methodology that considers each of these R-Level measurements. Procedures are explained in chapter 7 . Also see para 9-3 and AR 220-1 , chapter 9. Note that reporting R5 is no longer a reporting option.

(d) Unit training proficiency (T).Commanders of Army measured units will report the training status of their units based on the percentage of the unit's METL tasks trained to standard. While Army measured units also are required to determine and report additional training data (for example, required training days, squad/crew/team manning and qualification status, and so forth.) the training level is determined solely based on the results of MET proficiency assessments. See chapter 8 , paragraph 9-3 and AR 220-1, chapter 9.

(3) Measured areas supporting the overall assigned mission level (A-Level) assessment. Commanders determine and report two measured area levels indicating the current status of resources and training in the unit to support their overall A-level assessments: the assigned mission manning level (AMM-Level) and the assigned mission equipping level (AME-Level). These measured areas are defined below and further explained in chapter 9.

(a) Assigned mission manning level (AMM-Level).Army measured units determine and report the manning status for their assigned missions by comparing the manning requirements for the assigned mission that were established, conveyed or approved by the appropriate Army tasking authority with the personnel currently available to the unit to accomplish the assigned mission. Appropriate command guidance and/or formal orders will provide the basis for the assigned mission manning requirements, if they differ from the unit's MTOE/TDA requirements, and for determining Soldier availability, if criteria differ from that applicable to assessments of core functions or designed capabilities. This command guidance also will address how Soldiers programmed to join the unit but not currently available to it (for example, post deployment augmentees) should be considered. See chapter 9 .

(b) Assigned mission equipping level (AME-Level).Army measured units determine and report the equipping status for their assigned missions by comparing the equipment requirements for the assigned mission that were established or approved by the appropriate Army tasking authority (ATA) with the equipment items that are currently possessed/controlled by the unit to accomplish the assigned mission. If the resource requirements for the assigned mission differ from the unit's MTOE/TDA requirements, then the ATA must ensure that the unit receives the command guidance and/or formal orders necessary to establish the equipment requirements,. This command guidance also will address how equipment items programmed for use by the unit but not currently in its possession (that is, theater provided equipment) should be considered for CUSR purposes. See chapter 9.

(4) Measured areas supporting the overall CBRN assessment. Each Army measured unit will determine and report its overall readiness assessments for CBRN in accordance with the provisions of AR 220-1 , paragraph 4-4. Two measured area levels support the determination of the overall CBRN level.

(a) The CBRN S-Level (availability and serviceability of CBRN equipment items). For the CBRN report, the commander must identify the equipment items required by his unit to operate in a CBRN environment, assess the equipment on-hand (available) status and the current maintenance status of the required CBRN equipment items, and then provide an overall CBRN S-Level assessment in light of this information. The NetUSR software application will enable and support these actions. The CBRN S-Level is a four-tier metric (see table 3-6 ); however, unlike other USR S-Levels that are objectively calculated and do not consider equipment serviceability issues, the CBRN S-Level is subjectively determined by the unit commanders based on both supply and maintenance factors in accordance with the descriptive criteria established in table 6-3 . The detailed procedures are explained in paragraph 6-3 . The NetUSR User's Guide and Help Screens also explain CBNE S-Level reporting procedures and provide examples of the data entry requirements.

(b) CBRN T-Level (training).For the CBRN report, commanders must estimate the number of training days required by the unit to conduct operations in a CBRN environment and then determine the applicable CBRN T-Level. For the preponderance of reporting units this estimate should be the same as the estimate of overall training days determined in accordance with the provisions of paragraph 8-7 a . Subsequently, commanders will use table 8-4 to translate the estimated number of training days required for CBRN operations to the applicable CBRN T-Level. Additional instructions are provided in paragraph 8-7 b . The NetUSR User's Guide and Help Screens also explain CBRN T-Level reporting procedures and provide examples of the data entry requirements.

(c) Summary and review. The following figure and table summarize, review, and outline the various CUSR metrics addressed in this publication. Also see AR 220-1 , paragraph 4-4.

Table 3-3. Metrics for measuring and assessing core functions or designed capabilities
CORE FUNCTIONS or DESIGNED CAPABILITIES
Four-tier
metrics
Overall Readiness Assessment Associated/Supporting Resource Measurements and Training Assessments
Tier 1 C1 P1 S1 R1 T1 (in accordance with TPU METL training assessments {No U's})
Tier 2 C2 P2 S2 R2 T2 (in accordance with TPU METL training assessments {No U's})
Tier 3 C3 P3 S3 R3 T3 (in accordance with TPU METL training assessments)
Tier 4 C4/5 P4/5 S4/5 R4/5 T4/5 (in accordance with TPU METL training assessments)
Three-tier metrics Overall Capability
Assessment

Associated/Supporting METL Task Capability Assessments
Tier 1 Y (in accordance with YQN METL task capability assessments {Majority Y's. No N's}) Y = T in accordance with TPU METL task assessment and the resources required to execute the METL task currently are available to unit or specifically identified.
Tier 2 Q (in accordance with YQN METL task capability assessments {No N's}) Q = T in accordance with TPU METL task assessment if the resources required to execute the METL task currently are not available to unit or are not specifically identified but the risks have been mitigated.
Q = P if the resources required to execute the METL task currently are available to unit or are specifically identified.
Tier 3 N (in accordance with YQN METL task capability assessments. Any METL task currently assessed as N) N = T, P, or U in accordance with TPU METL assessment if the resources required to execute the METL task currently are not available to unit, are not specifically identified or the risks have not been mitigated.
N = U in accordance with TPU METL assessment, even if the resources required to execute the METL task currently are available to unit or are specifically identified.


Table 3-4. Primary assigned mission metrics
CORE FUNCTIONS or DESIGNED CAPABILITIES
Four-tier
metrics
Overall Readiness Assessment Associated/Supporting Resource Measurements and Training Assessments
Tier 1 C1 P1 S1 R1 T1 (in accordance with TPU METL training assessments {No U's})
Tier 2 C2 P2 S2 R2 T2 (in accordance with TPU METL training assessments {No U's})
Tier 3 C3 P3 S3 R3 T3 (in accordance with TPU METL training assessments)
Tier 4 C4/5 P4/5 S4/5 R4/5 T4/5 (in accordance with TPU METL training assessments)
Three-tier metrics Overall capability
assessment

Associated/supporting METL task capability assessments
Tier 1 Y (in accordance with YQN METL task capability assessments {Majority Y's. No N's}) Y = T in accordance with TPU METL task assessment and the resources required to execute the METL task currently are available to unit or specifically identified.
Tier 2 Q (in accordance with YQN METL task capability assessments {No N's}) Q = T in accordance with TPU METL task assessment if the resources required to execute the METL task currently are not available to unit or are not specifically identified but the risks have been mitigated.
Q = P if the resources required to execute the METL task currently are available to unit or are specifically identified.
Tier 3 N (in accordance with YQN METL task capability assessments. Any METL task currently assessed as N) N = T, P or U in accordance with TPU METL assessment if the resources required to execute the METL task currently are not available to unit, are not specifically identified or the risks have not been mitigated.
N = U in accordance with TPU METL assessment, even if the resources required to execute the METL task currently are available to unit or are specifically identified.


Table 3-5. Additional assigned mission(s) metrics
ADDITIONAL ASSIGNED MISSION(S)*
Three-tier metrics Overall capability
assessment
Associated/supporting METL task capability assessment
Tier 1 Y (in accordance with YQN supporting METL task capability assessments {Majority Y's. No N's}) Y = T in accordance with TPU METL task assessment and the resources required to execute the METL task currently are available to unit or specifically identified
Tier 2 Q (in accordance with YQN supporting METL task capability assessments {No N's}) Q = T in accordance with TPU METL task assessment if the resources required to execute the METL task currently are not available to unit or are not specifically identified but the risks have been mitigated.
Q = P if the resources required to execute the METL task currently are available to unit or are specifically identified
Tier 3 N (Any supporting METL task currently assessed as N) N = T, P or U in accordance with TPU METL assessment if the resources required to execute the METL task currently are not available to unit, are not specifically identified or the risks have not been mitigated
N = U in accordance with TPU METL assessment, even if the resources required to execute the METL task currently are available to unit or are specifically identified.

Notes:
1. Normally, only organizations at the brigade-level and above will be required to report their mission capability status for more than the one primary assigned mission. Exceptions may include special contingency requirements (that is, QRF, GRF, CCMRF, and so forth) and (for ARNG units) state assigned missions.
2. The commander may report either "Yes" or "Qualified Yes" (commander's option) if all of the supporting METL task assessments are evenly split between "Yes" and "Qualified Yes."


Table 3-6. Chemical, biological, radiological, and nuclear metrics
CBRN MEASUREMENTS AND ASSESSMENTS
Four-tier metrics Overall CBRN Readiness Assessment Associated/Supporting METL Task Capability Assessment
Tier 1 CBRN-1 CBRN S1 CBRN T1
Tier 2 CBRN-2 CBRN S2 CBRN T2
Tier 3 CBRN-3 CBRN S3 CBRN T3
Tier 4 CBRN-4 CBRN S4 CBRN T4

Notes:
1. CBRN S-levels include equipment on-hand and equipment serviceability factors.
2. CBRN T-levels are based on the TPU assessment of METL tasks under CBRN conditions.

3-6. Basic ground rules and procedures

a. General. The NetUSR calculates all measured area levels supporting the C-Level determination using the requirements associated with the unit's core functions or designed capabilities that are reflected by their organic or designed/established structure (cadre column for cadre units; table of organization and equipment (TOE) Type B column for Type B units, and MTOE and TDA required column for all other units, except APS) as stated in applicable requirements and authorization documents. The only exceptions to this basic rule are that the EOH (S-Level) calculations for APS are based on the "authorized" quantity of equipment.

b. Activation and/or reorganization. The objective of the Army force development process is to modernize the force without significantly degrading unit readiness. Therefore, E-dates for force development actions must be synchronized with and complemented by the availability of sufficient modernization equipment. Decisions regarding out-of-cycle reorganization and modernization must consider the potential of those actions to adversely impact the readiness of the units involved. In other than highly exceptional circumstances, reorganization should not occur unless the personnel and equipment that are required to support the new organization are reasonably available. The force validation process exists to ensure that, under normal circumstances; units are activated and reorganized at the C-3 level or better.

(1) Parent (AA-Level) units that activate/reorganize incrementally will report against their current full MTOE structure. (For example, a support battalion that activates one company at a time would report against its full battalion structure). When, prior to E-date, the AA-Level unit more closely resembles the new organization than the old organization regarding structure, manning and equipment, the unit will obtain approval from the responsible ACOM/ASCC/DRU and/or DARNG/NGB for ARNG/ARNGUS units not on active duty) to report as the new organization.

(2) Major units (FF-Level UIC) that activate/reorganize incrementally will reflect in their composite reports the status of each of the organic reporting units that are a part of their "as designed" force structure. When aggregating the measured area levels, consider organic units/elements that are not yet organized or activated as P-4 and S-4.

c. As MTOE/TDA change documents are published and provided to units, confusion often develops as to which authorization document the unit should use for calculating status. Commanders must decide which document, the current or future MTOE/TDA, the entire unit (personnel and equipment) most closely resembles, in order to accurately report unit status. However, units will not report early against a new MTOE/TDA without the approval of the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, or if it will result in a degraded overall level below C-3. Once a commander begins to report against a new MTOE/TDA ( future E-date), the previous MTOE/TDA will not be used for unit status reporting unless approved by the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable. Commanders must report all resource areas using the same MTOE/TDA. For example, commanders will not report personnel using the future MTOE/TDA and equipment from the current MTOE/TDA. Also see AR 220-1 , paragraph 7-2.

d. Availability of units.

(1) The availability of Army units/elements for missions and operational deployments is determined by the Army Force Provider in conjunction with HQDA, the Joint Force Provider, and the applicable ASCC/combatant commander, pursuant to the ARFORGEN process. While employed/deployed or conducting split-based operations, specific instructions and/or additional guidance, for CUSR purposes, regarding timelines and criteria for disengagement, recovery, post-deployment training, reconstitution, and redeployment may be provided to units through command channels. In the absence of such specific instructions and guidance, and when the availability of subordinate units/elements must be determined for CUSR purposes, commanders of major units and major headquarters preparing composite reports (FF-Level UICs) and commanders of measured units preparing regular reports (and other reports when applicable) will comply with the special instructions for CUSR calculations and assessments that are contained in paragraph 4-3 and the policy guidance contained in AR 220-1, paragraph 4-9.

(2) In general, subordinate units/elements that are operating outside of the command authority of their parent unit or parent headquarters will be considered not available by the parent unit or headquarters for CUSR calculations and assessments, subordinate units, and/or elements away from their home stations to participate in training will be considered available. For their USR calculations, commanders of composite reporting units will use P4 and S4 as the measured area levels of subordinate measured units that are part of their organic or designed/established structure but are not available, unless these detached units have been replaced by OPCON aligned augmenting units that have, in the commander's judgment, comparable and/or equivalent capabilities. This use of P4 and S4 enhances the accuracy of P-Level and S-Level calculations in composite reports by incorporating the negative impact of unavailable resources and assets. (Also, see para 9-3 ).

e. Rounding decimals. Use the rounding rule for decimals when you use a table or accomplish calculations in accordance with status level guidelines provided in this publication; round numbers ending in ".5" or more to the next higher whole number and round numbers less than ".5" to the next lower whole number.

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

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

3-7. C-5 reporting procedures

a. General. The measured area levels and the category levels (C-Levels) are explained in paragraph 3-5 . Units requiring significant additional resources and/or training to accomplish their core functions and/or to provide their designed capabilities (that is, C-4 units) due to HQDA actions or programs will report C-5 in accordance with the instructions in this paragraph and the policy in AR 220-1 .

b. C-5 reporting.

(1) Directed C-5 reporting. HQDA (DAMO-ODR) will direct C-5 reporting by Army reporting units when necessary to ensure uniformity in compliance with and interpretation of C-5 reporting policy by Army units and organizations (for example, when the availability of an Army unit for tasking is being restricted by HQDA, for exceptional deployment scenarios and in circumstances where non-standard missions and exceptional requirements and authorizations documents are applicable). HQDA- directed C-5 reporting units will report the applicable reason code (see app I ) to clearly indicate that the HQDA- directed C-5 reporting is due to special circumstances.

(2) Mandatory C-5 reporting. Army reporting units will report C-5/T-5 following redeployment while the unit is in the RESET force pool (see AR 220-1, chap 5). While NetUSR may auto-populate some data for units required to report C-5, this auto-population does not relieve mandated C-5/T-5 reporting units from requirements to accurately determine and report their measured area levels for personnel, EOH, and equipment readiness (ER) or from reporting their METL assessments. Mandatory C-5/T-5 reporting is applicable to all units in the ARFORGEN RESET force pool. The duration of the mandated C-5/T-5 reporting is 180 days for AC (COMPO1) units and 365 days for RC units. Requests to report C-5 beyond the specified reconstitution period require HQDA approval and will be submitted in accordance with the provisions of AR 220-1, paragraph 4-8 .

c. Inactivation/discontinuations. The responsible ACOM/ASCC/DRU, and/or DARNG/NGB, when applicable, may direct units programmed for inactivation/discontinuation to report C-5 when the unit reaches level 4 in any measured area level (except authorized 6s) and is within 365 days of the effective date (E-date) of inactivation/discontinuation. 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.

d. Activations/reactivations. The responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, will direct units undergoing activation/reactivation at an overall level of less than C-3 (that is, C-4) to report C-5 until they attain a minimum level of 3 in all measured areas (P-Level, S-Level, R-Level, and T-Level). Reporting C-5 begins when the unit initially activates or reactivates, and continues until it has achieved and can report an overall status level of C-3 or (unless an extension has been approved) or until the period authorized for C-5 reporting has ended (whichever is earlier). After achieving and reporting a C-3 status level, the unit must report C-4 and cannot report C-5 if unit status subsequently deteriorates below the C-3 level (that is, falls to C-4). The maximum time that a unit may report C-5 is 1 year for Active Component (AC) units and APS and 3 years for RC units.

e. Conversions. HQDA is the approval authority for C-5 reporting by all units that are undergoing modularity conversion. Requests for HQDA approval to report C-5 will be endorsed by a general officer or equivalent government official. For other conversions, the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, will direct units undergoing conversion to report C-5 when they reach level 4, in any measured area, as a result of the conversion. The units will continue to report C-5 until they again achieve at least a level 3 in all measured areas or reach the termination date specified by HQDA for C-5 reporting. The maximum time that a converting unit may report C-5 is 1 year for AC units and 3 years for RC units. Conversions are defined as a major unit change to another MTOE, or a complete change in the type of unit or branch.

f. Action by the Army command/Army component service command/direct reporting unit and/or DARNG/NGB, when applicable. These commands will inform HQDA (DAMO-ODR) of units with AA-level UICs that they have approved or directed to report C-5 as a result of undergoing an HQDA-directed action or program (includes conversion of units to cadre status, force stabilization, and the transfer of equipment from APS to designated units). Requests for HQDA approval to report C-5 will be endorsed by a general officer or equivalent government official. HQDA (DAMO-ODR) is the directing and approval authority for C-5 reporting by all major units and major headquarters. A C-5 level will be reported until the unit is able to report level-3 or higher in all four measured areas. The responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, installations, and units will determine the effect of HQDA directed program/actions prior to the E-date. If a C-4 level will result, the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, may approve C-5 reporting (or request an extension from HQDA (DAMO-ODR), if needed; request a change to the E-date from HQDA (DAMO-FMF), or continue the action at a C-4 level. The responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, must regularly review the status of units reporting C-5 (monthly for AC and every 3 months for RC) to determine if a C-5 level is still warranted and to evaluate actions being taken to improve the status of the unit.

g. C-5 reporting units.

(1) 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 a level three or higher (includes Type B, medical, transportation, and cadre units), will report C-5.

(2) Units will use the applicable reason code, provide comments to explain the action(s) that caused the level 5 to occur in a measured area and indicate the anticipated date of resolution. A unit that reports level 5 in any measured area must also report C-5 overall. Similarly, one or more of the measured areas must be reported as level 5 for the unit to report an overall level of C-5 (also see AR 220-1 , para 4-8).

h. Requests from the responsible ACOMs/ASCCs/DRUs and/or DARNG/NGB, when applicable. These commands must submit a request to HQDA for their units to continue to report C-5 beyond the time limits established for C-5 reporting in this paragraph. Requests will be forwarded to Office of the Deputy Chief of Staff, G-3/5/7 (ODCS, G-3/5/7) (DAMO-ODR/Army Readiness Division), 400 Army Pentagon, Washington, DC 20310-0400. If required, DAMO-ODR will coordinate with the Joint Staff regarding the request. Requests to extend authority for C-5 reporting are not required for units authorized to report C-5 under the provisions of paragraph 3-6 g (1), above (for example, type B, cadre units, and so forth); these units may report C-5 indefinitely or until they are able to achieve a level 3 or higher in all measured areas and/or can report C-3.

3-8. Level 6 reporting procedures

a. General. Level 6 indicates that the measured area is not measurable, or by HQDA direction, is not measured. (For example, R-6 could be reported if the ER level could not be determined because equipment is centrally stored, on board ship or because a civilian contractor performs maintenance for the unit.) Measured area levels of 6 are considered in determining the overall level for CUSRs; however, level 6 cannot be used as the overall level (that is, there is no C-6 level). When included in the composite calculations used by major units and major headquarters, the level 6 determinations will have a value of 4 in those calculations. Commanders remain responsible for accountability and management of any Army personnel and equipment in measured units under their control reporting level 6 for measured area(s).

b. Level 6 reporting by units with AA-Level composite reporting units. 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 and subjectively assess the status of the measured area and consider this assessment when determining whether or not upgrading/downgrading the overall unit level is appropriate. Use normal procedures for other measured areas and provide narrative comments regarding the unit's ability to accomplish its mission requirements.

c. Level 6 reporting by units composite reporting units.

(1) Commanders of composite reporting units will consider the measured areas of personnel and EOH for subordinate measured units that are included in their organic or designed/established structures but are not currently under their command authority (that is, units that are detached) as level 6 in their composite reporting calculations unless these detached units have been replaced by OPCON-aligned augmenting units that have, in the commander's judgment, comparable and/or equivalent capabilities. This use of level 6 is intended to enhance the accuracy of P-Level and S-Level calculations in composite reports by incorporating the impact of unavailable resources and assets. However, commanders may consider OPCON-aligned augmenting units that have, in the commander's judgment, comparable and/or equivalent capabilities to the units detached from the organic or designed/established structure as one-for-one replacements in composite reporting calculations.

(2) Level 6 determinations will have a value of four in composite reporting calculations.

3-9. Reporting commander's unit status report data via net-centric unit status report

See the NetUSR Users Guide and Training Support Package at the portal.

Chapter 4

Reporting Basic Unit Information and Subordinate Unit Relationships

4-1. General

a. This chapter explains the fundamental procedures for using NetUSR to enter BUI and to identify subordinate unit relationships in the CUSR. The NetUSR User's Guide and the various user help screens that are embedded in the software supplement the procedures explained in this chapter and provide reporting examples, additional instructions and further explain data entry procedures. The policy requirements for entering and updating BUI and for determining subordinate relationships are established in AR 220-1 , chapter 4. NetUSR uses information imported by units from ADS during CUSR preparation to auto-populate many of the BUI data fields and list of organic (designed/established) units for some reporting units. Reporting units with AA-Level UICs (parent units) and major units and major headquarters with FF-Level UICs (brigades and above) that submit composite reports must update their BUI data and subordinate relationships each time that they prepare and submit a CUSR using NetUSR. These updates are required from reporting units in all situations and operational environments, to include reporting while at the home station location and also reporting while deployed/employed away from the home station location.

b. The NetUSR software application will auto-populate many of the required BUI data fields based on the data established in the MTOE/TDA selected by the unit as the basis for its measurements and assessments of readiness for core functions or designed capabilities. The data entry procedures contained in this chapter identify and discuss the BUI data fields auto-populated by the NetUSR software application and explain the data entry procedures for the other BUI data fields that must be completed by the unit. The procedures explained in this chapter are applicable to all reporting units (AA-Level UICs and FF-Level UICs). Fundamental BUI reporting procedures are explained in paragraph 4-2 . Procedures for reporting subordinate relationships are explained in paragraph 4-3 .

4-2. Reporting basic unit information

a. Basic unit information. The BUI report is located at NetUSR's "Unit Information" tab. The BUI report contained in the CUSR is comprised of mandatory and optional data fields that are organized into six distinct sections. An asterisk (*) is used to annotate the mandatory data fields. The following paragraphs explain the data entry procedures for each section.

b. Authorization document section. The NetUSR application uses the unit information contained in the MTOE or TDA document selected by the unit to auto-populate the first three data fields in this section. All data fields in this section are mandatory, except the standard requirement code (SRC) data field. The MTOE/TDA document applicable to a unit describes the unit's core functions or designed capabilities and establishes the authoritative manning and equipping requirements for these functions and capabilities. Accordingly, NetUSR uses these requirements as the basis for the measurements and assessments of the core functions or designed capabilities included in the CUSR (the C, P, S, R, and T-Levels). The force management information contained in this section falls under the purview of the Director of Force Management (DAMO-FM) and is further explained in AR 71-32. This section consists of the following data fields:

(1) MTOE/TDA Effective Date (EDATE). This is the effective date of the MTOE/TDA selected by the unit in the "YYYYMMDD" format; (auto-populated from the MTOE/TDA document selected).

(2) Unit authorization document number (MTOE/TDA). This 10-posiiton alphanumeric code identifies the base TOE, proponent command and MTOE variation that are applicable to the MTOE/TDA selected by the unit; (auto-populated from the MTOE/TDA document selected).

(3) Command and control number. The command and control number (CCNUM) indicates the number of changes applied to a MTOE or TDA document by a specific command during a fiscal year; (auto-populated from the MTOE/TDA document selected.

(4) Standard requirement code. This 12-posiiton alphanumeric code identifies the base or intermediate TOE and subparagraph number. The SRC is auto-populated from the MTOE/TDA selection when applicable; (leave blank if not applicable).

(5) ACOM/ASCC/DRU: AR 10-87 establishes the ACOMs, ASCCs, and DRUs. While the preponderance of the Army's reporting units fall under the purview of a specific ACOM, ASCC, or DRU, there are some Army organizations that do not. The drop down menu provided by NetUSR lists the ACOMs, ASCCs, and DRUs and also includes various other commands/organizations that may be applicable to some reporting units. If more than one menu listed item is applicable to the unit, then select the command/organization at the highest level.

c. Report information section. The NetUSR uses the unit information contained in the MTOE or TDA document selected by the unit to auto-populate the first four data fields in this section. However, units may edit the auto-populated data, except for the COMPO data field, to correct any erroneous data resulting from NetUSR's application of the MTOE/TDA information. All of the data fields in this section are mandatory. This section consists of the following data fields:

(1) This is the unit's abbreviated organization name (ANAME) from the MTOE or TDA; (auto-populated from the MTOE/TDA document selected).

(2) Unit is an aviation unit with aircraft: "YES" and "NO" are the only valid entries. "YES" indicates that the unit is an aviation unit with aircraft; both criteria must apply. "NO" indicates that one or both of these two criteria do not apply (that is, the unit is either not an "aviation unit" or that it does not have any aircraft requirements on its MTOE/TDA). While NetUSR will auto-populate this data based on the MTOE/TDA document selected and, if applicable, the SRC data entry, the unit should edit this auto-populated data if necessary to ensure accuracy. "YES" entries result in the application by NetUSR of the S-Level and R-Level metrics that apply only to aviation units with aircraft requirements.

(3) Unit is a hospital unit: "YES" and "NO" are the only valid entries. "YES" indicates that the unit is a hospital unit. "NO" indicates that the unit is not a hospital unit. While NetUSR will auto-populate this data based on the MTOE/TDA document selected and, if applicable, the SRC data entry, the unit should edit this auto-populated data if necessary to ensure accuracy. Note that hospital units have additional reporting requirements, for example, the number of operational beds and surgical tables supportable with the resources currently available to the hospital unit (see para 9-5 ).

(4) Unit is partial deployed/split operations. "YES" and "NO" are the only valid entries. "YES" indicates that the unit is either partially deployed (applicable to units with AA-Level UICs) or that it is conducting split based operations (applicable to FF-Level UICs). Chapter 11 explains the procedures for reporting while deployed and the terms "partially deployed" and "split based operations" also are defined in the glossary. While NetUSR will auto-populate this data based on the type report selected for submission (for example, a deployed report), the unit should edit this auto-populated data if necessary to ensure accuracy.

(5) Force structure component (COMPO). The following force structure component designations apply to reporting units: "1" for units so designated as the result the TAA and POM processes (also known as "Regular Army," and/or "Active Component" units); "2" for Army National Guard (ARNGUS/ARNG) units; "3" for USAR units: and "6" for APS. The COMPO designation for multiple component units is the same as that of the controlling (flag holder) parent unit (see AR 220-1 , para 10-8 and para 12-6 of this publication). The various COMPOs also are defined in the glossary. This data field is auto-populated from the MTOE/TDA document selected and is not editable by the unit.

(6) Report classification. Enter the security classification of the report in accordance with the provisions of AR 220-1 chapter 11and chapter 13 of this publication. Note that all CUSRs are classified, except those practice reports containing notional/fictitious data that are used for training and exercises only.

(7) Report use. Use this data field to indicate whether the report is for normal/regular use or only for training or exercise use. Note that only "exercise" reports containing notional/fictitious data should be indicated as "UNCLASSIFIED" in the previous data field.

(8) Current activity code. Select the code from the drop down menu that most accurately describes the unit's current activity. See appendix I of this publication regarding the authoritative listing of current activity codes.

d. Reporting relationships section. This section enables the reporting unit to identify the next higher command/organization in its operational and administrative hierarchy. Army command and support relationships are explained in Field Manual (FM) 3-0, and the implications of these relationships to readiness reporting are explained in AR 220-1, paragraph 4-9 . Both of the data fields in this section are mandatory.

(1) Operational control. Enter the UIC of the next higher organization in the operational chain of command of the measured unit. This would include the next higher unit to which the reporting unit is either organic, assigned, attached or considered OPCON. (Note that "organic," "assigned," and "attached" are Army unique command relationships that, from a Joint perspective, are inherent in "OPCON" as defined in the Joint doctrine (see Joint Publication 3-0). For the purpose of this Joint data field, these Army unique command relationships are reported as "OPCON.") If the next higher OPCON unit is a composite reporting unit, then enter the FF-Level UIC of that unit. This data entry enables resource managers and strategic planners at higher levels to understand current command alignments. Note that the deployment/employment of units to meet operational requirements can result in a change to OPCON relationships.

(2) Administrative control. Enter the UIC of the organization currently exercising authority over the reporting unit with respect to administration and support. If the next higher ADCON authority is a composite reporting unit, then enter the FF-Level UIC of that unit. If, in accordance with AR 10-87 , ADCON authority at the next higher level is shared between two or more units, then enter UIC of the next higher ADCON authority responsible for "CUSR management oversight" (see AR 220-1 , paras 4-9 and 4-10). Note that the deployment/employment of units to meet operational requirements can result in a change in ADCON authority and/or responsibility for CUSR management oversight.

e. Current location section. The data fields in this section establish the current location of the reporting unit or, if partially deployed or conducting split based operations, the current location of the preponderance (more than 50 percent) of the personnel in the reporting unit. The first data field (current location code (CULOC)) and the last data field (location classification) in this section are mandatory. This section consists of the following data fields:

(1) Current location code. Use NetUSR's lookup feature to determine the code for the unit's current location or, if embarked onboard a ship, then enter the UIC of the Navy ship. Enter "ZZZQ" if the location is classified at a higher level than is appropriate for the unit's report or if the location cannot be disclosed. NetUSR's lookup feature enables users to enter a code and/or a general description (for example, the country, state, city, and so forth,) for the current location and then applies this user entered information to create a comprehensive listing containing all of the proximate codes and possible locations so that the user can verify and/or identify the correct code and/or the specific location information, respectively. When the user confirms or identifies the correct code and current location from this listing, NETUSR will populate the CULOC data field and the remaining data fields in this section, except for the location classification, with the applicable information.

(2) Post/base/city. Enter the post, base or city location that currently is applicable for the unit's location unless this data field has been populated following the use of NetUSR's lookup feature.

(3) State. Enter the state or territory that currently is applicable for the unit's location unless this data field has been populated following the use of NetUSR's lookup feature.

(4) Location classification. Enter the correct security classification data. Note that this data field indicates the security classification of the unit's current location, not the security classification of the report. All reports are classified; however, most current unit locations are not. Enter "ZZZQ" as the CULOC in the first data field in this section to indicate that the unit's current location is classified above the level appropriate for the report or that the unit's current location cannot be disclosed.

f. Unit commander section. This section establishes the identity and personal contact information of the current commander of the reporting unit. Routine access to this POC information is limited to the unit's chain of command and to HQDA (DAMO-ODR). Enter an AKO e-mail address unless an exception has been authorized by the ADCON authority at the ACOM/ASCC/DRU-level or, when applicable, the DARNG. All of the data fields in this section are mandatory, except that a DSN phone number and a SIRPNet email address are not required for commanders without access to DSN or to the SIPRNet, respectively. This section consists of the following data fields:

(1) Unit commander. Enter the current commander's full name and rank in this data field.

(2) Phone. Enter the complete commercial and DSN (if applicable) telephone number for the commander of the reporting unit.

(3) E-mail. Enter the complete NIPRNet (AKO) and (if applicable) SIPRNet (AKO-S) e-mail address of the commander of the reporting unit.

g. Point of contact section. This section establishes the identity and personal contact information of the individual who prepared and/or submitted the CUSR on behalf of the unit commander and/or the individual who is the POC for any technical issues involving the report. Routine access to this POC information is limited to the unit's chain of command and to HQDA (DAMO-ODR). Enter an AKO email address unless an exception has been authorized by the ADCON authority at the HQDA/ACOM/ASCC/DRU-Level or, when applicable, the DARNG. All of the data fields in this section are mandatory, except that a DSN phone number and a SIRPNet e-mail address are not required for POCs/submitters without access to DSN or to the SIPRNet, respectively. This section consists of the following data fields:

(1) Point of contact/submitter. Enter the POC/submitter's full name and rank in this data field.

(2) Phone. Enter the complete commercial and DSN (if applicable) telephone number of the POC and/or submitter.

(3) E-mail. Enter the complete NIPRNet (AKO) and (if applicable) SIPRNet (AKO-S) e-mail address of the POC and/or submitter.

4-3. Reporting subordinate relationships

a. General. The MTOE and/ or TDA document imported from Force Management System (FMS) by NetUSR to support CUSR preparation establishes the organic and formally assigned elements and the designed structure of parent units with AA-Level UICs. However, for major units (brigades, regiments, groups, BCTs, support brigades, and so forth) and major headquarters (modular division headquarters and corps headquarters) with FF-Level UICs, the designed structure of the organization is established by a separate table located at FMS. The FMS is the authoritative source of the designed structure of all units and NetUSR will auto-populate the organic and formally assigned relationships of some units based on the data imported from FMS. All organic and formally assigned units/elements that comprise the designed structure of a major unit or headquarters are considered to be under its command and administrative authority unless the organic or formally assigned units have been temporarily detached or unless ADCON authority has been reassigned via formal instructions or official orders. This paragraph explains procedures for reporting units with AA-Level UICs and FF-Level UICs to indicate their current command relationships and administrative authorities in the CUSR using NetUSR. The NetUSR Users Guide provides screenshot examples of notional data entries. AR 220-1 , paragraph 4-9 explains the implications of these command relationships and authorities to the readiness reporting process.

b. Procedures. The "Subordinate Unit Relationships" report is located at NetUSR's "Unit Information" tab. The following sub paragraphs explain the data entry procedures using NetUSR that enable reporting units to categorize their subordinate elements as follows: category #1: organic and formally assigned units/elements that comprise the reporting unit's designed/established structure; category #2: the current detachments from the reporting units designed/established structure; category #3: the current attachments to the reporting unit's designed/established structure; and category #4: any subordinate units/elements that do contribute to the reporting unit's ability to accomplish/provide its core functions or designed capabilities. This categorization enables the unit commander to clearly establish which assets are currently available to execute/provide the reporting unit's core functions or designed capabilities and, when applicable, accomplish its assigned missions. Subsequently, the measurements and assessments of the reporting unit's readiness and capability are based on or derived from these categorizations.

(1) Organic and formally assigned units that comprise the designed/established structure (category #1). Unless this data has been imported from FMS by NetUSR, reporting units must use NetUSR's "add unit" feature to create a by-UIC and by-name list of subordinate units that are organic or formally assigned to reporting unit. Enter the UICs (includes subunit UICs and DUICs) and unit names of these subordinate units and/or elements based on applicable force management policy publications, like TOE, MTOE/TDA, TPSN, or based on information or instructions from an authoritative source. This UIC/DUIC listing is intended to reflect the unit's designed and/or established structure to accomplish/provide core functions or designed capabilities. Note that the data imported from FMS cannot be edited. Units should use command channels to request that HQDA (DAMO-FM) correct erroneous data in FMS.

(a) For measured units with AA-Level UICs, organic and formally assigned subordinate units and/or elements generally are identified by subunit UICs on the unit's MTOE/TDA or by DUICs registered in the DRRS-Army database in accordance with AR 220-1 , chapter 6 and Part III of this publication.

(b) For major units and major headquarters with FF-Level UICs, subordinate units, and/or elements in the designed/established structure are determined in accordance with the applicable force management policy, publications, instructions or information (like TOE, TPSN, and so forth) or is specified by other authoritative sources; they may include AA-Level UICs, subunit UICs and/or DUICs. Note that entering subunit UICs or DUICs is unnecessary if these subordinate elements are themselves organic to an AA-Level UIC that is listed.

(2) Organic and formally assigned units that are currently detached (category #2). Use NetUSR's "add unit" feature to create a by-UIC and by-name list of organic or formally assigned units that currently are detached. Enter the UICs and/or DUICs of any units/elements that are included in the designed/established structure of the reporting unit/headquarters from category #1 that are presently detached and not currently under the command authority of the measured unit/headquarters. Detached units/elements should be considered as "not available" when the reporting unit determines the measurements and assessments for its core functions or designed capabilities and, when applicable, any assigned missions currently reportable in the CUSR. If appropriate, use a minus sign (-) to indicate that the detachment of an organic or formally assigned unit did not include all of its organic sub-elements.

(3) The OPCON units that are available to support core functions or designed capabilities (category #3). Use NetUSR's "add unit" feature to create a by-UIC and by-name list of units that currently are attached and support core functions or designed capabilities. In general, all elements currently under the command authority (includes organic, assigned, attached and OPCON) of the reporting unit contribute to readiness for all operational requirements and, therefore, are considered as available for both core functions or designed capabilities and assigned missions. Exceptions may apply in those situations when a command and control headquarters (for example, a corps and modular division headquarters or a functional brigade) may have subordinate elements temporarily under OPCON that do not contribute to the command and control mission for which the headquarters was designed. (Note that these exceptional OPCON augmentations are included in category #4 as explained in para (4), below.) Enter the UICs and/or DUICs of any augmenting units/elements that currently are under the command authority of the reporting unit/headquarters (attached or OPCON), unless these augmentations do not support the core functions or designed capabilities of the reporting unit. Subsequently, the units reported in this section should be considered as available and included in the readiness measurements and assessments for core functions or designed capabilities.

(4) The OPCON units that are not considered in the C-Level determination because they do not support the unit's core functions or designed capabilities (category #4). Use NetUSR's "add unit" feature to create a by-UIC and by-name list of OPCON augmentations that do not contribute to the execution of the core functions or designed capabilities of the reporting unit. Enter the UICs and/or DUICs of any subordinate units and/or elements that currently are under the OPCON of the reporting unit but that should not be considered in the measurements and assessments of its readiness to execute its core functions or designed capabilities due to restrictions, conditions, situations or specified exceptional circumstances. Reporting units should use this list to identify any exceptional OPCON alignments when including these OPCON units in the measurements and assessments of core functions or designed capabilities would distort the results. Some examples of possible use are as follows:

(a) By major headquarters while exercising OPCON authority over maneuver units that do not enhance the ability of the major headquarters to exercise battle command or to function as a command and control headquarters organization.

(b) By measured units with OPCON augmentations whose availability has been specifically restricted to an assigned mission or to a designated theater or area of operations.

(c) By measured units while exercising OPCON authority over units and/or elements assigned or attached to it solely because of geographical proximity or habitual association.

(d) By MTOE units while exercising OPCON authority over TDA units (includes augmentation table of distribution and allowances (AUG-TDA)).

(e) By Army measured units exercising OPCON authority over non-Army units/elements. Note that non-Army units/elements and resources are not considered when calculating the measured area levels; however, the capabilities provided by non-Army assets can be considered when determining whether or not upgrades/downgrades to the C-Level or the A-Level are warranted (also see AR 220-1 , app I).

c. Intent. The subordinate unit status data indicated on the four lists developed by the reporting unit in accordance with the above procedures is intended to provide visibility to important unit availability information relevant to the measurements and assessments determined and reported by the reporting unit. It also triggers various functions in NetUSR that automatically assist and/or enforce status reporting policy requirements. The organic and formally assigned units/elements comprising the designed/established structure in list #1 is intended to establish the basis (denominator) for the readiness measurements and assessments of core functions or designed capabilities. The detachments and attachments included on list #2 and list #3, respectively, are intended to establish the assets currently available (the numerators) for the reporting units for to accomplish/provide core functions or designed capabilities and, if applicable, assigned missions. Hence, unit readiness for core functions or designed capabilities is measured and assessed by comparing the currently available assets established by aggregating the units appearing on list #1 with those on list #2 (via addition) and list #3 (via subtraction) with the designed/established structure depicted on list #1. List #4 is for those exceptional situations when the OPCON augmentations do not contribute to unit readiness for core functions or designed capabilities. Note that while the units included on category #4 should not be considered in the readiness measurements and assessments of the reporting unit's core functions or designed capabilities, it may be appropriate for the reporting unit to consider these OPCON augmentations in the measurements and assessments of the readiness of the reporting unit for an assigned mission, depending on the nature of the assigned mission and the OPCON circumstances. Appendix H outlines various deployment/employment scenarios to illustrate reporting options and possibilities.

Chapter 5

Determining and Reporting Personnel Data (see AR 220-1, para 9-2)

5-1. General

The level for personnel is the first of the four measured area levels that are the primary factors in determining a unit's overall C-Level. The NetUSR software application will import personnel data for each individual Soldier currently assigned or attached to the unit from the applicable authoritative personnel system or database. The personnel level (P-Level) is calculated by comparing the reporting unit's available strength, its available military occupational specialty qualification (MOSQ) strength by duty position (also known as DMOSQ in this publication), and its available senior grade strength with the required strength established in its formal requirements and authorizations document (MTOE or TDA). The results of these three computations are referred to in AR 220-1 and in this publication as the P-Level metrics. Several additional personnel status data points also are reported in the CUSR; however, these data points are not factored into the unit' s P-Level calculation and, thus, are not P-Level metrics. For CUSR purposes, Soldiers are considered to be "available" if they are attached or assigned to the measured unit, are physically present, or can be present within the prescribed mission alert or response time (72 hours unless specified otherwise) and are not restricted by Army policy from deploying or employing with the unit to accomplish the full spectrum operations for which it was designed. Personnel availability criteria are addressed in AR 220-1, paragraph 9-2 and are further explained in this chapter. When determining personnel status data for the CUSR, unit commanders will report Soldiers in the grade to which they are promotable. Additionally, unit commanders should not physically move Soldiers from one unit to another, breaking up cohesive groups, to cross-level solely for readiness status reporting purposes.

5-2. Determining and reporting the required strength

a. General. The required strength is established by the data entered in the requirements column of the unit's formal requirements and authorization document (MTOE or TDA). The required strength is the baseline (that is, the denominator) for each of the three P-Level metrics, except that for Army Medical Department (AMEDD) Professional Filler System (PROFIS) personnel, NetUSR uses the authorized strength as the denominator for calculations.

b. The NetUSR application will import from FMSWeb the required strength data indicated on the formal requirements and authorizations document (MTOE or TDA) that is currently applicable to the unit (cadre column for cadre units, TOE type B column for type B units, and MTOE/TDA required column for all other units). The required strength data imported by NetUSR is fixed based on the MTOE or TDA and cannot be adjusted by the unit. For MTOE organizations, additions provided by AUGTDA are excluded from required strength determinations.
Note.
AR 71-32 describes the purpose and use of an AUGTDA.

5-3. Determining and reporting the assigned strength

a. General. The assigned strength status reflects the number of personnel formally assigned to the unit by official orders. Some of the assignment criteria that are applicable to COMPO 1 units are different from the assignment criteria that are applicable to RC units, and several unique criteria apply to Active Guard and Reserve (AGR) and PROFIS personnel. This paragraph explains the procedures for determining and reporting assigned strength data in the CUSR, to include assigned strength reporting procedures unique to RC units and PROFIS personnel. Paragraph 5-4 explains the procedures for determining and reporting the available strength. The following basic procedures for determining and reporting assigned strength data apply to all units.

(1) All units compute the assigned strength percentage by considering as "assigned" only those personnel currently assigned to the unit by official orders.

(2) Personnel may be reported as being assigned by only one unit at any one time.

(3) Personnel attached to a unit via temporary change of station (TCS) orders will not be included in the assigned strength data reported by that unit.

(4) The assigned strength percentage equals the assigned strength divided by the required strength. The NetUSR application will import required strength data and assigned strength data from the applicable authoritative sources for reference and verification by the unit, respectively.

(5) The authoritative personnel system for COMPO 1 units is the Integrated Total Army Personnel Database (ITAPDB) for USAR units it is the Regional Level Application Software (RLAS); and for ARNG units, it is Standard Installation/Division Personnel System (SIDPERS).

(6) Assigned strength status is determined and reported in the CUSR for reference as a data point only. The assigned strength status is not a P-Level metric.

(7) All personnel assigned to a reporting unit should be slotted against a valid position in the unit. The unit will fully explain the reasons for any unslotted personnel assigned.

b. RC units.

(1) Assigned strength for USAR units includes AGR and COMPO 1 personnel assigned on a separate TDA who would have deployed with the unit if it had been mobilized on the "as of" date of the report.

(2) Inactive National Guard (ING) personnel are not included in assigned strength computations.

(3) USAR AMEDD units with personnel assigned to the unit and further attached to the national AMEDD augmentee detachment (NAAD) will count those personnel as assigned.

(4) USAR troop-program unit (TPU) attachments and RC Soldiers attached to units "for training only" will be included in the assigned strength data reported by their parent units. The unit of attachment will not include USAR TPU attachments or RC Soldiers "attached for training only" in the assigned strength data reported by the unit of attachment.

c. PROFIS personnel. The PROFIS personnel (officer and enlisted) are AMEDD personnel formally assigned to Medical Command (MEDCOM) who currently are designated by name for attachment to a supported unit under alert, deployment, or combat conditions. When determining the assigned strength computation in the CUSR for PROFIS personnel, the following guidelines will be used:

(1) PROFIS personnel will be included in the assigned strength data determined and reported by the MEDCOM units, to include the time periods during which the PROFIS personnel are attached for deployment to the PROFIS supported unit via TCS orders.

(2) Units designated for PROFIS support, to include deploying and/or mobilizing units, will not include PROFIS personnel in their assigned strength computations.

(3) Commanders of PROFIS supported units will use the current PROFIS roster from the OTSG MODS-approved PROFIS automated database to identify PROFIS personnel designated for required MTOE positions. The PROFIS roster must be updated monthly and must be dated within 30 days of the CUSR "as-of" date. The same PROFIS individual will not be designated for more than one unit.

5-4. Determining and reporting the available strength

a. General.

(1) For CUSR purposes, the available strength is the portion of the unit's assigned strength and attachments, to include individual Soldier augmentations that are considered available for deployment or employment with the unit to accomplish the full spectrum operations for which the unit was designed. The available strength percentage is determined by dividing the available strength by the required strength. The available strength percentage is a P-Level metric.

(2) Commanders of reporting units that are deployed or that have deployed elements or individuals must determine if HQDA (DAMO-ODR) or the responsible ACOM, ASCC, DRU, and/or DARNG/NGB ADCON authority has established and disseminated any policy guidance applicable to their specific deployment(s) that supplement the instructions in AR 220-1 and/or the procedures in this DA Pam. This supplemental policy guidance may provide additional information regarding timelines for disengagement, recovery, post-deployment training, reconstitution, and redeployment, and they may include specific instructions to assist commanders in determining the availability for CUSR purposes of their subordinate elements, personnel, and equipment, to include rear detachments. The responsible ACOM, ASCC, DRU, and/or DARNG/NGB ADCON authority will insert comments in the CUSR of the measured unit or forward separate correspondence to HQDA (DAMO-ODR) to explain any supplemental guidance impacting on the determination of personnel availability that has been provided to the measured unit.

(3) Unless HQDA (DAMO-ODR) or the responsible ACOM, ASCC, DRU, and/or DARNG/NGB ADCON authority has prescribed otherwise in formal guidance, individual personnel who are currently assigned to a parent unit but who are attached to another unit under TCS orders or who are in units or sub elements currently located away from and outside of the command authority of their parent units will be counted as assigned but not available by the parent unit. (Note that the TCS criterion is applicable to the deployment of individual Soldiers only.) The deploying/mobilizing (gaining) unit, if applicable, will not count TCS attached Soldiers as assigned, but it will count them as available (unless other non-availability factors established in table 5-1 apply). Available strength may exceed assigned strength in units with personnel augmentations, to include Soldiers attached via TCS orders. Also see AR 600-8-105 .

(4) Individual mobilization augmentees (IMAs) assigned by orders to the measured unit (does not include IMAs assigned for training only) will be reported as available by the unit of assignment, unless they are determined to be unavailable based on the personnel availability criteria established in table 5-1.

(5) The USAR troop-program unit (TPU) attachments and RC Soldiers attached to units "for training only" will be reported by their parent units as available for deployment and mobilization; the unit of attachment will not count or report USAR TPU attachments or RC Soldiers "attached for training only" as available.

(6) Commanders with subordinate units/elements that are deployed separately will indicate the number of deployed Soldiers in personnel reporting remarks.

(7) As units progress through the ARFORGEN force pools, MEDCOM will designate PROFIS personnel by name via the MODS. MTOE units will identify and report PROFIS personnel as "available" using the MODS PROFIS roster as a source document. This PROFIS roster must be dated within 30 days of the CUSR "as of date."

(a) Per AR 601-142, MEDCOM has the responsibility to ensure that designated fillers are qualified in their areas of concentration (AOC)/military occupational specialty (MOS); are appropriately credentialed, privileged, and licensed in accordance with AR 40-68 ; and are prepared to deploy in accordance with AR 600-8-101 .

(b) The MEDCOM units will not report PROFIS personnel as available. MEDCOM units will use nonavailable reason code "PF" to identify currently assigned and on-hand MEDCOM personnel who are reported as nonavailable due to PROFIS. MEDCOM units will use "TC" non-availability reason code when PROFIS personnel are attached via TCS orders to the PROFIS supported unit.

(8) Soldiers stabilized in accordance with the Army stabilization policy will not be considered and reported as non-available due solely to this stabilization. Unless they are determined to be unavailable based on the personnel availability criteria established in table 5-1 , stabilized personnel will be considered and reported as available.

(9) When directed by headquarters at higher levels, the number of Soldiers that are pending separation will be reported in personnel status remarks. While "Pending ETS" is no longer a valid reason for non availability and there is no reason code for "Pending ETS" in the CUSR, a Soldier who has begun transition leave and who will not be recalled to the unit by the commander before the termination of service will be reported as "not available" under personnel availability code "LS." See table 5-1, note 14.

(10) Specific guidance regarding the availability of Soldiers during contingency operations and mobilization is in AR 600-8-101 and AR 614-30 . Soldier availability is directly linked to command emphasis of the Soldier readiness, mobilization, and deployment process. Commanders are responsible to conduct SRC to determine actions required to ensure Soldier availability and in order to comply with Soldier Readiness Program and Mobilization requirements as outlined in chapter 4 of AR 600-8-101 .

b. Commander oversight requirements. Command oversight of critical Soldier readiness programs such as Individual Medical Readiness (IMR) directly impact and contribute to unit readiness. The IMR module of the MEDPROS provides visibility to the medical and dental readiness data that is recorded in authoritative databases for individual Soldiers, units, and task forces. However, the unit status report is a commander's report, and commanders are responsible to report the most accurate information available to them at the time reports are prepared. If discrepancies in the MEDPROS data are identified and confirmed by the unit commander, then the commander should direct personnel within their unit with MEDPROS "write access" to update the data within MEDPROS. If the data element cannot be updated by unit personnel, then the commander should coordinate with the local medical treatment facility to update the MEDPROS data.

c. Determining personnel availability.

(1) The P-Level in the CUSR is determined by comparing that portion of the unit's required strength that is considered as "available" In accordance with CUSR personnel availability criteria with the strength requirements established for the unit in its formal requirements and authorization document (MTOE or TDA). Although, the personnel availability criteria established in this publication for CUSR purposes are intended to indicate and/or project the number of Soldiers that currently are available to reporting units for deployment/employment to accomplish/provide their core functions or designed capabilities, they may not accurately or precisely represent the ability of a specific Soldier to be deployed to or to be mobilized for (applicable to RC only) a specific area or for a specific contingency operation. When used in this publication in the context of readiness reporting, the terms "available" and "availability" specifically address the most common requirements, conditions and/or circumstances that, solely for CUSR purposes, are applicable to individual Soldiers. These personnel availability criteria provide the necessary benchmarks that all reporting units can apply uniformly to determine and report their unit' s P-Levels in the CUSR. Although many of the personnel availability criteria explained in this publication closely approximate criteria for individual medical readiness and Soldier deployability contained in other publications, the provision in this publication are authoritative only for unit status reporting purposes, and they do not supersede or override the provisions in the authoritative publications that govern medical readiness and personnel deployability. The terms "available," "deployable" and "medically ready" often are confused, misunderstood and misused; however, the distinctions between these terms are noteworthy and meaningful. The following explanations are provided to assist unit commanders in understanding these distinctions so that their determinations of personnel availability for CUSR purposes are not misinterpreted, misrepresented or misused.

(a) Available and availability. AR 220-1 , paragraph 2-1 explains that the term "availability," when used in the context of unit status reporting, indicates those unit resources, to include subordinate elements, personnel and equipment, that currently are possessed or controlled by the reporting unit or, when applicable, are available to it within 72 hours that, in accordance with the relevant criteria, are qualified, ready and/or available to the unit to meet operational requirements. The "availability" status of Soldiers is compared to the unit's MTOE or TDA personnel requirements and is considered by the unit commander when calculating the unit' s P-Level. Soldier availability is determined based on both medical and administrative criteria and is directly impacted by command emphasis of the Soldier readiness, mobilization and deployment processes.

(b) Deployable and deployability.The term "deployment" is defined in the DOD dictionary ( JP 1-02) as follows: "The movement of forces within operational areas. The positioning of forces into a formation for battle. The relocation of forces and materiel to desired operational areas. Deployment encompasses all activities from origin or home station through destination, specifically including intracontinental United States, inter-theater, and intratheater movement legs, staging, and holding areas." While there is no formal definition of deployable or non-deployable, it is generally understood that "non deployable" for personnel management purposes describes a servicemember who is unable to deploy to a specified area of operation as an individual or as part of a unit, and that a "deployable" servicemember is able to deploy to a specific area of operation as an individual or as part of a unit. Specific policies and procedures for determining the ability of an individual Soldier to deploy to a specific location or for a specific contingency operation are contained in AR 614-30 , AR 600-8-101 , DA Pam 600-8-101, Army Personnel Policy Guidance (PPG), and other personnel management publications. In some cases, directives promulgated by the combatant commander or the other external authorities (for example, execute orders, OSD memorandums, and so forth) may establish additional criteria for specific deployments or supplant Army requirements. Generally, the "deployability" status of Soldiers is compared to the assigned mission manning requirements and is considered by the unit commander when calculating the unit's Assigned Mission Manning (AMM) level.

(c) Medically ready. AR 40-501 governs medical fitness standards for enlistment, induction, appointment, officer procurement programs, retention, separation and retirement. It also governs medical fitness standards for specific duty assignments or activities (for example, diving, Special Forces, Airborne, Ranger, free fall parachute training and duty, certain enlisted MOSs, officer assignments, aviation, and so forth) and physical profiles. Although not specifically defined in this publication, the term "medically ready" is associated with the four individual medical readiness (MR) categories which are well defined by medical/dental condition/deficiency and the time period required to correct any deficiencies. Although Soldiers classified as either MR1 or MR2 in MEDPROS in accordance with the provisions of AR 40-501 are considered "GREEN" and medically ready, only Soldiers classified as MR1 are deemed as "fully medically ready."

(2) To facilitate the accurate determination of Soldier availability for the P-Level measurement, NetUSR imports medical/dental and administrative data for each Soldier assigned to a reporting unit from ADS. However, personnel availability is not synonymous with personnel deployability or with medical readiness as defined or explained above. All Soldiers determined as "available" for CUSR purposes in accordance with the personnel availability criteria contained in this publication may not be "deployable" to a specific area or for a specific contingency based on the deployment criteria that apply and that may differ by location, by contingency and other circumstances. Also, all personnel considered medically ready (for example, MR1 or MR2 in MEDPROS) may not be determined as available for CUSR purposes due to administrative reasons or externally directed requirements. Similarly, some personnel designated as not deployable and/or not medically ready could be determined and reported as available for CUSR purposes because the specific criteria governing their medical readiness or personnel deployability are not included in CUSR availability criteria. For example, AR 220-1 establishes that Soldiers classified as MR2 or MR4 will be reported as "available" in the CUSR. However, this CUSR availability status does not allow the unit commander to deploy these Soldiers before they have received the medical/dental treatments or items they require or before they have completed the required medical/dental examinations.

(3) Commanders will conduct Soldier Readiness Checks to determine actions required to enhance Soldier availability determinations and will comply with Soldier Readiness Program and Mobilization requirements as outlined in AR 600-8-101 , chapter 4 . Command oversight of critical Soldier readiness programs, such as Individual Medical Readiness (IMR), directly impact and contribute to unit readiness. The IMR module of the MEDPROS provides visibility to the medical and dental readiness data that is recorded in authoritative databases for individual Soldiers, units, and task forces.

(4) Use the decision matrix in table 5-1 to determine personnel availability for CUSR purposes. Not all categories and non-availability reason codes will apply to every force structure component. For example, the non-availability reason codes explained at Part II, category #14 in table 5-1 apply only to RC and multiple component units and the "PF" (PROFIS) non availability reason code in category #15 is applicable to MEDCOM units only. Note that the legal processing (LP) and parenthood (PH) nonavailability reason codes previously in effect have been replaced by new codes that provide greater specificity and that the 7E code indicating less than 7 days to expiration term of service (ETS) has been eliminated. Additionally, to avoid double counting in the CUSR, Soldiers who were not available to their units for more than one of the reasons listed in table 5-1 were reported previously in only one medical category in Part I and one administrative category in Part II. If more than one of the non availability codes in the administrative categories in Part II applied to the same Soldier, then commander reported the Soldier as not available under the reason code that most accurately depicted the compelling, dominant or decisive medical or administrative reason for non-availability (that is, the most difficult administrative non-availability factor to resolve). However, the NetUSR software application has been updated to enable commanders to indicate in their reports each reason that an individual Soldier is not available; therefore, commanders will report accordingly.

Table 5-1. Determining personnel availability-decision matrix (to determine if individual Soldiers in various situations should be reported as available in the commander's unit status report)
PART I: Individual Medical Readiness Classifications Available
a. Medical Readiness Class 1 (MR1)- "fully medically ready" YES 1
b. Medical Readiness Class 2 (MR2) - "medically ready within 72 hours" YES 2
c. Medical Readiness Class 3A (MR3A) - "medically ready within 30 days" NO 3
d. Medical Readiness Class 3B (MR3B) - "medical requirements will take more than 30 days to correct" NO 3
e. Medical Readiness Class 4 (MR4) - "medical readiness requirement deficiencies are considered to be in an indeterminate status" YES 4
PART II: Administrative Categories and Non-availability Reason Codes Available
1. Legal processing category (formerly the LP category)
a. Arrest and confinement (LR) NO 5
b. Pending military or civil court action (LZ) NO 5
c. Under investigation by a military/civil/criminal investigation activity (LI) NO 5
d. Pending administrative/legal discharge or separation (LD) NO 5
2. Absent without leave category (AW) NO
3. Deployed category (DP) NO 6
4. Temporary change of station category (TC) NO 7
5. Parenthood category (formerly PH)
a. Postpartum Operational Deferment (PD) NO 8
b. Adoption (PA) NO 8
6. Minimum training for deployment not completed category (TN) NO 9
7. Family Care Plan category (FP) NO
8. Lautenberg Amendment category (LA) NO 10
9. Missing/prisoner of war category (MP) NO
10. Sole surviving family member category (SS) NO 11
11. Child Soldier Protocol-Soldiers Under 18 category (CS) NO 12
12. Leave/TDY category
a. Ordinary Leave/TDY (LT) YES 13
b. Transition Leave (LS) NO 14
13. Conscientious objector category (CO) YES 15
14. The following categories and situations are applicable to RC and multiple-component units only:
a. Assigned, not joined category (AN) NO 16
b. Unsatisfactory participant category (UP) NO 17
c. Simultaneous Membership Program category (SM) NO
ARNG YES
Assuming temporary tour of active duty YES
Assuming PRC YES
USAR YES
Designated on critical list assuming temporary tour of active duty YES
Assuming PRC NO 18
Education Career Stabilization (EC)
15. PROFIS category (PF) NO 19
PART III: Rear Detachment Codes The rear detachment codes reported in the CUSR are listed and explained at the DRRS-Army Portal. Not applicable
(See note #20)

Notes:
1.
AR 40-501 establishes and defines the Medical Readiness Classifications. Soldiers in Medical Readiness Class 1 (MR1) are "fully medically ready" in accordance with the provisions of AR 40-501 and, for CUSR purposes, MR1 Soldiers will be reported as available (unless administrative non-available criteria in Part II apply). MEDPROS is the authoritative source for the MR1 status of individual medical readiness, and MEDPROS data will be used to auto-populate the medical readiness status box in NetUSR for each Soldier indicated as MR1.
2. AR 40-501 establishes and defines the Medical Readiness Classifications. Soldiers in MR2 are "medically ready with 72 hours" in accordance with the provisions of AR 40-501 and, for CUSR purposes, MR2 Soldiers will be reported as available (unless administrative non-available criteria in Part II apply). MEDPROS is the authoritative source for the MR2 status of individual medical readiness, and MEDPROS data will be used to auto-populate the medical readiness status box in NetUSR for each Soldier indicated as MR2. NOTE: Reporting MR2 Soldiers as available in the CUSR does not authorize the commander to deploy these Soldiers before they have received the medical and/or dental treatments or items required for deployment (for example, immunizations, medical warning tags, HIV or DNA lab tests, and so forth).
3. AR 40-501 establishes and defines the Medical Readiness Classifications. Soldiers in MR3A are "medically ready" within 30 days. Soldiers in MR3B have medical readiness requirements that need longer than 30 days to correct. Soldiers in MR3A and MR3B will be reported as not available.
4. AR 40-501 establishes and defines the Medical Readiness Classifications. Soldiers in MR4 have "medical readiness requirements that are considered to be in an indeterminate status." Soldiers in MR4 will be reported as available in the CUSR unless an appropriate medical authority has indicated in writing that the Soldier should not be deployed with his unit. NOTE: Reporting MR4 Soldiers as available in the CUSR does not authorize the commander to deploy these Soldiers before they have completed the required medical and dental examinations.
5. Generally NO; however, can be YES if, in coordination with the servicing OTJAG, the unit commander determines that the pending legal action does not preclude the Soldier from deploying with the unit.
6. Usually NO; however, can be YES, if in the judgment of the commander, the individual can return and meet an operational deployment requirement. When determining whether or not the Soldier can return, the commander must consider the type of deployment the Soldier is on, the proximity of the deployed location to the parent unit's location, and the approval authority for the Soldier's early return to the parent unit. If YES is determined for deployed/mobilized personnel, then the parent unit must coordinate directly with the unit of attachment to preclude double counting of the Soldier's availability. (For CUSR purposes, only one unit can count an individual Soldier as an available resource on a given as of date.) Also see Note #7.
7. Individual Soldiers who are currently away from their parent units in accordance with TCS orders will be considered assigned, but not available to the parent unit for CUSR purposes. Accordingly, the gaining units will consider these Soldiers as available but not as assigned.
8. The parenthood category includes Soldiers who become parents and are non-deployable solely due to administrative vice medical reasons. The parenthood category does not apply to a Soldier who is pregnant or during the designated postpartum period when the Soldier should be considered as nonavailable for CUSR purposes due to a temporary profile that is addressed in one of the individual medical readiness classifications in Part I. The "PD" code is applicable to a military mother of a new born, following the period for which the postpartum physical profile is effective, who remains non-deployable for an additional period due operational deferment following child birth. The "PA" code is applicable to one member of a military couple or a single parent seeking to adopt a child who is nondeployable for a specified period from the date the child is scheduled to be officially placed in the home pending adoption. The duration of the operational deferment applicable to a military mother due to childbirth and the non-deployable time period applicable to a military parent seeking to adopt are established by AR 614-30 and AR 600-8-101 .
9. Applicable to Soldiers who have not completed officer basic course (OBC), warrant officer basic course (WOBC), or initial entry training (IET) requirement or its equivalent.
10. Applicable to Soldiers known to have, or Soldiers whom commanders have reasonable cause to believe have, a conviction of a misdemeanor or felony crime of domestic violence and hence are restricted from possessing firearms or ammunition.
11. A Soldier may waive the deployment restriction in accordance with AR 614-30, paragraph 3-8 .
12. Child Soldier Treaty signed by the President of the United States (POTUS) in July 2000 and ratified by the U.S. Senate in June 2002 prohibits Soldiers under the age of 18 from direct participation in hostilities. Hence, Soldiers who are currently under the age of 18 will not be considered available.
13. Generally YES; will be NO only if highly exceptional circumstances will prevent the Soldier from being recalled from ordinary leave/temporary duty (TDY) in order to meet the unit's operational deployment requirements or if exceptional circumstances will prevent the Soldier from rejoining the unit in order to meet the unit's specific mission requirements. HQDA considers " within 72 hours" as reasonable criteria for Soldier recall from ordinary leave; however, the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, may establish more demanding criteria for their rapidly deployable, forward stationed or special mission units. Also see Note #14.
14. Generally NO, but can be YES for Soldiers during the first weeks of their terminal leave prior to separation. Use the "LS" nonavailability code ILO the "LT" code for Soldiers currently on Transition leave when the commander will not call them back from terminal leave for deployment with the unit.
15. Soldier`s who have submitted a conscientious objector application will continue to be available for deployment in connection with a contingency operation or selective/partial/full/total mobilization except as follows: Soldiers with an approved conscientious objector (1-0) status will not be deployable and will be allowed to continue processing for discharge. The General Court-Martial Convening Authority (GCMCA) may, at its discretion, excuse the Soldier from deployment when the Soldier has an application pending at the Department of the Army Conscientious Objector Review Board. Once a Soldier submits a formal application for conscientious objector status under the provisions of AR 600-43 , the Soldier's eligibility for OCONUS deployments, not ordered in connection with contingency operations or selective/partial/full mobilization, will be determined in accordance with AR 614-30 .
16. An Army reservist or Army guardsman 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.
17. A Soldier is not available beginning on the date the Soldier attained his or her ninth unexcused absence, or the date the Soldier is determined to be an unsatisfactory participant for failing to attend or complete the entire period of annual training (see AR 135-91 , para 4-12).
18. Currently NO but could be YES. In accordance with the provisions of AR 601-210 , USAR Soldiers selecting the Army Reserve Education Career Stabilization enlistment option will complete up to four years of post-secondary education in a non-deployable status. While this stabilization exemption currently applies to OND/OEF, it does not apply to future mobilizations initiated under Presidential authority. The stabilization period is based on unit priority and length of enlistment.
19. The MEDCOM units will use this code to identify Soldiers reported as not available due to PROFIS designation.
20. Rear detachment codes are listed and explained at the DRRS-Army Portal. These codes are applicable to deploying and deployed units ONLY, and they are used ONLY to indicate the reason(s) that a Soldier who is assigned/attached to a deploying/deployed unit will be or has been left behind in the rear detachment. The codes at the DRRS-Army Portal replicate those established and used in EMILPO for use by deploying/deployed units in the rear detachment reports that they submit separately to Army personnel managers. These rear detachment codes are NOT non-availability reason codes for use to explain why Soldiers are not available and they may not be used by units that have NOT been formally alerted for deployment or that currently are NOT deployed. While many Soldiers will remain behind or have been left in rear detachments because of the same factors that cause them to be non-available, a Soldier in the rear detachment is not unavailable to his unit (for CUSR purposes) solely because he will be or is in the unit's rear detachment. One or more valid and applicable non-availability reason codes listed in Part I and/or Part II of this table must be selected and reported by the unit to explain the non-availability factor(s) for each Soldier (includes Soldiers who are in or are projected to be in the rear detachment) who is reported as non-available. Unit commanders will use their remarks to clearly explain why any available Soldier will be or is in the unit's rear detachment.



Figure 5-1. Determining and reporting the assigned and available strength


5-5. Determining and reporting the percentage for available military occupational specialty qualification by duty position

a. The available MOSQ strength by duty position (also known as DMOSQ) reflects those assigned and attached Soldiers who are available and who possess the training and skills necessary to perform effectively in the duty positions to which they are currently slotted. The percentage of available MOSQ Soldiers by duty position is calculated by dividing the number of assigned and attached Soldiers who are MOSQ by duty position and currently available by the required strength. The Soldier's availability status is determined in accordance with paragraph 5-4 , above. The Soldier's qualification status for the duty military occupational specialty (DMOS) is determined in accordance with the provisions of paragraph 5-5 c , below. Both the current availability of the Soldier and his qualification for the assigned duty position (DMOS) are applicable to this P-Level metric. Note that the NetUSR software will import MOSQ and duty positon assignment data from ADS to facilitate the slotting of individual Soldiers to the specific duty positions for which they are trained and qualified by their units. Because the MOSQ data on RC Soldiers imported by NetUSR from RC ADS can indicate MOSQ by RC Soldiers prior to their completion of the training required for formal MOS qualification, the NetUSR software will allow reporting units to adjust the imported MOSQ status data of their Soldiers slotted against positions in pay grade of E3 so that units can accurately report MOSQ status data. This adjustment feature is limited to pay grade E3 only and is intended primarily for use by COMPO 2 and COMPO 3 units to correct erroneous MOSQ data imported from RC ADS; however, it is available for use by units in all COMPOs and can also be used to address security clearance issues (see para g ).

b. For CUSR purposes, a Soldier possessing the required MOS (includes either additional military occupational specialty code (MOSC) or secondary MOSC) indicated in the unit's formal requirements and authorizations document (MTOE or TDA) for his current assigned duty position or who holds one of the MOS's formally designated and directed for substitution by HQDA (DAMO-FMF) will be counted as qualified in the DMOSQ P-level metric. Required duty MOS's are indicated in the unit's formal requirements and authorizations document (MTOE or TDA). Unless specified otherwise by HQDA (DAMO-ODR or DAMO-FMF) for CUSR purposes, this DMOS qualification is applicable to a Soldier serving in a duty position up to two grades higher or one grade lower than the Soldier's current grade. The authoritative listing of HQDA-directed MOS substitutions will be published and maintained by DCS, G-3/5/7 (DAMO-FMF) at FMSWeb at https://fmsweb.army.mil and also will be accessible for reference via the NetUSR portal. The commander of the reporting unit will review and apply this mandatory guidance. The ADCON authority at the next higher level will validate that the MOS substitutions applied by the commander comply with HQDA's mandatory guidance. Commanders will indicate in their remarks any subjective assessments of MOS qualification that are at variance with the HQDA requirements and will consider their subjective assessments of duty MOS qualification when determining whether or not the overall C-Level should be upgraded or downgraded. The commander's subjective assessments of duty MOS qualification will have no bearing on the P-Level that is objectively calculated based on the MOS (additionally awarded military occupational specialty code (AMOSC)/ secondary military occupational specialty code (SMOSC)) matches and the MOS substitutions mandated by HQDA. Similarly, skill qualifications identifier (SQI), SSI, and specific language requirements will not be considered in determining the DMOSQ percentage (except in the case of AMEDD personnel and units) but will be considered in the C-Level determination.

c. The available duty military occupational specialty qualified (DMOSQ) personnel percentage (MSPER data field label) is based on a comparison of available DMOSQ personnel and required DMOSQ personnel. Available DMOSQ strength cannot exceed available strength. Additionally, Soldiers slotted to positions in excess of 100 percent of the manning requirement for that position have no impact on the P-Level determination. For example, the NetUSR software will calculate 100 percent DMOSQ for a position requiring 5 Soldiers even if the unit slots 10 Soldiers against that position. Accordingly, to enhance personnel readiness units with assigned Soldiers with a primary MOS that exceeds the unit's documented manning requirements should slot the excess Soldiers in vacant position based on the Soldier's secondary or additional MOS's if applicable. See paragraph h . The following process will be used to determine and report the available DMOSQ percentage.

(1) Determine the number of MTOE personnel spaces required by rank (commissioned officer, warrant officer, and enlisted) and by MOSC.

(2) Determine the number of personnel included in the available strength of the unit by rank and MOSC. Match the qualified available personnel against requirements. Personnel are considered DMOSQ for purposes of the CUSR as follows:

(a) Match officers to officer spaces on a one-for-one basis. Officers are considered DMOSQ when they have completed an officer basic course and have the minimum skills needed to perform the mission-required duties of their assigned position. AMEDD officers, to include AMEDD officers in clinical specialties and PROFIS, must be qualified in their areas of concentration (AOC) for their positions and must have been awarded the AOC. 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 AR 40-68 . For AMEDD officers, the SQI and additional skill identifier (ASI) will be considered in determining the MOSQ level. If shortages of SQIs and ASIs are degrading readiness, remarks are required.

(b) Based on the first four characters of the MOSC, warrant officers are considered DMOSQ when they are used in their primary military occupational specialty code (PMOSC), SMOSC, additional MOSC (AMOSC), or a MOSC that can be substituted for the above in accordance with AR 600-100 . AMEDD warrant officers must be AOC qualified for their assigned duty position. Warrant officer PROFIS are considered qualified for the position to which they are assigned.

(c) Based on the first three characters of the MOSC, the utilization guidance in AR 614-200 , paragraphs 3-10 a (10) and d (7), and HQDA (DAMO-FMF) guidelines for MOS substitutions, enlisted Soldiers are considered DMOS-qualified when they are used in their PMOSC, SMOSC, AMOSC, or a MOSC that can be substituted for the above in accordance with MOS substitutions mandated by HQDA (DAPE-MPE). AMEDD enlisted Soldiers must be MOS qualified for their positions. Enlisted PROFIS are considered qualified for the position to which they are assigned.

(d) If a SQI or ASI is specified in formal requirements and authorizations documents (MTOE or TDA), it will not be considered in determining a unit's DMOSQ level, except in the case of AMEDD units and personnel, where it will be considered. 1.

(1) However, if a commander considers the SQI, or ASI, to be essential to the completion of assigned wartime or primary missions, and the Soldier in this position does not have the required skill, then this issue will be considered by the commander in determining a unit's training and overall category level.

(2) If shortages of SQI and ASI Soldiers are degrading the readiness of a measured unit, this will be addressed in the 2ADDSKILL set of the report.

(e) For units with officer and enlisted language requirements, language proficiency required for DMOSQ will be determined and reported in accordance with the following guidelines:

(1) Linguists are considered MOSQ by duty position, provided they meet the Army minimum language proficiency standard in accordance with AR 611-6 , in the language of the position in which they are slotted. This standard is measured by maintaining a current ( within 12 months) score of two in listening and two in either reading or speaking on the DLPT or oral proficiency interview (OPI).

(2) Soldiers in career management fields (CMFs) 18, 37, or 38, areas of concentration 180, functional area (FA)/ branch 38 or 39 are considered MOSQ, regardless of their demonstrated proficiency in any language.

(3) The proficiency status of assigned linguists by language identification code (LIC) and the unit's current assigned language requirements will be reported in the CUSR. This data is reported in the CUSR for information and analysis at higher levels, to include HQDA. Reporting this language information is mandatory for all measured units with officer or enlisted language requirements, to include Army Staff MOSs/CMFs/FAs.

(4) If a commander considers the LIC to be essential to the completion of assigned wartime or primary missions and the Soldier in this position does not have the required skill, the commander will consider this training deficiency in determining the unit's training level and the overall category level.

(f) RC personnel awaiting initial active duty training (IADT) and prior service personnel in MOS-producing training are not considered available DMOS-qualified for the duty position until they have successfully completed the required training for the assigned duty position.

(g) Personnel who have successfully completed a MOS awarding program for the assigned duty position may be counted as MOSQ for CUSR purposes. This includes Soldiers who have submitted a proper request for the granting of a MOS based on civilian-acquired skills in accordance with AR 601-210 , paragraph 7, DA Pam 600-3, or similar guidance. RC personnel who have not been officially awarded the MOS owing to administrative delays may be counted as DMOSQ. RC prior service personnel in MOS-producing training will not be considered DMOSQ until they have successfully completed the required training. The following special provisions are applicable to positions coded for pay grade E3.

(1) For Soldiers in positions coded for pay grade E3 who have completed MOS training but have not been granted the security clearance required for award of the MOS, the commander will report the Soldier as DMOS-unqualified for the assigned position unless, in the commander's assessment, the absence of the security clearance does not prevent the Soldier from accomplishing the requirements of the duty position. Commanders will use remarks to explain such assessments.

(2) Similarly, for Soldiers in positions coded for pay grade E3 that require a security clearance or who are assigned to a site requiring a security clearance, the commander will report a Soldier slotted in the position as DMOS-unqualified pending receipt of the final required security clearance unless, in the commander's assessment, the absence of the security clearance does not prevent the Soldier from accomplishing the requirements of the duty position. Commanders will use remarks to explain such assessments.

(h) Personnel who are over strength in a specific skill will not be counted as DMOS-qualified. Any personnel holding a PMOS that is surplus to measured unit requirements and who have been awarded an SMOSC, AMOSC, or a substitute MOSC that matches a unit required vacancy will be counted against that vacancy as DMOS qualified. For example, if a unit's MTOE requires four cooks, but it has 6 MOS-qualified cooks in its available strength, the reporting unit should count only four against the requirement for cooks. However, if any of the cooks have an SMOSC or AMOSC of truck driver, and if truck driver required vacancies exist in the unit, then the unit will count the two remaining cooks as available DMOS-qualified drivers. However, the available DMOSQ percentage cannot be greater than 100 percent.

(i) PROFIS personnel will be considered MOS qualified per criteria in paragraph 5-5 c (2)(a) .

5-6. Determining and reporting the available senior grade composite level

a. General. The available senior grade composite level is the level resulting from the aggregation of the discrete levels determined for each of the five categories of senior grade personnel junior noncommissioned officer (NCO) (E4{Promotable}/E5 - E6), senior NCO (E6{P}/E7-E9), warrant officer (WO1 - CW5), junior officer (O1-O3) and senior officer (03{P}/O4 - O6). An available senior grade strength percentage is determined for each applicable senior grade category by dividing the number of available senior grade personnel in the category by the number of senior grade position requirements applicable to that category. The senior grade requirements for each category are derived from unit's formal requirements and authorizations document (MTOE or TDA). Both the availability status and the promotion status of the Soldier are considered in the determination of each senior grade category level. Subsequently, the senior grade composite level is determined by averaging the applicable category levels and then applying the results in a reference table to identify the composite level.

b. Business rules. The following business rules apply:

(1) Units must identify each of their promotable Soldiers. Promotable Soldiers will be considered in their promotable grades, even if this action moves the Soldiers to another senior grade category, unless this action results in an over strength status at the higher senior grade category and an under strength status at the lower senior grade category. For example E6(P)s would be considered in the senior NCO category, unless this consideration resulted in excess senior NCOs (more available than required) and a shortage of junior NCOs (fewer available than required). Both of these conditions must apply for a promo table E6 to be considered in the junior NCO category.

(2) The "two up" rule for Soldier utilization is not applicable to this metric and the "one down" rule is applicable only when there is a shortage at the lower grade in the lower senior grade category and an overage at the current grade and the higher senior grade category (both conditions must apply). For example, an E7 would be considered in the junior NCO category only if the unit was excess senior NCOs (more available than required) and (concurrently) there was a shortage of junior NCOs (fewer available than required). Note that this downward "cascading" is applicable only between the two NCO categories and between the two commissioned officer categories. For example, if the senior officer category is over strength and the junior officer category is under strength, then 04s will cascade downward to count against the unit's junior officer requirements. Similarly, if the senior NCO category is over strength and the junior NCO category is under strength, then E7s will cascade downward to count against the unit's junior NCO requirements. However, there is no cascading from officer to NCO categories and vice versa. Cascading is not applicable to the warrant officer category.

(3) A Soldier will be considered in only one senior grade category (no double counting).

(4) Levels for each senior grade category will be determined by dividing the number of Soldiers in the category by the number of required grades applicable to that category in accordance with the unit's MTOE and then applying the resulting percentage in a reference table to determine a level (1, 2, 3, or 4) for the category.

(5) The senior grade level will be determined by averaging the levels of the senior grade categories applicable to the unit and then applying the average calculated in a reference table to determine the "composite" senior grade level. Subsequently, these levels cannot be subjectively changed. Note that senior grade categories that are not applicable to the unit are not included in these calculations. For example, if no senior officers and no warrant officers were required in accordance with the unit's MTOE, then the number of applicable senior grade categories would be 3 versus 5.

c. Figure 5-2 outlines the senior grade categories and the unit P-Levels determined based on the averaging of the category P-Levels.



Figure 5-2. Senior grade categories and unit P-Levels


5-7. Determining and reporting the personnel level

a. General. The Personnel level (P-Level) reported by the measured unit will coincide with the lowest level determined for the available strength percentage, the available DMOSQ strength percentage and the available senior grade composite level in accordance with criteria in table 5-2 . Requirements for comments and other information and data are explained in paragraph 5-9 . The personnel level cannot be subjectively upgraded. Note that the following procedures apply to all reporting units (Operating Force and Generating force), unless exceptional procedures have been established or formally approved by HQDA (DAMO-ODR). For example, the exceptional procedures for determining the P-Level that apply to designated TDA units are explained at the DRRS-Army Portal.

Table 5-2. Metrics for determining the personnel level
Level Available strength Available DMOSQ Available Senior Grade
By Category Composite
1 100-90 percent 100-85 percent 100-85 percent 1.54 or less
2 89-80 84-75 percent 84-75 percent 1.55-2.44
3 79-70 percent 74-65 percent 74-65 percent 2.45-3.34
4 69 percent or less 64 percent or less 64 percent or less 3.35 or more

b. Process. Also see figure 5-3 .

(1) Automated process. The NetUSR software will auto-calculate the P-Level based on baseline data imported from authoritative data sources and the availability data entered by the unit commander. See the NetUSR Users Guide for detailed data entry instructions.

(2) Manual process. The P-Level can be manually calculated as follows: (Note: The following explanation of the manual process for calculating the P-Level is for illustration only. All units must use NetUSR to prepare and submit their CUSRs).

(a) Step 1. Use the MTOE to and CUSR personnel availability criteria to identify the unit's assigned strength, required strength, available strength and the available and required DMOSQ personnel.

(b) Step 2. Calculate the assigned strength percentage. Assigned strength percentage = Assigned strength Required strength X 100. Note that the assigned strength percentage is a data point only and is not a P-Level metric.

(c) Step 3. Calculate the available strength percentage. Available strength percentage = Available strength Required strength X 100. Determine the available strength P-Level using table 5-2 .

(d) Step 4. Compute the available DMOSQ percentage. Available DMOSQ percentage = Available DMOSQ personnel Required DMOSQ personnel X 100. Determine the available DMOSQ P-level using table 5-2.

(e) Step 5. Determine the available senior-grade composite level using the business rules in paragraph 5-6 .

(f) Step 6. Determine the unit's overall P-Level. The lowest P-Level determined in steps 3, 4, and 5, above, is the unit's overall personnel P-Level unless HQDA (DAMO-ODR) and/or the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, directs or approves the use of a P-Level of P-5.

c. If the Personnel level is P-2, P-3, P-4, or P-5, enter the personnel code from table I-3c at the DRRS Army portal that indicates the main reason the personnel level is not 1.

d. If the Personnel level is P-6, then no reason code is required and this data field is left blank.

e. Similarly, personnel reason codes are not applicable to APS and will be left blank for APS.



Figure 5-3. P-Level process chart


5-8. Reporting personnel data points and Army unique requirements

a. General. Personnel data points provide additional information regarding personnel/manning issues; however, they do not directly impact on the unit' s P-Level determination.

b. Additional personnel data points.

(1) Personnel turnover percentage. This data point provides an indicator of unit turmoil that could degrade unit readiness and capability. The personnel turnover percentage is calculated by dividing the total number of departures during the 3 months preceding the as-of date of the report by the assigned strength on the as-of date of the report. Compute the personnel turnover percentage by dividing the total number of departures during the 3 months preceding the as-of date of the report by the assigned strength on the as-of date: total of personnel departed (90 days) divided by Assigned strength X 100. Reassignments of personnel within the measured unit are not included in turnover computations. The personnel turnover percentage is not a P-Level metric.

(2) Assigned/attached MOSQ strength by duty position. The assigned/attached MOSQ strength by duty position reflects those assigned and attached Soldiers (both available and not available to the unit) who possess the training and skills necessary to perform effectively in the duty positions to which they are currently slotted. For CUSR purposes, the assigned/attached MOSQ by duty position is calculated by dividing the number of assigned and attached DMOSQ Soldiers by the required strength. The assigned DMOSQ percentage is not a P-Level metric.

(3) Senior-grade strength. The assigned/attached senior grade strength reflects the number of senior personnel assigned and attached to the unit (both available and not available). The senior grade percentage is determined by dividing the number of assigned and attached commissioned officers, warrant officers (WOs), and noncommissioned officers (NCOs) ( grades E-4(P) through E-9) by the number of those senior-grade personnel required in accordance with the unit's formal requirements and authorizations document (MTOE or TDA). Commanders will report Soldiers in the grade to which they are promotable. The assigned/attached senior grade percentage is not a P-Level metric.

(4) Skill qualification identifier, SSI, and language qualifications. Data points indicating these skills and qualifications are reported for all assigned and attached personnel.

(5) Gender specific data points. Measured units are required to report the number of women Soldiers currently assigned/attached to the unit and the number of women Soldiers that are currently pregnant. While the availability status of these Soldiers also is addressed via the personnel availability criteria in table 5-1 , these data points are separate requirements that provide visibility to this specific information.

(6) Active Guard and Reserve data points. Measured units are required to report the number of guardsmen and reservists on active duty that are assigned to the unit.

(7) Level of Professional Military Education. The NetUSR software application will import professional military education (PME) achievement data on all Soldiers assigned to reporting units with AA-Level UICs (that is, battalions and separate companies) when it imports other authoritative data from ADS. Subsequently, NetUSR will display this PME achievement data for review by the reporting unit. Commanders of reporting units will update/correct the displayed data, if necessary. However, commanders should note that the updates/corrections to the displayed PME achievement data accomplished via NetUSR are for CUSR purposes ONLY, and that separate actions governed by the business rules established by the ADS are necessary to correct/update the actual records possessed by the ADS. Additionally, commanders will update the PME data imported from the ADS on the Soldiers assigned to their units ONLY after they have verified via their review of official documentation that the information obtained from the ADS is inaccurate. The official documentation required to support updates/corrections by commanders to the PME status data obtained from the ADS is limited to a formal DA Form 1059 s (Service School Academic Evaluation Report) and/or official correspondence from the applicable convening authority or board that specifically establishes that the Soldier successfully completed the training/schooling or received constructive credit. Following the commander's review and, if necessary, update/correction of the PME status data on Soldiers assigned to the unit, NetUSR will create a report reflecting the number by rank/grade of Soldiers (including commissioned officers, warrant officers and noncommissioned officers) in the unit that meet the requisite PME status level commensurate with their grade and responsibility level. Commanders of composite reporting units will review the PME achievement data reported by their subordinate elements and report aggregated PME achievement data in their composite reports. Table 5-3 and 5-4 depict the PME milestones established for each rank/grade for CUSR purposes. The PME milestones used in these tables do not supersede, revise or replace any requirements or guidance from HRC, DCS, G-1, or the unit's chain of command regarding personnel policy or promotions. They simply set the data points reported by units for compilation at HQDA-level to assess PME achievement across the Army. Note that adjustments to the PME milestones in tables 5-3 and 5-4 and to consider time in grade/date of rank factors are planned and will be announced at the DRRS-Army portal prior to their application. Detailed reporting procedures are explained in the NetUSR User's Guide and user help screens.

Table 5-3. Commensurate professional military education milestones for commissioned and warrant officers by rank/grade
Rank/Grade Commensurate PME Status
COL/O6 Senior Service College (SSC)
LTC/05 Intermediate Level Education (ILE) or Command & General Staff College (C&GSC)
MAJ/04 Intermediate Level Education (ILE) or Command & General Staff College (C&GSC)
CPT/03 Captains Career Course (CCC) or Officer Advanced Course (OAC)
1LT/02 Basic Officer Leader Course (BOLC) Phase II and III, or Officer Basic Course (OBC)
2LT/01 Basic Officer Leader Course (BOLC) Phase II and III, or Officer Basic Course (OBC)
CW5 Warrant Officer Senior Staff Course (WOSSC)
CW4 Warrant Officer Staff Course (WOSC) or Intermediate Level Education ILE
CW3 Warrant Officer Advanced Course (WOAC)
CW2 Warrant Officer Basic Course (WOBC)
WO1 Warrant Officer Basic Course (WOBC)


Table 5-4. Commensurate professional military education milestones for noncommissioned officers by rank and/or grade
Rank/grade Commensurate PME Status
SGM/E9 Sergeants Major Course (SMC)
MSG/E8 Senior Leader Course (SLC) or Advanced Noncommissioned Officer Course (ANCOC)
SFC/E7 Senior Leader Course (SLC) or Advanced Noncommissioned Officer Course (ANCOC)
SSG/E6 Advanced Leader Course (ALC) or Basic Noncommissioned Officer Course (BNCOC)
SGT/E5 Warrior Leader Course (WLC) or Primary Leadership Development Course (PLDC)

5-9. Providing mandatory and optional personnel remarks and comments

a. General. Units can report additional information and provide remarks regarding any of the personnel data reported in the CUSR to focus attention on specific problem areas or to explain the mission readiness implications of current deficiencies. The information should be precise, concise and able to standalone. The following personnel matters require remarks:

b. Remarks regarding Soldier availability issues. Soldiers deployed away from and outside of the command authority of their parent units are considered unavailable by the parent unit, for CUSR purposes, unless the unit commander receives supplemental guidance indicating otherwise. If such supplemental guidance is provided, then the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, or the unit, when directed, will indicate that guidance by entering mandatory personnel remarks in accordance with paragraph 5-4 Commanders with assigned Soldiers that are deployed away from their units but considered available because of supplemental guidance will specify location and number of Soldiers deployed.

c. Remarks regarding Soldier skill qualification issues.

(1) The unit commander must identify his most critical MOS shortages using five-digit MOS codes. Consider MOSs of key positions when identifying critical MOS shortages. Key positions are those positions the commander has determined require unique training and/or a skill levels and are essential to the ability of the unit to accomplish/provide core functions or designed capabilities. Examples may include, but are not limited to, surgeons in hospitals, pilots in aviation units, fire direction center chiefs in artillery units, and master gunners in infantry and armor units. Commanders should provide specific comments to explain the significant effects of their critical shortages. (Example comment: "A shortage of 11B 2/3 severely hampers the ability to train at the squad/fire team level.") Also use remarks to identify or explain the number of Soldiers that are assigned to MTOE/TDA positions for which they are not MOS-qualified.

(2) While the NetUSR application will import information in personnel databases regarding ASI, SQI, and LIC for each Soldier assigned and/or attached to the unit, commanders should provide appropriate remarks to explain shortages and clarify their specific concerns. Additionally, security clearance requirements that impact on mission readiness should be addressed and explained.

Chapter 6

Determining and Reporting Equipment On-hand (Available) Status Data (See AR 220-1, para 9-3)

6-1. General

a. The S-Level (also known as the EOH level) is the second of the four measured area levels that are the primary factors in determining a unit's overall C-Level. The S-Level is calculated by separately comparing the quantities of mission essential equipment items that are established on the unit's MTOE and coded as ERC P (pacing item) or ERC A LINs and that currently are in the unit's possession and/or under its control (that is, available) with the corresponding quantities of ERC P (pacing items) and ERC A equipment items required in accordance with the unit's formal requirements and authorization document. The term "on hand" is widely used in the logistics community to reflect the items have been issued to units and/or that are accountable by them for supply or property book purposes, respectively, while the term "available" is specifically defined for CUSR purposes to require that the reporting unit possess or control the equipment items being included in the S-Level calculation. The distinctions between "availability" for CUSR purposes and "on hand" for supply and property accountability purposes are explained in AR 220-1 , paragraph 2-1. Because these terms were used interchangeably in previous editions of AR 220-1, there is occasional confusion regarding their meaning related to unit status reporting. To avoid further confusion the phraseology "on hand (available)" is used in this chapter to specifically indicate that the equipment items under discussion are currently in the possession of the reporting unit, currently controlled by the reporting unit and/or can be made available to it for operation use within 72 hours. Examples and illustrations are provided at appendix H .

b. Pacing items are those major weapon systems, aircraft, and other equipment items that are central to the organization's ability to accomplish/provide core functions or designed capabilities, and therefore, are subject to continuous monitoring and management at all levels of command. Because the equipment items listed on TDA documents are not currently ERC coded, those TDA equipment items listed in the MMDF will continue to be considered as ERC A for CUSR purposes, unless supplemental guidance developed by the ACOM, ASCC, DRU, or DARNG and approved by HQDA (DAMO-ODR) establishes otherwise. ACOMs, ASCCs, DRUs, and/or DARNG/NGB-level ADCON authorities that require more definitive readiness coding of equipment items in their TDA units and organizations to accommodate unique command requirements may establish additional readiness coding criteria in a supplement to this regulation that would be applicable only to their units. Supplements to AR 220-1 require formal approval by HQDA (DAMO-ODR).

c. HQDA (DAMO-FMF), in coordination with TRADOC, establishes and maintains the authoritative listing of ERC P (pacing item) LINs for MTOE units at FMSWeb in accordance with guidance in this publication. Units may not independently change their ERC P (pacing item) LINs, but must inform the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, if they believe that discrepancies exist. The responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, will review the discrepancies indicated and initiate the correction of unit documents in coordination with HQDA (DAMO-FMF). Units will report all items as currently documented while awaiting correction of administrative errors. DAMO-FMF, with DAMO-FMO and DAMO-OD coordination, is the final approval authority regarding ERC determination.

d. Special considerations for CBRN equipment items and APS.

(1) While not a direct factor in determining the unit's overall S-Level, the CBRN S-Level also is determined and reported in the CUSR and may be considered by commanders when determining whether the unit's overall C-Level should be upgraded or downgraded.

(2) The APS custodians will calculate the S-Level for APS by comparing the fill level to the authorized column in the formal requirements and authorizations document (MTOE) for the APS. The unit's overall S-Level is equal to the lower of the ERC A/P or ERC P computations.

e. The unit's overall S-Level is determined by the procedures explained in paragraph 6-12 .

6-2. Determining and reporting equipment requirements and authorizations

a. The TAADS and/or FMS is the official record for all approved formal requirement and authorizations documents (MTOE or TDA) and, in case of conflict between this system and LOGTAADS provided to the PBUSE or other automated property book accounting system, use The Army Authorization Documents System (TAADS)/FMS information for CUSR purposes until the differences are resolved. The FMSWeb provides customer access to the TAADS and FMS databases. The responsible ACOM/ASCC/DRU and/or DARNG, when applicable, will inform DCS G-3/5/7 (DAMO-FMF), 400 Army Pentagon, Washington, DC 20310-0400 of any discrepancies requiring resolution.

b. As updates and changes to requirements and authorizations are published and provided to units, confusion often develops as to which requirements and authorization document (MTOE or TDA) the unit should use to calculate the S-Level status. In general, reporting units will measure and report readiness status against their currently effective MTOE/TDA document. However, units can report early against a future document if the unit more closely resembles that future document rather than the currently effective document, provided that the E-date for the future document is within one year and the responsible ACOM, ASSC, DRU or DARNG, when applicable, has specifically approved such action. Measured units will not be approved to report early against a MTOE or TDA if the overall S-Level would be degraded below S-3 and the measured unit could report S-3 or better under the currently effective document. Once a unit begins to report against a future MTOE or TDA (that is, in advance of the E-date), the previous document will not be used for further readiness status reporting unless specifically directed by the responsible ACOM/ASCC/DRU or DARNG when applicable. Units must use the same MTOE or TDA to determine their requirements for both personnel and equipment.

6-3. Determining reportable equipment

a. Reportable equipment. All of the equipment on a measured unit's formal requirements and authorization document (MTOE or TDA) is reportable in the CUSR. However, only the EOH statuses of equipment classification code (ERC) P (pacing items) and ERC A equipment items are considered in the S-Level calculation, and the procedures for determining the S-Level for MTOE units and for TDA units are not the same.

b. Modificiation table of organization and equipment procedures. The CUSR S-Level calculations for MTOE units will include the availability status of two categories of mission essential equipment items, ERC P and ERC A. Refer to the formal MTOE requirements and authorization document to determine the category of each item of equipment and the required quantity. Pacing items are determined by HQDA in accordance with the guidance and procedures prescribed in paragraph D-5 . The authoritative listing of pacing items is maintained on FMSWeb at https://fmsweb.army.mil . All pacing items listed on the MTOE are reportable and will be included in S-Level calculations, to include developmental line item number (Z-LIN) pacing items, unless specifically exempted by HQDA (DAMO-FMF) in accordance with the procedures prescribed in paragraph 6-4 .

c. Table of distribution and allowances procedures. For TDA units required to submit reports, the equipment designated in AR 700-138 , appendix B , will be considered as reportable for the S-Level determination until TDA equipment items are equipment readiness coded, unless the ACOM, ASCC, DRU (or DARNG for ARNG reporting units that are not on active duty) has provided supplemental guidance for identifying S-Level reportable equipment items. This supplemental guidance must be contained in a supplement to AR 220-1 that has been formally approved by HQDA (DAMO-ODR).

d. Figures 6-1 and 6-2 outline the methodologies for determining reportable equipment for MTOE and TDA units, respectively.



Figure 6-1. Reportable equipment methodology (MTOE Reporting Unit)





Figure 6-2. Reportable Equipment Methodology (TDA Reporting Unit)


6-4. Determining exempt/non-type classified Items

a. General.

(1) HQDA (DAMO-FMF) may identify certain categories of equipment and/or specific equipment items that are exempt from consideration and use in the S-Level calculations of reporting units. LIN exemptions approved or directed by HQDA (DAMO-FMF) may apply Armywide to all units or only to specified units, specified types of units or to units at specified locations; all LIN exemptions will apply for a specified time period. ACOMs, ASCCs, DRUs, and/or DARNG/NGB, when applicable, are not authorized to exempt LINs from unit status reporting.

(2) The LINs exempted from S-Level computations. A listing of LINs currently approved by HQDA for exemption from CUSR S-Level calculations is posted and maintained on the Force Management System Web site (FMSWeb at https://fmsweb.army.mil . The business rules for requesting and processing LIN exemptions also are provided at this Web site and are further explained in this paragraph and in appendix J . Access to the Web site requires a user-id and password that can be obtained as follows:

(a) On the main page, click on FMSWeb.

(b) Enter AKO user name and AKO password.

(c) The FMSWeb Account Request Form will be displayed

(d) Select the system access level of Normal FMSWeb access and click Continue.

(e) Type in your AKO user name and password again.

(f) From the drop down menu select your clearance level.

(g) Type in your security officer's name, phone number, and e-mail address, and click continue.

(h) Once your account has been approved, login using your AKO user name and password.

(i) Go to LOOKUP TOOLS.

(j) Go to ERC tables/readiness.

(k) Look under LIN exemptions.

(l) All items designated as "to accompany troops and/or not authorized pre-positioning" (to accompany troops and/or not authorized pre-positioning) in APS MTOEs are exempt from reporting regardless of S-Level.

b. Nontype classified items

(1) The MTOE/TDA changes or modernization of items may not always meet the unique requirements of the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable. Equipment procured to meet current mission requirements may be reported against the formally documented EOH requirements if the nontype classified item (NTCI) meets the following criteria:

(a) Has the same characteristics as the authorized item.

(b) Can be used in conjunction with other required items

(c) 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). A source of supply for replacement of the major end item must be available.

(d) Is planned for deployment with the unit to accomplish its wartime mission(s), if the authorized item is not available.

(2) The NTCI will be counted as equipment on hand for S-Level reporting purposes in accordance with criteria established in paragraph 6-3 . The NTCI may be reported against Army standard equipment until type classification is completed. The responsible ACOM/ASCC/DRU, and/or DARNG/NGB, when applicable, are responsible for initiating and monitoring type classification actions required to catalog/document the NTCI properly to the unit's MTOE, SB 700-20, and to ensure that it meets the Standard Army Management Information System supportability for equipment readiness. The NTCI may be used as substitute items in accordance with the provisions of paragraph 6-6 .

c. Nontype classified items, standalone systems. 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, these items may have the effect of an ERC A item on the unit's ability to accomplish its mission. The following guidance is applicable to NTCI in this category:

(1) The NTCIs developed and procured for a "standalone" system/item must have an LIN assigned by the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, and meet the criteria for ERC A, as outlined in appendix D , before it is reported in the CUSR.

(2) All NTCI items that meet the above criteria will be reported if the unit is short of the item and the absence of the item has an adverse effect on the unit's ability to accomplish its full spectrum mission. NTCI standalone reported will not be included in the S-Level or R-Level calculations.

(3) The NTCI standalone will be reported in S-Level remarks. As a minimum, the local LIN, noun nomenclature, and brief description of item's function will be included in the remarks.

d. Line item number exemption process. Figure 6-3 depicts the LIN exemption process. The business rules for LIN exemptions are explained in appendix J .



Figure 6-3. Line item number exemption request process


6-5. Obsolete equipment

a. Obsolete equipment items. Equipment items that have been formally designated obsolete by HQDA (DAMO-FMF and DALO-SUE) will not be considered in S-Level calculations, even if the obsolete equipment items remain in the possession of the reporting unit. Obsolescence can be formally designated for equipment items by LIN or by National Stock Number (NSN). Obsolescence by NSN is designated when multiple NSNs apply to one LIN and all of the NSNs under the LIN have not been designated as obsolete. In this situation, the LIN remains valid and cannot be formally designated as obsolete until all of its NSNs have been formally designated as obsolete. The following instructions apply to the situations indicated. Detailed procedures also are explained in the NetUSR user help screens.

b. Obsolete line item numbers. The DAMO-FMF will coordinate with the USAFMSA for the removal of obsolete LINs from the MTOEs and TDAs of units in the month following the formal designation of the LIN as obsolete or update to SB 700-20. If an obsolete LIN cannot be removed from MTOEs in a timely manner, it will be added to the LIN exemption list on FMSWeb in accordance with the provisions of paragraph 6-4 a (2). If necessary while MTOE/TDA updates are pending execution in TAADS/FMS, DAMO-FMF will use the exempt LIN process to exempt the obsolete LINs from further consideration in S-Level calculations if the MTOE cannot be updated prior to the next USR cycle.

c. Obsolete national stock numbers while the line item number remains valid. In situations where an equipment item with a NSN is formally designated as obsolete the unit commander will not consider or report the obsolete items as on-hand (available) in the S-Level calculated for the unit. If the equipment requirements indicated by LIN on the unit's MTOE/TDA remain valid, then the S-Level calculation for the LIN will be determined by dividing the number of on-hand (available) equipment items (do not include any obsolete items) by the MTOE/TDA requirement.

d. Coordinating instructions.

(1) The authoritative source of equipment item obsolescence is SB 700-20, chapter 2 ( EM 0007, currently published in Logistics Information Warehouse (LIW)).

(2) Do not report any obsolete items ILO any MTOE/TDA required item.

(3) Exemptions due to obsolescence are "total LIN exemptions" that apply regardless of the level of fill. See appendix J .

(4) Equipment items announced by HQDA as pending obsolete, terminal or other interim stage to obsolete, with or without a specific obsolete date, will continue to be reported in the CUSR if the items remain on-hand (available) to the unit and meet the authorized substitute or ILO criteria below.

6-6. Applying substitutes and in lieu of equipment

a. The number of equipment items for which a unit currently is accountable is determined by the property book or, for classified items only, by the communications security custodian, because accountable quantity and model information of classified communications security items are not authorized to be recorded on unclassified systems such as the property book. For CUSR purposes, the number of equipment items that currently is on hand (available) to a unit to accomplish its mission requirements are determined by the unit commander pursuant to the provisions of this paragraph. The commander will ensure that the unit's property book records are updated accordingly.

b. HQDA-authorized substitute equipment items.

(1) Authorized substitutes are those class VII equipment items prescribed by HQDA in accordance with the provisions explained in DA Pam 708-3, that, if currently on hand (available) in the unit, will be reported as on hand (available) in the CUSR in place of the Class VII equipment items required in accordance with the unit's formal requirements and authorizations document (MTOE or TDA).

(2) The authorized substitutes listed by LIN in SB 700-20, appendix H are selected based on their ability to fulfill the operational requirements established by the MTOE/TDA for the equipment item and logistical support ability. Recommended changes to SB 700-20, appendix H, may be submitted to the Office of the Deputy Chief of Staff Army G-4, (DALO-ORR), 500 Army Pentagon, Washington DC 20310-0500. Users may access SB 700-20 by going to the LIW Web site at: http://liw.logsa.army.mil , using either the " SB 700-20 Search" in the Catalog Module or conducting an item information search within Web LIDB\Query Database Module. The "SB 700-20 Search" also will provide a link to download the entire document as a zip file. First time users must register with LOGSA at the module provided on the Web site.

(3) When authorized substitutes are approved for issue on a greater than one-for-one basis, calculate an adjusted quantity of fill for the required LIN; then, compute the percentage of fill and determine the level for the required LIN, in accordance with the process explained in figure 6-1 and the NetUSR user help screens. Comments are required if the commander determines that there are problems of capability/compatibility caused by the mandatory use of a HQDA-authorized substitute equipment item. Possible problems could include a compatibility problem (with higher, supported, or supporting unit's interoperability) or a problem that degrades the measured unit's mission readiness.

c. The criteria for determining the authorized substitute items that are listed in SB 700-20, appendix H, is explained in AR 710-1 , paragraph 13-4.

d. In lieu of items are those on hand (available) equipment items, to include NTCI and non standard items, that do not have a valid substitute relationship reflected in SB 700-20, appendix H, but that the commander wishes to report as on hand (available) in place of an equipment item required in accordance with the unit's formal requirements and authorization document. In the opinion of the commander of the measured unit, subject to validation at the 06 command level, ILO equipment items must be able to perform as required by the measured unit's core functions or designed capabilities. Relevant factors impacting on the suitability of an equipment item under consideration for designation as an ILO equipment item include the availability of trained operators, trained maintenance personnel, necessary repair parts, ammunition and compatibility with other equipment. Additionally, the following criteria will be used when determining suitability of an item for reporting as ILO in the CUSR:

(1) Item must have the same characteristics as the authorized item, and it cannot be formally designated as obsolete by HQDA and/or be included in a "total LIN exemption" established by HQDA.

(2) Item can be used in conjunction with other items (for example, a tractor can haul an ILO 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). A source of supply for replacement of the major end item must be available.

(4) Item will be deployed with the unit to accomplish and/or provide the core functions or designed capabilities if the required item is not available.

(5) Any NTCI or non standard item reported as an ILO for CUSR purposes must be registered in SSN-LIN Automated Management and Integrating System (SLAMIS) with either a standard LIN or a non-standard LIN (NSLIN).

(6) If a modernization item of equipment or system is added to an requirements and authorization document to replace a current vintage item of equipment but the new item (or an authorized substitute from SB 700-20) is not fielded, the unit commander will designate the older item/system as ILO the new item for CUSR purposes if it meets the above criteria.

(7) If a modernization item of equipment or system has not been added to a requirements and authorization document and SB 700-20 has not been updated to include the item as an authorized substitute, but the new item has been fielded to replace the current vintage item of equipment, then the commander will designate the modernization item as ILO the vintage item for CUSR purposes.

(8) On hand (available) equipment items and/or systems considered for ILO designation by the unit commander for CUSR purposes must be evaluated on a system-for-system, function-for-function, or capability-for-capability basis. The unit commander's decision to report in the CUSR on hand (available) equipment items (ILO) in place of the required and documented equipment items must be specifically approved at the 06 command level. The responsible ACOM/ASCC/DRU and/or DARNG, when applicable, will ensure that subordinate units properly apply this ILO policy. For APS, headquarters (HQ), AMC must approve ILO items (except Class VIII, which will be approved by OTSG/USAMEDCOM).

e. The process for determining and reporting authorized substitute items is illustrated in figure 6-4 .



Figure 6-4. Authorized substitute and in lieu of equipment items


6-7. Evaluating component part availability

Reportable LINs having several components, for example, sets, kits, or outfits and/or medical materiel equipment sets (MMS/MES/DES/DMS/VES) will be reported as on hand (available) if property records show the LIN has been issued and at least 90 percent of each sets, kits, or outfits nonexpendable and durable items are present and serviceable. Do not count the set as on hand (available), if more than 10 percent of the nonexpendable and/or durable components are unserviceable, missing, depleted, or require supply action under AR 735-5 (for example, a Financial Liability Investigation of Property Loss). To ensure that non expendables and durables are the only items included in the calculation, all RC units will exclude all expendable and durable MMS/MES/DES/DMS/VES component items that have a shelf life less than 60 months (shelf life codes of A-H, J-M, P-R, or 1-9). COMPO 1, echelon III and IV medical units will exclude all expendable and durable items with a shelf life less than 60 months that are part of the Surgeon General's centralized contingency programs. The list of this materiel is available in SB 8-75-S7 and can be accessed on http://www.usamma.army.mil/ . It should be noted that The Surgeon General (TSG) Contingency Stocks Unit Deployment Packages (UDPs) are potency and dated items with a shelf life of less than 60 months for early deploying units (deploying prior to day 31 in a scenario) and for echelons above brigade units. This program does not support all echelons above brigade units. This program also does not support brigade combat teams.

6-8. Special reporting requirements applicable to Reserve Component equipment

The RC units will include all reportable equipment at equipment concentration sites (ECS), displaced equipment training centers (DETC), regional training sites-maintenance (RTS-M), regional training site-medical (RTS-MED), unit training equipment sites (UTES), mobility and training equipment sites, weekend training sites (WETS), and Area Maintenance Support Activities (AMSA).

6-9. Reporting equipment not on-site and/or not under control

a. Normally, the unit commander considers as available for CUSR purposes only those equipment items that currently are possessed by the unit or that currently are under its direct control (includes equipment items possessed/controlled by subordinate elements that are organic, attached, or OPCON). However, by exception and at the specific direction of the responsible ASCC, the unit commander can consider as available for CUSR purposes the assigned equipment that is part of an established plan that ensures the equipment will be deployed to meet the unit in theater or will be provided to the unit in theater. A system must be established to keep the commander informed as to the fill level and maintenance status of this theater provided equipment (TPE). In general, equipment that is not on site but remains under the control of the unit will be considered as available only if the unit commander has both the authority and the resources to transport or move the equipment to rejoin the unit at its current location in 72 hours or less in order to meet operational requirements. Note that equipment items stored at ECS that is designated for specific RC units are normally considered as available, regardless of the time period required to move these equipment items to the unit, because many of these equipment items will be moved directly to the mobilization station. The responsible ACOM, ASCC or DRU commander will provide supplemental guidance to address any exceptional circumstances.

b. Assigned equipment outside of the control of the measured unit that is not included in an established plan that ensures the availability of the equipment for mission requirements will not be counted as available, unless Headquarters, Department of the Army (HQDA) or the responsible ASCC has provided supplemental guidance indicating otherwise in accordance with AR 220-1 , paragraph 10-5. Examples include, but are not limited to, equipment left in theater by redeploying units for use by other units, equipment loaned to deploying units, equipment undergoing rebuild or remaining behind at the home station of deploying units, equipment projected for use by deploying units upon arrival in theater and/or centrally stored supplies and equipment. Equipment that is deployed with a subordinate element (DUIC) of the parent organization owning the equipment will be counted as available by the parent organization only if the subordinate element remains under the command authority of the parent organization or the responsible ASCC has so directed. Note that unit equipment that is in transit to join the unit, to include equipment on board ship, is normally considered as on hand (available) for CUSR. Reportable equipment that is not counted as on hand (available) by the unit to which the equipment is assigned will be reported as on-hand (available) by the unit physically in control of the equipment if a CUSR is required from the unit possessing the equipment.

c. While equipment items that are not on site or under the control of the unit fall into various categories, there are specific Army programs for APS, left behind equipment (LBE), and Theater Provided Equipment (TPE). Policies and procedures governing APS are contained in AR 710-1 , AR 220-1, paragraph 9-3 and paragraph 6-10 of this publication. The following provisions address the USR requirements associated with LBE and TPE.

(1) Left behind equipment. The LBE items are those equipment items assigned to a unit and only to that unit that will remain at the home station under the control of Army Materiel Command (AMC) for CONUS-based units or local command authority for OCONUS units while the unit is deployed. Retained LBE are those LBE items that are not reissued to a unit following its return from deployment due to a condensed dwell time, less than 18 months.

(a) Retained LBE will be considered in the EOH (available) calculations in the CUSR provided the following conditions are met:

(1) The unit is NOT currently deployed for an operational requirement. Unit deployments for training or to support civil authorities are not applicable.

(2) The LBE items are assigned to an LBE account established using a derivative UIC (DUIC) of the reporting unit. See AR 220-1, paragraph 4-3 b (2) and paragraph 14-6 h in this publication.

(3) The reporting unit is the sole claimant for the LBE items in its DUIC account.

(b) The NetUSR software application imports and displays asset data from all of the DUICs of a reporting unit (that is, a parent unit with an AA-Level UIC), to include the equipment in its LBE accounts.

(c) Reporting units will obtain from AMC ( for CONUS-based units) or from the the local command authority (for OCONUS units) the current maintenance status and Army Materiel Status System (AMSS) data for their retained LBE items and will incorporate the equipment serviceability status of these items in their R-Level measurements. Until the NetUSR application can import equipment serviceability information on LBE from LIW, the unit will manually enter the LBE serviceability status data provided from SAMS-E/AMSS readiness feeder reports when preparing their CUSRs using NetUSR. Units will obtain the SAM-E/AMSS readiness feeder reports from the AMC activity that is maintaining their LBE. The ACOMs, ASCCs, and DRUs with command or oversight responsibilities for units with equipment in LBE will coordinate with the LBE maintainer to establish the processes and procedures to facilitate receipt of these SAMS-E/AMSS reports.

(2) Theater Provided Equipment

(a) The TPE is equipment that a deploying unit will receive in theater following its deployment for an assigned mission. Unlike the equipment on the unit's MTOE/TDA that is focused on the unit's core functions and designed capabilities, TPE is specifically focused on the unit's assigned mission. When the TPE is physically possessed by the deployed unit (or can be made available to it within 72 hours), the TPE equipment items are considered as on hand (available) by the unit and reported for both its S-Level and AME level determinations unless specific guidance from the ASCC specifically directs otherwise.

(b) All DEFs with AA-Level UICs that are scheduled or programmed to receive TPE upon their deployment to conduct their assigned missions will determine and report an AME-level that is based ONLY on the mission required equipment that currently is possessed/controlled by the unit and that will deploy with it . This AME-Level is a "USR metric" that supports the unit's overall A-Level determination. The A-Level is an Army-unique overall assessment determined and reported by Army units ILO the PCTEF level required by GSORTS. See paragraph 9-4 and appendix C .

(c) Deploying units will determine and report an AME-Level projection that considers both the mission required equipment that currently is possessed/controlled by the unit and that will deploy with it plus any TPE that is projected to be made available to the unit upon its deployment. This AME-Level projection is a mandatory "USR data point" for deploying units that is NOT considered in the overall A-Level determination. Mandatory box checks and comments are provided in NetUSR to clearly indicate the basis for the unit' s AME-Level projection and to explain potential issues, problems or risks.

(1) Deploying units are required to determine and report an A-Level beginning at latest arrival date (LAD) minus 270 days, upon formal assignment of a mission that has been ordered for execution, when the focus of the unit's training shifts to the assigned mission, or when directed by the responsible ASCC, whichever event comes first and is applicable. While deployed, the unit continues to determine and report an A-Level that is based on the equipment items that are currently on hand (available) to include TPE.

(2) Deploying units will begin reporting AME-level projections at LAD minus 180; however, a deploying unit may begin reporting earlier following completion of a PDSS and/or formal coordination with the unit that it will replace in theater or when directed by the responsible ASCC. At LAD minus 180 deploying units will consider planned TPE items as not available and report an AME level projection reflecting this non-availability if the PDSS or formal coordination have not been accomplished.

(3) All DEFs with AA-Level UICs that are scheduled or programmed to receive equipment items in theater (that is, TPE) upon their deployment to conduct their assigned missions will consider that TPE in their AME level projections reported beginning at LAD minus 180 days; however, a deploying unit may begin reporting these TPE items earlier following completion of a PDSS and/or formal coordination with the unit that it will replace in theater or when directed by the responsible ASCC.

6-10. Loans from prepositioned stocks

a. The APS equipment deployed/loaned as a unit set, partial set, or task force package will be reported as EOH (available) by the using units that signed for the equipment. The using unit will include the transferred/loaned equipment in its S-Level computations. The EOH (available) quantity used to determine the S-Level for the APS will be reduced to reflect the transfer/loan. APS will report level 6 in accordance with the provisions of AR 220-1 , paragraph 4-6 and C5 in accordance with the provisions of AR 220-1, paragraph 4-8.

b. NetUSR auto-calculates the unit' s S-Level using the procedures in paragraph 6-12 .

6-11. Equipment readiness code and pacing items

The ERCs (includes ERC P-pacing items) are annotated on the unit's formal requirements and authorization document (MTOE or TDA). HQDA (DAMO-FMF), in coordination with TRADOC, establishes and maintains the authoritative listing of pacing items at FMSWeb in accordance with process explained below. Units may not independently change ERCs, but must inform the responsible ACOM, ASCC, DRU, and/or DARNG/NGB, when applicable, when discrepancies exist. The responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, will review discrepancies and initiate the correction of unit documents in coordination with and approval from HQDA (DAMO-FMF). Units will report in accordance with the existing document while awaiting correction of administrative errors. DAMO-FMF with DAMO-FMO and DAMO-OD coordination is the final approval authority regarding ERC determination. The definitions of the various equipment readiness codes and the processes for establishing and updating ERCs and pacing items are explained in appendix D .

6-12. Determining the S-Level

a. General. The EOH (available) status (S-Level) reported by the measured unit will coincide with the lowest level determined separately for each of the unit's ERC P (pacing item) LINs and for the unit's ERC A/P LINs (includes pacing items). Requirements for comments and other information and data are explained in paragraph 6-14 . The S-Level cannot be subjectively upgraded.

b. Processes. (See fig 6-5 )

(1) Automated process. The NetUSR software will auto-calculate the S-Level based on the requirements and accountability data imported from authoritative data sources and the availability data entered by the unit commander. See the NetUSR Users Guide for detailed data entry instructions.

(2) Manual process. The S-Level can be manually calculated as follows: (Note: The following explanation of the manual process for calculating the S-Level is provided only to illustrate the procedures implemented by the NetUSR software application. All units must use NetUSR to prepare and submit their CUSRs).

(a) Step 1.Identify the LINs and the required quantities of equipment items that are reportable and applicable, respectively, for the unit' s S-Level determination. For MTOE units, the ERC P/A LINs on the MTOE are reportable for the S-Level determination and the required quantity for each ERC P/A LIN is that quantity indicated on the MTOE. For TDA units, unless the responsible ACOM, ASCC, DRU or DARNG (for ARNG units) has prescribed otherwise in supplemental instructions formally approved by HQDA (DAMO-ODR), the LINs that are reportable for the S-Level determination are the same LINs that are reportable for maintenance in accordance with the provisions of AR 700-138 , and the required quantity for each reportable LIN is that quantity indicated on the TDA. If a LIN is coded as both an ERC P and ERC A, it will be counted as two separate LINs. For example, a Medium Truck Company may be required 60 tractors ERC P and one ERC A. For CUSR reporting purposes, these are considered as two separate LINs, one ERC P LIN with a required quantity of 60 and one ERC A LIN with a required quantity of 1.

(b) Step 2.Identify the quantities of equipment on hand (available) that will be counted against the required determined in step 1. Ensure authorized substitutes and ILO items are counted (see para 6-6 ).

(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. (Note that the rounding rule explained in paragraph 3-6 d applies to this calculation.) Then use table 6-1 to determine the S-Level for that LIN. Percent Fill = Equipment On hand (available) Equipment Required X 100.

(2) If the number of items required under a LIN is 20 or less, use table 6-2 to determine an S Level for that LIN. When counting substitute items on a greater than one-for-one basis refer to paragraph 6-6b(3) .

(3) Note that while S-5 and S-6 levels are applicable values for the unit' s S-Level determination, S-5 and S-6 are not applicable values for the S-Levels determined for individual LIN level calculations.

(d) Step 4.Based on the results of step 3 record the following: Total number of reportable ERC A/P = ____. 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. ( Number S-1 LINs total ERC A/P LINs) X 100 = ____ percent. ( Number S-2 LINs total ERC A/ P LINs) X 100 = ____ percent. ( Number S-3 LINs total ERC A/P LINs) X 100 = ____ percent. ( Number S-4 LINs total ERC A/P LINs) X 100 = ____ percent.

(f) Step 6.Calculate a separate equipment fill S-Level for each ERC P (pacing item) LIN (see para 6-11 ). (Disregard this step if the unit has no ERC P pacing items).

(1) Identify those LINs that are pacing items (that is, designated as ERC P on the unit's MTOE).

(2) Based on step 3, identify which of the ERC P (pacing item) LINs has the lowest calculated S-Level. This S-Level is the S-Level for the ERC P (pacing item) LINs.

(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 other than S-1. If so, the then the unit' s S-Level is equal to the S-Level determined in step 6 for ERC P (pacing item) LINs.

(2) S-2.If the percentage of S-1 LINs is less than 90 percent but the percentages of the S-1 LINs and the S-2 LINs ( step 5) collectively is equal to or greater than 80 percent, the unit' s S-Level is S-2, unless an ERC P (pacing item) LIN (see step 6) is lower (worse) than S-2. If so, then the unit' s S-Level is equal to the S-Level determined in step 6 for ERC P (pacing item) LINs.

(3) S-3.If the percentage of S-1 LINs plus the percentage of S-2 LINs is less than 80 percent, but the total of the percentages of S-1 LINs, S-2 LINs and S-3 LINs ( step 5) is equal to or greater than 65 percent, the unit S-Level is S-3, unless an ERC P (pacing item) LIN (see step 6) is S-4. If so, then the unit S-Level is equal to S-4.

(4) S-4.If any ERC P (pacing item) LIN is S4 or if the percentage of LINs that are S-3 or better (that is, S-1, S-2, or S-3) is 65 percent or less (or the percentage of S4 LINs is higher than 35 percent), then the unit S-Level is S-4.

(h) Step 8. If any LINs are on the unit's MTOE that are not designated as either ERC P or ERC A, then.identify these LINs (for example, ERC B/C LINs and/or any non standard LINs that are not listed in SB 700-20) and their required quantities.

(i) Note:."Total LIN exemptions" (for example, APS MTOE LINs that are to accompany troops/not authorizing pre-positioning) are not considered in the unit' s S-Level calculations, and "conditional LIN exemptions" are considered only if the S-Levels of these LINs is S3 or better. See paragraph 6-4 .

Table 6-1. Equipment on-hand metrics (high density line item numbers)
Step 1: By- LIN S-Level Metrics (ERC P and A LINs only)
By- LIN S-Level 1 2 3 4
Equipment items other than aircraft 100-90 percent 89-80 percent 79-65 percent Less than 65 percent
Aircraft 100-90 percent 89-80 percent 79-65 percent Less than 65 percent
Step 2: Unit S-Level Metrics (ERC P &A LINs only)
Unit S-Level 1 2 3 4
All units ERC P/A LINs @ S-1 = 90 percent and all ERC P LINs = S1 ERC P/A LINs @ S-1 + S2 = 80 percent and all ERC P LINs = S1 or S2 ERC P/A LINs @ S-1 + S2 + S3 = 65 percent and all ERC P LINs = S1, S2 or S3 ERC P/A LINs @ S-1 + S2 + S3 < 65 percent or any ERC P LIN @ S4
Note: S5 levels equate to S4, and S6 levels are not considered in step 1.


Table 6-2. Equipment on hand criteria (low density individual line item numbers, 20 or fewer items, includes pacing items)
LINs S-1 S-2 S-3 S-4 S-5
(Equipment) (Aircraft)
20 20-19 17-16 15-13 15-12 Less than:
13-Equipment
12-Aircraft
19 19-18 16-15 14-12 14-11 Less than:
12-Equipment
11-Aircraft
18 18-17 16-14 13-12 13-11 Less than
12-Equipment
11-Aircraft
17 17-16 15-14 13-11 13-10 Less than:
12-Equipment
11-Aircraft
16 16-15 14-13 12-10 12-10 Less than:
10-Equipment
10-Aircraft
15 15-14 13-12 11-10 11-9 Less than:
10-Equipment
9-Aircraft
14 14-13 12-11 10-9 10-8 Less than:
9-Equipment
8-Aircraft
13 13-12 11-10 9 9-8 Less than:
9-Equipment
8-Aircraft
12 12-11 10 9-8 9-7 Less than:
8-Equipment
7-Aircraft
11 11-10 9 8-7 8-7 Less than:
7-Equipment
7-Aircraft
10 10-9 8 7 7-6 Less than:
7-Equipment
6-Aircraft
9 9 8-7 6 6-5 Less than:
6-Equipment
5-Aircraft
8 8 7-6 5 5 Less than:
5-Equipment
5-Aircraft
7 7 6 5 5-4 Less than:
5-Equipment
4-Aircraft
6 6 5 4 4 Less than:
4-Equipment
4-Aircraft
5 5 4 4 3 Less than: 3- Equipment 3-Aircraft
4 4 3 2 2 1 or 0-Equipment 1 or 0-Aircraft
3 3 - 2 2 1 or 0-Equipment 1 or 0-Aircraft
2 2 - 1 1 0- Equipment 0-Aircraft
1 1 - - - 0- Equipment 0-Aircraft

(3) Figures 6-5 and 6-6 outlines the process and the metrics for determining the S-Level, respectively.



Figure 6-5. The S-Level Process





Figure 6-6. S-Level Criteria


6-13. Chemical, biological, radiological, and nuclear equipment items and the chemical, biological, radiological, and nuclear S-Level

a. Background. The CJCSI 3401.02B and CJCSM 3150.02B require measured units to determine and report an overall CBRN level, a CBRN S-Level and a CBRN T-Level). The data required to establish these CBRN levels is determined from the corresponding CBRN status data reported by Army units in the CUSR in accordance with the provisions of this AR 220-1 , paragraph 9-3 (the CBRN S-Level), paragraph 4-3 (the CBRN T-Level) and paragraph 4-4 (the overall CBRN-level) and the procedures in table 6-3 that also are explained via the NetUSR user help screens. Commanders assess the status of equipment and training in their units to determine the CBRN S-Level and the CBRN T-Level, respectively. The overall CBRN level is the lower (worst case) of these two levels, except that CBRN S-6 levels are discarded.

b. Procedures.

(1) To determine the unit's CBRN S-Level, assess the readiness of the unit to accomplish/provide its core functions or designed capabilities under chemical or biological conditions based on the availability and condition of required CBRN equipment and supplies. Determine equipment readiness/serviceability of available CBRN equipment and supplies in accordance with the applicable publication (that is, based on the fully mission capable (FMC) standard in the applicable technical manual-10/20 series). Commanders will consider as available only the CBRN equipment and supplies that are currently on hand (available) in the unit and/or that are currently under the control of the unit. Consider centrally stored CBRN equipment items and supplies earmarked for use by the unit as available and operational/serviceable only if so stipulated in formal command directives.

(2) The NetUSR software will automatically identify by LIN on the unit' s S-Level page each LIN on the unit's MTOE/TDA that has been designated by HQDA (DAMO-ODR) as a CBRN LIN. While unit's can designate additional CBRN LINs on this page if necessary, they cannot adjust the LIN designations established by HQDA. After the unit has determined the availability status of the MTOE/TDA required equipment items listed on its S-Level page, the status data for the designated CBRN LINs will populate the CBRN recap page. While commanders should closely review and carefully consider the CBRN status data at the CBRN recap page, the determination of the unit's CBRN S-Level results solely from the commander's subjective assessment in accordance the descriptive criteria provided in table 6-3 , below.

Table 6-3. Descriptive criteria for determining the chemical, biological, radiological, nuclear S-Level
CBRN
S-Level
Description
1 Sufficient operational/serviceable CBRN equipment and supplies are currently on hand or available to the unit to undertake the full wartime or primary mission for which it is organized or designed. The status of on hand or available CBRN equipment and supplies will neither limit flexibility in methods for mission accomplishment nor increase vulnerability of unit personnel or equipment. The unit does not require any CBRN equipment or supplies to correct deficiencies.
2 Sufficient operational/serviceable CBRN equipment and supplies are currently on hand or available to the unit to undertake most of the wartime or primary mission for which it is organized or designed. The status of on hand or available CBRN equipment and supplies may cause isolated decreases in flexibility in methods for mission accomplishment but will not increase vulnerability of unit personnel or equipment in most envisioned operational scenarios. The unit would require few, if any, items of CBRN equipment or supplies to correct deficiencies.
3 Sufficient operational/serviceable CBRN equipment and supplies are currently on hand or available to the unit to undertake many, but not all, portions of the wartime or primary mission for which it is organized or designed. The status of on hand or available CBRN equipment and supplies will result in a significant decrease in flexibility for mission accomplishment and will increase vulnerability of the unit under many, but not all, envisioned operational scenarios. The unit would require a significant number of CBRN equipment items or quantity of CBRN supplies to correct deficiencies.
4 An insufficient number of operational/serviceable CBRN equipment and/or inadequate quantity of CBRN supplies are on hand or available to the unit. The unit requires additional CBRN equipment and supply assets to undertake its wartime or primary mission, but may be directed to undertake portions of the wartime or primary mission at its current level of resourcing.
5 As the result of a HQDA directed resource action or program (for example, the Army's Chemical Defense Equipment Go-To-War Program) impacting on the availability to the unit of operational/serviceable CBRN equipment and supplies, the unit is not prepared to undertake its wartime or primary mission in an CBRN environment. Note: Reporting CBRN S-5 must be authorized by the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, and/or HQDA.
6 The readiness/serviceability and/or availability status of CBRN equipment or supplies required by the unit to operate and survive in a CBRN environment is not measurable or cannot be determined. Note: CBRN S-6 levels are discarded in determining the overall CBRN level. (Also see para 6-9 regarding equipment not on site.)

6-14. Providing remarks

Narrative S-Level remarks should address any resourcing issues that impact of the S-Level reported by the unit. Narrative remarks also should be provided to clarify any differences between the unit's EOH (available) status and its EOH (accountable) status (for example, to explain borrowed or loaned equipment) and to identify problems or trends. Remarks that do not add value to the report should be avoided (for example, merely repeating the measurements and assessments already reported by the unit do not add value to the report).

Chapter 7

Determining and Reporting Equipment Readiness (Serviceability) Status Data (see AR 220-1, para 9-4)

7-1. General

The level for ER is the third of the four measured area levels that are the primary factors in determining a unit's overall C-Level. The R-Level indicates how well the unit or organization is maintaining its on-hand equipment. For CUSR purposes, equipment is considered operationally ready if it is determined to be "FMC" in accordance with the standards prescribed in the applicable technical manual (see "not ready if" column of the preventative maintenance checks and services in the technical manual (TM)-10/20 series).

7-2. Determining maintenance reportable equipment

a. Equipment items that are reportable for maintenance are those designated as reportable in the most current version of the MMDF. The MMDF is maintained by the Army Materiel Command LOGSA under the direction of the Office of the Deputy Chief of Staff, G-4 (ODCS, G-4). LOGSA updates the MMDF quarterly and electronically publishes the most current version on its Web site at: https://www.logsa.army.mil/pam700/700-1.pdf#3_7 . Do not include RC Hospital Decrement or the AC deployed medical system hospital decrement equipment in calculations.

b. Because the R-Level includes all maintenance reportable equipment items that currently are possessed by the unit, to include equipment items that are not listed on its MTOE and/or that are not authorized substitutes or ILO equipment items for MTOE listed items, the readiness condition of mission required equipment items can be masked by the status of reportable but non essential equipment items. Hence, commanders should be especially careful to consider the readiness condition of mission essential equipment items and subjectively adjust (upgrade or downgrade) the overall C-Level status determination if necessary to accurately represent the unit's overall mission readiness.

c. A decision support chart illustrating the relationship and applicability of the various Army criteria for determining the equipment items whose operational status should be used in R-Level calculations is provided below. The NetUSR application automates and enforces these criteria.



Figure 7-1. Criteria for determining the equipment items that should be included in R-Level (ER) calculations


7-3. Determining the available hours and/or days

a. 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 standalone computation. Units that have a mix of equipment rated in hours and days will convert the available hours for equipment rated in hours to available days. Then add the days to the equipment rated in days in the "all on hand reportable equipment" calculation. Compute each pacing item separately, whether rated 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 ILO equipment. Substitute and ILO items of equipment included in the R-Level computation must meet the requirements for substitute and for ILO items per paragraph 6-6 . If a substitute or ILO item is not reportable under AR 700-138 , but is counted against a required and/or authorized LIN that is reportable in accordance with AR 700-138, take available hours/days for this equipment from DD Form 314 (Preventive Maintenance Schedule and Record) or AMSS feeder report. However, annotate these items only in the remarks block on DA Form 1352 (Army Aircraft Inventory, Status and Flying Time), DA Form 2406 (Materiel Condition Status Report), and DA Form 3266-1 (Army Missile Material Readiness Report) that are submitted to the Army Materiel Command LOGSA.

c. The NetUSR computes the available days for all on hand reportable equipment by adding the individual equipment item available days on the DA Form 2406 and DA Form 3266-1. The NetUSR computes the available hours or days for each pacing item of equipment on the DA Form 1352, DA Form 2406, or DA Form 3266-1. Days and hours are not combined.

7-4. Determining the R-Level

a. Reporting units and organizations determine and report an R-Level in the CUSR in accordance with the policy provisions in this AR 220-1 , paragraph 9-4 and the procedures explained in this chapter and the NetUSR user help screens. The R-Level is determined by commanders of measured units by calculating an aggregate R-Level that considers all maintenance reportable equipment in the unit's possession and then determining a separate R-Level for each maintenance reportable pacing item (ERC P) LIN. The measured unit's overall R-Level is determined by comparing the aggregate R-Level and the R-Levels for each maintenance reportable pacing item LIN. The measured unit's overall R-Level is equal to the lowest of these R-Levels. See table 7-1 . Note that reporting units are no longer authorized to report R5.

Table 7-1. Level for percentage of equipment fully mission capable
Level 1 2 3 4
Equipment other than aircraft 100-90 percent 89-70 percent 69-60 percent less than 60 percent
Aircraft 100-75 percent 74-60 percent 59-50 percent Less than 50 percent

b. Because units are required to submit their monthly materiel condition status report (MCSR) to LOGSA as part of CUSR procedures, detailed maintenance data by LIN is available for each unit in the authoritative Army databases for maintenance data. Hence, NetUSR requires that units address the specific readiness status of only their maintenance reportable pacing items at the LIN level of detail in the CUSR. However, commanders may elect or higher headquarters can direct their units to address equipment readiness at the LIN level of detail for other maintenance reportable equipment items in their possession to provide additional visibility to significant maintenance issues.

c. Because the equipment items listed on TDA documents are not currently ERC coded, those TDA equipment items listed in the MMDF have been and will continue to be considered as ERC A for CUSR purposes. ACOMs, ASCCs, DRUs and/ or DARNG-level organizations that require more definitive readiness coding of equipment items in their TDA units and organizations to accommodate unique command requirements may establish additional readiness coding criteria in a supplement to this regulation that would be applicable only to their units. Supplements to AR 220-1 require formal approval by HQDA (DAMO-ODR).

d. During peacetime, the R-Level computation will be based on available and possible hours/days, as determined from the AMSS Feeder Data to feeder reports, or the Installation Materiel Conditions Status Reporting System (IMCSRS), or from DA Forms 1352, 2406, or 3266-1, with the same cutoff date as the USR. During call up, mobilization, deployment or employment, an "as of" time procedure will be used.

e. The equipment readiness computation procedures for reportable medical equipment sets/assemblages are specified in AR 40-61 .

f. See the NetUSR Users Guide for the automated process.

g. The following explanation of the manual process is provided for illustration only. All units report using the automated procedures supported by NetUSR.

(1) 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 Unit Level Logistics System -A/G, printout if available.

(2) Step 2. Identify all LINs and list their possible time and available time in hours or days as appropriate.

(a) Include all on hand reportable items in the list (that is, ERC A/P, (ERC B or ERC C, if any), substitute, ILO, and excess) in accordance with AR 700-138 .

(b) Identify all ERC P LINs to include those not in AR 700-138. Items being held as substitutes or ILO items for a required pacing Item LIN, which meet the requirements for substitute and ILO will be counted as pacing items.

(c) If an item is an aircraft, note with "A/C."

(3) 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.)

(4) Step 4. Note which items are pacing items.

(5) Step 5. Compute a total of all possible equipment days or hours for each LIN.

(6) Step 6. Compute a total of all available (actual) equipment days or hours for each LIN.

(7) Step 7. For each pacing item LIN, 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.

(8) Step 8. Using table 7-1 , determine an R-Level for each pacing item LIN. Identify which pacing item LIN has the lowest R-Level.

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

(10) Step 10. Divide the total available equipment days by total possible equipment days. Multiply by 100 and round to the nearest whole number.

(11) Step 11. Using table 7-1 (equipment other than aircraft metric), determine an R-Level for total reportable equipment.

(12) 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 lower of the two levels. (See example in fig 7-2 ). Note that reporting R5 is no longer authorized.



Figure 7-2. Determining R-Levels for all reportable equipment (unclassified example)


7-5. Reporting the R-Level

Units are required to submit their monthly MCSR to LOGSA as part of CUSR procedures to ensure detailed maintenance data is available for each unit in the authoritative Army databases for maintenance data. See AR 700-138 regarding policy and procedures for MCSR submission. Accordingly, NetUSR requires that units report equipment readiness data at the LIN level of detail for pacing items only. Commanders may elect or their higher headquarters can direct them to report equipment readiness data at the LIN level of detail for other maintenance reportable equipment items on-hand in the unit in order to provide additional visibility to significant maintenance issues, respectively.

7-6. Mandatory data points and remarks for equipment readiness

a. Pacing items operational percentage. Units with pacing items will identify the equipment readiness percentage of each pacing item in a pacing item field (disregard if the unit has no pacing items).

b. Operational percentage. Commanders of battalion size or smaller units with an R-Level not equal to R1 will list the five most critical reportable LINs that reduce their R-Level below R-1. The LINs will be listed in descending order of criticality. Indicate S or M to designate whether the problem is primarily due to a maintenance work stoppage caused by a supply shortage (S) or a backlog of maintenance requirements (M).

c. Remarks. Narrative remarks also will be provided to clarify a unit's equipment readiness status.



Figure 7-3. The R-Level Process


Chapter 8

Determining and Reporting Training Data (see AR 220-1, para 9-5)

8-1. General

a. Overview. The level of unit training proficiency (T-Level) is the fourth of the four measured area levels that are the primary factors in determining a unit's overall C-Level. The T-Level reflects the commander's assessment of unit proficiency in its FSO METL tasks. Army measured units determine and report a T-Level in the CUSR in accordance with the policy provisions in AR 220-1 , paragraph 9-5 and the procedures explained in this chapter, the applicable NetUSR User Guide and online reference materials.

b. Key terminology.

(1) The "FSO METL" represents fundamental doctrinal tasks that like type units were designed to perform in a contemporary operational environment. It reflects the core functions and the fundamental capabilities that units were designed to accomplish and provide, respectively. Standardized FSO METL are developed and approved by DCS, G-3/5/7 for specific units. Units for which standard FSO METL is not applicable will develop FSO METL in accordance with Army training doctrine.

(2) "Assigned missions" are those operational requirements that have been directed by Army tasking authorities to specific units and formally ordered for execution or officially assigned for contingency planning/preparation (includes named operations, OPLANs, quick reaction forces, and so forth).

8-2. Basic policy and procedures for determining, assessing, and reporting full spectrum operations mission essential task list

(See app B .)

8-3. Determining the mission essential task list percentage for the T-Level determination

a. The T-Level that supports the overall C-Level determination is based on the T-METL percentage resulting from the commander's proficiency assessments of each of the unit's FSO METL tasks as either trained (T), needs practice (P) or untrained (U). Techniques for assessing METL are described at the Army Training Network (ATN). When assessing METL proficiency, commanders consider "Squad/Crew/Team/System" Manning and Qualification status as described in paragraph 8-5 and also consider the "Unit Proficiency Level" as described in paragraph 8-5.

b. If the unit is untrained (U) on any of its FSO METL tasks, then it cannot report T-1 or T-2. The T-METL percentage is auto-calculated by NetUSR after the commander enters his unit proficiency assessment for each of the unit's FSO METL tasks. The NetUSR uses the following methodology to calculate the T-METL percentage and to determine the corresponding T-Level.

(1) The FSO METL tasks assessed by the unit commander as T are multiplied by 3; FSO METL tasks assessed by the unit commander as P are multiplied by 2; and FSO METL tasks assessed by the unit commander as U are multiplied by 1; and then the results are summed.

(2) The total number of FSO METL tasks is multiplied by 3.

(3) The T-METL percentage is calculated by dividing the sum from (1) by the product from (2), then multiplying the result by 100.

(4) Subsequently, NetUSR determines the T-Level in accordance with the procedures explained in paragraph 8-4 .

8-4. Determining and reporting the training level

The T-Level is determined as follows:

a. When all FSO METL tasks are assessed as either "trained" (T) or "needs practice" (P) and no FSO METL task is assessed as "untrained" (U), then the T-Level is determined by applying the T-METL percentages in table 8-1 , below.

Table 8-1. Translating the T-mission essential task list percentage into a T-Level
T-METL percentage determined T-Level
85 percent or greater T-1 (no untrained tasks)
70 percent to 84 percent T-2 (no untrained tasks)
55 percent to 69 percent T-3
Less than 55 percent T-4

b. When one or more of the unit's FSO METL tasks is assessed as untrained (U) and the TMETL percentage for all FSO METL tasks is 55 percent or higher, then the T-Level will reported as T-3.

c. When one or more of the FSO METL task is assessed as untrained (U) and the TMETL percentage for all FSO METL tasks is less that 55 percent, then the T-Level will reported as T-4.

d. Note that remarks are required to explain any significant inconsistency between the T-Level assessments by units determined in accordance with the provisions of this chapter and their P-Level measurements determined in accordance with the provisions of chapter 5 (that is, T1/P4). See paragraph 8-8 .



Figure 8-1. T-Level process


8-5. Determining and reporting squad/crew/team/system manning and qualification

a. General. While assessing unit proficiency for the FSO METL (T-Level metric) and estimating training days (a training status data point), the commander considers and reports the training qualification status of designated entities applicable to his unit. Key command posts, battle staffs and emerging command and control systems have been added to the list of entities and systems for which manning and qualification data will be reported in the CUSR. In some cases, the number of authorized and reportable squads, crews or teams may vary from the number of required entities or systems determined from the MTOE. For example, continuous operations may require that a command post have two or more qualified crews or multiple crews may be designated for a single aircraft. The authorized and reportable number will reflect the number of squads, crews, teams for which manning and qualification status must be reported in accordance with Army doctrine or command guidance.

b. Reporting requirements. All units and organizations ( COMPO 1, COMPO 2, and COMPO 3) will report the manning and training qualification status of designated squads/crews/teams/systems, command posts and staffs if they are either required to man any of these entities or are equipped with any of the systems indicated in table 8-3 . Using the NetUSR software application, units will report as follows:

(1) Indicate the number of reportable squads/crews/teams/systems required by their MTOE/TDA. This number reflects the unit's wartime requirements and do not change unless the MTOE changes.

(2) Indicate the number of reportable squads/crews/teams/systems authorized by their MTOE/TDA. Manning and qualification status reporting is intended to indicate the status of training in the unit. Accordingly, when the number of authorized squads/crews/teams exceeds the number of authorized equipment systems, the unit will report the manning and qualification status of all squads/crews/teams (for example, if an AH-64 (Apache Attack Helicopter) equipped battalion is authorized 24 crews, but has only 18 aircraft, the unit will report the manning and qualification status for each of the 24 crews authorized).

c. Reportable categories. For each category in table 8-2 , units report the total number of authorized and reportable squads/crews/teams/systems listed in table 8-3 that meet both the manning and qualification criteria of that category. The total number of squads/crews/teams/systems reported in all categories should equal the number of authorized squads/crews/teams/systems reported.

(1) Commanders should include remarks to clarify the training proficiency status of their squads, crews and teams.

(2) For classification guidance, see chapter 13 .

d. DA Pam 350-38. Commanders will use standards in weapons training or proficiency standards for assigned individual and crew served weapons.

e. AR 11-6. Commanders will use this regulation to determine the qualification status of Army linguists (foreign language 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 Oral Proficiency Interview (OPI) in a foreign language.

f. AR 40-68. Commanders will use this regulation to determine the qualification status of Soldiers with MOS 68W (formerly MOS 91W). Additionally, use TC 8-800 to provide the basis for 68W sustainment training and validation. Use the 68W Tracking Model at https://apps.mods.army.mil/91/secured/ for transition and sustainment data input and guidance from the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable.

g. PROFIS guidance. Commanders of units with PROFIS should consider PROFIS training and any impact to METL proficiency.

Table 8-2. Reportable categories for authorized squads/crews/teams/systems
Manning criteria 1 Qualification criteria Report
Fully manned 2 Qualified 5 Number both FM & Q
Fully manned Combat capable 6 Number both FM & CC
Fully manned Unqualified Number both FM & U
Minimally manned 3 Combat capable Number both MM & CC
Minimally manned Unqualified Number both MM & U
Partially manned 4 Combat ineffective Number both PM & CI
Unmanned Combat ineffective Number U

Notes:
1. Manning a position. To 'man' a position, personnel must be both available and MOS-qualified. Available means that the Soldier meets the availability requirements of
paragraph 5-4 . MOS-qualified means that the Soldier has completed the training required for his grade in his military occupational specialty.
2. Fully manned squad/crew/team. Fully manned squad/crew/team standards are provided in table 8-3 . "Fully-Manned" standard is based on the manning requirement for specific elements or systems established in MTOE and/or Army training doctrine by TRADOC capability managers (USASOC for special operations forces unique elements/systems) and is intended to reflect a robust manning level for the specified element/system and to provide the requisite number of Soldiers to perform all critical war-fighting tasks during continuous (24-hour) operations.
3. Minimally manned squad/crew/team/system. Minimum manning standards are provided in table 8-3. Minimum squad/crew/team/system manning standards are established by TRADOC Capability Managers (USASOC for special operations forces unique elements/systems) and are intended to reflect the minimum number of Soldiers needed to perform most critical warfighting tasks to standard during continuous (24-hour) operations while accepting some risk in sustained mission accomplishment and/or force protection.
4. Partially manned squad/crew/team/system. Partially manned squads/crews/teams are considered combat ineffective.
5. Qualified. Individuals in key positions meet position qualification requirements prescribed in table 8-3 and the number of qualified Soldiers in the squad/crew/team/system is equal to or greater than the number of Soldiers required to meet the full manning standard.
6. Combat capable. Individuals in key positions meet position qualification requirements prescribed in table 8-3, and the number of qualified Soldiers in the squad/crew/team/system is equal to or greater than the number of Soldiers required to meet the minimal manning standard.


Table 8-3. Squad/crew/team/system manning and qualification criteria
Type
Squad/crew/team/system
Key individuals Fully manned/minimally manned levels Notes
M1 TC & gunner 4/3 number 1
M1 ABV Engineer; Driver & Vehicle CDR 2/2 number 4
M1 JAB Engineer; Driver & Vehicle CDR, Gunner 2/2 number 4
M2 Vehicle CDR & gunner 3/NA number 1 & number 16
M3 w/dismounts Vehicle CDR & gunner 5/4 number 1 & number 2
M3 w/o dismounts BC & gunner 4/NA number 1 & number 16
Infantry squad
(ABN/AASLT/RGR)
Squad LDR 9/7 number 2
Infantry squad (light) Squad leader 9/7 number 2
Infantry squad (M2) Squad leader 9/7 number 2
RECON squad Squad leader 5/4 number 2
HMMWV scout / BTR squad / LMTV squad Squad leader/gunner 3/NA number 2, number 16 & number 39
TOW section/squad SEC/SQD leader & gunner 3/NA number 3 & number 16
Combat engineer squad Squad leader 7/6 number 4
Wheeled engineer squad Squad leader 7/6 number 4
ODS-E Bradley Crew 4/3 number 4
MLRS (M270/M2701A1/HIMARS) Section chief & gunner 3/NA number 5 & number 16
Howitzer, M119/M102 Section chief & gunner 7/6 number 6
Howitzer, M109A3/4/5 Section chief & gunner 9/8 number 6
Howitzer, M109A6 Section chief & gunner 9/7 number 6 & number 17
Howitzer, M198 Section chief & gunner 10/9 number 6
Mortar, 120 mm Squad leader & gunner 5/4 number 7
Mortar, 81 mm Squad leader & gunner 4/3 number 7
Mortar, 60 mm Squad leader & gunner 2/NA number 7 & number 16
Stinger/Avenger Team chief & gunner 2/NA number 8 & number 16
BSFV Vehicle CDR & gunner 5/4 number 9
Patriot Crew 28/NA number 11 & number 16
AH-64A/D Pilot & co-pilot/gunner 2/NA number 12 & number 16
AH-1 Pilot & co-pilot/gunner 2/NA number 12 & number 16
OH-58A/C Pilot 1/NA number 13, number 16
OH-58D Pilot & co-pilot/gunner 2/NA number 12, number 16
UH-60 Pilot & co-pilot/crew chief/gunner 4/NA number 13 & number 16
CH-47 Pilot & co-pilot/crew chief/gunner 4/NA number 13 & number 16
UH-1H Pilot & co-pilot/crew chief/gunner 3/NA number 13 & number 16
MEDEVAC Pilot & co-pilot/crew chief/flight medic 4/NA number 13 & number 16
MQ-5B, Hunter Unmanned Aircraft Operator (AO), External Operator (EO), Mission Payload Operator (PO), Mission Commander (MC) 4/4 number 42
RQ-7B, Shadow-200 Unmanned Aircraft Operator (AO), Mission Payload Operator (PO), Mission Commander (MC) 3/3 number 42
SFODA Key leader 10/6 number 14
SOTA Key leader 4/3 number 14
CAT C Key leader 6/4 number 14
CAT B Key leader 4/3 number 14
CAT A Key leader 4/3 number 14
PSYOP DEV DET Key Leader 12/8 number 14
TAC PSYOP DET Key leader 13/8 number 14
TAC PSYOP Team Key leader 5/3 number 14
BIDS Team 4/2 number 15
M93 FOX NBCRS Commander, driver, 2 surveyors 4/ 3 number 18 & number 20
M93A1 FOX NBCRS Commander, driver, surveyor 3/NA number 16, number 18 & number 19
SBCT Infantry Company
Infantry squad
Weapons squad
XM1128 MGS crew
M1126 ICV crew
M1129 MC squad
Snipers

Squad leader, SDM
Squad leader
TC and gunner
Vehicle Cdr
Squad leader, gunner
Senior sniper, observer

9/7
7/6
4/3
2/NA
4/NA
3/2

number 21
number 23
number 22
number 16 & number 27
number 16 & number 26
number 28
SBCT Infantry Battalion
M1127 RV squad
M1129 MC squad
Snipers
M1133 MEV crew
M1130 CV crew
M1126 ICV crew
XM1128 MGS crew
M1131 FSV crew

Squad leader
Squad leader, gunner
Senior sniper, observer
Emergency care SGT/driver
Vehicle Cdr/gunner
Vehicle Cdr
TC/gunner
Fire Support Officer/NCO

5/4
4/NA
3/2
3/NA
2/NA
2/NA
4/3
4/3

number 23
number 16 & number 26
number 28
number 16 & number 27
number 16 & number 27
number 16 & number 27
number 22
number 25
RSTA Squadron (Stryker)
M1127 RV squad
M1129 MC squad
M1135 NBCRV

M1133 MEV crew

M1130 CV crew
M1131 FSV crew

Squad leader
Squad leader, gunner
Vehicle Cdr, driver, two Surveyors
Emergency care SGT/driver
Vehicle Cdr/gunner
Fire Support Officer/NCO

5/4
4/NA
4/3

3/NA

2/NA
4/3

number 23
number 16 & number 26
number 39, number 40, & number 41
number 16 & number 27

number 16 & number 27
number 25
SBCT (other)
M1134 ATGMV crew
M1133 MEV squad
M1132 ESV crew
AN/TP Q 36
AN/ TPQ 37

SEC/SQD leader/gunner
Squad leader
Vehicle Cdr
Section Chief
Section Chief

3/NA
8/6
2/NA
6/NA
12/NA

number 16 & number 30
number 24
number 16 & number 31
number 16 & number 31
number 16 & number 31
Battalion CP CO
XO
Staff Section / OICs
Staff Section NCOICs
Full: 100 percent
Minimally: 85 percent of Soldiers and 95 percent of key leaders
number 33
Brigade CP CO
DCO (If authorized)
XO (If authorized)
Staff Section / OICs
Staff Section / NCOICs
Full: 100 percent
Minimally: 85 percent of Soldiers and 95 percent of key leaders
number 34
Division CP CG
ADCs
CoS
Cell and Element OICs
Cell and Element NCOICs
Full: 100 percent
Minimally: 90 percent of Soldiers and 90 percent of key leaders
number 35
Corps CP CG
DCG
CoS
Cell and Element OICs
Cell and Element NCOICs
Full: 100 percent
Minimally: 90 percent of Soldiers and 90 percent of key leaders
Number 36
Battalion CPN SR XMSN Sys Opr-Mnt
XMSN Sys Opr-Mnt
SR CPN Opr-Mnt
CPN Opr-Mnt
Fully: 8
Minimally: 8
number 37
Brigade JNTC-S SR Nodal Net Sys Opr-Mnt
Nodal Net Sys Opr-Mnt
TACSAT TM Chief
TACSAT Sys Opr-Mnt
SR XMSN Sys Opr-Mnt
XMSN Sys Opr-Mnt
Team Chief
Radio Retrans Opr
Range Ext Opr
Fully: 25
Minimally: 25
number 38
MH 60, MH-47D, MH47E, MH47G See note 43 See note 43 Number 43

Notes:
1. M1/M2/M3 crew. M1 crews meet qualification standards in
FM 3-20 .21. M2/M3 crews meet qualification standards in FM 3-22 .1 Bradley Gunnery.
2. Infantry/recon/scout squad/team. Must have a qualified squad leader (commander's judgment based on Soldier's ability to perform the leader/individual tasks that support the unit's METL). Must have Soldiers (see full/minimum requirements in table 8-2 for number of Soldiers required) who meet the standards for "individual" weapon qualification in accordance with DA PamM 350-38. Must be able to man an assigned crew-served weapon (that is, Javelin, M60/M2/240 machine gun, and MK-19 grenade machine gun) with qualified gunners in accordance with DA Pam 350-38.
3. TOW crew. Crew meets qualification standards in accordance with DA Pam 350-38.
4. Combat Engineer squad/team. Must have qualified squad leader (commander's judgment based on Soldier's ability to perform the leader/individual tasks that support the unit's METL). Must have Soldiers (see Fully Manned and Combat Capable levels in table 8-5 for number of Soldiers required) who meet the standard for "individual" weapon qualification in accordance with DA Pam 350-38. Must be able to man assigned crew served weapons (M60, M2, M240B, MK-19) with qualified gunners in accordance with DA Pam 350-38. M2A2 ODS-E equipped units must be qualified on Bradley table VIII within the past 6 months. The TC/BC must meet crew qualification in accordance with chapter 16 of FM 3-22.1 and DA Pam 350-38.
5. MLRS section. Section chief and gunner must satisfactorily complete the launcher section evaluation including tasks found in Artillery table 2 (Crew Certification), 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 of its METL-related fire mission tasks to standard twice annually for Active Component units and once annually for RC units. EUSA exception applies.
6. Howitzer section. Section chief, gunner, and crew must meet qualification/proficiency standards established by FM 6-50 and DA Pam 350-38. Training requirements include satisfactorily completing the cannon section evaluation and achieving at least 700 out of 1000 points in accordance with appendix G , FM 6-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's qualification 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 past year 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 standard, annually. For M109A6, incorporate the four Paladin skills required in appendix B, FM 6-50, pages four and 29-32. Upon approval of the cannon section evaluation in FM 3-90 .70, utilize those new tasks for determining qualification. Note: Commander, EUSA, by exception may determine FA qualification status for USR reporting due to range availability constraints and the impact of short tour personnel turnover.
7. 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 in each event and section leaders and FDC personnel must pass each event on the FDC exam within the past 6 months. Crew must meet the qualification standards in accordance with DA Pam 350-38
8. Stinger and Stinger/Avenger teams. Teams must meet the qualification standards in accordance with DA Pam 350-38. Stinger and Stinger/Avenger teams will be reported separately.
9. Bradley Stinger Fighting Vehicle (BSFV). Vehicle commander and gunner are qualified on a Bradley table VIII within the past 6 months. Stinger team chief and gunner meet qualification standards in accordance with DA Pam 350-38.
10. Not used.
11. Criteria for Patriot. To be determined.
12. AH-64/AH-1/OH-58D crew. Assigned aviators must be Readiness Level (RL) One, per the appropriate Aircrew Training Manual (ATM). Crews must meet the gunnery qualification standards in accordance with DA Pam 350-38 and the FM 3-04 .140. There is no requirement for aviation crewmen to qualify together as a crew.
13. CH-47/UH-60/UH-1H/OH-58A/OH-58C crew. Assigned aviators must be crew qualified within the past 12 months. Crew meets the qualification standards in accordance with DA Pam 350-38. MEDEVAC crews must have aviators, crew chief, and flight medic to be a qualified crew.
14. Special Forces Operational Detachment Alpha/Special Operations Team. Alpha/Civil Affairs Team A/Civil Affairs Team B/Civil Affairs Team C/PSYOP Development Detachment/Tactical PSYOP Detachment/Tactical PSYOP Team. Meets individual and team training certifications established by USASOC.
15. BIDS Team. All crewmembers must have ASI L4. In addition, complete the following tasks as a crew: tasks 03-3-0031; 03-3-0022; 03-3-0032; 03-3-0038.
16. NA. "NA" indicates that minimum manning standards and criteria are not applicable to the squads/crews/teams/systems listed.
17. MTOEs authorize a maximum of eight M109A6 crewmembers. Modular units will report using standards of 8 Fully Manned/7 Minimum Manned.
18. M93/M93A1 FOX Crew. Key individuals familiarize themselves with M240/M240E1 and perform to standard Crew Drills 1,2, and 3 within the past 6 months.
19. M93A1 Fox NBCES crewmembers. All M93A1 crewmembers must possess ASI L5.
20. M93 crewmembers. Three of four M93 crewmembers must possess ASI L5.
21. Qualified squad leader. Must have Soldiers who meet the standards for individual weapon qualification in accordance with DA Pam 350-38. Must be able to man crew-served weapons with qualified gunners in accordance with DA Pam 350-38. Has qualified Squad Designated Marksman. Has one Soldier qualified on the Javelin (Javelin ASI not required).
22. TC and gunner meet crew qualification standards. TC and gunner meet crew qualification standards in accordance with DA Pam 350-38. In lieu of vehicle is the ATGMV and MGS crews must meet the ATGMV training requirements until the MGS is fielded. Must have Soldiers who meet the standards for individual weapon qualification in accordance with DA Pam 350-38.
23. Qualified squad leader. Must have Soldiers who meet the standards for individual weapon qualification in accordance with DA Pam 350-38. Must be able to man crew-served weapons with qualified gunners in accordance with DA Pam 350-38.
24. Combat engineer squad is qualified in accordance with DA Pam 350-38. Must have Soldiers who meet the standards for individual weapons qualifications in accordance with DA Pam 350-38.
25. Crew must meet qualification/proficiency standards established by FM 6-50 and DA Pam 350-38. Must have Soldiers who meet the standards for individual weapon qualification in accordance with DA Pam 350-38.
26. Squad leader and gunner must pass the mortar gunner's exam with the minimum score of 70 percent in each event. Crew must meet the qualification standards in accordance with DA Pam 350-38. Must have Soldiers who meet the standards for individual weapons qualifications in accordance with DA Pam 350-38.
27. Vehicle Commander and driver meet crew qualification standards in accordance with DA Pam 350-38. Must have Soldiers who meet the standards for individual weapons qualifications in accordance with DA PamM 350-38.
28. Must be graduates of an approved sniper-producing course of instruction. Must have Soldiers who meet the standards for individual weapons qualifications in accordance with DA Pam 350-38.
29. In lieu of system is the M93A1 Fox NBCRS. M1135 Stryker NBCRV crews must meet the M93A1 Fox training requirements until the NBCRV is fielded. Must have Soldiers who meet the standards for individual weapons qualifications in accordance with DA Pam 350-38.
30. ATGMV crew. ATGMV crew meets qualification standards in accordance with DA Pam 350-38.
31. AN/ TPQ 36 and AN/ TPQ 37 crews. AN/ TPQ 36 and AN/ TPQ 37 crews must be MOS qualified.
32. TUAV. TUAV in developmental process.
33. Each BN must report its organic battalion level command post(s) (CP). In order to be rated as a qualified CP, the battalion CP must have conducted a CPX in coordination with the command and control combined arms training strategy (C2 CATS)* within the last 4 months; for a rating of combat capable the CP must have conducted a command post exercise (CPX) in coordination with C2 CATS* within the last 6 months. In order for a CP staff to be assessed as a qualified staff, each of the CP's battle command/mission common, organic or assigned systems must have at least two operators who have completed the MOS or common functional training within the last 18 months. Two operators per system is the minimum manning requirement for continuous (24/7) operations.
34. Each BDE must report its organic BDE level CP(s)'s battle staff and its organic subordinate BN level CPs' battle staff. In order to be rated as a qualified CP battle staff, each CP battle staff must have conducted a CPX in coordination with unit CATS* within the last 4 months; for a rating of combat capable the CP must have conducted a CPX in coordination with unit CATS* within the last 6 months. In order for a CP staff to be assessed as a qualified staff, each of the CP's battle command/mission common, organic, or assigned systems must have at least two operators who have completed the MOS or common functional training within the last 18 months. Two operators per system is the minimum manning requirement for continuous (24/ 7) operations.
35. Each division headquarters must report its organic division level CPs' battle staff. In order to be rated as a qualified CP battle staff, each division CP battle staff must have conducted a CPX ICW the C2 CATS* within the last 7 months; for a rating of combat capable the CP battle staff must have conducted a CPX in coordination with C2 CATS* within the last 13 months. In order for a CP staff to be assessed as a qualified staff, each of the CP's Battle Command/Mission common, organic or assigned systems must have at least two operators who have completed the MOS or common functional training within the last 18 months. Two operators per system is the minimum manning requirement for continuous (24/7) operations.
36. Each corps headquarters must report its organic corps level CPs' battle staff. In order to be rated as a qualified CP battle staff, each corps CP battle staff must have conducted a CPX in coordination with the C2 CATS* within the last 7 months; for a rating of combat capable the CP battle staff must have conducted a CPX in coordination with C2 CATS* within the last 13 months. . In order for a CP staff to be assessed as a qualified staff, each of the CP's Battle Command/Mission common, organic or assigned systems must have at least two operators who have completed the MOS or common functional training within the last eighteen months. Two operators per system is the minimum manning requirement for continuous (24/ 7) operations.
37. Each BN must report its organic BN level command post node (CPN) battle staff. In order to be rated as a qualified CPN battle staff, the battalion CPN must have conducted an field training exercise (FTX) in accordance with the Command and Control Combined Arms Training Strategy (Unit CATS) within the last 3 months; for a rating of combat capable the CPN battle staff must have conducted an FTX in accordance with Unit CATS within the last 6 months. In order for a CP staff to be assessed as a qualified staff, each of the CP's battle command/mission common, organic or assigned systems must have at least two operators who have completed the MOS or common functional training within the last eighteen months. Two operators per system is the minimum manning requirement for continuous (24/7) operations.
38. Each Brigade must report its organic brigade level Joint Network Transport Capability-Spiral (JNTC-S) battle staff. In order to be rated as a qualified JNTC-S, the brigade JNTC-S battle staff must have conducted an FTX in accordance with the C2 CATS within the last 3 months; for a rating of combat capable the JNTC-S battle staff must have conducted an FTX in accordance with C2 CATS within the last 6 months.
39. Driver, VC, and gunner meet crew qualification standards. VC and gunner meet crew qualification standards in accordance with DA Pam 350-38. Must have Soldiers who meet the standards for individual weapon qualification in accordance with DA Pam 350-38.
40. M1135 Stryker NBCRV crewmembers. Three of four NBCRV crewmembers must possess ASI L6. If manned at minimum level, all three crewmembers must possess ASI L6.
41. Vehicle Commander and both Surveyors must meet crew qualification standards in accordance with DA Pam 350-38. Must have Soldiers who meet the standards for individual weapons qualifications in accordance with DA Pam 350-38.
42. Unmanned Aircraft Operator (AO), External Operator (EO), Mission Payload Operator (PO), Mission Commander (MC) must possess MOS 15W. AO & PO must pass a yearly Class III Flight Duty Medical Examination. Must maintain currency and refresher training in accordance with AR 95-23 .
43. Army Staff units report in accordance with manning and qualification standards established by USASOC.

h. Reporting examples. The following figures provide reporting examples using a notional infantry squad. Figure 8-2 reflects the various possibilities for reporting a fully manned squad (9 squad members assigned); figure 8-3 reflects the various possibilities for reporting a minimally manned squad (7 or 8 squad members assigned); and figure 8-4 illustrates the possibilities for reporting a partially manned squad (1-6 squad members assigned) and an unmanned squad (no squad members assigned). Soldiers assigned to the notional squad that are not qualified for their positions are shaded. A combat capable squad requires that seven (7) or eight (8) of the assigned squad members are qualified for their positions. While multiple possibilities are illustrated in these figures, they do not reflect all possibilities.



Figure 8-2. Manning and qualification example (fully manned squad with unqualified Soldiers shaded)





Figure 8-3. Manning and Qualification Example (Minimally Manned Squad with Unqualified Soldiers shaded)





Figure 8-4. Manning and Qualification Example (Partially Manned and Unmanned Squads)


i. Report consolidation. All major units and major headquarters are required to consolidate and report in their full reports the squad/crew/team/system manning and qualification data reported by the subordinate units/elements for which they currently have command and control (for example, organic, assigned, attached, and OPCON units/elements).

j. Additional reported data. The Army tasking authority, and/or a major headquarters (brigade level or above) with ADCON authority may direct its subordinate units to determine and report manning and qualification data for additional squads/crews/teams/systems, command posts and staffs in the CUSR. The manning and training qualification status data for designated squads/crews/teams/systems, command posts and staffs are reported in the CUSR as Army unique data points for use at HQDA and by commands at all levels. While assessing unit proficiency in the METL tasks and estimating training days, the commander of a reporting unit should carefully consider the manning and training qualification status of those designated entities applicable to his unit.

8-6. Determining and reporting training resource constraints

a. All units report the degree to which resource constraints prevent them from achieving and maintaining the highest training status level (T-1 level). For each of the resource related data points listed in paragraphs b through I, enter one of the four codes below (for APS reporting, always enter "A"):

(1) "A" if the resource field has an insignificant impact on training.

(2) "B" if the resource field has a minor impact.

(3) "C" if the resource field has a major impact.

(4) "D" if the resource field prohibits training necessary to achieve or maintain T-1 level.

b. Assigned strength shortfall. Assess the impact of personnel shortages. When an overall assigned strength shortfall, lack of key MOS qualified personnel, and lack of full-time manning support (RC only) hinders training, commanders will comment in training remarks.

c. Special duty requirements. Assess the impact of diverting unit personnel to meet special duty requirements (includes BMM and TD).

d. Availability of funds. Assess the impact of funding availability. Commanders will comment when assistance is needed from higher-level headquarters.

e. Availability of equipment or materiel. Assess the impact of equipment or materiel shortages. This data point includes CBRN equipment and is not limited to equipment authorized on a unit's MTOE or TDA.

f. Availability of qualified leaders. Assess the impact of leader qualification. Emphasize those leaders key to METL performance (for example, platoon leaders, platoon sergeants, and squad leaders).

g. 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 TC1-210-1, chapter 7. The availability of non-aviator leaders in these 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. Consider the unit's aviator T-level when determining the T-Days.

h. Availability of training areas/facilities/training aids, devices, simulations and simulators. Assess the impact of availability training areas and facilities. Consider quality, size, and accessibility of training areas available to the unit and local/national restrictions on those training areas. Also consider availability of training aids, devices, simulators and simulations.

i. Availability of aviation fuel. Assess the impact of available aviation fuel. Consider the requirements for both field and garrison training.

j. Availability of ammunition (does not include wartime basic load). Assess the impact of available training ammunition. Consider both training standard and training unique ammunition, including sub-caliber rounds for training devices.

k. Availability of time/flying hours. Assess the impact of competing activities that detract from training time to the extent that they reduce training readiness (such as, school support activities and umpire details for other units). Also consider the impact of available flying hours on training.

l. Narrative remarks on resource constraints. In those cases where the above data points do not contain the letter "A" ("1" for aviation units in the "aviator training"), the impact of the resource constraints will be addressed in the remarks section of the CUSR that coincides with the data point that indicates the resource constraint. For example, a minor impact in funding would call for a "B" for the "availability of funds" data point The corresponding comment will be recorded in the remarks associated with the "availability of funds."

8-7. Reporting other training data

a. Training days. The T-days data point reflects the number of training days that the commander estimates is required for the unit to become fully trained on its METL, that is, for all METL tasks to be assessed as "T" when performed under the conditions established for training or performance. To estimate the number of training days needed to become fully trained on the unit's FSO METL, the commander estimates the minimum amount of training events/activities required to raise the unit's assessed proficiency in each FSO METL mission essential task (MET) to a "trained" (T) status. This estimate includes the time required to achieve and sustain proficiency on the critical individual, leader, and collective tasks required to successfully accomplish each FSO METL task. For RC units, the number of days required by the unit to train to achieve full proficiency on any specified pre-mobilization training tasks is included in this estimate if applicable. This estimate does not include the number of days required by the unit to train exclusively for CBRN requirements associated with an assigned mission tasked separately for planning/preparation or execution. This estimate also does not include time needed to conduct field training exercises or CPX at levels of command higher than that of the reporting unit. For example, a battalion commander should consider in his estimate the training time needed to conduct a BN FTX or CPX but he should not consider the training time needed for a brigade level FTX or CPX.

b. Training days attributable to chemical, biological, radiological and nuclear training requirements.

(1) The GSORTS CJCSI and CJCSM require measured units to determine and report an overall CBRN-Level, a CBRN S-Level) and a CBRN T-Level. The data required to establish each of these CBRN levels is determined from the corresponding CBRN status data reported by Army units in the CUSR in accordance with the provisions of this paragraph (the CBRN T-Level), chapter 6 (the CBRN S-Level) and chapter 9 (the overall CBRN-Level).

(2) Although CBRN preparedness is a fundamental part of core task proficiency, the CBRN related standard FSO METL tasks and/or the CBRN conditions for standard FSO METL training can vary significantly among units. The ASCC and the unit's chain of command may provide additional guidance regarding conditions for training on the FSO METL. The T-METL calculations and T-Days estimates reported in the CUSR will include consideration of the CBRN conditions established for FSO METL training.

(3) As required by CJCSM 3150.02B, all measured Army units will report (as CBRN T-days) the number of required training days estimated in accordance with the provisions of paragraph a , above that are attributable to FSO METL performance under CBRN conditions. When estimating required CBRN T-days, commanders will consider the unit's training proficiency (T/P/U) in those standard FSO METL tasks with CBRN conditions (also known as "CBRN tasks") and the expertise and qualifications of chemical personnel ( MOS 74D/74A). The NetUSR software application will enable the unit to identify its "CBRN" tasks" on the FSO METL and to review the current T/P/U training status assessment for each of these CBRN tasks pursuant to determining and reporting the CBRN T-Days estimate.

(4) If the commander cannot identify any CBRN tasks on the FSO METL or cannot distinguish the training time required to achieve proficiency on the CBRN tasks from the training times required to achieve proficiency in FSO METL under all conditions, then he will report CBRN T-days as equal to the T-days determined in paragraph a , above.

(5) When the commander can identify specific CBRN tasks on the FSO METL or can distinguish the training time required to achieve proficiency on the CBRN tasks from the training times required to achieve proficiency in standard FSO METL under all conditions, then he will report CBRN T-Days as a subset of the T-Days determined in paragraph a , above (that is, CBRN T-days + all other T-days = T-days determined in para a , above).

(6) To report CBRN training data, use the CBRN tab of the NetUSR application (RECAP section). NetUSR uses table 8-5 to auto-calculate the CBRN T-level based on the CBRN T-Days estimate determined and reported by the unit. Remarks are mandatory if the CBRN T-level is not level 1. For example, "Unit requires 15 training days to conduct decontamination training" or "Unit must train all tasks under CBRN conditions to become fully trained on the FSO METL." If the CBRN T-level is not level 1, then the unit also must enter an appropriate reason code from the reason code table (see appendix I ) provided at the CBRN tab to explain the training deficiencies.

Table 8-4. Estimating training days
T-CBRN/T-PRE MOB Levels 1 2 3 4
Estimated training days 0-14 15-28 29-42 43 or more

c. Unit and staff proficiency level.

(1) These mandatory assessments enable commanders to indicate their unit's general progress in building proficiency and meeting ARFORGEN training goals. The unit proficiency level is intended to reflect the level of the organization that is fully trained (shoot, move, communicate, and sustain) for Full Spectrum Operations. For example, after reporting its overall T-Level (see para 8-4 ), a brigade could submit UPL assessments indicating that its squads and platoons are generally fully trained (T), that its companies and battalions need more practice (P), and that the brigade staff is untrained (U).

(2) For UPL assessments, the commander of the reporting unit provides a general T/P/U evaluation for each of the staffs and subordinate elements in his organization. See figure 8-7 . NetUSR user help-screens explain the specific data entry procedures.

(3) Subsequently, NetUSR will require commanders of the reporting units to provide remarks when a reported UPL does not match the expected UPL associated with the unit' s T-Level determination. See table 8-5 .

(4) Figure 8-6 provides a UPL reporting example for a notional brigade with staffs and subordinate elements that do not meet the expected UPL status associated with the reported T-Level as explained in table 8-5.

Table 8-5. Unit proficiency level expected for reported T-Level
Reported
T-Level (Para 8-4)
Brigade Reporting
Minimum Expected UPL
Battalion Reporting
Minimum Expected UPL
Company Reporting
Minimum Expected UPL
T-1 Brigade staff UPL = T;
Battalions and lower units in brigade UPL = T (for maneuver / functional and live fire)
Battalion staff UPL = T;
Companies and lower units in battalion UPL = T (for maneuver / functional and live fire)
Company and lower units UPL = T (for maneuver / functional and live fire)
T-2 Brigade staff UPL = T;
70 percent or more of all companies and lower units in brigade UPL= T (for maneuver / functional and live fire)
Battalion staff UPL = T;
70 percent or more of all platoons and lower units in battalion UPL = T (for maneuver / functional and live fire)
70 percent or more of all platoons and lower units in company UPL = T (for maneuver / functional and live fire)
T-3 Brigade staff UPL = P;
70 percent or more of all platoons and lower units in brigade UPL = T (for maneuver / functional and live fire)
Battalion staff UPL = P;
70 percent or more of all squads in battalion UPL = T (for maneuver / functional and live fire)
70 percent or more of all squads in company UPL - T (for maneuver / functional and live fire)
T-4/T-5 Brigade staff UPL = U;
70 percent or more of all squads in brigade UPL = T (for maneuver / functional and live fire)
Battalion staff UPL = U;
70 percent or more of all teams/crews in battalion UPL = T (for maneuver / functional and live fire)
70 percent or more of all teams/crews in company UPL= T (for maneuver / functional and live fire)
Note: (for maneuver / functional and live fire) "maneuver and live fire" pertains to BCTs, "functional and live fire" pertains to functional and multifunctional units.



Figure 8-5. Notional Brigade reporting UPL that does not meet expected T-Level from table 8-5





Figure 8-6. UPL selections as viewed by user


d. Pre-mobilization training days. All measured Reserve Component units (ARNG/ARNGUS and USAR) that have insufficient training time to build and sustain full METL proficiency before mobilization are provided training guidance by the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, that specifies the level of proficiency that each unit is expected to achieve before mobilization. Each of these units is required to report "PRE MOB T-days" in the CUSR to indicate their success in achieving the pre-mobilization training level specified by the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable. After notifying HQDA, the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, may specify in their directives those subordinate RC units that are exempted from this reporting requirement because pre-mobilization training goals are either not applicable or inappropriate. For example, USARC can request exemption of separate companies in the USAR that, in accordance with FORSCOM training policy, are required to conduct premobilizing training at the level organized (that is, the company level).

(1) When specifying pre-mobilization training levels, the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, will consider capabilities required of the unit by operational planning, time available to the unit before mobilization, and time that should be available to the unit after mobilization for additional "post mobilization training." Additionally, the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, will consider training resources available to the unit as reflected in the unit's Combined Arms Training Strategy.

(2) The PRE MOB T-Days is calculated using the same procedures discussed in para 8-3 , that is, by estimating the number of training days required by the RC unit to reach the pre-mobilization proficiency level specified for the unit in the training guidance provided by the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable. This estimate is based on the commander's assessment of training proficiency in the tasks required for the level of pre-mobilization training. Report the number of PRE MOB T-Days on the training status tab in the training section of the NetUSR application.

(3) The NetUSR uses table 8-5 to auto-calculate the PRE MOB T-Level using based on the PRE MOB T-days determined and reported by the unit For example, if command training guidance requires the unit to achieve and sustain proficiency at the platoon level in FSO METL tasks and the unit has just completed annual training, where the focus for maneuver units was platoon level tasks, then for the next readiness report, leaders should update their assessment of unit proficiency in the FSO METL tasks at the platoon level. If, based primarily on the unit's performance during annual training, the commander concludes that his platoons need 7 additional days of training (PRE MOB T-days) to be fully proficient in platoon level, then the unit would report PRE MOB T-days as 7. Subsequently, the NetUSR software application will use table 8-5 to auto-calculate that the PRE MOB T-days reported by the unit translates to a PRE MOB T-Level of "1". As previously explained, the commander uses his assessments of the unit's training proficiency in FSO METL tasks to determine and report the battalion's overall T-Level. Note that the estimate of PRE MOB T-Days (in this example-7 days) is part of the number of overall days required for the unit to become fully trained in its METL tasks (that is, PRE MOB T-Days + training days required after mobilization to become fully trained in METL tasks = T-Days for RC units). Provide other pertinent comments on training status as appropriate using the REMARKS feature provided in the NetUSR software application.

e. Assigned mission/training requirements. On occasion external authorities (that is, Congress, OSD, Joint Staff, combatant commanders, and so forth) and/or Army commands at higher levels may, in conjunction with the assignment of operational requirements, prescribe specific training requirements for deploying Army units and also mandate that unit commanders report the status of training on these requirements in the USR. When these training requirements have been formally established for status reporting via the USR, the NetUSR application will provide the required data sets and pre-populate the applicable data fields on the "ASSESS METs" page to enable reporting units to provide both T/P/U training proficiency assessments and Y/Q/N capability assessments for each training requirement. For example, for Operation Enduring Freedom the CENTCOM commander has prescribed specific theater-unique training/education requirements on counter insurgency (COIN) operations that each deploying Soldier and unit must accomplish/complete before entering the Afghanistan-Pakistan JOA. Hence, Army units designated for deployment into this JOA (that is, DEFs deploying to the Afghanistan-Pakistan JOA) must report on the training accomplished to meet this CENTCOM requirement. Assigned mission training requirements are not FSO METL tasks; therefore, they will be listed by the NetUSR software application on the ASSESS METs page separately from the unit's FSO METL tasks and annotated to distinguish them from the unit's FSO METL tasks. The DRRS-Army portal and/or the NetUSR software application also will identify any specified instructions for determining the T/P/U and Y/Q/N assessments for each training requirement that is consistent with the guidance, standards and/or criteria prescribed by the originator of the training requirement. Also see figure B-1 and appendix C .

8-8. Providing remarks

Precise and concise remarks from the unit commander are required (mandatory) to explain the factors that are preventing the unit from achieving T-1 level status. Because the training status in a unit normally is directly linked to its manning status, training remarks also are mandatory if significant inconsistencies exist between the T-Levels and the P-Levels reported by unit (that is, 3 level differences), except for units in the RESET force pool reporting C5/T5. Accordingly, commanders of units reporting T1/P4 will fully explain the unit's training proficiency status in their training remarks.

Chapter 9

Preparing and Submitting Regular Reports

9-1. General

a. Background. Regular reports are routinely submitted by non-deployed units into the DRRS-Army database via NetUSR pursuant to the Army's normal mid-month readiness reporting cycle. Regular reports can use either the full or abbreviated format and include the reports routinely prepared and submitted by non-deployed Operating Force (MTOE) units with AA-Level UICs (separate companies and battalions) and also the composite reports routinely submitted by non-deployed major units and major headquarters (brigades and above). Paragraph 3-2 and table 3-1 in this publication explains the various report formats, categories, aggregation/assessment methodologies and submission timelines. Regular reports comprise the overwhelming preponderance of the CUSRs that are prepared by units and submitted into the DRRS-Army database. Accordingly, the procedures for preparing and submitting regular reports generally serve as the baseline or default for preparing and submitting other reports. This chapter explains how regular reports are prepared and submitted while chapters 10 , 11 , , and 12 explain the additional, different or special procedures that are applicable to composite reports, deployed reports, and other reports, respectively.

b. Recent and new reporting requirements.

(1) Reporting mission names, descriptions, and plan numbers. The commander will select the applicable mission names or descriptions and plan numbers supported by his unit's FSO METL tasks from the approved list found at the DRRS-Army SIPRNet Web site or provided to him via ADCON channels. AR 220-1 , chapter 11 and chapter 13 of this publication explain the provisions for the security classification of these mission names or descriptions and plan numbers.

(2) Reporting three-tier capability assessments.

(a) The most significant aspect of the OSD's DRRS process is the additional requirement for commanders of all reporting units, including designated Army installations, to report their assessments of the capabilities of their units, organizations or installations to accomplish individual mission essential tasks-"METs" using OSD's new "Yes," "Qualified Yes" and "No" (Y/Q/N) three-tier metrics in all readiness status reports, to include deployed reports. While the T/P/U assessments established in the Army Training Network measures the unit's training proficiency for its METL tasks, the Y/Q/N task capability assessments required by OSD DRRS are intended to reflect a unit's actual potential to perform the task. Because there are no algorithms or weighting factors assigned in the OSD DRRS MET assessment process, commanders must carefully analyze and consider resource status and recent performance and then apply operational judgments to determine valid Y/Q/N METL task assessments for these OSD DRRS reporting requirements. Regardless of the unit's demonstrated training proficiency accomplishments, the unit commander will report "No" for those METL tasks that his unit currently is unable to perform due to resource constraints or deficiencies that result in risks that have not been fully mitigated. It is entirely possible that a reporting unit could have the training proficiency and the required resources currently available to accomplish some METL tasks but not others.

(b) Commanders develop and assess their units' FSO METL training proficiency status in accordance with the Army's keystone training doctrine established in FM 7-0 and explained at the Army Training Network (ATN). Subsequently, commanders report their units' training proficiency status for each FSO METL tasks using the doctrinal metrics "Trained" (T), "Needs Practice" (P) and "Untrained" (U) - in accordance with the provisions of AR 220-1 using the procedures explained in this publication. In order to comply with the requirements of DRRS, commanders also must report on their units' capability to execute their FSO METL tasks. Since FSO METL tasks are derived from the unit's core capabilities, they are specifically applicable to the DRRS "core tasks" mission category, and all or some of the unit's FSO METL tasks also are applicable to its assigned missions, to include any "Named Operations" or "Major Plans" specified for preparation or execution by the unit. FSO METL task capability assessments will be accomplished using DRRS three-tier (Y/Q/N) scale as described in AR 220-1, paragraph 4-7 and in this chapter.

(c) An overview of CUSR metrics is provided at AR 220-1, paragraph 4-15 and paragraph 9-10 in this publication.

9-2. Determining and reporting three-tier assessments

a. General. The "three-tier" rating scale is used by all measured units to determine and report their METL task capability assessments as explained in this paragraph and in AR 220-1, paragraphs 4-2 and 4-7. Additionally, the "three-tier" rating scale is used by those units that, due to exceptional circumstances, are required to report overall readiness or capability status for assigned missions that are in addition to the primary assigned mission (see AR 220-1, para 4-4). The three-tier rating scale is used by combatant commanders and by OSD for operational and resourcing decisions and to brief Congress on Joint readiness matters.

b. Mission essential task list task capability assessments. The following are the "three-tier" metrics for the measurements and assessments applicable to the unit's METL tasks.

(1) "Yes" (Y) assessment:

(a) DOD definition. The organization can accomplish the task to standard under the specified conditions. A "Yes" assessment should reflect demonstrated performance in training or operations whenever possible.

(b) Army caveat: Army units reporting "Yes" for a METL task capability assessment must possess the necessary resources, or those resources must have been explicitly identified to the unit (and appropriately earmarked), to allow it to execute the METL task immediately if ordered (that is, "fight tonight," meaning within the next 72 hours).

(2) "Qualified Yes" (Q) assessment:

(a) DOD definition. The organization is expected to accomplish the task to standard, but this performance has not been observed or demonstrated in training or operations. Organizations assessing their task capability as a "Qualified Yes" may be employed for those tasks.

(b) Army caveat: Army units reporting "Qualified Yes" for a METL task must possess the necessary resources, or those resources have been explicitly identified to the unit (and appropriately earmarked), to allow it to execute the METL task immediately if ordered (that is, "fight tonight," meaning within the next 72 hours).

(3) "No" (N) assessment: The organization is unable to accomplish the task to standard at this time.

(4) Figure 9-1 outlines the Army methodology to accomplish METL task assessments.



Figure 9-1. METL Task Assessment Methodology


c. Y/Q/N overall mission assessments. The OSD requires that reporting units use its three-tier Y/Q/N metrics to assess and report on their units' capabilities to perform "core tasks" and to execute any "named operation" or "major plan" assigned to them. To meet these OSD requirements, Army reporting units assess their ability to accomplish/provide their core functions or designed capabilities and any assigned missions. In the Army's reporting process, assigned missions are further categorized as either "current operations" or "contingency operations" to distinguish those formally ordered for execution (current operations) from those assigned to units only for planning (contingency operations). The Y/Q/N overall mission assessment is based upon the Y/Q/N assessments of the METL tasks associated with that assigned mission. These Y/Q/N METL task assessments consider the T/P/U training proficiency assessments accomplished in accordance with Army training doctrine and the availability of the specific resources required for the assigned mission.

(1) Overall Y/Q/N assessment for the unit's core functions or designed capabilities (also known as "core tasks" by OSD). This overall Y/Q/N assessment indicates the reporting unit's ability to accomplish/provide its core functions and provide designed capabilities. It is based solely on the Y/Q/N METL assessments of the associated supporting METL tasks. Because this overall mission assessment is defined similarly to the C-level, these assessments should be consistent. Hence, commander's who report C4 and "Yes" or C1 and "No" for these assessments are required to specifically explain the reasons for these significant differences.

(2) Overall Y/Q/N assessment for the primary assigned mission. The primary assigned mission overall Y/Q/N assessment indicates the unit's ability to execute the primary mission assigned the current operation or the designated contingency operation. The primary assigned mission overall Y/Q/N assessment is based on the Y/Q/N METL assessments that are associated with the primary assigned mission. Because this overall mission assessment is defined similarly to the A-level, these assessments should be consistent. Hence, commander's who report A4 and "Yes" or A1 and "No" for these assessments are required to specifically explain the reasons for these significant differences. Note that An A-Level is determined and reported only for the primary assigned mission.

(3) Overall Y/Q/N assessments for any secondary and additional missions. When exceptional circumstances require that units determine and report overall capability status for more than the primary assigned mission, the units will determine and report an overall Y/Q/N assessment based on the Y/Q/N METL assessments that are associated with the secondary or additional mission(s). Only overall Y/Q/N assessments are available for use to assess secondary and additional assigned missions.

(4) The following are the "three-tier" metrics for the measurements and assessments applicable to the assessments of the unit's core functions or designed capabilities and assigned missions, to include any secondary and additional assigned missions, that are required for status reporting.

(a) Report "Yes" if the majority of supporting METL tasks for the mission are currently assessed as "Yes" and no supporting METL task for the mission is currently assessed as "No."

(b) Report "Qualified Yes" if the majority of supporting METL tasks for the mission are currently assessed as "Qualified Yes" and no supporting METL task for the mission is currently assessed as "No."

(c) Report either "Yes" or "Qualified Yes" (commander's ,option) if the supporting METL task assessments are evenly split between "Yes" and "Qualified Yes."

(d) Report `"No" if any of the supporting METL tasks for the mission are currently assessed as "No."

(e) Figure 9-2 outlines the methodology for the overall mission capability assessments.



Figure 9-2. Methodology for overall Y/Q/N mission assessments


9-3. Determining and reporting four-tier measurements and assessments

a. General. The status levels of measured areas and overall assessments also are determined and reported using the longstanding four-tier metrics established by the Joint Staff. The status levels of four measured areas support the overall C-Level assessment; the status levels of two measured areas support the overall assigned mission (A-Level) assessment; and the status levels of two measured areas support the overall Chemical Biological Defense Resources and Training (CBRN) level assessment. This paragraph and AR 220-1 , paragraph 4-4 explains the overall readiness assessments. This paragraph and AR 220-1, paragraph 4-6 explain the various measured areas whose status is reported via four-tier metrics. NetUSR user help screens explain in detail the procedures to determine and report the various measured area levels. Modification of the computed status of each individually measured area is not permitted. An overview of CUSR metrics is provided at in paragraph 9-8 of this publication and in AR 220-1, paragraph 4-15.

b. Measured areas supporting the overall C-Level assessment. Commanders determine and report four measured area levels indicating the current status of resources and training in the unit to support their overall C-Level assessments: personnel (P), equipment and supplies (S) on-hand/available, equipment readiness/serviceability (R), and unit training proficiency (T). These measured areas are referred to as "PSRT" and are further explained as follows.

(1) Personnel (P-Level). Army measured units will measure personnel readiness using three metrics for personnel fill percentages that are based on the unit's documented strength requirements: total available personnel strength divided by the required strength, available MOSQ strength by duty position divided by the required strength, and the available senior grade composite level determined by comparing the available and required strength in each of five senior grade categories. The applicable MTOE or TDA that reflects the unit's core functions ordesigned capabilities is the authoritative source for the unit's required strength. While Army measured units also are required to determine and report additional personnel data (for example, the assigned strength percentage, turnover percentage, and so forth), the personnel level is determined solely based on the results of these three P-Level metrics. Also see AR 220-1 , paragraph 9-2.

(2) Equipment and supplies on-hand/available (S-Level). Army measured units determine and report an S-Level by determining by line item number (LIN) the on hand/availability status of designated critical equipment items (pacing items) and the on-hand/availability status of the other mission essential equipment items (ERC A) that are listed on the unit's MTOE or TDA. Substitute items prescribed by HQDA via Supply Bulletin (SB) 700-20 and ILO substitutions directed by HQDA or determined by the commander are applied in accordance with the provisions of AR 220-1, paragraph 9-3. Note that for this S-Level measurement, the on hand/availability status of equipment items is based solely on those equipment items currently in the unit's possession, under its control or, when applicable, available to it within 72 hours for mission execution. The S-Level measurement is not based solely on property accountability records, and it does not consider the operational readiness/serviceability of the equipment items. A discrete measurement is accomplished at the LIN level of detail by comparing the equipment items currently in the unit's possession, under its control or available to it within 72 hours, to the formally documented requirements, and an S-Level rating is determined for each measurement. The applicable MTOE or TDA that reflects the unit's core functions or designed capabilities is the authoritative source for the unit's equipment requirements. The unit' s S-Level rating is determined in accordance with a methodology that considers each of these by LIN S-Level measurements. Also see AR 220-1, paragraph 9-3.

(3) Equipment readiness/serviceability (R-Level). Army measured units will measure the operational readiness or serviceability of the critical equipment items that are in their possession and that are designated by HQDA via the MMDF as reportable for maintenance. Separate measurements will be accomplished for each maintenance reportable pacing item and for all maintenance reportable equipment currently in the unit's possession (aggregate). An R-Level rating is determined for each measurement, and, subsequently, the unit' s R-Level rating is determined in accordance with a methodology that considers each of these R-Level measurements. Procedures are further explained in the NetUSR user help screens. Also see AR 220-1 , paragraph 9-4.

(4) Unit training level proficiency (T-Level). Commanders of Army measured units will report the training status of their units based on the percentage of the unit's FSO METL tasks trained to standard. While Army measured units also are required to determine and report additional training data (for example, required training days, squad/crew/team manning and qualification status, and so forth) the training level is determined solely based on the assessments of the METL tasks associated with the unit's core functions or designed capabilities. Also see AR 220-1, paragraph 9-5.

c. Measured areas supporting the overall assigned mission level (A-Level) assessment. Two measured area levels support the overall A-Level assessment. Commanders will determine and report the assigned mission manning level (AMM-Level) and the assigned mission equipping level (AME-Level). Commander's comments will be used to address any equipment readiness/serviceability or training issues, and these issues should be considered by the commander while determining whether to upgrade or downgrade the A-Level. The Army tasking authority will establish the specific manning and equipping requirements and provide training and readiness reporting guidance for each mission assigned to the unit. The Army tasking authority will either specify that the unit's MTOE requirements are applicable for the assigned mission or establish or convey specific manning and equipping requirements for the assigned mission. The DCS, G-3/5/7 (DAMO-SS) must validate any requirements that may result in an operational needs statement or joint unit operations needs statement or any that exceed the unit's current MTOE requirements. The two measured areas that are applicable to assigned missions are defined below and further explained in the NetUSR user help screens.

(1) Assigned mission manning level (AMM-Level). An Army measured unit will determine and report the manning status for its primary assigned mission by comparing the manning requirements for the assigned mission that were established and conveyed by the appropriate Army tasking authority with the personnel currently available to the unit to accomplish the assigned mission. The Army tasking authority also will specify any criteria for determining Soldier deployability for the assigned mission that differs from that applicable to the assessment of the unit's core functions or designed capabilities, to include establishing or clarifying how Soldiers programmed to join the unit but not currently available to it (for example, in-theater augmentees) should be addressed in the commander's comments and manning status projections and how rear detachment personnel will be considered for status reporting purposes. See AR 220-1, paragraphs 9-2 and 9-6.

(2) Assigned mission equipping level (AME-Level). Army measured units determine and report the equipping status for their assigned missions by comparing the equipment requirements for the assigned mission that were established and conveyed by the appropriate Army tasking authority with the equipment items that currently are on-hand/available to and/or possessed/controlled by the unit to accomplish the assigned mission. The guidance and instructions provided by the Army tasking authority will establish or clarify how equipment items programmed for use by the unit to accomplish the assigned mission, but not currently in its possession (that is, theater provided equipment and APS) will be addressed in the commander's comments and equipment status projections and how any equipment currently assigned to the unit that will not be deployed with the unit (that is, left behind equipment) will be considered for status reporting purposes. See AR 220-1, paragraphs 9-3 and 9-6.

d. Measured areas supporting the overall CBRN assessment. Each Army measured unit will determine and report its overall readiness assessments for chemical and biological defense resources and training in accordance with the provisions of this paragraph, AR 220-1 , paragraph 4-4 and NetUSR user help screens. Two measured area levels support the determination of the overall CBRN level.

(1) Equipment and supplies ( CBRN S-Level). For the CBRN report, commanders will determine the of equipment on-hand/available to properly equip the unit for operation in a CB environment, using the rating schema outlined in AR 220-1, paragraph 9-7.

(2) Training ( CBRN T-level). For the CBRN report, commanders will subjectively assess the level of training in the unit for operations in a CBRN environment, using the rating schema outlined in paragraph 9-7.

e. The following metrics comprise the "four-tier" rating scale for unit readiness status measurements and assessments. Note that level 5 and level 6 are exceptional values reported in place of level 4 or only when special circumstances apply, respectively.

(1) "1." The unit possesses the required resources and is trained to undertake the mission. The status of resources and training in the unit does not limit flexibility in methods for mission accomplishment nor increase vulnerability of unit personnel and equipment. The unit does not require any compensation for deficiencies.

(2) "2." The unit possesses the required resources and is trained to undertake most of the mission. The status of resource and training in the unit may cause isolated decreases in the flexibility of choices for mission accomplishment. However, it will not increase the vulnerability of the unit under most envisioned operational scenarios. The unit will require little, if any, compensation for deficiencies.

(3) "3." The unit possesses the required resources and is trained to undertake many, but not all, portions of the mission. The status of resource and training in the unit will result in significant decreases in flexibility for mission accomplishment and will increase vulnerability of the unit under many, but not all, envisioned operational scenarios. The unit will require significant compensation for deficiencies.

(4) "4." The unit requires additional resources or training to undertake its mission, but it may be directed to undertake portions of the mission with resources on hand (available).

(5) "5." The unit is undergoing a HQDA-directed resource action and/or is part of a HQDA directed program and is not prepared to accomplish/provide its core functions or designed capabilities. Units report C-5 in accordance with the policy and procedures established in para 3-7 . Level 5 is not applicable to A-Level reporting.

(6) "6." Level 6 is applicable to the measured areas only (see para 3-8 ). It indicates that a measured area is not measurable, or by HQDA direction, is not measured.

(a) When a resource or training measurement is not applicable to a unit by type or design, NetUSR will auto-populate level 6. For example, P6 and T6 are auto-populated for APS units.

(b) When a resource or training requirement is not defined in the designed structure (MTOE or TDA) of a particular unit, the unit will report level 6 for that resource measurement. For example, an adjutant general unit with personnel but no equipment requirements on its MTOE will report S6.

(c) Similarly, when an accurate or training status measurement is impractical, units will report level 6 for that resource or training measurement. For example, a unit would report R-6 if the serviceability of the unit's maintenance reportable equipment could not be determined because the equipment is centrally stored, on board ship or because a civilian contractor performs maintenance for the unit.

(d) For Regular reports, measured area levels of 6 will be subjectively considered by the commander while determining the unit's overall level; however, level 6 cannot be used as the overall level (that is, there is no C-6 or A-6 level).

(e) When included in the composite report calculations of major units and major headquarters, the level 6 determinations of subordinate units will have a value of 4 in those calculations.

(f) Reporting level 6 does not relieve commanders of their responsibilities to account for and manage Army personnel and equipment under their ADCON authority. Detailed procedures regarding level 6 reporting are in the NetUSR user help screens.

f. Factors to consider when making an overall assessment. The lowest measured area (except "6"-which indicates an unmeasured area) should be considered the principal factor. At a minimum, review the manning, equipping and training factors listed in chapter 9 to determine if they are sufficient individually or in combination with other factors to warrant subjectively upgrading or downgrading the overall C-Level or A-Level in compliance with the provisions of AR 220-1 , paragraph 4-5.

9-4. Determining and reporting the assigned mission level

a. Background. The assigned mission level (A-Level) is the overall level reported in the CUSR by commanders of measured units to provide their assessments of their units' ability to execute assigned missions. Joint Staff policy requires military units to report via GSORTS for all operational environments to facilitate the operational planning that is necessary for adequate and feasible military responses to crises and time-sensitive situations. Accordingly, current Joint Staff policy requires commanders of measured units to determine and report on their units' ability to accomplish their core functions and provide designed capabilities using the C-Level and also to determine and report their units' ability to execute any currently assigned missions using the PCTEF level." (Note that Army units report A-Levels ILO PCTEF levels.) The current Joint Staff guidelines require that commanders report a "PCTEF level" upon receipt of an order to execute any of the following missions: homeland defense or homeland security, peacekeeping or peace enforcement operations, humanitarian assistance, consequence management, counter-drug operations, civil disturbance operations, natural disaster relief operations, (includes wild firefighting missions). Current OSD guidelines require units to report their capability to accomplish a wide range of current operations and contingency requirements. For Army units, the assigned mission level reporting requirements established in this AR 220-1 supplant these Joint Staff and OSD reporting requirements. An assigned mission level (A-level) for the unit's primary assigned mission will be reported by Army units using both the four-tier and three-tier rating scales established in AR 220-1 , paragraphs 4-6 and 4-7 and explained in this chapter.

b. Concept. The A-Level is an overall readiness assessment that reflects the unit's ability to accomplish the assigned mission and those tasks on its METL that are specifically associated with the assigned mission. The A-Level contains measured resource areas that indicate the availability status of resources (personnel and equipment) measured against the resource requirements for the assigned mission that have been established or conveyed by the Army tasking authority. If the unit is preparing for or executing an assigned mission encompassing all of its core functions and designed capabilities, then the A-Level and C-Level will coincide.

c. Basic business rules and procedures. See appendix C .

9-5. Determining and reporting mission accomplishment estimates

a. Background.

(1) The policy requirement for the commander of each measured unit to develop and report the MAE in the CUSR and to consider the MAE during C-Level upgrade/downgrade determinations has been eliminated. However, the MAE data field has been retained in NetUSR software for optional data entry to enable commanders to develop and report the MAE as directed by command guidance or as desired.

(2) The MAE previously represented the commander's subjective assessment of the unit's ability to execute that portion of the wartime or primary mission for which the unit is organized or designed and that it would be expected to perform if alerted/committed within 72 hours of the "as of" date of the report. Only units/elements currently under the OPCON authority of the commander were considered in his estimate, unless gains to or losses from his OPCON authority within the next 72 hours were formally programmed/ordered and confirmed. Subsequently, the MAE provided the basis for decisions by the unit commander to upgrade or downgrade the unit' s C-Level. For a measured unit reporting C-4 or C-5, it also provided a more precise indication of the unit's residual capabilities to commanders at higher levels. The commander expressed this estimate in terms of the percentage of the wartime or primary mission that the unit could accomplish ( within 72 hours) if it were alerted/committed. Commanders of deployed units also used the MAE to assess and to report the unit's effectiveness in executing the wartime/designed mission unless the unit has been assigned a derivative UIC for status reporting purposes. DUIC units did not report MAE and it was not applicable to APS units. This paragraph provides instructions for determining the MAE when/if it is directed for reporting by commanders at higher levels or if desired by the unit commander.

b. Basic instructions for determining the mission accomplishment estimate.

(1) Commanders will determine and report the MAE on the overall summary page. Commanders will use the same criteria for all types of units.

(2) When determining the MAE, the commander must consider the unit's training proficiency in core tasks and critical resources such as personnel, equipment, and repair parts availability. The commander should consider unit training proficiency and the status of critical resources in light of other important factors that impact the unit's ability to accomplish the wartime mission for which the unit is organized or designed. Those factors include but are not limited to readiness factors (such as mobility, operating tempo (OPTEMPO)), exercises, unit morale, and leadership, command, control, communications, computers and intelligence, and measured areas of equipment, personnel, and training). Sustainability of the unit (includes the availability of spares and repair parts, to include authorized stockage list, if applicable).

(3) Commanders at all levels are required to acquire, operate, and maintain systems for information assurance within their commands in accordance with the provisions of AR 25-2 . The DODD 8500.01E requires that information assurance shall be monitored reported and evaluated as a distinguishable element of mission readiness throughout DOD. Accordingly, commanders will consider information assurance readiness when determining the MAE percentage and will include appropriate comments regarding information assurance readiness in their MAE remarks when warranted.

(4) The CUSR does not provide (nor is it practical to specify) the quantitative and qualitative factors that may impact a unit's ability to accomplish the mission for which it is organized or designed; therefore, the commander must critically examine all appropriate unit readiness indicators and carefully consider significant factors when determining the unit's MAE. For example-A transportation company may have an overall level of C-4 due to EOH shortfalls, but the commander may decide (after considering the specific equipment shortages, the availability of repair parts, and workload factors) that the unit could ( within 72 hours) actually perform 75 percent of the wartime or primary mission for which the unit is organized or designed. A MTOE hospital at S-4 EOH might be able to actually deploy and operate ( within 72 hours) 70 percent of its hospital beds and 60 percent of its operating tables. If, in this example, the commander determines and reports an MAE of 60 percent, then commanders at higher levels would have important information regarding the unit's actual overall capability that otherwise might not be reflected clearly in the unit's report.

(5) Commanders will assume that resupply actions, consumption and attrition rates, and operations tempo will continue at planned or demonstrated rates, unless definite indications of change have been identified or established.

c. Determining the mission accomplishment estimate for hospital units To determine the MAE of hospitals

(1) Commanders will estimate the overall ability of a hospital unit based on the wartime or primary mission for which the hospital unit is organized or designed, as well as all factors considered in determining the unit' s C-Level, and other factors (qualitative and quantitative) not previously considered.

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

(3) Commanders will use the remarks section using the label "MAE." These remarks should refer to the MAE percentage and reflect required versus operational capability based on available personnel and equipment. Use the following format: Required versus operational intensive care/intermediate care/minimal care/beds/operating tables.

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

(5) Commanders will list the required and operational (required/operational) data that the MAE was based on, as follows: Hospital MAE is XXX (two or three characters) Intensive Care Beds: XXXX/XXXX (four characters) Minimal Care Beds: XXXX/XXXX (four characters) Operating Room tables: XXX/XXX (four characters).

d. Reporting on ability for sustained operations. In their comments in the MAE section of the CUSR, commanders of measured units will indicate the ability of their units for sustained operations. Address the impacts, if any, of the availability and sufficiency of sustainment stocks (like authorized stockage list, prescribed load list, and so forth) and support items (like tools and other basic issue items) and consider these impacts when estimating the MAE percentage.

e. Mission accomplishment estimate bands of effectiveness.

(1) 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 the position (or has the necessary mobility) to undertake (for a period of 72 hours) the full wartime or primary mission for which it has been organized and designed. The status of personnel, equipment, supplies, consumables, and unit position does not decrease probability of mission success or increase vulnerability of the unit. The unit does not need extraordinary measures or extensive outside mobility assets to compensate for deficiencies.

(2) The 80 to 89 percent band. Report in this band when it is estimated that the unit possesses required resources and training and is in the position (or has the necessary mobility) to undertake (for a period of 72 hours) most of the wartime or primary mission for which it has been organized and designed. The status of personnel, equipment, supplies, consumables, and unit position does not decrease the probability of mission success or increase the vulnerability of the unit under most envisioned operational scenarios. Increases in vulnerability are acceptable relative to mission criticality. The unit may experience isolated decreases in flexibility in methods of mission execution. The unit does not need extraordinary measures or extensive outside mobility assets to compensate for deficiencies.

(3) The 70 to 79 percent band. Report in this band when it is estimated that the unit possesses required resources and training and is in the position (or has the necessary mobility) to undertake (for a period of 72 hours) many, but not all, portions of wartime or primary mission for which it has been organized and designed. The status of personnel, equipment, supplies, consumables, and unit position will decrease the probability of mission success or increase the vulnerability of the unit under many, but not all, operational scenarios. The unit will experience significant decreases in flexibility and increases in vulnerability in many, but not all, operational scenarios. The unit may need extraordinary tactics, procedures, OPTEMPO, or extensive outside mobility assets to compensate for deficiencies.

(4) The 50 to 69 percent band. Report in this band when it is estimated that the unit does not possess the required resources and training or is not in a position (or does not have the necessary mobility) to undertake (for a period of 72 hours) the full wartime or primary mission for which it has been organized and designed. If the situation allows, the unit may be directed to undertake portions of its mission with resources at hand. The status of personnel, equipment, supplies, consumables, and unit position decreases the probability of the mission success or increases the vulnerability of the unit under all envisioned scenarios. Mission success is possible for certain isolated scenarios but flexibility is severely restricted. The unit cannot compensate for deficiencies even with extraordinary tactics, procedures, OPTEMPO, or extensive outside mobility assets.

(5) Below 50 percent band. Report in this band when the unit is undergoing a service directed resource action and is not prepared, at this time, to undertake the wartime or primary 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 so short of personnel or equipment, or deficient in training, that they are unable to perform at least 50 percent of their assigned wartime or primary missions.

9-6. Determining and reporting the chemical, biological, radiological, and nuclear level

The CBRN level is determined and reported to reflect the ability of the measured unit to accomplish/provide its core functions or designed capabilities under chemical and/or biological conditions. The CBRN level corresponds to the lowest (worst case) status level determined for the CBRN S-Level and CBRN T-Level as described in paragraph 4-3 , except that CBRN S-6 levels are discarded. NetUSR user help screens also explain the reporting procedures and the NetUSR User's Guide explains data entry requirements. While the CBRN S-Level and the CBRN T-Level are not factors in determining the unit' s S-Level and T-Level, respectively, commanders of measured units should consider the unit's CBRN level when determining whether to upgrade or downgrade the unit' s C-Level.

9-7. Determining and reporting readiness projections

a. Commanders of major units/headquarters submitting composite reports are required to indicate their 90- day C-level status level projections and their top three issues in the remarks section of their reports. See paragraph 11-2 and AR 220-1 , paragraph 10-4.

b. When units in theater or following deployment are programmed to receive any resources or training required for their primary assigned mission (for example TPE, APS), their commanders also must project when the units are expected to attain sufficient assets to report A-L evel 1. If the unit's current manning status does not meet the manning standards established by the Army tasking authority for its deployment and post deployment manning augmentations are programmed, the commander will project what the LAD plus 30 personnel fill percentage will be and what the assigned mission manning level will be after the unit receives the programmed manning augmentations. See paragraph 9-3 .

9-8. Providing remarks

Units can provide remarks in their reports by clicking on the remarks icon on the NetUSR screen and then typing in the applicable comments. Remarks are mandatory to explain readiness deficiencies and/or to clarify readiness issues.

9-9. Overview of commander's unit status report metrics

Figure 9-3 and the following tables outline the various three-tier and four-tier CUSR metrics explained in this chapter.



Figure 9-3. CUSR metrics




Table 9-1. Core functions or designed capabilities
Core functions or designed capabilities
Four-tier metrics Overall mission readiness assessment Supporting resource and training measurements & assessments
Tier 1 C1 P1 S1 R1 T1 (in accordance with TPU METL training assessments {No U's})
Tier 2 C2 P2 S2 R2 T2 (in accordance with TPU METL training assessments {No U's})
Tier 3 C3 P3 S3 R3 T3 (in accordance with TPU METL training assessments)
Tier 4 C4/5 P4/5 S4/5 R4/5 T4/5 (in accordance with TPU METL training assessments)
Three-tier metrics Overall mission capability
assessment
Supporting METL task capability assessments
Tier 1 Y (in accordance with YQN METL task capability assessments {Majority Y's. No N's}) Y = T in accordance with TPU METL task assessment and the resources required to execute the METL task currently are available to unit or specifically identified
Tier 2 Q (in accordance with YQN METL task capability assessments {No N's}) Q = T in accordance with TPU METL task assessment if the resources required to execute the METL task currently are not available to unit or are not specifically identified but the risks have been mitigated.
Q = P if the resources required to execute the METL task currently are available to unit or are specifically identified
Tier 3 N (in accordance with YQN METL task capability assessments. Any METL task currently assessed as N) N = T, P, or U in accordance with TPU METL assessment if the resources required to execute the METL task currently are not available to unit, are not specifically identified or the risks have not been mitigated
N = U in accordance with TPU METL assessment even if the resources required to execute the METL task currently are available to unit or are specifically identified.


Table 9-2. Assigned mission levels (A-Levels)
A- Level 1 A- Level 2 A- Level 3 A- Level 4
The unit is fully trained and possesses the resources required to undertake the assigned mission. The unit is trained and resourced to undertake most of the assigned mission. The unit is trained and resourced to undertake many, but not all portions of the assigned mission. The unit requires additional resources or training to undertake the currently assigned mission; however, it may be directed to undertake portions of the assigned mission with the resources on hand.


Table 9-3. Assigned mission manning and assigned mission equipping level criteria
Measurement
( Note 1)
Level 1 Level 2 Level 3 Level 4
Assigned Mission
Manning (AMM)
( note 2)
= 90 - 100 percent of mission required personnel and = 85 - 100 percent of mission required senior grade personnel currently are available = 80 percent of mission required personnel and = 75 percent of mission required senior grade personnel currently are available = 70 percent of mission required personnel and = 65 percent of mission required senior grade personnel currently are available <70 percent of mission required personnel or <65 percent of mission required senior grade personnel currently are available
Assigned Mission Equipping (AME)
(notes 3 and 4)
= 90 - 100 percent of mission required equipment items currently are on-hand (available) = 80 - 89 percent of mission required equipment items currently are on-hand (available) = 65 - 79 percent of mission required equipment items currently are on-hand (available) <65 percent of mission required equipment items a currently are on-hand (available)
Notes:
All resource status measurements are based on the applicable requirements documents or ATA guidance that establish or convey the HQDA-approved resource requirements for the assigned mission. The unit's MTOE/TDA requirements will be used if the ATA has not established or conveyed other HQDA-approved manning and equipment requirements.
The assigned mission manning level percentages are determined by dividing the unit's available strength by the mission required strength and the unit's available senior grade strength by the mission required senior grade strength. Mission required personnel are those personnel required by the unit to successfully accomplish the assigned mission as established or conveyed by the Army Tasking Authority. Absent specific guidance regarding the manning requirements for the assigned mission, the AMM level will coincide with the P-Level determination.
The assigned mission equipping level percentage is determined by dividing the number of on-hand (available) equipment items required for the mission (numerator) by the number of mission required equipment items (denominator). When determining this percentage, for the numerator consider ONLY those equipment items that currently are on-hand (available) to the reporting unit in accordance with the availability criteria explained in paragraph 3-5 b . Do not consider any equipment projections (example: TPE). For the denominator, consider ONLY those equipment items designated or approved by HQDA or the ATA as required by the unit to successfully accomplish the assigned mission. The unit's mission requirements normally consist of unit organic equipment and TPE and equipment transfers planned as part of the relief in place process.
Beginning at LAD minus 180 days or earlier when directed, deploying units also will determine and report a projected AME level. While the denominator for this projection will continue to be based on the unit's mission requirements, the numerator will consider equipment that is either currently on hand (available) or projected for use by the unit to accomplish these mission requirements. Accordingly, the numerator for this projection may include TPE following the completion of a PDSS by the unit, APS formally designated for receipt by the unit, and equipment transfers from other units that have been planned, ordered and approved by the applicable authorities. Note that while this projected AME level is a mandatory data point, it is not considered in the A-level determination.
The initial A-Level determination will match the lowest (worst case) of the AMM and AME levels.
Upgrades/downgrades are governed by the provisions of AR 220-1 , paragraph 4-5.


Table 9-4. Primary assigned mission metrics
PRIMARY ASSIGNED MISSION
Four-tier metrics Overall mission readiness assessment Supporting resource and training measurements & assessments
Tier 1 A1 AMM 1 AME 1
Tier 2 A2 AMM 2 AME 2
Tier 3 A3 AMM3 AME 3
Tier 4 A4 AMM 4 AME 4
Three-tier metrics Overall mission capability assessment Supporting METL Task Capability Assessments
Tier 1 Y (in accordance with YQN supporting METL task capability assessments {Majority Y's. No N's}) Y = T in accordance with TPU METL task assessment and the resources required to execute the METL tasks associated with the assigned mission are available to unit or specifically identified
Tier 2 Q (in accordance with YQN supporting METL task capability assessments {No N's}) Q T in accordance with TPU METL task assessment if the resources required to execute the METL tasks associated with the assigned mission currently are not available to unit or are not specifically identified but the risks have been mitigated. Q = P if the resources required to execute the METL tasks associated with the assigned mission currently are available to unit or are specifically identified
Tier 3 N (Any supporting METL task currently assessed as N) N = T, P, or U in accordance with TPU METL assessment if the resources required to execute the METL task currently are not available to unit, are not specifically identified or the risks have not been mitigated
Note: The commander may report either "Yes" or "Qualified Yes" (commander's option) if all of the supporting METL task assessments are evenly split between "Yes" and "Qualified Yes."


Table 9-5. Secondary/additional assigned mission(s) metrics (when capability is available in net centric unit status report)
Secondary/Additional Assigned Missions(s)*
Three-tier metrics Overall capability
assessment
Supporting METL task capability assessment
Tier 1 Y (in accordance with YQN supporting METL task capability assessments {Majority Y's. No N's}) Y = T in accordance with TPU METL task assessment and the resources required to execute the METL tasks associated with the assigned mission currently are available to unit or specifically identified
Tier 2 Q (in accordance with YQN supporting METL task capability assessments {No N's}) Q = T in accordance with TPU METL task assessment if the resources required to execute the METL task currently are not available to unit or are not specifically identified but the risks have been mitigated.
Q = P if the resources required to execute the METL task currently are available to unit or are specifically identified
Tier 3 N (Any supporting METL task currently assessed as N) N = T, P, or U in accordance with TPU METL assessment if the resources required to execute the METL task currently are not available to unit, are not specifically identified or the risks have not been mitigated
Notes:
1. Normally, only organizations at the brigade-level and above will be required to report their mission capability status for more than the one primary assigned mission. Exceptions may include special contingency requirements (that is, QRF, GRF, CCMRF, and so forth) and (for ARNG units) state assigned missions.

2. The commander may report either "Yes" or "Qualified Yes" (commander's option) if all of the supporting METL task assessments are evenly split between "Yes" and "Qualified Yes."


Table 9-6. Chemical, biological, radiological, and nuclear metrics
CBRN Measurements and Assessments
Four-tier metrics Overall CBRN readiness assessment Supporting resource and training measurements & assessments
Tier 1 CBRN-1 CBRN S1 CBRN T1
Tier 2 CBRN-2 CBRN S2 CBRN T2
Tier 3 CBRN-3 CBRN S3 CBRN T3
Tier 4 CBRN-4 CBRN S4 CBRN T4

Chapter 10

Preparing and Submitting Composite Reports

10-1. General

a. Purpose. Composite reports are intended to provide a collective assessment of the status of measured major units (larger than battalion-size) and major headquarters (for example, corps headquarters and modular division headquarters, and so forth,), indicating their ability to accomplish their core functions and provide designed capabilities and also, when applicable, any assigned missions currently required for reporting. For major units, like regiments, brigades, and BCTs, these collective assessments are based on the conditions or the status levels reported by their organic units (minus any detachments) and current augmentations (assigned/attached and OPCON) and the ability of these subordinate units/elements to operate together. For major headquarters, like corps headquarters and modular division headquarters, that by design do not have organic forces beyond their headquarters elements, the collective assessment for the core functions or designed capabilities represented by the C-Level assessment is based on the collective ability of the organic elements (minus detachments) and current augmentations that comprise the headquarters to execute the command and control focused METL. However, for these major headquarters as well as reporting units at lower levels the basis for the A-Level assessments, when applicable, depend on the resources and assets available to accomplish the assigned mission measured against the specific requirements. These available assets and resources include the units/elements currently under command authority that were subordinated to the major headquarters for execution of the assigned mission.

b. Units required to submit reports. AR 220-1 , chapter 8 describes the measured units/headquarters, to include those measured major units and major headquarters that are required to submit composite reports. All currently existing ( post E-date) major units/headquarters listed in Annex A of the ACP are required to submit composite reports, unless they have been specifically exempted in accordance with the provisions of AR 220-1, paragraph 8-5.

c. Special reporting requirements. Commanders of major units/headquarters submitting composite reports are required to indicate their 90- day C-Level status level projections and their top three issues in the remarks section of their reports. When applicable, they also are required to provide A-level projections (see para 9-7 in this publication and AR 220-1, para 10-4).

d. Report types and formats. There are two formats (full and abbreviated) and various report types that apply to the composite reporting requirements established by this regulation. The two report formats are distinguished from each other by the methodology used by them to determine the collective assessments and the number of information and data entries that they require. Reports will be prepared and submitted by the measured major units/headquarters required to submit composite reports in accordance with the guidance and criteria and procedures explained in this paragraph and the NetUSR user help screens.

(1) Full format reports. Major units and major headquarters will submit report types using the full report format except as authorized in paragraph (2), below.

(2) Abbreviated format reports. Composite report types using the abbreviated format are authorized for use while the major unit/headquarters is deployed, when directed by HQDA or the responsible ACOM/ASCC/DRU and/or DARNG, when applicable, because the organizational structure of the major unit/headquarters is not definitively established or because submitting a full format report would involve redundant computations or aggregations of the measured area levels already reported by subordinate units. Reports using the abbreviated format feature a subjective collective assessment of the ability of the major unit/headquarters to accomplish the core functions and provide the fundamental capabilities for which it was designed. Unlike commanders' letters and memorandums that were previously used by some major units/headquarters or the higher command remarks entered into the reports prepared by the headquarters and headquarters company (HHC) commanders, a composite report using the abbreviated format provides the separate assessments required to process the report into the Joint and OSD databases and meets HQDA and Joint Staff requirements for a separate report reflecting the operational judgments of a field grade or senior officer, respectively. Subjective assessments include the commander's determination of the four measured area levels (personnel, equipment on hand available, equipment readiness and training), his assessment of the overall level (C-Level) and the A-Level (when applicable), and comments on readiness management responsibilities (when assigned). Major units and major headquarters that are not required to submit a report type using a full report format may submit a report type using an abbreviated format. Composite reports using the abbreviated format may be submitted by major units and major headquarters currently assigned or apportioned in Joint planning documents that do not have a clearly defined organizational structure or that previously were not required to prepare and submit separate reports. Command and control headquarters above the battalion level that do not have organic forces beyond their headquarters elements may submit a composite report using the abbreviated format.

10-2. Special instructions and procedures for composite reporting

a. Basic unit information data. Enter and update the information on the BUI screens in accordance with the instructions in the NetUSR Users Guide. BUI data entry requirements are applicable to all composite report formats.

b. Availability and accountability of subordinate units/elements.

c. Consider subordinate units/elements, to include personnel and equipment as available or unavailable in accordance with the guidelines and procedures in AR 220-1 and the special instructions for partial deployments and split-based operations in paragraph 3-6 of this publication.

d. Subordinate units/elements included in the organic or designed/established structure of the major unit/headquarters are identified by UIC/DUIC in the BUI data. The UICs/DUICs of augmenting Army units/elements currently under the OPCON authority of the measured units/headquarters and that are included in the commander's collective assessments, because they support the mission(s) for which the major unit/headquarters is designed are identified as organic/assigned. Units under the OPCON authority of the major unit/headquarters but that are not considered available and/or are not included in the commander's collective assessments (for example, non-Army units) are separately identified. Organic/assigned units/elements that are included in the designed/established structure but that have been detached and are not currently under the OPCON authority of the measured unit/headquarters also are separately identified. (Note: For composite reporting purposes, the personnel level (P-Level) and the EOH (available) level (S-Level) of these "detached" units are considered as Level 6 and, therefore, will have a value of 4 in those measured area calculations. This use of Level 6 enhances the accuracy of P-Level and S-Level calculation in composite reports by incorporating the impact of unavailable resources and assets. Equipment readiness levels (R-Levels) will be calculated based on currently available units only. (See basic process in figure 10-1 ). When determining the training level (T-Level) and the overall level (C-Level), commanders of composite reporting units will consider the impact of non-available subordinate units/elements on METL proficiency and the ability of the composite reporting organization to accomplish the wartime mission for which it is organized or designed. When one or more of the subordinate units/elements that is included in the organic/assigned or designed/established structure of the major unit/headquarters is unavailable due to deployment, select reason code D, E, F, or G to identify the percentage of overall capability that is deployed and to indicate that this is primary reason that the overall level is not C1, if appropriate.

e. Subordinate units/elements considered available for the commander's collective assessments of the ability of the major unit/headquarters to accomplish the wartime or primary mission(s) for which it is organized or designed are determined by subtracting the units/elements identified as "detached" and as "OPCON, but not considered" from the units elements identified as organic/assigned. NetUSR will auto-calculate this information and display the results for consideration and use by the unit as required.

f. Examples of units/elements that could be identified as "OPCON, but not considered" are provided in appendix H .

g. C-5 reporting.

(1) Units submitting Type I format composite reports will include subordinate units reporting Level-5 in a measured area or status level computations. When computing composite resource/status levels, include these units as Level-4. If the number of C-5 subordinate units degrades the status of the parent unit below a C-3 overall unit status level, the parent unit will designate the appropriate measured area and the unit's overall level as C-5 (must be approved by HQDA). The number of subordinate units reporting C-5 will be recorded on the remarks section.

(2) C-5 inactivating/discontinuing units may be excluded from composite reports if they are within 180 days of their E-dates. The major combat unit rendering the composite report will continue to report the number of C-5 units. This allows continued accountability of C-5 units. C-5 reporting units will continue to report in accordance with this regulation.

h. Major combat units. The following instructions are applicable to measured major combat units required to submit composite reports:

(1) Units not considered. Do not consider the band, adjutant general (AG), or finance units in composite reports. The measured area levels of non-Army units are not considered when calculating measured area levels.

(2) Squad/crew/team/system manning and qualification data. Consolidate and report squad/crew/team/system manning and qualification data reported by subordinate units in Type I reports.

(3) Special data requirements for Type I reports during partial deployments/split based operations.

(4) When directed by HQDA or the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, commanders of measured major combat units that are required to submit a Type I composite report will determine and report a separate status level for personnel and EOH if they have subordinate units/elements that are considered unavailable for USR purposes. Refer to paragraph 3-6 for guidance regarding detachments the availability of subordinate units/elements for CUSR purposes.) This requirement to report separate status levels for personnel and EOH will be directed when needed to support requirements by HQDA or the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, to assess the capability of the major combat unit to accomplish the wartime or primary mission(s) for which it was organized or designed based on the assumption that all unavailable personnel and equipment will be reunited with the major combat unit prior to mission execution.

(5) The first status level for personnel and EOH will be determined in accordance with the guidance and instructions contained in AR 220-1 , chapters 4 and 9 and and chapters 5 and 6 and of this publication. The availability of subordinate units (includes personnel and equipment) that are operationally deployed is addressed in AR 220-1, paragraph 9-2 and 9-3. In general, personnel attached to deployed units are considered unavailable to their parent units and equipment loaned to deployed units is considered not on hand to the parent unit.

(6) A second subjective level, with comments, is made by the reporting major combat unit commander to describe the unit's potential wartime or primary mission capability if unavailable personnel and/or equipment are assumed to have been reunited with the major combat unit.

10-3. Reserve component premobilization status level

a. Commanders of RC measured major units required to submit a Type I composite report will report the unit's training level (T-Level) and the pre-mobilization training status level, if applicable. The T-Level is applicable to all units and reflects the training proficiency of the units for their wartime or primary missions and tasks. The pre-mobilization training status level reflects the training proficiency of the unit to accomplish the missions and tasks prescribed by the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, for pre-mobilization training. If pre-mobilization training is not applicable to the RC unit, then the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, may exempt the RC unit from the requirement to determine and report its pre-mobilization training status level. The pre-mobilization training status level will be calculated in accordance with chapter 8 .

b. The pre- mobilization C-Level is calculated in the same manner as the C-Level, except that the composite premobilization training status level is used instead of the composite T-Level that reflects the wartime or primary mission proficiency.

c. Pre-mobilization levels are not applicable in Type II composite reports.

10-4. Determining measured area levels and C-Levels for composite reports

a. Full (Type I) reports.

(1) 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. While measured area levels of non-Army units are not included when calculating measured area levels in composite reports, the capabilities provided by these units to support mission accomplishment should be considered when determining whether the C-Level should be upgraded. Measured areas levels and a C-5 level cannot be changed.

(2) Composite C-Levels and measured area levels (except for training) are determined using the methodology outlined in figure 10-1 and the criteria in table 10-1 . The training level is determined in accordance with the applicable provisions of chapter 8. The detailed procedures are explained in the NetUSR Users Guide.



Figure 10-1. Composite reporting calculation methodology




Table 10-1. Composite level criteria (PER, equipment on hand, and equipment readiness)
Level At least 50 percent of units at: Average of units
1 1 1.54 or less
2 2 or better 1.55 to 2.44
3 3 or better 2.45 to 3.34
4 Cannot meet criteria to be level 3

b. Abbreviated (Type II) reports.

(1) When not established by HQDA (DAMO-FMF), the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, will prescribe the subordinate units/elements to be considered by major units or major headquarters approved to submit Type II composite reports. The subordinate units designated to be included in the commander's collective assessments should reflect the most likely war-fighting alignment. The commander will list the UICs and DUICs of the subordinate units/elements included in the Type II composite report.

(2) The C-Level and the status levels of the four measured areas are subjectively determined in a Type II composite report. Commanders will determine the level for each measured area and then select a C-Level in accordance with the following guidelines.

(a) The C-Level in Type II composite reports will be selected based on the lowest level determined for any one of the four measured areas. The levels for the measured areas will be subjectively determined based on reasonable assumptions that have been validated by commanders at higher levels. The C-Level definitions in chapter 9 apply.

(b) The measured area levels in Type II composite reports will be determined by comparing the resource and training requirements of the mission(s) for which the major unit or major headquarters is organized or designed pursuant to the war-fighting or battle command requirements derived from higher commanders' guidance to the current status of resources and training in designated subordinate elements as follows.

(1) Personnel.The commander of the major unit or major headquarters will determine the composite personnel level (P-Level) based on their subjective assessments regarding the quantity of available personnel and the mix of leaders and skills in subordinate units needed to execute the wartime or primary mission(s) for which the major unit or major headquarters was organized or designed. Using validated assumptions and C-Level descriptions provided in chapter 9, the commander will select the personnel level (that is, P-1, P-2, P-3, P-4, or P-6) that corresponds to the C-level description which most accurately depicts the sufficiency of available personnel in subordinate units/elements) to accomplish mission critical tasks (for example, P-1 corresponds to the C-1 description; P-2 corresponds to the Level C-2 description; and P-3 corresponds to the Level C-3 description; and so forth).

(2) Equipment-on hand (available).The commander of a major unit or major headquarters will determine the composite EOH level (S-Level) based on their subjective assessments regarding the adequacy of on hand equipment in subordinate units/elements to execute the wartime or primary mission(s) for which the major unit or headquarters was organized or designed (that is, the quantity and type of equipment, support items, classes of supply, and so forth, that are available to subordinate units/elements). Using the validated assumptions and C-Level descriptions provided in chapter 9 , the commander will select the EOH level (that is, S-1, S-2, S-3, S-4, or S-6) that corresponds to the C-Level description which most accurately depicts the status of the on hand equipment relative to the equipment needed to accomplish mission critical tasks (for example, S-1 corresponds to the Level C-1 description; S-2 corresponds to the Level C-2 description; S-3 corresponds to the Level C-3 description; and so forth).

(3) Equipment readiness.The commander of major unit or major headquarters will determine the composite R-level based on the their subjective assessments regarding the adequacy of operational equipment and equipment sustainability in subordinate units/elements needed to execute the wartime or primary mission(s) for which the major unit or headquarters was organized or designed (that is, the availability in the subordinate units/elements of required operational equipment, support items, repair parts, and so forth). Using validated assumptions and C-Level descriptions provided in chapter 9, the commander will select the ER level (that is, R1, R-2, R-3, R-4, or R-6) that corresponds to the C-Level description that most accurately depicts the operational readiness status and sustainability of the on hand equipment relative to the operational equipment and sustainability needed to accomplish mission critical tasks (for example, R1 corresponds to the Level C-1 description; R-2 corresponds to the Level C-2 description; R-3 corresponds to the Level C-3 description; and so forth).

(4) Training. The commander of a major unit or major headquarters will determine the composite training level (T-Level) based on their subjective assessments regarding the ability of the major unit or major headquarters to execute the wartime or primary mission(s) for which it was organized or designed. Unique environmental conditions also will be considered. Using validated assumptions, training guidance and instructions received from higher levels, and C-level descriptions provided in chapter 9 , the major unit commander will select the T-level (that is, T-1, T-2, T-3, T-4, or T-6) that corresponds to the C-Level description that most accurately depicts the training status of the unit's personnel relative to the collective training proficiency needed to accomplish mission critical tasks (for example, T-1 corresponds to the Level C-1 description; T-2 corresponds to the Level C-2 description; T-3 corresponds to the Level C-3 description; and so forth).

(3) Commanders of a major headquarters that are required to submit Type II composite reports will assess the ability of the designated headquarters units/elements to exercise command and control or battle command in support of warfighting or operations plan (OPLAN) requirements. Commanders should consider each of the battlefield operating systems in their subjective assessments and use READY remarks to identify significant issues and concerns. Use the separate field provided for "oversight" comments, when available, to address issues related to unit/elements for which the commander has oversight of training and/or readiness.

(4) Commander must consider the levels of all measured areas, if applicable, the MAE, when determining whether or not to subjectively upgrade or downgrade the unit' s C-Level.

(5) When required or directed, commanders also will report A-Level data reflecting their assessments of their organizations' ability to accomplish currently assigned missions in accordance with the provision of chapter 9 .

(6) Reason codes and comments are required if the C-Level or the supporting measured area levels are subjectively assessed as other than level 1.

(7) Commanders must review and update BUI screens in conjunction with report submission.

c. Completing composite reports-general. See the NetUSR Users Guide for detailed procedures.

10-5. Mandatory remarks for composite report

a. Mandatory READY and REASON remarks also apply to composite reports. READY remarks are required by all measured units and should focus on the unit's ability to accomplish/provide its core functions or designed capabilities. REASON remarks are required if the overall unit level differs from the lowest measured area level (subjective upgrade or downgrade). Mandatory remarks also are required from commanders of major combat units that have subordinate units/elements that are operating separately. When a unit's overall level is subjectively upgraded or downgraded, both READY and REASON remarks are required.

b. Measured area remarks described in this paragraph relate to composite reports. As with regular reports, these remarks should clarify and support data included in the CUSR. Units that do not attain a level of "1" in a measured area must submit remarks on that area explaining the primary reasons C-1 was not attained.

c. Units submitting composite reports will ensure that the assigned strength information provided in the report accurately reflects the aggregate strength figures of all subordinate organic units (do not include attached) units.

d. Commanders submitting composite reports also will report a composite CBRN equipment status and CBRN T-Level in accordance with the provisions of chapters 8 and 11 and .

e. Commanders required to submit composite reports will list their top three significant issues that affect the overall level (C-Level). These concerns are briefed routinely to the Chief of Staff, Army.

f. All major headquarters/units (those with UIC's ending in FF) will provide a 90-day projected C-Level (overall readiness) based on the commander's assessment of their subordinate organic units' projected levels. These projection figures will be reported in the composite report as a READY remark.

Chapter 11

Preparing and Submitting Deployed Reports

11-1. General

a. Deployed reports are submitted while a unit or organization is deployed away from its home station to execute an operational requirement. The first deployed report, an abbreviated report, is required within 24 hours after the main body closes in theater (during RSOI) or at the deployed location, with a follow on report once the unit achieves 90 percent of personnel and equipment availability; and subsequently, deployed reports are required as of the 15th of each month while the unit or organization is deployed. Deployed reports are due to HQDA NLT 96 hours after the "as of date" or RICDA. Deployed units may use either the full or abbreviated format. Deployed reports allow the commander to continue to determine and report the status of resources and training for the mission for which the unit is designed while, concurrently, determining and reporting the ability of the unit or organization to undertake the current operational requirement. Policy guidance for deployed reporting is provided at AR 220-1 , paragraph 10-5. This chapter explains the specific CUSR requirements and procedures that are impacted by the operational deployment of Army units and organizations. These requirements and procedures are applicable to all Army organizations designated as measured units/headquarters in accordance with AR 220-1, chapter 8.

b. The impact of deployment on specific units and organizations will depend on the deployment/employment circumstances, the assigned missions that are applicable and the external guidance and instructions received from HQDA or the responsible ACOM/ASCC/DRU and/or DARNG, when applicable, regarding Joint and Army status reporting requirements. These impacts may include changes to command relationships and authorities (for example, ADCON and OPCON), guidance for determining the availability of Soldiers and subordinate units, CUSR management oversight responsibilities and/or CUSR submission channels, the mandatory information and report types required, and CUSR submission timelines

11-2. Preparing and submitting reports

The overall levels and the levels for the supporting measured areas (see para 3-5 ) may be determined in an abbreviated/subjective manner (abbreviated format report) for status reporting by commanders of operationally deployed units. While the short report format in NetUSR contains all mandatory data reporting requirements, commanders of deployed units are not precluded from submitting a "full" report that contains the same information as a full report submitted from the home station. When the expanded report format is incorporated into NetUSR software and made available for use, commanders also may submit an "expanded" report that will enable unit commanders to report any additional CUSR information they deem relevant to the status of their units. The appropriate sets, fields, and labels must be used in expanded and full reports. The procedures in this chapter are specifically relevant to unit status reporting while deployed and supplement the procedures elsewhere in this publication that govern unit status reporting while at the home station and, unless specifically stated otherwise, continue to apply.

a. Personnel status. Personnel status data will be reported in accordance with the provisions of chapter 5 . 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. 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 at the deployed location within 72 hours to meet operational requirements or unless the rear detachment DUIC is not currently under the OPCON authority of the deployed parent unit.

b. Equipment-on hand (available). Only ERC P and ERC A MTOE required equipment items must be reported. Equipment left in the rear detachment will be considered as EOH (available) only if it meets the conditions specified in AR 220-1 , paragraph 9-3i and chapter 6 of this publication, and the rear detachment DUIC is currently under the OPCON authority of the deployed parent unit. The key criteria are that the equipment remains under the operational control of the deployed unit commander; the commander retains visibility of that equipment; and that an established plan exists to deploy the equipment in support of the unit's mission requirements within 72 hours. Equipment currently in the unit's possession that was borrowed against its MTOE requirements will be considered as EOH (available) and included in the unit' s S-Level status determination in accordance with the provisions of paragraph 9-3 and chapter 6. The borrowing unit will not consider equipment with no MTOE requirement in its S-Level status determination that is borrowed or issued solely to meet the unit's assigned mission requirements unless the borrowed equipment is an authorized substitute for MTOE required equipment items.

c. Equipment readiness/serviceability. Only ERC P and ERC A equipment readiness reporting are required. The percentage of on hand equipment fully mission capable and the percentage of pacing items on hand fully mission capable will be based on the status of equipment on the "as of" date of the report, not a monthly average used when reporting from the home station. Commanders will consider only the equipment in possession of subordinate units/elements that are under the OPCON authority. Accordingly, the readiness status of equipment in the rear detachment will be considered for the R-Level status determination only if the rear detachment remains under the OPCON authority of the deployed/employed unit.

d. Training level determinations and mission essential task list proficiency assessments.

(1) Training level determinations. While a measured unit is operationally deployed, commanders determine the training proficiency status of their units to undertake the wartime or primary mission(s) for which they are organized or designed following the same procedures described in chapter 8 for a regular report, but use abbreviated/subjective processes to derive results.

(2) Mission essential task list proficiency assessments. Unless exempted by HQDA (DAMO-ODR), deployed units will continue to report their METL proficiency assessments while deployed. The commander will assess unit task proficiency for METL tasks using the TPU metrics in accordance with procedures explained at the ATN Web site. However, when circumstances preclude following detailed assessment processes, the commander need not formally solicit input from subordinates to derive his overall TPU assessment of unit proficiency in each METL task. Instead, the commander may subjectively derive his METL proficiency assessment based on his personal knowledge. Subsequently, the unit' s T-Level will be auto-calculated by NetUSR based on these discrete METL proficiency assessments.

(3) Other training data. When required by HQDA (DAMO-ODR) or directed by the responsible ACOM/ASCC/DRU, units will determine and report other training related data ( CBRN T-Level and squad/crew/team/system manning and qualification data in accordance with the procedures in chapter 8.

e. Mission and task capability assessments. Commanders of measured units are required to determine and report their Y/Q/N mission and task capability assessments in all reports, to include deployed reports. The procedures for determining and reporting these assessments are explained in chapter 9 .

f. Readiness projections. Commanders of major units submitting a deployed report will continue to indicate their 90- day C-Level status level projections and their top three issues in the remarks section of their deployed reports. The NetUSR user help screens explain procedures and provide detailed instructions.

g. USR management oversight. Unless formally specified or directed otherwise, the responsible ACOM/ASCC/DRU-level command is responsible for CUSR management oversight of the Army units under their ADCON authority while these units are deployed. Pursuant to the deployment of Army units during a crisis and in wartime, the responsible ACOM/ASCC/DRU/TAG-Level command will coordinate with the gaining command and publish orders to specify the ADCON responsibilities to be retained by the losing command. CUSR management oversight is an important ADCON responsibility that must be addressed in these orders. See AR 220-1, paragraphs 4-9 and 4-10 and .

11-3. Basic deployment scenarios

For CUSR purposes, there are three basic deployment scenarios (total deployment, full deployment and partial deployment) that are applicable to Army units/elements registered in the DRRS-Army database and also a task force/team deployment scenario that is applicable to the deployment of ad-hoc Army organizations. Each of these deployment scenarios has specific implications to the CUSR requirements of the deploying/deployed Army units and elements. The specific implications of these scenarios to the CUSR are illustrated by examples provided in appendix H . Each of these scenarios is defined in the Glossary and NetUSR user help screens provide additional information.

Chapter 12

Preparing and Submitting Other Reports

12-1. General

The CUSRs are comprised of BUI, readiness and capability measurements, assessments, and data points, and the commanders' comments. There are two formats for CUSRs-"full" and "abbreviated" and four categories of reports that the commanders of units, organizations and installations use to report the required information into the DRRS-Army database via NetUSR-"Regular" reports, "Validation" reports, "Deployed" reports and "Change" reports. Procedures for entering force registration data and updates into DRRS-Army via the Force Registration Application are explained in part III of this publication and the NetUSR Users' Guide and user help screens. The procedures for preparing and submitting "Regular" and "Deployed reports are explained in chapter 10 and chapter 11 of this publication, respectively. This chapter explains procedures for preparing and submitting other reports.

12-2. Validation reports

The RC units (ARNG/ARNGUS and USAR) and custodians of APS submit a validation report when there is no change in readiness status from the last report submitted. Validation reports enable RC units and APS custodians to meet the Joint Staff's requirement for a monthly report (without the need to prepare a completely new report) when there are no significant changes in the readiness status of the unit. A validation report cannot be used if there is any change to an overall level, the status level of any measured area, the location, mission, or the command relationship with the next higher level. Since Validation reports merely update the RICDA of the readiness status information and data contained in the previous report, they assume the format of the previously submitted report. Validation reports must have a RICDA indicating the 15 th of the month.

12-3. Change reports

These reports have a RICDA other than the 15 th of the month and are submitted to report a change or update to the readiness status data or information of a reporting unit. Significant changes requiring the submission of a change report include any change to an overall readiness status level or overall capability assessment, any change to a measured area level, even if the overall level does not change, and any change to location, mission, or the command relationship with the next higher level. Change reports are required to be submitted within 24 hours of the event requiring the change report. When applicable, change reports can differ in format from the previous report or the change report can replicate most of the data contained in a previous report, except for the changed status data.

12-4. Derivative unit identification code reports

When required to report, DUIC organizations will submit special abbreviated reports (see table 3-1 ).

12-5. Reports of units governed by tables of distribution and allowances

a. The TDA units that are required to report into the DRRS-Army database are those with AA-Level UICs (parent units) that have not been officially exempted from reporting in accordance with the procedures in AR 220-1 , paragraph 8-5. These TDA units will submit reports in accordance with the reporting frequency requirements and the minimum data entry requirements established in chapter 4 for TDA units submitting CUSRs.

b. The CUSR management oversight authority in coordination with HQDA, DAMO-ODR, can require additional TDA units/elements or detachments to submit reports or require more frequent reporting than addressed in paragraph a , above. For example, the CUSR management authority, after coordinating with HQDA (DAMO-ODR), can designate as a reporting unit a TDA entity with a DUIC that is not addressed in paragraph a , above. Similarly, the CUSR management authority can direct a TDA unit with an AA-Level UIC to report monthly vice quarterly. TDA units reporting pursuant to requirements established by the CUSR management authority must comply with the procedures explained in this paragraph and the NetUSR Users' Guide and user help screens. For example, TDA units/elements with DUICs directed to report into the DRRS-Army database must use the applicable NetUSR report types designed for DUICs. All reports will be forwarded to HQDA in accordance with the submission timeline explained in AR 220-1, table 4-1.

12-6. Multiple component unit reports

a. General.

(1) Regardless of the force structure component (COMPO), multiple component units will submit a single report through the CUSR management oversight authority. The COMPO 1-Active Component, COMPO 2-ARNG, COMPO 3-USAR, or COMPO 6-APS units will submit their reports in accordance with the timelines and criteria in AR 220-1 , table 4-1.

(2) A multiple component unit is a unit that, on a single document, is authorized personnel and/or equipment from more than one component ( COMPO 1, 2, or 3). The intent of the multiple component initiative is to integrate, to the maximum extent within statutory and regulatory constraints, resources from more than one component into a cohesive, fully capable Army unit.

(3) Multiple component units are MTOE units under either AC or RC command and control.

(4) Each component specific element of a multiple component unit is assigned a derivative UIC (DUIC). The parent unit and its derivatives appear on the same MTOE document. An "N" in the second character of a UIC denotes that the unit is a MTOE multiple component unit. The fifth character of the derivative UIC denotes the component as follows: "X" for AC, "G" for ARNG, and "R" for Army Reserve. "AA" in the 5 th and 6 th position indicates the parent roll-up of all DUICs.

(5) The FF-Level organizations are composed of a number of AA-Level units, each organized under its own MTOE/TDA and therefore, by definition, FF-Level units are not multiple component units. Multiple component units can be AA-level units (that is, battalions and separate companies with subordinate AC and RC units and elements on the same authorization document). Multiple component units may contain subordinate units and elements that are multiple components themselves (for example, multiple component companies in multiple component battalions) as well as subordinate units and elements that are not (for example, ARNG pure dual-missioned elements that are assigned to, and documented with, multiple component battalions).

(6) Commanders of multiple component units determine training priorities, establish the unit's METL, and develop the training plan in accordance with the governing memorandum of agreement (MOA). The signature authority for the MOA is the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable; and the State Adjutant General (TAG), as appropriate. A letter of Agreement, when used, may further detail component relationships within the constraints of the MOA. The approval authority of the letter of agreement is the first general officer in each resourcing chain of command unless otherwise specified in the MOA. Assigned personnel and subordinate elements train and prepare to deploy as a unit to accomplish the wartime or primary mission.

b. Concept for multiple component unit status reporting. Each component-specific element (AC, ARNG/ARNGUS, and USAR) will provide USR feeder data to the flag holding (or sponsoring component) commander (AA-Level UIC). The multiple component commander (flag holder) will submit a consolidated USR that shows the status of the entire unit. Unit status reporting will remain in compliance with unit status reporting policy and procedures contained in this regulation for other types Army measured units. The ARNGUS/ARNG and Army Reserve feeder data will consist of quarterly regular reports, monthly validation reports, and periodic change reports or regular reports, as required by unit status changes. The ARNGUS/ARNG elements will submit reports to the Adjutant General with copies to the multiple component commanders and to the NGB as directed by NGB-ARR. The Army Reserve elements will submit reports to HQ, USARC via GCCS. Specific USR procedures for multiple component units will be addressed in a coordinated memorandum of agreement or policy letter. All unit status data (personnel and equipment) on the measured unit's MTOE/TDA (applicable to AA-Level multiple component units, regardless of component) will be considered and included in the USR in accordance with this regulation. The governing multiple component unit MOA may direct additional reporting requirements.

c. Reporting procedures for multiple component AA-Level units.

(1) Commanders of multiple component units (AA-Level) will submit a single consolidated unit status report for the entire unit (as documented on the MTOE/TDA) through the responsible higher headquarters as required by AR 220-1 .

(2) Commanders of multiple component units (AA-Level) that have subordinate units or elements that are not listed as DUICs on their MTOE/TDA will not include unit status data from these dual-missioned units in their USR. Commanders of these units/elements will submit their unit status data (USR or USR feeder data) to their respective component command (that is, AC, ARNG/ARNGUS, and USAR) in accordance with the reporting requirements in this regulation that are applicable to their component and will provide a copy of their unit status data to the commander of the multiple component unit for information.

(3) There are no other special Instructions, for completing CUSRs for multiple component units. Follow this regulation as you would for a single component unit.

d. Personnel status level determination (see chap 5).

e. Equipment on hand (available) status level determination (see chap 6).

f. Equipment readiness status level determination (see chap 7).

g. Training status level determination (see chap 8).

h. Overall category level determination (see chap 9).

12-7. Installation status reports

a. Army installations required to submit reports.

(1) Designated Army Installations are required to report quarterly into the DRRS-Army database. The authoritative listing of the installations and facilities currently required to provide quarterly reports, to include their UICs and corresponding installation codes (I/C) are posted and maintained at DAMO-ODR's unclassified and classified Web sites, and they also are accessible via the DRRS-Army portal.

(2) The authoritative listing of the Army installations required to submit quarterly reports into DRRS-Army is located on DAMO-ODR's unclassified and classified Web sites and the DRRS-Army portal under the CCSA files labeled "Data Extract file Installations Required to Report NetUSR (date of last update)." The unclassified and classified Web sites can be accessed using the following paths and information:

(a) Unclassified Web site (NIPRNet): available at AKO at https://www.us.army.mil/suite/page/137868 .

(b) Classified Web site (SIPRNet): available on AKO-S at http://www.us.army.smil.mil/suite/page/7531 .

(c) If unable to open the DAMO-ODR sites on AKO or AKO-S using the above paths, then proceed as follows: once logged into AKO or AKO-S, use the site map to navigate to Army Organizations -> Operations -> Army Readiness Division.

b. Installation status reporting requirements. HQDA (DAMO-ODR), in coordination with ACSIM, DARNG, and the responsible ACOM, ASCC, and DRU will incrementally establish and implement policies and procedures for Army installations to report into DRRS-Army. Specific guidance and implementing instructions will be provided to execute each iteration. During the initial phase of installation status reporting, critical power generation platforms and power generation support platforms designated by HQDA in coordination with ACSIM and IMCOM will report their METs into DRRS-Army using the new Y/Q/N metrics for capability assessments and provide mandatory commander comments. Subsequently, HQDA (DAMO-ODR), in coordination with ACSIM, DARNG, and the responsible ACOM, ASCC, and DRU, will refine the initial installation status reporting requirements and will establish requirements for status reporting by additional installations in follow-on implementing instructions.

c. Reporting channels. The IMCOM or USAAMC installations will report to HQDA through the Northeast, Southeast, West, Pacific, Europe, Korea, and the National Capital Region-D (NCR-D) regional offices, as appropriate. Installations under the purview of the Army National Guard (ARNG) will report through the appropriate JFHQ-State through the National Guard Bureau to HQDA. For other Army installations, the responsible ACOM, ASCC, or DRU will designate the appropriate reporting channels to HQDA.

d. Reporting changes to capability assessments.

(1) Changes to a MET assessment. Commanders of reporting units, to include the commanders of Army installations required to report into DRRS-Army, will report any change to a MET assessment that does not result in a change to the mission category assessment supported by that MET in the next monthly report when due. Changes to a MET assessment that result in a change to a mission category assessment will be reported within 24 hours after the commander determines the changed assessment in accordance with the instructions below.

(2) Changes to mission category assessment. Commanders of reporting units, to include the commanders of Army installations required to report into DRRS-Army, will report any changes to their capability assessments for a mission category within 24 hours of the commander's determination that the capability assessment has changed. Other changes to the readiness status of a reporting unit or installation will be reported into DRRS-Army in a change report prepared and submitted in accordance with the procedures explained in Appendix R of this publication and the NetUSR user help screens.

e. Security classification. All CUSRs submitted by Army installations into the DRRS-Army database are classified CONFIDENTIAL.

f. Other. Appendix G and the NetUSR user help screens explain the detailed procedures for status reporting by Army installations.

12-8. Army Force Generation status data

a. General. The DAMO-ODR has established various ARFORGEN data points and will continue to refine Army readiness reporting policy, procedures, and software to support ARFORGEN implementation and emerging ARFORGEN processes in coordination with FORSCOM, ACOMs, ASCCs, DRUs, ARSTAF, and, when applicable, DARNG and state adjutant generals. The ARFORGEN status reporting process will exploit current internet and automation technology to simplify and significantly enhance the readiness reporting by making it less burdensome to reporting units and more responsive to the requirements of commanders, resource managers, and senior leaders for timely, accurate, and complete readiness information, while concurrently incorporating mission focused capability assessments in support of the ongoing implementation of ARFORGEN, OSD DRRS, DRRS-Army and GSORTS. As requirements emerge for additional data and information to support ARFORGEN implementation, DAMO-ODR will revise and update the provisions of AR 220-1 , this publication and the supporting NetUSR software as necessary. Additional data points and information requirements will be incorporated through rapid action revision and become reportable by reporting units as supporting NetUSR software becomes available. The ARFORGEN data points that are supported by the current NetUSR software and that are visible via the ARMS application are listed and explained in ARMS user's guide. The NetUSR users guide and user help screens provide specific data entry instructions.

b. Unit status reporting requirements. While all units will provide the applicable information in each of the ARFORGEN fields, the most critical ARFORGEN reporting requirement are the force pool assignment and the expeditionary force package designation for rotational units and the force type/component designation for other units. The critical force type/components are defined in appendix I . The ARFORGEN force pools and expeditionary force packages that provide the framework for the structured progression of increased readiness over time are explained in AR 525-29 .

c. Army Force Generation data points.

(1) Because the basis for the measurements and/or assessments associated with several of the current ARFORGEN data points are either subjective, situation dependent or must be established and/or validated by appropriate authorities at higher levels, specific command guidance or supplementary instructions are essential to achieving effective implementation.

(2) The ASCC will provide guidance to focus the METL training of each subordinate unit as explained in the CSA's Army Training and Leader Development Guidance (ATLDG) and FM 7-0 .

(3) The Army tasking authority will issue the necessary command guidance to support ARFORGEN implementation and accurate readiness reporting. This command guidance will include, but is not limited to, conveying or approving the resource and training criteria and baselines for measuring the unit's readiness for its assigned mission(s), so that unit commanders can accurately determine and regularly report on the readiness status of their units in the CUSR using the CUSR metrics and the ARFORGEN data points explained in this publication and the NetUSR user help screens.

(4) Mandatory ARFORGEN data reporting requirements explained in this publication include the unit's current ARFORGEN force pool assignment and expeditionary force package designation for rotational units, the force type/component designation for non rotational units, and the return date for all units. For re-deploying units, the return date is the date when more than 50% of the unit's assigned personnel have returned from deployment. For all other units, the return date is the date established by or approved by FORSCOM for the unit to enter the RESET force pool. During the 180/365 day ( COMPO 1/RC) time period that rotational units are in the RESET force pool, reporting units will report C-5/T-5 in accordance with the provisions of para AR 220-1 , paragraph 4-8. The Army tasking authority will provide detailed guidance to commanders regarding the applicability of the other ARFORGEN data points to their units and will recommend to HQDA (DAMO-ODR) any new or revised ARFORGEN data points required to improve the management or implementation of the ARFORGEN process.

(5) Unit proficiency level. See paragraph 8-7 c .

12-9. Determining aggregate equipment on-hand status by Force Structure Component and by state or territory

a. General. This paragraph explains the basic policies and business rules that will be used to determine and, when necessary, to report the aggregate EOH (available) status and the aggregate EOH (accountable) status by COMPO and by state or territory to ensure that uniform results are produced to respond to externally directed reporting requirements. Calculating the aggregate EOH (available) and EOH (accountable) status by COMPO and by state or territory is a special requirement that is not related in any way to the S-Level calculations reported by Army reporting units in the CUSR to support their C-Level assessments. In addition to equipment status data imported from or furnished by authoritative sources, these special EOH calculations may use some equipment status data contained in CUSRs. However, these special EOH calculations will be accomplished only at HQDA-level and the provisions of this paragraph establish no additional status reporting requirements for individual Army reporting units. Detailed procedures for determining both the aggregate EOH (accountable) status and the aggregate EOH (available) status by COMPO and by state or territory are explained in appendix E .

b. Percent of fill. The current aggregate EOH status for each COMPO and state or territory will be determined as a percentage of fill calculated by LIN and designated equipment category. The percent of fill is calculated for EOH (accountable) and EOH (available) by dividing the EOH (accountable) quantity by the authoritative requirements and by dividing the EOH (available) quantity by the authoritative requirements, respectively. The detailed procedures are explained in appendix E.

c. On-hand (accountable) equipment items.

(1) COMPO 1 and COMPO 3. All equipment items for which the units/elements in the COMPO are accountable based on current property records are considered in determining the on-hand (accountable) quantity for COMPO 1 and COMPO 3. COMPO 3 Combat Support Hospitals also will include the equipment on hand in the Reserve Component Hospital Decrement (RCHD) program as part of the calculation for on hand (accountable) equipment. This data is provided by the U.S. Army Medical Materiel Agency RCHD USR Feeder Data Report. An EOH (accountable) quantity for each state or territory is not calculated for either COMPO 1 or COMPO 3.

(2) COMPO 2. All equipment items for which COMPO 2 units/elements are accountable based on current property records are considered in determining the on-hand (accountable) quantity for COMPO 2. EOH (accountable) status by state or territory also is calculated for COMPO 2. If COMPO 2 units have organic elements located in more than one state or territory, then DARNG will identify the accountable assets applicable to each state or territory.

d. On-hand (available) equipment items.

(1) COMPO 1 and COMPO 3. The on-hand (available) quantity is the same as the on-hand (accountable) quantity for COMPO 1 and COMPO 3. COMPO 3 Combat Support Hospitals also will include the equipment on hand in the Reserve Component Hospital Decrement (RCHD) program as part of the calculation for on hand (available) equipment.. This data is provided by the U.S. Army Medical Materiel Agency RCHD USR Feeder Data Report.

(2) COMPO 2. The on-hand (available) quantity for COMPO 2 is the same as the on-hand (accountable) quantity. However, the on-hand (available) quantity for each state territory will include only those on-hand (accountable) equipment items that are possessed by the COMPO 2 units that currently are under the control of that state or territory. Equipment items in the possession of ARNG units that are on federal duty status (that is, 10 USC status for mobilization) will not be considered in the calculation of the EOH (available) quantity by state or territory.

e. Critical dual use equipment items. Critical dual use (CDU) equipment items are those equipment items that support both the operational requirements of Army units ( COMPO 1, COMPO 2, and COMPO 3) and that are necessary to enable Army units ( COMPO 1, COMPO 2, and COMPO 3) and personnel to assist civil authorities in responses to natural disasters, acts of terrorism, and other man-made disasters as identified in national planning scenarios (that is, facilitate Defense Support of Civil Authorities). The Army's authoritative CDU list is developed and updated by the DARNG, formally approved by the Army DCS, G-3/5/7, and maintained by the DCS, G-8 for use at HQDA to meet all externally directed equipment status reporting requirements.

f. Equipment status projections. The 24 months out projections of future aggregate EOH (accountable) status and future aggregate CDU EOH (accountable) status will be prepared using the current aggregate equipment on-hand (accountable) status as a starting point and adding those distributions that have been approved during the Army Equipping Enterprise and Reuse Conference and loaded in the Army Equipping Enterprise System (AE2S). Projections of the future EOH (available) status or the future EOH (available) CDU status will not be calculated.

g. Equipment categories. The following categories of aggregate EOH status will be calculated and reported semiannually for each COMPO and, for COMPO 2 equipment items only, for each state, territory, and the District of Columbia.

(1) Aggregate EOH (accountable).

(2) Aggregate EOH (available).

(3) Aggregate CDU EOH (accountable).

(4) Aggregate CDU EOH (available).

(5) Aggregate EOH (accountable) projection 24 months out.

(6) Aggregate CDU EOH (accountable) projection 24 months out.

Chapter 13

Security Classification, Declassification, and Release of Defense Readiness Reporting-Army Information, Data and Reports

13-1. General

a. In accordance with the provisions of AR 380-5 , the DCS, G-3/5/7 has been delegated original classification authority (OCA) for all information, data and reports contained in the DRRS-Army database. The DRRS-Army information, data, and reports that warrant protection from unauthorized disclosure via security classification include information, data, and reports that identify or indicate the following:

(1) The current or planned missions or vulnerabilities of specific units or that could expose them to unnecessary risks, to include mobilization and deployment data on specific units.

(2) The commander's assessment of current or projected overall unit readiness or capability and the measurements of the specific resource status levels and training status levels supporting that assessment.

(3) The measurements and the assessments resulting from the application of the CUSR metrics or methodology in AR 220-1 that establish the unit's current readiness status, to include the commander's assessment of the unit's current capability to accomplish a specific plan, mission, operation, task or contingency requirement.

b. Accordingly, the type of DRRS-Army information, data and reports described above are classified under the provisions of Presidential Executive Order (EO) 12958, Sections 1.5(a) and 1.5(g). This order prescribes a uniform system for classifying, safeguarding and declassifying national security information. Original classification under the provisions of Section 1.5(a) concerns military plans, weapon systems, or operations. Original classification under the provisions of Section 1.5(g) concerns vulnerabilities, or capabilities of systems, installations, projects, or plans relating to the national security. The classification of a report is based on both the type of unit and the type of information and data contained in the report. The security classification of information and data extracted from a report, requests/approvals associated with readiness status reporting measurements and/or capability assessments requirements, and readiness status information applying CUSR metric procedures or metric criteria are based on the sensitivity of that information.

c. The procedures explained in this chapter are specifically applicable to all information, data and reports presently contained in the DRRS-Army database, to include any information or data that has been entered or any report that has been submitted via a DRRS-Army software application for processing into the DRRS-Army database. This includes, but is not limited to, the CUSRs that are prepared and submitted via the NetUSR application in compliance with the provisions of AR 220-1 , the readiness information and data contained in or extracted from these reports following their submission, any readiness information and data that apply the metric procedures or metric criteria established by AR 220-1 to specific reporting units, and to all force registration information and data entered into the DRRS-Army database via the Force Registration application in accordance with the provisions of AR 220-1, chapter 6 and the procedures in part III of this publication.

d. The provisions of this chapter are not applicable to information, data and reports regarding the personnel status, equipment status or training status of units, Soldiers or equipment that reside in or is derived from other databases or systems or to reports, information and data that do not apply CUSR metric procedures or metric criteria. Additionally, the provisions in this chapter are not applicable to feeder reports or to other input data prepared by subordinate units/elements or compiled by reporting units prior to its formal approval by the commander of the reporting unit for submission into the DRRS-Army database as part of an official CUSR. Prior to its approval by the unit commander and submission into the DRRS-Army database, unit status information and data is under the purview of the chain of command for determination of security classification.

e. Classified information will be marked, protected, and transmitted in accordance with the provisions of AR 380-5 and AR 25-2 . CUSRs, sensitive information extracted from reports (as described in this chap), and C-5 requests/approvals will be marked with a specific declassification date.

13-2. Security classification of commander's unit status report information and data

a. Table 13-1 for METL task assessment information.

Table 13-1. Minimum classification guidance for mission essential task list assessments (modification table of organization and equipment units)
Type METs Minimum Classification
Individual METs METL task assessments (Y/Q/N)*
Battalion (BN)/SEP CO Brigade (BDE) AND ABOVE
The METs contained in the standardized FSO METL UNCLASSIFIED CONFIDENTIAL SECRET
The METs associated with a Current Operation CONFIDENTIAL, unless classified otherwise by the operation or plan classification or the appropriate Tasking Authority CONFIDENTIAL, unless classified otherwise by the operation or plan classification or the appropriate Tasking Authority SECRET, unless classified otherwise by the operation or plan classification or the appropriate Tasking Authority
The METs associated with a Contingency Operation (CONOPS) CONFIDENTIAL, unless classified otherwise by the operation or plan classification or the appropriate Tasking Authority CONFIDENTIAL, unless classified otherwise by the operation or plan classification or the appropriate Tasking Authority SECRET, unless classified otherwise by the operation or plan classification or the appropriate Tasking Authority
METL for a State assigned Mission CONFIDENTIAL, unless classified otherwise by the operation or plan classification or the appropriate tasking authority CONFIDENTIAL, unless classified otherwise by the operation or plan classification or the appropriate tasking authority SECRET, unless classified otherwise by the operation or plan classification or the appropriate tasking authority
* TPU METL task assessments accomplished in accordance with FM 7-0 and ATN are UNCLASSIFIED, unless classified by the command, tasking authority, or METL approval authority.

b. Table 13-2 shows the measurements of resources and training status.

Table 13-2. Minimum classification guidance for resource and training status measurements (modification table of organization and equipment units)
BN/SEP CO BDE AND ABOVE
Personnel (P-Level) CONFIDENTIAL SECRET
Equipment On-hand (S-Level) CONFIDENTIAL SECRET
Equipment Readiness (R-Level) CONFIDENTIAL SECRET
Training (T-Level) CONFIDENTIAL SECRET
CBRN Equipment Status ( CBRN S-Level) CONFIDENTIAL SECRET
CBRN Training Status ( CBRN T-Level) CONFIDENTIAL SECRET
A ssigned Mission Manning (AMM) level CONFIDENTIAL SECRET
Assigned Mission Equipping (AME) level CONFIDENTIAL SECRET

c. Table 13-3 show the metrics and data points.

Table 13-3. Minimum classification guidance for metrics and data points
Metrics for the measured area levels Minimum classification
BN/SEP CO BDE AND ABOVE
Available Strength Percentage CONFIDENTIAL SECRET
Available DMOSQ Strength Percentage CONFIDENTIAL SECRET
Equipment On-hand Percentage (Pacing Item) CONFIDENTIAL SECRET
Equipment On-hand Percentage (Overall ERC A & ERC P) CONFIDENTIAL SECRET
Equipment Readiness Percentage (Pacing Item) CONFIDENTIAL SECRET
Equipment Readiness Percentage (ERC A & ERC P) CONFIDENTIAL SECRET
METL Training Percentage CONFIDENTIAL SECRET
OTHER DATA POINTS
Squad/Crew Manning and Qualification Data CONFIDENTIAL SECRET
ARFORGEN Data Points (see Note) UNCLASSIFIED (except as noted below) UNCLASSIFIED (except as noted below)
Plan Numbers (w/o association to names or descriptions) UNCLAS (for official use only (FOUO)) UNCLAS (FOUO)
All other CUSR data points CONFIDENTIAL SECRET

Notes:
1. The mision and LAD data reported by units among ARFORGEN data points is classified by other sources.

d. Table 13-4 shows the overall levels and assessments.

Table 13-4. Minimum classification guidance for overall assessments
Type of Overall Assessments Minimum Classification
BN/SEP CO BDE AND ABOVE
Core functions or designed capabilities CONFIDENTIAL SECRET
MAE CONFIDENTIAL SECRET
Assigned Mission Level (Current Operations Assessment) CONFIDENTIAL SECRET
Assigned Mission Level (CONOPS Assessment) CONFIDENTIAL SECRET
Assigned Mission Level (State Assigned Mission) CONFIDENTIAL, unless classified at a higher level by the Tasking Authority CONFIDENTIAL, unless classified at a higher level by the tasking authority
CBRN Level CONFIDENTIAL SECRET

e. Classification of CUSR data when aggregated with other data. When CUSR data is aggregated in a document or Web-enabled system, the classification of the document or the system must be coordinated with and specifically approved by HQDA (DAMO-ODR). This restriction is applicable to CUSR data elements obtained from a single report, CUSR data elements obtained from multiple reports, and any CUSR data to be used in combination with other data residing in the DRRS-Army database that is not part of the CUSR (for example, force registration data, imported background data, and so forth,) and data obtained from other systems. Table 13-5 outlines the minimum classification guidance when the document or Web-enabled system contains any of the following sensitive information supported by CUSR data elements. See paragraph 1-3 c regarding the security classification of aggregated force registration data.

Table 13-5. Minimum classification guidance for commander's unit status report data when aggregated with other data
SENSITIVE INFORMATION SUPPORTING CUSR DATA ELEMENTS MINIMUM CLASSIFICATION WHEN AGGREGATED
Current or Planned Unit Activity BUI and ARFORGEN Data CONFIDENTIAL
Deployed Unit Location ARFORGEN Data CONFIDENTIAL
Current Mission Assignment ARFORGEN Data SECRET
Plan numbers ARFORGEN Data SECRET, when associated with names and/or descriptions. UNCLAS (FOUO) when listed alone.
Names and/or Descriptions of Assigned Plans or Operations ARFORGEN Data SECRET
OPCON Relationships BUI Data CONFIDENTIAL
METL Task Assessments See table 13-1 SECRET
Resource and Training Measurements See table 13-2 SECRET
Other CUSR Metrics and Data Points See table 13-3 SECRET
Overall Assessments See table 13-4 SECRET

13-3. Security classification of commander's unit status reports

a. The following classification guidelines apply:

b. Minimum classification of the CUSRs of MTOE units and organizations.

(1) SECRET when the CUSR is a report submitted by a MTOE organization at the brigade level and above, to include the major units and major headquarters.

(2) SECRET when more than one battalion or five or more separate MTOE company/detachment-size units (AA-level UIC) are represented or reflected in the report.

(3) CONFIDENTIAL for all reports not classified SECRET in accordance with the guidelines above.

(4) Reports that reference specific plans, operations or exercises will be classified either with the classification of the plan, operation or exercise, or consistent with the guidelines established in paragraphs (1), (2), and (3), above, whichever results in the higher classification.

c. Classification of information extracted from CUSRs of MTOE units and designated TDA units reporting in accordance with the provisions of AR 220-1 , paragraph 3-4 d . In addition to the provisions for minimum classification established in tables 13-1 , 13-2 , 13-3 , and 13-4 , above, any portion of the CUSR that reflects current or projected overall readiness status measurements or capability assessments, to include squad/crew manning and qualification data; the mission accomplishment (MAE); and/or references to deployability, employability, or inability to accomplish an assigned mission are classified as follows:

(1) SECRET when this information represents or reflects the status of a MTOE organization at brigade-level or above, to include major units and major headquarters.

(2) SECRET when this information represents or reflects more than one MTOE battalion or five or more separate MTOE company/detachment-size units (AA-Level UIC).

(3) CONFIDENTIAL when this information is not classified SECRET in accordance with the guidelines in sub paragraphs (1) and (2), above.

d. Classification of requests and approvals for C-5 status reporting by MTOE units and designated TDA units reporting in accordance with the provisions of AR 220-1, paragraph 3-4 d . Because requests for and approval of C-5 status reporting may provide insight into the deployability, employability, or inability of specific unit(s) to accomplish/provide their core functions or designed capabilities, these requests are classified as follows:

(1) C-5 requests/approvals will be classified SECRET if more than one battalion or five or more separate company/detachment-size units are addressed in the request/approval or if the request/approval addresses a unit of brigade size or above, to include a major unit or major headquarters.

(2) Requests/approvals not classified SECRET in accordance with the guidelines in paragraph (1), above, will be classified CONFIDENTIAL.

e. Classification of CUSRs submitted by TDA units, organizations, and installations. The security classification of CUSRs submitted by TDA units, organizations and installations is CONFIDENTIAL, unless a higher level of security classification has been specifically prescribed. For example, CUSRs from TDA units and organizations required to report in accordance with the provisions of AR 220-1 , paragraph 3-4 d are classified in accordance with the same criteria that are applicable to MTOE units (see para c , above). All CUSRs submitted by Army installations are classified CONFIDENTIAL in accordance with the provisions in AR 220-1, paragraph 4-14.

f. Table 13-6 outlines the minimum classification of reports by type of reporting unit.

Table 13-6. Minimum classification guidance for commander's unit status reports
SENSITIVE INFORMATION SUPPORTING CUSR DATA ELEMENTS MINIMUM CLASSIFICATION WHEN AGGREGATED
Current or planned unit activity BUI and ARFORGEN Data CONFIDENTIAL
Deployed unit location ARFORGEN Data CONFIDENTIAL
Current mission assignment ARFORGEN Data SECRET
Plan numbers ARFORGEN Data SECRET, when associated with names and/or descriptions. UNCLAS (FOUO) when listed alone.
Names and/or descriptions of assigned plans or operations ARFORGEN Data SECRET
OPCON relationships BUI Data CONFIDENTIAL
METL task assessments See table 13-1 SECRET
Resource and training measurements See table 13-2 SECRET
Other CUSR metrics and data points See table 13-3 SECRET
Overall assessments See table 13-4 SECRET

13-4. Security classification of force registration information and data

The guidelines for the minimum security classification of force registration data are depicted in tables 13-7 and 13-8 and .

Table 13-7. Classification of force registration information and data for modification table of organization and equipment units
SET and/or Type Data
Criteria by Type and Number of TDA Units
SORTUNIT, RPTDUIC & BIDE SETS
ANAME, UTC ULC TPSN ABIDE ETC.
RPTNORG, LOSING, GAINING & TRANSFER SETS
RPTOR SBRPT INTR CMD ETC.
ORGLOCN SET
CSERV OPCON ADCON HOGEO PRGEO ACTIV ETC.
RESERVE SET
Mobilization/ Deployment Data
PERSTREN SET
Personnel Data
MEQLOCN SET
Major Equipment Data
1 - 5 subunit UICs or DUICs UNCLAS ( note 1) UNCLAS ( note 2) UNCLAS ( note 2) CONFIDENTIAL ( note 3) UNCLAS ( note 4) UNCLAS ( note 4)
6 or more subunit UICs or DUICs UNCLAS ( note 1) UNCLAS ( note 2) UNCLAS ( note 2) SECRET ( note 3) UNCLAS ( note 4) UNCLAS ( note 4)
1 - 5 Separate Companies (AA-Level UIC) UNCLAS ( note 1) UNCLAS ( note 2) UNCLAS ( note 2) CONFIDENTIAL ( note 3) UNCLAS ( note 4) UNCLAS ( note 4)
6 or more Separate Companies (AA-Level UIC) UNCLAS ( note 1) UNCLAS ( note 2) UNCLAS ( note 2) SECRET ( note 3) UNCLAS ( note 4) UNCLAS ( note 4)
One Battalion (AA-Level UIC) UNCLAS ( note 1) UNCLAS ( note 2) UNCLAS ( note 2) CONFIDENTIAL ( note 3) UNCLAS ( note 4) UNCLAS ( note 4)
Two or more Battalions (AA-Level UICs) UNCLAS ( note 1) UNCLAS ( note 2) UNCLAS ( note 2) SECRET ( note 3) UNCLAS ( note 4) UNCLAS ( note 4)
Major Unit/HQ (FF-Level UIC (Any number) UNCLAS ( note 1) UNCLAS ( note 2) UNCLAS ( note 2) SECRET ( note 3) UNCLAS ( note 4) UNCLAS ( note 4)

Notes:
1. This data may be classified for some units.
2. This data may be classified up to SECRET during deployed operations or crisis.
3. This data may be classified at a higher level based on the systems from which the data was derived and/or current operational requirements.
4. This data will be updated based on CUSR data during crisis when directed by HQDA (DAMO-ODR) or the responsible ACOM, ASCC, DRU or, for ARNG units not on active duty, by DARNG.


Table 13-8. Classification of force registration information and data for table of distribution and allowances units
Criteria by Type and Number of TDA Units ANAME, unit type code (UTC) ULC TPSN ABIDE ETC RPTOR SBRPT INTR CMD ETC CSERV OPCON ADCON HOGEO PREGEO ACTIV ETC Mobilization/ Deployment Data Personnel Data Major Equipment Data
1 - 5 subunit UICs or DUICs UNCLAS ( note 1) UNCLAS ( note 2) UNCLAS ( note 2) CONFIDENTIAL ( note 3) UNCLAS ( note 4) UNCLAS ( note 4)
6 or more subunit UICs or DUICs UNCLAS ( note 1) UNCLAS ( note 2) UNCLAS ( note 2) CONFIDENTIAL ( note 3) UNCLAS ( note 4) UNCLAS ( note 4)
1 - 5 Separate Companies (AA-Level UIC) UNCLAS ( note 1) UNCLAS ( note 2) UNCLAS ( note 2) CONFIDENTIAL ( note 3) UNCLAS ( note 4) UNCLAS ( note 4)
6 or more Separate Companies (AA-Level UIC) UNCLAS ( note 1) UNCLAS ( note 2) UNCLAS ( note 2) CONFIDENTIAL ( note 3) UNCLAS ( note 4) UNCLAS ( note 4)
One Battalion (AA-Level UIC) UNCLAS ( note 1) UNCLAS ( note 2) UNCLAS ( note 2) CONFIDENTIAL ( note 3) UNCLAS ( note 4) UNCLAS ( note 4)
Two or more Battalions (AA-Level UICs) UNCLAS ( note 1) UNCLAS ( note 2) UNCLAS ( note 2) CONFIDENTIAL ( note 3) UNCLAS ( note 4) UNCLAS ( note 4)
Major Unit/HQ (FF-Level UIC (Any number) UNCLAS ( note 1) UNCLAS ( note 2) UNCLAS ( note 2) CONFIDENTIAL ( note 3) UNCLAS ( note 4) UNCLAS ( note 4)

Notes:
1. This data may be classified for some units.
2. This data may be classified up to SECRET during deployed operations or crisis.
3. This data may be classified at a higher level based on the systems from which the data was derived and/or current operational requirements.
4. This data may be reported by units during crisis when directed by HQDA (DAMO-ODR) or the responsible ACOM, ASCC, DRU or, for ARNG units not on active duty, by DARNG.

13-5. Declassifying and downgrading Defense Readiness Reporting-Army information, data, and reports

a. The CUSRs and readiness status information and data extracted from CUSRs and readiness status information and data applying CUSR metric procedures or metric criteria will be marked with a specific downgrading and declassification date. Classification applies when the information or data was submitted for processing into the DRRS-Army database or the "as of" date of the report. The declassification date will be 8 years from the date of classification. Secret information will be downgraded to confidential 4 years after the date of classification. The intent of this downgrading and declassification process is to make all information, data and reports unclassified within 8 years of the classification date. Requests to downgrade or to declassify DRRS-Army information, data or reports outside the time lines prescribed in this paragraph will be forwarded to HQDA (DAMO-ODR) for evaluation on a case-by-case basis.

b. Information classified by the authority of a separate security classification guide or similar authority will be declassified in accordance with the security classification guide instructions.

c. This publication may be cited as the authority for the classification of CUSRs, sensitive information extracted from reports, readiness status information applying CUSR metric procedures and metric criteria, C-5 requests/approvals, and force registration information. The responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, may establish additional classification guidance for CUSRs and the data contained in CUSRs, not to exceed SECRET with the approval of HQDA.

13-6. Access to and release of Global Status of Resources and Training System and Defense Readiness Reporting System-Army information and data

a. General. The CUSRs are prepared by units via NetUSR and then submitted via ADCON channels for processing into the DRRS-Army database. Force registration data is entered into the DRRS-Army database by UICIOs and designated force management officials via the Force Registration application. Subsequently, the DRRS-Army database updates the Joint Staff's GSORTS database with current readiness and force registration information for Army measured units and registered entities. The ARMS application provides visibility of selected Army readiness status and force registration data and information contained in the DRRS-Army database to authorized users of ARMS. Policy for NetUSR and ARMS registration are established in AR 220-1 , chapter 2. Provisions regarding user registration for the Force Registration application are in AR 220-1, chapter 5 . This paragraph explains policy guidelines regarding access to and release of any DRRS-Army information or data obtained via any of these DRRS-Army applications and any data applying CUSR metrics obtained via other means.

b. Joint Staff guidelines. The Joint Staff authorizes the Services to release GSORTS data to members of DOD having a valid need to know and the appropriate clearance. Services may only release information on their units and only that amount of information required to satisfy the requirement. Joint Staff approval is required prior to the release of any GSORTS data (classified and unclassified) to any non-DOD requester or to any foreign agency. The GSORTS database in classified as SECRET/NOFORN.

c. HQDA policy.

(1) Information and data reported into the DRRS-Army database is under Army purview until such time as that information and data is processed by HQDA into the GSORTS database whereby it becomes GSORTS data falling under the purview of the Joint Staff. Except as noted in the following paragraphs, HQDA requires Army units to obtain HQDA approval to release DRRS-Army information outside of Army channels, to include its release to either DOD or non-DOD agencies or to any of their sub-elements (that is, to other Services, joint organizations, GAO, members of Congress, and so forth).

(2) The restriction against releasing DRRS-Army information and data outside of Army channels does not apply to properly cleared officers participating in an official foreign officer exchange program with an Army organization and having a valid need to know based on their formally assigned duties. Also see AR 25-2 , paragraph 4-15, regarding foreign access to information systems.

(3) The five theater armies (USARNORTH, USARSO, USARCENT, USAREUR, and USARPAC) and EUSA are authorized to release DRRS-Army information and data on the units under their ADCON authority to their applicable combatant commands and sub unified commands, and USASOC and FORSCOM similarly are authorized to release DRRS-Army information on units under their ADCON authority to the Special Operations Command and Joint Forces Command, respectively. The coalition partners of the various combatant commanders will obtain information and data on Army forces from the combatant commander.

(4) Requests for other approval to release DRRS-Army information and data outside of Army channels will be made in writing and forwarded to the ODCS, G-3/5/7 (DAMO-ODR/Army Readiness Division), 400 Army Pentagon, Washington, DC 20310-0400. The Army Readiness Division will obtain concurrence from J-3, Joint Staff, before approving the release of any GSORTS information to non-DOD agencies.

13-7. Retention of data

a. The CUSRs will be retained on file for no less than 2 years at the major unit/headquarters level and for not less than 6 months by other reporting units (AA-Level UIC). Electronic files of CUSR data submitted via NetUSR or printed copies of NetUSR screen shots may be retained to satisfy this requirement. CUSRs 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 readiness 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. Submit all requests for readiness status data that is not in the possession of the unit to the ODCS, G-3/5/7 (DAMO-ODR/Army Readiness Division), 400 Army Pentagon, Washington, DC 20310-0400.

13-8. Specific policies and procedures for Defense Readiness Reporting System-Army Information, data, and reports referencing the entire Army, Army National Guard, United States Army Reserve, and other large groupings

a. The CUSR data that is aggregated or projected for identifiable entities and large groupings above the level at which Army units are required to report will be classified SECRET if the data references deployability/employability or associates a specific CUSR metric or overall unit assessment with a specific number of units or a specific percentage of units. (1)

(1) Identifiable entities above the level at which Army units report include the entire Army, the Active Component, the ARNG, the USAR, a specific state, a specific command or any other specific grouping of a large number of Army units by category, status, type, or location (for example, by COMPO, force pool, force package, warfighting function, installation, SRC, LAD, boots on the groud end date, and so forth).

(2) CUSR metrics are the readiness status measurements and assessments accomplished (includes projections) in accordance with the criteria established by this regulation that directly support the calculations or the determinations of the resource measurements, capability assessments, and/or the overall unit assessments that are required to be reported. CUSR metrics include the three-tier metrics (for example, the Y/Q/N assessments for the METL tasks) and the four-tier metrics (for example, the P, S, R, and T-Levels) described in AR 220-1 , paras 4-2 and 4-3). The overall unit readiness assessments include the required capability assessments for the core functions or designed capabilities (C-Level and Y/Q/N assessment) and any assigned missions (A-level and/or Y/Q/N assessments), CBRN level and MAE as described in AR 220-1, chapter 4. References to actual or projected deployability/employability status applicable for classification include references that indicate specific geographical locations or identify response times, capabilities, or limitations.

(3) For the purpose of determining the security classification of DRRS-Army information and data, a specific number of units or specific percentage of units covered by these provisions also includes descriptive terms that explicitly establish a number or percentage like "all," "none," "two thirds," "one half," "one out of ten," and so forth.

b. When all of the above three elements are associated in a document, statement or discussion, the resulting readiness information will be classified as SECRET. Also, if two separate statements in the same document or discussion, when considered together, disclose DRRS-Army data classified under the provisions of this chapter, then the document and each statement will be considered as classified. For example the following notional statements would be classified as SECRET.

(1) Eighty-five percent of the Army currently is reporting C1.

(2) Sixty USAR units currently are reporting S2.

(3) All units at Fort Swampy currently are reporting T3.

(4) Eighteen Army IBCTs currently are reporting A-L evel 4.

(5) Fifty-five percent of the Army units in state X currently report "Q" for their overall assessments of core functions or designed capabilities.

(6) Twenty four of the fifty-five Army units examined during the inspection currently are reporting "Y" for the "movement to contact" METL task.

(7) All of the ARNG units in State X currently are reporting a percentage of fill (determined in accordance with the provisions AR 220-1 and app P) of 80 percent or higher.

(8) Seventy-five percent of the Army units stationed in location X are currently reporting S2 or better.

(9) Two thirds of the ARNG units in state X currently are reporting an overall CBRN level of 4.

(10) Only 1 of 10 ASCC X units is currently reporting a MAE of 90 percent or higher.

(11) Army units reporting C3 or higher are considered as deployable for global operations. Seventy percent of Army units currently are deployable for global operations.

(12) Sixty percent of the Army is projected to be S2 or better by the end of FY09.

(13) Two thirds of the ARNG combat brigades in the Train-Ready force pool are projected to be C3 by October 20XX.

13-9. Specific procedures applicable to auditors, Congress, and the general public

a. Auditors and inspectors of the Government Accountability Office or the Office of the DOD Inspector General have legal authority under Public Laws 96-226 and 97-252 for access to DRRS-A information and data. Only the President or Secretary of Defense can deny final access.

b. Release of data to Congress and its committees, staff and investigators is governed by DODD 5400.4 .

c. Requests from the public for readiness data are processed under provisions of the Freedom of Information Act. Requests must be referred to the Directorate for Freedom of Information and Security Review.

d. Army units will forward all requests for Army readiness data received from GAO, DODIG, members of Congress, and the general public to HQDA (DAMO-ODR) for action or approval. When required, HQDA (DAMO-ODR) will refer denial proposals to the Joint Staff/J-39 for resolution action.

13-10. Specific access authorizations to readiness data

a. All systems that use or provide access to readiness data under the purview of this regulation will ensure that only appropriate personnel are authorized access to the readiness data elements. Personnel must have a valid need to know and hold the appropriate level of security clearance. Coordinate access to readiness IT systems with HQDA (DAMO-ODR) and/or USACCSA.

b. Developers and administrators of application systems (that is, MDIS, ARMS, and so forth) that use or provide access to readiness data will ensure that only appropriately designated personnel are authorized access to readiness data elements according to approved permissions. Developers and administrators of applications that access or use readiness data will staff and coordinate with HQDA (DAMO-ODR) an interface control document that documents the readiness data used by the application. Developers and administrators of these systems will not grant access or release readiness data, the database schema, the requirements traceability matrix, or any other technical documentation for use by, or in other applications.

c. System administrators that hold or maintain copies of the readiness database must ensure that only appropriately designated personnel are authorized access to it. Administrators of these systems will not grant access or release readiness data, the database schema, the requirements traceability matrix, or any other technical documentation without approval of HQDA (DAMO-ODR). The HQDA (DAMO-ODR) will staff all requests for access with affected commands and agencies prior to approval.

Part Three

Force Registration and Basic Identity Data Element Procedures

Part three of this DA Pam provides procedural guidance for the registration of units in the DRRS-Army database, the authorized database of record for operational Army organizations

Part three of this DA Pam provides procedural guidance for the registration of units in the DRRS-Army database, the authorized database of record for operational Army organizations

Chapter 14

Overview

14-1. General

a. General. The DRRS-Army is the authorized database of record for operational Army organizations. For these organizations, it establishes procedures for entering and maintaining official unit identification codes (UICs) and derivative unit identification codes (DUICs) in the DRRS-Army database. It is important to note that this DA Pam serves as the authoritative source of Army procedures regarding the development and operational use of official Army UICs/DUICs and that the force registration procedures contained in this DA Pam take precedence in the event of any conflict with the procedures established by other HQDA agencies regarding the development and operational use of official UICs/DUICs in automated Army systems. A UIC is not valid for operational use by an Army organization in Army systems until it has been properly registered in the DRRS-Army database in accordance with the procedures set forth in this DA Pam. The procedures in this DA Pam regarding the creation and use of DUICs are applicable only to those DUICs that must be registered in the DRRS-Army database in order to interface properly with other automated Army systems. Unofficial DUIC-like constructs that are developed separately by other agencies for their internal use are not considered approved or official DUICs, and they may not be used in automated Army systems. This restriction is applicable to any unofficial DUIC-like constructs created under policy provisions established by Army agencies solely to support their internal requirements or unique processes. The development, management and use of these unofficial DUIC-like constructs within the internal processes of the agencies that created them fall outside of the purview of this DA Pam.

(1) Part III of this DA Pam complements AR 220-1 and also the provisions in Part II of this publication by establishing the procedures for proper registration of the UICs and DUICs in the DRRS-Army database for all Army organizations, to include reporting units. Change in unit status, as defined in AR 220-1 and explained in this DA Pam, applies to all Active Component and Reserve Component (RC) units organized under modified tables of organization and equipment (MTOE) or tables of distribution and allowance (TDA) that are registered in the DRRS-Army database. Changes in unit status include (but are not limited to) redesignations, modernizations, reorganizations, conversions, activations, inactivations (MTOE units), discontinuations (TDA units), reactivations, mobilizations, demobilizations, deployments, redeployments, and so forth.

(2) Another major function of the DRRS-Army database is to serve as the central registry of all operational Army organizations and units. All operational Army units must be registered in the DRRS-Army database, to include civilian accounting, contractor accounting, non-U.S. military, logistics, personnel accounting, and cellular derivatives. This DA Pam prescribes which units to register, activate, and remove from the DRRS-Army database and explains how and when to accomplish these transactions.

(3) Maintaining attribute data is the third major function of DRRS-Army database. Attribute data consists of information regarding the unit's location, chain of administrative and operational command, mobilization status, personnel, and major equipment. This DA Pam includes specific guidance for entering data into the DRRS-Army database, and it also contains information about the interface between DRRS-Army and other automated Army systems. (A data element dictionary is provided on line (see app I .)

b. Specific guidelines. This DA Pam establishes detailed procedural guidelines for the following:

(1) Registering parent (AA-Level UIC) units in DRRS-Army.

(2) Registering UICs for titular (FF-Level UIC) organizations in DRRS-Army. Titular UICs are derived from an already registered headquarters unit (AA-Level). Titular units include corps, divisions, brigades, groups, regiments, commands, and agencies.

(3) Registering DUICs in DRRS-Army. These include

(a) Structurally defined subordinate organizations (sub-unit UICs) that are already documented in The Army Authorization Document System-Redesign (FMS), such as, companies, batteries, troops, detachments, teams, and so forth.

(b) Elements or fragments of such units as platoons, squads, sections, or teams when they are required for Command operational support or functions.

(c) Functionally comprised or task-organized elements of units when they are required to report unit status data and/or are required for detached operations or functions.

(d) Carrier UICs that facilitate the activation of new units.

(e) TDA augmentation units created to augment an MTOE unit to accomplish specific missions for which the MTOE unit was not designed or structured.

(f) Administrative (ADMIN) DUICs that may be registered in the DRRS-Army database only as directed by HQDA or when specifically approved by the responsible ASCC, DRU, or DARNG/NGB (for ARNG not on active duty) to facilitate administrative or logistics requirements established for deploying/deployed units. (See chap 20.)

(4) Activating units previously registered in DRRS-Army. (See para 16-7 .)

(5) Inactivating and discontinuing units. (See para 16-20 .)

(6) Performing data maintenance with any changes in to a unit's status or its attributes. (See para 16-7.)

(7) Performing unit transfers between commands. (See para 16-19 .)

(8) Changing reporting responsibilities or mobilizing units. (See para 16-7.)

(9) Data review. (See para 16-8 .)

14-2. References

Required and related publications and prescribed and referenced forms are listed in appendix A .

14-3. Responsibilities

See AR 220-1, paragraph 3-2.

14-4. Access to the Defense Readiness Reporting System-Army Database and the Force Registration Application

The DCS, G-3/5/7 has overall responsibility for granting access to the DRRS-Army database and the Force Registration application. The DCS, G-3/5/7 has delegated authority to grant DDRS-Army access to the United States Army Command and Control Support Agency (USACCSA) at HQDA and to designated commands and DASAs. Commands and DASAs that have been delegated authority to grant access may only grant access to users subordinate to their command or agency. Paragraph 3-9 explains the procedures to gain access to the Force Registration application. The following figure illustrates the UICO hierarchy.

14-5. Registration, frequency, and communication precedence of updates

a. Unit registration.

(1) The registration process for parent (AA-Level) UICs is initiated when an approved UIC is issued by DCS, G-3/5/7 Force Management Division (DAMO-FMP) and a skeleton record is created in DRRS-Army by USACCSA.

(2) Subsequently, the command or DASA UIC information officer (UICIO) completes the registration of the parent (AA-level) UIC and all structured DUICs (sub-unit UICs), in accordance with the permanent order, MTOE document, and/or other documentation.

(3) Additionally, the command or DASA UICIO will register all DUICs required for current operations, deployments, and mobilizations in accordance with the procedures in this DA Pam.

b. Reporting frequency and procedures.

(1) Routine data updating will be accomplished on a daily basis or as required, unless changes to selected data elements have occurred.

(2) The ACOM UICIO (or ASCC UICIO, when applicable) must provide data updates to USACCSA within 24 hours following changes to the present location (PRGEO), the current status and activity code (ACTIV), the operational command and control (OPCON), and/or administrative control (ADCON) fields.

c. Precedence of reports. The ACOMs, ASCCs, DRUs and DARNG/NGB must have a sufficient number of personnel trained as DRRS-Army data handlers and as alternate UICIOs to maintain continuous (that is, 24 hours a day, 7 days a week) operations during an emergency or crisis.

d. Technical channels. Figure 14-1 illustrates UICIO technical channels However, direct coordination and communication between UICIOs and force registration officials is authorized and encouraged when necessary to address and resolve force registration issues.



Figure 14-1. UICIO Hierarchy


14-6. Unit registration process

a. Background.

(1) Organizations are assigned a UIC to facilitate processing of information in other automated Army systems. Because the DRRS-Army database updates Army information in the GSORTS database, the UICs and DUIC registered in the DRRS-Army database also are registered in the GSORTS database. This UIC/DUIC registration in the DRRS-Army and GSORTS databases provides a standard method of identifying units as official organizations in the automated systems within the Army and throughout the entire Defense community.

(2) All Army organizations providing information/data input to any component of GCCS or other DOD systems that use UICs must be registered in the DRRS-Army database at HQDA and the GSORTS database maintained at the National Military Command Center (NMCC). Organizations without registered UICs are not recognized as valid organizations, irrespective of their status or restructuring importance. The DRRS-Army database at HQDA is the system of record (SOR) for Army UIC(s). The database at the NMCC is the SOR for all UIC(s) (Joint, combined commands, combatant commands, defense organizations, U.S. Army, U.S. Navy, U.S. Marines, U.S. Air Force, U.S. Coast Guard), and other government organizations.

b. Parent unit's unit identification code registration.

(1) The UIC registration requests: Organizations authorized to request establishment of parent level UICs are ACOMs, ASCCs, DRUs, DARNG/NGB and designated DASAs. In order to request establishment of a UIC, these organizations will submit requests to DCS G-3/5/7 (DAMO-FMP) for assignment of a parent UIC based on a command plan approved by the Directorate of Force Management (DAMO-FM) or a valid position in SAMAS. Upon approval by DAMO-FM), a parent UIC will be issued within 30 days. The requesting organization has 3 working days to pass this information to the respective UICIO for further processing.

(2) A unit is approved in accordance with the applicable provisions of AR 71-32 . The ACOM, ASCC, DRU, DARNG/NGB or DASA requests must contain the following information, referred to as parent UIC assignment request data. Proposed reorganization/effective date (ODATE/EDATE), command assignment (ASGMT), planned unit location, proposed troop program sequence number (TPSN), SRC, proposed Operating Force/Generating Force categorization in accordance with ACP DP 99, and ACOM, ASCC, DRU, or DARNG/NGB.

(3) The Center of Military History (CMH) provides LNAME for requested parent UICs and TITULAR (FF) UICs approved and submitted by DAMO-FMP. CMH will determine if there is an inactive unit with a lineage or other attributes that warrant its activation. If conditions warrant reactivation, the previously assigned historic UIC and the LNAME will be provided to DAMO-FMP. Otherwise, CMH will provide a new unit number, LNAME, and any other applicable nomenclature. The DAMO-FMP UIC manager must provide the following information (at the minimum) to USACCSA for the purpose of initial entry into the DRRS-Army database: organization security classification (SCLAS), UIC, TPSN, component (COMPO) "1," "2," "3," "6," SRC or table of distribution and allowance (TDA) number, abbreviated organization name (ANAME), ASGMT, unit level code, (SRC level for TOE), planned organization date (ODATE), carrier UIC (if applicable), and carrier ODATE (if applicable). USACCSA enters the skeletal BIDE/ABIDE in the DRRS-Army database, thus creating a new unit record. This will be accomplished within 3 working days after receipt of the information from the DAMO-FMP UIC manager.

(4) Provisional UICs are not authorized and cannot be registered. (The definition of a provisional unit is provided in the glossary.)

(5) Parent unit registration flow. Figure 14-2 illustrates the steps in establishing a parent UIC.



Figure 14-2. Parent unit registration flow


c. Structured DUIC(s) for sub-organizations, subunits, sub-elements, and split organizations will be obtained from authoritative data sources and ACOM, ASCC, DRU, DARNG/NGB, or DASA UICIOs will register them into the DRRS-Army database after the assignment of the parent UICs and their full registration in the DRRS-Army database. Upon registration in the DRRS-Army database, DRRS-Army will automatically update the GSORTS database and those of other agencies and commands, as required. The following describes the types of organizations/sub-organizations that can be assigned DUIC(s) and registered in DRRS-Army database, and subsequently in the GSORTS database.

(1) Titular (FF) organization. This can be for a command, Army, corps, division, brigade, or a regiment, Titular organizations stem from an already registered headquarters and headquarters company, battery, troop, or detachment. In effect a parent (AA-Level) UIC must exist before deriving a titular UIC from it. A titular UIC will not have an SRC or TDA reported.

(2) Structural derivative unit identification codes. The Structural DUICs identify subunits whose structure is documented in a specific section, paragraph, or line number of an approved FMS SRC which expresses the structure of these subunits. Company and equivalent level units have a unique SRC on FMS. Cellular organizations in FMS have a unique SRC to identify cells that perform their primary mission away from their parent organization. Registering subunits that have a unique SRC in FMS, is mandatory. These subunits are registered as derivatives in DRRS-Army. The last two characters from (see table 15-2 ) distinguish the DUIC. The first four characters are the same as the parent UIC. Each time the cellular unit is reorganized, the registered cells are reviewed for accuracy and completeness. Planned UIC(s) deleted from the active file will not be added to the archive database. Fragments of units that do not have an SRC documented in FMS require derivative registration if they report personnel and/or equipment status data. Likewise, sub-elements of TDA organizations that report personnel and/or equipment require DUIC registration. Definitions of major derivative units are as follows:

(a) A sub-organization or subunit is a portion of a parent unit with a unique SRC which is documented in FMS.

(b) A sub-element is a portion of a TDA unit generally made up of multiple paragraphs of the TDA. Registering sub-elements of TDA units as DUIC(s) facilitates permanent party reporting.

(c) A split organization is a part of a parent or derivative organization stationed at a different location from the main or headquarters portion of the organization. Registering the split portion of the organization as a DUIC ensures getting equipment and supplies to the correct location and accounting for the personnel and equipment at the correct location.

(3) An augmentation unit is a TDA unit that augments an existing MTOE organization. The design facilitates execution of specific missions that the MTOE unit is unable to conduct alone. This type of DUIC is considered a 1st level DUIC and will be registered into DRRS-Army in accordance with chapter 16 .

(4) A carrier unit allows the assignment of resources to a registered unit before its EDATE (actual activation). The carrier unit gets deleted automatically on the EDATE of the parent unit. This type of DUIC is considered a 1st level DUIC and will be registered into DRRS-Army in accordance with chapter 16.

(5) Senior Reserve Officers' Training Corps units. Register these units with an UTC ending in "FRAG" following special rules for personnel status code.

(6) Junior Reserve Officers' Training Corps units. Register these units as property books, following all rules for property book registration.

(7) Functional derivative unit identification code. In the absence of regulatory reasons and/or under extraordinary circumstances, a functional derivative is provided to satisfy management requirements. Extraordinary circumstances may be temporary or permanent in nature. The feature common to them is the need for visibility of resources not attainable by using their existing structure. The following organizations are some examples of units provided with functional derivatives:

(a) Nonpermanent party.Organizations must account for nonpermanent party personnel not chargeable to the personnel authorization of a TOE organization. Schools and training units have TDA(s) to account for their cadre, but they use DUIC(s) to separately manage their students.

(b) Stock records, property books, or maintenance accounts.Management needs require unique identification of these records. See chapter 16 regarding correct coding for these types of UIC(s).

(c) Rear detachments.These elements remain behind at the unit's home location under the purview of the unit commander when the commander and a portion of the unit deploy. Registration of a DUIC is required for the rear detachment to account for non-deploying personnel, to receive replacements, and to maintain property accountability. This DUIC is inactivated or maintained for future use once the main body returns to the rear detachment's location, ensuring that all personnel and equipment previously assigned to the rear detachment are assigned to the returning UIC.

(d) Ad-hoc units.Units organized from one or more parent units to conduct unique missions, require unique identification. These UIC(s) are for missions of a limited duration and do not have a corresponding structure in FMS. An ad-hoc unit's UIC is derived from the parent UIC. The parent unit supplies the commander/person in charge. If the ad-hoc unit does not have a formally designated commander, derive the DUIC from the parent UIC contributing the most resources to the organization. Inactivate the DUIC when the mission has been completed and personnel or equipment have been returned to original units.

(e) Special management unit identification code(s).Special circumstances or unique management needs may arise that require the use of a DUIC. For example, the ACOM, ASCC, DRU, or DARNG/NGB might register a DUIC to function as a replacement detachment (control measure) for USAR volunteers in response to a crisis. Another use of this type of DUIC is to account for the ARNG personnel assigned to a specific unit or state in excess of structural requirements.

(f) Multiple-component unit identification code(s).These units can be made up of some combination of Active Component, ARNG, or USAR personnel. Parents as well as derivative-level UIC(s) are registered by the DAMO-FMP, DA UIC manager in SAMAS. The parent UIC is a placeholder and does not contain personnel or equipment. All personnel and equipment are maintained in the DUIC(s). The second position for Multi-component UICs/DUICs is 'N' and the sixth position of these UIC(s) is 'G' for ARNG, 'R' for USAR, and 'X' for AC organizations, respectively. DAMO-FMP provides the initial data elements for registration into Status of Resources and Training System and these DUICs are considered as 1st level DUICs. Refer to tables 15-1 , 15-2 , and 15-3 for types of UIC(s). (See fig 14-3 .) All structured multiple-component UICs/DUICs are considered 1st level DUICs and will be registered into DRRS-Army in accordance with chapter 16 .

(g) Contractor/vendor elements.These entities/organizations are separately managed and organized to provide maintenance services and other support to Army organizations. This functional DUIC type includes Army contractor operations that are independent government maintenance operations and separately report their completed work project. It is not applicable to contract/vendor maintenance personnel who augment military/civilian maintenance operations, or who are integrated into an Army MTOE or TDA maintenance organization reporting its completed work product in accordance with AR 750-1 , DA Pam 750-8 , and DA Pam 738-751 .

(h) Left behind equipment derivative unit identification codes.These are special DUICs that are created for the equipment left behind when a unit that maintains a property book deploys to a theater of operations. These DUICs will have an "L" in the 5 th position of the DUIC and they will be assigned to the Army Materiel Command (AMC) for CONUS-based units and to the local command authority for OCONUS units. Equipment will be designated as LBE and transferred to this DUIC in accordance with the policy and procedures established by the DCS, G-4. Units will consider LBE in their S-Level calculations in accordance with the provisions of AR 220-1 , paragraphs 4-3 b (2) and paragraph 6-9 c in this publication.

(i) DUICs supporting doctrinal operational formations that are not reflected in the MTOE - usually teams, sections, or crews. These DUICs are usually permanent and registered at the discretion of the ACOM, ASCC, DRU, or DARNG/NGB. They are used for units that deploy in small elements at short notice so that appropriate administrative support can be provided in a timely manner.



Figure 14-3. Derivative unit identification code registration flow


14-7. Database corrections and synchronization

a. Synchronization. The DRRS-Army database is composed of several thousand data elements that are used by numerous Army, Joint, and DOD offices and agencies for various purposes. Many of the data elements in DRRS-Army fall under the purview of other agencies and offices, to include Joint and DOD proponents, and are used in other databases. Therefore, revisions and modifications affecting the display or use of the data elements in DRRS-Army must be thoroughly coordinated with the proponent agency/office for the data elements and synchronized with users, as appropriate. The office of primary responsibility for each of the data elements in the DRRS-Army database and the primary users are indicated in an online listing (see app I ). The DRRS-Army database at HQDA is the authoritative source for DRRS-Army data, and all UICIOs will advise USACCSA/DAMO-ODR immediately of any suspected discrepancies. USACCSA is responsible for synchronizing the DRRS-Army database with the GSORTS database at National Military Command Center (NMCC) and the DRRS.

b. Maintenance. The USACCSA in coordination with command UICIOs will manage and maintain DRRS-Army database at HQDA. All Army activities, specifically Commands are responsible for ensuring that their data in the DRRS-Army database is current and correct. If a discrepancy exists between data elements in DRRS-Army or GSORTS databases and/or DRRS, USACCSA will provide synchronization between the databases maintained by the Joint Staff and OSD to ensure accuracy of Army data.

14-8. Classification guidelines

Force registration data is considered "UNCLASSIFIED" unless indicated by the SCLAS data field as Confidential (C) or Secret (S), or an extracted data set includes classified data elements.

Chapter 15

Structure of a Unit Identification Code

15-1. General

The UIC is a 6-character alphanumeric code that uniquely identifies a unit/organization. When a TOE/MTOE organization is inactivated, the UIC is retired with the organization, and a record is maintained by U.S. Army Center of Military History (CMH). If the organization is reactivated at some future date, the historic UIC is provided by CMH and reused. The UIC and its associated organization number, branch, and level represent a single permanent identifier for the organization. Reorganization, new designation, and reactivation actions that do not change organization number, branch, or parent unit level do not require a new UIC assignment.

15-2. Unit identifier code structure

a. The UIC consists of three data elements and is structured as follows: service designator ( position 1); parent organization designator (positions 2 through 4); and descriptive designator (positions 5 and 6). (See fig 15-1 , UIC structure.)

b. Position 1 - service designator: "W" for all Army UIC(s). (See App I regarding the online listing of the designators for other services and federal agencies.)

c. Parent unit designators, positions 2-4. These three positions of the UIC uniquely identify the parent unit. The first digit of the parent designator set (the second position of UIC) is used to identify the type of unit (that is, TOE, TDA). (See table 15-1 for an explanation of the significance of the first digit of the parent designator set (second position of the UIC) for U.S. Army organizations ).



Figure 15-1. Unit identification code structure




Table 15-1. Significance of the second position of the unit identification code
Type Army organization Second position of the UIC
TOE units Alphabetic
Active Component units A-L (less I)
APS M
Multiple component units N
ARNG and USAR units Q through Z
TDA units Numeric
Active Component units 0-6 ( less 5)
ARNG and USAR units 7-9
Mobilization TDA(s) (currently under review) 5

d. Positions 5 and 6 - descriptive designators. These two positions further define organizational elements or distinctive features of the parent organization.

(1) The following tables list the descriptive designators applicable to parent organizations (that is, battalions and separate company-size units, split organizations, multi-component organizations, MTOE multi-component AUGTDA elements, and nonpermanent party personnel).

(a) Table 15-2 lists the descriptive designators that are applicable to U.S. Army parent organizations (that is, battalions and separate company-size units).

Table 15-2. Descriptive designators for U.S. Army table of organization and equipment/modification table of organization and equipment organizations
5th-6th PSN of the UIC Description
FF 1 Titular organization
AA Parent organization
A0 2 A company, battery, or troop
B0 2 B company, battery, or troop
C0 2 C company, battery, or troop
D0 2 D company, battery, or troop
E0 2 E company, battery, or troop
F0 2 F company, battery, or troop
G0 3 G company, battery, or troop
H0 2 H company, battery, or troop
J0 2 J company, battery, or troop
K0 2 K company, battery, or troop
L0 3 L company, battery, or troop
M0 4 M company, battery, or troop
N0 Missile support company, maintenance battalion
P0 Howitzer battery of a cavalry squadron, combat support company of armor, mechanized, airborne, air assault, or infantry battalion
RA-RZ Designates subordinate elements of a training base unit. Retain the name if it is a historic regimental maneuver unit.
S0 Service battery or service company
T0 Headquarters company or detachment organic to a parent organization. Not used to designate headquarters, headquarters companies (HHCs) or headquarters, headquarters detachments (HHDs) that are themselves parent organizations
U1-U9, V1-V9, W1-W9, and Z1-Z9 Reserved for use to identify cellular teams
ZZ A MTOE parent organization that is minus (does not have operational control of one or more of its organic sub-organizations). Establish a DUIC using "ZZ" when reporting data on the organization minus (for example, BN-). (The "ZZ" UIC will not have a SRC. The SRC will be included on the "AA" UIC.)
Notes:
1. Each division will have an FF record. Each brigade in a division, separate brigade, regiment, or group (position 1 of TPSN=1) will have an FF record. Each division artillery (DIVARTY) will have an FF record. Each division support command (DISCOM) will have an FF record.
2. Also use for forward support company and maintenance battalion.
3. Also use for heavy maintenance company and maintenance battalion.
4. Also use for aircraft maintenance company and maintenance battalion.

(b) Table 15-3 lists descriptive designators applicable to split organizations and TDA organizations that are parent organizations (that is, battalions and separate company-size units). Nonsignificant designators will be assigned when the number of splits exceeds the number of significant designators allocated.

Table 15-3. Descriptive designators for split organizations and tables of distribution and allowances organizations
5th and 6th PSN of the UIC Split organization and TDA organization
A1-A9 Applies to the split unit if the unit is a parent organization
B1-B9 B element
C1-C9 C element
D1-D9 D element
E1-E9 E element
F1-F9 F element
G1-G9 G element
H1-H9 H element
J1-J9 J element
K1-K9 K element
L1-L9 L element
M1-M9 M element
N1-N9 Missile support company, maintenance battalion
P1-P9 Howitzer battery of a cavalry squadron, combat support company of a mechanized, airborne, air assault, or light infantry battalion
S1-S9 Service battery or service company
T1-T9 Headquarters company or detachment organic to a parent organization. Split organizations, TDA organizations, or TDA augmentations.
01-89 TDA split organization. TDA sub-elements, U.S. Army Special Forces TOE organizations, and ARNG property books and exercises.
90-99* TDA augmentation to TOE organizations. (Initial augmentation to a TOE organization will be assigned the derivative "99." Assign additional augmentations in descending sequence.) "90" applies to a temporary carrier UIC. Restricted to HQDA top load.
ZZ A TDA parent organization representing an Installation which is used for Installation Readiness Reporting versus The Garrison UIC (The "ZZ" UIC will not have a SRC. The SRC will be included on the "AA" UIC.)
*See table 14-5 for a complete description of MTOE Augmentation TDAs

(c) Multicomponent units. Table 15-4 lists descriptive designators applicable to multi-component organizations that are parent organizations (that is, battalions and separate company-size units).

Table 15-4. Descriptive designators for multiple-component units
5th and 6th PSN of the UIC Description
AA Multi-component parent level UIC. The parent is a display-only record in the Structure and Manpower Allocation System (SAMAS). In DRRS-Army, it is set with a "Z" in OESTS to indicate the unit is empty. All personnel and equipment are reflected in the DUIC(s)
X1-XZ Active multi-component Structured DUIC(s) that are top loaded first in SAMAS then in DRRS-Army that end in X1-X are identified as 1st level structured DUIC(s). These type of Structured DUICs will have the Multi-component parent level UIC, ending in AA as the Parent Organizations UIC (PUIC) (Note: When subelements DUIC organizations will deploy separately, XZ-XA DUICs will be created as indicated below.)
XZ-XA Active component additional DUIC(s) may be registered by Commands, but must use the 1st level DUIC ending in X1-X... as the parent organization's UIC (PUIC). Also this level of DUIC must begin with the XZ and continue up to XA, Example: WN12XC is a structured 1 level DUIC then the DUIC would be WN12XZ with the parent being the WN12XC. If the XZ is already used they use the XY, if the XY is already used then use the XX, and so on. If there are no available combinations to use or the structured 1st level DUICs extend to XZ, contact HQDA USACCSA.
G1-GZ National Guard Structured DUIC(s) that are top loaded first in SAMAS then in DRRS-Army that end in G1-G... are identified as 1st level structured DUIC(s). These type of Structured DUICs will have the Multi-component parent level UIC, ending in AA as the Parent Organizations UIC (PUIC) (Note: When sub-elements DUIC organizations will deploy separately, GZ-GA DUICs will be created as indicated below.)
GZ-GA National Guard additional DUIC(s) may be registered by Commands, but must use the 1st level DUIC ending in G1-G... as the parent organization's UIC (PUIC). Also this level of DUIC must begin with the GZ and continue up to GA, Example: WN12GC is a structured 1ST level DUIC then the DUIC would be WN12GZ with the parent being the WN12GC. If the GZ is already used they use the GY, if the GY is already used then use the GX, and so on. If there are no available combinations to use or the structured 1st level DUICs extend to GZ, contact HQDA USACCSA.
R1-RZ Reserve Structured 1st level DUIC(s) that are top loaded first in SAMAS then in DRRS-Army that end in R1-R... are identified as 1st level structured DUIC(s). These type of Structured DUICs will have the multicomponent parent level UIC, ending in AA as the Parent Organizations UIC (PUIC) (Note: When sub-elements DUIC organizations will deploy separately, RZ-RA DUICs will be created as indicated below.)
RZ-RA Reserve additional DUIC(s) may be registered by Commands, but must use the 1st level DUIC ending in R1-R... as the parent organization's UIC (PUIC). Also this level of DUIC must begin with the RZ and continue up to RA, Example: WN12RC is a structured 1ST level DUIC then the DUIC would be WN12RZ with the parent being the WN12RC. If the RZ is already used they use the RY, if the RY is already used then use the RX, and so on. If there are no available combinations to use or the structured 1st level DUICs extend to RZ, contact HQDA USACCSA.

(2) Table 15-5 displays the descriptive designator conventions for MTOE multi-component AUGTDA UICs.

Table 15-5. Modification table of organization and equipment multi-component augmentation table of distribution and allowances unit identification code convention
5th and 6th PSN of the UIC Description
99 Multi-component augmentation UIC. The augmentations display only a record in SAMAS. In DRRS-Army it is set with a "Z" in OESTS to indicate the unit is empty. All personnel and equipment are reflected in the derivatives augmentation UIC(s). Top loaded first in SAMAS then in the DRRS-Army database.
9A-9H Active multi-component
9J-9R ( excluding 9I and 9O, which are assigned by DAMO-FM) USAR
9S-9Z ARNG

(3) Table 15-6 displays the descriptive designator conventions for nonpermanent party personnel.

Table 15-6. Nonpermanent party personnel
5th and 6th PSN of the UIC Description
Alphanumeric
(Any unrestricted character - such as 1A or 2B)
Detailed record of each category of non-permanent party personnel reporting organizations. (Requested by the Human Resources Command Personnel Activity (PPA/PAPCO) through the UICIO in accordance with this table.)

e. Restrictions are as follows:

(1) The letters "I" and "O" will not be used in UIC(s)

(2) The descriptive designators listed in tables 15-2 through 15-6 have been assigned significance and are restricted as indicated. All other possible combinations are considered nonsignificant and will be assigned and used as stock records, property books, and maintenance account records or split organizations when the number of derivative or sub-organization UIC(s) exceed the number of significant designators allocated.

Chapter 16

Unit Identification Code/Derivative Unit Identification Code Registration and unit identification code/Derivative Unit Identification code Data Maintenance

16-1. Registration of parent level and first level derivative unit identification codes

a. Restrictions are as follows: For all parent UICs (Both MTOE and TDA), those ending in AA and 1st level DUICs, as defined in chapters 14 and 15 and , USACCSA will provide an initial partial registration in Force Registration and will enter the following required fields (Note: Many fields may be auto populated based on the authoritative database and/or data entered in other fields), provided by DAMO-FMP/USAFMSA:

(1) Unit identification code (UIC).

(2) Assignment vode (ASGMT).

(3) Abbreviated name (ANAME).

(4) Unit level code (ULC).

(5) Troop program sequence number (TPSN).

(6) Standard requirement code.

(7) Component (COMPO).

(8) Planned location geographical code (PLGEO).

(9) Organization status code (OESTS).

(10) Organization status change calendar date (ODATE).

(11) Classification (SCLAS).

(12) Reporting organization (RPTOR).

(13) ACOM, ASCC, DRU, DARNG/NGB UIC (MJCOM).

(14) Branch (For MTOE Only).

(15) Unit descriptor code (UDC).

(16) Unit type code (UTC).

(17) Force type (FRCTYP).

(18) Planned activation date (PAOD).

(19) Interested commands (INTR2).

(20) Attached command (ATACH).

(21) Combatant command service code (CSERV).

(22) For 1st level DUICs the Parent UIC (PUIC), that is, the AA.

(23) For 1st level DUICs the Type of DUIC (TOD) will be entered with the value of "S" for all but Carrier DUICs which will be "T."

(24) Deployed indicator code.

(25) Operational control (OPCON).

(26) Administrative control (ADCON).

(27) Activity code (ACTIV).

(28) Home geolocation code (HOGEO).

(29) Present location code (PRGEO).

(30) Home city (HOGEO).

(31) Home country code (derived automatically from HOGEO).

(32) Present geolocation code (PRGEO).

(33) Present zip code.

(34) USR frequency (IFREQ).

(35) For USARC Reserve UICs, ONLY, the Army Reserve General Officer (ARGO).

(36) TAPFOR (for FORSCOM units).

(37) Indicates field is required for USACCSA to complete the initial registration.

b. Personnel status code and PERSINS Processing Activity Code (PPA) in accordance with below

(1) If the unit is an AC and the unit is required/authorized personnel.

(2) These fields will be left Blank for Guard and Reserve Units. These fields will be populated by the DRRS-A Force Projection application.

(3) Functional area code (FUAC) will be filled in under the following conditions:

(a) If the unit is an equipment only unit, contractor accounting, personnel accounting, or civilian accounting/only type Unit.

(b) If the unit meets one of the above conditions then the PPA and personnel status code must be left blank.

c. The ACOMs, ASCCs, DRUs, or DARNG/NGB will normally activate all parent level UICs no earlier then 30 days prior to its' planned activation date (PAOD), and no later than it's PAOD. Deviations from this rule are allowed if there is prior coordination with USACCSA, who will further coordinate with DAMO-FMP. Upon coordination, USACCSA will change/modify the PAOD to the requested date to allow the command to activate the unit earlier or later in accordance with the commands request. When a parent UIC or structured DUIC is due for inactivation, USACCSA will PIDD (planned inactivation date) the UICs 30 prior to the inactivation date. A PIDD is required for an AA UIC before it can be inactivated.

d. ARLOCs:. There are instances when an ARLOC code does not exist for a given PLGEO, HOGEO, or PRGEO. In order for it to be used an ARLOC must be requested from USACCSA. The following information must be provided to USACCSA:

(1) City name and state.

(2) Type of code (City, RTC, and so forth).

(3) Name of the Reserve Center (if applicable).

(4) Geographical location coordinates (GEOLOC).

16-2. Registration of structured derivative unit identification codes

Upon completion of the registration of all parent UICs (MTOE, TDA, 1st level derivative UICs) ACOMs, ASCCs, DRUs, or DARNG/NGB will register all structured DUICs (DUICs identified in the authorization documents) in accordance with paragraphs 15-2 and 16-1 and a , 16-1 b , and 16-1 c , above.

16-3. Registration of functional derivative unit identification codes

a. Functional DUICs (See para 14-6c(7)(f) ) will be registered in accordance with paragraphs 15-2 and 16-1 and a , b , and c and with the following additional fields:

(1) Parent UIC (PUIC).

(2) Type of DUIC (TOD).

b. Functional DUICs are of two types, permanent, or temporary. The following rules will apply to each category of functional DUIC:

(1) Permanent functional DUICs will be initially registered with a TOD of "R" for " Permanent unstructured-Requested by Command". USACCSA in conjunction with DAMO-ODR will either approve the request and change the TOD TO "P" for "Permanent unstructured - Approved by HQDA" or disapprove and ask for more justification. If there is no final approval from HQDA then TOD will be changed to "T" for Temporary.

(2) Temporary Functional DUICs will be registered with a TOD of "T" for temporary unstructured. Temporary unstructured DUICs require a review by the command every 28 months and will be subject to removal if not review within that time frame.

16-4. Maintenance of unit identification codes/derivative unit identification codes

a. Following the registration of UICs/DUICs, ACOMs, ASCCs, DRUs, DARNG/NGB and designated DASAs have direct responsibility for the maintenance of UICs/DUICs assigned to their organization. Although these organizations are authorized to delegate this authority to subordinate organizations, the ultimate responsibility for UIC/DUIC maintenance resides with the ACOM, ASCC, DRU, DARNG/NGB or DASA. Maintenance of UICs/DUICs will consist of the following requirements. Queries may be executed in Force Registration that will assist to accomplish the required maintenance:

(1) Activations. Once UICs/DUICs are registered in force registration, UICIOs must ensure activations occur on their effective dates.

(2) Inactivations. Keep the database clean of old/unnecessary DUICs and those programmed for inactivation/discontinuance. If the AA UIC is due for inactivation but has not been PIDDed (Planned Inactivation Date), then make the request to USACCSA.

(3) Use UIC Scrubs to keep the UIC data accurate.

(4) Keep locations codes (PLGEO, HOGEO, PRGEO) current.

(5) USR Workflow and IFREQ (see table 16-1 ).

(6) All parent level UICs and Structured DUICs that have an SRC are required to be updated when unit document is updated. This will normally be accomplished automatically when the authoritative data source changes. ACOMs, ASCCs, DRUs, DARNG/NGB and DASAs are required to request approval from HQDA (DAMO-FM) if they wish to deviate from the authorative document.

(7) Organizations are not required to enter the unit's home address for temporary DUICs, however they are encouraged to do so, whenever possible. They must be entered for AA and 1st level DUICs.

b. The ACOMs, ASCCs, DRUs, DARNG/NGB, and DASAs will establish review processes within their organizations to ensure data is accurate and valid. Special attention should be given to a unit's present location code.

c. The ACOMs, ASCCs, DRUs, DARNG/NGB, and DASAs will ensure that the current deployment status is updated and current. The following fields will be maintained:

(1) Deployed command assignment. This field will remain blank when the unit is not deployed and filled in with the assignment code of command the unit is deployed to, if deployed.

(2) Deployed indicator code. This field will have a code of "N" if the unit is not deployed and if they unit is deployed it will have the appropriate code for the units deployment status. (See table 16-1 .)

(3) Title 32 Mission Location (T32LOC) - This field is required to be filled in when DIC field = "G," with the State 2 letter abbreviation where the unit is performing its Title 32 mission, otherwise it is blank.

Table 16-1. USR requirements and exemption codes
5th-6th PSN of the UIC Description
1 Required to submit a monthly report regular or validation)
2 Required to submit a type II composite report
3 Required to submit a type I composite report
4 Required to report quarterly
5 Required to report annually in October
6 Not currently used -for future use only if directed by HQDA (DAMO-ODR)
7 Required to submit a DUIC/Special report
8 Required to submit a report for a temporary period
9 Approved for consolidated USR Permanent exemption approved by HQDA
A Temporary exemption approved by HQDA
B Permanent exemption approved by ACOM, ASCC, DRU or DARNG (applicable to TDA units only)
C Permanent exemption approved by ACOM, ASCC, DRU, or DARNG (applicable to TDA units only)
D Temporary exemption approved by ACOM, ASCC, DRU, or DARNG (applicable to TDA units only)
N Not measure but not exempt (Default for DUICs)
T Temporarily approved to submit a DUIC/Special report due to exceptional circumstances
X Other
See the DRRS-Army Portal for changes and updates


Table 16-2. Deployment Indicator Codes
5th and 6th PSN of the UIC Split organization and TDA organization
A Alerted ( COMPO 2/3 = not mobilized)
C Unit is at the CONUS location ( COMPO 1/2/3)
D COMPO 2/3 mobilized and arrived at DEMOB station (OESTS = G/V)
E COMPO 6 unit with distributed equipment
G ARNG ( COMPO 2) unit performing Title 32 missions
H COMPO 2/3 mobilized but still at the Home Station (OESTS = G/V)
M COMPO 2/3 mobilized and arrived at MOB station (OESTS = G/V)
N Not deployed (COMPO 1 = not deployed, COMPO 2/3 = not mobilized)
O Unit is at the OCONUS deployed location ( COMPO 1/2/3)
R Redeployed from OCONUS destination (applicable to HQs units only)
T In transition to deployed destination (applicable to HQs units only)
Z COMPO 2/3 mobilized and arrived at Home Station (OESTS = G/V) awaiting demobilization
See the DRRS-Army Portal for changes and updates

Chapter 17

Multiple Component Units

This chapter establishes responsibilities, policies and procedures for registering multiple component units in DRRS-Army. Refer to AR 71-32 and the DRRS-Army portal for other multiple component unit policies and procedures.

17-1. Overview

a. Intent. The intent of the multiple component unit initiative is to integrate, to the maximum extent within statutory and regulatory constraints, resources from more than one component into a cohesive, fully capable Army unit. Multiple-component unit status will not change the priority of the parent unit, but may change the priority of component derivatives so that they align with the parent unit. Any change in a unit's priority continues to be based on force packaging, Department of the Army master priority list (DAMPL) sequence, and the tiered resource policies of the Army's components.

b. Goals and objectives. Desired goals and objectives of the multiple component unit initiative include the following:

(1) Enhance integration of the Army by using resources of more than one component to fill authorizations in units consistent with force packaging and tiered resourcing policies.

(2) Improve the resource and readiness posture of Army units by eliminating cadre level organizations when multiple component unit status can be used to bring an organization's authorized level of organization to a mission capable level.

(3) Optimize the unique capabilities of each component by encouraging the integration of AC and RC resources (that is, personnel and equipment) in units while leveraging component strengths. Units organized as multiple component unit(s) must provide value not only to the Army in general but also to the resourcing components and the individual Soldiers.

(4) Improve Army documentation procedures by reducing the need to maintain a separate MTOE and AUGTDA that must be combined to form a mission-capable unit.

17-2. Special functions

The Office of the Deputy Chief of Staff, G-3/5/7 will

a. Manage unit identification code (UIC) registration and management procedures to conform to Army policy for multiple component units established in AR 71-32 .

b. Modify the Army Status of Resources and Training System (DRRS-Army) accordingly and coordinate with the Joint Staff (J-3 Readiness Division) to ensure changes to the GSORTS.

c. Ensure UIC registration is validated in DRRS-Army for a minimum of 1 year prior to the effective date (EDATE) for multiple component unit(s).

17-3. Modification table of organization and equipment unit identification conventions

The UIC conventions are established as follows:

a. General.

(1) An "N" in the second character of the UIC denotes a multiple component unit.

(2) HQDA will assign each component-specific element of a DUIC based on the initial request included in the Multiple Component Unit Concept Plan (MCUCP). Resourcing components will continue to assign additional derivatives as required. For example, after the initial DUIC(s) are assigned, the NGB and USARC may use the remaining DUIC(s) to split-station units to meet operational requirements. The DUIC will be constructed as follows:

(3) The first four characters of the DUIC will be the same as those of the parent UIC.

(4) The fifth character of the DUIC will denote the component: "X" for Active Component, "G" for ARNG, and "R" for USAR.

(5) The sixth character of the DUIC will identify the first occurrence and, as needed, succeeding occurrences of component-specific elements (for example, WNAAX1, WNAAX2, WNAAX3). Once the numeric characters are exhausted, alpha characters will be used in the sixth position (WNAARA, WNAARB, WNAARC, and so forth). Alpha characters "I" and "O" will not be used. Table 17-1 illustrates the approved DUIC conventions.

Table 17-1. Modification table of organization and equipment unit identification code convention
MTOE UIC convention Convention combinations
AA elements X1...X9 then XA...XZ (excluding XI & XO)
ARNG elements G1...G9 then GA...GZ (excluding GI & GO)
USAR elements R1...R9 then RA...RZ (excluding RI & RO)

b. Parent augmentation table of distribution and allowances. The "parent" AUGTDA UIC will have the same first four characters as the HQDA-assigned multiple component unit MTOE UIC. The fifth and sixth positions will reflect a "99."

c. Augmentation table of distribution and allowances derivative unit identification code naming convention. The UIC convention retains the "9" as the fifth character and uses "A" through "Z" in the 6 th position to denote component-specific elements. Alpha characters "I" and "O" will be not used. Table 17-2 illustrates the options that will be used for the 6 th position.

Table 17-2. Augmentation table of distribution and allowances unit identification code convention
AUGTDA UIC convention Approved 5 th and 6 th character combinations
AA elements 9A, 9B, 9C, 9D, 9E, 9F, 9G, 9H
ARNG elements 9R, 9S, 9T, 9U, 9V, 9W, 9X, 9Y, 9Z
USAR elements 9J, 9K, 9L, 9M, 9N, 9P, 9Q

(1) The DUIC convention allows each re-ourcing component to request several AUGTDA UIC(s) based on component-specific requirements. Using this methodology, ODCS, G-3/5/7 (DAMO-FMP) will assign the 6 th position based on the coordinated AUGTDA UIC request that should be contained in the MCUCP.

(2) Table 17-3 illustrates a hypothetical application of the AUGTDA UIC convention. WNXX99 (AUGTDA) was created to support the MTOE MC UIC WNXXAA. The MC MTOE contains five geographically dispersed elements. This unit will be combined into one AUGTDA with all five derivatives on one document. Based on the AUGTDA convention (see table 17-3) ODCS, G-3/5/7 (DAMO-FMP) will assign component-specific DUIC(s) as follows:

Table 17-3. Augmentation table of distribution and allowances hypothetical illustration
AUGTDA MTOE Description
WNXX99 WNXXAA Parent/carrier
WNXX9A WNXXX1 Active element
WNXX9B WNXXX2 Active element
WNXX9R WNXXG1 ARNG element
WNXX9S WNXXG2 ARNG element
WNXX9J WNXXR1 USAR element

d. Permanent orders procedures. Permanent military orders are required for documented unit actions described in AR 220-5 Special instructions for preparing permanent orders for multiple component units are as follows:

(1) Procedures when the Active Component organization is the flag holder. The ACOM, ASCC, DRU, or DARNG/NGB will publish POs for USAR and Active Component elements. The ACOM, ASCC, DRU, or DARNG/NGB also will publish federal permanent orders for ARNGUS elements in accordance with AR 71-32 . State permanent orders and organization authority will continue to be published by the appropriate state Adjutant General and NGB, respectively, in accordance with NGR 10-1 .

(2) Procedures when the Army National Guard of the United States organization is the flag holder. The NGB will request that the appropriate ACOM, ASCC, DRU, or DARNG/NGB publish POs for Active Component and/or USAR elements as well as the federal permanent orders for ARNGUS elements. The NGB will provide the ARNG organization authority to the appropriate ACOM, ASCC, or DRU. This will enable the ACOM, ASCC, or DRU to publish permanent orders for Active Component and/or USAR elements as well as the federal permanent orders for ARNG elements. The ACOM, ASCC, or DRU will provide a copy of the permanent orders to the designated office at the NGB. State permanent orders and organization authority will continue to be published by the appropriate state Adjutant General and the NGB respectively in accordance with NGR 10-1.

(3) Procedures when the United States Army Reserve organization is the flag holder with Active Component and/or Army National Guard elements. The USARC or the responsible Active Component ACOM, ASCC, or DRU will publish the PO for the Active Component and USAR elements and the federal permanent order for the ARNGUS element. State permanent orders and organization authority will continue to be published by the appropriate state Adjutant General and the NGB, respectively, in accordance with NGR 10-1. If the USAR organization holds the flag of a unit located overseas as in the case of the 7th and 9th Army Reserve Commands, then the OCONUS ASCC will publish the POs for the USAR and AC element.

(4) Publication of POs and Federal POs. When the sponsoring component is an ACOM, ASCC, or DRU with resources provided by the RC, it is imperative that orders be published as soon as practical to allow the RC to requisition personnel, facilities, equipment, and so forth. The goal is to provide POs to the USAR 1 year prior to the multiple component unit's activation date, but not later than 9 months prior to activation. Federal permanent orders for ARNGUS elements should be published using the same timelines.

e. Logistics.

(1) Single property book. There is no requirement to combine equipment from the resourcing components of a multiple component unit on a single property book.

(2) Property accountability. Equipment from re-sourcing components should normally not be mixed within a DUIC. If the re-sourcing component of the DUIC determines that the unit must be split because of personnel requirements, then the component must submit an MTOE change to correct the MTOE to indicate the split. For example, if B Company, known as "G1" is split, the second portion will be known as "G2," not "B1." The MTOE will be adjusted to reflect equipment shown as "G2,"

(a) Each component will maintain organizational clothing and individual equipment (OCIE) records and accountability, and Soldiers will have OCIE at their geographical location to the greatest extent possible. The MOA may state that in the event of mobilization, mobilizing Soldiers will be equipped at a specific central issue facility (CIF).

(b) One or all of the resourcing components may appoint an accountable officer for property. If one accountable officer is appointed for all property, then each component will appoint a responsible officer to sign for their component's property.

(c) All property assets will be reported under its component DUIC through logistics channels to ensure component visibility of equipment assets.

f. Operational policies.

(1) Mobilization and deployment procedures. The RN elements of multiple component units will be mobilized in accordance with AR 500-5 . FORSCOM will provide guidance in those cases where there is no command linkage established to order RC elements to active duty (for example, WNA1R1, 3 BN, 66th AR, 6 personnel assigned). Mobilization of RC members of multiple component units is the same as for any RC unit. Accordingly, FORSCOM and OCONUS ASCCs must ensure that sufficient time to mobilize the RC is available prior to scheduling the deployment of a multiple component unit. FORSCOM will ensure that Active Component and RC elements of the same multiple component units are assigned to installations providing optimal mobilization and peacetime support. Exceptions are those RC elements where the Active Component flag or Active Component element are already forward stationed or have deployed early.

(2) Measures of effectiveness. To ensure multiple component unit initiatives meet Army goals, resourcing components should give special emphasis to monitoring multiple component unit readiness. USR information recommended for monitoring are the number of units documented, number of units reporting P3, S3, and T3; and the number of units using the common Standard Army Management Information System.

g. Legal issues.

(1) Commensurate with their positions and subject to restrictions found in AR 27-10 , AC and USAR officers will exercise Uniform Code of Military Justice authority (that is, non-judicial punishment and courts-martial) over Active Component and USAR Soldiers assigned to their multiple component unit.

(2) Authority and responsibility for military discipline over ARNG Soldiers not in federal status rests with each state. Every ARNG element will have a designated state chain of command for purposes of military justice. Non-ARNGUS multiple component unit commanders will forward recommendations for disciplinary actions pertaining to ARNG Soldiers to the designated ARNG commander from the state of the respective ARNG element. ARNGUS multiple component unit commanders, whose multiple component unit includes ARNG elements from outside their own state, will forward recommendations for disciplinary actions pertaining to such ARNG Soldiers to the designated ARNG commander from the state of that element.

(3) For AC and USAR Soldiers assigned to a multiple component unit with an ARNGUS commander, the AC and USAR will attach these Soldiers on orders for purposes of UCMJ to the nearest appropriate AC or USAR command. The ARNGUS unit commander will forward recommendations for disciplinary actions pertaining to USAR or AC Soldiers to the designated USAR or AC commander.

h. Command and control. Command and control relationships will be prescribed in a MOA between components.

Chapter 18

Force Management Actions

18-1. General

a. The Army manages organizations through organizational integration, and it manages change through the force integration process. Army organizations are modernized, reorganized via MTOE changes, and/or redesignated to enhance force capabilities. Army units are inactivated or discontinued when no longer required.

b. Consolidated policies for the determination, development, and documentation of Army personnel and equipment requirements and authorizations and associated force management activities are contained in AR 71-32 and AR 71-9 . The UICIOs should use these publications and/or consult with force management officials in their organizations regarding the implications of specific force management actions to UICIO requirements.

18-2. Activation and reactivation of unit identification codes

Parent units will be activated and reactivated in accordance with the UIC registration process established in chapter 16 .

18-3. Modernization, reorganization, and redesignation

a. The UICIO will initiate the transactions required to register new UICs resulting from MTOE changes because of modernization or reorganization. UICIOs are responsible for correcting any processing errors and ensuring that transactions are successfully completed in DRRS-Army.

b. The following documents and data elements are required by the UICIO to complete these transactions:

(1) Required documents.

(a) Permanent order.

(b) The MTOE or TDA document.

(c) SRC/ UTC cross-reference list.

(2) Required data.

(a) The following data is contained in the MTOE/TDA: UIC, ANAME, SRC, TPSN, ULC, and PPA.

(b) The following data is contained in the permanent order: OPCON and ADCON.

(c) For redesignation, UICs will be registered in accordance with chapter 16 .

18-4. Inactivation and discontinuation of parent units

a. Modification table of organization and equipment units inactivate. The TDA units discontinue.

b. Process.

(1) The ACOM, ASCC, DRU, or DARNG/NGB will issue a permanent order to effect the inactivation or discontinuation of units as required.

(2) The ACOM, ASCC, DRU, or DARNG/NGB UICIOs will execute an inactivation transaction in DRRS-Army for inactivating MTOE units.

(3) The ACOM, ASCC, DRU, or DARNG/NGB UICIOs will execute a discontinuation transaction in DRRS-Army to accomplish the discontinuation of TDA units.

18-5. Inactivation of derivative unit identification codes outside of redeployment

The DUICs that require inactivation for reasons other than redeployment will be inactivated as follows:

a. The UICIO will inactivate the DUIC upon formal request from the responsible commander.

b. The UICIO will inactivate the DUIC during routine maintenance if it is determined that the DUIC is no longer required.

c. The UICIO will inactivate the DUIC if it has been eliminated during MTOE/TDA realignments.

Chapter 19

Mobilization and Demobilization

19-1. Mobilizing Army National Guard units

a. The process for mobilization is for follows:

(1) The HQDA will issue alert and mobilization orders.

(2) The ARNG UICIO will create DUICs for employing (CONUS), deploying, and stay behind elements in accordance with the policy guidance in chapter 16 .

(3) The automated DRRS-Army Force Projection process will mobilize and federalize the ARNG units on the basis of the mobilization order and will change DRRS-Army Force Registration data elements to reflect that units are FORSCOM units and identify the mobilization station.

(4) The ARNG UICIO will create DUICs in DRRS-Army upon receipt of alert notification.

(5) Upon arrival at the mobilization station, the mobilization station UICIO will enter DTAMS and the MOB STRENGTH in MOBODEE which will generate a transaction to change the PRGEO to the mobilization station location.

b. When moving the unit from the mobilization station to the port of embarkation (POE), the mobilization station UICIO will change the pertinent data fields (ORGLOCN set) to transfer the unit to the theater of operations.

c. Documents required: The mobilization order is required.

d. Data element changes required upon movement to the mobilization station: PRGEO and ORGLOCN sets.

e. Data element changes required (as a minimum) on movement to the POE: OESTS, PRGEO, and RPTOR, as required.

19-2. Mobilizing United States Army Reserve units

a. Process for mobilization

(1) HQDA will issue alert and mobilization orders.

(2) The mobilizing ACOM, ASCC, DRU, or the USARC UICIO will create DUICs for employing (CONUS), deploying, and stay behind elements in accordance with the policy guidance in chapter 16 .

(3) The automated DRRS-Army process will mobilize the USAR units on the basis of the mobilization order and will identify the mobilization station.

(4) Upon arrival at the mobilization station, the UICIO will change the PRGEO.

(5) When moving the unit from the mobilization station to the POE, the UICIO will change the pertinent data fields to transfer the unit to the theater of operations.

b. The mobilization order is required.

c. Data element changes required (as a minimum) when moving the unit to the mobilization station: PRGEO and ORGLOCN sets.

d. Data element changes required when moving the unit to the POE: OESTS, PRGEO, and RPTOR, as required.

19-3. Demobilizing Army National Guard and United States Army Reserve units

a. The process for mobilization:

(1) HQDA will issue demobilization orders or modify mobilization orders, as required.

(2) The mobilizing command (ACOM, ASCC, or DRU) or the theater UICIO will transfer the demobilizing unit/elements to the designated demobilization station by making appropriate changes to the ORGLOCN set.

(3) The demobilization station will accomplish actions required to move the unit/elements to the home station(s).

(4) Upon arrival of the unit/elements at the home station(s), the mobilization station, the DARNG/NGB, USARC or the mobilizing command UICIO will accomplish actions required to release the unit/elements from active duty (REFRAD) or change location of unit and inactivate the DUIC (if required) in accordance with the following guidelines. (If any of these actions are delegated by DARNG/NGB to the JFHQ or State area command, then the DARNG/NGB UICIO will provide oversight to ensure that all required actions are accomplished effectively.)

(a) If the unit was mobilized under its AA-Level UIC and all of its mobilized elements are being released from active duty, then the ARNG, USARC, or the mobilizing ACOM, ASCC, DRU, or DARNG UICIO will execute an ACTUAL REFRAD transaction via MOB/ODEE to release the unit from active duty.

(b) If the unit was mobilized under its AA-Level UIC and some of its mobilized elements will remain on active duty, then the ARNG, USARC, or mobilizing command or DARNG/NGB UICIO must coordinate with HQDA (DAMO-ODM) to modify the original mobilization order to include activation of a DUIC with the same effective date of initial MOB order to which the elements remaining on active duty can be assigned.

(c) If the unit/elements were mobilized under a DUIC and all of the mobilized elements are being released from active duty, then the ARNG, USARC, or mobilizing command UICIO will execute an ACTUAL REFRAD transaction via MOB/ODEE (if applicable) to release the unit/elements from active duty and will inactivate the DUIC.

(d) If the unit/elements were mobilized under a DUIC and some of the elements will remain on active duty, then the ARNG or USARC UICIO must coordinate with HQDA (DAMO-ODM) to modify the original mobilization order so that the existing DUIC is made applicable to those elements remaining on active duty. DAMO-ODM will coordinate with DAMO-ODR as required.

(e) If required, DUICs created for mobilization may be retained in DRRS-Army after REFRAD.

b. Documents required: Demobilization order or modification to mobilization order is required.

c. Data element changes required when moving the unit from the theater of operations to the mobilization station: RPTOR in the ORGLOCN set.

d. Data element changes required when releasing the unit from active duty: PRGEO in the ORGLOCN set and OESTS in the ABIDE set

e. The ACOM, ASCC, DRU, or DARNG/NGB responsibilities: CONUS and Theater commands and DARNG/NGB will coordinate as required regarding USR submission procedures and location changes and in order to facilitate effective force tracking and command and control

Chapter 20

Deployment and Redeployment

20-1. General

a. The policies and procedures in this chapter have been aligned with the policies and procedures in AR 220-1 , (which is complemented by this publication) regarding data reporting requirements for deploying or deployed units.

b. The policies and procedures in this chapter also have been crafted to facilitate and/or support, to the extent possible, the continued effective operation of existing systems used by various Army agencies and commands to manage and/or monitor resources in deploying/deployed and stay-behind Army units and elements.

c. The policies and procedures in this chapter take precedence in the event of any conflict with policy guidance established by other Army commands and agencies regarding the creation of UICs and those DUICs that must be registered in the DRRS-Army database. DUICs not registered in the DRRS-Army database and other alpha-numeric constructs associated to units that are similar, but that were created under provisions of policy established by other Army commands or agencies to support the management or operating requirements of their proponent systems, are outside the purview of this publication.

d. The policies and procedures in this chapter and in other parts of this publication that prescribe how rear detachment DUICs will be constructed and registered in the DRRS-Army database should not be misconstrued as directing or mandating that each deploying/deployed parent unit must establish or organize a rear detachment. (See the total deployment scenario discussed below.)

20-2. Registration requirements in support of status reporting by parent units identification

There are three basic unit deployment scenarios (total deployment scenario, full deployment scenario, and partial deployment scenario), a special team/task force deployment scenario that may involve one or more of the three basic scenario types, and exceptional deployment scenarios that may require additional guidance from HQDA. The descriptions of these scenarios and the applicable UIC/DUIC guidelines for them are as follows:

a. Total deployment scenario.

(1) A total deployment occurs when a parent unit (AA-Level UIC) deploys with all of its assets (personnel and equipment), without exception.

(a) For DRRS-Army purposes, the total deployment of a parent unit is indicated by changing (as a minimum) the present location code (PRGEO) to the deployed location (or the deployed vicinity depending on security classification restrictions), the unit's status code (STATC) to D1 - signifying that the unit is deployed - and the activity code (ACTIV) to reflect the current activity of the unit. Because there are no stay behind assets (personnel or equipment) in a totally deploying/deployed parent unit, the registration of a rear detachment DUIC in the DRRS-Army database is unnecessary.

(b) When directed by HQDA or approved by the ACOM, ASCC, DRU, or DARNG/NGB to facilitate administrative or logistics requirements (for example, property accountability, supply transactions), a totally deploying/deployed parent unit may register an "ADMIN DUIC" in the DRRS-Army database for use at the home station and/or in the theater to which the parent unit is deploying/deployed. The personnel and equipment in the totally deploying/deployed parent unit will remain associated with the AA-Level UIC. The "ADMIN DUIC" is unstructured and is assigned for administrative use only.

(2) Parent units also are considered totally deployed when any non-deploying or stay-behind assets (personnel and equipment) are formally reassigned/transferred to another UIC/DUIC organization(s) that is not under the purview of the commander of the deploying/deployed parent unit. In this situation, the responsibility to account for the stay-behind assets, for DRRS-Army and USR purposes, passes from the commander of the deploying/deployed parent unit to the commander of gaining unit on the effective date of the formal transfers/reassignments. For example, if a deploying unit has personnel that are in the hospital, it would be considered totally deployed only if the hospitalized personnel were formally reassigned to the hospital or to another UIC/DUIC organization that was not under the purview of the unit commander. Otherwise, the hospitalized personnel would be included in the unit's rear detachment and, for USR and DRRS-Army purposes, the unit would not be considered totally deployed.

b. Full deployment scenario.

(1) Full deployment occurs when the preponderance (more than half) of the assigned personnel in a parent unit (AA-Level UIC) are deployed, to include the unit's command and control system, and only a relatively small rear detachment, consisting of non-deploying personnel and/ or stay-behind equipment items, remains at the home station. A unit's command and control system includes the commander on orders to command the parent unit and the personnel and systems necessary to plan, direct, and control forces and operations to accomplish the unit's mission (also see definition of "full deployment" in the glossary).

(a) For DRRS-Army purposes, the full deployment of a parent unit is indicated by changing the PRGEO, the STATC, and the ACTIV codes (same as described above for a total deployment) to reflect the movement of the parent unit to the deployed location, and the establishment of a "rear detachment" DUIC to account for the stay-behind assets.

(b) When directed by HQDA or approved by the ACOM, ASCC, DRU, or DARNG/NGB to simplify property accountability issues and/or facilitate supply transactions, a fully deploying parent unit may register an "ADMIN DUIC" in the DRRS-Army database for use at the home station and/or in the theater to which the parent unit is deploying/deployed. The personnel and equipment in the fully deploying/deployed parent unit will remain associated with the AA-Level UIC. The "ADMIN DUIC" is unstructured and is assigned for administrative use only.

(2) When necessary, commanders of fully deploying parent units will coordinate via appropriate command and logistics channels for the realignment of DODAACs and to prevent the cancellation of valid requisitions or maintenance actions. Shipments, to include those already in the distribution pipeline, should be redirected to the rear detachment DUIC, when appropriate.

(3) Rear detachment DUICs will be registered in DRRS-Army in accordance with procedures established in chapter 16 of this publication. For USR purposes, the status of assets in the rear detachments of fully deploying/deployed parent units will be determined and reported in accordance with the applicable guidelines in references materials provide at the DRRS-Army portal.

c. Partial deployment scenario.

(1) A partial deployment of a parent unit is any deployment of its elements or assets (personnel or equipment) that does not meet the criteria for either a total deployment or a full deployment as described above or for an exceptional deployment scenario described below.

(2) There are two types of partial deployments, depending of the deployment status of the unit's command and control system.

(a) Partial deployment with the unit's command and control system. For DRRS-Army purposes, a partial deployment where elements and/or assets of the parent unit deploy with the unit's command and control system is considered and treated the same as a full deployment. (See para b above.) Key provisions include:

(1) Changing the PRGEO, the STATC, and the ACTIV codes for the AA-Level UIC (same as described above for a total deployment).

(2) Accounting for non-deploying personnel and stay-behind equipment via a rear detachment DUIC.

(3) Registering an "ADMIN DUIC" in the DRRS-Army database for use at the home station and/or in the theater to which the parent unit is deploying/deployed when directed by HQDA or approved by the ACOM, ASCC, DRU, or DARNG/NGB to simplify property accountability issues and/or facilitate supply transactions. The personnel and equipment in the partially deploying/deployed parent unit will remain associated with the AA-Level UIC. The "ADMIN DUIC" is unstructured and is assigned for administrative use only.

(b) Partial deployment without the unit's command and control system. For DRRS-Army purposes, a partial deployment where elements and/or assets of the parent unit deploy without the unit's command and control system (which remains at the home station location) may require that the parent unit commander register one or more DUICs in the DRRS-Army database to account for the deploying elements and assets.

(1) The separation of these elements and assets from the parent unit and their movement to the deployed location is indicated by changing the PRGEO, STATC, and ACTIV codes for each respective DUIC to reflect the deployed location. The PRGEO, STATC and ACTIV codes for the parent unit (AA-Level UIC) will continue to reflect the home station location and unit activity.

(2) The DUIC registration in the DRRS-Army database will be accomplished in accordance with procedures established in chapter 16 .

d. Team/task force scenario.

(1) There are special missions and situations for which a deployable team or task force will need to be organized or constructed using the assets from different parent units. It should be noted that the deployment scenarios for these ad-hoc teams and task forces can involve parent units that, at their level, are engaged in all of the various types of the deployment scenarios described above (total deployment, full deployment, and/or partial deployment). In these special deployment situations, the type of deployment and the applicability of the UIC/DUIC business rules established in this chapter will depend upon (for each supporting parent unit) the non-deploying elements and assets, if any, and the deployment status of the parent unit's command and control system.

(a) For example, if a brigade with three battalions is directed to form a battalion task force from its organic units, then units/elements of this task force could come from the BDE HHC and from any of the three battalions. A DUIC for each element sourced from a parent unit (the HHC and/or a battalion) would be registered in the DRRS-Army database (if the parent unit's command and control system was not deploying) in accordance with the business rules for a partial deployment, and a DUIC for the battalion task force also would be registered in the DRRS-Army database.

(b) However, if a parent unit, to include its command and control system, is included in the team or task force, then the business rules for a total deployment (if no unit assets remained behind) or for a full deployment (if a rear detachment was established) would apply.

(2) In the above example, the DUIC that has operational control over all of the task-organized elements is the battalion task force. The UIC that has administrative control of this battalion task force is the brigade under which the task force was organized. Therefore, the DUIC registered in the DRRS-Army database to represent all of the units and elements comprising the battalion task force would be a derivative of the brigade's UIC. This same process also would apply to ad-hoc organizations constructed at higher levels and lower levels. For example, a brigade combat team organized under a division (higher-level example) would register a derivative of the division's UIC in the DRRS-Army database, and a separate company-team organized under a battalion (lower-level example) would register a derivative of the battalion's UIC of the DRRS-Army database.

e. Exceptional deployment scenario.

(1) An exceptional deployment scenario is one that clearly does not fit within the scenarios described previously because of extraordinary circumstances, such as when a parent unit is mobilized and/or deployed/employed in a piecemeal manner to the extent that, over time, its command and control system loses its identity or when the relevance of the disposition of its command and control system to the determination of the parent unit's deployment status is questionable.

(2) The responsible ACOM, ASCC, DRU, or DARNG/NGB will notify HQDA (DAMO-ODR) and provide details when they identify parent units that have been deployed/employed via an exceptional deployment scenario.

(3) Subsequently, DAMO-ODR will provide guidance regarding DRRS-Army actions required, if any.

20-3. Registration requirements in support of status reporting by units with derivative unit identification codes and subunit unit identification codes

a. General. For DRRS-Army purposes, the following general guidelines apply.

(1) Parent unit identification code deployment. The total or full deployment of a DRRS-Army registered parent UIC (AA-Level) requires that the UICIO change the PRGEO, STATC, and ACTIV codes for the UIC to reflect the deployed location and unit activity during the period of deployment.

(2) Sub-unit unit identification code deployment. The deployment of a DRRS-Army registered sub-unit UIC (A0-Level, B0-Level, C0-Level, and so forth) requires that the UICIO change the PRGEO, STATC, and ACTIV codes for the sub-unit UIC to reflect the deployed location and unit activity during the period of deployment.

(3) Derivative unit identification code deployment. The deployment of a DUIC (applicable to a partial deployments without the unit's command and control system) requires that the UICIO register the DUIC in the DRRS-Army database and change the PRGEO, STATC, and ACTIV codes for the DUIC to reflect the deployed location and activity during the period of deployment.

(4) Rear detachment derivative unit identification code registration. If a rear detachment is established (applicable to a full deployment and a partial deployment with the unit's command and control system), a rear detachment DUIC will be registered in the DRRS-Army database and all non-deploying personnel and stay-behind equipment will be assigned to the rear detachment DUIC.

(5) ADMIN derivative unit identification code registration. If directed by HQDA or approved by the ACOM, ASCC, DRU, or DARNG/NGB to facilitate administration and/or logistics (for example, property accountability, supply transactions) a totally deploying parent unit, a fully deploying parent unit, or a partially deploying parent unit (both types) may register an "ADMIN DUIC" in the DRRS-Army database for use at the home station and/or in the theater to which the parent unit or its elements are deploying/deployed. ADMIN DUICs are unstructured. Unit personnel and equipment will remain associated with the parent unit (AA-Level) UIC (total and full deployments and partial deployments with the parent unit's command and control system) or with the DUIC registered for the deploying/deployed elements (partial deployments without the parent unit's command and control system).

b. Total deployment scenarios. For DRRS-Army purposes, the following business rules are applicable to all total deployment scenarios.

(1) The PRGEO, STATC, and ACTIV codes for the AA-Level UIC will be changed to reflect the deployed location and unit activity.

(2) The RPTOR, sub-RPTOR, and OPCON sets will be changed as required.

(3) The MAJCOM and ADCON sets will continue to reflect the responsible ACOM, ASCC, DRU, or NGB.

(4) An unstructured ADMIN DUIC may be registered in the DRRS-Army database when directed by HQDA or approved by the ACOM, ASCC, DRU or DARNG/NGB.

c. Full deployment scenarios. For DRRS-Army purposes, the following business rules are applicable to all full deployment scenarios:

(1) The PRGEO, STATC, and ACTIV codes for the AA-Level UIC will be changed to reflect the deployed location and unit activity.

(2) The RPTOR, sub-RPTOR and OPCON sets will be changed, as required.

(3) The ACOM, ASCC, DRU, or DARNG/NGB and ADCON sets will continue to reflect the MAJCOM.

(4) An unstructured ADMIN DUIC may be registered in the DRRS-Army database when directed by HQDA or approved by the ACOM, ASCC, DRU or DARNG/NGB.

(5) A rear detachment DUIC will be created to account for and track nondeploying stay-behind assets (personnel and equipment).

d. Partial deployment. There are two basic types of partial deployments.

(1) Partial deployment when the unit's command and control system also deploys.

(a) This type of partial deployment occurs when the command and control system for the parent unit and a portion (less than half) of the parent unit deploys. The deploying commander must be the commander on orders to command the parent unit.

(b) The UIC/DUIC business rules that are applicable to full deployments also are applicable to partial deployments when the unit's command and control system is deployed (see para c , above).

(2) Partial deployment when the unit's command and control system does not deploy.

(a) This type of partial deployment occurs when a portion of the parent unit deploys without its command and control system. The size of the deploying portion of the parent unit is not material; however, the commander on orders to command the unit must remain with the non-deploying portion of the parent unit.

(b) The following business rules are applicable to partial deployments when the parent unit's command and control system does not deploy.

(1) The non-deploying portion of the parent unit will continue to be represented by the AA-Level UIC.

(2) PRGEO, STATC, and ACTIV codes for the AA-level UIC will continue to reflect the home station location and unit activity.

(3) The deploying portion of the parent unit will be assigned and represented by a DUIC. If A0/B0-level (sub-unit) UICs are deploying in whole or in part, then the A0/B0-level (sub-unit) UICs may serve as the DUIC for the deploying portions.

(4) If A0/B0-level (sub-unit) UICs were assigned to the deploying units or elements, then non-deploying and stay behind assets in these units may be accounted for and tracked via AD/BD-Level DUICs. See chapter 16 .

(5) The PRGEO, STATC, and ACTIV codes for the deploying DUICs ( or sub-unit UICs) will be changed to reflect the deployed location and activity.

(6) An unstructured ADMIN DUIC may be registered in the DRRS-Army database when directed by HQDA or approved by the ACOM, ASCC, DRU or DARNG/NGB.

(7) The RPTOR and OPCON sets will be changed as required.

(8) The MAJCOM and ADCON sets for deploying units/elements will continue to reflect the responsible for ACOM, ASCC, DRU, or NGB.

e. Army command, Army service component command, direct reporting unit, or DARNG/NGB responsibilities. Gaining and losing commands will coordinate as required regarding USR submission procedures and unit location changes and to facilitate effective force tracking and command and control. Additionally, if partial deployments transition to full or total deployments, then gaining and losing commands will coordinate the realignment of UICs and DUICs to comply with the UIC/DUIC business rules that are applicable to a full or total deployment.

20-4. The deployment indicator code

a. Deployed DUIC format rules, parent level: Use 0-9 in the sixth position and A-Z (minus "I, O"), when needed. Note that DUIC conventions for multiple-component units are prescribed in chapter 17 .

b. Deployed DUIC format rules, lettered companies. Use the first five characters of the UIC of lettered companies (for example, company A: WAAAA0; company B: WAAAB0). Enter 1-9 in the sixth position. If numbers 1-9 are not available, use "B-Z", except for "I, O". Unless it is prescribed by the ACOM, ASCC, DRU, or DARNG/NGB, do not use a "D" in the sixth position to avoid confusion with the rear element (stay behind DUIC).

c. Rear element DUIC format rules: Parent level organizations must use a DUIC with the first four characters identical to the first four characters of the parent (AA-level) UIC. The ACOM.ASCC/DRU or DARNG may establish their own guidelines for the fifth and sixth positions of the DUIC as long as these guidelines do not conflict with the policy and instructions established in this paragraph and in tables 15-1 through 15-6. In the absence of ACOM, ASCC, DRU, or DARNG/NGB guidelines and when local DUIC usage factors permit, UICIOs may (optional) use the following construction convention for the fifth and sixth positions of the DUIC. (1) For parent (AA-level UIC) units, use an "H" in the fifth position and a "D" in the sixth position. Thus "HD" would represent the home detachment. For the rear detachments of lettered companies with sub-unit UICs ("A0", "B0", "C0", and so forth), use a "D" as the sixth character.

d. Multiple-component UIC format: The first four characters of the DUIC will be the same as those of the parent UIC. The fifth character of the DUIC will denote the component: X for Active Component, G for U.S. Army National Guard, and R for U.S. Army Reserve. (See chapter 15 for instructions regarding the sixth character.)

e. BIDE/ABIDE data elements:

(1) If the DUIC has personnel only associated with it, then make the status code (STATC) "D1", and enter a "P" in the LIC if the derivative unit has a property book, otherwise LIC should be "N."

(2) If the DUIC has equipment only (no personnel), then the LIC will be blank; FUAC will have an "L," UTC will have a "JZZZ2", and STATC will be blank.

f. ORGLOCN data elements: Enter the appropriate current status and activity (ACTIV) code.

g. Operational control: Enter the operational command and control (OPCON(s)) UIC of the unit that is assuming the operational control. Enter the deployed location as the unit's present location (PRGEO).

h. Changes during deployment: During deployment, responsible officials will accomplish changes to the data above, as appropriate.

20-5. Redeployment

a. DRRS-Army data that was entered or revised to reflect deployment will be changed to reflect the redeployment of the parent units and/or derivative elements, as appropriate.

b. Responsible UICIOs will coordinate with the appropriate logistics/DODAAC agency regarding the deletion and/or realignment of DODAACs, as required.

c. DUICs specifically created for partial deployment scenarios, when elements of a parent unit (AA-Level UIC) deploy without the parent unit's command and control system, may be retained in DRRS-Army pending reassignment of the personnel and equipment associated with that DUIC. However, USAR and ARNG DUICs will be released from active duty (REFRAD) upon the effective date of the orders, and all data that was changed to reflect deployment will be changed back to reflect the home station locations and activity.

Appendix A
References

The Official Army Publications Web Sites.

Publication Section I
Required Publications

AR 220-1. Army Unit Status Reporting and Force Registration-Consolidated Policies (Cited throughout the publication.)

Publication Section II
Related Publications

A related reference is a source of additional information. The user does not have to read it to understand this publication. Unless otherwise indicated, field manuals and training circulars may be obtained at http://www.adtdl.army.mil/atdls.htm .

AR 10-47. U.S. Army Command and Control Support Agency

AR 10-87. Army Commands, Army Service Component Commands, and Direct Reporting Units

AR 11-2. Manager's Internal Control Program

AR 11-6. Army Foreign Language Program

AR 25-2. Information Assurance

AR 25-52. Authorized Abbreviations, Brevity Codes, and Acronyms

AR 40-61. Medical Logistics Policies

AR 40-68. Clinical Quality Management

AR 40-501. Standards of Medical Fitness

AR 70-1. Army Acquisition Policy

AR 71-9. Warfighting Capabilities Determination

AR 71-32. Force Development and Documentation-Consolidated Policies

AR 135-91. Service Obligations, Methods of Fulfillment, Participation Requirements, and Enforcement Procedures

AR 140-10. Assignments, Attachments, Details, and Transfers

AR 140-30. Active Duty in Support of the United States Army Reserve (USAR) and Active Guard Reserve (AGR) Management Program

AR 140-145. Individual Mobilization Augmentation (IMA) Program

AR 220-5. Designation, Classification, and Change in Status of Units

AR 220-90. Army Bands

AR 350-1. Army Training and Leader Development

AR 380-5. Department of the Army Information Security Program

AR 525-29. Army Force Generation

AR 570-4. Manpower Management

AR 600-8-6. Personnel Accounting and Strength Reporting

AR 600-8-101. Personnel Processing (In-, Out-, Soldier Readiness, Mobilization, and Deployment Processing

AR 600-8-105. Military Orders

AR 600-20. Army Command Policy

AR 600-43. Conscientious Objection

AR 600-60. Physical Performance Evaluation System

AR 600-100. Army Leadership

AR 600-110. Identification, Surveillance, and Administration of Personnel Infected with Human Immunodeficiency Virus (HIV)

AR 601-142. Army Medical Department Professional Filler System

AR 601-210. Active and Reserve Components Enlistment Program

AR 614-30. Overseas Service

AR 614-100. Officer Assignment Policies, Details, and Transfers

AR 614-200. Enlisted Assignments and Utilization Management

AR 635-200. Active Duty Enlisted Administrative Separations

AR 700-138. Army Logistics Readiness and Sustainability

AR 708-1. Logistics Management Data and Cataloging Procedures for Army Supplies and Equipment

AR 710-1. Centralized Inventory Management of the Army Supply System

AR 710-2. Supply Policy Below the National Level

AR 710-3. Inventory Management Asset and Transaction Reporting System

AR 735-5. Policies and Procedures for Property Accountability

AR 750-1. Army Material Maintenance Policy

CJCSI 3401.02B. Force Readiness Reporting (Available at http://www.dtic.mil/cjcs_directives .)

CJCSM 3150.02B. Global Status of Resources and Training System (Available at http://www.dtic.mil/cjcs_directives.)

CJCSM 3500.04E. Universal Joint Task Manual (Available at http://www.dtic.mil/cjcs_directives/.)

DA Pam 350-38. Standards in Training Commission

DA Pam 708-3. Cataloging of Supplies and Equipment, Army Adopted Items of Materiel and List of Reportable Items (SB 700-20)

DA Pam 600-3. Commissioned Officer Development and Career Management

DA Pam 611-21. Military Occupational Classification and Structure

DA Pam 710-2-1. Using Unit Supply System (Manual Procedures)

DODD 6025.19. Individual Medical Readiness (Available at http://www.dtic.mil/whs/directives/ .)

DODD 7730.65. Department of Defense Readiness Reporting System (DRRS) (Available at http://www.dtic.mil/whs/directives/.)

DODD 8500.01E. Information Assurance (IA) (Available at http://www.dtic.mil/whs/directives/.)

DODI 4165.14. Real Property Inventory and Forecasting (Available at http://www.dtic.mil/whs/directives/.)

DODI 5400.4. Provision of Information to Congress (Available at http://www.dtic.mil/whs/directives/ .)

EO 12958. Classified National Security Information

FM 1. The Army

FM 1-01. Generating Force support for Operations

FM 1-02. Operational Terms and Graphics

FM 3-0. Operations .

FM 7-0. Training Units and Developing Leaders for Full Spectrum Operations

FM 7-15. The Army Universal Task List

JP 1-02. Department of Defense Dictionary of Military and Associated Terms (Available at http://www.dtic.mil/doctrine/new_pubs/jp1_02.pdf.)

SB 8-75-S7. Army Medical Department Supply Information (Available at http://www.usamma.army.mil .)

SB 700-20 (EM 0007). FEDLOG S & I, Commander USAMC Logistics Support Activity (AMTIS-MLA), Bodge. 5307, Redstone Arsenal, AL 35898-7466.

TC 1-210-1. United States Army Special Operations Aviation Aircrew Training

TC 8-800. Medical Education and Demonstration of Individual Competence (MEDIC)

10 USC. Commanders of combatant commands: assignment; powers and duties (Available at www.gpoaccess.gov/uscode .)

10 USC 117. Readiness reporting requirements (Available at www.gpoaccess.gov/uscode.)

10 USC 164. (Available at www.gpoaccess.gov/uscode .)

10 USC 165. Combatant commands: administration and support (Available at www.gpoaccess.gov/uscode.)

10 USC 3013b. Secretary of the Army (Available at www.gpoaccess.gov/uscode .)

10 USC 12301. Reserve components generally (Available at www.gpoaccess.gov/uscode.)

32 USC 502(f). Required drills and field exercises (Available at www.gpoaccess.gov/uscode.)

Publication Section III
Prescribed Forms

This section contains no entries.

Publication Section IV
Referenced Forms

Except where otherwise indicated below, forms are available as follows: DA Forms are available on the U.S. Army Publishing Directorate Web site (http://www.apd.army.mil); DD Forms are available at http://www.dtic.mil/whs/directives/infomgt/forms/index.htm .

DA Form 11-2. Internal Control Evaluation Certification

DA Form 1059. Service School Academic Evaluation Report

DA Form 1352. Army Aircraft Inventory, Status and Flying Time

DA Form 2028. Recommended Changes to Publications and Blank Forms

DA Form 2406. Materiel Condition Status Report (MCSR)

DA Form 3266-1. Army Missile Materiel Readiness Report

DD Form 314. Preventive Maintenance Schedule and Record

Appendix B
Reporting Full Spectrum Operations Mission Essential Task List

B-1. Background

a. FM 3-0 establishes Full Spectrum Operations (FSO) as the Army's operational concept, and Army forces are designed to conduct FSO as their core function. FM 7-0 and the Army Training Network (ATN) Web site establish and explain, respectively, Army doctrine for the development and assessment of the FSO METL.

b. This appendix explains the procedures that Army units will use to report FSO METL assessments in their CUSRs. The concept and key terminology are explained in paragraph B-2 . Basic procedures are explained in paragraph B-3 , and detailed instructions are provided in the NetUSR User's Guide and at the user's help screens embedded in the NetUSR software application.

B-2. Concept

Army units have a single FSO METL that supports both unit training and unit status reporting. HQDA standardizes the FSO METLs of certain units (normally brigade level and above) to ensure that like units have like capabilities. Standardized FSO METL is developed and approved by the DCS, G-3/5/7. Units that do not have a standardized FSO METL and that are not subordinate to a unit that has a standardized FSO METL develop their FSO METLs based on the mission statements contained in their tables or organization and equipment (TOEs) or table of distribution and allowances, their assigned missions, the guidance received from their higher headquarters, and the FSO METLs they normally support. Every FSO METL that is standardized by HQDA is composed of FSO mission essential tasks (METs) and task groups. Task groups are a set of collective tasks necessary to accomplish a specific part of a FSO MET.

B-3. Basic procedures

a. All unit commanders must dialog with their higher commanders regarding specific resourcing requirements, training priorities and where risks exist or might be taken. While this dialog may result in units training on some task groups and collective tasks more intensively than others, all unit commanders must continuously assess and report the training and capability status of their units for each of the METs on their FSO METL.

b. The requirement for the continuous monthly assessment of the FSO METL is necessary to meet reporting requirements directed by OSD and the Joint Staff and is applicable while reporting units are at their home stations and also while they are deployed. Each MET on the FSO METL will be identified by the applicable UJTL, or Army Universal Task List task reference number. Unit training proficiency assessments "Trained" (T), "Needs Practice" (P) and "Untrained" (U) will be accomplished in accordance with Army training doctrine, and unit capability assessments-"Yes" (Y), "Qualified Yes" (Q) and "No" (N) will be accomplished in accordance with the procedures explained in paragraph 9-2 .

c. The FSO METs and supporting task groups do not change, regardless of the unit's mission. The unit's assigned mission, anticipated operational environment, and time available determine the task groups and collective tasks the unit commander selects to train. Appendix C explains the procedures for reporting unit readiness for any assigned mission(s) and for reporting unit status for any additional assigned mission training requirements (also see para 8-7e ).

d. The supporting NetUSR software will auto-calculate the T-level and enable the Y/Q/N capability assessments of each of the FSO METs that reflect the unit's core functions and designed capabilities. The NetUSR User's Guide and user's help screens explain the detailed reporting procedures. Figure B-1 illustrates the concept for reporting on FSO METL and on the Assigned Mission Training Requirements explained in paragraph 8-7 e and appendix C.



Figure B-1. Concept for reporting on FSO METL and additional mission training requirements


Appendix C
Determining and Reporting the Assigned Mission Level (A-Level) and Additional Mission Training Requirements

C-1. Background

a. The OSD and Joint Staff policies require Army units to report on their readiness to execute their core functions and, when applicable, the missions formally assigned to them. Army units comply with these reporting requirements by determining and reporting on their core functions or designed capabilities and FSO METs in accordance with the provisions in chapter 9 and appendix B , and by determining and reporting an "Assigned Mission level" (A-Level) in accordance with the provisions in chapter 9 and this appendix, respectively . Assigned missions are those operational requirements that have been directed by Army tasking authorities to specific units and that have been formally ordered for execution or officially assigned for planning/preparation.

b. On occasion external authorities (that is, Congress, OSD, Joint Staff, combatant commanders, and so forth) and/or Army commands at higher levels may, in conjunction with the assignment of operational requirements, prescribe specific training requirements for deploying Army units and also mandate that unit commanders report the status of training on these requirements in the USR. Army units comply with these reporting requirements by determining and reporting on these assigned mission training requirements in accordance with the provisions in paragraph 8-7 e and this appendix.

C-2. Concept

a. The A-Level is an overall readiness assessment that reflects the unit's ability to accomplish the assigned mission and indicates the status of training requirements associated with the assigned mission. The A-level contains measured resource areas that indicate the availability status of resources (personnel and equipment) measured against the resource requirements for the assigned mission that have been established or conveyed by the Army Tasking Authority. If the unit is preparing for or executing an assigned mission encompassing all of its core functions and designed capabilities, then the A-Level and C-Level will coincide.

b. Under normal circumstances, units at the brigade level and below will be required to report readiness and capability assessments in the CUSR for no more than one assigned mission at any one time. When exceptional circumstances require that brigades, battalions, or separate companies/detachments report on more than one assigned mission, they will identify the primary assigned mission the most significant or demanding operational requirement-via the commanders' dialog, unless specific instructions are provided by HQDA or the responsible ADCON authority. Commanders will then determine and report overall readiness and capability assessments for this primary assigned mission using the measurements and metrics established in this appendix. Note that the A-level is applicable to the primary assigned mission only.

c. When required, unit commanders report on the status of any additional training requirements associated with their assigned mission(s). Detailed instructions and data entry procedures for reporting on these separate "Assigned Mission/Training Requirements" will be provided at the DRRS-Army portal and/or explained in the NetUSR User's Guide and user help screens (also see para 8-7 e ).

d. Figure B-1 depicts the concept for reporting on FSO METL and Assigned Mission Training Requirements.

C-3. Basic procedures

a. General. Reporting units that have assigned missions will report an overall assigned mission level (A-Level) 1, 2, 3, or 4). This overall A-level will consider and include the readiness status of subordinate units/elements-those that submit separate reports and those that do not that have assigned missions supporting the assigned mission of the reporting unit while these subordinate units/elements remain under the command authority of the reporting unit. Reporting units will not consider detached elements in their A-level assessments/determinations. Additionally, assigned mission status reporting is not required for unit deployments to accomplish training only or to participate in training exercises. While assigned missions normally require units to deploy away from their home stations, the assigned mission status reporting requirements established in this appendix also apply to assigned missions that can be executed by units from their home station locations (for example, civil support operations). Commanders will provide detailed comments in the remarks field for each assigned mission assessment to explain any capability gaps associated with the assigned mission. When units are programmed to receive any resources or training required for their assigned mission after arrival in theater (for example, in- theater manning augmentations, TPE, APS, or in-theater training), commanders also must project when the units are expected to attain sufficient assets or training to report A- level 1. If the unit's current manning status does not meet the manning standards established by the Army Tasking Authority (ATA) for its deployment and in-theater manning augmentations are programmed, the commander will project what the LAD plus 30 days personnel fill percentage will be and what the assigned mission manning level will be after the unit receives the programmed manning augmentations.

b. Assigned mission status reporting. Army units will report assigned mission status data in the CUSR as follows:

(1) Unless supplementary guidance received from HQDA (DAMO-ODR) or the ATA require earlier reporting, assigned mission status data reporting by Army measured units will begin in accordance with the following criteria, depending on whichever event or date is earliest or applicable.

(a) When training for the assigned mission becomes the focus of unit training.

(b) Within 24 hours after the unit receives an order (warning order or execution order) to execute a major OPLAN, named operation or any of the following missions: homeland security, peacekeeping, or peace enforcement operations, humanitarian assistance, consequence management, counter-drug operations, civil disturbance operations, and natural disaster relief operations (includes wildfire fighting missions).

(c) Not later than 270/730 days AC/RC prior to the unit's scheduled deployment/employment (that is, LAD minus 270/730 days AC/RC) or upon receipt of formal orders/notification of sourcing, whichever is applicable, and continually until the unit redeploys or is released from orders for the assigned mission.

(d) In accordance with command guidance.

(2) If the A-Level changes, unit commanders must submit change reports in accordance with table 4-1 within 24 hours of the event causing the change.

(3) Assigned mission status reporting ends for all measured when the measured units have been formally released from orders for their assigned missions (for example, upon relief in place), when the units have redeployed to their home stations (that is, at the "return date"), or when subordinate units/elements (organic, attached, assigned or OPCON) with the assigned missions are no longer under their command authority, whichever event comes first or is applicable.

c. Reportable units/elements. Assigned mission level data will be reported by measured units as described above and, when applicable, by measured units for their subordinate units/elements with assigned missions that do not report separately while these elements are in this reporting status. Various scenarios and conditions for assigned mission status reporting are explained in DA Pam 220-XX and the NetUSR User's Guide and user help screens.

d. Reporting by exception. Assigned mission status data will be determined and reported for Army units/elements that do not meet the above criteria when directed by HQDA (DAMO-ODR) or the ATA, by exception. For example, DUIC elements that have been assigned exceptional operational requirements that warrant visibility via a CUSR can be directed to prepare and submit reports in accordance with the provisions of paragraph 10-2 .

e. Measured areas supporting A-level measurements. The two measured areas-assigned mission manning (AMM) and assigned mission equipping (AME) that support the determination of the overall A-level assessment are outlined in table C-1 . The initial A-level determination is based on the worst case level of these two supporting measured area levels. Commanders may upgrade/downgrade this initial A-level determination in accordance with the provisions of AR 220-1 , paragraph 4-5. (Note that the commander's assessment of the unit's training proficiency in the tasks associated with the assigned mission and the serviceability status of mission required equipment items should be considered when determining the need for subjective changes to the A-Level.)

f. Establishing assigned mission requirements. For any mission assigned to a unit by the ATA, the ATA will establish or convey the specific manning and equipping requirements to the unit that will serve as the basis for the unit's determination of the AMM and AME levels as follows:

(1) The ATA can, without further HQDA-approval, establish the manning and equipment requirements for the assigned mission and convey them to the unit when

(a) The manning and equipping requirements determined by the ATA for the assigned mission do not exceed the unit's MTOE/TDA requirements.

(b) The manning and equipment requirements determined by the ATA for the assigned mission exceed the unit's MTOE/TDA requirements but the ATA will resource the overages internally.

(c) The manning and equipment requirements determined by the ATA for the assigned mission exceed the unit's MTOE/TDA requirements but the overages have been formally approved by the DCS, G-3/5/7. For example, further HQDA approval is not required for equipment requirements that are established on a mission essential equipment list (MEEL) that has been formally approved by the DCS, G-3/5/7 for specific missions.

(2) The ATA will obtain the approval of the DCS, G-3/5/7 before establishing or conveying manning and equipment requirements when

(a) The manning and equipment requirements determined by the ATA for the assigned mission exceed the unit's MTOE/TDA requirements in any way (that is, by type/grade/classification or by number) and will not be resourced internally by the ATA.

(b) The manning and equipment requirements determined by the ATA for the assigned mission will result in an operational needs statement or a joint unit operational needs statement.

(3) Following determination by the ATA of the unit's manning and equipment requirements for the assigned mission and, if applicable, any HQDA actions required, the ATA will provide the appropriate command guidance to clearly establish the approved requirements. For example, the ATA guidance will specify any additions or deviations to the unit's MTOE/TDA requirements, include or reference the memorandum received from the DCS, G-3/5/7 approving specific additions or deviations to the MTOE/TDA requirements, cite the formally approved MEEL or ONS that is applicable, and so forth.

(4) If the manning and equipping requirements for the currently assigned mission are not specified to the unit by the ATA, then the unit commander will use the MTOE/TDA requirements for personnel and equipment as the basis for determining and reporting the unit's manning and equipping status levels for the assigned mission. This means that the AMM and AME levels will replicate the P and S-Levels determined by the unit to support the C-Level assessment.

(5) Commanders will provide appropriate comments to explain any resource or training deficiencies for their units' assigned missions and to explain their concerns regarding their units' overall readiness for their assigned missions.

(6) The NetUSR User's Guide and user help screens explain A-Level reporting procedures and provide detailed data entry instructions. Tables C-1 and C-2 and outline the applicable metrics and figures C-1 and C-2 and illustrate the process.

Table C-1. Assigned mission manning and assigned mission equipping level measurements
Measurement ( Note 1) Level 1 Level 2 Level 3 Level 4
Assigned Mission Manning (AMM) ( note 2) = 90 - 100 percent of mission required personnel and = 85 - 100 percent of mission required senior grade personnel currently are available = 80 percent of mission required personnel and = 75 percent of mission required senior grade personnel currently are available = 70 percent of mission required personnel and = 65 percent of mission required senior grade personnel currently are available <70 percent of mission required personnel or <65 percent of mission required senior grade personnel currently are available
Assigned Mission Equipping (AME) (notes 3 and 4) = 90 - 100 percent of mission required equipment items currently are on-hand (available) = 80 - 89 percent of mission required equipment items currently are on-hand (available) = 65 - 79 percent of mission required equipment items currently are on-hand (available) <65 percent of mission required equipment items a currently are on-hand (available)

Notes:
1. All resource status measurements are based on the applicable requirements documents or ATA guidance that establish or convey the HQDA-approved resource requirements for the assigned mission. The unit's MTOE/TDA requirements will be used if the ATA has not established or conveyed other HQDA-approved manning and equipment requirements.
2. The assigned mission manning level percentages are determined by dividing the unit's available strength by the mission required strength and the unit's available senior grade strength by the mission required senior grade strength. Mission required personnel are those personnel required by the unit to successfully accomplish the assigned mission as established or conveyed by the Army Tasking Authority. Absent specific guidance regarding the manning requirements for the assigned mission, the AMM level will coincide with the P-Level determination.
3. The assigned mission equipping level percentage is determined by dividing the number of on-hand (available) equipment items required for the mission (numerator) by the number of mission required equipment items (denominator). When determining this percentage, for the numerator consider ONLY those equipment items that currently are on-hand (available) to the reporting unit in accordance with the availability criteria explained in paragraph 3-5b . Do not consider any equipment projections (Example : TPE). For the denominator, consider ONLY those equipment items designated or approved by HQDA or the ATA as required by the unit to successfully accomplish the assigned mission. The unit's mission requirements normally consist of unit organic equipment and TPE and equipment transfers planned as part of the relief in place process.
4. Beginning at LAD minus 180 days or earlier when directed, deploying units also will determine and report a projected AME level. While the denominator for this projection will continue to be based on the unit's mission requirements, the numerator will consider equipment that is either currently on hand (available) or projected for use by the unit to accomplish these mission requirements. Accordingly, the numerator for this projection may include TPE following the completion of a PDSS by the unit, APS formally designated for receipt by the unit, and equipment transfers from other units that have been planned, ordered and approved by the applicable authorities. Note that while this projected AME level is a mandatory data point, it is not considered in the A-Level determination.
5. The initial A-Level determination will match the lowest (worst case) of the AMM and AME levels. Upgrades/downgrades are governed by the provisions of AR 220-1, paragraph 4-5.


Table C-2. Assigned mission levels (A-levels) descriptive criteria
A- Level 1 A- Level 2 A- Level 3 A- Level 4
The unit is fully trained and possesses the resources required to undertake the assigned mission. The unit is trained and resourced to undertake most of the assigned mission. The unit is trained and resourced to undertake many, but not all portions of the assigned mission. The unit requires additional resources or training to undertake the currently assigned mission; however, it may be directed to undertake portions of the assigned mission with the resources on hand.



Figure C-1. Decision Tree for Reporting A-Level





Figure C-2. Decision Tree for Reporting AMM and AME Level


Appendix D
Equipment Readiness Codes and Pacing Items

D-1. General

a. The Joint Staff's GSORTS guidelines require reporting units to calculate the equipment on hand status level (S-Level) by separately considering their combat essential equipment and their other end item and support equipment. AR 71-32 establishes that only minimum mission essential wartime personnel and equipment will be included in TOE. The ERCs are used to indicate the importance of specific equipment items to the unit's mission and, more specifically, to the unit' s war-fighting capabilities specified in doctrine and TOE Section I. ERCs 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 mission tasks and functions. (For example, ammunition and fuel trucks that support the primary weapon/mission system and technology automation equipment in sustainment units.)

b. Tasks and functions that are less directly (or indirectly) related to the primary mission tasks also require coding distinction. These may be tasks that are required to provide sustainment support for the organization at large. They are often related to logistic or administrative functions (such as feeding, distribution of general supplies, maintenance, and secondary means of communication) that may be essential but do not directly impact on accomplishment of critical combat tasks. Codes also distinguish between the criticality of certain categories of equipment based on types of missions (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 (see para B-2, below).

D-2. Equipment readiness code definitions

a. ERC A or ERC P. Principal weapon/mission systems and equipment (to include technology automation equipment), which are essential to the accomplishment of primary doctrinal mission tasks and force protection, and critical mission support items. Critical mission support items are selected items of equipment required to refuel, rearm, power, move, recover, provide medical support, or provide direct command and control. The ERC P items are ERC A items/systems that are also designated as pacing items (see para D-5 ).

b. ERC B. Auxiliary equipment (AE) and/or associated support items of equipment that are required to support ERC A or P equipment and provide mission sustainment support. This category of equipment includes items/systems required to transport, maintain, supply, service, cover/shield, enhance or backup ERC A/P items.

c. ERC C. Auxiliary support equipment (ASE) and/or ASIOE that are required for unit sustainment and to perform administrative or other support tasks that have little or no immediacy to sustainment of operating tempo.

d. Exceptions. Exceptions to the above criteria include individual and crew served weapons, communication equipment, critical technology automation equipment, and selected maintenance support equipment. Exceptions in those areas are specified in paragraph D-3 . The exceptions recognize the unique risks involved in combat operations conducted by maneuver forces and their greater need due to what is often continuous movement on the battlefield and immediacy of need.

D-3. Coding guidelines

a. Items will not be coded as pacing items unless they are specifically identified in the listing of pacing items on the official HQDA FMSWeb (FMS, formerly The Army Authorization Documentation System (now FMS) online (WebTAADS)).

b. If a LIN is identified as ERC A or ERC P, all associated items listed by separate LINs will be considered ERC A unless specified otherwise in the Web page listing of pacing items in the FMSWeb. (Note: Associated items of ERC P LINs are not in the pacing items list.)

c. Not all wheeled and track vehicles are ERC P or A. Depending on the mission and nature of the unit, some wheeled and tracked vehicles and their subsystems may be coded ERC B (AE). For example, a 1.25-ton truck with radios may be coded as ERC B in the HHC of a mechanized battalion. (In a mechanized unit, tracked vehicles are normally the principal items used for command and control of tactical operations.) In a nonmechanized battalion, the same vehicle could be coded ERC A.

d. In TOE/MTOE units, an item's readiness code assignment is based on how essential that item is to the primary mission of the unit. Similar items in a unit can have different equipment readiness codes. For example, within a TOE/MTOE it may be appropriate to designate the commander's radio as ERC A and another radio in the unit as ERC B.

e. Generally, the ERC for any item specifically identified by nomenclature or model will also apply to replacement/modernization items.

D-4. Designating equipment readiness codes

a. The USAFMSA will use the ERC guidelines provided in paragraphs D-1 through D-3 and on the applicable Web pages at the Force Management System Web site (FMSWeb, formerly WebTAADS) to assign readiness codes to TOE equipment items.

b. The 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. The ERC and pacing item guidelines contained on the FMSWeb are not all encompassing listings of ERC codes for all equipment in TOEs, but reflect the need to distinguish mission essential equipment. However, if an item is included in the FMSWeb, the ERC listed will be used unless a specific exception is coordinated with the organization proponent and approved by DAMO-FMF in coordination with DAMO-ODR. If an item is not specifically included in the Web page listings at the FMS, then the organization documenter, in coordination with the organization proponent, will determine the appropriate ERC using similar items in the tables as guides. In case of difference in agreement DAMO-FMF in coordination with DAMO-FMO & DAMO-OD will be the final approval authority.

d. Items that are generally ERC A, but could be ERC P in some organizations/circumstances, will be coded P only when identified in the authoritative listing of pacing items maintained at the FMSWeb site.

D-5. Pacing Items

a. Unless identified differently in the authoritative listing of pacing items in the Force Management System Web site (FMSWeb, formerly WebTAADS), the majority of units should have two pacing items. If more than four pacing items are on a unit's MTOE/TDA, USAFMSA will inform DAMO-FMF which will coordinate with the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, and TRADOC regarding any adjustments required. Approval of exceptions may be requested by the responsible ACOM/ASCC/DRU and/or DARNG/NGB, when applicable, or by USAFMSA from HQDA, DAMO-FMF. The following criteria normally limit the number of pacing items in a unit to four. Major equipment items will be designated as pacing items if they are:

b. Key to a unit's capabilities, as delineated in its requirement and authorization documents.

c. Central to a unit's ability to perform its doctrinal mission (for example, a howitzer in a field artillery battalion).

d. 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.

e. 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 status reporting in recognition of their interchangeability with respect to the critical capability. (Note. The items must still be reported separately in materiel condition status reports. Two or more items may be essentially the same but identified by different LINs because they have different auxiliary equipment. For example, bulldozers are assigned 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 coded ERC P.)

f. If several similar LINs are listed in SB 700-20 ( EM 0007), appendix H, as substitutes for each other, they should be grouped under one LIN for FMC computations. For example, if unit A has two trucks of type LIN X, three trucks of type LIN Y, and four trucks of type LIN Z, and LINs X, Y, and Z are substitutes for each other in accordance with SB 700-20, then for USR purposes unit A should compute FMC for these trucks based on the total quantity of the group (that is, 2 + 3 + 4 = 9).

g. When dissimilar units are grouped in a single battalion to enhance command and control, pacing items will be reported as if the subordinate elements were separate companies or derivative equivalent organizations. In such cases, subordinate unit pacing items will not be used to compute battalion headquarters readiness. (For example, in the main support battalion of a DISCOM, the number of designated pacing items will be kept to the lowest possible number consistent with the above guidance.)

h. Not all organizations will have equipment designated as pacing items. Many units (such as light infantry rifle companies and personnel services companies) are principally organized around personnel resources and not key items of equipment. For those organizations that have low density, high cost ERC A equipment, it may not be appropriate to designate those items as pacing items.

D-6. Unit pacing items

a. 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 (DAMO-FMF).

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 the overall C-Level, as appropriate.

D-7. Exceptions to paragraph D-6

a. If a unit is short an equipment item designated as a pacing item, but it has an authorized substitute (SB 700-20) or an "ILO" item that substitute item will be counted as a pacing item in place of the item the unit is short.

b. A unit that receives a modernization item as a replacement for a current pacing item will consider the new item to be the pacing item, even if it has not yet been coded with a "P" in the ERC column. (For example, UH-60 helicopters may replace UH-1 helicopters or M1A2 tanks may replace M1 tanks.) During transition, both old and new items may be counted. If enough new items have not been received to meet the total authorization, then old items must be on hand in the unit and be in use. (They cannot be turned into a maintenance unit or otherwise placed out of the unit commander's control.)

c. TDA units will not report pacing items until such time as they are designated on their TDA or in consonance with AR 220-1 .

D-8. Use of pacing items for preparing reports

Pacing items are limiting factors in determining S and R-levels. For battalion size and smaller units, these levels will be no higher than the lowest pacing item level in EOH or ER, respectively. Equipment percentages and/or levels for pacing items will be computed the same as for other reportable LINs.

D-9. Recommending changes

a. Submit recommended ERC changes for specific unit LINs, with justification, through channels to HQDA, Office of the Deputy Chief of Staff, G-3/5/7 (DAMO-FMF), 400 Army Pentagon, Washington, DC 20310-0400. DAMO-FMF is the final approval authority for changes.

b. The authoritative listings of ERC and pacing item information will be posted on the Force Management System (FMSWeb, formerly WebTAADS). Access to the FMSWeb is at https://fmsweb.army.mil/. Access to the Web site requires a userID and password that can be obtained as follows:

(1) On the main page, click on FMSWeb.

(2) Enter AKO login and AKO password.

(3) The FMSWeb Account Request Form will be displayed. Select the system access level of Normal FMSWeb access and click Continue.

(4) Type in your AKO user name and password again.

(5) From the drop-down menu select your clearance level.

(6) Type in your security officer's name, phone number, and e-mail address, and click Continue.

(7) Once your account has been approved, login using your AKO user name and password. Go to LOOKUP TOOLS.

(8) Go to ERC tables/readiness.

(9) Look under tables B and C.

D-10. Process and procedures for maintaining and updating equipment readiness code and pacing item information.

The process and procedures to maintain and update ERC and pacing item information falls under the purview of AR 71-32 .

Appendix E
Determining Current Aggregate Equipment On-hand (Accountable) Status by Component and Current Aggregate Equipment On-hand (Available) Status by State or Territory

E-1. Background

a. The Army continues to meet current operational demands and to restructure into a Modular force. The challenge of maintaining unit readiness and capabilities to ensure that units are well equipped to meet wartime and homeland defense missions requires "operationalized" RC forces (ARNG and USAR) and significant management oversight and precise resource synchronization for all force structure components (COMPOs) to ensure that Army units have what they need to perform full spectrum operations, to include civil support missions.

b. Although civil support missions are not limited solely to ARNG units, as a dual-purpose force with both a Federal and State mission, the Army National Guard (ARNG) is particularly well suited for civil support missions. The ARNG's Federal mission is to maintain well-equipped units available for prompt mobilization during war and provide assistance during national emergencies (such as natural disasters or civil disturbances). When ARNG units are not mobilized or under federal control, they are supervised by the JFHQ-State and report to the Governor via the Adjutant General of their respective state or territory. When directed by the Governor or the appropriate state authority, ARNG forces can respond quickly to perform homeland defense and homeland security activities within US territory. In the event of national emergencies, it is likely that ARNG units will be deployed/employed in advance of a formal federal response.

c. Because of the heavy use of ARNG units in ongoing overseas operations and their increased role in homeland defense missions, Congress is especially interested in the current and projected equipping status of the ARNG and the overall readiness of ARNG units to respond to any state assigned missions. The 2008 National Defense Authorization Act (NDAA) requires the SECDEF to provide an annual report to Congress regarding the readiness of National Guard equipment to support civil authorities or to respond to domestic emergencies or major disasters. USD, P&R spiral guidance memorandums #2 and #4 require that National Guard units report into OSD DRRS on both their Federal and State missions. To meet these reporting requirements

(1) ARNG units prepare and submit CUSRs via NetUSR to report readiness status for their assigned missions (includes state assigned missions) in accordance with the provisions of this publication and AR 220-1 .

(2) The JFHQs-State and State Joint Task Forces report directly into OSD DRRS regarding their overall capabilities for mission requirements IAW the applicable DOD or NGB policy guidance.

(3) The DARNG identifies critical dual use equipment items necessary for Army units and personnel to support civil support operations. (4)

(4) The DCS, G-8 prepares and submits externally directed reports indicating current and projected Army equipment status, to include the CDU equipment items.

E-2. Purpose and scope

a. Headquarters, Department of the Army (HQDA) is required to establish an authoritative list of critical dual use (CDU) equipment items to facilitate Army compliance with various Congressional mandates regarding domestic security preparedness. These mandates require the Army to plan to support civil authorities in the event of a catastrophe or national emergency. The Army plan includes requirements to develop and annually update a comprehensive and authoritative list of CDU equipment items that can provide needed equipment to strengthen national preparedness. Hence, this appendix explains the process and critical milestones in support of the Army's responsibilities. Subsequently, the authoritative list of CDU equipment items resulting from the execution of this process will be used by all stake holders as the basis to prepare and submit reports to Congress and to request funds during POM cycle. The process will ensure that the Army speaks with one voice to other departments, agencies and Congress regarding Army equipment issues.

b. This appendix explains the HQDA-approved process for compiling and representing the current aggregate equipment status data in external reports. The process to determine the projected aggregate equipment status will be developed by the DCS, G-8 and promulgated in a separate publication. While the procedures explained in this appendix to determine the current aggregate equipment status data by COMPO and by state or territory use some of the methodologies established for unit status reporting and exploits equipment status data reported by units into the DRRS-Army database via the CUSR, these procedures constitute an entirely separate process that also uses data obtained from other sources and applies distinct business rules and methodologies that are not applicable to unit status reporting.

E-3. Concept

a. The process explained in this appendix to determine the current aggregate equipment status by COMPO and by state or territory provides the "right now, point-in-time" equipment status assessments for use in all externally directed reports. It does not support the projections of future requirements, inventory, distributions, procurements or the resulting computations of projected status, shortages and/or funding shortfalls that, if required for externally directed reports, will be determined separately by the DCS, G-8 using internal tools. It also is a separate and distinct process from the unit status reporting process and is in no way related to a unit' s S-Level determinations. To explain this process, the term "EOH (accountable)" is used in this appendix to signify accountability via authoritative Army property accountability systems (that is, LIW/PBUSE) while the term "EOH (available)" is used to indicate that the equipment items are currently possessed and/or controlled by the designated entity. The process establishes the "percent of fill" (POF) as the common metric to represent the EOH (accountable) and the EOH (available) status of Army equipment items, and this POF status will be determined in a similar manner for each COMPO and for each state or territory. Subsequently, an aggregate EOH (accountable) POF status will be determined for each COMPO, and an aggregate EOH (available) POF status will be determined for each state or territory. Critical Dual Use (CDU) equipment items are those deployable, war-fighting equipment items specifically identified by the DARNG and approved by the DCS, G-3/5/7 (DAMO-SS, DAMO-OD and DAMO-FM), that have high utility for domestic missions (for example, Defense Support to Civil Authorities). CDU equipment items support the requirements of ARNG units to successfully execute both their federal and their state assigned missions.

b. Because mobilized ARNG units do not fall under the purview of the states and territories while they are in a Title 10 status, the specific procedures in this appendix for determining the EOH (available) status of equipment items for states and territories are applicable to nonmobilized ARNG units only. The DRRS-Army software applications will apply the data and information contained in current CUSRs and will import or top load relevant information from ADS to support the current EOH (accountable) POF calculations required for the COMPO aggregations. DARNG, in coordination with the applicable ARNG element of the JFHQ-State, will provide the additional data necessary to support determining the current EOH (available) status of the individual states and territories.

c. The process for determining the current EOH (accountable) status by COMPO and the current EOH (available) status by state or territory will not require that any reporting units have any additional status reporting requirements. This appendix explains procedures and metrics needed to determine, aggregate and report the EOH (accountable) status for COMPOs and the EOH (available) status for states and territories accurately and uniformly during this process. While the results of this process will provide authoritative current EOH (accountable) status data by COMPO and EOH (available) status data by state or territory to meet HQDA's externally directed reporting requirements, the resulting POF status data must be carefully evaluated in consonance with other salient factors in order to assess equipment sufficiency or deficiency for specific missions or requirements.

E-4. Responsibilities established by AR 220-1

a. DCS, G-3/5/7 will

(1) Approve the authoritative listing of CDU equipment items and CDU equipment categories recommended by the DARNG and maintained by the Deputy Chief of Staff, G-8 (DCS, G-8) in coordination with DCS, G-4 and AMC.

(2) Review for accuracy all external reports prepared by the DCS, G-8 that include data compiled under the provisions of this appendix.

b. The DARNG, in coordination with the ARNG elements of the JFHQ-States, will

(1) Ensure that appropriate and timely transactions are accomplished by all ARNG units in accordance with AR 735-5 and AR 710-2 so that the accountability by UIC and DUIC of all ARNG equipment items is accurately reflected in LIW/PBUSE. Following unit mobilization but prior to their deployments, ensure that all equipment items left behind by deploying units are transferred to the property book accounts of their rear detachment DUICs and/or to other ARNG units.

(2) For ARNG MTOE units with AA-Level UICs that are based in more than one state or territory, determine how the total equipment requirements of the AA-level UIC will be split between/among the states/territories where the organic elements of the AA-Level UIC are based and provide this information to DAMO-ODR for top loading into DRRS-Army.

(3) Participate in forums hosted by DAMO-ODR to establish and develop DRRS-Army software requirements. Monitor and analyze ARNG equipping trends as required.

(4) In coordination with the DCS, G-8, recommend to the DCS, G-3/5/7 the CDU equipment items and the CDU equipment categories that best enable the ARNG to support civil authorities and that most effectively represent the ARNG's essential equipping requirements, respectively.

c. DCS, G-8 , in coordination with DARNG, DCS, G-4, AMC, and DAMO-FM will

(1) Maintain the Army's authoritative listing of CDU equipment LINs and the applicable LINs for each of the equipment categories established in this appendix, as required.

(2) Determine current equipping status data by COMPO and by state or territory following the procedures established in this appendix.

(3) Pursuant to the DCS, G-8's responsibility for transitioning approved Army requirements from the planning to the programming phase, develop, coordinate and publish separate procedures for determining projected equipping status data by COMPO and by state or territory.

(4) Following coordination with key stakeholders, prepare and submit externally directed reports.

(5) Participate in forums hosted by DAMO-ODR to establish and develop DRRS-Army software requirements.

(6) Monitor and analyze Army equipping trends, as required.

d. DAMO-FM will ensure that requirements data in Structure and Composition System (SACS) and FMSWeb is maintained and updated. Provide files to DAMO-ODR and/or establish linkages to the DRRS-Army database, as required.

e. DCS, G-4 will

(1) In coordination with AMC, ensure that current and correct property accountability data for all units and applicable organizations and activities accountable for Army equipment items (includes DUICs and any state controlled organizations and activities in which Army equipment items may reside) is available via LIW/PBUSE and will ensure that asset visibility systems under its purview apply the business rules established in this appendix for equipping status determinations. (2)

(2) In accordance with DCS, G-8 and DAMO-FM, maintain and update the authoritative listing of authorized substitute items and obsolete equipment items in SB 700-20, as required.

E-5. Procedures

a. General. The current EOH (accountable) status for each COMPO and the current EOH (available) status for each state or territory will be determined as a percentage of fill calculated LIN, by designated equipment category, in the aggregate and for the overall total in accordance with the process outlined in paragraph 10-10, AR 220-1 , and paragraph 12-8 of this publication and explained in detail in this appendix. ERC is not a factor in these current equipping status determinations. The procedures in this appendix for aggregating current equipment status data are applicable to all COMPOs, states and territories and will be used within HQDA to ensure that uniform results are produced to support external reporting requirements. The four step process explained in this paragraph applies to current status determinations for Army equipment items only. It is not applicable to any equipment items received from other Services or government agencies that may be currently possessed by the COMPO, state or territory. DRRS-Army software applications will support the equipment status determinations for all Army MTOE parent units (AA-Level UICs) in accordance with the provisions of AR 220-1, paragraph 9-3; however, determining the current availability of Army equipment items by state and territory may involve organizations that do not routinely prepare and submit a CUSR and, therefore, whose equipment assets are not captured in the DRRS-Army database via the CUSR process. Accordingly, determining the current equipment status of Army equipment items possessed by any organization that does not routinely prepare and submit a CUSR will be accomplished by importing or top loading data from ADS into the DRRS-Army database and subsequently accomplishing the required calculations via the ARMS application. Neither the provisions of AR 220-1 nor the provisions of this publication establish additional equipping status reporting requirements for Army reporting units.

b. Basic guidelines.

(1) Procedures for determining the EOH (available) status of ARNG equipment items for the state or territory apply to MTOE units only. Equipment items currently possessed by mobilized ARNG units in a Title X status are not included in the EOH (available) status determined for the state or territory.

(2) In addition to establishing procedures regarding how current status data will be compiled by COMPO and by state or territory, the process established in this appendix also addresses how to determine current aggregate equipment status data by LIN, by individual equipment category, and provide for an overall total, regardless of category.

(3) Procedures for determining the current EOH (accountable) status of CDU equipment items by COMPO and the current EOH (available) status of CDU equipment items by state or territory will include only those LINs on the currently approved CDU list.

c. The four step process for determining current EOH (accountable) status by COMPO and current EOH (available) status by state or territory is as follows:

(1) Step 1: Determine the equipment items that currently are required by each COMPO and by each state or territory.

(a) COMPO determination procedures. The FMSWeb will be the authoritative database for determining requirements by COMPO. Requirements data from FMSWeb will be imported or top loaded into DRRS-Army.

(b) State or territory determination procedures. The current equipment requirements by state or territory will be determined by aggregating the requirements of the ARNG MTOE units currently located in that state or territory. The equipment requirements for ARNG MTOE parent units (AA-Level UIC) with organic elements that currently are located in more than one state or territory will be split between/among the applicable states/territories. The DARNG will provide the data reflecting the splitting of these requirements for top loading into DRRS-Army.

(2) Step 2: Determine the equipment items that should be included in the current EOH (accountable) status for each COMPO and in the current EOH (available) status for each state or territory. Equipment items that have been deemed obsolete by HQDA will not be included in these determinations; however, HQDA authorized substitutes will be applied. Authoritative data from SB 700-20 will be top loaded into DRRS-Army to facilitate these procedures.

(a) COMPO determination procedure. The LIW/PBUSE will be used to determine the current EOH (accountable) status by LIN for each COMPO. Obsolete LINs will be discarded and authorized substitutes will be applied based on SB 700-20 data top loaded into DRRS-Army.

(b) State or territory determination procedures. The current EOH (available) status for each state or territory will be determined by aggregating the equipment items currently reported as EOH (available) by the non-mobilized ARNG MTOE units and elements that are currently located in each state or territory. The EOH (available) status of equipment items currently possessed by any non- reporting non-mobilized MTOE elements of ARNG units will be determined using LIW/PBUSE data and applying the procedures for EOH (accountable) (vice EOH available) status determinations. Authorized substitutes and ILO items are applicable to MTOE parent units only and are determined and reported via NetUSR by MTOE parent units in accordance with the provisions of AR 220-1 , paragraph 9-3; they are not applicable otherwise in this EOH (available) status determination process for states and territories. Obsolete LINs will be disregarded in accordance with AR 220-1, paragraph 9-3.

(3) Step 3: Calculate the current aggregate EOH (accountable) status for each COMPO and the EOH (available) status for each state or territory.

(a) COMPO EOH (accountable) status determination procedures. By LIN, divide the sum of the currently EOH (accountable) quantities determined in step 2 by the sum of the currently required quantities determined in step 1 and multiply the results by 100. Subsequently, aggregate results by the equipment categories established in table P-1.

(b) State or territory EOH (available) status determination procedures. By LIN divide the sum of the currently EOH (available) quantities by the sum of the currently required quantities and multiply the results by 100. The aggregate determinations accomplished for each state or territory will include the status data for Army equipment items currently possessed by the MTOE elements that was top loaded. Subsequently, aggregate results by the equipment categories established in table P-1.

(4) Step 4: Use the current percentages of fill determined in step 3 to prepare external reports indicating the status of Army equipment items by COMPO, state and territory.

Table E-1. Designated equipment categories for current equipment on hand (accountable) status determinations by COMPO and for current equipment on hand (available) status determinations by state or territory
CAT Description of the equipment category LINs included in the equipment category Remarks
1 All CDU equipment items Prescribed by DCS, G-8 in coordination with DARNG Notes 1 &2
1A Command and control Prescribed by DCS, G-8 in coordination with DARNG Notes 1 &2
1B Force protection Prescribed by DCS, G-8 in coordination with DARNG Notes 1 &2
1C Maintenance Prescribed by DCS, G-8 in coordination with DARNG Notes 1 &2
1D Aviation Prescribed by DCS, G-8 in coordination with DARNG Notes 1 &2
1E Engineer Prescribed by DCS, G-8 in coordination with DARNG Notes 1 &2
1F Medical Prescribed by DCS, G-8 in coordination with DARNG Notes 1 &2
1G Communications Prescribed by DCS, G-8 in coordination with DARNG Notes 1 &2
1H Transportation Prescribed by DCS, G-8 in coordination with DARNG Notes 1 &2
1I Security Prescribed by DCS, G-8 in coordination with DARNG Notes 1 &2
1J Logistics Prescribed by DCS, G-8 in coordination with DARNG Notes 1 &2
2 Total (Overall) Includes all equipment items, to include non-CDU equipment items Note 3

Notes:
1. A percentage of fill will be determined for each equipment category in this table by dividing the sum of all equipment items in the equipment category that currently are EOH (accountable) for the COMPO determination based on LIW/PBUSE data and that currently are EOH (available) for the state or territory determination based on CUSR and top loaded data by the sum of all equipment items in the equipment category that currently are required.
2. The equipment items in categories #1A thru #1J are the CDU equipment items applicable to that category. Hence, categories #1A thru #1J are subsets of category 1.
3. The total (overall) percentage of fill includes all reportable equipment items regardless of category or CDU status.

d. Annual milestones.

(1) NLT 1 August: DAMO-ODR will solicit CDU update proposals from primary stakeholders (DARNG/NGB, Chief, Army Reserve/USARC, DAMO-CI, DCS G-4, DCS, G-8, FORSCOM, and ARNORTH) and from other ACOMs, ASCCS, DRUs, and ARSTAF.

(2) NLT 1 October: DAMO-ODR will review proposed CDU equipment list submitted by primary stakeholders and identify potential issues, if any.

(3) NLT 1 November: DAMO-ODR will staff a CDU equipment list update proposal among primary stakeholders to gain consensus before submitting list to DCS, G-3/5/7.

(4) NLT 1 December: DAMO-ODR will submit the proposed CDU list update to DCS G-3/5/7 for approval.

(5) NLT 1 January: DAMO-ODR will use the approved CDU list to update the DRRS-Army database.

Appendix F
Procedures for Status Reporting by Generating Force Organizations (except Army installations)

F-1. Background

a. The generating forces is comprised or organizations whose mission is to generate and sustain the Operational Army's capabilities for employment by joint force commanders. As a consequence of its performance of functions specified, and implied by law, the Generating Force also possesses operationally useful capabilities for employment by, or in direct support of, joint force commanders. Generally, the components of the Generating Force include ACOMs, DRU Headquarters, United States Army Recruiting Command (USAREC) units, depots, schools, and centers.

b. While the unit status reporting process for Army Operating Force units is longstanding, well defined, and heavily influenced by the information requirements of external authorities (that is, OSD, Joint Staff, combatant commanders, and so forth), the status reporting process for Army Generating Force units is less mature and the information requirements continue to evolve. Unlike operational Army units which are usually assigned to combatant commanders (CCDRs) and report status information to support the requirements of the CCDR to assess the capabilities and risks associated with the operations and contingencies that he is responsible for, organizations within the generating force typically are assigned to the Department of the Army and report status information to support the information requirements of HQDA.

c. FM 1-01 defines the Army's Generating Force and establishes as doctrine the employment of its capabilities in support of ongoing joint and multinational operations and deployed forces.

d. Although most, but not all, Generating Force units are organized under a TDA, their roles, missions and structures are far more diverse than those of Operating Force units, and several generating force organizations are unique.

F-2. Purpose and scope

This appendix explains the basic reporting procedures for Army Generating Force units (less Army installations). Additional information and details on the reporting requirements of generating force organizations are provided at the DRRS-Army portal and data entry instructions are embedded in the NetUSR software application. AR 220-1 , paragraph 8-3 and table 4-1 establish which generating force units are required to submit reports and prescribe the reporting frequency, respectively. Appendix G explains the procedures that Army installations and garrisons use to assess and report readiness status information.

F-3. Concept

To the degree possible, the status reporting process for those generating force organizations that are required to report will mirror that for operating force units. Generating Force units organized under MTOEs will follow the same well established policies and procedures that Operating Force units use to assess and report readiness status information. Generating Force units organized under a TDA (except Army installations) will assess and report readiness status information in accordance with the applicable policy in AR 220-1 and the procedures explained in this appendix.

F-4. Generating force structure

The Structure and Manpower Allocation System (SAMAS) database is the authoritative data source for the force directory listing of all MTOE and TDA units in the Army (Active Component { COMPO 1}, ARNG { COMPO 2} and USAR { COMPO 3}). SAMAS retrievals permit detailed and summary analysis of the Army force structure to include organization, unit description, and strength data. The SAMAS database does not contain detailed personnel data or equipment information; however, it does include over 100 categories of unit information that can be extracted selectively for analysis. Key elements of information, in addition to required and authorized strengths by identity, are the UIC, EDATE, location, assignment code, AMSCO, TPSN, SRC, and DP 99 force type code. The Generating Force is comprised of the following DP force types:

a. Command committed. Generating Force organizations whose sole purpose is to sustain the ACOM, ASCC, or DRU by continuing to support operational capabilities.

b. Operationally available. Army capabilities and forces within the generating force that are not intended to deploy or rotate through the ARFORGEN force pools, but can be made available to deploy as needed (includes trainees, transients, holdees, and students {TTHS}).

c. Strategic Asset. Army capabilities and forces with the Generating Force that do not deploy, but do; however, provide support with reachback capability.

F-5. Status reporting by generating force organizations

a. Reporting units.

(1) Reporting by parent TDA units. The TDA units that are required to report into the DRRS-Army database are those with AA-level UICs (parent units) that have not been officially exempted from reporting in accordance with the procedures in AR 220-1 , paragraph 8-5. These TDA units will submit reports in accordance with the reporting frequency requirements and the minimum data entry requirements established in AR 220-1, chapter 4 for TDA units submitting CUSRs.

(2) Reporting by deploying/deployed TDA units. Any TDA unit with a UIC ending in AA that has been alerted or is currently scheduled for operational deployment away from its home station or that is apportioned in a Joint operations plan or contingency plan is an assessed unit that will report against the resource and training requirements in its formal TDA requirements and authorization document on a monthly basis, unless the deployable/apportioned TDA unit has been specifically exempted from monthly readiness status reporting by HQDA (DAMO-ODR). All TDA units with AA-level UICs (parent units) will submit monthly reports while deployed. The CUSR management oversight authority will identify the TDA units under their purview that are required to report under these criteria and will ensure compliance with the applicable CUSR requirements.

b. Reporting process.

(1) The CUSR management oversight authority in coordination with HQDA, DAMO-ODR, can require additional TDA units/elements or detachments to submit reports or require more frequent reporting than prescribed in AR 220-1. For example, the CUSR management authority, after coordinating with HQDA (DAMO-ODR), can designate as a reporting unit a TDA entity with a DUIC that is not deploying/deployed and, therefore, required to report in accordance with the provisions of AR 220-1 . Similarly, the CUSR management authority can direct a TDA unit with an AA-Level UIC to report monthly vice quarterly. TDA units reporting pursuant to requirements established by the CUSR management authority must comply with the procedures explained in this appendix and the NetUSR Users' Guide and user help screens. For example, TDA units/elements with DUICs directed to report into the DRRS-Army database must use the applicable NetUSR report types designed for DUICs. All reports will be forwarded to HQDA in accordance with the submission timeline explained in AR 220-1, chapter 4.

(2) Because the equipment items listed on TDA documents are not currently ERC coded, those TDA equipment items listed in the MMDF have been and will continue to be considered as ERC A for CUSR purposes, unless supplemental guidance approved by HQDA (DAMO-ODR) establishes otherwise. ACOMs, ASCCs, DRUs, and/ or DARNG-level organizations that require more definitive readiness coding of equipment items in their TDA units and organizations to accommodate unique command requirements may establish additional readiness coding criteria in a supplement to AR 220-1 that would be applicable only to their units. Supplements to AR 220-1 require formal approval by HQDA (DAMO-ODR).

(3) The policy guidance governing subjective upgrades and downgrades in the reports submitted by operation units also is applicable to Generating Force TDA units, unless the ACOM, ASCC, DRU, or DARNG for non-mobilized ARNG units, formally establishes in a supplement to AR 220-1 other provisions for subjectively changing the overall levels. Prior to their implementation, supplements to AR 220-1 must be formally approved by HQDA (DAMO-ODR), and they may provide supplementary guidance for subjectively changing the overall levels of Generating Force TDA units only.

(4) The security classification of CUSRs submitted by TDA units is CONFIDENTIAL, unless a higher level of security classification has been specifically prescribed. For example, CUSRs from TDA units and organizations required to report in accordance with the provisions of AR 220-1 , paragraph 8-4 are classified in accordance with the same criteria that are applicable to MTOE units. All CUSRs submitted by Army installations are classified CONFIDENTIAL in accordance with the provisions in AR 220-1, paragraph 10-6.

Appendix G
Status Reporting by Army Installations into Defense Readiness Reporting System-Army

G-1. Army installations required to submit reports

a. Designated Army Installations are required to report quarterly into DRRS-A. The authoritative listing of the installations and facilities currently required to provide quarterly reports, to include their UICs and corresponding I/Cs will be posted and maintained at DAMO-ODR's unclassified and classified Web sites and accessible via the NetUSR portal.

b. The authoritative listing of the Army installations that are required to submit quarterly reports into DRRS-Army is located on DAMO-ODR's unclassified and classified Web sites under the filename "Installations Reporting (date of last update)." DAMO-ODR's unclassified and classified Web sites can be accessed using the following paths and information:

(1) Unclassified Web site (NIPRNet): available on AKO at https://www.us.army.mil/suite/page/137868.

(2) Classified Web site (SIPRNet): available on AKO-S at http://www.us.army.smil.mil/suite/page/7531.

G-2. Installation status reporting requirements

a. Data entry requirements for installations are located at the "Unit Information," "Training" and "RECAP" tabs in NetUSR software. These are the only tabs that are required for installation status reporting via NetUSR. Data entry instructions are as follows:

(1) The "Unit Information Tab."

(a) In the authorization document data field, always select "Army Command (ACOM) Installation Management Activity CODE." No other selection is applicable.

(b) "Report Information Tab." Select Active Component, National Guard or Army Reserve for the Force Structure Component (COMPO) data entry. Select 'CONFIDENTIAL" to indicate the security classification of the report. All reports are classified CONFIDENTIAL. Select "Operations" (OP) as the current activity code. This code is the applicable activity code for all Installations. Note that the Installation Status Report (ISR) is currently unclassified (UNCLAS); however, installation status data becomes classified (CONFIDENTIAL) by compilation when entered into the DRRS-A database via the NetUSR software. This security classification guidance is in accordance with the provisions of AR 380-5, and is consistent with the security classification guidelines for unit status reporting contained in chapter 13 . While ISR Approvers/Administrators are not required to change the classification of the ISRs that they prepare and manage outside of DRRS-A, they must understand that combining normally unclassified ISR data with the other unclassified information required for entry into DRRS-A results in a classified report. Because many ISR approvers/administrators are civilians who may not be familiar with the provisions in AR 380-5 regarding classification by compilation, responsible management officials at ACOMs, ASCCs, DRUs and NGB will emphasize these provisions in supplementary instructions that clearly explain the distinctions between the ISR and DRRS-Army reports

(2) Reporting channels, relationships, and locations. IMCOM installations will report through the South East, North West, South West, North West, Pacific, Europe and Korea regional offices, as appropriate. IMCOM installations will select "IMCOM" (by UIC) as the next higher Operational Control (OPCON) authority and will select "Office of the ACSIM (OCACSIM)" (by UIC) as the next higher Administrative Control (ADCON) authority. Installations under the purview of the Army National Guard (ARNG) will select the "National Guard Bureau (NGB)" (by UIC) as the next higher OPCON authority and will select the applicable Joint Force Headquarters-State (by UIC) as the next higher ADCON authority. Installations under the purview of the United States Army Reserve (USAR) will select (the parent unit UIC) as both the next higher OPCON authority and the next higher ADCON authority. For other Army installations, the responsible ACOM or DRU will designate the appropriate ADCON and OPCON selections. In the "CURRENT LOCATION" data field, all installations will enter "HOME" or the geographic location (GEOLOC) code for the present location. Follow the guidelines in AR 220-1 and chapter 4 of this publication regarding the "CULOC" to determine the security classification of this location information.

(a) For the purpose of infrastructure reporting by installations, a new Derivative UIC (DUIC) has been established for the installation's real property. This DUIC will be registered in the DRRS-Army database (ASORTS db) in accordance with the provisions of AR 220-1, chapter 6 and part III of this publication and will be matched to a corresponding installation code from the ISR database. The DUIC for real property will end with "ZZ" as the last two characters (5 th and 6 th position, that is, W0XQZZ). The complete 5 integer I/C from the ISR will be used to identify each Installation DUIC for reporting via NetUSR software (that is, 36D38).

(b) The first four characters of the installation's UIC will be used to populate the BUI.

(c) The following report logic flow will apply to the Active Component and Army Reserve (USAR) installations under IMCOM control: After each IMCOM regional office receives its NetUSR reports from all of its assigned installations, the responsible regional office will aggregate or "roll-up" this information in a "summary report." After the summary report is compiled at the regional level, each regional office will then forward the NetUSR reports that it received from its assigned installations and the summary report to IMCOM Headquarters.

(d) The authoritative database for Installation Mission Essential Tasks (IMETs) will be the ISR database. IMET status data will be obtained from the ISR database via a direct data feed from the ISR database into the NetUSR local data cache. Therefore, IMET selections available via NetUSR will be limited to those contained in the nine ISR Facility Classes that are associated with the thirty (30) categories and sixty-one (61) subcategories that are currently established. The NetUSR Users Guide contains screen shot examples showing how IMET selection options are linked to facility class, category and sub category at the Training Tab.

b. Training Tab.

(1) The IMETS will map to the ISR Infrastructure Category Level data. Use the ISR Infrastructure category level ratings to generate Y/Q/N MET ratings following the ISR logic model below.

(a) Identify the Y/Q/N rating for each ISR rating. Each of the three ISR ratings for the IMET are assigned a DRRS-A rating of Y/Q/N in the tables applicable to that rating type.

(b) Apply the mathematical formula to derive the Y/Q/N rating for the IMET. The final infrastructure rating for the IMET becomes the lowest of the three DRRS-A ratings for mission support, quality, and quantity. The possible ratings, from highest to lowest, are Y, Q, and N. Tables G-1 , G-2 , , and G-3 indicate the relationship between ISR ratings and IMET assessments.

Table G-1. ISR metrics for mission support
ISR rating MET rating
Mission support
C1 Y
C2 Y
C3 Q
C4 N


Table G-2. ISR metrics for quality
ISR rating MET rating
Quality
Q1 Y
Q2 Y
Q3 Y
Q4 Q


Table G-3. ISR metrics for quantity
ISR rating MET rating
Quantity
C1 Y
C2 Q
C3 Q
C4 N

(2) It is important to note that ISR C-Ratings are not comparable and do not correlate to the overall category levels C-levels) in NetUSR that are reported by operational forces. The following guidelines are applicable to ISR C-ratings.

(a) ISR infrastructure rating system.

(b) Mission Support C-Ratings. For the ISR, the mission support C-rating is calculated based on the color ratings for rated facility components, adjusted by component mission weightings and component mission essential status. Mission support C-ratings start at the facility level and are rolled upward to facility class. For DRRS-A reports, NetUSR will import data at the category level for the 30 category classes and will convert the ISR Mission Support Ratings to MET ratings as follows: C1 and C2 corresponds to the Y MET Rating; C3 corresponds to the Q MET Rating, and C-4 corresponds to N MET Rating.

(c) Definitions of C-Level ratings:

(1) C1: Minor facility condition deficiencies and no significant facility configuration deficiencies, with negligible impact on the capability to support the tenant organizations' required missions.

(2) C-2: Some facility condition deficiencies and/or configuration deficiencies that have limited impact on the capability to support the tenant organizations' required missions.

(3) C-3: Significant facility condition deficiencies and/or configuration deficiencies that impair the capability to support some of the tenant organizations required missions.

(4) C-4: Major facility condition deficiencies and/or configuration deficiencies that present significant obstacles to the tenant organizations accomplishment of required missions.

(3) Quality Q-Ratings.

(a) In accordance with the provisions of DODI 4165 .14, Quality Q-rating is calculated based on the ratio between the total Quality Improvement Cost and the total PRV (Plant Replacement Value) reporting starting at the facility level and rolled upward to the facility class. Total improvement costs equals the sum of restoration cost for all the components of a facility. For DRRS-A reports, NetUSR will import data at the category level for the 30 category classes and will convert the ISR Quality Ratings to MET ratings as follows: Q1, Q2, and Q3 correspondents to the Y MET rating and Q4 corresponds to the Q MET Rating. Facility types with no improvement cost factors will have no quality rating.

(b) Quality Q-Ratings summary .

(1) Q-1: Cost to Fix / PRV&lt;/=10 percent of PRV.

(2) Q-2: Cost to Fix / PRV &rt;10 percent and &lt;/= 20 percent of PRV.

(3) Q-3: Cost to Fix / PRV &lt;20 percent and <&gt;=40 percent of PRV.

(4) Q-4: Cost to Fix / PRV &gt;40 percent of PRV.

(5) PRV equals plans replacement value.

(4) Quantity C-Rating.

(a) The Quantity C-Rating reflects the relationship between the requirement for each type of Facility Category Group (FCG) and the permanent/semi-permanent assets at the reporting location that are available to meet that requirement. The Quantity C-Rating is reported starting at the FCG level and rolled upward to Facility Class. For DRRS-A reports, NetUSR will import data at the category level for the 30 category classes and will convert the ISR Quantity Ratings to MET ratings as follows: C1 corresponds the Y MET Rating, C2 corresponds to the Q MET Rating, C3 corresponds to the Q MET Rating and C-4 corresponds to the N MET Rating.

(b) Quantity C-Ratings Summary. Note that "perm" means permanent assets and "semi perm" means semi-permanent assets. 1.

(1) C-1: Percent of Perm + Semi Perm &gt;/= 95 percent of required.

(2) C-2: Percent of Perm + Semi Perm&gt;/= 80 percent of required.

(3) C-3: Percent of Perm + Semi Perm &gt;/= 60 percent of required.

(4) C-4: Percent of Perm + Semi Perm &lt;60 percent of required.

(a) Commanders can overwrite the Y/Q/N IMET assessments determined by the NetUSR software; however, they must provide a remark to explain the reasons for the overwrite.

(b) The training proficiency assessments (T/P/U) described in FM 7-0 and FM 7-1 are not applicable to installations and there is no column for these "T/P/U" assessments at the NetUSR "Training Tab" for installations. The logic model for determining the Y/Q/N MET assessment is provided below.

(c) "Yes" (Y) Assessment: Installation can accomplish the task to standard under specified conditions.

(d) "Yes" assessments should reflect demonstrated performance in training or operations whenever possible. Installation possesses the necessary resources, or those resources have been explicitly identified to the unit, to allow it to execute when so directed.

(e) "Qualified Yes" (Q) Assessment: Installation is expected to accomplish the task to standard, but this performance has not been observed or demonstrated in training or operations. Installations assessing their task or mission as a "Qualified Yes" can be employed for those tasks. Installation possesses the necessary resources, or those resources have been explicitly identified to the unit, to allow it to execute when so directed.

(f) "No" Assessment: (N) The installation is unable to accomplish the task to standard at this time.

(c) In DRRS-Army, "Yes" or Qualified Yes" indicates that the installation is considered available to provide immediate support

c. Instructions regarding other options and selections.

(1) All IMET's selections are "core tasks". Current Operations should be addressed in the comments for that MET if they are directed METs.

(2) Reporting Installations can enter existing "reason codes" into the "reason" field when reporting task assessments that are other than "Yes". Installations also have unique source codes that can be entered into the reason field that are preceded by the letter "I" and, therefore, are referred to as "I codes." The three (3) I-codes established for use in NetUSR infrastructure assessments are "IQL" for quality, "IQT" for quantity and "IMS" for mission support.

(3) Garrison commanders are required (mandatory) to provide appropriate remarks for those IMET assessments that are other than "Yes". They also may provide (optional) remarks for those tasks assessed as "Yes". The commander's remarks must be updated quarterly.

(4) Please note that the description name on the "Overall Assessments" data field is now called MTOE/TDA/ISR Mission. Garrison Commanders can provide overall remarks regarding their IMETs in the data field for "Overall Assessments" at the RECAP tab. These remarks should be consistent with the remarks on the IMETs that were entered at the "Training" Tab. f.

d. Commanders comments.

(1) Garrison commanders are required to provide overall remarks quarterly in the "Comments" data field. Commanders also are required to indicate the top three (3) issues or concerns that impact on the effectiveness and/or efficiency of operations at their installations and to recommend corrective or resolution actions.

(2) The overall C-Ratings on the RECAP TAB will be comprised of level C1 through C4. Garrison commands must provide overall C Level Rating and "Reason Code for not level 1."

(3) Regional commanders are required to provide overall remarks quarterly in the "Upper Echelon Comments" data field.

G-3. Installation status reporting channels

Army installations routinely submit their status reports through ADCON channels. The following figures depict the specific channels for active duty, ARNG, USAR, AMC, and MEDCOM Installations. Figures G-1 and G-2 shows IMCOM installation reporting channels and USAR installation reporting channels.



Figure G-1. IMCOM installation reporting channels





Figure G-2. USAR installation reporting channels


Appendix H
Illustrative Examples and Scenarios

H-1. General

The following examples are provided to illustrate how various Army units could report under certain conditions and given a specific set of circumstances. Tables H-1 through H-5 in this appendix represent hypothetical situations that were selected to portray various reporting options and procedures; therefore, they may not reflect likely, actual or doctrinal deployment/employment scenarios. Additional examples and responses to FAQs are available online at the DRRS-Army portal.

H-2. Illustrative example

Table H-1 shows the unit with AA-Level UIC in the "RESET Force Pool" submitting a report following recent return from deployment to the CCDR's area of responsibility (AOR).

Table H-1. Illustrative example #1
Scenario: The reporting unit is a COMPO 1 tank battalion that returned last month from rotational deployment where it conducted COIN operations. Although, the BN has not received formal alert orders or specific guidance for a follow-on mission, the battalion has been advised via command channels that it is scheduled to deploy for another rotation after 16 months of dwell time. Therefore, the battalion will not be reissued the MTOE equipment items that were designated as LBE and that remained at the home station under AMC control (CONUS based battalion) or under local command authority (OCONUS based battalion) while the battalion was deployed, and it will quickly transition to training focused on the operational environment for the deployed mission as soon as training guidance is provided by the next higher commander. Currently, the battalion is conducting resetting activities and preparing its monthly CUSR. The following chart outlines some of the key CUSR issues applicable to this scenario and illustrates how this battalion could report. Note that all of the mandatory reporting requirements are not addressed.
WHAT: HOW AND WHY:
1. CUSR Category and Format Prepare and submit a "Regular Report" (AA-Level UIC) using the "Full" format (VS a "Deployed Report" using the "Abbreviated" format that was authorized for use only while the battalion was deployed).
2. BUI Data
-Current unit location Report the home station location ILO the deployed location that was previously reported while the unit was deployed.
3. ARFORGEN data points
-Return date Determine and report the date when 51 percent of the personnel assigned to the unit returned to the home station location from deployment.
-Force pool assignment Report "RESET" based on the "Return Date." (Note: in the future, this data field may be auto-populated by data imported from the AST.)
-Force package designation Report "Deployed Expeditionary Force (DEF)" based on the command guidance regarding subsequent deployment. (Note: in the future, this data field may be auto-populated by data imported from the AST.)
4. Resource & Training Status Measurements
-P-Level Consider and report personnel on block leave during RESET as "available."
-S-Level Based on the provisions in AR 220-1 , paragraph 9-3 and those in paragraph 6-9 of this publication, consider the "retained LBE" as "available" for the S-Level calculation unless directed otherwise by the ACOM/ASCC/DRU.
-R-Level Report based on the MCSR submitted into AMSS. (Note that reporting R5 is not authorized.)
-T-Level Report "T5" ILO "T4" while in the RESET force pool unless directed otherwise. (NOTE that until NetUSR software allows otherwise, this will require that the CDR report several of the unit's METL tasks as UNTRAINED; see "METL" in #5).
-AMM Level N/A ( The A-level triggers do not yet impact)
-AME Level N/A ( The A-level triggers do not yet impact)
5. Y/Q/N MET Task Capability Assessments
-MET Report "N" for most MET tasks.
6. Overall Readiness and Capability Assessments
-C-Level Must report C-5 (based on T5) for next 180 days after the "Return Date"
-Y/Q/N for the "core tasks" mission category (that is, core functions or designed capabilities) Should report "N" for next 180 days after the "Return Date"
-A-Level N/A (A mission is not currently assigned)
-Y/Q/N for the "Named Operations" and "Major Plans" Mission Categories (that is, the Assigned Mission: Current or Contingency Operation) N/A (A mission is not currently assigned)
7. Commander's remarks Identify and explain any significant resourcing or training readiness issues. Clearly distinguish between resource and training issues impacting on the mission pending assignment and those issues impacting on the unit's core functions or designed capabilities. Explain any exceptional METL proficiency issues.
8. Significant data points and projections None.

H-3. Illustrative example #2

Table H-2 show the unit with AA-level UIC in the "Train-Ready Force Pool" submitting a report while preparing for deployment to the CCDR's AOR.

Table H-2. Illustrative example #2
Scenario: The reporting unit is a COMPO 1 artillery battalion that, after 24 months of dwell time, is preparing for deployment to the CCDR'S AOR to provide transportation support. The battalion has received formal alert orders and specific guidance for this assigned mission for which it is scheduled to deploy in 8 months. Because the transportation mission assigned for execution is significantly different from the battalion's doctrinal fire support mission, capabilities and equipment, many of the battalion's MTOE equipment items have been designated as left they will remain while the battalion is deployed. Currently, the battalion is conducting training focused on the operational environment in the AOR and preparing its monthly CUSR. The following chart outlines some of the key CUSR issues applicable to this scenario and illustrates how this battalion could report. Note that all of the mandatory reporting requirements are not addressed.
WHAT: HOW AND WHY:
1. CUSR Category and Format Prepare and submit a "Regular Report" (AA-Level UIC) using the "Full" format
2. BUI Data
- Current Unit location Report the home station location
3. ARFORGEN Data Points
- Force Pool Assignment Report "Train-Ready". (Note: in the future this data field may be auto-populated by data imported from the AST.)
-Force Package Designation Report "DEF" based on the scheduled deployment. (Note: in the future this data field may be auto-populated by data imported from the AST.)
-LAD Report this date based on the formal orders and deployment schedule
4. Resource & Training Status Measurements
- P-Level Consider MR 4 personnel as "available," but note that they cannot be deployed until the required examinations have been completed
- S-Level Based on the provisions in AR 220-1 , paragraph 9-3 and those in paragraph 6-9 of this publication, consider the "retained LBE" as "available" for the S-Level calculation (until deployment) unless directed otherwise by the ACOM/ASCC/DRU.
-R-Level Report based on the MCSR submitted into AMSS.
-T-Level Determine the T-level based on the CDR's TPU assessments of the unit's current proficiency in its FSO METL tasks. (Note that comments are mandatory if the T-level and P-level differ by 2 or 3 levels.)
-AMM Level Determine and report the AMM level based on the specific manning requirements for the assigned mission that were established or conveyed by the Army Tasking Authority. Use the personnel requirements in the MTOE requirements if no guidance was provided.
-AME Level Determine and report the AME level based on the specific equipment requirements for the assigned mission that were established or conveyed by the Army Tasking Authority. Use the equipment requirements in the MTOE if no guidance was provided.
5. Y/Q/N METL Task Capability Assessments
-METL Assess the status of all METs, and, if applicable, any "assigned" mission training requirements to include any out of design METs. Associate applicable the METs with the unit's core functions or designed capabilities or the assigned mission, as appropriate.
6. Overall Readiness and Capability Assessments
-C-Level Determine and report a C-Level based on the PSRT levels and the battalion commander's judgment regarding the overall readiness of the unit to accomplish/provide its core functions or designed capabilities.
-Y/Q/N for the "core tasks" mission category (that is, core functions or designed capabilities) Determine and report this mission category assessment based on the Y/Q/N METL assessments.
-A-Level Determine and report an A-Level based on the AMM & AME levels and the battalion commander's judgment regarding the unit's overall readiness for the assigned mission. The CDR should consider the unit's training proficiency status for the METs associated with the assigned mission and any equipment serviceability factors when determining whether A-level upgrades/downgrades are warranted.
-Y/Q/N for the "Named Operations" and "Major Plans" Mission Categories (that is, the Assigned Mission: Current or Contingency Operation ) Determine and report based on the Y/Q/N assessments of the METs associated with the assigned mission: (For example, Current Operation/Named Operation.)
7. Commander's remarks Identify and explain any significant resourcing or training readiness issues. Clearly distinguish between resource and training issues impacting on the assigned mission and those issues impacting on the unit's core functions or designed capabilities. Explain any post deployment readiness projections required, for example, the projected A-level after receiving resources in theater.
8. Significant data points and projections
-Unit and staff proficiency level Determine and report the level at which subordinate elements currently have achieved training proficiency. (Note that comments are mandatory if the UPL determination does not coincide with the T-Level reported.)
-AMM level projection at LAD+30 Determine and report based on the manning guidance received via command channels.
-AME projection after receiving TPE Determine and report based on equipping guidance received via command channels and the instructions in tables 9-3 and C-2 and .

H-4. Illustrative example #3

Table H-2 show the unit with AA-Level UIC in the "Available Force Pool" submitting a report while deployed to the CCDR'S AOR.

Table H-3. Illustrative Example #3
Scenario: The reporting unit is a COMPO 2 mechanized infantry battalion that is deployed in the CCDR'S AOR conducting COIN operations. Although this mission is clearly within the full spectrum operations for which the battalion was designed, many of the battalion's tracked vehicles were left with rear detachment elements where they will remain while the battalion is deployed. The battalion is conducting mounted operations using wheeled vehicles provided in theater (TPE). Currently, the battalion is preparing its monthly CUSR. The following chart outlines some of the key CUSR issues applicable to this scenario and illustrates how this battalion could report. Note that all of the mandatory reporting requirements are not addressed
WHAT: HOW AND WHY:
1. CUSR Category and Format Prepare and submit a "Deployed Report" (AA-Level UIC) using either the "Full" format or the "Abbreviated" format.
2. BUI Data
- Current Unit location Report the deployed location
- Attachments and Detachments Indicate by UIC/DUIC any units/elements that currently are either attached to or detached from the battalion's organic structure. If the battalion's rear detachment is not currently under its command authority, then report the rear detachment DUIC as "detached".
3. ARFORGEN Data Points
- Force Pool Assignment Report "Available"
- Force Package Designation Report "DEF" based on the current mission status
- Boots on the ground Date Report this date based on the redeployment schedule
4. Resource & Training Status Measurements
- P-Level Consider any personnel augmentations or attachments currently with the unit as available (includes personnel who joined the unit in theater). Consider rear detachment personnel as "available" only if the rear detachment currently is under the command authority of the battalion and the rear detachment personnel can rejoin the unit for mission execution within 72 hours.
- S-Level Do not consider any equipment that was not deployed with the unit as available unless directed otherwise by HQDA. Consider any TPE currently possessed/controlled by the unit that matches its MTOE requirements as "available" for the S-Level calculation unless directed otherwise by HQDA or the ASCC.
- R-Level Report based on the MCSR submitted into AMSS (Full report) or determine and report the unit's equipment serviceability status as of the date of the report (Abbreviated report). Note that in an abbreviated report this is a point in time calculation and not a monthly average.
- T-Level Determine T/P/U assessments based on the unit's current proficiency in its METs.
- AMM Level Determine and report based on the manning requirements for the assigned mission that were established or conveyed by the ASCC.
- AME Level Determine and report based on the equipment requirements for the assigned mission that were established or conveyed by the ASCC.
5. Y/Q/N METL Task Capability Assessments

H-5. Illustrative example #4

Major unit (FF-Level UIC) in the "RESET Force Pool" submitting a report following recent return theater.

H-6. Illustrative Example #5

Major unit (FF-level UIC) in the "Train-Ready Force Pool" submitting a report while preparing for deployment to the CCDR'S AOR.

H-7. Illustrative Example #6

Major unit (FF-level UIC) in the "Train-Ready Force Pool" submitting a report while preparing for deployment to the CCDR'S AOR.

H-8. Illustrative Example #7

Major unit (FF-level UIC) in the "Available" Force Pool" submitting a report while deployed in the CCDR'S AOR

H-9. Illustrative Example #8

Major unit (FF-level UIC) in the "Available Force Pool" submitting a report while deployed in the CCDR'S AOR.

H-10. Example unit status report comments

The following table contains some example comments that were included in the reports received from actual units. These example comments have been sanitized for security classification issues and are sorted by the applicable measured area or assessment to which they are associated. They are provided only as recent examples of meaningful comments. and they should not be used as boiler plates.

Appendix I
Online Reference Tables

I-1. General

The reference tables described in this appendix will be maintained at the DRRS-Army Portal ( http://userguide.drrs.org/ ).

I-2. Army Force Generation data points

a. Force type codes ( DP 99 Force Types), force pools, and force packages (see table I-2A).

b. Missions: Contingency Plans, named operations (see table I-2B CLASSIFIED).

I-3. Commander's unit status report reason codes

a. Primary reason overall level is not C1 (see table I-3A).

b. Primary reason overall level is not C1 because of deployment of subordinate elements (Applicable to Composite Reporting Units only) (see table I-3B).

c. Reason codes for other than P1 (see table I-3C).

d. Reason codes for other than S1 (see table I-3D).

e. Reason codes for other than R1 (see table I-3E).

f. Reason codes for other than T1 (see table I-3F).

g. The CBRN equipment supply/readiness and trainings status codes (see table I-3G).

I-4. Commander's requirements and exemption codes

See table I-4.

I-5. Current status and activity codes

a. General (see table I-5A).

b. Specific (see table I-5B).

I-6. Training events and activities

See table I-6.

I-7. Deployment Indicator Codes

See table I-7.

I-8. Data element descriptions

(Table I-8)

I-9. Data labels associated with the commander's unit status report

See table I-9.

I-10. Assignment Codes for Army commands, Army service component commands, direct reporting units, Department of the Army Staff Agencies, staff support agencies, and field operating agencies

See table I-10.

I-11. Abbreviated names, unit level codes, and unit type codes

a. The ANAMES and ULCs (see table I-11A).

b. UTCs (see table 1-11B)

I-12. Unit codes for combatant commanders and major non-Army commands, separate operating agencies, Joint units that report directly to the Joint staff and for the services and agencies

a. DOD and Joint organization codes (see table I-12A).

b. Designators for services and agencies (see table I-12B).

c. Combined command codes (see table I-12C).

I-13. Country codes and State codes

a. Country codes are located in table I-13A.

b. State codes are located table I-13B.

I-14. Major Army units and headquarters

See table I-14.

I-15. Major equipment codes

a. User monitor indicator code is located in table I-15A.

b. Functional classification code is located in table I-15B.

c. capability indicator codes is located in table I-15C.

d. The LIN and cross-references are located in table I-15D.

I-16. Transactions executed by the force projection application

See table I-16.

Appendix J
Line Item Number Exemption Procedures

J-1. General

a. Definition. A LIN exemption is a highly exceptional, deliberate action taken by HQDA to exclude equipment Items designated by LIN in the currently effective authorization and requirements documents of specified reporting units from their USR S-Level calculations for a prescribed period of time.

b. Functions. The Army Readiness Division (DAMO-ODR) and the Force Management and Integration Division (DAMO-FMF) share responsibility for managing the Army's LIN exemption program. The DAMO-FMF manages the process governing the request, coordination and approval of LIN exemptions, and DAMO-ODR manages the process for implementing approved LIN exemptions in the CUSR. The Director of Force Management is the HQDA approving authority for all LIN exemptions; however, all LIN exemption actions must be staffed with DAMO-ODR before approval, except LINs exempted for obsolescence in accordance with the provisions of paragraph 6-5 . The policy and procedures for LIN exemptions are established and explained in this appendix, in paragraph 6-4 of this publication and in AR 220-1 , paragraph 9-3. If required and appropriate, DAMO-ODR and DAMO-FMF will develop a MOA/memorandum of understanding to clarify or supplement these policies and procedures.

J-2. Basic business rules

a. Line item number exemption requests. The LIN exemption requests can be submitted to HQDA by ACOMs, ASCCs, DRUs, and DARNG/NGB on behalf of the reporting units under their purview, or they can be requested by organizations and agencies at HQDA-level. Reporting units may initiate LIN exemption requests; however, they must process their requests through their chains of command to the responsible ACOM, ASCC, DRU or DARNG/NGB for endorsement and submission to HQDA. Figure 6-1 depicts the process for requesting LIN exemptions.

b. Line item number exemption criteria. The LIN exemptions are interim actions taken by HQDA until equipment documentation issues can be corrected or resolved and/or to synchronize equipment distribution programs with unit status reporting processes. The LINs may be approved by HQDA for exemption for either one of the following two reasons:

(1) Because the LINs represent equipment items on the unit's MTOE/TDA that are obsolete or currently unnecessary for the unit to accomplish its core functions or designed capabilities or that were documented erroneously or prematurely.

(2) Because the LINs represent equipment items on the unit's MTOE/TDA that were included on the document based on equipment availability and distribution projections, assumptions and timelines that are under adjustment or revision.

c. Line item number exemption types. As the approving authority for LIN exemptions, the Director of Force Management can approve two types of LIN exemptions a "total LIN exemption" and a "conditional LIN exemption." Total LIN exemptions are approved actions that will result in the exclusion of all of the equipment items represented by the exempted LIN from the unit's USR S-Level calculations, regardless of the quantity of equipment items that is currently on hand in the unit. Conditional LIN exemptions are approved actions that will result in the exclusion of all of the equipment items represented by the exempted LIN from the unit's USR calculations only if the quantity of items that currently is on hand in the unit is at the S4 level (that is, the current on hand quantity is less than 65 percent of the quantity required by the unit's MTOE/TDA). If a unit has sufficient equipment to report S1, S2, or S3 for a conditionally exempt LIN, then it will include this S-Level measurement when calculating the unit' s S-Level.

d. Line item number exemption procedures.

(1) The Director of Force Management will specify in a formal memorandum the units whose S-Level calculations will be impacted by the LIN exemptions he approves. All LIN exemptions will be specified by UIC and by ERC, and the time period that the LIN exemption will be effective also will be prescribed in this memorandum.

(2) Approved LIN exemptions will be effective beginning on the first day of the month specified in the LIN exemption memorandum, and they will be implemented during the monthly USR cycle for that month. Data for approved LIN exemptions must be posted to the official LIN exemption table in the USAFMSA database NLT the 15 th day of the of the month prior to the monthly USR cycle during which the LIN exemptions will be implemented (for example, NLT 15 MAR for LIN exemptions that begin 1 APR). The USAFMSA database will enforce this business rule and will reject any new or modified LIN exemptions that are non compliant. (Note that the start date for any extensions of current LIN exemptions also must comply with the above business rules).

(3) The process to implement approved LIN exemptions will be fully automated, and DAMO-ODR will accomplish daily updates to the DRRS-Army database based on the official LIN exemption table in the USAFMS