1. Unit Level Information Brief
Defense Readiness Reporting System - Army
Unit Level Information Brief
As of 12 May 2006

2. Current system vs. future system Task assessment methodology
Agenda
Why DRRS-A for the Army
DRRS-A features
Current system vs. future system
Task assessment methodology
Net USR Demonstration
The Army will implement DRRS-A in an effort to update our legacy readiness reporting systems and processes. Our legacy system was shaped during the cold war period.
DRRS-A will provide the Army two major improvements:
First, it allows better readiness reporting for the high OPTEMPO conditions inherent with the GWOT. As the Army moves to ARFORGEN construct for preparing units for deployments, DRRS-A will support this process.
Secondly, the Army will be able to retire it’s DOS based PC reporting system and move to a WEB based architecture.

3. Why the Army is Moving to DRRS-A
OSD has mandated that the Service move toward a single Readiness reporting system – Defense Readiness Reporting System (DRRS).
Our legacy systems were shaped during the cold war period, when the Army resourced and tracked readiness of units based on concept of “first to fight, first to resource”.
The new readiness reporting system provides the Army two major improvements
First it will allow better readiness reporting for the high OPTEMO conditions inherent with GWOT. As the Army moves to ARFORGEN construct for preparing units for deployments, DRRS-A will support this process.
Secondly, the Army will be able to retire it’s DOS based PC reporting system and move to a WEB based architecture.
The Army will implement DRRS-A in an effort to update our legacy readiness reporting systems and processes. Our legacy system was shaped during the cold war period.
DRRS-A will provide the Army two major improvements:
First, it allows better readiness reporting for the high OPTEMPO conditions inherent with the GWOT. As the Army moves to ARFORGEN construct for preparing units for deployments, DRRS-A will support this process.
Secondly, the Army will be able to retire it’s DOS based PC reporting system and move to a WEB based architecture.

4. Like the USR it remains the “Commander’s report”.
DRRS-A Features
Like the USR it remains the “Commander’s report”.
Data is validated by the chain of command and quality-controlled by the Army institutional processes.
Transforms the Army’s “business processes” and mindset for assessing and reporting readiness.
Looks like the familiar USR, but with enhanced features.
Maintains GCCS-J/GSORTS and JOPES compatibility and interoperability.
Fulfills the Army’s command and control data requirements, supporting pay, personnel, training support, and others.
Protects sensitive and classified readiness information across the Army.
Supports current and future Army and DoD systems and requirements (such as ARFORGEN).

5. Unit Status Report What Army users see now
This is what our current readiness report looks like, as you can see, a DOS- based application.

6. DRRS-A NETUSR What Army users can expect soon
This is what our readiness reports will look like under DRRS-A, a web-enabled input system that looks very similar to most web pages you see today.

7. DRRS-A Task Assessment Methodology
Sufficient resources (i.e., personnel & equipment) required to successfully accomplish the task are available or specifically identified (APS, LBE, TPE)?
Task is assessed by unit commander as TRAINED? Y Y
YES
N (with risk mitigation) N N
QUALIFIED
YES
(Reason code and comments required)
Sufficient resources (i.e., personnel & equipment) required to successfully accomplish the task are available or specifically identified (APS, LBE, TPE)?
Task is assessed by unit commander as NEEDS PRACTICE? Y Y N N NO
(Reason code and comments required)
Task is assessed by unit commander as UNTRAINED ? Y

8. DRRS-A Overall Assessment Methodology
The majority of supporting METs are assessed as “Y” and No MET is assessed as “N” Y
YES N
QUALIFIED
YES
(Reason code and comments required) Y
The majority of supporting METs are assessed as “Q” and No MET is assessed as “N” N NO
(Reason code and comments required) Y
Any MET currently assessed as N?

9. NETUSR in Development What is not part of the application yet
Development of the NetUSR application is ongoing, scheduled for completion and deployment in October. The following functionality has not yet been incorporated into NetUSR.
1. USR Report Sections - Some sections of the report are not complete or not there at all at this time.
a. Equipment Readiness Information (The Equipment Readiness page is being reworked, we are not looking for feedback on the Equipment Readiness page that exists now.)
b. Equipment On-Loan data
c. Mission Accomplishment Estimate data
d. Overall Readiness Ratings (C Level and associated data)
2. Special Report Types – the system has regular reports, no special report types are in completed yet (i.e. it does not yet support Composite, Change, Validation reports)
3. Report Validation, Review and Submission – functionality in this area has not been developed
a. Report Validation: a page that shows all errors with the USR in one place.
b. Review and approval – approving the USR when complete
c. Routing a USR – sending the USR up to the higher level chain of command
d. Export or Import of a completed USR – You can export and import the raw data used to create a USR, but not the completed USR
4. NetUSR – Standalone – The NetUSR Standalone Application has the same functionality as the Dev Net version (except for some items on the “Report Options” menu. Although the standalone application is completed, there is no automated install that would make it possible for someone in the field to install NetUSR Standalone.
The Army will implement DRRS-A in an effort to update our legacy readiness reporting systems and processes. Our legacy system was shaped during the cold war period.
DRRS-A will provide the Army two major improvements:
First, it allows better readiness reporting for the high OPTEMPO conditions inherent with the GWOT. As the Army moves to ARFORGEN construct for preparing units for deployments, DRRS-A will support this process.
Secondly, the Army will be able to retire it’s DOS based PC reporting system and move to a WEB based architecture.

10. Now that you are familiar with PC-ASORTS, the following is a brief overview of NetUSR. These slides are based on the developmental NetUSR software, and may change from what you use in October 2006.
This is the welcome screen. Read the “news” portion – this is one way we will communicate with users in the field regarding software changes and is very important.

11. Login
The Login procedure is standard. The user selects NetUSR on his browser (or enters the appropriate URL). This causes the screen shown in Figure 1 to appear. The user enters his AKO-S user ID and Password and either clicks submit or presses the enter key on his/her keyboard.
The UID and Password are validated and the user is allowed to proceed with the creation of the USR.

12. Report Options Screen
This screen provided the user with access to the various screens for the creation of a report, the viewing of a report and the export or import of data to support the NetUSR Stand Alone (NetUSR-SA) version of the software. Figure 2 shows this screen with its drop down menu activated.
The screen also has other information: Unit Identification Code (UIC) and Reports available.
Clicking on the View USR button invokes the report selected from the Available reports.
Clicking on the Create Report Menu Bar (Figure 3 below) invokes the Create Report Screen (Figure 4 below).

13. Create Report
The create report process is straight forward. The user steps through each tab of the menu (Basic Unit Information, Equipment, Personnel, Training, and finally Overall. Each tab menu selections the user must view and fill in if required. It is recommended that the tab be worked from left to right.
The data for many of the screens will be pre-populated with data from Systems of Record databases. This will allow the user to concentrate on the data relationships as opposed to spending the majority of the time on just entering the data into the report.
The sections below will provide information on each tab and menu involved in the creation of the USR.

14. Create Report Screen
The Create Report screen displays several pieces of information. The user must select the unit for which the USR is to be generated (usually only one to select), the time period for which the report is to be generated (from a drop down) and the MTOE (effective date selection) which is to serve as the units report template (if multiple MTOE are available).
Once the Unit, MTOE and Report Period are selected, the Create USR button is clicked. After this button is clicked, the tabs for Basic Unit Information, Equipment and Personnel are active. The user should now clink on the BUI tab.

15. Basic Unit Information Screen
Clicking on the Basic Unit Information tab causes the BUI Screen (Figure 5 below) to be created and displayed. This screen displays information about the unit creating the USR. Some of this information is editable by the user. Table 1 shows these data items.
Under usual conditions these editable entries will not require modification. If the Unit Commander has changed or the Unit Point of Contact has changed, these data should be updated.

17. Subordinate Unit Relationships Screen
After the BUI information has been reviewed and validated the user should move to the Subordinate unit screen to determine if all sub-units are accounted for. To do this, mouse over the Unit Information tab and then select Subordinate Unit Relations menu bar. This will move the user to the Subordinate Unit Relationships Screen ( Figure 6 ). If all units are account for, the user should proceed to the Equipment tab. Otherwise the user should add or delete the units in question.
To delete a unit simply click on the and then click save. To add a unit, click on the add button on the lower left of the screen. This will invoke the add unit dialog screen (Figure 7).
The user must enter the UIC, the Unit name and the status. The status is selected from the dropdown Figure 8. The remarks section allows the user to enter any comment appropriate to the unit. Once the information is entered, click on the submit button. A filled in example is shown at Figure 9.
This process is repeated until all units are accounted for. Once all units are accounted for, the user should proceed to the Equipment tab of the main screen.

18. This is where you would add a subordinate unit, if applicable.

19. This is where you would select the status of the added unit to show the command relationship, options are:
Organic
OPCON and available
OPCON but NOT considered
Detached

20. This shows where to enter remarks for the added unit.

21. Equipment
The equipment pages of NetUSR are used to review and validate the data as it is pre-populated.
Equipment on Hand
The Equipment-on-Hand display screens are shown below. These screens reflect the MTOE Authorized and Required numbers for each LIN listed on the MTOE. This information is collected by accessing WebTAADS and down loading the appropriate MTOE data for the unit selected on the Report Options Page (Figure 2 above). Figure 10 below shows the detail page of the EOH screen with individual LIN shown.
For each LIN the Required and Authorized amounts from the MTOE (drawn from webTAADS), the On-Hand amount as indicated by the Logistical Database (PBUSE at this time, LIW in the near future), the Total from the Detail section, the Number as reported by the Commander and finally the S rating for the LIN are shown. At the top of the page is the overall computed S-level of the unit.
The reported as per Commander and LIN S-level are editable by the user. The remarks button ( ) opens a pop-up allowing a comment to be entered for the LIN (See Figure 11)

22. After making any modifications to the editable, user selectable or the remarks page, the user may examine the detail portion of the information. To do this, click on the DESCRIPTION of the LIN. This invokes the Equipment on Hand Detail page.
The Detail page is shown in Figure 12. The detail page provides information on the specific LIN selected. It shows how the quantity of the LIN available was determined. The Authorized Substitutes, the “In Lieu of” substitutions and other items used to arrive at the Quantity on Hand are shown in the section Actuals Satisfying Required LIN.
This page is also used to add substitute items for the specified LIN. It allows the user to search the available LINs to determine if any are suitable fill-ins for the subject LIN.
The user editable/selectable values on the Equipment on Hand Detail page are shown in Table 3

23. Shows the user how to edit remarks.

24. Equipment Readiness
Equipment Readiness is determined only for those items of equipment that are on hand. The Equipment Readiness page is shown in Figure 14. The data populating this page is all drawn from databases and is not editable at the current time. (This page is being modified in the next release of the software.)

25. Equipment Shortage Ranking Page
This page is invoked when there are equipment shortages that impact on the overall EoH level (the S-level rating). The ranking reflect the commander’s assessment of order the item should be obtained to raise the S rating. Figure 15 shows the Equipment Shortage Page without ranking.
The Ranking is the only item editable on this page. The user may enter any value they choose or they may click on the button to automatically enter the next available sequence number. Figure 16 shows the Shortage Ranking Page with enumeration.
When the user has completed this section of the USR, they should save their updates then move to the Personnel tab.

26. Personnel
The personnel portion of NetUSR falls into four sections. The sections provide the means to review and validate data from System of Record databases. The commander is able to review the data and make the necessary annotation via remarks etc. The user should examine the Personnel strength page first, followed by the Personnel Strength by Grade, then the Shortage Rankings and finally the Non-Available Reasons.
This provides a smooth transition from one area to another. The next four sections discuss the use of each section in detail.

27. Personnel Strength Page
The personnel Strength page (Figure 17) provides a list by Grade and position of the MTOE positions as shown in the selected MTOE below. . Certain values are editable by the user and are shown in Table 4.
Editable values on Personnel Strength Page
The MOS/Position that preceded by an * has a shortfall, i.e. Avail ≤ Assgn. If a position has a shortfall, a reason code must be provided for each. The exact procedure for this will be discussed below. If, to the commander’s knowledge, the Avail number is incorrect, he may change it. For example in Figure 17 position 42A10 has a shortfall. If the commander knows that there is not a shortfall, he may adjust the Avail number to the correct amount, in this case by adding one. When he clicks the save button, the * will disappear, indicating no shortfall is now present. The commander should go through the complete list to ensure an accurate accounting of all positions and personnel. When finished, the commander can quickly review by going to the Personnel by Grade page.

28. The personnel Roll-Up by Grade page (Figure 18) provides a total list by Grade of the MTOE positions as shown in the selected MTOE below.

29. Personnel Shortage Ranking
Personnel Shortage Ranking provides the relative ranking of the missing MOS/Position to the unit commander.
Figure 19 shows the ranking page. The ranks are assigned by clicking the NEXT button on the position considered to be the next most important. This places the next available ranking number on the position. If the user desires, the ranking numbers may be entered by typing them in directly.

30. Personnel Non-Available Reasons
Each person not available for duty must be accounted for by a Non-Available Reason code. There may be a 1-to-1 correspondence to the reasons codes or there may be a many person to 1 correspondence. For example assume there are 6 people mission from a particular position. Four may be out due to being AWOL, one is out because of illness and one is sole surviving child. This accounts for all six. Similarly, each could have a different reason for being unavailable. The process allows for this. Figure 20 shows the page for non-available reason assignment.
To associate a reason code the following process is used. Click on the Add Reason button. This will add a line to the reasons display containing a dropdown letting the user select any reason code contained therein. The user clicks on the code and it is entered. To remove a code incorrectly assigned, simply click on the X

31. The manage METL data entry page is shown at Figure 21
The manage METL data entry page is shown at Figure 21. This page allows the user to either select the METL from standard sources (AUTL, MTP, or KFTL ) or enter their own, based on the standard reference numbers.
The user selects the source of the MET (from the dropdown), scans or scrolls down the list and selects the MET wanted and then clicks on the add METL button. The item selected is placed in the Mission Essential Task List window of the screen. The user now selects the appropriate values from each dropdown (see Table 5). After the selection are made the user may click the save button. This action will save the data to the database and then return the user to the METL Management screen. The user continues until all MET are entered into the METL. Each MET should have the appropriate selections made for each check box and dropdown.

32. This page is used to establish the squads with the unit and to provide information on them. The squads may be selected from the dropdown or they may be created by the user. The data associated with each squad are shown in Table 6.
The user either selects a squad type from the dropdown or enters the type himself. Once this is done, the user clicks on the add Squad button. Once the button is clicked the selected (or defined) squad is placed in the Manage Squads window. The user then must enter the data indicated in Table 6.
Once the data is entered, the save button should be clicked. This places the data into the local database. The sum of the Fully Manned and Minimally manned data items (shaded green) must not exceed the Auth Reportable value (shaded blue). If it does the Auth Reportable value is flagged red and the data are not allowed to be saved until the summation is correct.

33. The Overall rating page deals with the rating of each measured area (Personnel, EoH, Equipment Readiness and Training) and the C-level rating of the unit. The C rating is the minimum of the rated areas. This page allows the rating of each rated area to be modified by the unit commander, unless the rating is a 5. If this is the case, the rating cannot be changed. As the ratings are changed the unit C level is adjusted to match the modified rating. This process is discussed in section
The same type of information is show in the NBC Recap. It is limited to the NBC equipment present in the unit. This is discussed in

34. The Recap Measured Areas provides a summary of the data reported on/in the data entry pages of Equipment, Personnel and Training. The rating for each section is shown, and the unit commander is allowed to adjust the values within specific values as outlined in AR
This adjustment is made by clicking on the dropdown arrow for each rating. The rating may be changed to any value the user wants unless the value is a computed 5. If it is, then the rating may not be changed. Looking at Figure 24 we see there are four places where this may be applied.
There is also another item that must be filled in if the rating is not 1. There is a dropdown for each rated area. The user must select one reason. There are also remarks that must/may be filled in as directed by AR These have to do with the various ratings for the equipment, the personnel and training. These remarks are mandatory if the rating is changed.
The items with a may have a remark entered. Again there are times when the remark is required. These are specified in AR Table 7 provides a list of the user editable items on the Recap page. All of the items allow for a remark to be made. Some items will require remarks. Required remarks are determined by AR rules and will be enforced by the software.

35. This recap page provides a list of the selected NBC equipment and the rating generated by the computations specified in AR Figure 25 shows the page as it is currently configured.
The NBC Equipment on Hand Summary is based on the items checked on the Equipment on Hand data page. The information on this page is not editable by the user. The only way to add or deleted from this summary is to check or un-check the equipment item on the Equipment on Hand page.

36. The to do list is a feature of NetUSR that allows the user to view a list of items that need to be completed before the USR may be submitted. Figure 27 show a To Do list. It has two entries, one for personnel and one for equipment. The item to be completed for personnel, in this example is unexplained shortages. The user would click on the indicated link, correct the problem and then return to this page (either by using the back page feature of clicking on the todo list menu bar from the Overall tab).
The same procedure would be used to fix the equipment item.
The items may be filterable by three sets of categories:
Type Severity Page

37. Stand Alone Desktop Application Process1 2
Enters AKO ID & password
At Net USR website
Create
HQDA Server
NIPR (Low Side)
.mil or .gov domain 3
Create Data Disk 4
Data
Import
Data Disk
Import data (disks)
Create USR report
Export completed USR report
Import Data Disk 5
Data Disk
//SECRET// 6
Export
Log on to Net USR website
Enter AKO ID & password
Data is retrieved for AKO ID & UIC
Create data disk for import
Import data disk onto CLASSIFIED stand-alone system
Export CLASSIFIED report for submission
Submit to higher HQ or installation USR officer for
submission via SIRPNET
Note:
No change to current entry process for readiness reporting
Installation USR Officer or
Higher HQ

38. Questions / Assistance
A help desk with a number will be established to provide users with assistance
For interim assistance, please contact
MAJ Vince Bailey at DSN 224 or
MAJ Jim Oakes at DSN 227 or
MAJ Keith George at DSN 222 or
MAJ Thomas Burke at DSN 223 or
Mr. James Forbes at DSN 227 or