Defense Readiness
Reporting System - Army
Unit Level Information Brief
1
As of 12 May 2006
Agenda
Why DRRS-A for the Army
DRRS-A features
Current system vs. future system
Task assessment methodology
Net USR Demonstration
2
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.
3
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).
4
Unit Status Report
What Army users see now
5
DRRS-A NETUSR
What Army users can expect soon
1
6
DRRS-A Task Assessment Methodology
Task is assessed by
unit commander as
TRAINED?
Y
Sufficient resources (i.e.,
personnel & equipment)
required to successfully
accomplish the task are
available or specifically
identified (APS, LBE, TPE)?
Y
N (with risk mitigation)
N
Task is assessed by
unit commander as
NEEDS PRACTICE?
N
Y
N
Task is assessed by
unit commander as
UNTRAINED ?
YES
Sufficient resources (i.e.,
personnel & equipment)
required to successfully
accomplish the task are
available or specifically
identified (APS, LBE, TPE)?
QUALIFIED
YES
Y
(Reason code and
comments required)
N
NO
Y
(Reason code and
comments required)
7
DRRS-A Overall Assessment Methodology
The majority of supporting
METs are assessed as “Y” and
No MET is assessed as “N”
Y
YES
N
Y
The majority of supporting
METs are assessed as “Q” and
No MET is assessed as “N”
QUALIFIED
YES
(Reason code and
comments required)
N
Y
Any MET currently assessed as N?
NO
(Reason code and
comments required)
8
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.
9
10
25
26
27
28
29
30
31
32
33
34
35
36
Stand Alone Desktop Application Process
1
2
Enters AKO ID & password
At Net USR website
HQDA
Server
NIPR (Low Side)
.mil or .gov domain
Create
Data Disk
3
4
Data
Data Disk
Import
Data Disk
Import data (disks)
5
Data Disk
Create USR
report
//SECRET//
Export
6
Installation USR Officer or
Higher HQ
Export completed USR
report
1.
2.
3.
4.
5.
6.
7.
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
37
Questions / Assistance
A help desk with a 1-800 number will be established to provide users with assistance
For interim assistance, please contact
MAJ Vince Bailey at 703-614-4871 DSN 224 or vincent.bailey@hqda-aoc.army.pentagon.mil
MAJ Jim Oakes at 703-697-1718 DSN 227 or james.oakes@hqda-aoc.army.pentagon.mil
MAJ Keith George at 703-692-5825 DSN 222 or keith.george@hqda-aoc.army.pentagon.mil
MAJ Thomas Burke at 703-693-9438 DSN 223 or thomas.burke@hqda-aoc.army.pentagon.mil
Mr. James Forbes at 703-697-1012 DSN 227 or james.forbes@hqda-aoc.army.pentagon.mil
38