Defense Readiness Reporting System Army

1
Defense Readiness Reporting System - Army
Unit Level Information Brief
As of 12 May 2006
2
Agenda
Why DRRS-A for the Army DRRS-A features Current
system vs. future system Task assessment
methodology Net USR Demonstration
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 its
  DOS based PC reporting system and move to a WEB
  based architecture.

4
DRRS-A Features

• Like the USR it remains the Commanders report.
• Data is validated by the chain of command and
  quality-controlled by the Army institutional
  processes.
• Transforms the Armys 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 Armys 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
6
DRRS-A NETUSR What Army users can expect soon
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
Y
The majority of supporting METs are assessed as
Y and No MET is assessed as N
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.
10
(No Transcript)
11
(No Transcript)
12
(No Transcript)
13
(No Transcript)
14
(No Transcript)
15
(No Transcript)
16
(No Transcript)
17
(No Transcript)
18
(No Transcript)
19
(No Transcript)
20
(No Transcript)
21
(No Transcript)
22
(No Transcript)
23
(No Transcript)
24
(No Transcript)
25
(No Transcript)
26
(No Transcript)
27
(No Transcript)
28
(No Transcript)
29
(No Transcript)
30
(No Transcript)
31
(No Transcript)
32
(No Transcript)
33
(No Transcript)
34
(No Transcript)
35
(No Transcript)
36
(No Transcript)
37
Stand Alone Desktop Application Process
1
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 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 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_at_hqda-aoc.army.pentagon.mil MAJ
Jim Oakes at 703-697-1718 DSN 227 or
james.oakes_at_hqda-aoc.army.pentagon.mil MAJ Keith
George at 703-692-5825 DSN 222 or
keith.george_at_hqda-aoc.army.pentagon.mil MAJ
Thomas Burke at 703-693-9438 DSN 223 or
thomas.burke_at_hqda-aoc.army.pentagon.mil Mr.
James Forbes at 703-697-1012 DSN 227 or
james.forbes_at_hqda-aoc.army.pentagon.mil