PAPERWORK REDUCTION ACT
MANAGEMENT SYSTEM II
USERS MANUAL
Version 1.1
cornpex.
I CoroorationV
-------
PAPERWORK REDUCTION ACT
MANAGEMENT SYSTEM II
USERS MANUAL
Version 1.1
PREPARED FOR:
INFORMATION POLICY BRANCH
ENVIRONMENTAL PROTECTION AGENCY
401 M STREET, S.W.
WASHINGTON, D.C. 20460
PREPARED BY:
COMPEX CORPORATION
5500 CHEROKEE AVENUE, SUITE 550
ALEXANDRIA, VIRGINIA 22312
CONTRACT # 68-01-7444
DELIVERY ORDER # 6
DECEMBER 28, 1989
-------
TABLE OF CONTENTS
1.0 OVERVIEW 1
1.1 Introduction 1
1.2 Processing 1
1.2.1 SF-83 Processing 1
1.2.2 FORM 2B Processing 2
1.2.3 Form 2A Processing 2
1.2.4 ICW Processing 3
1.2.5 OMB Action Notice Processing 3
1.2.6 Tracking Event Processing 3
1.3 Reporting 4
1.4 Program Structure and Flow 4
2.0 CONVENTIONS 6
2.1 Conventions within this manual 6
2.2 Conventions within PRAMS II 7
2.1.1 The Menu Screen 7
2.2.2 Moving Through the Menus 8
2.2.3 Memo Field 8
2.2.4 Completing a Data Entry Screen 10
2.2.5 Error Messages 10
2.3 Entering the Syste 11
3.0 ADDING DATA 13
3.1 Input an Original Profile Sheet 13
3.2 Adding an SF-83 14
3.2.1 Adding an SF-83 for an ICR proposed at the
time of ICB processing 16
3.2.2 Adding an SF-83 for an ICR not previously
proposed 17
3.2.3 Adding an SF-83 as an amendment to an
existing ICR 18
3.3 Adding an Inventory Correction Worksheet (ICW) for
an ICR 19
3.4 Adding a Form 2A 20
3.5 Adding an OMB Response Form 21
3.5.1 Adding an OMB Response to an SF-83 .... 22
3.5.2 Adding an OMB Response to an ICW 23
3.6 Adding a Tracking Event 24
3.7 Displaying Tracking Events 28
4.0 EDITING DATA 31
4.1 Editing an ICR Profile (Form 2B) 31
4.2 Editing an SF-83 (an Existing Package) 31
4.3 Editing an Inventory Correction Worksheet for an
ICR 31
4.4 Editing a Form 2A 32
4.5 Editing and Deleting a Tracking Event 33
4.6 Editing an OMB Response 34
-------
TABLE OF CONTENTS
Continued
5.0 GENERATING REPORTS
5.1
5.2
5.3
5.4
5.5
5.6
5.7
35
The ICR Status Report 37
The Tickler Report 38
The Monthly Report 38
Edit Forms Reports 38
Proposed ICRs Listing 40
Tracking Event History 40
Display an ICR Summary 41
INDEX
APPENDIX A Sample Input Screens
APPENDIX B Tracking Event Codes
APPENDIX C Report Samples
APPENDIX D Database Structure
APPENDIX E Agency Names
APPENDIX F AA/Division Codes
-------
LIST OF FIGURES
Figure 1 PRAMS II Main Menu ,
Figure 2 Error Message
Figure 3 Entering a Password ,
Figure 4 ICB Management Menu ,
Figure 5 ICR MANAGEMENT MENU ,
Figure 6 Form 2A
Figure 7 Warning Message: Validation Conflict for an OMB
Response
Figure 8 Adding an OMB Response to an ICW
Figure 9 Tracking Event Menu
Figure 10 Event Codes Online Help Function
Figure 11 Tracking Event Input Screen
with Prompt for adding the Tracking Record
Figure 12 Displaying Tracking Events for a Specified
Package
Figure 13 Display All Tracking Events for a specified ICR
Figure 14 Inputs required to edit an existing ICW ....
Figure 15 Information Required to Edit or Delete an ICW .
Figure 16 Reports Menu
Figure 17 Edit Forms Options
Figure 18 Display an ICR Summary
7
11
12
13
15
20
22
24
25
26
28
29
30
32
34
35
39
40
-------
LIST OF TABLES
Table 1 Program Structure and Flow 5
Table 2 Cursor Control within a Memo Field 9
-------
PRAMS II USER MANUAL
1.0 OVERVIEW
Instructions for entering the PRAMS II system are provided in
Section 2.3.
1.1 Introduction
The Paperwork Reduction Act Management System II (PRAMS II)
was developed to assist the Information Processing Branch
(IPB) in their mission to process and track Information
Collection Requests (ICR) submitted by the Environmental
Protection Agency to the Office of Management and Budget.
The system provides full input/storage/retrieval functions
for ICR data.
PRAMS II is a PC-based database system, which is completely
menu-driven and user-friendly and is available to all staff
members of the IPB as a READ ONLY system. A single system is
designated as the System Administrator Version and only this
system should be used for input and edit of data. A security
shell, with access authorization levels, allows input and
editing of data on the System Administrator's unit, by
designated users.
1.2 Processing
PRAMS II will accept the following forms for input and
storage:
o Standard Form 83 (SF-83)
o ICR Profile Sheet for ORIGINAL Clearance (Form 2B)
o Information Collection Budget (ICB) Profile Sheet
(Form 2A)
o Inventory Collection Worksheet (ICW)
o OMB Action Notices
(responses to SF-83 or ICW submission)
Examples of these forms are provided in Appendix G.
In addition, PRAMS II accepts the input of Tracking Events to
chronicle the status of an ICR.
1.2.1 SF-83 Processing
When the first SF-83 for an ICR is entered into the system,
December 28, 1989 Ver 1.1 Page 1
-------
PRAMS II USER MANUAL
an ICR Summary record is created in the ICR database and a
Package record is created in the Package database. A 4-digit
ICR number is automatically generated and assigned to the ICR
record. This record contains the summary information for the
ICR and will be continuously updated throughout the life
cycle of a given ICR. ICR numbers are assigned sequentially
by the database. The Package record, which contains all of
the individual SF-83 data, is assigned the same ICR number as
the summary record and a Package identifier or number. The
Package number for the first SF-83 will always be 01.
Additional SF-83s, input into the system, for the same ICR
are assigned the same ICR number as the original but have a
Package number which is one greater than the previous Package
number. All previous Package (SF-83) data is retained by the
system when a subsequent SF-83 is input thereby retaining a
historical log of all SF-83 submissions for a given ICR.
The SF-83 data is available in hard copy form for review and
editing by the responsible Desk Officer. Any changes
required to the data may be input into the system using the
Package Edit function.
1.2.2 FORM 2B Processing
When the ICR Profile Sheet for ORIGINAL Clearance or Form 2B
is input into PRAMS II, an ICR Summary record is created in
the ICR database and an ICB Profile record is created in the
ICB Profile database. The next sequential ICR number is
generated and assigned to the ICR. The status of the ICR is
marked as proposed or pending to indicate that the ICR record
was created by a Form 2B, not by an SF-83. This system will
change this status to actual once an SF-83 is input.
The Form 2B data is available in hard copy form for review
and editing by the responsible Desk Officer. Any changes
required to the data may be input into the system using the
Form 2B Edit function.
1.2.3 Form 2A Processing
When the ICB Profile Sheet or Form 2A is input into PRAMS II,
an ICB Profile record is created in the ICB Profile database.
The ICR Profile record is assigned to the ICR that is input
by the user at the system prompt. The system will verify if
an ICB Profile already exists. If this is the case, the Edit
Form 2A function must be used to input any new data. This
function will overwrite any existing ICB Profile data for the
given ICR number.
December 28, 1989 Ver l.l Page 2
-------
PRAMS II USER MANUAL
Version l.X of PRAMS II does not provide a means of
generating a hard copy output for this form. However, by
pressing the print screen key, the user may receive, in hard
copy format, the data as it appears on the screen.
1.2.4 ICW Processing
When an ICW is input into PRAMS II, an ICW record is created
in the ICW database. The ICW record is assigned the ICR
number that is input by the user at the system prompt. Each
ICW entered for a given ICR is uniquely identified by the
effective date of the ICW as input during data entry.
The ICW data is available in hard copy form for review and
editing by the responsible Desk Officer. Any changes
required to the data may be input into the system using the
ICW Edit function.
1.2.5 OMB Action Notice Processing
An OMB Action Notice may be in response to either an SF-83 or
an ICW submission. The system will prompt for the type of
form (i.e., Package or ICW).
The system will retrieve the record containing the requested
data and store the response data in separate fields of the
corresponding record. This will allow retention of both
requested and OMB approved data. The OMB Action data is also
posted to the ICR summary record for the given ICR number to
maintain a current status of approved burden hours,
responses, adjustments, program changes, and expiration date.
The old inventory totals in the ICR Summary record are
replaced with the new OMB-approved totals while the 0MB-
approved adjustments and program changes are added to the
existing ICR Summary totals for the same.
Version l.X of PRAMS II does not provide a means of
generating a hard copy output for this form. However, by
pressing the print screen key, the user may receive, in hard
copy format, the data as it appears on the screen.
1.2.6 Tracking Event Processing
Each Tracking Event entered into the systems creates a new
record in the Tracking database. A Tracking Event may be
related to a Package (SF-83) or to an ICW. The system will
prompt for the type of relationship to establish. In the
case of a Package Tracking Event, the associated record is
identified by the ICR number with the Package extension
(e.g., for the second SF-83 submitted for ICR number 1234,
December 28, 1989 Ver 1.1 Page 3
-------
PRAMS II USER MANUAL
the identifier would be 1234.02). For an ICW Tracking Event,
the identifier would be the 4-digit ICR number and the
effective date of the Tracking Event.
A hard copy of an individual Tracking Event record is not
available on Version l.X of PRAMS II. However, a complete
listing of all Tracking Events for a given ICR number is
available from the Tracking Events History selection on the
Reports menu.
1.3 Reporting
PRAMS II provides a number of predefined report formats.
Details of the report processes are located in the Generating
Reports section of this document. Sample reports are also
included in Appendix C.
1.4 Program Structure and Flow
PRAMS II was designed and developed with a structured
approach using top-down design and modular construction.
The basic functions of the system can be categorized as the
following:
o Add data
o Edit data
o Report Data
These functions are grouped on the menu structure by the
associated data type (ICR, Tracking Event, or ICB). Add or
edit operations relating to a given data type may be found on
the same menu. All reports for all data types are contained
on the Report menu.
The operational flow of PRAMS II is determined by the menu
items selected by the user. Navigation through the system
follows the branches of the menu tree shown on the following
page. It is not possible to move laterally among menu
branches without first moving up to the root level.
The database structures are provided in Appendix D.
December 28, 1989 Ver 1.1 Page 4
-------
PRAMS II
USER MANUAL
MAIN MENU
II 1 1 ' 1 '
|ICR MGT| | TRACKING | |ICB MGT| | REPORTS | |SYS ADMIN |
1 1 1
Add/Edit
SF-83
ICW
OMB Resp
Add/Edit Add/Edit
Events Form 2A
Generate
ICR Status
Tickler
Monthly
Edit Form
Event Hist
Pending
Display
Summary
|
Add/Edit
Users
Tables
Archive
Export
Restore
Table 1
Program Structure and Flow
December 28, 1989 Ver 1.1
Page 5
-------
PRAMS II USER MANUAL
2.0 CONVENTIONS
2.1 Conventions within this manual
Certain conventions are used throughout this manual to
indicate specific aspects of using the PRAMS II database.
User-required keystrokes are indicated by the use of angle
brackets (< >). Thus, indicates that the user is to
press the enter key (or return key on some keyboards), and
indicates that the user should press the "Y" key in order
to continue. When an entry requires typing a response,
instead of pressing a single key or two-key combination, the
examples in this manual will be shown in quotation marks.
For example, the instructions:
Type "prams2"
indicates that the user is to type "prams2" and then press
the enter key. Note: The user does not type the quotation
marks.
The term "screen" is used to refer to what the user will see
on the computer monitor. This is different than a "form",
which signifies the physical piece of paper from which data
is entered into the database. A form is the SF-83, Form 2B,
ICW, etc. The screen is the electronic representation of
these forms within the PRAMS II database.
A memo field is an area within a data entry screen in which
the user can enter a large block of free form text. This is
where the comments, abstracts and titles are entered. This
area is different than a data entry field. A data entry
field has a pre-determined number of spaces and, in many
instances, is limited to either numeric or alphanumeric
characters. A memo field, on the other hand, has none of
these limitations.
An ICR number refers to the four-digit number assigned by the
computer referencing a specific ICR. An ICR package number
refers to an ICR with its two-digit package extension. The
two are distinguished within the system by the prompts used.
When an ICR number is to be entered, the screen displays
square brackets ([ ]); for an ICR package number, the square
brackets have the period in place, indicating the need for
the two-digit extension ([ . ]).
December 28, 1989 Ver 1.1 Page 6
-------
PRAMS II
USER MANUAL
2.2 Conventions within PRAMS II
The PRAMS II database is menu driven: the user does not have
to know a computer programming language or memorize difficult
procedures in order to access the data and utilize the
features of the system. All options are provided by
selecting items from the various menus and responding to
prompts as they appear.
2.1.1 The Menu Screen
There are three parts to each menu screen:
1. The header
2. The menu
3. The message area
The header is the top portion of the screen where the current
screen number, the system name and the system version number
are displayed.
Screen 1.0
PAPERWORK REDUCTION ACT
MANAGEMENT SYSTEM II
Ver. 1.0
** MAIN MENU **
1 ICR MANAGEMENT
2 TRACKING EVENTS
3 ICB MANAGEMENT
4 RUN REPORTS
5 SYSTEM ADMINISTRATION
E EXIT PRAMS II
Functions for SF-83, Form 2B, and ICW Input/Edit/Query
Figure 1
PRAMS II Main Menu
December 28, 1989 Ver 1.1
Page 7
-------
PRAMS II USER MANUAL
The menu area is in the center of the screen and displays the
current menu options.
The message area is the lower portion of the screen. The
message in this portion of the screen changes, depending upon
the menu item which is presently selected. These messages
provide the user with information about the function that the
highlighted menu selection performs. The message area is
also where many error messages will be displayed (see the
section on Error Messages).
2.2.2 Moving Through the Menus
Moving through the menus is accomplished by highlighting the
desired selection and pressing . To highlight an
item, either (1) press the number or letter associated with
that item; or (2) use the arrow keys to move down or up the
list until the desired selection is highlighted.
Throughout the system, the user is requested to enter certain
information or respond to prompts before preceding with a
given function. Square brackets ( [ ] ) are used to indicate
where a response is required. After entering data within a
field, it is necessary to press in order to advance
to the next field.
2.2.3 Memo Fields
When entering data in the data entry screens, the system will
accept the entries given by pressing . The exception
occurs within the memo fields.
In memo fields (where abstracts, comments, and titles are
entered), can be used without terminating the editing
of that block of text. In order to complete the editing
process within these fields, the and keys are to
be pressed simultaneously. Also, when working in the memo
fields, the information entered may sometimes scroll out of
view. This is to allow the user to enter more information
into these fields than can be accommodated on the screen at
one time. To scroll forward or back within a memo field, use
the up or down arrow keys.
December 28, 1989 Ver 1.1 Page 8
-------
PRAMS II
USER MANUAL
Additional key combinations can be used within the memo
fields which are not applicable in other areas of the data
entry screens. These key combinations and their functions
are listed in Table 2.
Key Combination
Insert
Function
Pressing the key
allows text to be
entered to the right of
the cursor without
overwriting the existing
text
Delete
Backspace
Arrow Keys
Deletes the text to the
right of the cursor, one
character at a time
Deletes the text to the
left of the cursor, one
character at a time
Moves the cursor around
the memo field (up,
down, left, right)
Deletes a line of text
Exits from the memo field
without saving the text
that was entered
Saves the text entered
into the memo field and
moves to the next data
entry field.
Table 2
Cursor Control within a Memo Field
December 28, 1989 Ver 1.1
Page 9
-------
PRAMS II USER MANUAL
2.2.4 Completing a Data Entry Screen
Once all of the data within a data entry screen has been
entered, the system will beep and a prompt will appear at the
bottom of the screen. The user can respond to this prompt
and terminate the input of data in one of three ways:
D (done) will result in the data being posted to the
database; the system will return to the previous
menu;
R (review) returns to the first page of the current
input screen, allowing the user to review the data
just entered.
When reviewing the data, using the key will
advance through the screens one page at a time; the
key will take the cursor from one field to the
next ;
E (escape) returns the user to the previous menu,
without keeping the data entered.
2.2.5 Error Messages
The PRAMS II system anticipates certain typing and data entry
errors and warns the user when omissions of data have
occurred or invalid responses have been supplied. When
invalid or missing data is identified by PRAMS II, a beep
will sound and an error message will appear. If the error
occurs when supplying an ICR or ICW number, or answering a
yes or no question prior to entering a data entry screen, the
message will appear in a box in the center of the screen.
If the error occurs when the user is entering data in one of
the many data entry screens, the message which appears
following the beep will be at the bottom of the screen (in
the "message area").
A final place where the system anticipates and checks for
errors is when entering data pertaining to OMB Responses. If
invalid data is supplied, a full screen error message will
appear when the user completes the last data entry screen.
The message displayed will indicate the kind of error found
and where the error occurred (see the section, Adding an OMB
Response Form).
December 28, 1989 Ver 1.1 Page 10
-------
PRAMS II
USER MANUAL
Screen 1.1
PAPERWORK REDUCTION ACT
MANAGEMENT SYSTEM II
Ver. 1.0
** An ICR does not exist for Date 09/29/89 **
Try Again? (Y/N) [Y]
Check inputs before retrying selection
Figure 2
Error Message
2.3 Entering the System
To access the PRAMS II database:
From the DOS prompt type
"cd\allprams"
Type "setprams" to clear memory and initialize
DOS environment
Type "prams2"
to invoke the system.
The first screen will request the user's ID. Each user is
assigned an ID when given access to the PRAMS II system.
After an ID is entered by the user, the system will prompt
for a password. Passwords are used as a security device.
The password does not display on the screen when it is keyed
in; only dots will appear indicating that the keys being
pressed are accepted by the system (see Figure 3 below). A
December 28, 1989 Ver 1.1
Page 11
-------
PRAMS II
USER MANUAL
user is given three attempts at keying in the correct
password before access is denied and the login process is
aborted by the system.
Screen 0.0
PAPERWORK REDUCTION ACT
MANAGEMENT SYSTEM II
Ver. 1.0
1
Enter Password:
Figure 3
Entering a Password
December 28, 1989 Ver 1.1
Page 12
-------
PRAMS II
USER MANUAL
3.0
ADDING DATA
3.1 Input an Original Profile Sheet
The Original Profile Sheet, or Form 2B, is submitted during
the Information Collection Budget (ICB) process and indicates
to IPB that an ICR is being proposed for the next fiscal
year. Therefore, the Form 2B is usually IPB's first record
of the existence of an Information Collection Request (ICR).
When the data from a Form 2B is input, PRAMS II will assign a
new ICR number. This number will be used at all times in the
future when any activity relating to this ICR occurs.
A listing of all ICR numbers assigned and for which an SF-83
has not been filed is available from the Reports Menu (see
Section D, Generating Reports)
Screen 1.3
PAPERWORK REDUCTION ACT
MANAGEMENT SYSTEM II
Ver. 1.0
** ICB MGT MENU **
1 INPUT ORIGINAL PROFILE SHEET (FORM 2B)
2 EDIT ORIGINAL PROFILE SHEET (FORM 2B)
3 INPUT ICB PROFILE SHEET (FORM 2A)
4 EDIT ICB PROFILE SHEET (FORM 2A)
R RETURN TO MAIN MENU
Input data from an ICR Profile Sheet (Form 2B) for ORIGINAL Clearance
Figure 4
ICB Management Menu
December 28, 1989 Ver 1.1
Page 13
-------
PRAMS II USER MANUAL
Steps
1. From the PRAMS II MAIN MENU, select ICB MANAGEMENT.
2. Select INPUT ORIGINAL PROFILE SHEET (FORM 2B) from
the ICB MGT MENU.
3. Enter the data from the Form 2B.
4. When finished, select if done, to review
the inputs, or to escape without saving the
inputs.
3.2 Adding an 8F-83
There are three instances when an SF-83 may be added to PRAMS
II:
1. When the SF-83 relates to an ICR proposed at the
time of ICB processing (the original SF-83).
2. When the SF-83 is for an ICR not previously
proposed.
3. When the SF-83 is filed as an amendment to an
existing ICR.
The steps for processing the three different instances are
outlined below.
December 28, 1989 Ver 1.1 Page 14
-------
PRAMS II
USER MANUAL
Screen 1.1 PAPERWORK REDUCTION ACT Ver. 1.0
MANAGEMENT SYSTEM II
** ICR MGT MENU **
1
2
3
4
5
6
R
CREATE NEW ICR
CREATE NEW PACKAGE
EDIT EXISTING PACKAGE
CREATE NEW ICW
EDIT EXISTING ICW
INPUT AN OMB RESPONSE
RETURN TO MAIN MENU
•••^^^^^•••••1
Input the first
SF-83 or Original ICR Profile (Form 2B)
Figure 5
ICR MANAGEMENT MENU
Each SF-83 is referred to as a package of information about a
particular ICR. The package number (assigned by the computer
when the SF-83 is entered) is a two-digit number added as an
extension to the ICR number. The package number serves to
identify all of the information from a specific SF-83, and
keeps this information separate from any other modified (or
conflicting) information entered about the ICR.
A package is created (1) with the original SF-83 or (2) with
additional SF-83's filed as amendments to the ICR. A package
is not created when the Form 2B is entered. Thus, when the
original SF-83 is to be entered, the function CREATE NEW ICR
(from the ICR MGT MENU) is utilized, and not the CREATE NEW
PACKAGE function (see steps below). The CREATE NEW PACKAGE
function is used only when the SF-83 is filed as an
amendment.
Appendix A provides the input screens for the SF-83 data
entry process.
December 28, 1989 Ver 1.1
Page 15
-------
PRAMS II USER MANUAL
3.2.1 Adding an SF-83 for an ICR proposed at the time of
ICB processing
Steps
1. Select ICR MANAGEMENT from the MAIN MENU.
2. Select CREATE NEW ICR from the ICR MGT MENU.
3. At the prompt, "Do you have an ICR number for this
SF-83? (Y/N)" type .
4. Enter the ICR number.
5. The data entry screen will be presented. Enter the
data from the SF-83.
6. When finished, type to save the data, to
review the inputs or to escape without saving
the inputs made.
7. After pressing , the option to add comments to
the ICR Summary is provided.
Press to display the comments entered with the
Form 2B. These comments may be edited; press
when completed.
Pressing will by-pass the comments and advance
to the next step.
8. Following the option to change the ICR Summary
Comments, the data entry screen for package
Tracking Events is displayed.
Note that tracking code "II" is automatically
placed in the Event Code field. Because this is
the first SF-83 being entered, the Tracking Event
being created is given the code "II" ("Initial
IPB").
After completing the Tracking Event entry form, the
user is provided the option of saving the data
(press at the prompt) or exiting without saving
the Tracking Event (press ) NOTE: pressing
at this point will not effect data entered for the
SF-83 and/or changes made to the comments; only the
Tracking Event data will not be saved.
December 28, 1989 Ver 1.1 Page 16
-------
PRAMS II USER MANUAL
3.2.2 Adding an SF-83 for an ICR not previously proposed
Steps
1. Select ICR MANAGEMENT from the MAIN MENU.
2. Select CREATE NEW ICR from the ICR MGT MENU.
3. When prompted, "Do you have an ICR number for this
SF-83? (Y/N)", type .
4. The data entry screen will be presented. Note that
a new ICR number has been assigned by the system.
Enter the data from the SF-83 to the database.
5. When finished, type to save the data, to
review the inputs or to escape without saving
the inputs made.
6. After pressing , the option to add comments to
the ICR Summary is given.
Press to display the comments field. Because a
2B was not filed for this ICR, the comments field
will be blank; press when completed.
Pressing will by-pass the comments and advance
to the next step.
7. Following the option to change the ICR Summary
Comments, the data entry screen for package
Tracking Events is displayed.
Note that tracking code "II" is automatically
placed in the Event Code field. Because this is
the first SF-83 being entered, the Tracking Event
being created is given the code "II" ("Initial
IPB").
After completing the Tracking Event entry form, the
user is provided the option of saving the data
(press at the prompt) or exiting without saving
the Tracking Event (press ). NOTE: pressing
at this point will not effect data entered for the
SF-83 and/or changes made to the comments; only the
Tracking Event data will not be saved.
December 28, 1989 Ver 1.1 Page 17
-------
PRAMS II USER MANUAL
3.2.3 Adding an SF-83 as an amendment to an existing ICR
Steps
1. Select ICR MANAGEMENT from the MAIN MENU.
2. Select CREATE NEW PACKAGE from the ICR MGT MENU.
3. Enter the ICR number.
The system will check for this ICR number. If the
number is not found in the system, an error message
is displayed.
The system will prompt the user for another ICR
number. Type to try again with another ICR
number; type to return to the previous menu.
4. Once a valid ICR number has been entered, the data
entry screen is provided. Enter the new
information from the SF-83.
5. When finished, select to save the data, to
review the inputs or to escape without saving
the inputs.
6. After pressing , the option is provided to add
comments to the ICR Summary.
Press to display the comments entered with the
Form 2B. These comments may be edited; press
when completed.
Pressing will by-pass the comments and advance
the user to the next step but will not effect the
SF-83 data entered.
7. Following the option to change the ICR Summary
Comments, the data entry screen for package
Tracking Events is displayed.
Note that tracking code "II" is automatically
placed in the Event Code field. Because this is
the first SF-83 being entered, the Tracking Event
being created is given the code "11" ("Initial
IPB").
December 28, 1989 Ver 1.1 Page 18
-------
PRAMS II USER MANUAL
After completing the Tracking Event entry form, the
user is provided the option of saving the data
(press at the prompt) or exiting without saving
the Tracking Event (press ). NOTE: pressing
at this point will not effect data entered for the
SF-83 and/or changes made to the comments; only the
Tracking Event data will not be saved.
3.3 Adding an inventory Correction worksheet (lew) for an
ICR
An ICW is submitted to correct an ICR's inventory or change
the expiration date; therefore, an ICW may only be input for
valid ICR numbers within the system.
The PRAMS II system will accept more than one ICW form for an
ICR number. Thus, it is necessary to note, at input time,
the effective date and the OMB docket number of the ICW and
to record this information on a manual list, maintained
separately from the database. This information is required
prior to retrieving the ICW for future edits and for entering
the OMB Response data. (See the section on Editing an ICW and
the section on Adding an OMB Response).
Appendix A shows the data entry screens for entering a new
ICW.
Steps
1. Select ICR MANAGEMENT from the MAIN MENU.
2. Select CREATE NEW ICW from the ICR MGT MENU.
3. Enter the valid ICR number associated with the ICW.
4. Enter the data from the ICW.
5. Add the OMB docket number and the effective date of
the ICW to the manual list of ICWs.
6. When finished, type to save the data, to
review the inputs, or to escape without saving
the inputs.
December 28, 1989 Ver 1.1 Page 19
-------
PRAMS II
USER MANUAL
3.4 Adding a Form 2A
The Form 2A is used to create an ICB Profile and the physical
existence (i.e., paper format) of a Form 2A indicates that
some processing relating to a given ICR number has already
taken place.
The PRAMS II system will only allow one Form 2A to be
associated with any given ICR number.
Screen 1.3.2
PAPERWORK REDUCTION ACT
Page 1 of 1
ICR Number: 0010 Current OMB #: 2060-0095 Expires on: 12/31/90
Title: Information Requirements for Importation of Nonconforming Vehicles
Contact: Claude Magnuson
Phone #: (202) 382-254 OMB Approved Hours:167836
FISCAL YEAR 1989
ICB original est.:
Adjustments:
Program Changes:
Total Estimate:
0]
0]
0]
0]
FISCAL YEAR 1990
Burden hours: [
Adjustments: [
Program Changes: [
Total Estimate: [
0]
0]
0]
0]
(i) Reason for adjustment or program change: (CTRL-W to exit)
(j) If this ICR should not be on 1990 budget, mark T on reason number(s)
1. [F] 2. [F] 3. [F] 4. [F] 5. [F] 6. [F]
Figure 6
Form 2A
When adding or editing a Form 2A, the top portion of the
screen will already be filled in, and cannot be edited
through the INPUT FORM 2A or EDIT FORM 2A functions. The
information contained on this portion of the 'screen was
obtained from the most recent package (SF-83) filed for this
ICR. The ICR Summary totals and Expiration Date contained in
December 28, 1989 Ver 1.1
Page 20
-------
PRAMS II USER MANUAL
the ICR Record may be modified using Item 7 on the Reports
Menu.
steps
1. Select ICB MANAGEMENT from the PRAMS II MAIN MENU.
2. Select INPUT FORM 2A from the ICB MGT MENU.
3. Enter the valid ICR number associated with the Form
2A to be entered.
4. Enter the data from the input form.
5. Type to save data, to review the data
input, or to escape without saving the inputs.
3.5 Adding an OMB Response Form
The OMB Response Form may originate from either a previously
submitted SF-83 (package) or a previously submitted ICW. A
valid ICR number will be required to access the OMB Response
function in order to enter the response to an SF-83. To
enter the OMB response to an ICW, an ICR number and the
effective date of the ICW are required.
Entering data from an OMB Response function results in an
unalterable record of the OMB Response. This information
cannot be altered, as it plays a vital role in the creation
of ICR audit trails. These audit trails provide one of the
key features of the PRAMS II systems: a means of accurately
tracking the sequence of events that occur during the life of
an ICR. Therefore, it is of utmost importance to ensure the
accuracy of the data entry that takes place with an OMB
Response.
The PRAMS II system checks the validity of the data being
entered for OMB Responses. If items on the screen do not
add-up properly, or if important information is missing, a
warning message will appear on the screen. The areas where
the validity of the entered data is questioned will be
explained in the message.
The user is given the option to return to the data entry
screen to review the inputs or to leave the data as it is and
continue. Because the OMB Response forms cannot be edited,
it is strongly recommended that the user review the inputs
whenever an warning message appears.
December 28, 1989 Ver 1.1 Page 21
-------
PRAMS II USER MANUAL
Screen 1.1.7a PAPERWORK REDUCTION ACT Page 2 of 2
OMB RESPONSE DATA - INPUT VALIDATION CONFLICT
* Response Difference *
Sun of all Adjustments & Prog Changes does NOT equal Difference.
* Reporting Hours *
Sum of all Adjustments & Prog Changes does NOT equal Difference.
* New-Old Response Status *
New Responses minus Old Inventory does NOT equal Difference.
* New-Old Reporting Hrs Status *
New Reporting Hrs minus Old Inventory does NOT equal Difference.
*** Notify Desk Officer of ERROR before posting data ***
After all data entry is complete, Select E to escape without saving.
Enter to edit data or to leave data as is and continue: C
Figure 7
Warning Message: Validation Conflict
for an OMB Response
Steps
3.5.1 Adding an OMB Response to an SF-83
1. Select ICR MANAGEMENT from the MAIN MENU.
2. Select INPUT AN OMB RESPONSE from the ICR MGT MENU.
3. At the prompt, type to indicate that the
Response is to an SF-83 submission.
4. The next screen will ask for an ICR Package number.
This should be a valid number (with the appropriate
package extension) relating to the Response which
is to be entered.
December 28,1989Ver 1.1Page 22
-------
PRAMS II USER MANUAL
5. Enter the data from the Response form.
(See Appendix A for an example of the input screens
for adding an OMB Response to an SF-83).
6. After entering the data, the user will be asked:
"Is there a condition for renewal or other
comments associated with this OMB response form?
[N]"
Respond with a or and, if applicable, add
OMB Remarks in the place provided.
7. When all of the data has been entered into the
input screen, select to review the inputs for
accuracy. It is important to remember to review the
information which was input following data entry,
because the data cannot be changed once it has been
posted.
8. Once the information that was input has been
reviewed, select to save the data or to
escape without saving the inputs.
3.5.2 Adding an OMB Response to an ICW
1. Select ICR MANAGEMENT from the MAIN MENU.
2. Select INPUT AN OMB RESPONSE from the ICR MGT MENU.
3. When prompted, type to indicated that this is
an OMB Response to an ICW.
4. The next screen will prompt for an ICR number as
well as the effective date of the ICW. This should
be a valid number relating to the Response which is
to be entered.
5. Enter the data from the Response form.
(See Appendix A for an example of the input screens
for adding an OMB Response to an SF-83).
6. When all of the data has been entered into the
input screen, select to review the inputs for
accuracy. It is important to remember to review the
information which was input following data entry,
December 28, 1989 Ver 1.1 Page 23
-------
PRAMS II
USER MANUAL
7.
because the data cannot be changed once it has been
posted.
Once the information that was input has been
reviewed, select to save the data or to
escape without saving the inputs.
Screen 1.1
PAPERWORK REDUCTION ACT
MANAGEMENT SYSTEM II
Ver. l.o
Enter the ICW Data below for the record to Update.
ICR #: [ 0]
Effective Date: [10/02/89]
Figure 8
Adding an OMB Response to an ICW
3.6 Adding a Tracking Event
Both the SF-83s and the ICWs are tracked separately for any
one ICR. Remember that each ICR can have more than one SF-83
and more than one ICW, and each of these can have several
Tracking Events. The existence of this level of detail in
the tracking of these forms is intended to facilitate
documentation by EPA to OMB of any discrepancies in responses
and reporting hours, which may occur over time, between EPA
and OMB.
December 28, 1989 Ver 1.1
Page 24
-------
PRAMS II
USER MANUAL
There are a limited number of Tracking Event codes which can
be used to indicate the kind of Tracking Event that is being
recorded. This limitation is designed to make possible the
retrieval of:
(1) a list of all ICW Tracking Events associated with a
given ICR and
(2) a list of all package Tracking Events associated
with a given ICR.
Screen 1.2
PAPERWORK REDUCTION ACT
MANAGEMENT SYSTEM II
Ver. 1.0
** TRACKING EVENT MENU **
1 ENTER PACKAGE EVENT
2 DISPLAY PACKAGE EVENTS
3 ENTER ICW EVENT
4 DISPLAY ICW EVENTS
5 DISPLAY ALL ICR EVENTS
6 EDIT A TRACKING EVENT
7 DELETE A TRACKING EVENT
R RETURN TO MAIN MENU
Input One or More Tracking Events for PACKAGE types
Figure 9
Tracking Event Menu
A complete list of all the valid event codes is available in
Appendix B. If an invalid event code is entered into the
Event Code field of the Tracking Event data entry screen, the
computer will beep and the message at the bottom of the
screen will indicate that an invalid code has been entered.
At this point a listing of the valid event codes may be
December 28, 1989 Ver 1.1
Page 25
-------
PRAMS II
USER MANUAL
viewed online, by typing a question mark () at the prompt
in the error message field.
Screen 1.2.1
PAPERWORK REDUCTION ACT
Page 1 of 1
Ent
Event Code
AD
CR
CS
DD
DI
HR
II
IO
IS
OA
OD
PO
RP
SD
WP
EX
Tracking Event Description
OMB approval date
Correction received from OMB
Correction Sent to OMB
To Division Director
Deleted by program
Hold for rule
In IPB
In OMB
Informal submission to OMB
Out of OMB - Approved
Out of OMB - Disapproved
Resubmitted by Program
Returned to Program
Signed by Director
Withdrawn by program
Extension of expiration date /received
Press any key to return to inputs.
Event Code XX in NOT a valid code - Press now for Code List
Figure 10
Event Codes online Help Function
If a duplicate Tracking Event code is entered, the system
will beep and indicate an error. The user may return to the
Tracking Event entry screen and enter another Tracking Event
code, or abort the process by pressing .
Steps
Note: The directions below apply to adding either an
December 28, 1989 Ver 1.1
Page 26
-------
PRAMS II USER MANUAL
SF-83 (package) Tracking Event or an ICW Tracking
Event.
1. Select TRACKING EVENTS from the MAIN MENU.
2. For an SF-83 Tracking Event, select ENTER PACKAGE
EVENT.
For an ICW Tracking Event, select ENTER ICW EVENT.
3. For an SF-83 Tracking Event, enter the ICR number
and the package number to identify the SF-83 being
tracked.
For an ICW Tracking Event, enter the ICR number to
identify the ICW being tracked.
4. Enter the data as prompted on the screen.
5. After entering the comments, the system will give
the user the option of adding the Tracking Event
record. Type if the information is correct and
the data is to be recorded; type if the
information is incorrect and to proceed without
saving the data entered.
6. To enter additional Tracking Events for this
package, press at the prompt; press if no
more Tracking Events are to be added for this
package.
7. When the inputs for a particular package or ICW
have been completed (and has been pressed in
response to the prompt in Step 6), the option is
given to enter Tracking Event information for
another ICR. Type to continue with the
Tracking Event information for a new ICR; type
to return to the TRACKING EVENT MENU.
December 28, 1989 Ver 1.1 Page 27
-------
PRAMS II
USER MANUAL
Screen 1.2.1
PAPERWORK REDUCTION ACT
Page 1 of 1
Do you want to add this Tracking Event record?
Enter (Y/N) Y
Input Package Tracking
Event Code:
Enter Comments below:
Event for ICR # 0010.01
1 Date: 09/28/89
(Press CTRL-W when done)
Figure 11
Tracking Event Input Screen
with Prompt for adding the Tracking Record
3.7 Displaying Tracking Events
A record of all Tracking Events for a given package or ICW
can be reviewed online. As with entering Tracking Events,
the steps for displaying the Tracking Events are similar for
either a package or an ICW.
Steps
1. Select TRACKING EVENTS from the MAIN MENU.
2. To display the Tracking Events associated with a
given package, select DISPLAY PACKAGE EVENTS.
To display the Tracking Events associated with a
given ICW, select DISPLAY ICW EVENTS.
December 28, 1989 Ver 1.1
Page 28
-------
PRAMS II
USER MANUAL
3. Enter the ICR number and the two-digit package
number to display the Tracking Events for a
particular package or use a "00" package number to
display all of the Tracking Events for a particular
ICR.
To display the Tracking Events for a given ICW,
enter the ICR number.
Screen 1.2.2
PAPERWORK REDUCTION ACT
Page 1 of 1
Tracking Events for
ICR/PACKAGE [0010.01]
CODE
II
10
OA
CR
DATE
03/17/82
04/19/82
05/27/82
11/06/84
*** TRACKING EVENT COMMENTS ***
New OMB number
*** GENERAL ICR COMMENTS ***
Figure 12
Displaying Tracking Events for a Specified Package
4. The system will display a listing of the requested
Tracking Event codes and their dates. The TRACKING
EVENT COMMENTS field on the top right part of the
screen provides the comments relating to the
Tracking Event highlighted in the column on the
left of the screen.
The GENERAL ICR COMMENTS field on the bottom right
December 28, 1989 Ver 1.1
Page 29
-------
PRAMS II
USER MANUAL
part of the screen displays the ICR Comments from
the ICR Summary (see the section on Generating
Reports).
5. To return to the previous menu, press .
Screen 1.2.2
PAPERWORK REDUCTION ACT
Page 1 of 1
ALL Tracking Events
with ICR Number [0010]
i
PKG CODE DATE ICW
1
1 1
1
1
1
2
2
1 2
2
2
1 2
3
3
II
10
OA
O'D
CR
Co
CR
II
SD
10
OA
CS
DI
II
DD
03/17/82
04/19/82
05/27/82
IT / f\£i / Q A
11/06/04
r\C. Jin / O C
05/ 1 //oD
06/18/85
07/09/85
07/22/85
07/23/85
09/06/85
09/16/85
07/09/86
05/04/87
07/23/87
N
N
N
Y
N
N
N
N
Y
N
N
N
*** TRACKING EVENT COMMENTS ***
Ext. exp. date
*** GENERAL ICR COMMENTS ***
Figure 13
Display All Tracking Events for
a specified ICR
December 28, 1989 Ver 1.1
Page 30
-------
PRAMS II USER MANUAL
4.0 EDITING DATA
4.1 Editing an ICR Profile (Form 2B)
1. From the MAIN MENU select ICB MANAGEMENT.
2. From the ICB MGT MENU select EDIT ORIGINAL PROFILE
SHEET (FORM 2B) .
3. At the prompt, enter the ICR number.
4. The original Form 2B screen will appear for the
selected ICR number. All fields can be edited.
5. When finished type to save the data; to
review the inputs; to escape the session
without saving the new inputs.
4.2 Editing an SF-83 (an Existing Package)
1. Select ICR MANAGEMENT from the MAIN MENU.
2. Select EDIT EXISTING PACKAGE from the ICR MGT MENU.
3. Enter the ICR package number to identify the SF-83.
4. Edit the data from the input form into the
database.
5. When finished, type to save the data; type
to review the data entry screens'; type to
escape without saving the data entered.
6. After pressing , the option to change the
comments from the ICR Summary is given. Type
to change the comments; type to return to the
previous menu.
4.3 Editing an Inventory Correction Worksheet for an ICR
1. Select ICR MANAGEMENT from the MAIN MENU.
2. Select EDIT EXISTING ICW from the ICR MGT MENU.
3. Enter the ICR number relating to the ICW to be
edited.
4. Enter the OMB docket number of the ICW to be
edited.
December 28,1989Ver 1.1Page 31
-------
PRAMS II USER MANUAL
5. Enter the effective date of the ICW to be edited.
Screen 1.1 PAPERWORK REDUCTION ACT Ver. 1.0
MANAGEMENT SYSTEM II
Enter the ICW Data below for the record to Edit.
ICR #: 0
OMB (Docket) ft: 0
Effective Date: 09/29/89
Edit data for an Existing Inventory Correction Worksheet
Figure 14
Inputs required to edit an existing ICW
6. Edit the data as needed.
7. When finished, type to post the data; to
review the inputs; to escape the session
without saving the new inputs.
4.4 Editing a Form 2A
Steps
December 28, 1989Ver 1.1Page 32
-------
PRAMS II USER MANUAL
1. Select ICB MANAGEMENT from the MAIN MENU.
2. Select EDIT FORM 2A from the ICB MGT MENU.
3. Enter the ICR number from the Form 2A to be edited.
4. Edit the data presented on the screen.
5. When finished, type to save the data; to
review the data; or to escape without saving
the changes.
If the system cannot find the requested Form 2A for the ICR
number entered, it is assumed that (1) an oversight has been
made earlier in not keying this form originally, or (2) the
ICR number entered was incorrect. The system will indicate
that the requested input form is not within the system and
advise that the user input the form using the INPUT FORM 2A
menu option. When prompted, type to enter another ICR
number; type to return to the INPUT FORM 2A screen where
the new Form 2A can be entered.
Recall that, as with the inputting of data to the Form 2A,
when editing this information, some items cannot be directly
edited at this screen. The fields which cannot be edited
are:
(1) ICR Number
(2) Title
(3) Contact
(4) Phone Number
(5) Current OMB Number
(6) Expires on
(7) OMB Approved Hours.
These fields are pulled from the most recent package for the
ICR. The ICR Summary totals and Expiration Date contained in
the ICR Record may be modified using Item 7 on the Reports
Menu.
4.5 Editing and Deleting a Tracking Event
Tracking Events can be edited, or deleted from PRAMS II.
Steps
1. From the MAIN MENU select TRACKING EVENTS.
December 28, 1989 Ver 1.1 Page 33
-------
PRAMS II
USER MANUAL
Select EDIT A TRACKING EVENT to edit an event;
Select DELETE A TRACKING EVENT to delete an event.
Whether editing or deleting, a prompt will appear
asking if the event to be edited/deleted is for an
ICW.
Press if for an ICW; press for a package
event (SF-83).
The user is then requested to enter the following
information:
The ICR number
The event code
The date of the tracking event.
Enter ICR #, CODE, DATE for the Tracking Event:
[0000.00]
[ ]
[09/29/89]
Figure 15
Information Required to Edit or Delete an ICW
4.6 Editing an OMB Response
Once the original data has been entered, an OMB Response
cannot be edited.
The OMB Response cannot be edited in order to preserve the
information from the Response for future audit trails, which
may be needed for a given ICR.
December 28, 1989 Ver 1.1
Page 34
-------
PRAMS II
USER MANUAL
5.0
GENERATING REPORTS
PRAMS II is designed to facilitate the generation of six
different reports, and provide on-screen review of an ICR
Summary. To access the reporting options, select REPORTS
MENU from the PRAMS II MAIN MENU.
Screen 1.4
PAPERWORK REDUCTION ACT Ver. 1.0
MANAGEMENT SYSTEM II
** REPORTS MENU **
1
2
3
4
5
6
7
R
PRINT ICR STATUS REPORT
PRINT TICKLER REPORT
PRINT MONTHLY REPORT
EDIT FORMS
LIST PROPOSED ICRs
LIST TRACKING EVENT HISTORY
DISPLAY AN ICR SUMMARY
RETURN TO MAIN MENU
1
Generate ICR STATUS report for IPB - Grouped by PO, sorted by ICR # or OMB
Figure 16
Reports Menu
Samples of the reports available from PRAMS II are provided
in Appendix C of this manual.
December 28, 1989 Ver l.l
Page 35
-------
PRAMS II
USER MANUAL
The reports currently available from the system are:
Report Description
ICR Status Report Status report of all ICRs;
grouped by Program Office,
and sorted by ICR number
or OMB number
Listing of all ICRs with
an expiration date with 9
months of the current date
A monthly report grouped
by program office
Printing of data from an
SF-83/Form 2B/ICW for Desk
Officer edits
A list of ICRs proposed at
ICB for which an SF-83 has
not yet been processed
A list of all Tracking
Events for a given ICR
number
Provides a current status
of a select ICR displaying
the total inventory for
that ICR to date; the
comments field can be
edited.
When generating a report from PRAMS II, ensure that the
computer is connected to either a dot matrix or laser printer
and that the printer is turned on and is online. The printer
paper should be properly aligned at the top of the page
before a report is sent the printer.
In addition to sending a report to a printer, each report may
be sent to a file. Utilizing this option sends the data
created through the reporting function to a disk file. The
file will be saved in a DOS ASCII file format and can be
accessed using the following DOS commands:
Tickler Report
Monthly Report
Print Edit Forms
Proposed ICR Listing
Tracking Event History
ICR Summary
December 28, 1989 Ver 1.1
Page 36
-------
PRAMS II USER MANUAL
1. To display the data on the screen, type
"type "
where is the name given the file when
saved (do not include the brackets).
2. To print the data on the default printer, type
"print "
where is the name given the file when
saved (do not include the brackets).
5.1 The ICR Status Report
The ICR Status report provides a listing detailing:
o ICR number
o OMB docket number
o ICR title
o Hours approved
o ICR expiration date
o Contact person
o Most recent package number
o Most recent status (latest Tracking Event)
The report is ordered either by ICR number or OMB docket
number, depending on the user's choice. In either case, the
report is grouped by Program Office.
Note that the hours approved are inclusive of any and all
packages which have been approved to date, although only the
MOST RECENT package number is displayed in the report.
steps
1. Select RUN REPORTS from the MAIN MENU.
2. Select ICR STATUS REPORT from the REPORTS MENU.
December 28, 1989Ver 1.1Page 37
-------
PRAMS II USER MANUAL
At the prompt, enter to indicate a report
ordered by ICR number; enter <0> to sort the report
by OMB docket number.
From the selection presented, choose the printer
type to be used.
Press to route the report to the printer; press
to route the data to a file.
5.2 The Tickler Report
Steps
1. Select RUN REPORTS from the MAIN MENU.
2. Select TICKLER REPORT from the REPORTS MENU.
3. Select the printer type.
4. Press to route the report to the printer; press
to route the data to a file.
5.3 The Monthly Report
Steps
1. Select RUN REPORTS from the MAIN MENU.
2. Select MONTHLY REPORT from the REPORTS MENU.
3. Select the printer type.
4. Press to route the report to the printer; press
to route the data to a file.
5.4 Edit Forms Reports
Any of the three EPA forms (Form 2B, SF-83, or Form 2A) which
are used during the input procedure for an ICR may be printed
out in a format similar to that of the original form.
The purpose of providing this report feature is not to
evaluate or analyze summary information, but to provide a
check on the accuracy of the data being entered into the
December 28, 1989Ver 1.1Page 38
-------
PRAMS II
USER MANUAL
system. Only a single ICR is printed with each execution of
this report.
To view all three of the edit forms provided in this menu
selection, it will be necessary to repeat the following steps
for each form desired.
Screen 1.4.4
PAPERWORK REDUCTION ACT
MANAGEMENT SYSTEM II
Ver. 1.0
** EDIT FORMS MENU **
1 PRINT SF-83
2 PRINT ICR PROFILE (FORM 2B)
3 PRINT ICW
R RETURN TO REPORTS MENU
Print an SF-83 data for a given ICR & Package number
Figure 17
Edit Forms Options
Steps
1. Select RUN REPORTS from the MAIN MENU.
2. Select PRINT EDIT FORMS from the REPORTS MENU.
3. Select the desired input form from the choices
given.
December 28, 1989 Ver 1.1
Page 39
-------
PRAMS II USER MANUAL
4. Enter the appropriate ICR number or the ICR package
number.
5. Select the printer type.
6. Press to route the report to the printer; press
to route the data to a file.
5.5 Proposed ICRS Listing
This menu option will generate a listing of all ICR numbers
and their corresponding titles for ICRs proposed for the
forthcoming fiscal year. The ICRs presented have had an ICR
number assigned (at the time of the Information Collection
Budget - ICB), but they have not had an SF-83 filed. These
are the "pending" ICRs.
Steps
1. Select RUN REPORTS from the MAIN MENU.
2. Select PROPOSED ICR LISTING from the REPORTS MENU.
3. Select the printer type.
4. Press to route the report to the printer; press
to route the data to a file.
5.6 Tracking Event History
This short report generates a list of all the Tracking Events
that have ever been associated with a specified ICR. If the
user specifies a package number other than package number 00,
then the report is restricted to only those Tracking Events
which are associated with the specified package (i.e., a
specific SF-83). Specifying a package number 00 will
generate the complete list of all Tracking Events associated
with the indicated ICR.
Steps
1. Select RUN REPORTS from the MAIN MENU.
2. Select TRACKING EVENT HISTORY from the REPORTS
MENU.
December 28, 1989 Ver 1.1 Page 40
-------
PRAMS II USER MANUAL
3. Enter the ICR number as desired for the ICR which
is being reported. Enter a 00 package number to
receive a report of all packages associated with
the particular ICR; enter the appropriate package
number to receive a listing for a single package.
4. Select the printer type.
5. Press to route the report to the printer? press
to route the data to a file.
Screen 1.4.7 PAPERWORK REDUCTION
ICR Number: 1545 Expires: 12/30/89 Las
Title: THis is the TITLE for 1545.01 create
Department/ Agency/Bureau/Off ice:
This is the DABO name for 1545.01
Summary of Responses and Reporting Hours:
Response
Total Inventory: 200
Total Adjustments: 199
Total Program Changes: 2901
Comments: (Use arrow keys to scroll - Press
This is the first package and these are the
ACT Page 1 of 1
t Track Event: DD on 09/29/89
new ICR function
s Reporting Hours
0
-50
750
Ctrl-W when done)
ICR summary comments
Figure 18
Display an ICR Summary
5.7 Display an ICR Summary
1. Select RUN REPORTS from the MAIN MENU.
December 28, 1989 Ver l.l Page 41
-------
PRAMS II USER MANUAL
Select DISPLAY AN ICR SUMMARY from the REPORTS
MENU.
Enter the ICR number for the ICR which is to be
reviewed.
The summary may be reviewed on screen and the
Comments can be edited.
Press to exit without saving any changes made
to the comments; press to save any
changes and return to the REPORTS MENU.
December 28, 1989 Ver 1.1 Page 42
-------
PRAMS II USER MANUAL
INDEX
Accessing PRAMS II 10
Adding Data
Form 2A 17, 18
Form 2B 11
ICRs not proposed 14
ICRs proposed 14
ICWs 16
OMB Responses 19, 20
Original ICR Profile 11
SF-83 12
SF-83s as amendments 15
Tracking Event 22, 24
Audit Trails
to OMB Responses 19
Conventions within PRAMS II 6
highlighting menu selections 7
user prompts 7
Conventions within this manual 5
enter key 5
typing a response 5
user-required keystrokes 5
Data entry field
defined 5
Data Entry Screen
escaping without saving 9
reviewing data 8
saving data 8
Database
program structure and flow 4
Display an ICR Summary
generating 39
Edit Forms Reports
generating 36
Editing Data
Form 2A 30
Form 2B 29
ICW 29
OMB Responses 32
SF-83 29
Tracking Event 31
Error Messages 9
displayed in message area 7,9
displayed in the center of the screen 9
for OMB Responses 9
Event Codes 22
December 28, 1989 Ver 1.1 Page 43
-------
PRAMS II USER MANUAL
duplicate entries 24
list of 23
online help for 23
Form
defined 5
December 28, 1989 Ver 1.1 Page 44
-------
PRAMS II USER MANUAL
INDEX
continued
Form 2A
adding 17, 18
data which cannot be edited 31
editing 30
editing top portion online 18, 31
function of 17
number allowed 17
processing 2
Form 2B
adding 11
editing 29
hard copy of 2
ICR numbers and 11
packages and 13
when processed 2
without corresponding SF-83, listing of .... 11
ICR
tracking events and 22
ICR number
assigned 1
defined 5
ICR package number
defined 5
when assigned 13
ICR Status Report
description 34
generating 35
ICR Summary
description 34
ICR Summary Record
when created 2
ICW
adding 16, 17
adding OMB Responses to 21
deleting associated tracking event 31
displaying associated tracking events 26
editing 29
editing associated tracking event 31
function of 16
inputs required to edit 30
manual list pertaining to 17
OMB Responses and 17, 19
processing 2
Tracking Event and 3, 22
Memo field
December 28, 1989 Ver 1.1 Page 45
-------
PRAMS II USER MANUAL
defined 5
entering data into 7
keys used to edit 7, 8
using the enter key within 7
December 28, 1989 Ver 1.1 Page 46
-------
PRAMS II USER MANUAL
INDEX
continued
Menu Screen 6
the header 6
the menu area 7
the message area 7
Monthly Report
description 34
generating 36
OMB Response
adding 19, 20
adding a response to an ICW 21
adding a response to an SF-83 20
audit trails and 19
editing 19, 32
error messages 9, 19, 20
ICR number and 3
ICW and 19
processing 3
reviewing 19, 21
SF-83 and 19
Original ICR Profile
adding 11
when processed 2
Package 13
when created 1, 13
when number is assinged 13
Package Tracking Event
creation of 3
Password
entering 10
Print Edit Forms
description 34
Proposed ICR Listing
description 34
generating 38
Reports
available 34
Display an ICR Summary, generating 39
Edit Forms Reports, generating 36
ICR Status Report, described 34
ICR Status Report, generating 35
ICR Summary, described 34
Monthly Report, described 34
Monthly Report, generating 36
preparing printer 34
Print Edit Forms, described 34
December 28, 1989 Ver 1.1 Page 47
-------
PRAMS II USER MANUAL
Proposed ICR Listing 38
Proposed ICR Listing, described 34
sending to file 34
sending to file, procedure 34
Tickler Report, described 34
Tickler Report, generating 36
INDEX
continued
Tracking Event History, described 34
Tracking Event History, generating 38
Screen
defined 5
SF-83
adding 12
adding as an amendment 15
adding ICRs not proposed 14
adding ICRs proposed 14
adding OMB Responses to 20
and package numbers 13
deleting associated tracking event 31
displaying associated tracking events 26
editing 29
editing associated tracking event 31
Form 2B and 2
hard copy of 2
ICR number and 1
instances when filed 12
OMB Responses and 19
processing 1
Tracking Event and 3, 22
Tickler Report
description 34
generating 36
Tracking Event
adding 22, 24
deleting 31
displaying 26
editing 31
event codes 22
hard copy of 3
ICW and 3, 22
ICW and deleting 31
ICW and editing 31
information required to delete 32
information required to edit 32
lists of 22
number per ICR 22
December 28, 1989 Ver 1.1 Page 48
-------
PRAMS II USER MANUAL
processing 3
SF-83 and 3, 22
SF-83 and deleting 31
SF-83 and editing 31
Tracking Event History
description 34
generating 38
User ID
entering 10
December 28, 1989 Ver l.l Page 49
-------
APPENDIX A
Sample Input Screens
-------
Screen 1.1.1 PAPERWORK REDUCTION ACT Page 1 of 2
ICR number: 1511.00
ICR Title: (Use Arrow keys to scroll; Press when done)
Mark X at the expected FY of request for original clearance:
FY90 [ ] FY91 [ ] FY92 [ ]
Contact person: First name: [
Last name: [
Mail code: [ ]
Telephone: [( )
Estimated burden hours for this ICR: [ 0]
Form 2B Data Entry Screen
Page One
-------
Screen 1.1.1
PAPERWORK REDUCTION ACT
Page 2 of 2
AA Code: [ ] Division Code: [ 0]
Abstract: (Use Arrow keys to Scroll; Press when done.)
ICR Comments: (Use Arrow keys to Scroll; Press when done.)
Form 2B Data Entry Screen
Page Two
-------
Screen 1.1.3
PAPERWORK REDUCTION ACT
Page 1 of 4
ICR
#:
1000
.02
Desk Officer Initials [ ]
1. Department/Agency/Bureau: (Press Ctrl-W when done)
2. Agency Code:
[70]
3. Name of person who can answer questions concerning this request:
First Name [ ] Mailing Address [ ]
Last Name [ ] Telephone [ ( ) - ]
4. Title: (Arrow keys to scroll, CTRL-W to exit)
5. Legal authority for information collection or rule: (site U.S. code
law, or executive order)
[ 0] USC: [ ] [ ]
SF-83 Data Entry Screen
Page One
-------
Screen 1.1.3
PAPERWORK REDUCTION ACT
Page 2 of 4
6. Affected Public: (X all that apply) [ ]Federal Agencies/employees
[ ]Individuals/households [ ]Farms [ ]Non-profit institutions
[ ]State/local government [ ]Businesses [ ]Small Business/Organization
13. Abstract: (Arrow keys to scroll, CTRL-W when finished.)
14. Type of information collection:
(Enter number from SF 83) [ ]
15. Type of review requested:
(Enter selection from SF 83) [ ]
SF-83 Data Entry Screen
Page Two
-------
Screen 1.1.3 PAPERWORK REDUCTION
17. Annual Report ing/disclusure burden:
Number of respondents [
Number responses per respndt. [
Total annual responses [
Hours per response [ 0
Total hours [
18. Annual Recordkeeping Burden:
No. of record keepers [
Hours per record keeper [ 0
Total hours [ 0
Retention period (in years)
19. Total Annual Burden:
Requested [
In current OMB inventory [
Difference (current-requested) [
20. Explanation Program Change [
of difference: Adjustment [
ACT Page 3 of
0]
0]
0]
.00]
0]
0]
.00]
.00]
[ 0]
0]
0]
0]
0]
0]
4
21. Expires: [ / / ]
22. Purpose:
[ ] Benefits
[ ] Program Evaluation
[ ] Statistics
[ ] Regulatory/complianc
[ ] Program planning/mgt
[ ] Research
[ ] Audit
23. Frequency:
[ ] Recordkeeping
[ ] On occasion
[ ] Weekly
[ ] Monthly
[ ] Quarterly
[ ] Semi-annually
[ ] Annually
[ ] Biennially
[ ] Other:
8F-83 Data Entry Screen
Page Three
-------
Screen 1.1.3 PAPERWORK REDUCTION ACT Page 4 of 4
24. Respondents obligation to comply: (Enter number from SF-83) [0]
25. Are the respondents primarily educational agencies/institutions, or is
primary purpose related to federal educations programs? (Y/N): [N]
26. Does the ICR have sampling/statistical requirements? (Y/N) : [N]
Enter Statistician Comments (Press when done)
Package Comments: (Arrow keys to scroll; Press when done)
SF-83 Data Entry screen
Page Four
-------
Screen 1.1.5 PAPERWORK REDUCTION ACT Page 1 of 2
1
1
1
INVENTORY CORRECTION
WORKSHEET for ICR Number : 0010
Completion Date of the ICW:
From (desk officer) :
Docket number or OMBf:
Effective date of correction:
[ / / ]
[ ]
[ / / ]
SF 83 item: Currently
Agency/ Bureau #:
Functional code:
Expiration date:
in inventory: as corrected:
[0] [0]
[ / / ] [ / / ]
1
ICW Data Entry Screen
Page one
-------
Screen 1.1.5 PAPERWORK REDUCTION ACT Page 2 of 2
Reporting Burden: Responses: Reporting Hours:
In Inventory (old): [ 0] [ 0]
New (if changed): [ 0] [ 0]
Difference (new-old): [ 0] [ 0]
Adjustments: Responses: Reporting Hours:
Correction - Error: [ 0] [ 0]
Correction-Reestimate: [ 0] [ 0]
Change in use: [ 0] [ 0]
Program Changes: [ 0] [ 0]
ICW Comments: (Use Arrow keys to Scroll; Press when done)
ICW Data Entry Screen
Page Two
-------
Screen 1.1. 7b PAPERWORK
REDUCTION ACT
Page 1 of 2
OMB Response Data for
Approved: (Y/N) [N] Expiration
I CR. PACKAGE #
[ 1000.
Date: [05/3 1/91] OMB #
1 ]
: [2070-0003]
EFFECT ON BURDEN
Previous Status:
New Status:
Difference: [
EXPLANTION OF THE DIFFERENCE
Ad j ustments :
Correction-Error :
Correction-Reestimate :
, Change in use:
II Adjustment Totals:
I Program Changes:
1 (Use "-" for decrease)
RESPONSES
[ 113768]
[ 113768]
0]
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
REPORTING HRS
[ 19860]
[ 19860]
t 0]
[ 0]
[ 0]
[ 0]
[ 0]
[ 0]
OMB Response to an SF-83
Page One
-------
Screen 1.1.7b
PAPERWORK REDUCTION ACT
Page 2 of 2
Is there a condition for renewal
or other comments associated with
this OMB response form? [N]
OMB REMARKS: (Use Arrow keys to Scroll; Press when done)
OMB Response to an SF-83
Page Two
-------
Screen 1.1.7a
PAPERWORK REDUCTION ACT
Page 1 of 2
OMB Response Data Input for an ICW with ICR #: 0010
Date of completion of this ICW: 09/10/89
FROM:(desk officer responsible)
Docket number or OMB #: 0
Effective date of correction(s): 09/09/90
ITEM CURRENT
Agency/Bureau #:
Functional code:
Expiration date: 12/31/90
REQUESTED OMB Approved:
0 [ 0]
[ ]
/ / [ / / ]
OMB Response to an ICW
Page One
-------
Screen 1.1. 7a PAPERWORK REDUCTION ACT Page 2 of 2
REQUESTED OMB APPROVED
Responses Report Hrs Responses Report Hrs
In Inventory (old) : 0
New (if changed) : 0
Difference (new - old) : 0
0
0
0
[ 0] [
[ 0] [
[ 0] [
0]
0]
0]
Correction - Error: 0
Correction-Reestimate: 0
Change in use: 0
0
0
0
[ 0] [
[ 0] [
[ 0] [
0]
0]
0]
Program Changes: 0
ICW Comments: (Use Arrow keys to Scroll;
0
Press
t 0] [
CTRL-W when done)
0]
OMB Response to an ICW
Page Two
-------
Screen 1.3.2 PAPERWORK REDUCTION ACT Page 1 of 1
ICR Number: 0010 Current OMB #: 2060-0095 Expires on: 12/31/90
Title: Information Requirements for Importation of Nonconforming Vehicles
Contact: Claude Magnuson
Phone f: (202) 382-254 OMB Approved Hours:167836
FISCAL YEAR 1990 FISCAL YEAR 1991
ICB original est.: [ 0] Burden hours: [ 0]
Adjustments: [ 0] Adjustments: [ 0]
Program Changes: [ 0] Program Changes: [ 0]
Total Estimate: [ 0] Total Estimate: [ 0]
(i) Reason for adjustment or program change: (CTRL-W to exit)
(j) If this ICR should not be on 1991 budget, mark T on reason number(s)
1. [F] 2. [F] 3. [F] 4. [F] 5. [F] 6. [F]
Form 2A Data Entry Screen
Page One
-------
APPENDIX B
Tracking Event Codes
-------
Tracking Event Codes
Event Code Tracking Event Description
AD OMB approval date
CR Correction received from OMB
CS Correction sent to OMB
DD To Division Director
DI Deleted by program
HR Hid for rule
II In IPB
10 In OMB
IS Informal submission to OMB
OA Out of OMB - approved
OD Out of OMB - disapproved
PO Resubmitted by Program
RP Returned to Program
SD Signed by Director
WP Withdrawn by Program
EX Extention of expiration
date/rece ived
CA Canceled
-------
APPENDIX C
Report Samples
-------
Date : 05/01/89
ICR STATUS REPORT
SORTED BY AGENCY / ICR NUMBER
FOR
Office of Administration and Resources Management
PAGE: 1
ICR OMB
NUMBER NUMBER
ICR TITLE
HRS ICR EXP CONTACT
APPROVED DATE PERSON
PKG# STATUS
S:SSS3S33S33BSSS333S3SSS333883ESS333SSS3S=3==S33=SS3S:3SS3SS333S333SSSSS
0246 2030-0016 Contractor emulative Claim and
Reconciliation EPA Form 1900-10
150 07/31/89
Shirley Ross
Ph * (202) 475-8666
.01 Out OMB Approved
08/15/88
0287 2030-0009 Report of Nonexpendable Government
Property Acquired by Contractor
0788 2030-0019 Hazardous Substance Response Fund
Contractor Cost Report
0938 2030-0020 General Regulation for Assistance Program
0973 2030-0013 Procurement System Certification Form for
for Applicants for EPA Assistance
1037 2030-0007 Oral and Written Purchase Orders
0 11/30/89
17100 10/31/89
186996 11/30/89
20986 10/31/90
35042 04/30/90
Shirley Ross
Ph * (202) 475-8666
Shirley Ross
Ph * (202) 475-8666
Shirley Ross
Ph « (202) 475-8666
Shirley Ross
Ph * (202) 475-8666
Shirley Ross
Ph * (202) 475-8666
.01 CS
07/12/88
.01 In OMB
07/12/89
.01 Extention
08/18/89
.01 Out OMB Approved
02/08/88
.01 CR
08/14/89
1038 2030-0006 Procurement Solicitations (RFPs and IFBs)
203890 12/31/90
Shirley Ross
Ph * (202) 475-8666
.01 CS
08/01/89
1039 2030-0005 Technical and Financial Progress Reports
Submitted in Accordance with Contract
Requirements
1474 2030-0022 Ecological Information Initiative
979256 10/31/90
Shirley Ross
Ph « (202) 475-8666
.01 CS
08/04/89
100 09/30/91 Barbara Lamborne .01 Out OMB Approved
Ph * (202) 382-5224 09/08/88
-------
ICR Status Report
-------
Tickler Report
-------
Date : 05/01/89 PAGE: 1
ICR TICKLER REPORT
FOR
Office of Administration and Resources Management
EXPIRATION DATE: 07/31/89 ICR f: 0246 OMB #: 2030-0016
TITLE: Contractor Cumulative Claim and Reconciliation EPA Form 1900-10
POINT OF CONTACT: Eleanor Nonnent PHONE: (202) 382-5035
EXPIRATION DATE: 11/30/89 ICR f: 0287 OMB #: 2030-0009
TITLE: Report of Nonexpendable Government Property Acquired by
Contractor
POINT OF CONTACT: Anthony Borda PHONE: (202) 475-7712
EXPIRATION DATE: 10/31/89 ICR #: 0788 OMB #: 2030-0019
TITLE: Hazardous Substance Response Fund Contractor Cost Report
POINT OF CONTACT: Carolyn Anderson PHONE: (202) 475-8243
EXPIRATION DATE: 11/30/89 ICR #: 0938 OMB #: 2030-0020
TITLE: General Regulation for Assistance Program
POINT OF CONTACT: Richard Johnson PHONE: (202) 382-5296
-------
Monthly Status Report
-------
MONTHLY STATUS REPORT
REVIEW OF INFORMATION COLLECTION REQUEST
ISSUED and CURRENT AS OF
05/01/89
-------
Date : 05/01/89
* In ONB for 60 DAYS or MORE
" In OMB for 90 DAYS or MORE
MONTHLY STATUS REPORT
FOR
Other Offices
PAGE: 1
ICR.PKG OMB NUMBER
DESK
OFC.
IPB DATE
RETURNED
TO PROGRAM
RESUBMIT
BY PROGRAM
DIRECTOR
SIGNED
HOLD
RULE
OMB DATE OMB ACTION
ACTION
DATE
0086.01 - 0 DO 03/27/81
TITLE : Quality Assurance Specifications and Requirements
COMMENTS :
0963.02 2000-0422 HH 07/28/82
TITLE : Categorical Exclusions and Segmentation of Construction Grants Projects
COMMENTS : 0 0 198207281 0
1336.01 - 0 DO 10/08/86 10/15/86
TITLE : Hunan Exposure Assessment Location Study (HEALS)
COMMENTS : 0 0 0 New collection
1343.01 2050-0099 RU 12/07/88
TITLE : Reports for States to SARA Capacity Assurances
COMMENTS : 168000 0 0
12/14/88 No
12/21/88 APPROVED
03/15/89
1396.02 2060-0173 BU 04/11/89
TITLE : National Resindential Radon Pretest
COMMENTS : 7500
04/18/89 No
04/19/89 APPROVED
05/31/89
1544.01 - 0 DD 09/19/89
TITLE : Survey of Toxicological Testing Facilities
COMMENTS :
-------
Edit Report Forms
-------
SF-83 Edit Report Form
-------
1. Department/Agency/Bureau
THis is the title for CODE 60
2. Agency Code
60
3. Name of person who can answer questions concerning this request:
First Name:Claude Mail Code: 340
Last Name: Magnuson Telephone: (202) 382-2542
4. Title:
Information Requirements for Importation of Nonconforming Vehicles
5. Legal Authority: 42
USC: 7401
6. AFFECTED PUBLIC: (X all that apply)
X Individuals/ households Farms
State/ local government X Businesses
13. Abstract: (see next page)
or CAA Sec. 203 & 208
X
Fed. Agencies/employees
Non-profit institutions
Small Businesses/organiztns
14. TYPE OF INFORMATION COLLECTION (numeric selection from SF 83): 5
15. TYPE OF REVIEW REQUESTED (numeric selection) 2
17. ANNUAL REPORTING/DISCLOSURE BURDEN:
Number of respondents 2035
Number responses per respndt. 0
Total annual responses 0
Hours per response 0.00
Total hours 150336
18. ANNUAL RECORDKEEPING BURDEN:
No. of record keepers 35
Hours per record keeper 500.00
Total hours 17500.00
Retention period (in years) 6
21. EXPIRATION 12/31/90
22. PURPOSE
Benefits
Program Evaluation
Statistics
X Regulatory/compliance
Program planning/mgmnt
Research
Audit
19. TOTAL ANNUAL BURDEN:
Requested 167836
In current OMB inventory 0
Difference (current-requested) 0
20. EXPLANATION
OF THE DIFFERENCE:
Change 0
Adjustment 0
23. FREQUENCY
On occasion
Weekly
Monthly
Quarterly
Semi-annually
Annually
X Biennially
Other:
-------
25. Are the respondents primarily educational agencies
or institutions or is the primary purpose of the collection
related to Fed. education programs ? (Yes or No):
26. Does the agency use sampling to select respondents
or does the agency recommend or prescribe the use of
sampling or statistical analysis by respondents? (Yes or No) : N
ABSTRACT (from previous page):
GENERAL COMMENTS:
167836 0 1985 916
SUMMARY OF RESPONSES AND REPORTING HOURS FOR ICR # 0010:
Responses Reporting Hours
Total Inventory 37070 167836
Adjustment 0 0
Program Change 0 0
ICR expiration = 12/31/90
-------
ICR Profile Edit Form
-------
Original ICR Profile (Form 2B) Edit Form for ICR # 0010 as of 10/02/89
Title of this Information Collection Request (ICR)
Information Requirements for Importation of Nonconforming Vehicles
Fiscal year of expected request for original clearance: 1990
Zontact person : First name: Claude
Last name: Magnuson
Mail code: 340
Telephone: (202) 382-2542
ABSTRACT :
NONE
Est. burden hours for this ICR: 0
AA-Division code: AR 25
ICR Comments (Administrative notes here if needed.)
NONE
-------
ICW Edit Report Form
-------
Inventory Correction Worksheet Edit Form for ICR # 0010 as of 10/02/89
Date of completion of this ICW. 09/29/89
FROM: (desk officer responsible)
Docket number or OMBl - 0
Effective date of correction(s) 09/29/89
SF 83 ITEM
Agency/Bureau #
Functional code
Expiration date
REPORTING BURDEN:
In Inventory (old)
New (if changed)
Difference (new-old)
CORRECTION
0
Responses
0
0
0
ADJUSTMENTS:
Responses
Correction - Error 0
Correction-Reestimate 0
Change in use 0
Reporting Hours
0
0
0
Reporting Hours
0
0
0
PROGRAM CHANGES:
ICW COMMENTS:
NONE
-------
Tracking Event History
-------
10/02/89 Page: 1
TRACKING EVENT REPORT for ICR # 0010.01
CODE DESCRIPTION DATE
II In IPB 03/17/82
10 In OMB 04/19/82
OA Out of OMB - approved 05/27/82
CR Correction received from OMB 11/06/84
CS Correction Sent to OMB 05/17/85
CR Correction received from OMB 06/18/85
-------
APPENDIX D
Database Structure
-------
DATABASE STRUCTURES
There are a total of 15 databases in the PRAMS II
PACKAGE.DBF
TRACKING.DBF
EVENTS.DBF
ICR.DBF
ICW.DBF
ICB_PROF.DBF
AGENCIES.DBF
SYSTEM.DBF
TRAKTEMP.DBF
AADIV.DBF
ARC_ICR.DBF
ARC_PKG.DBF
ARCJECB.DBF
ARC_ICW.DBF
ARC TRK.DBF
There are 14 associated index files:
PACKAGE1.NDX
PACKAGE2.NDX
TRAKICR.NDX
TRAKPKG.NDX
TRAKDATE.NDX
ICRINDEX.NDX
ICRAGNCY.NDX
ICROMBAG.NDX
ICW_ICR.NDX
ICB.NDX
TTMPDATE.NDX
AGENCIES.NDX
ICW DATE.NDX
-------
There are 12 memo files associated with the databases.
ICR.DBT
PACKAGE.DBT
ICB_PROF.DBT
ICW.DBT
TRACKING.DBT
ACRJECR.DBT
ARC_PKG.DBT
ARC_ICW.DBT
ARC_ICB.DBT
ARC TRK.DBT
The following pages provide detailed database structures, index
associations, and index keys for each database in the PRAMS2
system.
-------
Structure for database : PACKAGE.DBF
Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
Field name
ICR_NUMBER
PKG_NUMBER
TTL_RECHRS
TTL_HOURS
TTL_RESPON
ADJUSTMENT
PGM_CHANGE
TAB_DIFFER
CUR_OMB_IN
REQ_BURDEN
REC_RETENT
HR_PER_KPR
NO_REC_KPR
HR_PER_RSP
PER_RSPOND
NO_RESPDNT
STAT_FLAG
ED_FLAG
REQ_X_DATE
REVIEW_TYP
FR_DATE
COLECTJTYP
PKG_ABSTRC
OTHER_AUTH
USC_CHAPTR
USC_TITLE
AFFECTPUB7
AFFECTPUB6
AFFECTPUB5
AFFECTPUB4
AFFECTPUB3
AFFECTPUB2
AFFECTPUB1
POC_MAIL
POC_PHONE
POC_FIRST
POC_LAST
OMB_X_DATE
PKG_TITLE
CUR_OMB_NO
NEW_NO_FLG
OBLIGATION
GEN_COMNTS
OMBPREVRSP
OMBPREVHRS
OMBNEWRESP
OMBNEWRPT
OMBRESPADJ
OMBRPTADJ
OMBPRGCRSP
OMBPRGRPT
Type
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Logical
Logical
Date
Numeric
Date
Character
Memo
Character
Character
Numeric
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Date
Memo
Numeric
Logical
Numeric
Memo
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Width
4
2
14
18
12
14
14
18
18
18
2
7
8
7
4
8
1
1
8
1
8
1
10
20
24
2
1
1
1
1
1
1
1
6
10
10
15
8
10
10
1
1
10
8
8
8
8
10
10
8
8
Dec
2
2
2
2
-------
52 FREQ_RR_1
53 FREQ_RR_2
54 FREQ_RR_3
55 FREQ_RR_4
56 FREQ_RR_5
57 FREQ_RR_6
58 FREQ_RR_7
59 FREQ_RR_8
60 FREQ_RR_9
61 FREQ_DSCRP
62 PURPOSE_1
63 PURPOSE_2
64 PURPOSE_3
65 PURPOSE_4
66 PURPOSE_5
67 PURPOSE_6
68 PURPOSE_7
69 STAT_CMNTS
70 OMB_CMNTS
71 OMB_CONDIT
72 OMB_APPROV
73 DABO_NAME
74 DO INITALS
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Memo
Memo
Logical
Logical
Memo
Character
1
1
1
1
1
1
1
1
1
25
1
1
1
1
1
1
1
10
10
1
1
10
2
This database uses the memo file: PACKAGE.DBT
This database is associated with index file(s):
: PACKAGE2.NDX (ICR_NUMBER)+STR(PKG NUMBER)
: PACKAGE1.NDX (icr_number)
Structure for database : TRACKING.DBF
Field
1
2
3
4
5
6
7
Field name
ICR_NUMBER
PKG_NUMBER
EVNT_CODE
EVNT_DATE
EVNT_CMNTS
EVNT_CLOSE
ICW FLAG
Type
Numeric
Numeric
Character
Date
Memo
Logical
Logical
Width
4
2
2
8
10
1
1
Dec
This database uses the memo file: TRACKING.DBT
This database is associated with index file(s):
: TRAKICR.NDX (icr_number)
: TRAKPKG.NDX (ICR_NUMBER) +STR(PKG_NUMBER)
: TRAKDATE
(ICR_NUMBER) +STR (PKG_NUMBER) +DTOS (EVNT_DATE)
N D X
-------
Structure for database : EVENTS.DBF
Field Field name
1 EVENT_CODE
2 EVENT NAME
Type
Character
Character
Width
2
50
Dec
Structure for database : ICR.DBF
Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
Field name
ICR_NUMBER
SUM_RESP
SUM_RPT_HR
SUM_ADJRSP
SUM_ADJRPT
SUM_PC_RSP
SUM_PC_HRS
EXP_DATE
DIV_CODE
INIT_DATE
ICR_TITLE
AGENCY
CUR_OMB_NO
PENDING
ICR_CMNTS
DABO_NAME
AA_CODE
TE_STATUS
TE DATE
Type
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Date
Numeric
Date
Memo
Numeric
Numeric
Logical
Memo
Memo
Character
Character
Date
Width
4
10
10
10
10
10
10
8
2
8
10
2
8
1
10
10
3
2
8
Dec
This database uses the memo file called: ICR.DBT.
This database is associated with the followind index files;
ICRINDEX.NDX (icr_number)
ICRAGNCY. NDX (AGENCY) +STR( ICR_NUMBER)
ICROMBAG.NDX (AGENCY)+STR(CUR_OMB NO)
-------
Structure for database : ICW.DBF
Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
Field name
ICR_NUMBER
ICW_LOGGED
DESK_OFFC
ICB_OMB_NO
EFFCT_DATE
AGNCY_NUMB
FUNCT_CODE
EXPIR_DATE
RESPD_OLD
RESP_NEW
RESP_DIFF
RSP_ADJ_ER
RSPADJREST
RSPADJCIU
RSP_PRG_CH
HOURS_OLD
HOURS_NEW
HOURS_DIFF
HRS_ADJ_ER
HR_ADJREST
HR_ADJ_CIU
HRS_PRG_CH
ICW_ID_NO
OMBRESFOLD
OMBRESPNEW
OMBRESPDIF
OMBRSPADER
OMBRSADRES
OMBRSADCIU
OMBRSPRGCH
OMBHRS_OLD
OMBHRS_NEW
OMBHRS_DIF
OMBHRSADER
OMBHRADRES
Type
Numeric
Date
Character
Numeric
Date
Numeric
Character
Date
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Width
4
8
40
8
8
6
3
8
10
10
10
10
10
10
10
10
10
10
10
10
10
10
6
10
10
10
10
10
10
10
10
10
10
10
10
Dec
-------
36 OMBHRADCIU Numeric
37 OMBHRPRGCH Numeric
38 ICW_COMNTS Memo
39 OMBAGNCYNO Numeric
40 OMBFUNCODE Character
41 OMBEXPIRE Date
10
10
10
6
3
8
This database uses the memo file: ICW.DBT
This database is associated with index file(s):
: ICW_ICR.NDX (icr_number)
: ICW_DATE.NDX (ICR_NUMBER)+DTOS(EFFCT_DATE)
Structure for database : ICB PROF.DBF
Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
Field name
ICR_NUMBER
CURRENT_FY
NEXT_FY
ORIG_EST1
ADJ_HOURS1
PRG_CHANG1
EST_HOURS2
ADJ_HOURS2
EST_TOTAL1
PRG_CHANG2
PASS_BACK
APPEAL_2
ALLOWANCE2
CLOSE_OUT
ICB_COMNT
ICB_REASON
REASON_1
REASON_2
REASON 3
Type
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Character
Character
Memo
Memo
Logical
Logical
Logical
Width
'4
4
4
10
10
10
10
10
10
10
10
10
20
1
10
10
1
1
1
Dec
-------
20 REASON_4
21 REASON_5
22 REASON_6
23 REASON_ICR
24 EST TOTAL2
Logical
Logical
Character
Numeric
Numeric
1
1
50
4
10
This database uses the memo filme: ICB_PROF.DBT
This database is associated index file:
: ICB.NDX (icr_number)
Structure for database : AGENCIES.DBF
Field Field name
1 AGENCYCODE
2 AGENCYNAME
Type
Numeric
Character
Width
2
50
Dec
This database is associated with index file(s)
: AGENCIES.NDX (icr_number)
Structure for database : SYSTEM.DBF
Field Field name Type
1 USER_ID Character
2 PASSWORD Character
3 LASTUPDATE Date
4 FULLNAME
5 SEC LEVEL
Character
Numeric
Width
10
10
8
25
1
Dec
Structure for database : TRAKTEMP.DBF
Field
1
2
3
4
5
6
7
Field name
ICR_NUMBER
PKG_NUMBER
EVNT_CODE
EVNT_DATE
EVNT_CMNTS
EVNT_CLOSE
ICW FLAG
Type
Numeric
Numeric
Character
Date
Memo
Logical
Logical
Width
4
2
2
8
10
1
1
Dec
This database uses the memo file: TRAKTEMP.DBT
This database is associated with index file(s):
: TTMPDATE
(ICR_NUMBER) +STR(PKG_NUMBER) +DTOS (EVNT DATE)
NDX
-------
Structure for database : AADIV.DBF
Field
1
2
3
4
5
Field name
AA CODE
DIV CODE
OFFICE
MAIL CODE
OD NAME
Type
Character
Numeric
Character
Character
Character
Structure for database : ARC
Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
Field name
ICR NUMBER
SUM RESP
SUM RPT HR
SUM ADJRSP
SUM ADJRPT
SUM PC RSP
SUM PC HRS
EXP DATE
DIV CODE
INIT DATE
ICR TITLE
AGENCY
CUR OMB NO
PENDING
ICR CMNTS
DABO NAME
AA CODE
Type
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Date
Numeric
Date
Memo
Numeric
Numeric
Logical
Memo
Memo
Character
Width
3
2
5
7
80
JCR.DBF
Width
4
10
10
10
10
10
10
8
2
8
10
2
8
1
10
10
3
Dec
Dec
This database uses the memo file: ARC ICR.DBT
Structure for database : ARC PKG.DBF
Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
Field name
ICR_NUMBER
PKG_NUMBER
TTL_RECHRS
TTL_HOURS
TTL_RESPON
ADJUSTMENT
PGM_CHANGE
TAB_DIFFER
CUR_OMB_IN
REQ_BURDEN
REC_RETENT
HR_PER_KPR
NO_REC_KPR
HR_PER_RSP
PER_RSPOND
NO_RESPDNT
STAT FLAG
Type
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Logical
Width
4
2
14
18
12
14
14
18
18
18
2
7
8
7
4
8
1
Dec
2
2
2
2
-------
18 ED_FLAG
19 REQ_X_DATE
20 REVIEWJTYP
21 FR_DATE
22 COLECT_TYP
23 PKG_ABSTRC
24 OTHER_AUTH
25 USC_CHAPTR
26 USC_TITLE
27 AFFECTPUB7
28 AFFECTPUB6
29 AFFECTPUB5
30 AFFECTPUB4
31 AFFECTPUB3
32 AFFECTPUB2
33 AFFECTPUB1
34 POC_MAIL
35 POC_PHONE
36 POC_FIRST
37 POC_LAST
38 OMB_X_DATE
39 PKG_TITLE
40 CUR_OMB_NO
41 NEW_NO_FLG
42 OBLIGATION
43 GEN_COMNTS
44 OMBPREVRSP
45 OMBPREVHRS
46 OHBNEWRESP
47 OMBNEWRPT
48 OHBRESPADJ
49 OMBRPTADJ
50 OMBPRGCRSP
51 OMBPRGRPT
52 FREQ_RR_1
53 FREQ_RR_2
54 FREQ_RR_3
55 FREQ_RR_4
56 FREQ_RR_5
57 FREQ_RR_6
58 FREQ_RR_7
59 FREQ_RR_8
60 FREQ_RR_9
61 FREQ_DSCRP
62 PURPOSE_1
63 PURPOSE_2
64 PURPOSE_3
65 PURPOSE_4
66 PURPOSE_5
67 PURPOSE_6
68 PURPOSE_7
69 STAT_CMNTS
70 OMB_CMNTS
71 OMB CONDIT
Logical
Date
Numeric
Date
Character
Memo
Character
Character
Numeric
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Date
Memo
Numeric
Logical
Numeric
Memo
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Character
Memo
Memo
Logical
1
8
1
8
1
10
20
24
2
1
1
1
1
1
1
1
6
10
10
15
8
10
10
1
1
10
8
8
8
8
10
10
8
8
1
1
1
1
1
1
1
1
1
25
1
1
1
1
1
1
1
10
10
1
-------
72 OMB_APPROV Logical i
73 DABO_NAME Memo 10
74 DO_INITALS Character 2
This database uses the memo file: ARC PKG.DBT
Structure for database : ARC ICB.DBF
Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Field name
ICR_NUMBER
CURRENT_FY
NEXT_FY
ORIG_EST1
ADJ_HOURS1
PRG_CHANG1
EST_HOURS2
ADJ_HOURS2
EST_TOTAL1
PRG_CHANG2
PASS_BACK
APPEAL_2
ALLOWANCE2
CLOSE_OUT
ICB_COMNT
ICB_REASON
REASON_1
REASON_2
REASON_3
REASON_4
REASON_5
REASON_6
REASON_ICR
EST TOTAL2
Type
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Character
Character
Memo
Memo
Logical
Logical
Logical
Logical
Logical
Character
Numeric
Numeric
Width
4
4
4
10
10
10
10
10
10
10
10
10
20
1
10
10
1
1
1
1
1
50
4
10
Dec
This database uses the memo file: ARC ICB.DBT
Structure for database : ARC ICW.DBF
Field
1
2
3
4
5
6
7
8
9
10
11
12
Field name
ICR_NUMBER
ICW_LOGGED
DESK_OFFC
ICB_OMB_NO
EFFCT_DATE
AGNCY_NUMB
FUNCT_CODE
EXPIR_DATE
RESPD_OLD
RESP_NEW
RESP_DIFF
RSP ADJ ER
Type
Numeric
Date
Character
Numeric
Date
Numeric
Character
Date
Numeric
Numeric
Numeric
Numeric
Width
4
8
40
8
8
6
3
8
10
10
10
10
Dec
-------
13 RSPADJREST
14 RSPADJCIU
15 RSP_PRG_CH
16 HOURS_OLD
17 HOURS_NEW
18 HOURS_DIFF
19 HRS_ADJ_ER
20 HR_ADJREST
21 HR_ADJ_CIU
22 HRS_PRG_CH
23 ICW_ID_NO
24 OMBRESPOLD
25 OMBRESPNEW
26 OMBRESPDIF
27 OMBRSPADER
28 OMBRSADRES
29 OMBRSADCIU
30 OMBRSPRGCH
31 OMBHRS_OLD
32 OMBHRS_NEW
33 OMBHRS_DIF
34 OMBHRSADER
35 OMBHRADRES
36 OMBHRADCIU
37 OMBHRPRGCH
38 ICW_COMNTS
39 OMBAGNCYNO
40 OMBFUNCODE
41 OMBEXPIRE
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Numeric
Memo
Numeric
Character
Date
10
10
10
10
10
10
10
10
10
10
6
10
10
10
10
10
10
10
10
10
10
10
10
10
10
10
2
3
8
This database uses the memo file: ARC ICW.DBT
Structure for database : ARC TRK.DBF
Field
1
2
3
4
5
6
7
Field name
ICR_NUMBER
PKG_NUMBER
EVNT_CODE
EVNT_DATE
EVNT_CMNTS
EVNT_CLOSE
ICW FLAG
Type
Numeric
Numeric
Character
Date
Memo
Logical
Logical
Width
4
2
2
8
10
1
1
Dec
This database uses the memo file: ARC TRK.DBT
-------
APPENDIX E
Agency Names
-------
AGENCY TABLE
OFFICE NAME
OMB NUMERIC
CODES
Office of Policy Planning and Evaluation
Office of General Council
Office of Admin. Resources Management
Office of Water
Office of Air and Radiation
Office of Pesticides and Toxics
Office of Research and Development
Office of the Inspector General
Other Agencies
2010
2020
2030
2040
Office of Solid Waster and Emergency Response 2050
2060
2070
2080
2000
-------
APPENDIX F
AA/Division Codes
-------
/ra
Environmental Protection Agency
Office of Policy. Planning and Evaluation
Paperwork Reduction Act Nanagenent System
• Listing of Office-Division Code File •
K Division Office Hail
Lode Code Initials Code Office or Division Name
00
10
A 20
00
AR 01
" 02
03
„» 10
IB 11
12
13
AR 14
15
20
AR 21
•" 22
23
24
AR 25
30
31
AR 32
33
34
ADM OQ
10
11
ARM 12
I 13
1 14
ARM 15
-- ' 20
I 30
-»rJ 31
ARM 32
40
EA 00
10
20
EA 30
00
10
ECH 20
30
AO
OCR
OSDBU
OAR,
OAR
OAR
OAR
OAOPS
OAQPS
OAOPS
OAOPS
OAQPS .
OAQPS
OHS
QMS
QMS
QMS
QMS
OHS
OP.P
ORP
ORP
ORP
ORP
OARM
OA
OA
OA
OA
OA
OA
OIRM
OC
OC
OC
OHRM
OEA
OFA
OPA
OCIR
OECH
OCAPO
AEC
MEIC
A 100 Office of the Administrator
A105 Office of Civil Rights
A149C Office of Small ft Disadvantaged Business Utilization
ANR443 Office of Air and Radiation
ANR643 Office of Program Management Operations
AHR443 Office of Policy Analysis and Review
AMR445 Office of Program Development
HD10 Office of Air Quality Planning and Standards
MD15 Control Programs Development Division
MD13 Emission Standards and Engineering Division
HDU Monitoring and Data Analysis Division
EM341 Stationary Source Compliance Division*
MD12 Strategies and Air Standards Division
ANR455 Office of Mobile Sources
Certification Division
Emission Control Technology Division
-*- Engineering Operations Division
EN397F Field Operations and Support Division
EN340F Manufacturers Operations Division
ANR458C Office of Radiation Programs
ANR461C Analysis and Support Division
ANR460C Criteria and Standards Division
EERF Eastern Enviromental Radiation Facility (Montgomery AL)
ORP- IV ORP - Las Vegas Facility
PM208 Office of Administration and Resources Management
PH217 Office of Administration
PM212 Personnel Management Division
_.»•«•« u — _l A • • _* * •
PnZi3 Management ana organization Division
PM214F Procurement and Contracts Management Division
PM215 Facilties and Support Services Division
PM216 Grants Administration Division
PM211 Office of Information Resources Management
PN225 Office of the Comptroller
PM225 Budget Division
PM226 Financial Management Division
PM224 Office of Hunan Resources Management
A100EA Office of External Affairs
AIM Office of Federal Activities
A107 Office of Public Affairs
A100EA Office of Ccmnnity & Intergovernmental Relations
LE133 Office of Enforcement and Compliance Monitoring
LE133 Office of Compliance Analysis ft Program Operations
LEI 34 Associate Enforcement Counsel
NEIC Natl Enforcement Investigations Ctr (Denver)
-------
0/00
Environmental Protection Agency
Office of Policy, Planning and Evaluation
Paperwork Reduction Act Management System
• Listing of Office-Division Code File •
AA Division Office Mail
de Code Initials Code Office or Division Name
GC 00 OGC LE130 Office of General Counsel
A106 Office of International Activities
Office of the Inspector General
Office of Policy, Planning and Evaluation
Office of Management Systems and Evaluation
Office of Policy Analysis
Regulatory and Economic Analysis Division
Regulatory Integration Division
Office of Standards and Regulations
Chemicals and Statistical Policy Division
Information and Regulatory Systems Division
Office of Pesticides & Toxic Substances
Office of Compliance Monitoring
Office of Pesticide Programs
Benefits and Use Division
Hazard Evaluation Division
Program Management and Support Division
Registration Division
Office of Toxic Substances
Chemical Control Division
Economics and Technology Division
Existing Chemical Assessment Division
Exposure Evaluation Division
Health and Environmental Review Division
Information Management Division
TSCA Assistance Office
Region 1 - Boston
Region 2 - Mew York
Region 3 - Philadelphia
Region 4 - Atlanta
Region 5 - Chicago
Region 6 - Dallas
Region 7 - Kansas City
Region 8 • Denver
Region 9 - San Francisco
00
IG 00
E 00
PPE 10
E 20
E 21
PPE 23
""E 30
E 31
I 32
S 00
5 01
PTS 10
5 11
5 12
r,S 13
PTS u
5 20
S 21
PTS 22
5 23
5 24
PTS 25
"! 26
5 27
RQ1 00
2 00
i 00
R04 00
i 00
R06 00
7 00
3 00
*„? 00
01A
DIG
OPPE
OMSE
OPA
OPA
OPA
OSR
OSR
OSR
OPTS
OPTS
OPP
OPP
OPP
OPP
OPP
OTS
OTS
OTS
OTS
OTS
OTS
OTS
OTS
R-1
R-2
R-3
R-4
R-5
R-6
R-7
R-8
R-9
A106
A109
PM219
PM222
PM221
PM221
PM220
PH223
PH223
PH223
TS788
EN342
TS766C
TS768C
TS769C
TS757C
TS767C
TS792
TS794
TS779
TS778
TS798
TS796
TS793
TS799
-------
/88
Environmental Protection Agency
Office of Policy, Planning and Evaluation
Paperwork Reduction Act Management System
• Listing of Office-Division Code File *
Division Office Nail
Code Code Initials Code Office or Division Name
I 00 R-10 Region 10 - Seattle
»n 00 ORD RD672 Office of Research & Development
10 OEET RD681 Office of Environmental Engineering and Technology
20 OEPER RD682 Office of Environmental Processes and Effects Research
RD 30 OER RD67S Office of Exploratory Research
F 40 OHEA RD689 Office of Health and Environmental Assessment
( SO OHR RD683 Office of Health Research
RD 60 OADEH RD6BO Office of Acid Deposition. Environmental Monitoring and Quality Assurance
B" 70 ORPH RD674 Office of Research Program Management
Ru 00 ORO A101 Office of Regional Operations
s
s
su
«
S
su
s
s
s.
su
S1
S'
su
s
s
pi
Sw
SV
u
J
J
J
i
t
I
t
i
1
i
i
00
10
11
12
13
K
20
21
22
23
24
25
30
40
50
e 1
31
52
00
10
11
12
20
21
22
23
24
30
31
33
34
35
40
41
42
OSUER
OERR
OERR
OERR
OERR
OERR
OSU
OSU
OSU
OSU
OSU
OSU
OUPE
OUST
OPMT
nAUT
UrnT
OPMT
OU
OUEP
OUEP
OUEP
OURS
OURS
OURS
OURS
OURS
OMPC
OMPC
OMPC
OMPC
OMPC
QOU
ODU
ODU
UH562A
UH548
UH548D
UH548B
UH54&A
UH546E
UH562
UH565
UH562B
UH563
UH565
UH565
UH527
UH562A
UH562A
uuC/ OA
UH>«oA
UHS62A
UH556
EN335
EN338
EM336
UH551
UH552
UH553
UH585
UH586
UH546
WH546
UH595
UH547
UH554
UH550A
UH550D
UH550E
Office of Solid Uaste & Emergency Response
Office of Emergency and Remedial Response
Office of Program Management
Emergency Response Division
Hazardous Response Support Division
Hazardous Site Control Division
Office of Solid Uaste
Office of Program Management and Support
Characterization and Assessment Division
Permits and State Programs Division
Uaste Management Division
Policy, Planning & Information Staff
Office of Uaste Programs Enforcement
Office of Underground Storage Tanks
Office of Program Management & Technology
PrannMHf^vnnn ftmtt
repareoness start
Cross-Media Analysis Staff
Office of Uater
Office of Uater Enforcement and Permits
Enforcement Division
Permits Division
Office of Uater Regulations and Standards
Industrial Technology Division
Monitoring & Data Support Division
Criteria & Standards Division
Analysis & Evaluation Division
Office of Municipal Pollution Control
Office of Program Management & Evaluation
Municipal Facilities Division
Municipal Construction Division
Planning & Analysis Division
Office of Drinking Water
Criteria I Standards Division
State Programs Division
-------
/88
Division Office Nail
Code Initials Code
u
w
I
43
IA
50
60
61
62
70
ODU
ODU
OGP
OHEP
OMEP
OHEP
OWP
WH550B
WHSSOG
UH556F
UH556F
UH5S6F
A104
Environmental Protection Agency
Office of Policy, Planning and Evaluation
Paperwork Reduction Act Management System
• Listing of Office-Division Code File •
Office or Division Name
Technical Support Division (Cincinnati)
Program Development and Evaluation Division
Office of Grounduater Protection
Office of Marine & Estuarine Protection
Marine Operation Division
Technical Support Division
Office of wetlands Protection
-------
------- |