United States Office of Enforcement and 300-B-96-004d
Environmental Protection Compliance Assurance February 23, T936
Agency Washington DC 204610 NTIS # PB96-141569
• £EPA IDEA User's
Integrated
Data For
Enforcement
Analysis
-------
Disclaimer
The information and examples contained within this manual are strictly for training purposes,
with no basis in fact regarding any actual or ongoing enforcement initiative(s). The "screen
shots" and examples that appear in this manual are only intended to illustrate the uses and func-
tions of IDEA and do not contain enforcement sensitive information.
-------
Contents
Chapter 1. Introduction 1-1
1.1 Background of the IDEA System 1-1
1.2 Purpose of the User's Guide '. 1-2
1.3 Summary 1-3
Chapter 2. IDEA: What it Does & How it Works 2-1
2.1 What is a Query? 2-1
2.2 The Data Accessed by IDEA ! 2-2
2.3 How IDEA Processes Queries •. 2-4
2.3.1 Initial Facility Selection , . 2-6
2.3.2 Integration Process 2-6
2.3.3 Query Status 2-7
2.3.3.1 Linked Queries 2-8
2.3.3.2 Nonlinked Queries 2-9
2.3.3.3 Linked Nonlinked Queries 2-9
2.3.4 Detailed Data Retrieval : 2-9
2.3.4.1 Linked Queries i 2-10
2.3.4.2 Nonlinked Queries '. 2-11
2.3.4.3 Linked Nonlinked Queries 2-11
2.4 Data Analysis Considerations ,1 2-11
2.5 Summary . 2-12
Chapter 3;. Accessing IDEA on the EPA IBM Mainframe . 3-1
3.1 Mainframe Access 3-1
3.1.1 (])btaining an EPA Mainframe User ID and Password 3-1
3.1.2 Obtaining IDEA Authorization 3-2
3.1.3 Hardware/Software Considerations 3-2
3.1.3.1 PC on a LAN Using the SNA Gateway 3-3
3.1.3.2 Hardwired Terminal 3-3
3.1.3.3 PC or Video Terminal with Modem 3-4
3.2 Logging on to EPA's Mainframe ; 3-5
3.2.1 First Time Logon ! 3-5
3.2.2 Quick Logon Procedure 3-8
3.2.3 Password Errors 3-10
3.3 Keyboard Mappings ,: 3-10
3.3.1 Program Function (PF) Keys . . . 3-11
3.3.2 Program Attention (PA) Keys 3-12
3.4 Entering the IDEA System 3-13
3.4.1 The IDEA WELCOME SCREEN 3-14
3.5 Logging off EPA's Mainframe 3-15
3.6 Summary 3-17
Chapter 4. Conducting a Search Using the Menu Interface 4-1
4.1 IDEA Menu Categories 4-1
4.2 Using Menu Categories to Form Queries . , 4-3
4.2.1 Navigating the Menu Screens 4-4
4.2.2 Location Category 4-4
Contents V
-------
4.2.3 Pollutants Category 4-10
4.2.4 Industry Category 4-13
4.2.5 Noncompliance Category 4-16
4.2.6 Enforcement Category 4-19
4.2.7 Facility Status Category 4-21
4.3 Managing Queries 4-24
4.3.1 Clearing Queries 4-24
4.3.2 Saving Queries 4-25
4.3.3 Retrieving Queries . 4-25
4.4 Running Queries 4-26
4.4.1 Input and Report Selection Screen: Choosing Input 4-27
4.4.1.1 Linked 4-27
4.4.1.2 Nonlinked 4-27
4.4.1.3 Linked Nonlinked 4-28
4.4.2 Input and Report Selection Screen: Choosing Reports 4-28
4.4.3 Viewing the Query Reports 4-30
4.5 Exiting the IDEA Menu Interface 4-31
4.6 Summary 4-32
Chapter 5. Managing Libraries 5-1
5.1 Selecting an IDEA Library 5-1
5.2 Managing Queries Using the Member List 5-4
5.2.1 Creating a New Query 5-4
5.2.2 Looking at an Existing Query 5-5
5.2.3 Editing an Existing Query 5-6
5.2.4 Renaming an Existing Query 5-6
5.2.5 Writing/Updating a Query Description 5-7
5.2.6 Deleting a Query from the Member List 5-8
5.3 Allowing Access to your IDEA Library 5-9
5.4 Summary 5-10
Chapter 6. Conducting a Search Using GO Names . . .' 6-1
6.1 Introduction to GO Names 6-1
6.2 Using GO Names to Form Queries 6-4
6.2.1 The "Data Options" Action Bar 6-5
6.2.2 Searching for Facilities by Name 6-7
6.2.3 Searching for Facilities by Location 6-8
6.2.4 Searching for Facilities by Name and Location 6-10
6.3 Managing Queries in the ISPF Editor Mode 6-10
6.3.1 Returning a Facility List to a Query 6-11
6.3.2 Getting a Dun & Bradstreet Corporate Profile 6-12
6.4 Looking at a GO Names Query 6-13
6.4.1 Modifying a GO Names Query 6-15
6.5 Running a GO Names Query 6-17
6.6 Viewing a Query Report 6-18
6.7 Exiting GO Names 6-19
6.8 Summary 6-20
Chapter 7. Conducting a Search Using GO MenuA 7-1
7.1 Introduction to GO MenuA 7-1
7.2 Getting Started 7-1
VI IDEA User's Guide " February 29, 1996
-------
7.3 Using GO MenuA 7-4
7.3.1 Editing GO MenuA Queries 7-8
7.3.2 Combining GO MenuA and GO Names Queries 7-9
7.4 Running a GO MenuA Query 7-12
7.5 Viewing Reports 7-12
7.6 Exiting GO MenuA 7-13
7.7 Summary • • 7-14
Chapter 8. Conducting a Search Using Keywords . . 8-1
8.1 Introduction to IDEA Keywords 8-1
8.2 Using Keywords to Write Queries 8-5
8.2.1 The INPUT Statement 8-6
8.2.1.1 Using Linked and Nonlinked Keywords 8-6
8.2.2 The SELECT Statement . 8-8
8.2.2.1 Choosing a SELECT Database 8-8
8.2.2.2 Choosing a SELECT Data Element 8-9
8.2.2.3 Using a Boolean Operator 8-10
8.2.2.4 Providing SELECT Data Values 8-13
8.3 Using Boolean Connectors in a Query . . '•-.-•' 8"14
8.4 Using Parentheses in a Query 8-15
8.5 Using the TEXT command to help you build your query ...-..' 8-16
8.6 Output Report Selection 8-19
8.7 Specifying Report Destinations 8-20
8.8 Adding Comments to a Query . 8-25
8.9 JOB, ROUTE & DD Statements ,„••••• 8'25
8.10 Running a Keyword Query 5 . .:. . 8-28
8/0.1 Viewing the Query Report 8-29
8.11 Exiting Keywords 8-29
8.12 Summary j . ., 8-30
Chapter 9. Managing Keyword Queries and the ISPF Editor 9-1
9.1 Introduction to the ISPF Editor 9-1
9.2 Keyword Queries and the ISPF Line Editor 9-2
9.2.1 Inserting and Deleting Lines 9-2
9.2.2 Copying, Moving, and Repeating Lines . 9-3
9.2.3 Excluding Lines 9-6
9.2.4 Adding Comments to a Query 9-8
9.3 Using ISPF Primary Commands 9-8
9.3.1 Copying Lines From One Query to Another 9-10
9.3.2 Combining Queries 9-11
9.3.3 Deleting Excluded or Non-Excluded Lines 9-11
.9.3.4 Clearing a Query from the ISPF Editor 9-11
9.3.5 Scrolling Data : 9-12
9.4 Summary 9-14
Chapter 10. IDEA Standard Reports 10-1
10.1 Choosing a Standard Report Format 10-1
10.1.1 Report 1A 10-1
10.1.1.1 AFS Report 1A Elements 10-4
10.1.1.2 CER (CERCLIS) Report 1A Elements 10-7
10.1.1.3 DCK (Civil Docket) Report 1A Elements 10-9
Contents Vli
-------
10.1.1.4 DUN (Dun & Bradstreet) Report 1A Elements 10-13
10.1.1.5 ERN (ERNS) Report 1A Elements 10-15
10.1.1.6 FFI (FFIS) Report 1A Elements 10-17
10.1.1.7 FIN (FINDS) Report 1A Elements 10-18
10.1.1.8 LST (Contractor Listing Docket) Report 1A Elements 10-19
10.1.1.9 NCD (NCDB) Report 1A Elements 10-21
10.1.1.10 OSH Report 1A Elements 10-24
10.1.1.11 PCS Report 1A Elements 10-26
10.1.1.12 RCR (RCRIS) Report 1A Elements 10-28
10.1.1.13 TRI Report 1A Elements 10-30
10.1.2 Report IB 10-31
10.1.2.1 AFS Report IB Elements 10-34
10.1.2.2 CER(CERCLIS) Report IB Elements 10-39
10.1.2.3 DCK (Civil Docket) Report IB Elements 10-46
10.1.2.4 DUN (Dun & Bradstreet) Report IB Elements 10-50
10.1.2.5 ERN (ERNS) Report IB Elements 10-52
10.1.2.6 FFI (FFIS) Report IB Elements 10-60
10.1.2.7 FIN (FINDS) Report IB Elements 10-61
10.1.2.8 LST (Contractor Listing Docket) Report IB Elements 10-62
10.1.2.9 NCD (NCDB) Report IB Elements 10-65
10.1.2.10 OSH (OSHA) Report IB Elements 10-69
10.1.2.11 PCS (PCS) Report IB Elements 10-75
10.1.2.12 RCR (RCRIS) Report IB Elements 10-78
10.1.2.13 SET (SETS) Report IB Elements 10-83
10.1.2.14 TRI (TRIS) Report IB Elements 10-85
10.1.3 Report 2 10-87
10.1.4 Summary Report 10-89
10.2 Accessing and Navigating Reports 10-94
10.3 Printing Reports 10-97
10.4 Saving Reports 10-103
10.5 Exiting Reports 10-103
10.6 Summary 10-104
Chapter 11. IDEA User-Specified Reports 11-1
11.1 Overview of IDEA User-specified Reports (USRs) 11-1
11.2 A Basic USR Request 11-1
11.2.1 Report Layout 11-2
11.2.1.1 Elements of a Basic USR Request 11-5
11.2.1.2 The OUTPUT Statement - Requesting a USR 11-5
11.2.1.3 The Detail Line 11-6
11.2.2 Customizing a Basic USR Request 11-8
11.2.2.1 Specifying a Report Title 11-8
11.2.2.2 Controlling the Report Header 11-9
11.2.2.3 Formatting the Report Data 11-10
11.2.3 Custom USR Functions 11-13
11.3 Controlling USR Report Output 11-17
11.3.1 Restricting Report Data 11-18
11.3.2 Sorting the Report Data 11-20
11.3.3 The Summary Line 11-22
11.3.3.1 Statistical Functions 11-23
11.3.3.2 Controlling Where Summary Information Appears 11-28
VIM IDEA User's Guide February 29, 1996
-------
11.4 Requesting a USR in the Keyword Interface 11-30
11.4.1 Report Design Considerations 11-31
11.4.2 Preparing a Query in the ISPF/PDF Editor 11-32
11.4.3 Adding the USR Request to the Query 11-34
11.5 Running Queries and Viewing Reports 11-35
11.6 Printing Reports 11-38
11.7 Saving Reports 11-43
11.8 Exiting Reports 11-44
11.9 Summary 11-44
Appendix A. Access and Security Procedures for IDEA A-l
A.I Attachments A-4
Appendix B. Database Descriptions B-l
B.I AFS B-l
B.2 CER B-2
B.3 DCK B-3
B.4 DUN B-4
B.5 ERN B-5
B.6 FFI B-6
B.7 FIN B-7
B.8 LST B-8
B.9 NCD . . . . ,ft - . B-9
B.10 PCS .... t - B-9
B.ll RCR ....'? B-ll
B.12 SET ....„, s .... B-ll
B.13 TRI ' B-12
B.14 ZIP ? B-13
Appendix C. Data Elements in IDEA Shadow Files C-l
C.I AFS-AIRS Facility Subsystem Data Elements (7/95) C-2
C.2 CER-CERCLA Information System Data Elements (7/95) C-3
C.3 CRM-Criminal Docket Data Elements (7/95) C-14
C.4 DCK-Enforcement Docket Data Elements (7/95) C-15
C.5 DUN-Dun & Bradstreet Data Elements (7/95) C-l6
C.6 ERN-Emergency Response Notification System Data Elements (7/95) . . C-17
C.7 FFI-Federal Facilities Information System Data Elements (7/95) C-20
C.8 FIN-Facility Index System Data Elements (1/96) C-21
C.9 LST-Contractor Listing Docket Data Elements (7/95) C-21
C.10 NCD-National Compliance Database Data Elements (7/95) C-23
C.ll OSH-Occupational Safety & Health Administration Data Elements (7/95) C-25
C.12 PCS-Permit Compliance System Data Elements (7/95) C-29
C.I3 RCR-RCRA Information System Data Elements (7/95) C-32
C.14 SET-Site Enforcement Tracking System Data Elements (7/95) C-35
C.15 TRI-Toxic Chemical Release System Data Elements (7/95) C-36
C.16 ZIP-Census Bureau's Zip Code Data Elements (1/96) C-37
Appendix D. Error Messages for the Keyword Interface D-l
Appendix E. The Structure of the IDEA Shadow Databases E-l
E.I Skeletons of the IDEA Databases E-l
Contents IX
-------
E.2 How the underlying structure affects your Select criteria E-10
Appendix F. Accessing the User's Guide Online F-l
F.I Accessing the User's Guide in Bookmanager F-l
F.2 Printing Additional Copies of the IDEA User's Guide F-5
Glossary X-l
Index X-9
IDEA User's Guide
February 29, 1996
-------
Tables
3-1. Program Function Keys and PC/LAN SNA Gateway Key Map .... 3-11
3-2. Program Function Keys and Crosstalk/Kermit Key . . 3-12
3-3. Program Attention Keys 3-12
4-1. ISPF Commands and (default) PF Key Values in the Menu Interface . 4-3
4-2. IDEA Standard Reports 4-29
5-1. Library Member List Commands 5-4
6-1. Library Member List Commands 6-3
6-2. Line Editing Commands 6-15
6-3. ISPF Keys and Commands (default values) : . 6-16
6-4. IDEA Standard Reports 6-17
7-1. Library Member List Commands 7-3
7-2. Line Editing Commands 7-8
8-1. Library Member List Commands 8-3
8-2. ISPF Keys and Commands (default values) 8-4
8-3. Database Select Codes 8-8
8-4. IDEA Standard Reports 8-20
9-1. Line Edit Commands 9-2
9-2. Primary Edit Commands 9-9
10-1. Commands for Navigating Reports . 10-97
11-1. Levels of Hierarchy in IDEA Shadow Databases 11-2
11-2. Library Member List Commands 11-33
11-3. Line Edit Commands 11-35
11-4. Commands'for Navigating Reports . 11-38
C-l. Descriptions of Data Types C-2
E-l. Levels of Hierarchy in IDEA Shadow Databases E-ll
Tables XJ
-------
Xii IDEA User's Guide February 29, 1996
-------
Figures
2-1. IDEA Data Integration 2-5
2-2. Initial Facility Selection . . 2-6
2-3. Integration Process 2-7
2-4. Query Status Screen 2-8
2-5. Detailed Data Retrieval 2-10
3-1. U.S. Environmental Protection Agency Menu System Screen 3-4
3-2. U.S. Environmental Protection Agency Menu System Screen 3-6
3-3. EPA TSO LOGON Screen 3-7
3-4. TSO News Alert/READY Screen 3-8
3-5. U.S. Environmental Protection Agency Menu System Screen 3-9
3-6. TSO News Alert/READY Screen 3-9
3-7. TSO LOGON Screen : 3-10
3-8. IDEA Welcome Screen 3-13
3-9. Database Status Screen 3-14
3-10. OE Data Integration Primary Menu 3-16
3-11. LOG/LIST Screen ! 3-17
3-12. READY Prompt Screen 3-17
4-1. Interface Selection Screen ,; 4-1
4-2. Main Menu Interface Screen 4-2
4-3. Menu Interface with Location Category 4-5
4-4. Location Category with Region codes . , 4-6
4-5. Location Category with County Codes 4-7
4-6. County Codes and Clear command 4-8
4-7. Menu Interface with selected ZIP Code 4-9
4-8. The map of EPA Region 8 4-10
4-9. Menu Interface with Pollutant Category . 4-11
4-10. Menu Interface with Industry Category 4-14
4-11. Industry Category: Searching for SIC Range of Mining Industry ... 4-15
4-12. Industry Category: Selecting SICs of Metal Mining Industry 4-16
4-13. Menu Interface with Noncompliance Category 4-17
4-14. Menu Interface with Enforcement Category 4-19
4-15. Menu Interface with Facility Status Category 4-22
4-16. Query Retrieval Screen 4-25
4-17. Input and Report Selection Screen 4-26
4-18. Query Status Screen ; 4-30
4-19. Report 1A 4-31
5-1. Interface Selection Screen 5-1
5-2. Input Library Selection Screen 5-2
5-3. Member List Screen 5-3
5-4. Edit Screen i 5-5
5-5. Browse Screen 5-6
5-6. Member List Screen - Renaming a Member 5-7
5-7. Edit Member Screen - Updating a Description 5-8
5-8. Member List Screen - Deleting a Member 5-9
5-9. READY Screen - RACF Commands . 5-10
6-1. Library Selection Screen 6-2
6-2. Member List Screen 6-3
Figures xiii
-------
6-3. Edit Screen 6-4
6-4. GO Names Selection Screen 6-5
6-5. Selection Screen Data Options 6-6
6-6. GO Names Facility Count Returns 6-11
6-7. Dun & Bradstreet Keywords 6-13
6-8. A GO Names Query in the Edit Screen 6-14
6-9. Query Status Screen 6-18
6-10. Report 1A in Browse Mode 6-19
7-1. Input Library Selection Screen 7-2
7-2. Member List Screen 7-3
7-3. Blank Edit Screen 7-4
7-4. Main Menu Screen 7-5
7-5. Noncompliance Criteria in the Menu Interface 7-6
7-6. Edit Screen with keyword logic 7-7
7-7. Name Selection Menu Screen 7-9
7-8. Edit Screen with Names Keywords , 7-10
7-9. Edit Screen with changes shown 7-11
7-10. Query Status Screen 7-12
7-11. Report 1A in Browse Mode 7-13
8-1. Input Library Selection Screen 8-2
8-2. Member List Screen 8-3
8-3. Edit Screen 8-4
8-4. Example Keyword Query 8-5
8-5. Top of Decoding Tables List 8-17
8-6. Bottom of Decoding Tables List 8-17
• 8-7. Top of TRI.TCID Decoding Table 8-18
8-8. Code for TRI.TCID for Toluene 8-19
8-9. SDSF Primary Option Menu Screen 8-21
8-10. SDSF Output Queue Screen 8-22
8-11. SDSF Output Queue Screen - "Command Issued" 8-23
8-12. SDSF Output Queue Screen - Print Destination Changed 8-24
8-13. Query Status Screen 8-28
8-14. Report 1A (Browse Mode) 8-29
8-15. Example Keyword Query 8-30
9-1. Edit Screen 9-1
9-2. Query Lines Excluded From Display 9-7
9-3. Edit Screen With Scroll Prompt 9-12
10-1. DBA Standard Report 1A 10-3
10-2. AFS Report 1A Elements 10-4
10-3. CER (CERCLIS) Report 1A Elements 10-7
10-4. DCK (Civil Docket) Report 1A Elements 10-9
10-5. DUN (Dun & Bradstreet) Report 1A Elements 10-13
10-6. RN (ERNS) Report 1A Elements 10-15
10-7. FFI (FFIS) Report 1A Elements 10-17
10-8. FIN (FINDS) Report 1A Elements 10-18
10-9. LST (Contractor Listing Docket) Report 1A Elements 10-19
10-10. NCD (NCDB) Report 1A Elements 10-21
10-11. OSH Report 1A Elements 10-24
10-12. CS Report 1A Elements .' 10-26
10-13. RCR (RCRIS) Report 1A Elements 10-28
10-14. TRI Report 1A Elements '. 10-30
Xiv IDEA User's Guide February 29, 1996
-------
10-15. IDEA Standard Report IB 10-32
10-16. AFS Report IB Elements 10-34
10-17. CER (CERCLIS) Report IB Elements 10-39
10-18. DCK (Civil Docket) Report IB Elements 10-46
10-19. DUN (Dun & Bradstreet) Report IB Elements 10-50
10-20. ERN (ERNS) Report IB Elements 10-52
10-21. FFI (FFIS) Report IB Elements 10-60
10-22. FIN (FINDS) Report IB Elements . . .". : 10-61
10-23. LST (Contractor Listing Docket) Report IB Elements 10-62
10-24. NCD (NCDB) Report IB Elements . 10-65
10-25. OSH (OSHA) Report IB Elements . . 10-69
10-26. PCS (PCS) Report IB Elements 10-75
10-27. RCR (RCRIS) Report IB Elements 10-78
10-28. SET (SETS) Report IB Elements . . . . 10-83
10-29. TRI (TRIS) Report IB Elements 10-85
10-30. IDEA Standard Report 2 '. 10-87
10-31. IDEA Standard Summary Report . . 10-91
10-32. Summary Report (Continued) 10-92
10-33. Query Status Screen 10-95
10-34. An Example of Report 1A 10-96
10-35. Report 1A 10-98
10-36. Print Save Parameter Screen 10-99
10-37. SDSF Primary Option Menu Screen 10-100
10-38. SDSF Output Queue Screen 10-101
10-39. SDSF Output Queue -"'Command Issued" Screen 10-102
10-40. SDSF Output Queue - Print Destination Changed Screen 10-102
11-1. Data elements requested in USR 11-3
11-2. IDEA User Specified Report Output 11-4
11-3. The IDEA Report Boilerplate 11-6
11-4. USR with Customized Title . . 11-8
11-5. The IDEA USR Header .' 11-9
11-6. Simple USR with Title and Formatting 11-12
11-7. Simple USR with Title and Formatting 11-13
11-8. Example of Use of ENFACTS 11-14
11-9. Using the Text function 11-15
11-10. TEXT INFO Command 11-16
11-11. Top of Decoding Tables List 11-17
11-12. RESTRICT Keyword Section 11-19
11-13, Use of Restrict Keyword 11-20
11-14. Sorting by Reporting Year, then Chemical 11-21
11-15. Sorting by Chemical, then Reporting Year 11-22
11-16. Using COUNTQ on the Summary Line 11-25
11-17, USR With Request for Summary Information 11-27
11-18. USR Output With Summary Information 11-28
11-19. Example USR With Detail Line Suppressed 11-30
11-20. Library Selection Screen 11-32
11-21. Member List Screen • 11-33
11-22. Example Query in the ISPF Edit Screen 11-34
11-23. Query Status Screen 11-36
11-24. Viewing a USR in Browse Mode 11-37
11-25. A "Complete" USR 11-39
Figures XV
-------
11-26. Print/Save Parameter Screen 11-39
11-27. SDSF Primary Option Menu Screen 11-41
11-28. SDSF Output Queue Screen 11-41
11-29. SDSF Output Queue - "Command Issued" Screen 11-42
11-30. SDSF Output Queue - Print Destination Changed Screen 11-43
A-l. Attachment 1 A-6
A-2. Attachment 2(a) - Sample EPA Regional memorandum A-7
A-3. Attachment 2(b) - Sample EPA Headquarters Program Office
Memorandum A-8
A-4. Attachment 2(c) - Sample Office of Enforcement Memorandum . . . A-9
A-5. Attachment 2(c) - Sample EPA Contractor Employee Memorandum A-10
E-l. AFS Database Skeleton E-3
E-2. CRM Database Skeleton E-3
E-3. DCK Database Skeleton E-4
E-4. DUN Database Skeleton E-4
E-5. ERN Database Skeleton E-5
E-6. FFI Database Skeleton E-5
E-7. FIN Database Skeleton E-6
E-8. LST Database Skeleton E-6
E-9. NCD Database Skeleton E-7
E-10. OSH Database Skeleton E-7
E-ll. PCS Database Skeleton E-8
E-12. RCR Database Skeleton E-9
E-13. SET Database Skeleton E-9
E-14. TRI Database Skeleton . .' E-10
E-15. Select Criteria consulting two databases E-ll
E-16. User-specified Report—Two facilities E-12
E-17. Select criteria limited to FFIS E-13
E-18. User-specified Report—One facility E-14
E-19. Select criteria with parentheses reversed E-15
E-20. Query Status Screen-No facilties E-15
F-l. The books command F-l
F-2. The EPA SOFTCOPY LIBRARY MAIN PANEL . -, F-2
F-3. Environmental Bookshelves F-2
F-4. The IDEA Bookshelf F-3
F-5. Table of Contents of the IDEA User's Guide F-4
F-6. Documents available for printing F-5
F-7. EPA Print Routing Screen F-6
XVi IDEA User's Guide
February 29,1996
-------
-------
IDEA User's Guide
February 29, 1996
-------
Chapter 1. Introduction
This chapter provides a brief description of the background of IDEA, its intended
use, and the basic features of the IDEA User's Guide.
1.1 Background of the IDEA Svstem
The Integrated Data for Enforcement Analysis (IDEA) System has been developed in
response to an identified need for integrated data on facilities that may be involved in
EPA enforcement or compliance actions. Historically, data systems within EPA
program offices were developed to manage data related to the individual programs
and associated legislation. In most cases, these data systems were developed without
any centralized coordination. As a result, the data management systems in the
program offices operate on different hardware platforms and software environments.
Agency standards for identifying facilities by name:, location, or identification number
either did not exist, or were not actively enforced. Often the individual program
offices tracked data on the same facilities without an easy way to cross-reference or
link the data.
The General Accounting Office (GAO) and the EPA Inspector General (IG) noted
the need for the Agency to be able to link facility data across all EPA program office
databases. This deficiency was also identified by ElPA's top management as an Office
of Enforcement material weakness under the Federal Managers Financial Integrity
Act (FMFIA). At a meeting of the Enforcement Management Council of EPA in
early 1990, the Council members began the strategic planning process to develop
multi-media approaches to environmental problems.
To support the multi-media approach to the analysis of environmental problems, the
EPA Headquarters Office of Enforcement designed, the IDEA System to retrieve data
about facilities across program office databases. For example, the Agency can more
easily target inspection resources where they are likely to be needed most if integrated
data are available on air quality, water quality, solid and hazardous waste, toxic sub-
stances, and EPA enforcement actions for specific facility locations. If EPA is initi-
ating an enforcement action on water quality, data on other media and other actions
will help to define and possibly expand the current enforcement action. IDEA was
developed to assist enforcement personnel as a preliminary screening device and an
aid to targeting facilities for enforcement initiatives. IDEA can be employed for
numerous tasks. The following are examples of the types of assistance IDEA offers:
• Enforcement Case Screening:
Chapter!. Introduction 1-1
-------
Identify the Multi-Media Enforcement Profile for a specified facility or company.
Case Development
Litigation Support
Settlement Negotiations
Enforcement/Inspection Targeting:
Identify compliance monitoring/enforcement candidates for an industry-specific
enforcement initiative.
Identify compliance monitoring/enforcement candidates for a discharge reduction
initiative of a specific pollutant.
Develop a facility inventory for a geographically defined environmental assess-
ment.
Management Decision Making
1.2 Purpose of the User's Guide
The IDEA User's Guide is intended to aid and instruct users of Integrated Data for
Enforcement Analysis (IDEA) by explaining procedures for accessing the system,
building queries, retrieving data, and obtaining and understanding reports.
The IDEA User's Guide is organized to lead you step by step through using and
understanding the system. Chapter 1, Introduction through Chapter 3, Accessing
IDEA on the EPA IBM Mainframe provide background information on IDEA that is
necessary for understanding how IDEA operates and how to access it. Chapter 4,
Conducting a Search Using the Menu Interface through Chapter 9, Managing Keyword
Queries and the ISPF Editor provide detailed information on IDEA'S query building
tools. These chapters on query building are modular in design so users can find
enough basic information in each to go from start to finish without having to refer to
other sections of the manual. Chapter 5, Managing Libraries, Chapter 9, Managing
Keyword Queries and the ISPF Editor, Chapter 10, IDEA Standard Reports, and
Chapter 11, IDEA User-Specified Reports were designed to give users more detailed
information on managing libraries, the ISPF editor, and IDEA Reports. IDEA users
1-2 IDEA User's Guide February 29, 1996
-------
will need to refer to the appendices for access and. security procedures, detailed infor-
mation on database descriptions, data elements uised by IDEA, and error messages.
1.3 Summary
IDEA was developed in response to a defined need for data integration across various
EPA program office databases. This integration is essential for a multi-media
approach to the analysis of environmental problems.
This manual is designed to facilitate the use of IDEA by new and experienced users.
It contains detailed information on IDEA'S design features, query building, and
IDEA reports.
Chapter 1. Introduction 1-3
-------
1-4 IDEA User's Guide February 29, 1996
-------
Chapter 2. IDEA: What it Does & How it Works
Considerations for forming an IDEA query are explained in this chapter.
2.1 What is a Query?
By definition, a query is a question. In IDEA, a query is a tool you can use to access
vast amounts of information. After you form a query, IDEA goes to work retrieving
information and returns it to you in the form of am IDEA report.
When you construct an IDEA query, you select the criteria that IDEA will use for its
search. While choosing parameters for your query, keep in mind that the data
accessed by IDEA are organized by facility. This arrangement allows you to search
for a facility according to its name, location, the chemicals it releases, and other cri-
teria available in the linked IDEA databases.
IDEA queries can be very simple or extremely complicated, depending on your objec-
tive. When forming a query, consider your goal and ask yourself the following
questions:
• How will the report data be used?
• What criteria are integral to the search?
• What criteria can be used to help narrow the search?
Forethought in the formation of your queries will help you to retrieve the information
you need in a useful report. The following sections illustrate the way IDEA collects
data. Each section includes explanations designed to give you an understanding of
how to perform searches and effectively retrieve data from IDEA. The second part of
this manual will teach you how to use IDEA to access information.
IDEA allows you to choose between two types of searches: facility screening or tar-
geting. Facility screening refers to the process of searching for a particular facility or
facilities by name. This type of search can only be done with the GO Names utility
of the Keyword Interface. Targeting, on the other hand, refers to the process of
searching for facilities according to criteria you set. This task can be performed by
Chapter 2. IDEA: What it Does & How it Works 2-1
-------
using the Keyword Interface or the Menu Interface, depending on your experience
with IDEA and the ISPF Editor.
IDEA query building options:
The Menu Interface, discussed in Chapter 4, Conducting a Search Using the Menu
Interface, is the simplest means of retrieving facility data from IDEA. It is structured
to provide options and convenient "pop-up" windows that allow you to form queries
by simply choosing from the different criteria. This interface also makes some choices
about the logical construction of the query for you.
GO Names, explained in Chapter 6, Conducting a Search Using GO Names, allows
you to generate queries in a structured environment and to edit them in the Keyword
Interface EDIT SCREEN. By entering the facility name and/or location (EPA
Region, state, zip code, or county), you can form a query that will retrieve facility
data, including corporate profile data.
GO MenuA, covered in Chapter 7, Conducting a Search Using GO MenuA, is a utility
in the Keyword Interface that allows you to build a query in the Menu Interface and
edit it in the Keyword Interface EDIT SCREEN. This utility gives you the conven-
ience of the Menu Interface and the option to edit the logical construction of the
query using the powerful Keyword Interface.
Using the IDEA Keyword Interface, described in Chapter 8, Conducting a Search
Using Keywords, is more demanding than the other options, but it provides you with
more flexibility than they do. The Keyword Interface allows you to retrieve facility
data according to any criteria in the databases indexed by IDEA. Thus, you can
form very specific and detailed queries. However, to use the Keyword Interface effec-
tively you must understand the command syntax and possess some knowledge of the
data systems accessible through IDEA.
2.2 The Data Accessed bv IDEA
No new data are created by IDEA. With the exception of CERCLIS, data are copied
from the source databases and are reformatted so they can support high-speed
retrievals.
IDEA currently provides access to data from the following databases:
AFS AIRS Facility Subsystem (Office of Compliance),
2-2 IDEA User's Guide February 29, 1996
-------
CERCLIS CERCLA Information System (Officfe of Solid Waste and Emergency
Response),
CRM
Criminal Docket (Office of Criminal Enforcement),
DOCKET Civil Enforcement Docket (Office of Compliance),
DUNS Dun & Bradstreet Market Identifiers (Office of Information Resources
Management),
ERNS Emergency Response Notification System (Department of Transporta-
tion),
FFIS Federal Facility Information System (Office of Federal Facilities Enforce-
ment),
FINDS Facility Index System (Office of Infomiation Resources Management),
LST
Contractor Listing Docket (Office of Compliance),
NCDB National Compliance Database (Office of Compliance),
OSHA Occupational Safety and Health Administration (U.S. Department of
Labor),
PCS
Permit Compliance System (Office of Compliance),
RCRIS RCRA Information System (Office of Solid Waste and Emergency
Response),
SETS Site Enforcement Tracking System (Office of Compliance), and
TRIS Toxic Chemical Release Inventory System (Office of Pollution Prevention
and Toxic Substances).
See Section 8.2.2.1, Choosing a SELECT Database of Chapter 8, Conducting a Search
Using Keywords for general descriptions of the data in each of these databases.
Appendix B, Database Descriptions also contains brief descriptions of these databases
and how to reach user assistance for each. Appendix C, Data Elements in IDEA
Shadow Files provides a list of the data elements in the IDEA copies of the databases.
Chapter 2. IDEA: What it Does & How it Works
2-3
-------
Note: When analyzing data retrieved by IDEA, it is important to understand that
the data comes from copies of EPA program office databases and other gov-
ernment agency systems. Although the Office of Enforcement updates these
copies monthly, some data might be out of date. You can access a list of the
databases and the days of their most recent updates from the IDEA
WELCOME SCREEN, shown in Figure 3-8 of Section 3.4, Entering the IDEA
System, by typing D at the COMMAND prompt and pressing < Enter >.
2.3 How IDEA Processes Queries
The principal utility of IDEA is its ability to access and integrate enforcement data
on facilities across EPA program office databases in addition to data systems main-
tained by other government agencies.
Suppose you are interested in retrieving data on facilities classified as current Signif-
icant Noncompliers and Violators in AFS (the AIRS Facility Subsystem contains
data on stationary sources of airborne pollution), PCS (the Permit Compliance
System tracks permits for the National Pollutant Discharge Elimination System
(NPDES) under the Clean Water Act), and High Priority Violators in RCRIS (the
RCRA Information System tracks hazardous waste handlers under RCRA). IDEA
will locate facilities that meet these criteria in all three databases.
Figure 2-1 below illustrates the way IDEA integrates data. The intersection repres-
ents those facilities that are current Significant Noncompliers and Violators in all
three databases. IDEA allows you to retrieve facility data on the intersection. To
get the same information without using IDEA, you would have to retrieve the
noncompliers from each database separately and compare the three lists to determine
the common set of facilities. Searching each program office database for a multi-
media targeting effort becomes difficult to manage beyond two or three databases.
IDEA provides rapid access to integrated data from multiple EPA program office
databases.
2-4 IDEA User's Guide February 29, 1996
-------
Intersection
Figure 2-1. IDEA Data Integration
There are three data retrieval (or input) options available to you in IDEA.
• Linked,
• Nonlinked, and
• Linked Nonlinked.
If you choose the Linked option, IDEA will attempt to integrate facility data selected
from multiple EPA databases using the Facility Index System (FINDS) as a cross-
referencing mechanism. However, if you specify Nonlinked data, IDEA will retrieve
data on facilities within each program office database that is relevant to your query
without any attempt to integrate the data from the different sources. In Linked Non-
linked queries, IDEA selects facilities that meet query criteria in the different data-
bases then it attempts to link facilities using FINDS but also reports on the facilities
that were not in FINDS.
The data retrieval process is explained below in the context of an example query,
which will report on facilities that are:
• RCRA Generators AND
• PCS Major Dischargers AND
Chapter 2. IDEA: What it Does & How it Works
2-5
-------
located in Maine (FINDS).
2.3.1 Initial Facility Selection
IDEA searches each database in turn and retrieves the "local" IDs (IDs native to the,
databases) of facilities that match the query criteria. When the example above is run,
IDEA searches RCRIS, PCS, and FINDS for facilities that are Generators, Major
Dischargers, and located in Maine, respectively. See Figure 2-2 for an illustration of
this step.
Databases
Groups of
Local IDs
Selected
RCRIS J
*
RCR.IDS
of
Generators
f PCS J [ FINDS J
i
r •
PCS.IDS
of Major
Dischargers
f
EPA-IDs
of facilities
located in
Maine
Figure 2-2. Initial .Facility Selection
Note: Nonlinked queries ignore FINDS. When the example query is run as a Non-
linked query, IDEA does not search the FINDS database. Since there is no
mechanism for comparing these facilities without FINDS, Boolean connectors
are not applied to Nonlinked searches; so Figure 2-3, Integration Process
applies only to Linked and Linked Nonlinked queries.
2.5.2 Integration Process
When IDEA integrates facility data, a two step process is involved. Once IDEA has
gathered the local IDs for the facilities selected in Linked and Linked Nonlinked
queries, it uses FINDS to locate EPA IDs for them. Then IDEA applies the Boolean
connectors for the query. If the example query were run Linked or Linked Non-
linked, IDEA would use FINDS to locate the EPA IDs for the facilities selected from
RCRIS and PCS (the FINDS facilities already have EPA IDs) then it would compare
the facilities to find the ones that met all of the query criteria. In order to meet all of
the query criteria, a facility would have to be a RCRA Generator AND a PCS Major
Discharger AND be located in Maine according to FINDS. Refer to Figure 2-3
below.
2-6
IDEA User's Guide
February 29, 1996
-------
Groups of
Local IDs
Selected
Local IDs
Converted
to EPAJDs
(where
possible)
Boolean
Connectors
Applied
RCR.IDS
of
Generators
. Jf US.ILJS
of Major
Dischargers
of facilities
/EPJLIDs
[(for facilities
EPA.ID
(for facilities
FINDS)
EPA.ID
(for facilities
FINDS)
(for facilities
not
(for facilities
not
in FINDS)
Figure 2-3. Integration Process
Note: FINDS serves dual purposes in IDEA. As a database, it is searched when
part of the query criteria has to do with the location of a facility. In Linked
and Linked Nonlinked queries, it is also used as a cross-referencing mechanism
to locate the EPA IDs of facilities selected from other databases.
2.3.3 Query Status
At this point, IDEA will display the QUERY STATUS SCREEN (see Figure 2-4)
showing the number of facilities found that match the query. Although the content
generally remains the same, the appearance of this screen differs for Linked, Non-
linked, and Linked Nonlinked queries.
Chapter 2. IDEA: What it Does & How it Works
2-7
-------
r,i- jv'-s-.. • < .<<
-------
FINDS. In other words, the 596 facilities excluded make up eight percent of the total
number of facilities in PCS that are Major Dischargers. This means that 92 percent
of the Major Dischargers are in FINDS and were evaluated according to all of the
query criteria. Of the 92 percent of PCS facilities evaluated (approximately 6854
facilities), 796 of them meet all the query criteria, Seven hundred and ninety-six facil-
ities that are Major Dischargers in PCS and in FINDS are also Generators in RCRIS
and located in Maine.
2.3.3.2 Nonlinked Queries
Nonlinked queries ignore FINDS; therefore, the QUERY STATUS SCREEN for
these queries simply displays the total number of facilities that were selected and the
"counts" or number selected from each program office database. Because these
queries do not attempt to integrate facility data, Nonlinked queries select more facili-
ties than the other query types. When the example query is run Nonlinked, 282,495
facilities are selected as opposed to 796 for Linked and a total of 3873 (those in
FINDS and not in FINDS) for Linked Nonlinked.
2.3.3.3 Linked Nonlinked Queries
Since these queries are combinations of Linked and Nonlinked queries, the QUERY
STATUS SCREEN for them shows the number of facilities selected that are in
FINDS (line 1) and those not in FINDS (line 2) as well as the counts and percent-
ages for each database searched (lines 5 to 8).
2.3.4 Detailed Data Retrieval
Before presenting you with a report containing data on the facilities selected from the
query, IDEA must first retrieve the data. The amount of work IDEA has done up to
now is small in comparison to the work it will do in the next step when it performs
the detailed data retrieval. This process differs for Linked, Nonlinked, and Linked
Nonlinked queries.
Chapter 2. IDEA: What it Does & How it Works 2-9
-------
EPAJDs of facilities
for which report(s)
will be generated
Sample FINDS
Pointers
EPA
Databases
EPA.IDS of
facilities selected
and in FINDS
EPA.ID = MED000791681
RCR.ID =MED000791681
PCS.ID =MEQQ022764
PCS.ID =ME00022861
AFS.ro =2303100002
TRI.ro = 03906PRTTWROUTE
JLST
CDTJNS) (FESTDS) CPCS
(NCDB)
Figure 2-5. Detailed Data Retrieval
2.3.4.1 Linked Queries
For Linked queries, IDEA retrieves data only for the facilities that are in FINDS and
meet the query criteria. As illustrated in Figure 2-5, IDEA looks up the FINDS
record on each facility for which it has an EPA ID. Among other data, the FINDS
record contains the IDs (if they exist and are linked in FINDS) for the facility in the
program office databases. These program office database IDs or "local" IDs are
"pointers" -- they point to locations where more data on the facility can be found.
During the detailed data retrieval, IDEA pulls up report data for the facility from
each of the databases to which it is linked in FINDS, whether or not these databases
were searched as part of the initial facility selection.
2-10
IDEA User's Guide
February 29, 1996
-------
2.3.4.2 Nonlinked Queries
Figure 2-5, Detailed Data Retrieval does not apply to Nonlinked queries. Because
these queries ignore FINDS entirely, IDEA retrieves data on the facilities from the
program office databases searched in the query — one at a time. If the example query
were run Nonlinked, the initial facility selection would take place, as illustrated in
Figure 2-2, then the report data would be retrieved separately for the facilities
selected from RCRIS and PCS.
2.3.4.3 Linked Nonlinked Queries
In the case of Linked Nonlinked queries, IDEA retrieves data on facilities that meet
the query criteria and would be selected by a Linked query (i.e., are in FINDS) then
the ones that would have been excluded from the: Linked query (i.e., are not in
FINDS). For the facilities selected by the Linked portion, the detailed data retrieval
looks like Figure 2-5 . IDEA pulls report data up from each of the databases that
are linked to the facility in FINDS whether or not these databases were part of the
query. It groups the data retrieved in this part by facility. For the Nonlinked facili-
ties, IDEA only retrieves data from the program office databases that were searched
in the query -- one at a time. Data reported from this section are grouped by data-
base.
2.4 Data Analysis Considerations
It is important to keep in mind that IDEA has been designed primarily to provide
factual information to experienced enforcement personnel for enforcement targeting,
case screening, case development, litigation support, and settlement negotiations.
Because each program office database management system is unique, knowledge of
statutory provisions, program definitions, and data relationships as well as sound pro-
fessional judgement are essential to accurately interpret the information retrieved.
It is very easy to misinterpret the information obtained through IDEA. The data
accessed by IDEA are useful subsets of information on each program's performance.
To arrive at accurate conclusions about performance, however, one must rely on non-
automated information, such as discussions with appropriate EPA Headquarters,
regional enforcement program, and state personnel. The automated data systems
accessible through IDEA do not contain all of the information that an individual
needs in order to accurately assess program performance or the environmental status
or significance of a particular facility, corporation, or industry.
Chapter 2. IDEA: What it Does & How it Works 2-11
-------
IDEA is not intended to replace any automated EPA information system or reporting
procedures. Existing quality assurance/quality control procedures for each program
information system will not be duplicated or altered. For management accountability
reports and other official displays of quantitative enforcement information (e.g.,
tallies of administrative actions), the Office of Enforcement will continue to rely on
EPA's Strategically Targeted Activities for Results System (STARS) reporting
process. The quantitative STARS reports are based on well-established state and
regional reporting processes, data retrieval dates, and discrepancy reconciliation proc-
esses that cannot be duplicated or replaced by IDEA.
The selection criteria utilized by IDEA is based on EPA's subjective assessment of the
types of information that will be most useful in analyzing or predicting behavior. In
the absence of an agreed upon objective basis for developing these rankings and eval-
uating their accuracy, public release or misuse of any rankings could unfairly identify
a regulated entity as being among the nation's worst polluters. It would be extremely
time consuming and expensive to develop a consensus set of subjective criteria that
could be used in the ranking of sources. The Office of Enforcement does not consider
this a useful approach to EPA's targeting efforts. Rather than focus on a list, we
believe the analysis should be an interactive process in which one selects various
objective criteria and places data in the context of other information to meet the par-
ticular goal of a targeting exercise (e.g., industry or pollutant tailored to a particular
area or environmental problem).
2.5 Summary
In order to construct an effective IDEA query, it is important to have a clear set of
objectives and to select an appropriate procedure for executing the query. IDEA'S
principal utility is its ability to integrate data from these databases. New data is not
created in IDEA. For the most part, the system accesses copies of the original data-
bases. When analyzing data, consult EPA Headquarters, regional enforcement
program, state personnel, and nonautomated information sources.
2-12 IDEA User's Guide February 29, 1996
-------
Chapter 3. Accessing IDEA on the EPA IBM Mainframe
This chapter instructs users on how to access EPA's IBM mainframe computer and
describes the hardware/software requirements needed for this access. Additionally,
users are instructed on how to access IDEA.
3.1 Mainframe Access
IDEA runs on EPA's IBM mainframe computer at the National Computer Center
(NCC) in Research Triangle Park (RTF), North Carolina. The IBM mainframe is the
computer platform for most of the program office databases. It provides the
resources and performance required to meet the on-line interactive requirements for
IDEA.
To use IDEA, you first must have access to the EPA IBM mainframe computer.
Specifically, you must have a mainframe user ID and password. You must also have
authorization to gain access to the IDEA system, and an appropriate
hardware/software link to the mainframe.
For detailed information on gaining access to the IBM mainframe, see the EPA
Guide to NCC Services, issued by the Office of Administration and Resources Man-
agement (OARM), National Data Processing Division (NDPD), Research Triangle
Park (RTP), NC 27711. This document may be obtained by contacting NCC User
Support at the number listed below.
NCC User Support
(800) 334-2405 (outside NC)
(919) 541-7862 (in NC)
Dial "0" to talk to a Customer Call Center representative.
3.1.1 Obtaining an EPA Mainframe User ID and Password
• If you are an EPA employee who does not have a user ID with the NCC, contact
your Automated Data Processing (ADP) Coordinator. ADP Coordinators estab-
lish accounts, register users, and control the expenditure of time sharing funds.
Your ADP Coordinator will obtain a user ID and password for you under a new
or existing account. If you do not know who your ADP Coordinator is, call the
appropriate NCC User Support number above.
Chapter 3. Accessing IDEA on the EPA IBM Mainframe 3-1
-------
If you are a State employee, contractor, or other Agency affiliate who does not
have a user ID, contact your EPA representative to obtain one. If you do riot
have an EPA contact, call The National Technical Information Service (NTIS) at
703-487- 4630.
3.7.2 Obtaining IDEA Authorization
Once you have a mainframe user ID, you will need to request additional authori-
zation to gain access to IDEA. To do so, submit a memorandum to the Office of
Compliance (Enforcement Planning, Targeting and Data Division) at EPA Headquar-
ters. For further guidance and sample memoranda, refer to Appendix A, Access and
Security Procedures for IDEA.
3.1.3 Hardware I Software Considerations
To communicate with the IBM mainframe computer at the NCC, you must have one
of the following:
• IBM 3270 or compatible terminal
• DEC VT100 that can emulate an IBM 3270 full screen terminal
• personal computer with software that can emulate one of these terminals.
Communication may be through a long distance, high-speed link that is connected
directly to the mainframe or through a modem connection established by dialing into
the mainframe through a telephone line. IDEA cannot be accessed with a TTY (tele-
type) terminal.
As part of setting up your NCC account, your ADP Coordinator or EPA contact,
can assist you in establishing a communications link to the NCC. If you have
questions about the telecommunications link to the NCC, call NCC User Support at
the number listed in Section 3.1, Mainframe Access .
3-2 IDEA User's Guide February 29, 1996
-------
3.1.3.1 PC on a LAN Using the SNA Gateway
Most EPA personnel use a personal computer (PC) attached to a Local Area
Network (LAN) to access the NCC. Most LANs go through the SNA Gateway to
access EPA's mainframe. Because each LAN can be configured differently, contact
your local LAN Administrator should you need assistance. The following are general
instructions for gaining access to the mainframe.
1. From the AUTOMAXX WORKSTATION MENU SCREEN, select the COMMU-
NICATIONS option by pressing the Function (F) key associated with this option.
2. From the COMMUNICATIONS MENU SCREEN, select the 3270 EMU-
LATION or MAINFRAME/3090 ACCESS option by pressing the Function (F)
key associated with this option.
3. From the 5270 EMULATION SCREEN or MAINFRAME/3090 ACCESS
SCREEN, select the MOD 2 -SCREEN SIZE - 24 x 80 option by pressing the
Function (F) key associated with this option.
4. A CONTROL PROGRAM NOW RESIDENT SCREEN will be displayed indi-
cating special keys to be used in your mainframe processing session. You should.
make note of these keys. Usually you will be instructed to simultaneously press
the left < Alt > and < Page Up > keys to switch from the LAN to Mainframe
Mode. Refer to Section 3.2, Logging on to EPA's Mainframe for additional
instructions on keyboard mappings.
3.1.3.2 Hardwired Terminal
A hardwired terminal is a terminal that is linked directly to the EPA mainframe. Spe-
cifically, your terminal is connected with direct-line cables and a full-screen session is
already established. A hardwired terminal does not require dialing through the tele-
phone lines or using the AUTOMAXX WORKSTATION MENU to access the NCC.
To establish the link:
• Make sure that your terminal is turned on. The U.S ENVIRONMENTAL PRO-
TECTION AGENCY MENU SYSTEM SCREEN (see Figure 3-1) will be dis-
played. If it is not, press the < Reset > or < JEnter > key and the screen should
appear, or turn the terminal off then on again. If it does not appear, call NCC
User Support at the number listed in Section 3.1, Mainframe Access
Chapter 3. Accessing IDEA on the EPA IBM Mainframe 3-3
-------
,. - ^s^v^i^^sit^v,^'^^
s_i i 11* j*t ji*;*; ? {[jt (jVqe HJ j {t = ?f ^ ^S *j*r t " ! *
Figure 3-1. U.S. Environmental Protection Agency Menu System Screen
Refer to Section 3.2, Logging on to EPA's Mainframe for additional instructions.
3.1.3.3 PC or Video Terminal with Modem
Dial-up terminals, often called line terminals, can be linked to the EPA mainframe in
a variety of ways. The common denominator is the modem which requires you to
dial a telephone number before the link is complete.
Modems are the dialing hardware which link the telephone line to your terminal.
Getting your modem's "attention" through your keyboard may require help from
someone at your site who is familiar with your modem and terminal. Along with the
modem, you need some type of telecommunications software (for example, Crosstalk
or PROCOMM).
Since there is a wide variety of communications packages and modems that can be
used, you should refer to your hardware/software documentation for specific
instructions. There are, however, some general guidelines that apply to all types of
communication with the EPA mainframe:
• You may dial-up at either 1200, 2400 or 9600 baud.
3-4
IDEA User's Guide
February 29, 1996
-------
Your communication software should emulate a VTlOO-type terminal.
Communication parameters should be 7 data bits, 1 stop bit, even parity and full
duplex.
You must now determine what telephone number you must dial for access. If your
local sources do not have this information, call the National Computer Center,
Network Control Facility:
NCC Network Control Facility
(800) 445-2795 (outside NC)
(202) 488-2795 (DC Area)
Refer to Section 3.2, Logging on to EPA's Mainframe for additional instructions.
3.2 Lossins on to EPA's Mainframe
Once you have established a link to EPA's mainframe, it is necessary to "logon" to
the system. These instructions assume that you have a valid 3-character user ID and
a password.
3.2.1 First Time Logon
1. The U. S. ENVIRONMENTAL PROTECTION AGENCY MENU SYSTEM
SCREEN (see Figure 3-2) will appear once you have established a link to EPA's
mainframe.
Chapter 3. Accessing IDEA on the EPA IBM Mainframe 3-5
-------
l^HiX.i'^i^lsi.^^
Figure 3-2. U.S. Environmental Protection Agency Menu System Screen
2. At the COMMAND prompt, type TSO (for Time Sharing Option), and press the
< Tab > key to move the cursor to the USERID prompt. Type your three char-
acter user ID and press the < Tab > key again to move the cursor to the PASS-
WORD prompt. Type your password and press < Enter >.
Since this is your first logon with a new user ID, the TSO/E LOGON SCREEN
(see Figure 3-3) will appear. The message PASSWORD EXPIRED will appear
in either the upper right hand corner of the screen or on the second line of the
screen, and the cursor will be positioned at the NEW PASSWORD prompt.
3-6
IDEA User's Guide
February 29, 1996
-------
Figure 3-3. EPA TSO LOGON Screen
3. At the NEW PASSWORD prompt, type a password of your own selection (for
security reasons your entry will not be displayed on the screen) and press
< Enter > . Remember a password must be at least six characters, but not more
than eight characters, and it must contain at least one number.
4. The message VERIFY PASSWORD will be displayed in either the upper right
hand corner of the screen or on the second line of the screen. The cursor will
again be positioned at the NEW PASSWORD prompt. Type the same password
and press < Enter >.
In addition to the user ID and password, there are a number of other required
parameters that must also be provided when you log on for the first time. They
are: Procedure, Account number, FIMAS code and Bin number. Once all the
required fields have been entered, they will be saved in a file. Subsequent logons
will require you to supply only the USERID and PASSWORD information.
Type the required information, using < Tab > to move between fields. Press
< Enter > when complete. The required fields are:
USERID:
three characters; provided by your ADP Coordinator or
EPA Contact.
Chapter 3. Accessing IDEA on the EPA IBM Mainframe
3-7
-------
PASSWORD:
six to eight characters with at least one number.
PROCEDURE:
use SEPATSO.
ACCOUNT NUMBER: four characters; provided by your ADP Coordinator or
EPA Contact.
FIMAS:
five characters; use IESYP.
BIN NUMBER:
four characters; provided by your ADP Coordinator or
EPA Contact, or use M*** where *** is your user ID.
If you have any problems, your ADP Coordinator, or EPA Contact, should be
able to assist you with these parameters.
5. If you typed your user ID and password correctly, a logon confirmation message
and System News Alert messages will appear (see Figure 3-4), followed by a
READY prompt.
Figure 3-4. TSO News Alert/READY Screen
3.2.2 Quick Logon Procedure
Once you have established the required parameters as detailed in Section 3.2.1, the
system remembers this information. In all future logons, you need only provide your
USERID and PASSWORD.
1. The U. S. ENVIRONMENTAL PROTECTION AGENCY MENU SYSTEM
3-8
IDEA User's Guide
February 29, 1996
-------
SCREEN (see Figure 3-5) will appear once your terminal has been linked to the
EPA mainframe.
6|i|^e^^i&l^isii^A6ffl^|''«l^J^la fllesSiElWifeV.'fi
Ij^jAiMy-X^ldr.^fclSI-.'i^isr^ig 1i*'l;li^:iSi;.i,<
iy fpiil-j s key to move the cursor to the USERID prompt. Type your three char-
acter user ID and press the < Tab > key again to move to the PASSWORD
prompt. Type your password and press < Enter >. A logon confirmation message
and System News Alert messages will appear (see Figure 3-6), followed by a
READY prompt.
Figure 3-6. TSO News Alert/READY Screen
Chapter 3. Accessing IDEA on the EPA IBM Mainframe
3-9
-------
5.2.3 Password Errors
If you typed your password incorrectly, the TSO/E LOGON SCREEN (see
Figure 3-7) will appear. The message, PASSWORD NOT AUTHORIZED will be
displayed in either the upper right hand corner of the screen or on the second Me of
the screen. The cursor will be positioned at the PASSWORD prompt, and you will
have another opportunity to type your password. After three unsuccessful password
attempts, the message PASSWORD REVOKED will appear and your user ID will
not be allowed to logon again. You must contact your ADP Coordinator to have
your password reset.
'„,.->:.! V? ^s tf ;|,rf f ?',,! .<•• '<•"- x<;';;?
., „ '-6g{* US^Swi.fefeSSSS^iil^^&sS .'fe
j-' ^ja«,|;'||,i,
Figure 3-7. TSO LOGON Screen
33 Keyboard Mavvinss
The keys used to perform program functions are not always the same from one com-
puter to the next because of the types of connections used to link a terminal with the
mainframe. This means that if your computer connects to the mainframe via the
SNA Gateway, its keyboard mapping will be different from one that uses Crosstalk.
3-10 IDEA User's Guide
February 29, 1996
-------
3.3.1 Program Function (PF) Keys
Program Function (PF) keys are a shortcut for entering commands. For IBM 3270
Model Terminals, there are 24 keys that are mapped to perform specific functions.
The Function (F) keys on Personal Computers are usually mapped to correspond to
the IBM Mainframe 3270 PF key mapping. The following (Table 3-1) shows the
default key command and description for both IBM 3270 terminals (PF keys) and
most Personal Computers (F keys) with a LAN connected to the SNA Gateway.
Table 3-1. Program Function Keys and PC/LAN SNA Gateway Key Map
Command
ISPF HELP
SPLIT SCREEN
END
RETURN
RFIND
RCHANGE
UP
DOWN
SWAP
LEFT
RIGHT
RETRIEVE
Description
Displays information about the current
screen.
Splits the screen into two ISPF ses-
sions.
Saves changes and returns to the pre-
vious screen in edit mode. Returns to
the previous screen in browse mode.
Returns directly to the previous
Primary Option Menu.
Repeats the previous FIND
command.
Repeats the previous CHANGE
command in edit mode.
Scrolls Up by the amount set at the
SCROLL or COMMAND prompt
Scrolls Down by the amount set at the
SCROLL or COMMAND prompt.
Moves the cursor from one screen to
the other in the split screen mode.
Scrolls Left by the amount set at the
SCROLL or COMMAND prompt.
Scrolls Right by the amount set at the
SCROLL or COMMAND prompt.
Moves the cursor to the first input
field on the screen and retrieves the
last command entered.
IBM 3270 Ter-
minal Keys
PF1/PF13
PF2/PF14
PF3/PF15
PF4/PF16
PF5/PF17
PF6/PF18
PF7/PF19
PF8/PF20
PF9/PF21
PF10/PF22
PF11/PF23
PF12/PF24
PC/LAN SNA
Gateway Keys
Fl
F2
F3
F4
F5
F6
F7
F8
F9
F10
Fll
F12
Table 3-2 contains the same information for computers using Crosstalk1 and Kermit2
instead of SNA Gateway.
1 WIC-developed Crosstalk XVI TCP.XTK command file, with VT100 emulation and < Num Lock> on.
2 WIC-developed Kermit-MS 2.30 TCP.KMK take file, with VT102 emulation and < Num Lock> on.
Chapter 3. Accessing IDEA on the EPA IBM Mainframe
3-11
-------
Table 3-2. Program Function Keys and Crosstalk/Kermit Key
Command
ISPF HELP
SPLIT SCREEN
END
RETURN
RFIND
RCHANGE
UP
DOWN
SWAP
LEFT
RIGHT
RETRIEVE
Description
Displays information about the current
screen.
Splits the screen into two ISPF ses-
sions.
Saves changes and returns to the pre-
vious screen in edit mode. Returns to
the previous screen in browse mode.
Returns directly to the previous
Primary Option Menu.
Repeats the previous FIND
command.
Repeats the previous CHANGE
command in edit mode.
Scrolls Up by the amount set at the
SCROLL or COMMAND prompt.
Scrolls Down by the amount set at the
SCROLL or COMMAND prompt.
Moves the cursor from one screen to
the other in the split screen mode.
Scrolls Left by the amount set at the
SCROLL or COMMAND prompt.
Scrolls Right by the amount set at the
SCROLL or COMMAND prompt.
Moves the cursor to the first input
field on the screen and retrieves the
last command entered.
IBM 3270
Terminal
Keys
PF1/PF13
PF2/PF14
PF3/PF15
PF4/PF16
PF5/PF17
PF6/PF18
PF7/PF19
PF8/PF20
PF9/PF21
PF10/PF22
PF11/PF23
PF12/PF24
Crosstalk /
Kermit Keys
Fl or
Keypad 1
F2or
Keypad 2
F3 or
Keypad 3
F4or
Keypad 4
F5or
Keypad 5
F6 or
Keypad 6
F7 or
Keypad 7
F8or
Keypad 8
F9or
Keypad 9
FlOor
Keypad 0
Fl or
Keypad .
F2or
Keypad *
3.5.2 Program Attention (PA) Keys
In addition to the Program Function (PF) keys listed above, there are several other
keys, referred to as Program Attention (PA) keys, that you will find helpful for navi-
gating within IDEA. These keys are noted in Table 3-3 .
Table 3-3 (Page 1 of 2). Program Attention Keys
Command
Attn - Reset Keyboard
Attn - Attention Interrupt
Enter - Transfers data to the
computer
Delete Character
Delete End of Field
IBM 3270 Terminal
' Keys
< Reset >
+
pressed simultaneously
< Enter >
PC/LAN SNA Gateway Keys
right
Numeric key pad < Enter > or right
< Ctrl >
< Delete >
< End >
3-12 IDEA User's Guide
February 29, 1996
-------
Table 3-3 (Page 2 of 2). Program Attention Keys
Delete End of Line
Home - Move Cursor to first
input field
Insert - Places the terminal in
character insert mode
allowing you to add charac-
ters at the cursor position
Move back a field
Move to next field
Switch from LAN to PC
Mode
Reshow -Reshow the last full
screen image displayed by
ISPF
< Erase EOF >
+
< BACKTAB > keys
pressed simultaneously
< BACKTAB >
< Home >
< Insert >
+
left +
3.4 Enteritis the IDEA System
1. To access IDEA, type IDEA and press < Enter > at the READY prompt. This
step will take you to the IDEA WELCOME SCREEN (see Figure 3-8).
Figure 3-8. IDEA Welcome Screen
Chapter 3. Accessing IDEA on the EPA IBM Mainframe
3-13
-------
Technical Note: IDEA'S security, Resource Access Control Facility (RACF), does
not allow you to access IDEA through other non-ISPF programs. If you
have run a non-ISPF program prior to invoking IDEA, you will receive an
IDEA security notice requesting that you logoff off and log back on before
using IDEA.' If you continue to experience problems in accessing IDEA,
contact IDEA User Support.
IDEA User Support Line: 202 260-4250
Monday-Friday 9:00am to 5:30pm (eastern time)
Operated by the Data Integration and User Support Team, Data Management Branch,
OECA/OC/EPTDD
3.4.1 The IDEA WELCOME SCREEN
Figure 3-8 shows the IDEA WELCOME SCREEN, which is the introductory screen
to the IDEA system. From this screen you can either obtain IDEA system informa-
tion on various topics or begin IDEA query processing.
• To obtain DATABASE STATUS information, type D at the COMMAND
prompt and press < Enter >. The IDEA DATABASE STATUS SCREEN (see
Figure 3-9) will be displayed. This screen shows the databases available through
IDEA and the most recent day that the system copies were updated.
.' '.tij^M^iiiMis V .\^j^^a^^rarfi!iiB!!'StJ^'«. ill'lfaill1?
Figure 3-9. Database Status Screen
3-14
To return to the IDEA WELCOME SCREEN, press < Enter >.
IDEA User's Guide February 29, 1996
-------
To obtain HELPLINE INFORMATION, type H at the COMMAND prompt
and press < Enter >. The BASIC HELP FACILITY SCREEN will be displayed.
This screen shows information on how to obtain user support for IDEA. If you
have comments about the system functions or requests for future enhancements,
contact IDEA User Support at the number listed in Section 3.4 .
To return to the IDEA WELCOME SCREEN, press PF3.
To obtain USER DOCUMENTATION information about IDEA, type U at the
COMMAND prompt and press < Enter > .
To return to the IDEA WELCOME SCREEN, press PF3.
To obtain NEWS ALERT information type a. News Alert member name (listed
on the bottom left portion of the screen) (e.g., ALERT02) and press < Enter > .
To return to the IDEA WELCOME SCREEN, press < Enter >.
From the IDEA WELCOME SCREEN, press < Enter > to continue IDEA query
processing. The INTERFACE SELECTION SCREEN will be displayed. At this
screen, you indicate how you want to communicate with IDEA and what basic
type(s) of queries you wish to develop. To learn more about queries and how
IDEA integrates data, refer to Chapter 2, IDEA: What it Does & How it Works.
3.5 Logging off EPA's Mainframe
To exit IDEA at any time, follow these procedures:
• Use the END command or PF3 key to back out of the program screen by screen
until you reach the TSO READY prompt (see Figure 3-12), type LOGOFF, and
press < Enter > to exit the IBM Mainframe.
• Use the RETURN command (PF4 key) to return directly to the OFFICE OF
ENFORCEMENT DATA INTEGRATION PRIMARY MENU (see Figure 3-10).
You may then type I (for IDEA) at the OPTION prompt to get back to the
IDEA WELCOME SCREEN, or type X to exit to the TSO READY prompt.
Type LOGOFF at the READY prompt, and press < Enter > to exit the IBM
Mainframe (see Figure 3-12).
• Type =X at the COMMAND line to go directly to the TSO READY prompt.
Type LOGOFF, and press < Enter > to exit the IBM Mainframe.
Chapters. Accessing IDEA on the EPA IBM Mainframe 3-15
-------
Figure 3-10. OE Data Integration Primary Menu
Note: When an ISPF session is initiated for a user, the system creates two datasets,
LOG and LIST, in which information can be recorded during the ISPF
session. This activity happens with no direct user participation. When you
attempt to leave the IBM Mainframe, the screen shown in Figure 3-11 may
appear before you reach the TSO READY prompt. You are being asked to
specify how you wish to dispose of the LOG/LIST datasets.
To exit this screen, should it appear, type D at the LOG DATA SET PROCESS
OPTION prompt and press < Tab > to move the cursor to the LIST DATA SET
PROCESS OPTION prompt. Type D, and press < Enter >. The READY prompt
(see Figure 3-12) will appear.
To exit the IBM mainframe, type LOGOFF and press < Enter > at the READY
prompt.
3-16 IDEA User's Guide
February 29, 1996
-------
imi^i'W^, m <*gg/jgj $| fini \
Ji|
st^^fiftafeif asAuftftA:»^sft^^'1fflilr'..1s;' ,, i'I'
i;
-------
IDEA can be accessed from many different types of hardware; however, it is neces-
sary to have full-screen (3270 emulation) capability.
Function keys are a shortcut for entering commands and navigating within IDEA and
may vary depending upon your connection to the mainframe.
General information about IDEA can be obtained from the IDEA WELCOME
SCREEN.
3-18 IDEA User's Guide
February 29, 1996
-------
Chapter 4. Conducting a Search Using the Menu Interface
This chapter discusses what the Menu Interface is, how it was built, and a step-by-
step presentation of how to conduct a search by using the Menu Interface.
4.1 IDEA Menu Categories
The Menu Interface is the simplest means of retrieving information from IDEA. It
provides convenient pop-up windows that allow you to form queries by selecting
criteri a from lists. In order to use this interface, you must be able to use your termi-
nal's PF key equivalents for END, UP, and DOWN. For more information see
Table 4-1 at the end of this section.
To access the Menu A Interface, type A at the ENTER INTERFACE OPTION
prompt which appears at the bottom of the INTERFACE SELECTION SCREEN
shown below in Figure 4-1 .
Figure 4-1. Interface Selection Screen
Upon entering the Menu Interface, you will see the MAIN MENU SCREEN, pic-
tured in Figure 4-2 . The six categories at th e upper left of the MAIN MENU
Chapter 4. Conducting a Search Using the Menu Interface
4-1
-------
SCREEN (location, pollutant, industry, enforcement, noncompliance, and facility
status) are the categories that you can use to construct your query, to Construct a
Query
By specifying small bits of information in one or more of these categories you will be
able to retrieve the data you are seeking. The category or categories you use will
depend on the purpose of your search and the information you may have already.
Short descriptions of the six categories follow.
-
•''
Figure 4-2. Main Menu Interface Screen
LOCATION
Gives you the ability to focus your search on a specific geographical area -
from the scale of an EPA Region to a ZIP code.
POLLUTANTS
Allows you to target facilities by the pollutants they have released, handled,
or stored.
INDUSTRY
Enables you to focus your search on a certain type of industry or range of
related industries.
4-2
IDEA User's Guide
February 29, 1996
-------
NONCOMPLIANCE
Lets you search for facilities on the basis of their compliance with major
environmental statutes: Clean Air Act (CAA), Clean Water Act (CWA),
Resource Conservation and Recovery Act (RCRA), Federal Insecticide,
Fungicide, and Rodenticide Act (FIFRA), Toxic Substances Control Act
(TSCA), Emergency Planning and Community Right-to-Know Act
(EPCRA 313) (Section 313 of SARA Title III).
ENFORCEMENT
Allows you to search for facilities that have been subject to enforcement
actions.
FACILITY STATUS
Lets you call up facilities according to their regulatory status; e.g. whether
or not a toxic waste disposal site is on the CERCLA National Priorities
List.
The MAIN MENU SCREEN is the base for all the information you will need and use
in the IDEA Menu Interface. The following table (Table 4-1) provides a list of com-
mands and keystrokes that will help you navigate the Menu Interface.
Table 4-1. ISPF Commands and (default) PF Key Values in the Menu Interface
Command
END PF3/PF15
RETURN
PF4/PF16
UP PF7/PF19
DOWN PF8/PF20
To maneuver the
cursor around
IDEA screens
To reset the key-
board when it locks
up
Mode
Edit&
Browse
Edit&
Browse
Edit&
Browse
Edit&
Browse
Description
Returns to the previous screen.
Returns directty to the previous Primary Option Menu.
Scrolls up by the amount set at the SCROLL or
COMMAND prompt.
Scrolls down by the amount set at the SCROLL or
COMMAND prompt.
Use arrow keys for all directions; use < Tab > key to
move the cursor from prompt to prompt; use < Home >
to move the cursor to the top-left prompt
< Reset > key; < Ctrl> key with R; right < Alt> key; or
< End > key dsipending on your keyboard configuration
4.2 Usins Menu Categories to Form Queries
IDEA queries are formed in the Menu Interface by selecting categories from the
MAIN MENU SCREEN. Each category contains pop-up windows from which spe-
cific information can be selected, such as a ZIP code or pollutant code. This "point
and click" feature requires minimal technical knowledge of proper syntax since it is
automatically built into the query.
Chapter 4. Conducting a Search Using the Menu Interface
4-3
-------
4.2.1 Navigating the Menu Screens
— helpful hint ——~^—~~~~~~~~~^~~~~^~~—^—-^—^—-^—
To choose a-menu category, use to move the cursor so that it is to the
left of the category name, then type S ("select") followed by < Enter >. This
sequence is used whenever you want to make a selection from any IDEA Menu.
After you choose a category, the main window for that category will pop up in front
of the original MAIN MENU SCREEN that was shown in Figure 4-2 . The fol-
lowing sections will provide you with a detailed description of each of the six query-
building categories and their pop-up windows. Since the procedure is basically the
same for all six categories, a step-by-step presentation will only be given for Location.
Sections 4.2.3, Pollutants Category through 4.2.7, Facility Status Category provide
details regarding the other five categories.
4.2.2 Location Category
Let's say that you want to focus your search on the EPA-regulated facilities in a
certain geographic area. Since you will be targeting your search geographically, your
first choice would be to choose the Location category.
— helpful hint —^—^-~~~~—"——~"~~^~~~'~~~~~~"~~~~—^——^—^
To select a Menu category, use < Tab > to move the cursor over the underscore
mark to the left of the category. Then type S followed by < Enter > .
1. When you choose the Location category, IDEA automatically opens the Location
pop-up window, pictured in Figure 4-3 .
4-4
IDEA User's Guide
February 29, 1996
-------
'Aw<<, vlSit fell- /, •'<• gilts'' .l-ll-"..< Sh—fe4LffiKb& ,1
to move the cursor to one of the fields reserve:d for entering an Individual Region
code. Type a ? over the underscore mark and press < Enter > . This will cause
IDEA to open the following list of EPA regions, region offices, and the states
they include, shown in Figure 4-4 .
Chapter 4. Conducting a Search Using the Menu Interface
4-5
-------
-'
^^pln^qll^iilj
'c -"fc'&Q.HT** /hnwr'vr'*' to move the cursor to the
left of the region you wish to select and type an S over the underscore mark.
Repeat as necessary. When you finished, press < Home > to get back to the
FINISHED? (Y/N) prompt, type a Y over the default value, and press < Enter >.
(The cursor will move to the next field immediately. You do not need to move it
back.)
4. If you would like to focus your search on the state level, use < Tab > to move the
cursor to the right of the State prompt and type the two digit state abbreviation
over the underscore mark. If you are unsure of the correct state abbreviation,
type a ? over the underscore and press < Enter >. (Remember: PF7 scrolls the
page up and PF8 scrolls the page down.)
5. To select a county code, use < Tab > to move the cursor to County Code. Type
the two-letter state abbreviation and then enter the three-character FIPS county
code after the slash. For example, you could type in CO for Colorado and 031
for Denver County. If you do not know the county code, type in the two-letter
state abbreviation followed by < Enter > or type a ? over the underscore mark of
the county code then press < Enter > .This keystroke will call up the list of all
county codes for the state you have entered as you can see on the following
screen (Figure 4-5 ).
4-6
IDEA User's Guide
February 29, 1996
-------
js-'
J"t (i(|c i ,5 E1^ [C SJtiltt'J ft 'I'hcjt f, '{jl'JSc.cJ ! {'^ c { {.'itSS {tt-t 'V'flv^- 'dfet'tt*** Jt'd'5'' ('(St'fef' \)£& ,tc ''iwStJ* 1 * J '(Sf^cEc't'i
t «({i{S»«**(e r a{:E!ift {i-ij jLuk.H{ic a!i" Kk I ti ^ c «{ rp ; t^( t: : 1 1 ? 'c ; t ({JC£ H'Kc' i 't4 ' I ' :Tt^t
e-.-'
j
,!, { ci, , iSStSVe .iS- c £ ;& ;t ft?tf! t « ! c •?% f
***«!*' (5*^1 £e
Figure 4-5. Location Category with County Code's
6. The easiest way to include a county code in your query is to use < Tab > to move
the cursor to the left of the county you are choosing (remember: PF7 scrolls the
page up and PF8 scrolls the page down). Type S. IDEA will automatically enter
the county code into your query. ;
7. Now you might choose a second county for your query. Let's say that you want
to expand your search to include Clear Creek County, Colorado. Move the
cursor next to Clear Creek. County and type S; you now have a two-county
search.
— helpful hint ~^~^~^^^~~™^^~'~~~~1~1~~1~~1~~~<~~~~~~1~~~~~<~'~"~~
If you have finished your selections, you can now exit the pop-up window.
Use or to move the cursor to the FINISHED? (Y/N)
prompt and type Y followed by < Enter >.
8. Let's say you decide that a two-county search is too large for your purpose. So
you decide to focus your query on a very precise area, for instance the City of
Denver, Colorado 80202. Your next step is to delete the county codes by typing
Y next to the CLEAR? (Y/N) prompt at the upper right of the box. This
command is shown in Figure 4-6 . If you did not want to clear all the entries in
a -up window, but only some, you would have to < Space > over the entries you
no longer wanted in the Location category window.
Chapter 4. Conducting a Search.Using the Menu Interface
4-7
-------
.(tsJ<<(. You will be
ready to run a query on EPA-regulated facilities within the geographic parameters
you have specified. (As of this writing, you cannot enter a ? to see a list of all
possible ZIP Codes. You wouldn't want to scroll through the list to find the right
one anyway!)
10. If you are satisfied with the location criteria that you selected for your query, use
< Home> or < Tab> to move the cursor to the top of the.pop -up window that
you are in, type Y next to the FINISHED? (Y/N) prompt and press < Enter >.
[— helpful hint
To exit a pop-up window, type Y at the FINISHED? (Y/N) prompt, followed
by < Enter >.
11. From here you will return to the MAIN MENU SCREEN and your query
instructions will be listed in the right-hand portion of the screen. Figure 4-7
shows what the screen would look like for our query with the Location value of
ZIP Code = 80202.
4-8
IDEA User's Guide
February 29, 1996
-------
• It
t,f'v-JiJi-
<( M'ffv «V<(5 & = ' /?/ fp < *&(«* {j£\ {;;w<:£
Figure 4-7. Menu Interface with selected ZIP Code
At this point, you have formed a complete query that you can run to receive data or
you can combine this query criterion with information from the other five categories
to perform a more detailed search. See Section 4.4, Running Queries to run the
query.
Note: Be as specific as possible when constructing your query. This will help you to
avoid a search that turns up hundreds or thousands of facilities. Since in our
example you are looking for all EPA-regulated facilities in a certain location,
you should be as specific as possible about the geographic area you search.
When using the Location Category, the IDEA system will conduct its search
according to the largest geographical entity that you enter in the Location pop-up
window. In technical terms, the computer is performing what is known as a
"Boolean OR" by considering each criterion separately and then summing the facili-
ties retrieved by the search. The map of EPA Region 8 shown in Figure 4-8 illus-
trates the IDEA logical operating mechanism.
Chapter 4. Conducting a Search Using the Menu Interface
4-9
-------
I "" —til
Figure 4-8. The map of EPA Region 8
In this example if you were to enter anything in addition to the ZIP code of the city
of Denver (80202), for instance the State name (CO), you would receive more facility
names than you intended (all the EPA-regulated facilities in Colorado State in this
example). If you were to enter the State name (CO), the EPA Region (8), the county
code (CO/031 - Denver), and the ZIP Code (80202), the system will read your query
in the following manner: Find any facility in Colorado State OR EPA Region 8 OR
Denver County OR ZIP Code 80202. As you can see, the number of facilities in this
case will be the same as the number of facilities in the largest geographical entity; i.e.
EPA Region 8.
4.23 Pollutants Category
— helpful hint •"—
To select a menu category, use < Tab > to move the cursor over the underscore
mark to the left of the category. Then type S followed by < Enter > .
Type S to select the Pollutants Category. You will be presented with a pop-up
window that offers many options for your query. The Pollutant pop-up window
looks like Figure 4-9 :
4-10
IDEA User's Guide
February 29, 1996
-------
• "ss,t. 1 •«,ji5w,£..,:',%?>,, * SSw.F? gfSfi '.S'SsJ'-- U&w U.,'.. .iSwi'v&.jCt <
-------
Pollutant Compliance Status - A one-character code that indicates the compliance
status of a plant for an indicated pollutant. You can enter up to four per search.
Enter ? for a listing of the codes.
The PCS (Water) system lets you search by:
• Meas./Viol. Parameters - A five-digit code that indicates a facility's particular
monitored parameters and physical attributes. You can enter two per search.
Type ? for a multi-page listing.
• Violation Types - Three-character codes indicating the worst violation detected for
a given report parameter's measurements. You can enter up to two per search.
Type ? for a listing of the violation types.
The RCRIS (Solid Waste) system provides you the opportunity to search by:
• Waste Codes - Codes of four digits or less that represent contaminants or haz-
ardous characteristics (e.g., ignitable waste). You can enter two per search. Type
? for a multi-page listing.
• Waste Amt. (in tons) - This entry requires you to enter a range of waste tonnages.
On the underscore marks to the right of the word IN, enter the lower value. On
the underscore spaces to the right of those, enter the higher value. Do not add
commas in the amount beyond thousand (e.g., 10000 = 10 thousand).
— helpful hint :
Menu prompts that feature the word IN are asking you to enter a range of values.
Enter the lower number first and the higher number second. IDEA will select any
facility with a value included in this range.
• Waste Process - This three-character code indicates the manner by which the
waste is handled (e.g., in containers, incinerated, landfilled). You can enter two
per search. Type ? for a list of processes.
The TRI (Toxic Release) system allows you to create a search with these criteria:
• Chemical Codes - Nine-digit codes representing chemicals and pollutants (e.g.,
007439921 stands for Lead). You can enter two per search. Type ? for a multi-
page listing.
4-12 IDEA User's Guide February 29, 1996
-------
Release Medium - This one-character code indicates the area of the environment
into which the contaminant was released. You can enter up to seven per search.
Press ? for a listing of the codes.
Reporting Years - Enter a four-digit year. You can enter up to three years. Type
? for a list of the available years.
Release Amount (in Ibs.) - This entry requires you to enter a range of contaminant
amounts. On the underscore marks to the right of the word IN, enter the lower
value. On the underscore spaces to the right of those, enter the higher value. Do
not add commas in the amount beyond thousand (e.g., 10000 = 10 thousand).
|— helpful hint —
To exit a pop-up window, type Y at the FINISHED? (Y/N) prompt, followed by
< Enter >.
4.2.4 Industry Category
— helpful hint
To select a menu category, use < Tab > to move the cursor over the underscore
mark to the left of the category. Then type S followed by < Enter >.
Upon selecting the Industry Category, a pop-up window will appear, which presents
two simple options for your search. These options are searching by a range of
Standard Industrial Classification Codes (SICs) or by individual SIC. The Industry
pop-up window is pictured in Figure 4-10 .
Chapter 4. Conducting a Search Using the Menu Interface 4-13
-------
Bai^Sp^'?;^
" " .3^_-i-,, , 13^.1^^-^JIId^l^^^J!^*?,^^^ $£&,;&&3"'isL'.
,,^m^^Sm
-- v - [ *•! ' ? (-i i i t •;t'';tl!! * -t to move the
cursor over the underscore marks to the right of the word IN. Now you can see the
list of general SICs by typing ? next to IN followed by < Enter >.
IDEA will provide you with a list of general SICs. Since you are looking for the
metal mining industry, scroll down (PF8) to your subject. IDEA tells us that the SIC
range for "Metal Mining" is 1011-1099. If you select this range, IDEA will search for
EPA-regulated facilities that are involved with mining metals.
Alternatively, there is a quick way to find a particular SIC. You can type in the
name of the industry you are searching for at the NEXT VALUE, line followed by
< Enter >. In this case, it is MINING (see Figure 4-11).
4-14
IDEA User's Guide
February 29, 1996
-------
'%4*t^&!v! K&*'e&s Ht I'l^lli- lilt''?!!!* < i!%J l<'%< ^lis,!;
B«?m 7iif »-|i *«a-t s«a^sfexjp«^taj. (i .^ipc
j;H||H
-------
— -"^ " f «* * es{ ,
_>Run auto? " "LCikstf
*•* —•—• I t S tl 4 j , •" ( 4 ffc' tifStfrf..!
'.Lve^ar-.-ftaeRS?";'^'
' '"* !' -<•> *- (
C-iPFKS/gg^^li^BeBiV*
Figure 4-12. Industry Category: Selecting SICs of Metal Mining Industry
Suppose you wanted to be more specific and, for example, you were interested in tar-
geting lead mining. To find out the individual SIC for lead mining, you would move
the cursor next to the " = " using < Tab > and type ? next to it followed by
< Enter >. A list of general SICs will pop up. You could type in LEAD at the
NEXT VALUE: prompt and press < Enter > . IDEA would then provide you the
SIC for lead and zinc ores, which is 1031. You can enter up to ten of these four-digit
codes , or enter a range as wide as you like (you could extend the range to include
several general sectors of industry ).
Note: The general SIC list can be helpful in narrowing your search for the SIC you
need. By consulting the general list first, you can save yourself the time of
scrolling through the several hundred specific SICs.
— helpful hint •
To exit a pop-up window, type Y at the FINISHED? (Y/N) prompt, followed by
< Enter >.
4.2.5 Noncompliance Category
4-16
IDEA User's Guide
February 29, 1996
-------
I— helpful hint
To select a menu category, use < Tab > to move the cursor over the underscore
mark to the left of the category. Then type S followed by < Enter >.
After choosing the Noncompliance Category, you will be presented with a pop-up
window that offers many options for your query. The Noncompliance pop-up
window is pictured in Figure 4-13 .
|«H.p>p:ra8jist(s,& <$$&" 'ssii" "S,
• "'JUsfm ', tAI\ 4feSfi' 1'!''*^ ii^;,
r^^s^^q^fcto'^j!^
'AffifS-^Jflr*. I,Aa«^«" ,'^fen SI
^.'^^sttSS^^S^^'^^^JSs^^^k
? t .{(c- t et { (t;< s. t
<< ''c -' < •' -s
iii!Sii ''ll i^l || 1;',| H" i! cu;||lv'^s|d !'|
Figure 4-13. Menu Interface with Noncompliance Category
As you can tell from the statutes listed along the left side of the window, this cate-
gory lets you conduct your search according to facilities' compliance status with
regard to CAA, CWA, RCRA, FIFRA, TSCA, and EPCRA 313. This category's
pop-up window can be handled much like the others, but it offers different criteria.
The following paragraphs provide instruction on the use of this pop-up window and
how to create a search.
The entry under Law(s) that reads "2 or more" allows you to choose any facility
flagged as a noncomplier (NC) or significant noncomplier (SNC) with any two or
more of the statutes listed above. Simply enter an S next to NC and/or SNC under
the Values heading.
The CAA entry allows you to use the following criteria for your search:
Chapter 4. Conducting a Search Using the Menu Interface
4-17
-------
• In Violation - Use this criterion to search for all facilities in violation of CAA.
Type S to activate this criterion.
• Significant Violation Status - Use this criterion to search for all Significant Viola-
tors under CAA. Type S to activate this criterion.
• EPA Compliance Status - You can enter up to five of these one-character compli-
ance codes. Type ? to see a multi-page list of the different codes.
• Significant Violation Flagl - You can enter up to five of these one-digit codes per
search. Type ? to call up a list of the codes.
Under CWA you have the following options for forming your query:
• Reportable Noncompliance - Use this criterion to search for all facility
noncompliers under CWA. Type S to activate this criterion.
• Significant Noncompliance - Use this option to search for all Significant
Noncompliers under CWA. Type S to activate this criterion.
• Current Year Noncompliance - One-digit codes that indicate current compliance
status under CWA. You can enter up to five codes within each Quarter. Type ?
to see a list of the codes.
Under RCRA you can form a search according to:
• Unresolved Violations - Use this criterion to search for all facilities in violation of
RCRA, except High Priority violations. Type S to activate this criteria.
• Unresolved High Priority Violations - Use this criteria to search for all facilities
classified as High Priority Violators under RCRA. Type S to activate the criteria.
For FIFRA, TSCA, and EPCRA 313 you can choose to search for:
• Noncompliers (NC) and/or Significant Noncompliers (SNC) - Use either of these
criteria to search for all facilities classified as NCs or SNCs under FIFRA, TSCA
or EPCRA 313. Type S to activate the criteria.
4-18 IDEA User's Guide February 29, 1996
-------
— helpful hint
To exit a pop-up window, type Y at the FINISHED? (Y/N) prompt, followed by
< Enter >.
4.2.6 Enforcement Category
— helpful hint ———————^——^—-——^——^————.^^—
To select a menu category, use < Tab > to move the cursor over the underscore
mark to the left of the category. Then type S followed by < Enter >.
The Enforcement pop-up window, displayed in Figure 4-14 , provides you with an
array of options to use in your query formation.
8*?? { ct;jV T?S« v5"" (< c SS
-------
(m= month, d= day, y=year), and remember to include zeros preceding numbers
under ten. Enter the earlier date next to the word IN and the later date after the
word TO. The following paragraphs provide a more detailed explanation of your
options when using the Enforcement pop-up window.
The entry 2 or more, found under the heading Law(s), allows you to search for all
facilities that have been subject to enforcement actions under any two or more of
these statutes. You can choose to specify the enforcement action(s) by typing S next
to NOVS (Notices of Violation), Administrative Action, or Judicial Action, and speci-
fying the date of the action by entering a range of dates in the appropriate spaces.
Under CAA, you can conduct a search according to:
• Nat'l Act. Type - a code of up to two characters indicating actions at air facilities.
You can enter up to five of these codes per search. Type ? to call up a multi-page
list of the codes.
• The date of the enforcement action.
Under CERCLA, you can form a search using the following criteria:
• Enforcement Action Type - a code of one or two characters indicating the type of
CERCLA enforcement action. You can enter up to five per search. Type ? to see
a multi-page list of the codes.
• The start date and/or completion date of the enforcement action.
Under CWA, you can conduct a search according to:
• Enforcement Action Code - a code of one or two characters that represents the
action taken in response to CWA. You can enter up to five per search. Press ?
for a multi-page list of the codes.
• Enforcement Action Type - a one-letter code that indicates EPA or State enforce-
ment actions. You can enter up to two per search. Press ? for a list of the codes.
• The date of the enforcement action.
Under RCRA, you can form a search using the following criteria:
4-20 IDEA User's Guide February 29, 1996
-------
• Enforcement Action Type - a code of up to three characters that represents the
RCRA enforcement action taken. You can enter up to five per search. Type ?
for a multi-page listing of the codes.
• Response Agency - one-character code that indicates whether the action was
EPA-lead, State-lead, or EPA oversight. You can enter up to two per search.
Type ? for a listing.
• The date of the enforcement action.
Enforcement information about TSCA, FIFRA, and EPCRA 313 is aU drawn from
the same database, NCDB. When you choose to search this database (by searching
for information under one of these laws), you must first specify the Statute Violated.
This entry allows you to enter any two of the following three codes per search:
E= EPCRA 313, F= FIFRA, and T= TSCA. Other criteria available regarding these
statutes are:
• Enforcement Action Type - a code of up to three characters that indicates the type
of enforcement action for which you are seardiing. You can enter up to five per
search. Type ? for a multi-page listing.
• The date of the enforcement action.
The ALL LAWS option allows you to search the federal docket for facilities that
have been subject to judicial enforcement actions. Enter the appropriate three- to
six-character acronym in the spaces next to the word Law in order to include a partic-
ular statute in your query. You can enter up to tliree of these codes. Type ? to see
a listing.
You can also search the docket by the date that any enforcement action was filed or
concluded.
— helpful hint
To exit a pop-up window, type Y at the FINISHED? (Y/N) prompt, followed by
< Enter >.
4.2.7 Facility Status Category
Chapter 4. Conducting a Search Using the Menu Interface 4-21
-------
— helpful hint ~~~~~
To select a menu category, use < Tab > to move the cursor over the underscore
mark to the left of the category. Then type S followed by < Enter >.
After you have selected the Facility Status category, you will be presented with a
pop-up window that offers many options for constructing your query. The Facility
Status pop-up window is pictured in Figure 4-15 .
& »,f ?«"•?/ 7 • ;i-wy s s H ,,A .',$ f,: m'
,! -^oqatto'.!! ^^VlM-MS*
^7:>&i11ia; i :^'iP'jri.?iwtif:
• ' . («"«?',J^?(j 'vstjj.jy* ,c', 5
:( ,{( : t ,(ct=^^ = = c £!!-K< (,e$«lje{s*e 'c1 (, j *{! <^
tji i^v j«««c i U! « tctV'««•&!
»r«feY$!ra!fih3ffintWii&
Figure 4-15. Menu Interface with Facility Status Category
While this category's pop-up window is used much like the others, there are differ-
ences. The following paragraphs provides instruction on the use of this pop-up
window and how to create an efficient search.
To create a query concerning CAA, you can specify:
• Class A SIP/NSPS/NESHAP (State Implementation Plan/New Source Perform-
ance Standard/National Emissions Standard for Hazardous Air Pollutants) - Type
an S to activate this criterion.
• Air Program - A one-digit code that indicates the air programs to which a plant is
subject. You can enter up to five of these per search. Type ? to see a list of all
the codes.
4-22
IDEA User's Guide
February 29, 1996
-------
Source Classification - A two-digit code that represents the actual or potential air
emission totals for a facility. You can include up to three per search. Type ? for
a listing of the classification codes.
Regarding CERCLA, the facility status indicators you can search for are:
• NPL Status - A one-character code representing a facility's status with regard to
the National Priorities List. You can choose up to three per search. Type ? to
see a listing of the codes.
• Site Classification - A one- to two-character facility classification. You can
choose up to three per search. Type ? to see a listing of the codes.
• Incident Type - A one-character code that indicates whether an incident was an oil
spill. There are only two codes; type ? to see a listing.
To retrieve information regarding federal facilities, use the FEDFAC option in the
Facility Status pop-up window. Enter the two-character code representing the federal
agency in which you are interested. You can enter up to three codes per search.
Type ? to see a multi-page listing of the codes.
Concerning CWA, you can build a query along the following lines:
• Active, Major Discharger - Use this criteria to search for all Active, Major Dis-
charges under CWA. Type S to activate this criteria.
• Facility Type - A one-digit number indicating whether the facility is federal, indus-
trial, municipal, or other. You can enter up to three per search. Type ? to see a
listing of the codes.
• Industrial Classification - A one-character code that indicates a facility's industrial
classification. You can enter up to three per search. Type ? to see a listing of the
codes.
• Ownership Type - A three-character code that indicates whether a facility is feder-
ally, privately, municipally, etc. owned. You can enter up to three per search.
Type ? to see a listing of the codes.
To include RCRA facility status values in a query, you must choose the RCRA
universe(s) that you wish to search. The universes are: transporter, fully regulated
Chapter 4. Conducting a Search Using the Menu Interface 4-23
-------
generator, land disposal, incinerator, storage/treatment, and small generator. In order
to choose one of these options, enter an S next to the appropriate universe.
To select a facility status from TSCA, FIFRA, or EPCRA 313, IDEA requires you to
enter a two-character Facility Function code. You can enter up to two per search.
Type ? to see a multi-page listing of the codes.
— helpful hint
To exit a pop-up window, type Y at the FINISHED? (Y/N) prompt, followed by
< Enter >.
4.3 Managing Queries
The key to managing your query is the four options at the bottom left of the MAIN
MENU SCREEN (above the PF key indicators, see Figure 4-2 ). Like the categories
above, these commands work by typing S to the left of the desired command followed
by < Enter >.
4.3.1 Clearing Queries
Whenever you are not satisfied with the query you have created, you can delete
and/or change it. There are three different ways achieve this task.
1. The CLEAR QUERY command on the MAIN MENU SCREEN will erase the
query currently displayed on the MAIN MENU SCREEN. After performing this
function, a small box will appear at the lower right of the screen announcing that
the Query has been cleared. To remove the message from the screen, press
< Enter >.
2. To clear all the data elements or values in a category pop-up window, select that
category and use < Home > and/or < Tab > to place your cursor at the CLEAR?
(Y/N) prompt. Type Y followed by < Enter > and the window will be cleared.
3. To erase one data value or element that you have chosen, select that category and
< Space > over the undesired characters.
4-24
IDEA User's Guide
February 29, 1996
-------
4.3.2 Saving Queries
The SAVE QUERY command will ask you to name your query followed by a short
description, and then it will save the query in the system's memory. After saving the
query, a small announcement box will appear at the lower left telling you the "Query
has been saved as...." To remove the message from the screen, press < Enter >.
4.3.3 Retrieving Queries
After saving the query, you will be able to recall it at any time by using RETRIEVE
QUERY. When you select RETRIEVE QUERY, a list of saved queries comes to the
screen in a pop-up window like the one shown in Figure 4-16 .
Figure 4-16. Query Retrieval Screen
Retrieval is carried out by typing S next to the desired query. The query you selected
will then be moved onto the MAIN MENU SCREEN with all its values listed as
before.
Chapter 4. Conducting a Search Using the Menu Interface
4-25
-------
You can delete a query that is no longer needed by typing D next to it and pressing
< Enter >. A small box will show up to ask CONFIRM QUERY DELETION
(Y/N). Type Y to confirm your delete command or type N to cancel it, then press
< Enter >.
You can update the name and/or the optional description of a saved query by typing
a U next to it and pressing < Enter >. You may then change the name on the first
line, or < Tab > to the second line to change the description, by typing over the ori-
ginal description and spacing over anything left at the end of the line. Remember not
to press < Enter > until you are satisfied with your modifications.
4.4 Running Queries
The RUN QUERY command instructs the computer to carry out the search with the
criteria that you selected. Once you choose to run the query and press < Enter >, the
screen will change to the title screen shown in Figure 4-17 .
Caution
Be sure not to push < Enter > until you make all of your choices on this screen;
otherwise, < Enter > will instruct the system to begin running your query.
Figure 4-17. Input and Report Selection Screen
4-26
IDEA User's Guide
February 29, 1996
-------
4.4.1 Input and Report Selection Screen: Choosing Input •
After telling IDEA to run your query, the Input and Report Selection pop-up
window appears and asks you to specify whether you want your query to be Linked
or Nonlinked. When you choose Linked, Nonlinked, or both, you are telling IDEA
what type of information to retrieve: data that has been integrated using FINDS
(linked data), non-integrated data from the separate databases (nonlinked data), or a
combination of the two.
4.4.1.1 Linked
After you specify select criteria and indicate linked data, IDEA searches for a facility
or facilities that meet those criteria. For each facility retrieved, IDEA tries to find the
identification number for that facility in the Facility Index System (FINDS). Linked
is the default; that is, if you do not choose Nonlinked or Linked Nonlinked, IDEA
will retrieve data that has been integrated using FINDS. Linked data may not be
complete since FINDS does not contain data for all facilities.
4.4.1.2 Nonlinked
If you choose nonlinked data, IDEA will not use FINDS to integrate information.
The information retrieved by IDEA will come from different individual databases
indicated by your query. The benefit of choosing Nonlinked is that you will receive
all the data you are seeking. But you will have to manually match facilities from
separate systems in order to integrate the data to your specifications; IDEA cannot
do this for you.
— helpful hint —^—^——^————-^————^——^————^———.
Since nonlinked data was retrieved from different individual data systems, you can
not select Report Summary for your output.
Chapter 4. Conducting a Search Using the Menu Interface 4-27
-------
4.4.1.3 Linked Nonlinked
You can combine Linked and Nonlinked in your query to get both integrated and
nonintegrated data. Type an S next to both Linked and Nonlinked and you will
receive each type of information in a separate section of the report. The first section
will contain those facilities that meet all your selection criteria and are linked using
FINDS. The second section will consist of the facilities that meet your criteria within
each of the particular databases but have not been linked using FINDS. Data in the
first section will not be repeated in the second.
— helpful hint • ~
Since nonlinked data was retrieved from different individual data systems, you can
not select Report Summary for your output.
Note that all the facilities in the second section were selected because they fulfill only
the criteria that pertain to a particular database and could not be linked using
FINDS. For example, if you form such a query looking for facilities that are viola-
tors of both the Clean Water Act and the Clean Air Act, the Nonlinked part of the
report will contain all air violators and, separately, all water violators. Since FINDS
does not provide the link, you will have to manually correlate the facilities in order to
obtain integrated data.
4.4.2 Input and Report Selection Screen: Choosing Reports
After choosing a Linked or Nonlinked query, IDEA asks you to select a report
format. As you can see in Figure 4-17 , there are currently four standard reports
available to you in the Menu Interface: 1A, IB, 2, or Summary. Short descriptions
of the formats are given in Table 4-2 below. See Chapter 10, IDEA Standard
Reports for more detailed information on the information given in each of the four
standard reports.
4-28 IDEA User's Guide February 29, 1996
-------
Table 4-2. IDEA Standard Reports
There are currently four standard IDEA report formats: 1A, IB, 2, and Summary.
REPORT 1A
A brief report of individual facilities. Organized by the linked database, IDEA displays the
facility name and database identifier, location and other business information, noncompliance
or violation status, and enforcement information.
REPORT IB
A more detailed presentation of information on individual facilities, including historical and
programmatic data such as dates and results of inspections, specific toxic substances reported,
and details of enforcement actions.
REPORT 2
A linked docket table that indicates whether each facility is listed as a significant noncomplier
or high priority violator.
REPORT SUMMARY
Provides total facility counts by program and EPA region; sum of facilities that are in compli-
ance and not in compliance by program and total numbers of enforcement actions by
program; and total toxic substance release information for the selected facilities.
IDEA will automatically choose the default formal, Report 1A; you can then over-
write it and select other reports. Once you are satisfied with your selection, press
< Enter > to instruct IDEA to begin running your query.
When finished, IDEA will present you with the QUERY STATUS SCREEN. An
example of a QUERY STATUS SCREEN for a Linked query is shown below in
Figure 4-18 . Of course, the number of facilities and the databases consulted will
vary depending on your query.
Chapter 4. Conducting a Search Using the Menu Interface 4-29
-------
Figure 4-18. Query Status Screen
Caution
It is important that the Counts by Database information that is displayed is not
misinterpreted. For the QUERY STATUS SCREEN shown in Figure 4-18 , for
example, there were 60 facilities that satisfied any one of the AFS-related criteria
in the query throughout the nation, but were not in FINDS. These 60 facilities
comprise 35 percent of all facilities in the nation satisfying any of the AFS-related
criteria in the query. These numbers are national because IDEA uses FINDS to
sort facilities by location, and these are the facilities that are not in FINDS. See
Section 2.3.3, Query Status for more discussion of the QUERY STATUS
SCREEN.
4.43 Viewing the Query Reports
If you press < Enter > at the QUERY STATUS SCREEN, IDEA will transfer you to
the BROWSE mode and will provide you with report(s) based on the query you
formed and the report format(s) you specified earlier. Figure 4-19 is an example of
Report 1A showing the RCRIS and PCS information about the first facility selected.
In the BROWSE mode you can view, print, or save information, but you can not
change it. To maneuver through the report(s), use PF7- to page up, PF8 to page
down, PF10 to scroll left, and PF11 to scroll right. You can also type in SW at the
COMMAND prompt to switch to the next report. Upon reading the last report gen-
4-30
IDEA User's Guide
February 29, 1996
-------
crated, entering SW at the COMMAND prompt will bring you back to the first
report.
t$*
'K , I ' * f s S « :lj ji
, , . -v < , , • - vf" ^
ifri^ir: H j^T?-^j¥*3n!^
Figure 4-19. Report 1A.
4.5 Exiting the IDEA Menu Interface
To exit the Menu Interface at any time, you must save your current work first by
selecting SAVE QUERY at the bottom left of the MAIN MENU SCREEN. If you
do not save your work you will have to start from scratch to rebuild it. After saving
the query you can use one of the procedures listed below:
• Press the PF3 key to back up one screen at a time until you get back to the
INTERFA CE SELECTION SCREEN.
• Use the PF4 key to return to the OFFICE OF ENFORCEMENT DATA INTE-
GRATION PRIMARY MENU. Then:
1. type I for IDEA at the OPTION prompt to get back to IDEA WELCOME
SCREEN, or
2. type X to exit to the TSO READY prompt.
Chapter 4. Conducting a Search Using the Menu Interface
4-31
-------
4.6 Summary
This chapter describes the IDEA Menu Interface. The Menu Interface is the simplest
means of retrieving information with IDEA. The convenient pop-up windows allow
you to form queries according to your search criteria from different databases inte-
grated by IDEA.
The Menu Interface has six categories: Location, Pollutants, Industry, Noncompli-
ance, Enforcement, and Facility Status. These six categories are used to direct your
query. Based on the purpose of your search and the information you may have
and/or you want to get, you can easily retrieve the data and build an efficient query.
You can manage your queries using commands of CLEAR, SAVE, RUN, or
RETRIEVE, which are located at the bottom left of the MAIN MENU SCREEN.
Simply by selecting one or more of these commands, you will be able to run, save,
retrieve, or even clear your query.
4-32
IDEA User's Guide
February 29, 1996
-------
Chapter 5. Managing Libraries
This chapter provides detailed information on managing IDEA libraries.
5.1 Selecting an IDEA Library
To access the Keyword Interface in IDEA, type K at the ENTER INTERFACE
OPTION prompt, which appears at the bottom of the INTERFACE SELECTION
SCREEN (Figure 5-1). IDEA displays the INPUT LIBRARY SELECTION
SCREEN shown in Figure 5-2 . Your IDEA library, or dataset, is where you build
and store your queries in the Keyword Interface. Before you will be allowed into the
interface, you must specify the library in which you will be working.
I— Caution
When working in the INPUT LIBRARY SELECTION SCREEN, do not press
< Enter > until you are finished editing the options on the screen; otherwise,
IDEA will take you to the next screen. If < Enter > is pressed accidently, press
PF3 or type END at the COMMAND prompt and press < Enter > to return to
the INPUT LIBRARY SELECTION SCREEN,
V ^ J?c' 1 £c
-------
The library name that IDEA provides is a default name based on your NCC logon
prefix (see Figure 5-2 below). The first three letters are your user ID; the second
four characters are your NCC account number. IDEA default libraries have the
extension (called qualifiers) of "QUERY.SPECS." You should use this default name
for your first library.
. m
^.^^Mmm^^Ayy^^yfm^^ri, •,
„ j -y -i „•* t.FT^^ T" <.TV[ T3? 181 §CKS
*. :•! -1- -^* t'f«% *i.LivMiiiLfl:
Figure 5-2. Input Library Selection Screen
If you want to form a new library, type over the default library name with the name
of your new library. Use < Space > to erase any leftover characters. Keep the fol-
lowing rules in mind when you are naming the new library:
1. The first three characters of the name must be your user ID and the next four
your NCC account number.
2. Follow these first seven characters with a period.
3. The words you enter next must form a library name that does not yet exist.
4. Periods must be used to separate qualifiers.
Once you are satisfied with your library name, press < Tab > to move the cursor to
the LIBRARY STATUS(Shr/New/Old) prompt.
5-2
The default status for your library is SHR (share). Share status means that more
than one person can use the library at the same moment. For example, if you call
IDEA User Support, you and the technician can browse your library simultaneously.
Note: It is also necessary to provide security access to your library. See Section 5.3,
Allowing Access to your IDEA Library for additional instructions.
IDEA User's Guide
February 29, 1996
-------
By changing the status to OLD, you will be given, exclusive access to the library. If
you are creating a new library, change the status from SHR to NEW and press
< Enter >. If you do not, a message will pop up in the top right corner of the screen
informing you that the LIBRARY DOES NOT EXIST. Select a library status by
pressing < Enter > to accept SHR or by typing in either NEW or OLD, and pressing
< Enter >.
Press < Enter > at the INPUT LIBRARY SELECTION SCREEN and the MEMBER
LIST SCREEN (see Figure 5-3) will appear. In other words, once the library is
selected, IDEA will display the contents of the library as a "Member List." This list
displays the member (file) name, the date and time that is was created or last
changed, an optional description of the member's contents, and the user ID of the
person who last modified the member.
Figure 5-3. Member List Screen
The heading CHANGED provides you with the date and time when that particular
query was last modified. The date format is a six- digit code comprised of the last two
numbers of the year, two numbers for the month and two numbers for the day. For
instance, June 15, 1993 would be written 930615. The date is followed by the time,
which is in 24-hour format. The DESCRIPTION category allows you to give a brief
summary of the contents of each query. The user ID of the person who last modified
the query is displayed under the ID heading.
The MEMBER LIST SCREEN (see Figure 5-3), is a catalogue of entries in the
library that you selected. The entries, called members, are listed along the left-hand
Chapter 5. Managing Libraries
5-3
-------
margin of the screen under the NAME heading. Members are queries that you
compose and then store in your library like a book on a shelf. The queries listed in
the Member List will be available to you each time you use IDEA. If you have no
queries at this point, the screen will be blank under the headings.
IDEA requires that you give every query a name, even if you don't intend to save it.
Word processors, such as WordPerfect, ask you to name a document (file name) after
you have created it. IDEA, on the other hand, requires that a query be named prior
to creating it. You must enter a member name (file name) before the EDIT SCREEN
(see Figure 5-4) wiH appear. When you create a new member in the library you are
actually setting up a work space to compose and run your query. If you decide to
save it, the contents of the work space are saved to the member (file) under the name
you provided.
5.2 Managing Queries Using the Member List
Table 5-1 is a summary of the commands available to you for managing your
Member List. They allow you to retrieve, rename, describe, and delete the queries in
your Member List. These commands are either typed on the COMMAND line fol-
lowed by a name, or are placed next to the left of the query name in the MEMBER
LIST SELECTION SCREEN. Sections 5.2.1, Creating a New Query through 5.2.6,
Deleting a Query from the Member List describe how each is used.
Table 5-1., Library Member List Commands
B query
E (or S) query
R query
U query
D query
Browse/Read the query; no editing possible.
Edit/Select an existing query or create a new one in
the editor.
Rename the query.
Update the query description.
Delete the query From the MEMBER LIST.
5.2.7 Creating a New Query
When you create a new member in the Library you are actually setting up a work
space to compose and run your query. IDEA requires that you give every query a
name before the EDIT SCREEN will appear (even if you don't intend to save it). If
you decide to save it, the contents of the work space are saved to the member under
the name you provided.
5-4
IDEA User's Guide
February 29, 1996
-------
1. To create a new query (member) press < Tab > or < Home > to move the cursor
next to the COMMAND prompt of the MEMBER LIST SCREEN (see
Figure 5-3).
2. Type E (or S) and < Space >, followed by a name of up to eight letters or
numbers for the query you are creating (e.g., E NEWQUERY). Special characters
or spaces cannot be used when writing the member name.
3. Press < Enter > and the EDIT SCREEN will appear (see Figure 5-4) in which
you can construct a query.
Figure 5-4. Edit Screen
5.2.2 Looking at an Existing Query
To look at a query, use the B (Browse) command as described in the following step.
When you are in Browse, you can look at the queiry (member) but you cannot update
it. In Browse mode, the member does not have sequence numbers down the left hand
side of the screen whereas the Edit mode does.
1. To Browse an existing query (member) from the MEMBER LIST SCREEN (see
Figure 5-3), type B two spaces to the left of the query name and press < Enter >.
The BROWSE SCREEN (see Figure 5-5) will be displayed.
Chapter 5. Managing Libraries
5-5
-------
- '^p|^^|ft^cprAtei¥|§l!^||^bJ .^-Hrtd^Mt^itel^i
r-.lu.-.A.hr3!''' '""J ;<^';A,tff «•£!•< VSr,MA A-,;'' '<M;j: s .-:.,^K'--'
Figure 5-5. Browse Screen
5.2 J Editing an Existing Query
To edit an existing query, use the E (Edit) or S (Select) commands as described in the
following steps.
1. To edit an existing query from the MEMBER LIST SCREEN (see Figure 5-3),
type E or S two spaces to the left of the query name. Press < Enter >.
2. An existing query may also be edited by typing E or S and the member name on
the COMMAND line and pressing < Enter >.
5.2.4 Renaming an Existing Query
To rename a member on the Member List, use the R (Rename) command as
described in the steps below. The information in the member will remain unchanged,
but will now be stored under the new member name.
1. From the MEMBER LIST SCREEN (see Figure 5-3), use the arrow keys or
< Tab > to move the cursor so that it is two spaces to the left of the member
name that you want to change.
5-6
IDEA User's Guide
February 29, 1996
-------
2. Type R (see Figure 5-6) and you will be in position to type over the existing
name. Use < Space > to erase any undesired characters.
3. When you are satisfied with the new name, press < Enter > and the member
name will be updated with the new name. Remember that you may not use
special characters or spaces in query names.
'_ I y.'_ .^ _S?1'', hs 1 •• vXSL'"', J V'L1*
Figure 5-6. Member List Screen - Renaming a Member
5.23 Writing I Updating a Query Description
Once you form a query and return to the Member List, you will probably want to
record a short description of the query to remind you of its contents. To write a new
description or change an old one, use the U (Update) command as described in the
following steps:
1. From the MEMBER LIST SCREEN (see Figure 5-3) use the arrow keys or
< Tab > to move the cursor so that it is two spaces to the left of the query name.
2. Type U (see Figure 5-7) followed by < Tab >. The cursor will be in position for
you to type in a description of up to 47 characters.
Chapter 5. Managing Libraries
5-7
-------
3. Press < Enter > when you are satisfied with your description. If you want to
change a description, follow the same process and type over the old description.
Use < Space > to erase any unwanted characters.
;tf"^iE5fj^^^
•;', 'VFiliofiffif fMspK ^i|i'i|ff ^ogratff
"' -.«...j.,4 jii'A * *^«&S.iU'. iif#sfi& i4f!v'?,_* ss>j-i
."- - r-lffi ,* !'<"i^MStpSif ^8/SslW^fftMfl?'6'1'6*^ •'
;
1 r •<*pEiHAiL. - $m$m&m^i!m$^i/vmi>m,A
Figure 5-7. Edit Member Screen - Updating a Description
5.2.6 Deleting a Query from the Member List
If you want to remove a member from your library's Member List, follow the steps
below. Keep in mind that deletions are permanent; the deleted query will be lost.
1. From the MEMBER LIST SCREEN (see Figure 5-3) use the arrow keys or
< Tab > to move the cursor so that it is two spaces to the left of the query that
you want to delete.
2. Type D and press < Enter >.
3. A message will be displayed in the top right corner of the screen asking you to
Confirm Delete. To confirm, type D once more followed by < Enter > . This will
delete the query. The name will remain on the screen, along with the word
**DELETED** under the CHANGED heading, until you have left the
MEMBER LIST SCREEN.
5-8
IDEA User's Guide
February 29, 1996
-------
Figure 5-8. Member List Screen - Deleting a Member
5.3 Allowing Access to your IDEA Library
Data security protection is controlled by an IBM product called RACF (Resource
Access Control Facility). If you want to allow other users, or groups of users, access
to your library it is necessary to update your library security information. For
example, you may want to do this to give IDEA User Support the ability to access
your library in order to provide query assistance.
Remember:
The library name that IDEA provides is a default name based on your NCC logon
prefix. The first three letters are your user ID; ithe second four letters are your
NCC account number.
All IDEA User Support personnel have NCC account A036. To grant IDEA
Support personnel access to your datasets, type the following RACF commands at
the READY prompt (see Figure 5-9).
Chapter 5. Managing Libraries
5-9
-------
Figure 5-9. READY Screen - RACF Commands
1. Type ALD 'UID.ACCT.*' UACC(READ) AUDIT(NONE) NOWARNING where
UID and ACCT are your user ID and account number, and press < Enter >. The
READY prompt will be returned.
2. Type PE 'UID.ACCT.*' ID(A036) ACCESS(UPDATE) and press < Enter >. The
READY prompt will again be returned. To grant other users access to your data-
sets, replace "A036" in Step 2 above with the appropriate NCC account number.
5.4 Summary
Your IDEA library is a work space that you must establish to use the Keyword Inter-
face option. Once you have established your library, you can create new members
(queries), change or delete existing members. You can also add a description to a
member to help you keep track of the contents of your library. Your IDEA library
with its members is similar to using WordPerfect directories and files.
The IDEA library processing differs from WordPerfect in that you must name your
member (query) prior to creating it. This process sets up a work space to compose
and run your query. If you decide to save it, the contents of the work space are
saved to the member (file) under the name you provided.
5-10
IDEA User's Guide
February 29,1996
-------
Chapters. Managing Libraries 5-11
-------
5-12 IDEA User's Guide February 29, 1996
-------
Chapter 6. Conducting a Search Using GO Names
This chapter provides detailed information on IDEA'S GO Names feature, which
allows users to build a query based on a facility name or location.
6.1 Introduction to GO Names
GO Names is a utility that allows you to form a query based on small bits of infor-
mation such as the facility name, state, county, EPA region, or ZIP code. This utility
is a Keyword function since it is accessed through the Keyword Interface and the
queries generated with it may be modified in the ISPF Editor (the EDIT SCREEN).
Its name searching feature uses an algorithm that recognizes consonant character
strings in the facility name, case name, defendant name, PRP (Potentially Responsible
Party) name, and available alias names from each of the program office data systems.
IDEA builds a query for you, based on the EPA ID number for each selected facility.
GO Names' Keyword format offers a number of query building advantages. For
instance, queries built in GO Names are returned to the ISPF Editor. In this mode,
you can modify your query using Keyword syntax to suit your purposes. This feature
allows GO Names to be used as a query builder by itself or as a handy precursor to a
custom Keyword query. GO Names also offers the flexibility of Keywords combined
with the important ability to search for facilities by name alone.
Before you can access the GO Names feature, you must choose the Keyword Inter-
face from the INTERFACE SELECTION SCREEN. IDEA will then ask you to
select a Hbrary in the INPUT LIBRARY SELECTION SCREEN. Your IDEA
library is where you will build and store your queries. The next few paragraphs
describe how to manage libraries. For a more detailed treatment of this subject refer
to Chapter 5, Managing Libraries.
Once you choose the Keyword Interface from the INTERFACE SELECTION
SCREEN, the LIBRARY SELECTION SCREEN will appear (see Figure 6-1). The
cursor should be positioned next to the LIBRARY NAME prompt.
Chapter 6. Conducting a Search Using GO Names 6-1
-------
Figure 6-1. Library Selection Screen
— Caution —^^——^———————"—-—
When working in the INPUT LIBRARY SELECTION SCREEN, do not press
< Enter > until you are finished editing the options on the screen; otherwise,
IDEA will take you to the next screen. If < Enter > is pressed accidently, press
PF3 or type END at the COMMAND prompt and press < Enter > to return to
the INPUT LIBRARY SELECTION SCREEN.
The library name shown in Figure 6-1 is a default name that IDEA provides based on
your TSO prefix. The first three letters are your user ID; the second four letters are
your NCC account number. IDEA default libraries have the extension
"QUERY.SPECS." You should use this default name for your first library.
If you want to use a different library or form a new library, type the name of your
choice over the default. Press < Space > to erase leftover characters.
Once you are satisfied with your library name, press < Tab > to move the cursor to
the LIBRARY STATUS(Shr/New/Old) prompt.
SHR The default status for your library is SHR (share). This status allows two
people to browse the library simultaneously. For example, if you call
IDEA User Support, the technician can look at your dataset with you.
NEW When you create a new library, you must change the status from SHR to
NEW, and press < Enter >. If you do not, a message will appear in the
top right corner of the screen informing you that the LIBRARY DOES
NOT EXIST.
OLD By changing the status to OLD, you will be given exclusive access to the
dataset.
6-2
IDEA User's Guide
February 29, 1996
-------
When you are satisfied with the library status, press < Enter >, and the MEMBER
LIST SCREEN will appear (see Figure 6-2). Members are queries that you compose
and store in your library as with books on a shelf or files in a WordPerfect directory.
This screen displays the member name, the date and time that is was created or last
changed, an optional description of the member's contents, and the user ID of the
person who last modified the member. If you have not created any queries up to
now, there will be no entries under the headings.
Figure 6-2. Member List Screen
When you create a new member in the library, you actually set up a work space for
composing and running your query. If you decide to save the query, the contents of
the work space will be saved to the member you named. Simple commands allow you
to browse, create, retrieve, rename, describe, and delete the queries in your Member
List. These commands are listed in Table 6-1, Member List Commands below. They
should be typed to the left of the member name or at the COMMAND prompt fol-
lowed by a space and the member name.
Table 6-1. Library Member List Commands
B query
E (or S) query
R query
U query
D query
Browse/Read the query; no editing possible.
Edit/Select an existing query or create a new one in
the editor.
Rename the query.
Update the query description.
Delete the query from the MEMBER LIST.
Chapter 6. Conducting a Search Using GO Names
6-3
-------
After you select a query or create a new query in the MEMBER LIST SCREEN,
press < Enter > . IDEA will bring you to the EDIT SCREEN illustrated in
Figure 6-3 .
j^terv pSJnrt sfi^&ft WiD'A * $iC$&*&^?ffr,
*M$$m'« &'$$%&• " -,'" '''JtellK rl1''."'
U« . Km1E.O { !M T , {E**. dt-iV , ,s ie s E e . <./• t t : ( {if.rfrfffrf .fi..t!c.( {
Figure 6-3. Edit Screen
6.2 £/5//ig GO Names to Form Queries
To access the GO Names function, use < Home > or < Tab > to place your cursor at
the COMMAND prompt in the EDIT SCREEN, type GO NAMES and press
< Enter > (see Figure 6-3). IDEA will bring up the NAME SELECTION MENU
SCREEN to build a name-based query (see Figure 6-4).
6-4
IDEA User's Guide
February 29, 1996
-------
Figure 6-4. GO Names Selection Screen
As Figure 6-4 illustrates, GO Names gives you the option of conducting your search
according to facility name, location, or a combination of the two. Press or
use your arrow keys to move the cursor from field to field on the screen.
6.2.1 The "Data Options?' Action Bar
When you run GO NAMES, the NAME SELECTION SCREEN in Figure 6-4 is pre-
sented. Provided in the upper lefthand corner of the NAME SELECTION SCREEN,
on the line above the NAME SELECTION MENU title, is the "Data Options" action
bar. To access this action bar, press < Home > (or use your Arrow keys to position
the cursor anywhere on the action bar). Press < Enter > to pull down a menu of the
data selection options available (see Figure 6-5J.
Chapter 6. Conducting a Search Using GO Names
6-5
-------
Figure 6-5. Selection Screen Data Options
Choosing option 1, "All available data," will cause IDEA to search for names in all
three of the FINDS, ERNS, and OSHA databases, and create a three-part query
based on EPA ID numbers from FINDS, Discharger ID numbers from ERNS, and
Inspection Activity numbers from OSHA. Because ERNS and OSHA are not in
FINDS, the default INPUT statement for the generated query is LINKED NON-
LINKED (see Section 4.4.1.3, Linked Nonlinked).
— Caution
Because the ERNS and OSHA data are not linked using FINDS, it is necessary to
run ERNS or OSHA queries as Nonlinked or Linked Nonlinked. This situation
should be considered when combining GO Names and GO MenuA keywords (see
Section 7.3.2, Combining GO MenuA and GO Names Queries).
Choosing option 2, "Exclude ERN" will instruct IDEA to limit the name search to
FINDS and OSHA. Choosing option 3, "Exclude OSH" will instruct IDEA to limit
the name search to FINDS and ERNS. Choosing option A, "Exclude ERN and
OSH," will instruct IDEA to limit the name search and query to FINDS alone. The
generated query will have a default INPUT statement of LINKED.
Note: It is not necessary to move the cursor to select option 2, 3, or 4. Simply type
2, 3, or 4, over the default entry of 1.
6-6
IDEA User's Guide
February 29, 1996
-------
— helpful hint '
The selection you make at the Data Options action bar will remain in effect for all
GO Names queries until you change the selection or exit the IDEA system.
You can make your "Data Options" selection either before you specify the GO
NAMES search criteria or after you have specified your criteria and received the "#
names selected" information (see Section 6.2.2, Searching for Facilities by Name).
6.2.2 Searching for Facilities by Name
Caution
While you are using the GO NAMES NAME SELECTION MENU, do not press
the < Enter > key until you have finished typing in all the necessary information.
Pressing < Enter > will instruct IDEA to run the name search function, so use the
< Tab > key and arrow keys to navigate the screen.
GO Names uses a soundex algorithm to search for facilities. It takes the first char-
acter of the name and the next three distinct consonants and searches for facility
names that match them in an effort to find facilities that sound like the one you
entered. If a facility name matches this pattern, it will appear in the list that is
returned to the EDIT SCREEN. For instance, if you enter the name Chempyro, the
names search algorithm will use the letters CHMP, so your search could retrieve facil-
ities named Chempoly, Champion Goods, or Mr. Champs Food Stores. You will
have to delete any mismatched facilities (called "false positives") from your query.
(Refer to Section 6.4.1, Modifying a GO Names Query for instructions.)
You can enter the name of a specific facility (e.g., Schlage Lock Company). If you
want information about a specific facility but can only remember part of the name,
enter the word(s) that you know. GO Names can still help because it will search for
all facilities that contain the word(s) you enter (e.,g., Schlage or Lock).
To form a query according to facility name alone, take the following steps:
1. Use < Tab > or the arrow keys to move the cursor to the right of the NAME
prompt.
2. Enter the name that you want IDEA to search for, and press < Tab >.
3. Type ANY at the WORDS REQUIRED (ALL/ANY) prompt if you want IDEA
to find facilities whose names match with ANY of the words you enter. ALL is
the default and will instruct IDEA to search for facility names that match with all
the words you have entered.
Chapter 6. Conducting a Search Using GO Names 6-7
-------
If you type ANY, GO Names will search for each word separately, performing what is
known as a Boolean OR. In other words, choosing ANY tells IDEA to retrieve the
names of those facilities which have any of the chosen words in their titles. If you
enter Schlage Lock and select ANY, IDEA will list those facility names that include
either word: Schlage OR Lock. If, on the other hand, you decide to select ALL
words (or leave it as the default), GO Names will only retrieve facility names that
contain all the chosen words. In this case, IDEA puts a Boolean AND between the
words. Using our example again, if you chose the ALL option you would only get
facilities with both the words Schlage AND Lock in their titles.
I— helpful hint "~
Once you have typed in the facility names you want IDEA to search for, press
< Enter > ; IDEA will run your name search.
See Section 6.3, Managing Queries in the ISPF Editor Mode to learn how to return the
list of names to the editor.
6.2.3 Searching for Facilities by Location
While the GO Names function is typically used to select facility records based on
their name, it can be used to create a query that will select all facilities in a specified
geographic area. This can be useful for looking at all facilities in a small geographic
area and if you wish to view and/or edit the facility name data prior to running the
query.
The keyword queries that IDEA generates are based on facility ID numbers, and can
provide one or more lines of information per facility. Because of this construction,
queries based solely on geographic parameters can be rather lengthy. Therefore, the
GO Names function is not recommended for generating geographic queries beyond
the ZIP code level without also specifying a facility name.
To begin a location search, use the arrow keys or press < Tab > to place the cursor
two spaces to the right of the prompt you are answering. Enter the appropriate
value(s) to indicate the state(s), region(s), ZIP code(s), county, or counties you want
IDEA to search.
State To enter the state code, type in the two letter state abbreviation used by
the U.S. Postal Service. You may enter up to five states per search.
6-8
IDEA User's Guide
February 29, 1996
-------
County The county code is a five character code of the following pattern: the first
two characters are the two letter postal abbreviation for the state in which
the county is located and the last three spaces are left for the three-digit
FIPS county code. You may enter up to five county codes per search. A
list of county codes is available in the IDEA Menu Interface (see Section
4.2.2, Location Category ).
Region The region entry refers to the EPA region number. Each EPA region is
composed of several states and numbered from one to 10. Be sure to
include a zero before regions one throuigh nine. You may enter up to seven
EPA regions per search. This is the least specific location criterion offered
in GO Names.
ZIP The ZIP code is the five digit code assigned to specific areas by the U.S.
Postal Service. You may enter up to five ZIP codes per search. This is the
most specific location criterion in GO Names.
When you are using GO Names, IDEA inserts a Boolean OR between all of the
location entries that you have chosen. In other words, IDEA will retrieve all the
facilities in each of the geographic areas you have selected. Thus, you should be as
specific as possible to avoid calling up more facilities than you need.
For example, if you want to find all the EPA regulated facilities in Montgomery
County, Maryland, you should enter only the county code. If you were to enter the
state abbreviation (MD) as well as the EPA region number (3), IDEA would read
your query in the following manner: find all facilities in EPA Region 3 in addition to
(OR) all facilities in Maryland in addition to (OR) all facilities in Montgomery
County, MD. As you can imagine, you would have to sift through far more facility
names (all the facility names in Region 3 in this example) than you had planned. On
the other hand, Boolean ORs come in handy when you need to find all facilities in
Virginia and Maryland, for example, or Virginia in addition to Montgomery County,
MD.
— helpful hint ————^—^^————^^^—^———~^^—^^^—
When you are satisfied with your entries, press the < Enter > key to run the
facility selection function.
Chapter 6. Conducting a Search Using GO Names
6-9
-------
6.2.4 Searching for Facilities by Name and Location
Probably the most common use of the GO Names function is the combination of the
previous two sections: specifying both a facility name and a location parameter. For
name queries of this type, the line that reads "Other values that may be Ored together
and the result ANDed with the name above" tells you that IDEA inserts a Boolean
OR between each location entry and then inserts a Boolean AND between the facility
name and the location entry.
In other words, IDEA will search for the facility name in any of the location(s) you
select and provide you with a list of facilities that match that name.
— helpful hint ^^——————————-——
Enter the facility name and location values just as described in the previous two
sections, press < Enter > and IDEA will run your name search.
See Section 6.3, Managing Queries in the ISPF Editor Mode, to learn what to do with
a query after using GO Names.
6.3 Managing Queries in the ISPF Editor Mode
After you tell IDEA to run the name search by pressing < Enter > on the NAME
SELECTION MENU SCREEN, the total number of possible matches to your name
and/or location appears under the ZIP code prompts (see Figure 6-6).
If you are not satisfied with the number of facilities that your search turns up then
you can redefine your query by changing your Data Options selection or by entering
facility name and/or location values that are more specific than what you originally
entered.
6-10
IDEA User's Guide
February 29, 1996
-------
*?{,;*,{ (cr&^&! it $?cf i tfe c (Vt{ci * *W{ t t t "ct^''11 (*"({{*
•SfcV^.'.l v'^X .v*','Mfr^ •','!I,A* •' Iff I',c'i,hH!$',
j'i'j.g.j,j;i|.;y ;tft; ;|j'!fiy2.'''V.tglJi..1ll.g.:.l.flfe!f.l
Figure 6-6. GO Names Facility Count Returns
As shown in Figure 6-6, two prompts also appear at the bottom of the screen after
you have made name and/or location selections, a!nd pressed < Enter >: RETURN
NAMES TO QUERY and CORP. PROF. (Y/N). Your responses to these prompts
will determine the nature and appearance of the query IDEA builds for you.
6.3.1 Returning a Facility List to a Query
The first prompt, RETURN NAMES TO QUERY, gives you the option of specifying
one of three ways to return the names to the EDIT SCREEN. They differ in the
amount of facility information included:
Y(es) Returns the facility name, the source database name, and local ID number
to the query.
Example:
Schlage Lock Co (RCR CAD98209356)
A(U) Returns to the query the same data as Y(es) plus the facility name in each
of the databases to which it is linked in FINDS and the source database
names and IDs.
Chapter 6. Conducting a Search Using GO Names
6-11
-------
Example:
Schlage Lock Co (RCR CAD98209356)
Schlage Lock Company (NCD CAD983647785)
M(ax) Returns everything in A(ll) plus the address for the facility in each of the
databases, its EPA region and FIPS county code.
Example
Schlage Lock Co (RCR CAD98209356)
2401 Bayshore Blvd
San Francisco CA 94134 09 075
Schlage Lock Company (NCD CAD983647785)
2401 Bayshore Blvd
San Francisco CA 94134 09
63.2 Getting a Dun & Bradstreet Corporate Profile
The second prompt, CORP. PROF. (Y/N), asks whether or not you would like to
create a corporate-based query using the Dun & Bradstreet Market Identifiers data-
base. The default response of N (No) will instruct IDEA to build a query based on
the FINDS, ERNS, and OSHA (depending on your Data Options setting) ID
numbers of the facilities from your Names search. A Y (Yes) response will cause
IDEA to base the query on the Dun & Bradstreet ultimate parent numbers of the
Names search facilities. If you have included ERNS in your search, the query will
have a second part based on ERNS Discharger ID numbers.
A corporate profile query (or the linked portion of a corporate profile/ERNS query)
will list all of the facilities that have parent and subsidiary relationships to the facili-
ties you have chosen. By selecting all facilities that are linked to the same corporate
"ultimate parent," the entire corporate tree of the named facility can be retrieved.
Producing the query depends on an existing link in FINDS to the Dun & Bradstreet
numbers, as well as a link to the corporate ultimate parent; this link may not exist in
some cases.
If you choose to generate a corporate profile, you will see facilities listed under one of
three headings. The first, NO DUNS NUMBER, indicates that no Dun & Bradstreet
number for those facilities exists in FINDS. The second heading, NOT IN A CORP.
TREE, tells you that no corporate tree - no parent or subsidiary relationships - exists
in Dun & Bradstreet. Finally the third header, CORP. TREE NUMBER, precedes
the facilities that share a corporate relationship with the facilities that matched your
GO Names criteria. Figure 6-7 illustrates two of these headings in a query.
6-12 IDEA User's Guide February 29, 1996
-------
Figure 6-7. Dun & Bradstreet Keywords
6.4 Looking at a GO Names Ouerv
Once you have returned the facility list to your query by selecting Y, A, or M, and
CORP. PROF. Y or N, and pressing < Enter >, IDEA takes you to the EDIT
SCREEN and displays the GO Names query you have constructed.
Figure 6-8 represents a portion of a GO Names-generated facility query based on
EPA ID numbers. The first two lines (numbers 000001-000002) on the screen contain
comments indicating the selection criteria, and how many names were selected. The
Keyword query logic follows these comments. (A brief explanation of Keywords will
be given here - see Chapter 8, Conducting a Search Using Keywords for a more
detailed treatment of the subject.)
The first line of the actual query logic (line no. 000003) indicates that when you run
this query, you will receive OUTPUT in REPORT format 1A. The next line indicates
that the INPUT data that IDEA will use to process your query will be LINKED
NONLINKED; i.e. the FINDS system will be used to integrate data taken from the
program office databases, then data from the ERNS database will be retrieved sepa-
rately (since ERNS is hot linked to the other systems through FINDS). (See
Chapter 2, IDEA: What it Does & How it Works, for a discussion of linked and non-
linked data in IDEA.)
Chapter 6. Conducting a Search Using GO Names
6-13
-------
-'-***•***
Figure 6-8. A GO Names Query in the Edit Screen
Lines 000005 and 000016 indicate the SELECTion criteria that IDEA is using in the
query. When you conduct a name search, GO Names takes the name you enter and
looks up all the facilities with matching names in the FINDS (FIN) and ERNS
(ERN) databases. FINDS provides a list of EPA identification numbers (EPID),
while ERNS provides a list Discharger identification numbers (OWNID). Finally,
IDEA sets up the query as shown in Figure 6-8 and returns it to you with the ID
numbers of all the facilities. IDEA also provides the facility names for your conven-
ience, but they are not actually part of the query. The characters /* tell IDEA to
ignore anything to their right on the same line.
Technical Note: IDEA uses an enhanced version of the FINDS database. It is
enhanced during the monthly program file refresh/update cycle to include facil-
ities that the OIRM FINDS file does not contain. If a facility from a
program office data system is not included in the OIRM FINDS file, IDEA
will generate a pseudo EPA ID Number for that facility record. These
IDEA/EPA ID Numbers can be readily distinguished from officially assigned
numbers as they contain the character string "IDEA" starting in the third
position of the number. In this way, every facility that is provided to IDEA
from EPA's program office data systems can be included in this enhanced
FINDS file.
By selecting this facility by its IDEA-generated FINDS ID, the facility will
appear in the Linked portion of the report. It any criteria from its "local"
database, PCS, is used, the facility would come out in the Nonlinked portion
of the report, under its PCS NPDES ID.
6-14
IDEA User's Guide
February 29,1996
-------
6.4.1 Modifying a GO Names Query
As discussed in Section 6.2.2, Searching for Facilities by Name, when IDEA searches
for names, it uses a system that looks for matches to the first character and the next
three consonants or numbers of each word you eater; it does not attempt an exact
character-for-character match. For this reason, }rou may wish to delete lines that
contain "false positives" -- facility names that are not of interest to you (e.g. Luck
School District, shown on line 000009).
The ISPF EDIT SCREEN, in which your GO Names query is displayed, is a scrolling
display text editor (word processor) that allows you to type over any data displayed
and perform certain editing functions. General commands (e.g., END, CANCEL) are
entered next to the COMMAND prompt on the second line of the screen. Any
editing operations (e.g. deleting or moving lines) are performed by entering a
command directly on the line number(s) of the affected line(s). Table 6-2 lists several
of the line commands available.
Table 6-2. Line Editing Commands
C Copy this line
M Move this line
D Delete this line
CC, MM, or DD Mark starting and ending lines for copying, moving,
or deleting a block of lines.
Cn,Mn,Dn Copy, Move, Delete next n lines
A Place moved/copied lines after this line
B Place moved/copied lines before this line
I Insert a line
-In Insert n lines
As an example of how these commands are used, suppose that you are only interested
in the first facility listed in the above query (Figure 6-8), the one with EPA ID
number COD082657420. You would perform the following steps to delete lines 8
through 13 and edit the query:
1. Use < Tab > or the arrow keys to move the cursor to the first line you wish to
delete (line 000008) and type DD directly over the zeros in the line number.
2. < Tab > or arrow down to the last line of the block you wish to delete (line
000013, the last line in the query) and type DD over that line number as well.
3. Check your work to make sure you marked the correct lines (deletions are perma-
nent!!), then press < Enter > to delete the block of lines.
4. Use < Tab > and the arrow keys to move the cursor to the end of the EPA ID
number in line 000007, and < Space > over the comma to remove it.
Chapter 6. Conducting a Search Using GO Names 6-15
-------
— helpful hint — """"
If you delete the last facility in a list of facilities, you must make sure that there
are no commas in the entry that is last in the resulting list. Note that the facilities
in lines 7, 8, 11, and 12, of Figure 6-7 have commas, but the entries in lines 9 and
13 do not.
Table 6-3 below highlights several other commands available for use in the EDIT
SCREEN, including commands for scrolling (should your query be too long to fit on
a single screen). Chapter 9, Managing Keyword Queries and the ISPF Editor contains
detailed instructions for using all of the ISPF Editor features introduced in this
Chapter.
Table 6-3. ISPF Keys and Commands (default values)
Command
END PF3/PF15
RETURN
PF4/PF16
UP PF7/PF19
DOWN PF8/PF20
LEFT PF10/PF22
RIGHT PF11/PF23
To maneuver the
cursor around
IDEA screens
To reset the key-
board when it locks
up
Mode
Edit
Browse
Edit & Browse
Edit & Browse
Edit & Browse
Edit & Browse
Edit & Browse
Description
Saves changes and returns to the previous screen.
(Returns to the previous screen without saving when in
Menu Interface.)
Returns to the previous screen.
Returns directly to the previous Primary Option
Menu.
Scrolls up by the amount set at the SCROLL or
COMMAND prompt.
Scrolls down by the amount set at the SCROLL or
COMMAND prompt.
Scrolls left by the amount set at the SCROLL or
COMMAND prompt.
Scrolls right by the amount set at the SCROLL or
COMMAND prompt.
Use arrow keys for all directions; use < Tab > key to
move the cursor from prompt to prompt; use
< Home > to move the cursor to the top-left prompt
< Reset > key; < Ctrl > key with R; right < Alt > ,
depending on your keyboard configuration
Report 1A is the default report format used by GO Names. You may change formats
by typing another format over 1A, and you may select additional formats by typing
in REPORT on the same line and specifying another format. The keyword
"REPORT" must be entered each time another report is specified. For example, if
you want reports 1A, 2, and SUMMARY, the OUTPUT line should look like this:
OUTPUT REPORT 1A REPORT 2 REPORT SUMMARY
6-16
IDEA User's Guide
February 29, 1996
-------
See Table 6-4 for a brief description of the different report formats available in
IDEA.
Table 6-4. IDEA Standard Reports
There are currently four standard IDEA report formats: 1A, IB, 2, and Summary.
REPORT 1A
A brief report of individual facilities. Organized by the linked database, IDEA displays the
facility name and database identifier, location and other business information, noncompliance
or violation status, and enforcement information.
REPORT IB
A more detailed presentation of information on individual facilities, including historical and
programmatic data such as dates and results of inspections, specific toxic substances reported,
and details of enforcement actions.
REPORT 2
A linked docket table that indicates whether each facility is listed as a significant noncomplier
or high priority violator.
REPORT SUMMARY
Provides total facility counts by program and EPA region; sum of facilities that are in compli-
ance and not in compliance by program and total numbers of enforcement actions by
program; and total toxic substance release information for the selected facilities.
6.5 Runnins a GO Names Query
Once you are satisfied with the content of your query, you are ready to run the query
and receive the report(s) you have specified. To :run a Keyword query, use < Home >
or < Tab > to move your cursor to the COMMAND prompt, type GO, and press
< Enter >.
From here, IDEA processes the query and then presents the QUERY STATUS
SCREEN, shown below in Figure 6-9 .
Chapter 6. Conducting a Search Using GO Names
6-17
-------
Figure 6-9. Query Status Screen
6.6 Viewing a Query Report
If you choose to see the reports, IDEA will deliver information to your screen
according to the format(s) you selected earlier. The report is presented to you in the
BROWSE mode (see Figure 6-10) which allows you to view, print, or save data, but
not alter it. To maneuver through the report, use PF7 to page up, PF8 to page
down, PF10 to scroll left, and PF11 to scroll right. If you selected multiple report
formats, type SW at the COMMAND prompt to switch to the next report. See
Chapter 10, IDEA Standard Reports for more details.
6-18
IDEA User's Guide
February 29, 1996
-------
If tkfilai? ;^^
Figure 6-10. Report 1A in Browse Mode
6.7 Exiting GO Names
To exit the Keyword Interface at any time follow these procedures:
• To save your current work, use the END command (PF3 key) to back out of the
program screen by screen.
• If you would rather exit without saving, use the CANCEL command at the EDIT
SCREEN, then use END or PF3 to back out screen by screen.
• Use the RETURN (PF4) command to return to the OFFICE OF ENFORCE-
MENT DATA INTEGRATION PRIMARY MENU (your current work will be
saved), then type I for IDEA at the OPTION prompt to get back to the IDEA
WELCOME SCREEN, or type X to exit to the TSO READY prompt.
• Or type =X at the COMMAND line to go directly to the TSO READY prompt
(your work will be saved automatically).
Chapter 6. Conducting a Search Using GO Names
6-19
-------
6.8 Summary
GO Names is a utility that allows IDEA users to build a query based on a facility
name or location parameters. This utility applies an algorithm that recognizes conso-
nant character strings within names. GO Names allows users to specify how much
information is returned to the ISPF editor. It will return a Dun & Bradstreet corpo-
rate profile if the CORP. PROF. (Y/N) option is selected. GO Names will return
facility information to the ISPF editor where it can be reviewed, edited, or run as a
query.
6-20
IDEA User's Guide
February 29, 1996
-------
Chapter 7. Conducting a Search Using GO MenuA
IDEA'S GO MenuA utility allows you to build a query in the Keyword Interface by
using the Menu Interface.
7.1 Introduction to GO MenuA
The GO MenuA utility allows you to build a queiy in the Menu Interface and edit it
in the Keyword Interface. The Menu Interface is the simplest means of retrieving
information from IDEA. It provides convenient pop-up windows for you to form
queries simply by selecting criteria from lists. Although easy to use, the Menu Inter-
face is fairly rigid because it makes some assumptions about the data selection and
logical structure of a query. These assumptions cannot be altered in this interface.
The Keyword Interface, on the other hand, is not as easy to use but allows you more
freedom. It is a word processor that allows you to build queries from scratch
according to almost any criteria found in the linked IDEA databases. This wide
range of choices gives you the ability to form very detailed queries involving many
variables. The hard part is that you must know the correct query syntax to build
Keyword queries from scratch. You have more freedom because you can tailor the
query, including the query logic, to suit your needs. By using the GO MenuA utility,
you have the advantages of both interfaces ~ the convenience of a ready-built query
from the Menu Interface and the flexibility to edit; it within the Keyword Interface to
suit more specific needs.
7.2 Gettins Started
Before you can access the GO MenuA feature, you must choose the Keyword Inter-
face from the INTERFACE SELECTION SCREEN. IDEA will then ask you to
select a library in the INPUT LIBRARY SELECTION SCREEN (see Figure 7-1).
Your IDEA library is where you will build and store your queries. For more infor-
mation on this topic, refer to Chapter 5, Managing Libraries.
Chapter 1'. Conducting a Search Using GO MenuA 7-1
-------
I— Caution
When working in the INPUT LIBRARY SELECTION SCREEN, do not press
< Enter > until you are finished editing the options on the screen; otherwise,
IDEA will take you to the next screen. If < Enter > is pressed accidently, press
PF3 or type END at the COMMAND prompt and press < Enter > to return to
the INPUT LIBRARY SELECTION SCREEN.
Figure 7-1. Input Library Selection Screen
To accept the default values listed at the LIBRARY NAME and the LIBRARY
STATUS(Shr/New/Old) prompts, press < Enter >; and the MEMBER LIST
SCREEN will appear (see Figure 7-2). Members are queries that you compose and
store in your library as with books on a shelf or files in a WordPerfect directory. The
queries in the Member List will be available to you each time you use IDEA. If you
have not created any queries up to now, there will be no entries under the headings.
7-2
IDEA User's Guide
February 29, 1996
-------
Figure 7-2. Member List Screen
When you create a new member in the library, you actually set up a work space for
composing and running your query. If you decide to save the query, the contents of
the work space will be saved to the member you named. Simple commands allow you
to browse, create, retrieve, rename, describe, and delete the queries in your Member
List. These commands are listed in Table 7-1, Member List Commands below. They
should be typed to the left of the member name or at the COMMAND prompt fol-
lowed by a space and the member name.
Table 7-1. Library Member List Commands
B query
E (or S) query
R query
U query
P query
Browse/Read the query; no editing possible.
Edit/Select an existing query or create a new one in
the editor.
Rename the query.
Update the query description.
Delete the query from the MEMBER LIST.
To create a query, type E at the COMMAND prompt, press < Space >, type the
name of the new query (for example, E NEWQUERY as in Figure 7-2 ), and press
< Enter >.
| helpful hint
Query names can be up to eight characters long including numbers and letters but
not special characters such as @#$% &*()"?/!.
After you choose to create or edit a query from the MEMBER LIST SCREEN, the
EDIT SCREEN will appear (see Figure 7-3).
Chapter 7. Conducting a Search Using GO MenuA
7-3
-------
73 Usins GO MenuA
To access the GO MenuA utility, type GO MENUA at the COMMAND prompt of
the EDIT SCREEN, and press < Enter > (see Figure 7-3). It does not matter where
in the current member you are, GO MENUA will always return the Keyword logic
you generate to the top of the current member.
Figure 7-3. Blank Edit Screen
As shown in Figure 7-4 , the MAIN MENU SCREEN of the Menu Interface will
appear. With this utility, you can select criteria from the Menu Interface, and GO
MenuA will generate a Keyword query for you back in the Keyword Interface.
7-4 IDEA User's Guide
February 29, 1996
-------
. h'S.1 <<,.i
!^
Figure 7-4. Main Menu Screen
— helpful hint ———-—^•""•"•———~~^-———
To choose a category in the Menu Interface, use < Tab > to move the cursor to
the left of the category name, then type S (for select) followed by < Enter >. This
sequence is used whenever you want to make a selection from the IDEA Menu
Interface.
For more information on building a query in the Menu Interface, refer to Chapter 4,
Conducting a Search Using the Menu Interface.
To illustrate one possible use of the GO MenuA utility, we will use it to generate
some noncompliance keyword logic, then combine that with a name search using GO
Names. The combined query will then select only those named facilities that are also
noncompliers.
The GO MenuA portion of the query will find facilities that are noncompliers or sig-
nificant noncompliers in any of the program office databases accessed by IDEA.
(This is merely an exercise that has no basis in fact regarding any planned or on-
going enforcement initiatives.) Select noncompliance criteria in the Menu Interface
as shown in Figure 7-5 .
Chapter 7. Conducting a Search Using GO MenuA
7-5
-------
.i.» .; r .. .
5
" -8 • '&f'--'&&£*,'£sf&8MAff-
tf&£l&£ * &tH ,< L J(t«{i=—i_t «,n.J,:£ iSsiJittt'.i'ta.Vd(- Vj.*;5,
Figure 7-5. Noncompliance Criteria in the Menu Interface
— helpful hint ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^-~-'-~------
When you are satisfied with the content of your query, type S next to RUN
QUERY , and press < Enter >.
The INPUT REPORT SELECTION SCREEN will appear. Select the type of search
you want to conduct (linked, nonlinked, or linked nonlinked), the report format(s)
you want to view (1A, IB, 2, SUMMARY), and press < Enter >.
If you were simply building a query in the Menu Interface, IDEA would run your
search at this point, and the QUERY STATUS SCREEN would appear. The GO
MenuA utility of the Keyword Interface, however, generates a Keyword query and
returns it to the editor for you to edit, at the top of the member you are currently
editing. Therefore, the EDIT SCREEN will appear with the Keyword query you have
just generated. For example, the query criteria in Figure 7-5 generated the keywords
in Figure 7-6 .
7-6
IDEA User's Guide
February 29, 1996
-------
!4!* "Mm .idtaVsfe&S At!. $$£
-------
• Line 000010 - A comment line that notes the Menu category from which the fol-
lowing keywords were generated. In this case, the keywords came from the Non-
compliance Category.
• Lines 000011 to 000016 ~ Parentheses are included for each database condition
and for each Menu category. These lines make up the rest of the SELECT state-
ment.
Once you have generated a Keyword query using GO MenuA, you have several
options. You can edit the query, add more criteria to it (by accessing the GO Names
utility, by running GO MenuA again, or advanced users might add Keyword logic of
their own), or run it as it is.
7.5.7 Editing GO MenuA Queries
The ISPF EDIT SCREEN is a scrolling display format that allows you to type over
or delete any data that is displayed. You can edit the lines in the query with the
commands in Table 7-2, Line Editing Commands. Type these commands over the line
numbers at the left of the EDIT SCREEN. Chapter 9, Managing Keyword Queries
and the ISPF Editor describes how to edit Keyword queries in detail.
Table 7-2. Line Editing Commands
C
M
D
CC, MM, DD
C«,M«,D«
A
B
I
Jte
Copy this line
Move this line
Delete this line
Mark starting and ending lines for copying, moving,
or deleting a block of lines.
Copy, Move, Delete next n lines (including this line)
Place moved/copied line(s) after this line
Place moved/copied line(s) before this line
Insert a line after current line
Insert n lines after current line
For more information on the Keyword query you generated, refer to Chapter 8, Con-
ducting a Search Using Keywords.
7.3.2 Combining GO MenuA and GO Names Queries
You can add facility name and/or location parameters to your query using the GO
Names utility. To access this utility, type GO NAMES at the COMMAND prompt,
and press < Enter >.
7-8
IDEA User's Guide
February 29, 1996
-------
— Caution
While you are using the GO NAMES NAME SELECTION MENU, do not press
the < Enter > key until you have finished typing in all the necessary information.
Pressing < Enter > will instruct IDEA to run the name search function, so use the
< Tab > key and arrow keys to navigate the screen.
Enter name and/or location parameters in the NAME SELECTION MENU
SCREEN, and press < Enter > . To recreate the example in Figure 7-7 , type
CAMPBELL SOUP at the NAME prompt and NJ at the STATE (SS) prompt.
After you are satisfied with your entries, press the < Enter > key to run the facility
selection function. IDEA will display the number of possible matches it found for
your name and/or location criteria followed by two prompts, which are explained
below. If you are not satisfied with the number of possible matches, you can edit
your entries, and press < Enter >. IDEA will dissplay the number of possible matches
for your new criteria.
ill
Figure 7-7. Name Selection Menu Screen
The prompt, RETURN NAMES TO QUERY, gives you the option of specifying one
of three ways to return the names to the EDIT SCREEN. Type Y at this prompt,
press < Enter > , and the GO Names keywords will be returned to the EDIT
SCREEN followed by those generated from GO MenuA. In Figure 7-8 , lines 000001
to 000009 were generated by GO Names and lines 000010 to 000021 came from GO
MenuA. •
Chapter 7. Conducting a Search Using GO MenuA
7-9
-------
Note: When IDEA searches for names, it uses a soundex algorithm that looks for
matches to the first character and the next three consonants of each word you
enter. For this reason, your query may contain some "false positives" -- facili-
ties with names that do not exactly match the one you are looking for. You
should delete any extraneous facilities from your list.
Caution
If you delete the last facility in the GO Names portion of the query, you must
make sure that there are no commas in the entry that is last in the resulting list.
Note that the facilities in lines 000007 and 000008 of Figure 7-8 have commas, but
the facility entry in line 000009 does not.
If you need more information about GO Names, refer to Chapter 6, Conducting a
Search Using GO Names.
-, EDIT" ---^''inp^ccf ^jfefp
""''"1
• BQ88S4
Hww6
-BQ88B6 , SELECT
1 89B8(# ' ''
i seaeW \
a' -^B^^j^^^^j^^^
- 908811 i*^^^s^^A\^:^.&^^
• •_._.?* *.-. '^-w,.:«,-»wyAS*uJ'*^,''i'.i
Figure 7-8. Edit Screen with Names Keywords
Since the GO MenuA and GO Names utilities were designed to generate self- con-
tained Keyword queries, you have to modify the query that results from combining
them in order to preserve proper query syntax. There are two steps to modifying the
query:
7-10
IDEA User's Guide
February 29, 1996
-------
1. Insert the word AND between the two queries (between lines 000009 and 000010
in Figure 7-8 ). To do this step, type I on line 000009 (over the line number
itself), and press < Enter > . Then type AND,, and press < Enter > two times.
2. Delete the INPUT, OUTPUT, and SELECT statements in the second query,
which occupy lines 000019 and 000020 in your query now. To do this step, type
D2 on line 000019 (over the line number itseU:), and press < Enter >.
Figure 7-9 shows the sample query after these changes have been made.
;lSMl^:l4iaS^^
•q ,'M£ ^u. &£ «•: liAfei ,M'
Figure 7-9. Edit Screen with changes shown
7.4 Runtime a GO MenuA Ouerv
To run the query, use < Home > or < Tab > to move your cursor to the
COMMAND prompt, type GO, and press < Enter >. From this point, IDEA will
process the query and display the QUERY STATUS SCREEN shown below in
Figure 7-10 . In the sample query, two facilities were found that met all of the cri-
teria.
Chapter 7. Conducting a Search Using GO MenuA
7-11
-------
Figure 7-10. Query Status Screen
7.5 Viewing Reports
If you choose to see the report, IDEA will deliver information to your screen
according to the format designated on the OUTPUT line of your query. The report is
presented to you in BROWSE mode which allows you to view, print, or save data,
but not alter it (see Figure 7-11). To maneuver through the report, use PF7 to page
up, PF8 to page down, PF10 to scroll left, and PF11 to scroll right. If you selected
multiple report formats, type SW at the COMMAND prompt to switch to the next
report.
7-12 IDEA User's Guide
February 29, 1996
-------
m* 'W'' /&g&.i..
ly.v-.is*1. iiii fiftr^
Figure 7-11. Report 1A in Browse Mode
7.6 Exiting GO MenuA
Since the GO MenuA utility runs from within the Keyword Interface and uses the
Menu Interface, you can exit this utility from either of these interfaces.
To exit from the Menu Interface, follow these steps:
• Press PF3 to back up to the EDIT SCREEN of the Keyword Interface.
The criteria you have selected in the Menu Interface will be preserved in
the Menu Interface, but the keyword query will not be generated unless
you select RUN QUERY from the Menu Interface.
From the Keyword Interface, you have the following options:
• To get back to the INTERFACE SELECTION SCREEN (at any time)
Chapter 7. Conducting a Search Using GO MenuA
7-13
-------
And save your work -- Type END at the COMMAND prompt or press PF3 to back
out of the program screen by screen. This method saves your work.
Without saving your work -- Type CANCEL at the COMMAND prompt of the
EDIT SCREEN then use END or PF3 to back out screen by screen.
To return to the OFFICE OF ENFORCEMENT DATA INTEGRATION
PRIMARY MENU, use the RETURN (PF4) command (your current
work will be saved). Type I for IDEA at the OPTION prompt to get
back to the IDEA WELCOME SCREEN, or type X to exit to the TSO
READY prompt.
• To go directly to the TSO READY prompt, type =X at the
COMMAND prompt. Your work will be saved automatically.
7.7 Summary
GO MenuA is a utility that allows you to build a Keyword query by selecting criteria
from lists in the Menu Interface. If you use GO MenuA, you can have the conven-
ience of the Menu Interface and the flexibility of the Keyword Interface while assem-
bling your query. After constructing a query with GO MenuA, you can edit it, add
to it using the GO Names utility, or run it as it stands.
7-14 IDEA User's Guide February 29, 1996
-------
Chapter 8. Conducting a Search Using Keywords
This chapter provides detailed information on IDEA Keyword Queries.
8.1 Introduction to IDEA Keywords
The Keyword Interface allows you to conduct a search according to almost any cri-
teria that can be found in the linked IDEA databases. This wide range of choice
gives you the ability to form very detailed queries involving many variables; a luxury
that is not available to you when using the Menu functions. To use Keywords you
must have a good idea of what you are searching for and how to find it. This chapter
will teach you how to take the search criteria you have and use the IDEA Keyword
Query Language (IKQL) to gather the information you need.
To build a Keyword query, choose the Keyword Interface from the INTERFACE
SELECTION SCREEN (see Figure 5-1). IDEA will then ask you to select a library
in the INPUT LIBRARY SELECTION SCREEN (see Figure 8-1). Your IDEA
library is where you will build and store your queries. For more information on this
topic, refer to Chapter 5, Managing Libraries.
I— Caution
When working in the INPUT LIBRARY SELECTION SCREEN, do not press
< Enter > until you are finished editing the options on the screen; otherwise,
IDEA will take you to the next screen. If < Enter > is pressed accidently, press
PF3 or type END at the COMMAND prompt and press < Enter > to return to
the INPUT LIBRARY SELECTION SCREEN.
Chapter 8. Conducting & Search Using Keywords 8-1
-------
Figure 8-1. Input Library Selection Screen
To accept the default values listed at the LIBRARY NAME and the LIBRARY
STATUS(Shr/New/Old) prompts, press < Enter >; and the MEMBER LIST
SCREEN will appear (see Figure 8-2). Members are queries that you compose and
store in your library as with books on a shelf or files in a WordPerfect directory. The
queries in the Member List will be available to you each time you use IDEA. The
list displays the member name, the date and time that it was created or last changed,
an optional description of the member's contents, and the user ID of the person who
last modified the member (see Figure 8-2). If you have not created any queries up to
now, there will be no entries under the headings.
8-2
IDEA User's Guide
February 29, 1996
-------
Figure 8-2. Member List Screen
When you create a new member in the library, you actually set up a work space for
composing and running your query. If you decide to save the query, the contents of
the work space will be saved to the member you named. Table 8-1 below is a
summary of the command options used for managing a member list. They should be
typed to the left of the member name, or at the COMMAND prompt followed by a
space and the member name. An existing member can be selected and edited or a
new one created by typing E or S followed by the member name at the COMMAND
prompt.
Table 8-1. Library Member List Commands
B query
E (or S) query
R query
U query
P query
Browse/Read the query; no editing possible.
Edit/Select an existing query or create a new one in
the editor.
Rename the query.
Update the query description.
Delete the query from the MEMBER LIST.
After you select a query to edit, or create a new one, press < Enter > . IDEA will
bring you to the EDIT SCREEN illustrated in Figure 8-3 .
Chapter 8. Conducting a Search Using Keywords
8-3
-------
EDIT -— __-_,™n
CQrtwNB-fs-'1;±.
Figure 8-3. Edit Screen
Before getting started, a glance at Table 8-2 will provide you with some helpful tips
for maneuvering around the Keyword Interface. For more information on navigating
Keyword screens, see Chapter 9, Managing Keyword Queries and the ISPF Editor.
Table 8-2 (Page 1 of 2). ISPF Keys and Commands (default values)
Command
ISPF HELP
PF1/PF13
SPLIT SCREEN
PF2/PF14
END PF3/PF15
RETURN
PF4/PF16
REFIND
PF5/PF17
RECHANGE
PF6/PF18
UP PF7/PF19
DOWN PF8/PF20
SWAP PF9/PF21
Mode
Edit & Browse
Edit & Browse
Edit
Browse
Edit & Browse
Edit & Browse
Edit
Edit & Browse
Edit & Browse
Edit & Browse
Description
Displays information about the current screen.
Splits the screen into two ISPF sessions.
Saves changes and returns to the previous screen.
Returns to the previous screen.
Returns directly to the previous Primary Option
Menu.
Repeats the previous FIND command.
Repeats the previous CHANGE command.
Scrolls up by the amount set at the SCROLL or
COMMAND prompt.
Scrolls down by the amount set at the SCROLL or
COMMAND prompt.
Moves the cursor from one screen to the other in the
split-screen mode.
8-4
IDEA User's Guide
February 29, 1996
-------
Table 8-2 (Page 2 of 2). ISPF Keys and Commands (default values)
Command
LEFT PF10/PF22
RIGHT PF11/PF23
RETRIEVE
PF12/PF24
FIND
CHANGE
SAVE
CANCEL
Mode
Edit & Browse
Edit & Browse
Edit & Browse
Edit & Browse
Edit
Edit
Browse
Edit
Description
Scrolls left by the amount set at the SCROLL or
COMMAND prompt.
Scrolls right by the amount set at the SCROLL or
COMMAND prompt.
Moves the cursor to the first input field on the screen
and retrieves the last command entered.
Locates the first line containing a specified character
or string of characters.
Changes the first occurrence of a character^) to
another character^).
Saves your work and remains in the edit session.
Refer to the Saving Reports portion of Chapter 10.
Ends an edit session without saving any changes.
8.2 Using Keywords to Write Queries
The typical Keyword query contains three basic elements, or statements, made up of
required keywords and parameters, as well as optional keyword qualifiers. These
three elements are the INPUT statement, the SELECT statement, and the OUTPUT
statement.
Figure 8-4. Example Keyword Query
Figure 8-4 is an example of a keyword query. Notice that it consists of an OUTPUT
statement (line 1), an INPUT statement (line 2), and a SELECT statement (line 3).
Lines 5 and 7 show the Boolean connector AND, (Note: the OUTPUT statement
can appear before the INPUT statement.) Lines 4, 6, and 7 show data element
names and values.
Chapter 8. Conducting a Search Using Keywords
8-5
-------
Note: There may only be one INPUT statement and one OUTPUT statement.
"SELECT" may only be entered once.
8.2.1 The INPUT Statement
The INPUT statement, which instructs IDEA how to process the search criteria, is a
necessary component of every Keyword query. It will affect how many facilities may
be selected and how the output will be organized. The INPUT qualifiers LINKED,
NONLINKED, and the combination LINKED NONLINKED, determine exactly how
your query is processed. These qualifiers are discussed in Section 8.2.1.1, Using
Linked and Nonlinked Keywords .
At the blank EDIT SCREEN, the cursor will be flashing by the COMMAND prompt
(see Figure 8-3). IDEA may include messages at the top of the screen. To remove
these, type RESET at the COMMAND prompt (optional). To begin building a
query, you will have to move the cursor below these messages and to the right of the
six apostrophes on the left hand side of the screen. After you have formed your
query and pressed < Enter > these apostrophes will turn into line numbers. If you
press < Enter > before completing your query, insert lines by typing i on a line
number; press < Enter >. This will insert a line after that line.
Use < Tab > or the arrow keys to move your cursor down to the first open line on
the EDIT SCREEN. Type the word INPUT. If you do not include an INPUT qual-
ifier, IDEA assumes the default: LINKED. INPUT should typically appear as the
first statement in a Keyword query. Two notable exceptions, however, are GO
Names and GO MenuA generated queries.
8.2.1.1 Using Linked and Nonlinked Keywords
When you include the keywords LINKED and/or NONLINKED in your query, you
are telling IDEA what type of information to retrieve; namely, data that has been
integrated using FINDS, non-integrated data from the separate databases, or both
together. Refer to Section 2.3, How IDEA Processes Queries for complete details.
Linked
LINKED is the default; that is, if you do not specify LINKED and/or NON-
LINKED in your query, IDEA will retrieve data that has been integrated using
FINDS.
8-6 IDEA User's Guide February 29, 1996
-------
Nonlinked
The NONLINKED keyword instructs IDEA to retrieve information from the sepa-
rate systems without using FINDS to integrate the data.
The benefit of choosing NONLINKED is that you will receive all the data you are
seeking. (LINKED data may not be complete since FINDS does not contain data
for all facilities.) The drawback of NONLINKEE* data is that you will have to man-
ually match facilities from separate systems in order to integrate the data.
If you would like to retrieve non-integrated data without using FINDS, type NON-
LINKED after INPUT and use only Boolean ORs as connectors between databases.
If you use a Boolean AND between databases, IE»EA will interpret it as an OR since
integration of data is not possible when you are searching databases separately.
Linked Nonlinked
LINKED and NONLINKED can be combined in. a query to get both integrated and
nonintegrated data. Typing LINKED NONLINKED after INPUT will instruct IDEA
to retrieve data that has been integrated by FINDS and data that has not been inte-
grated by FINDS.
This INPUT criteria will generate two parts to reports 1A, IB, and 2. The first part
will contain those facilities that meet all your selection criteria and are linked using
FINDS. The second part will consist of the facilities that meet at least one of your
criteria within each of the particular databases but have not been linked using
FINDS. Data in the first section will not be repeated in the second,1 but facilities
may.
Note that all the facilities in the second section were selected because they fulfill only
the criteria that pertain to a particular database and could not be linked using
FINDS. For example, if you form such a query looking for facilities that are viola-
tors of both the Clean Air Act and the Clean Water Act, the non-linked part of the
report will contain all air violators and, separately, all water violators. Since FINDS
does not provide the link, you will have to manually correlate the facilities in order to
obtain integrated data.
Chapter 8. Conducting a Search Using Keywords 8-7
-------
8.2.2 The SELECT Statement
The SELECT statement is the core of any Keyword query. This required statement
allows you to specify the database(s) you want IDEA to search and the information
you want IDEA to test for. The SELECT keyword tells IDEA that the facility
selection criteria for the query will follow.
The required keyword SELECT should follow the INPUT statement and directly
precede your Keywords search criteria. Type SELECT after or below the INPUT
statement.
8.2.2.1 Choosing a SELECT Database
As described in Chapter 2, IDEA: What it Does & How it Works , the IDEA system
integrates information from several databases. IDEA distinguishes where a data
element comes from by using a three character prefix to denote the source database.
These databases, along with a short description and their IDEA abbreviations, are
listed in Table 8-3 below.
Table 8-3 (Page 1 of 2). Database Select Codes
IDEA
Abbrev
iation
AFS
CER
DCK
DUN
ERN
FFI
FIN
LST
Database
AIRS Facility Subsystem
CERCLA Information
System
Civil Docket
Dun & Bradstreet Mar-
keting Index
Emergency Response
Notification System
Federal Facilities Index
System
Facilities Index System
Contractor Listing
Docket
Description
Information regarding airborne pollution in the U.S.
The AFS contains emission and compliance data on
individual facilities.
Information regarding the official inventory of CERCLA
sites, including enforcement, financial and site/incident
data.
Tracking system of enforcement case activity, including
court- related information, violation, and penalty data.
Information regarding corporations and their locations,
parent- subsidiary relationships, industrial classification,
and sales figures.
Information on release notifications of oil and hazardous
substances occurring in the United States and reported to
the NRC, one of the ten EPA regions, or the Coast
Guard.
Information about environmental regulatory projects that
target federal facilities, including compliance status and
budget data.
A computerized inventory of facilities under EPA regu-
lation. Provides facility EPA ID numbers as well as
pointers to other databases.
Information on contractors that have been listed as ineli-
gible for EPA contracts under CAA and CWA.
8-8
IDEA User's Guide
February 29, 1996
-------
Table 8-3 (Page 2 of 2). Database Select Codes
IDEA
Abbrev
iation
NCB
OSHA
PCS
RCR
SET
TRI
Database
National Compliance
Data Base (for FIFRA,
TSCA, EPCRA 313)
Occupational Safely and
Health Administration
Permit Compliance
System
RCRA Information
System
Site Enforcement
Tracking System
Toxic Chemical Release
Inventory
Description
Compliance data under FIFRA, TSCA, and EPCRA
313 including inspections, case reviews, and enforcement
actions.
Contains OSHA inspections data, including types of vio-
lations, substances involved, actions required, accidents,
and penalties.
Contains permit compliance and enforcement informa-
tion under NPDES of CWA, including inspection data,
facility data, monitoring information and description of
outfalls (pipes).
Contains tracking of RCRA handlers and information
on compliance monitoring and enforcement, corrective
action, handler IDs, permitting, and facility management
planning.
Contains tracking of the names and addresses of PRPs
who have been issued CERCLA 104 "general" notice
letters, or CERCLA 122 "special" notice letters, date of
letters, and Notice Letter Addressee name and address.
Information on manufacturing facilities that release man-
ufactured toxic pollutants; data concerns pollution pre-
vention, chemical uses, on-site chemicals, and waste
treatment.
After the word SELECT, enter the three letter abbreviation for the database(s) that
you want IDEA to search. For instance, if you would like to query information from
the Toxic Chemical Release Inventory, you would type TRI after the INPUT and
SELECT statements, like this:
INPUT LINKED
SELECT
TRI
Directly after the database identifier is entered, type a period (.) followed by the data
element name.
8.2.2.2 Choosing a SELECT Data Element
Data element names are multi-character codes that tell IDEA where to look for the
information you wish to query for. Each database has a large number of data ele-
ments that are available for selection. For instance, in the TRI database you may
select TRI.TCID to search according to chemical ID numbers or TRI.RPYR to indi-
cate the chemical reporting year. In RCRIS you may select, for example,
RCR.HUSML to search for small quantity generators or RCR.WAMTT to indicate
Chapter 8. Conducting a Search Using Keywords
8-9
-------
waste amounts in tons. These specific elements are listed in the Data Element
column in Appendix C: Data Elements in IDEA Shadow Files.
— Caution
Only data elements which have been indexed may be used in IDEA queries (refer
to the Index column in Appendix C, Data Elements in IDEA Shadow Files ).
Having selected specific data elements, you can define your search by identifying the
particular codes, dates, amounts, etc. on which you wish to query. These data values
will be explained in Section 8.2.2.4, Providing SELECT Data Values. Before these can
be entered however, you must first include a Boolean operator (see Section 8.2.2.3,
Using a Boolean Operator).
8.2.2.3 Using a Boolean Operator
At this point you have already told IDEA which database to search and which data
element to focus on. To complete your SELECT statement, and be more specific at
the same time, you will have to include a data value or values. The Boolean operator
employs Boolean logic to tell IDEA exactly how you want it to search for the data
value you have specified.
Leave a < Space > after database.element and type in the appropriate Boolean oper-
ator.
IDEA currently uses seven Boolean operators. These operators and examples of their
use are presented below. The first two operators, EQ and NE, are concerned with
definite values. The other five deal with whether a data element is less than, less than
or equal to, greater than, or greater than or equal to a given data value, or in
between two data values.
EQ(=)
The EQual operator tells IDEA to select all facilities that have a data value equal to
the one you have specified. In other words, EQ is only used with definite values. For
example, if you typed in the following SELECT statement:
SELECT
TRI.TCID EQ 000108883
8-10 IDEA User's Guide February 29, 1996
-------
IDEA would select all TRI releasers of the chemical with this ID number, which is
toluene. IDEA also allows you to search for more than one data value at a time
within the same data element. To do so, you must separate the values by a comma.
IDEA performs the search by placing a Boolean OR between the values you list. In
other words, IDEA will retrieve the names of all facilities that fulfill the first data
value OR the second OR the third. For example, if you wanted to search for all
facilities that release toluene (TRI code 000108883) or xylene (TRI code 001330207)
or trichloroethylene (TRI code 000079016) then you would enter the following
SELECT statement (Note: the " = " sign may be used interchangeably with EQ):
SELECT
TRI.TCID = 080108883, 001330207,, 000079016
In this case, IDEA will search for all TRI releasers of toluene OR xylene OR
trichloroethylene.
NE
The present and Not Equal operator tells IDEA to select all facilities that have a data
value that is present and not equal to the value you have specified. In RCRIS, for
instance, you can choose to search for facilities in the State of Pennsylvania by using
the data element LSTATE set equal (EQ) to PA. On the other hand, if you were
interested in searching for RCRIS facilities that were not in Pennsylvania, then you
could type the following SELECT statement:
SELECT
RCR.LSTATE NE PA
IN
The INclude operator tells IDEA to select all facilities that have a data value that is
included in a range of values that you specify. The IN operator allows you to
perform an indefinite search. For example, if you typed in the following SELECT
statement:
SELECT
RCR.WAMTT IN 100, 1000
IDEA would select all RCRA facilities that produce amounts of waste that fall
between 100 and 1000 tons. You are required to separate the values by a comma,
putting the lower value first and the higher value second (IDEA will not automat-
ically check for proper arrangement).
Chapters. Conducting a Search Using Keywords 8-11
-------
LT
The present and Less Than operator tells IDEA to select all facilities that have a data
value that is present and less than the value you have specified. For example, to
search for any RCRA facility that produced less than 1000 tons of waste, you could
write the following SELECT statement:
SELECT
RCR.WAMTT LT 1000
LE
The present and Less than or Equal to operator tells IDEA to select all facilities that
have a data value that is present and less than or equal to the value you have speci-
fied. So, if you wanted to search for all RCRA facilities that produce 1000 tons of
waste or less, you would write the following SELECT statement:
SELECT
RCR.WAMTT LE 1000
GT
The present and Greater Than operator tells IDEA to select all facilities that have a
data value that is present and greater than the value you have specified. So to search
for all RCRA facilities that produce over 1000 tons of waste, you would write the
following SELECT statement:
SELECT
RCR.WAMTT GT 1000
GE
The present and Greater than or Equal to operator tells IDEA to select all facilities
that have a data value that is present and greater than or equal to the value you have
specified. Thus, if you wanted to search for the names of all RCRA facilities that
produce 1000 or more tons of waste, you would enter the following SELECT state-
ment:
SELECT
RCR.WAMTT GE 1000
8-12
IDEA User's Guide
February 29, 1996
-------
The operators LT, LE, GT, GE, and NE tell IDEA to evaluate only data that is
present. In other words, when these operators are used, IDEA will ignore any data
field that is left blank, even if the absence of data has an implied meaning. For
instance, the major discharge indicator (MADI) Held in the PCS database is blank
unless the facility is a major discharger, in which case an M is stored. A blank in
PCS for MADI implies that the discharger is a minor, but no blanks are stored in the
PCS shadow file, or any IDEA shadow files.
IDEA retrieves all its data from these shadow files, which are copies of the original
databases. The shadow files preserve the data intact; however, in order to conserve
computer storage space, blanks or missing values; have been excluded.
How, then, can you select a minor facility in PCS when the keyword statement
PCS.MADI = blank is not valid? In this case you could use the operator NOT to
select all facilities that are not equal to M:
SELECT
NOT PCS.MADI = M
Since a minor facility is any one that is not M, the NOT operator gets the job done.
IDEA is not counting the blanks in this case. Instead, it is eliminating the facilities
that have PCS.MADI = M and counting the ones that are left (i.e., the ones that are
not M).
The operators LT, LE, GT, and GE are also dependent on the presence of data; that
is, they also ignore blank data fields. NOT can be used to accurately count facilities
that are not equal to a value, as in the PCS example above, but the same cannot be
done when the operator calls for less than or greater than. Nor would NOT be accu-
rate if the blanks were the result of missing information. Keep in mind that when a
data field has a blank or missing value, nothing can be assumed about what the real
value may be and, consequently, it is neither greater or less than any value you select.
8.2.2.4 Providing SELECT Data Values
The data value is a more specific classification within each data element. Each data-
base has its own list of data elements and corresponding values that you can refer-
ence before forming your query. Appendix C: Data Elements in IDEA Shadow Files
lists SELECT value types, but does not currently list the actual values that could be
used in a query. For this information, refer to Appendix B: Database Descriptions,
which lists User Support numbers for each database used by IDEA, or refer to the
database's data element dictionary.
Chapter 8. Conducting a Search Using Keywords 8-13
-------
Some examples of data values were presented in the SELECT statements above.
Other examples are ZIP codes, two-letter state abbreviations, chemical codes, signif-
icant violator status, Standard Industrial Classification codes (SICs), dates of enforce-
ment actions, amounts of waste releases, etc.
When you have finished composing your SELECT statement, it should have the same
format as the following expression:
SELECT
database.element Boolean-operator data-value
This is the basic format for any SELECT statement.
8.3 Using Boolean Connectors in a Query
The true power of IDEA comes into focus when you begin to form queries that
request information from more than one data element or database at a time. To form
these more intricate queries you will have to learn to use Boolean ORs, ANDs and
other connectors, as well as parentheses.
OR The Boolean OR tells IDEA to retrieve a facility record if it fulfills one criterion
OR a second criterion, OR a third, etc. Use the OR as a connector between
database.element expressions. IDEA interprets commas between data values as ORs,
so spelling out OR is not necessary when you are setting value criteria in the same
data element.
To demonstrate, let's say you are searching for all RCRA facilities that are either in
the transporter universe or the land disposal universe. The data elements for these
criteria are HUTRAN and HULAND, respectively, and these criteria are selected by
typing X after the = sign. So, remembering to insert the Boolean OR, the SELECT
criteria would look like this:
SELECT
RCR.HUTRAN = X
RCR.HULAND = X
OR
The same can be done between databases; for instance, if you wanted to search for
facilities that are either fully regulated RCRA generators (HUFUL) or are NPDES
"major" dischargers the SELECT statement would be as follows:
8-14
IDEA User's Guide
February 29, 1996
-------
SELECT
RCR.HUFUL = X OR
PCS.MADI = M
AND The Boolean AND is a handy tool to use when you are performing very spe-
cific, targeted searches. AND tells IDEA to retrieve facility names only when they
fulfill all the specified criteria; i.e., the first criterion AND the second AND the third,
etc. AND is used as simply as OR, by inserting it between search criteria. AND may
be used between databases; for instance, if we change the search above to all facilities
that are fully regulated RCRA generators AND NPDES "major" dischargers:
SELECT
RCR.HUFUL = X AND
PCS.MADI = M
Additionally, the AND may be used between data elements within the same database,
when commas (ORs) are not appropriate. Let's say for instance that you are looking
for all TRIS facilities that produce both toluene AND trichloroethylene:
SELECT
TRI.TCID = 0001G8883 AND
TRI.TCID = 000079016
Use the Boolean connector AND between "database.element Boolean-operator data-
value" statements in order to select facilities according to one criterion AND a second
criterion AND a third, etc.
8.4 Usins Parentheses in a Query
IDEA prioritizes the logical operators present in a query. This mechanism causes
IDEA to process some parts of a query before others. IDEA will consider informa-
tion between parentheses first, then it will consider ANDed criteria, then it will con-
sider ORed criteria.
You can use parentheses to instruct IDEA to consider any criteria inside the paren-
theses before the rest of the query.
helpful hint
Use parentheses around an expression in the SELECT statement if you want
IDEA to consider the expression first.
Chapter 8. Conducting a Search Using Keywords 8-15
-------
You can see how in the following example: let's say you are searching for all RCRA
facilities in the State of Pennsylvania, RCR.LSTATE = PA, that are fully regulated
generators OR release toluene:
SELECT
RCR.LSTATE = PA AND
(RCR.HUFUL = X OR TRI.TCID = 000108883)
To see the difference that parentheses can make, switch the parentheses to cover the
first two segments of this statement:
SELECT
(RCR.LSTATE = PA AND RCR.HUFUL = X)
OR TRI.TCID = 000108883
This search would give you a much different list of facilities since IDEA would call up
all facilities that are either fully regulated RCRA generators in Pennsylvania OR
release toluene.
While the SELECT keyword provides the core of a query, several necessary compo-
nents of the Keyword query are still missing. The following sections will introduce
you to these keywords.
8.5 Using the TEXT command to help you build your query
One of the primary obstacles to writing your own IDEA queries in the Keyword
Interface is not knowing what codes the data elements you are interested in can take.
More significantly, you may have trouble selecting an indexed data element to use in
your search because the description provided in Appendix C, Data Elements in IDEA
Shadow Files does not tell you enough abo ut the data element. One solution to this
is to use the TEXT command to see what values data elements can take.
Suppose you don't have all the codes for the TRIS Chemical Identifier memorized,
and need to look up the code for toluene. Type TEXT INFO at the Command
prompt La any IDEA screen. This will bring up a list, 'in browse mode, of IDEA data
elements that have translation tables of their codes available on-line. (See
Figure 8-5.)
8-16 IDEA User's Guide February 29, 1996
-------
Figure 8-5. Top of Decoding Tables List
Type MAX at the Command prompt and press PF8, to get to the bottom of this list.
(See Figure 8-6.)
'1S»_D*I,' &','& i-ii!SS',,'iP.f'fA.Sjii'QSS?*!
Figure 8-6. Bottom of Decoding Tables List
Chapter 8. Conducting a Search Using Keywords
8-17
-------
list, and type TEXT TRI.TCID at the Command prompt. A list of all valid codes for
TRI.TCID and their values appears in browse mode. (See Figure 8-7.)
_t •"••"- r-7r;-7i^,'g?'™?yfivryc^v, " ef
- «- "*_" 11 (" (^"t S? '*(*< ,f tffi, c' 'iH^t C't!( **( J!-< rt{ c£5ttct- ? C
< El ettfeftt •' .:• '•. ~ r.'. .^HftEftHseist 's=??i> -ife i
Figure 8-7. Top of TRI.TCID Decoding Table
Type FIND TOLUENE at the Command prompt. Press PF5 (the "repeat find" key)
until you get to just plain "toluene." Note that the code for "toluene" is,indeed
000108883. (See Figure 8-8.) Press PF3 to exit this list.
8-18
IDEA User's Guide
February 29, 1996
-------
i',',! vw?i"*"ss^a/$sr -rf>s sift
.4 feV'^v : pf Ms < -'0«,
; M^1 ."s 'lisV HiS ''llll 'f If' •'!
tjtet,, tx. .~?t ,( {fij, , ,{| Me, " {,{,3E,{,
J !* ?&J ; 'tjtj jCjC; *t { rf{J J * *({({(*tj C (jrf^ * CC
Figure 8-8. Code for TRI.TCID for Toluene
Output Report Selection
The keyword OUTPUT is another necessary component in your query. The
OUTPUT statement must immediately precede this keywords that provide directions
about the query report format (REPORT) and its destination (PRINT or
DATASET). It can appear before the INPUT statement or after the SELECT state-
ment. Table 8-4 offers a brief description of the standard report formats currently
available in IDEA. Refer to Chapter 10, IDEA Standard Reports for more detail.
You also have the option of specifying the information you wish to be included in
your report; that is, you can design a User-specified Report (USR). See Chapter 11,
IDEA User-Specified Reports for the USR keywords you will need, and see
Appendix C, Data Elements in IDEA Shadow Files for the list of data elements whose
values are available to a USR.
Once you have chosen a report format, type REPORT followed by a < Space > and
the desired format (1A, IB, 2, SUMMARY, or USR report-name). Multiple reports
can be generated by repeating the REPORT keyword followed by another format.
For example, to get reports IB, 2, and Summary, the OUTPUT line should look like
this:
OUTPUT REPORT IB REPORT 2 REPORT SUMMARY
Chapter 8. Conducting a Search Using Keywords
8-19
-------
Each report may be directed to a different destination: your terminal, a printer, or
saved in a dataset. Section 8.7, Specifying Report Destinations will tell you how to
print to each of these destinations.
Table 8-4. IDEA Standard Reports
There are currently four standard IDEA report formats: 1A, IB, 2, and Summary.
REPORT 1A
A brief report of individual facilities. Organized by the linked database, IDEA displays the
facility name and database identifier, location and other business information, noncompliance
or violation status, and enforcement information.
REPORT IB
A more detailed presentation of information on individual facilities, including historical and
programmatic data such as dates and results of inspections, specific toxic substances reported,
and details of enforcement actions.
REPORT 2
A linked docket table that indicates whether each facility is listed as a significant noncomplier
or high priority violator.
REPORT SUMMARY
Provides total facility counts by program and EPA region; sum of facilities that are in compli-
ance and not in compliance by program and total numbers of enforcement actions by
program; and total toxic substance release information for the selected facilities.
8.7 Specifying Report Destinations
The default output destination for your query report(s) is your computer terminal. If
you want to see your report before printing or saving, you do not have to specify a
destination after the OUTPUT statement. You will then have the option of saving or
printing when you view the report(s) (see Section 8.10.1, Viewing the Query Report).
Simply type SAVE or PRINTO at the COMMAND prompt, press < Enter >, then
answer the prompts on the PRINT/SAVE PARAMETER SCREEN that appears.
This method of printing and saving reports is explained more fully in Chapter 10,
IDEA Standard Reports (see Sections 10.3, Printing Reports and 10.4, Saving
Reports).
If you do not wish to view the output at your terminal, but prefer to print it imme-
diately or save it directly to a dataset, you must use the keyword(s) PRINT and/or
DATASET in the output statement of your Keyword query. These two keywords are
discussed in the following paragraphs.
Note that you may only specify one output destination - your terminal (default), a
printer, or a dataset - per REPORT statement. For example:
OUTPUT REPORT 1A REPORT 1A PRINT
8-20
IDEA User's Guide
February 29, 1996
-------
This OUTPUT statement will send one copy of Report 1A to your terminal screen
and one copy to be printed.
PRINT
To print a report, type the keyword PRINT on the OUTPUT line after the report
specification. If you would like to print multiple copies of the report, then type
PRINT COPIES X and substitute the number of copies you want for X.
After you run the query as described in Section 8.10, Running a Keyword Query and
return to the EDIT SCREEN, a message will appear at the top of the query saying
"Your batch job is JOBxxxxx" where xxxxx will be a 5-digit number. IDEA will have
sent the requested report(s) to a HOLD queue to await further instructions. You
must then let the system know to which printer you want the output to be routed by
using the System Display and Search Facility (SDSF). Take the following steps to
release your print job from the HOLD queue:
1. To access SDSF, type SDSF at the COMMAND line of any Keyword screen.
This will bring up the SDSF PRIMARY OPTION MENU SCREEN pictured in
Figure 8-9 .
Figure 8-9. SDSF Primary Option Menu Screem
Chapter 8. Conducting a Search Using Keywords
8-21
-------
2. Type O at the COMMAND prompt and press < Enter > to "display jobs in the
JES2 output queue." Look for your user ID and batch job number (JOBxxxxx)
under the JOBNAME.and Jobid headings, as in Figure 8-10 .
Figure 8-10. SDSF Output Queue Screen
3. Press < Tab > to move the cursor down to your print job, then over to the DEST
column. The text should read R255, which simply means that your print job is in
the HOLD queue. Type the identification number of the printer at your site or ^.
one of the options listed below over R255, and press < Enter > two times. ••
Destination options:
WIC Prints at the Washington Information Center (WIC) at EPA Headquar-
ters, Washington, DC.
LOCAL Prints at the National Computer Center (NCC), Research Triangle
Park, NC.
RMTO Same as LOCAL.
R + RP# Prints at the designated remote printer. Here RP# is the ID for the
remote printer. To view a list of the remote printers available to IDEA
users:
8-22 IDEA User's Guide
a. Exit IDEA and type ISPF 3.4 at the TSO READY prompt. The
DATA SET LIST UTILITY SCREEN will appear.
b. Type JUSD.REMOTE.DATA at the DSNAME LEVEL prompt;
press < Enter > . The DS LIST SCREEN will appear.
February 29, 1996
-------
c. < Tab > down and type B (Browse) next to the
JUSD.REMOTE.DATA member. Press < Enter > to view the list
of remote printers.
d. When you are finished, use the RETURN command (PF4) to go to
the ISPFJPDF PRIMARY OPTION MENU. Type X to return to
the READY prompt.
— helpful hint —^——---—"~———————————^———
The first time you press < Enter > in step 3 a message reading COMMAND
ISSUED will appear in the upper right hand corner of the screen, and the
printer destination you just typed in will change back to R255. Don't panic!
When you press < Enter > the second time, the correct destination will again
be displayed. (Compare Figure 8-11 with Figure 8-12 .)
Figure 8-11. SDSF Output Queue Screen - "Command Issued"
Figure 8-12. SDSF Output Queue Screen - Print Destination Changed
Chapter 8. Conducting
-------
If you decide not to print your job, type a P (Purge) under the NP column on the
line of the job you want to cancel; press < Enter >. Warning: a purged record
can not be recovered.
4. To exit SDSF, use the END command or PF3 two times. You will return to the
Keyword screen from which you issued the SDSF command in step 1.
DATASET
To save a report directly to a dataset, the output line must specify the report type,
the library, and the name of the member in which the report is to be saved. On the
OUTPUT line, type REPORT, specify a format, then type the keyword DATASET
followed by the dataset name. Since IDEA will automatically prefix your dataset
name with your user ID and account number (UIDACCT), you must either:
• not specify your user ID and account number on the OUTPUT line; that is, type:
QUERY.REPORTS(MEMBERNAME)
• or, enter your user ID, account number, and membername with single quotes
around the entire character string; that is, type:
'UIDACCT.QUERY.REPORTS(MEMBERNAME)'
The dataset you specify may be NEW or OLD. By default, IDEA assumes that it is
NEW (i.e., that it does not yet exist and must be created). If you wish to overwrite
an existing dataset, you must type OLD after the dataset name. For instance, let's
say you want to save Report IB to an existing library called QUERY.REPORTS and
you have decided to name the member SEARCH 1. Your OUTPUT line would
resemble the following:
OUTPUT REPORT IB DATASET QUERY.REPORTS(SEARCH1) OLD
If the data set you wish to overwrite does not actually exist, IDEA will give you an
error message and you will have to delete the OLD status to save the report.
8-24
IDEA User's Guide
February 29, 1996
-------
8.8 Adding Comments to a Query
To identify your query in a way that is understandable and. easy to read, you can add
comments that will not be a part of the query for processing purposes, but will
remind you of the query's contents. To do this, simply type the two characters /*.
The sequence /* makes IDEA ignore anything to the right of the two characters on
the same line. Comments can appear anywhere in the query: on separate comment
lines or on the same line with executable IDEA expressions. You may also find this
sequence useful when you are trying to refine queries. Instead of deleting an
expression from the query, you can just type /* in front of the line and then check
your output. This will, in effect, turn the line off. You can always restore the
expression by deleting the /* sequence from the line.
8.9 JOB. ROUTE & DP Statements
IDEA creates JOB , ROUTE , and DD statements for the batch jobs that result from
your PRINT or DATASET statements. These statements are written in Job Control
Language (JCL); unless you are familiar with writing JCL, you should accept the IDEA
defaults (that is, you should not use the optional keywords JOB and DD). If you are
familiar with JCL, the following section shows you the IDEA defaults so that you
can decide whether you want to write your own JOB, ROUTE, and DD statements.
For the batch part of a query, there are only one JOB statement and one ROUTE
statement; however, there are DD statements for each report in the batch part of the
query.
The IDEA system will supply the following defaults for JOB and ROUTE statements:
BIN/BOX=(your TSO logon default)
PRIORITY =2
REGION =2M
TIME =2 minutes
MSGLEVEL = (1,1)
Chapters. Conducting a Search Using Keywords 8-25
-------
ROUTE PRINT HOLD
LINES =100000
If you want to specify your own JOB and ROUTE statements, use the keyword JOB
in the OUTPUT section of the query request; JOB is at a keyword level equal to
REPORT and so will apply to all batch reports in the query. If the word JOB
appears, IDEA will expect to find JOB and ROUTE statements at the end of the
query. These statements are not free-form as most query statements are, but are JCL
statements that will be copied from the query into the batch job; they must appear
just as they would at the start of a batch job to be submitted by the user. Following
is an example:
OUTPUT JOB REPORT IB PRINT REPORT 2
INPUT LINKED SELECT (criteria)
//uuuxx JOB (aaaafffff,bbbb)l%%IDEA',REGION=2M,PRTY=2,TIME=2,
// MSGLEVEL=(0,0)
/*ROUTE PRINT HOLD
/*JOBPARM LINES=10G
where uuu is the User Id, xx is an optional letter or number suffix to help identify the
job in the output queue, aaaa is the account number, ffiffis the fimas, and bbbb is
the bin number.
If the JOB and ROUTE statements are incorrect or incomplete, you will get an error
message and the query will not be processed.
Similarly, IDEA will generate DD statements for your PRINT and DATASET batch
jobs. IDEA'S PRINT DD statement is the following:
SYSOUT=A,RECFM=VBA,LRECL=259,BLKSIZE=23000
IDEA'S provides four DATASET DD statements.
For a new partitioned dataset (PDS):
//RaaaOUT DD DSN=bbb.bbb(bbb),
DISP=(,CATLG,DCB=(RECFM=VB,LRECL=259,BLKSIZE=23310),
// SPACE=(TRK,(50,50,10))
_
statement; bbb.bbb(bbb) is the dataset name the user entered.
8-26 IDEA User's Guide February 29, 1996
-------
For a new non-PDS:
//RaaaOUT DD DSN=bbb.bbb,
DISP=(,CATLG,DCB=(RECFM=VB,LRECL=259,BLKSIZE==23310),
// SPACE=(TRK,(50,50))
For an existing PDS:
//RaaaOUT DD DSN=bbb.bbb(bbb), DISP=ccc
where aaa is a sequential number beginning at 001 and incremented for each DD
statement; bbb.bbb(bbb) is the dataset name the user entered; ccc is the disposition
(OLD) the user entered.
For an existing non-PDS:
//RaaaOUT DD DSN=bbb.bbb, DISP=ccc
If you want to specify your own DD statement for a batch report, use the keyword
DD = ddname after either PRINT or DATASBT. A DD statement with the specified
DD name must appear at the end of the query, after JOB and ROUTE statements, if
they are present. (They will be present only if JOB has also been specified.) Fol-
lowing is an example:
OUTPUT REPORT IB DD=REPT01 REPORT 2
INPUT LINKED SELECT (criteria)
//REPT01 DD UNIT=DISK,DSN=uuuaaaa.dataset(myreport),DISP=(,CATLG),
// SPACE=(TRK, (10^0,3),RECFM=VBA,LRECL=259,B:LKSIZE=23476 '
8.10 Runnins a Keyword Query
Once you are satisfied with the content of a Keyword query, you are ready to run the
query and receive the specified report(s).
|— helpful hint
To run a Keyword query, at the EDIT SCREEN , use < Tab > or < Home > to
move the cursor to the COMMAND prompt; type GO followed by < Enter >.
Chapter 8. Conducting Ji Search Using Keywords 8-27
-------
From here, IDEA processes the query and then presents the QUERY STATUS
SCREEN, shown below in Figure 8-13 .
Figure 8-13. Query Status Screen
If you are satisfied with the number of facilities that your query has turned up then
press < Enter > to see the query report. If you are not satisfied and wish to return to
the EDIT SCREEN, then type END at the COMMAND prompt (or use PF3).
8.10.1 Viewing the Query Report
If you choose to see the report, IDEA will deliver information to your screen
according to the format you selected earlier. The reports are presented to you in the
BROWSE mode (see Figure 8-14) where you can view, print, or save, but not alter
the reports. To maneuver through the report, use PF7 to page up, PF8 to page
down, PF10 to scroll left, and PF11 to scroll right. If you selected multiple report
formats, type SW at the COMMAND prompt to switch to the next report. See
Chapter 10, IDEA Standard Reports for more details.
8-28
IDEA User's Guide
February 29, 1996
-------
.rffiK
A!.t' ?fe - - ' * s t V f &wA 4J«SS' ' *«s-6 JScUcSMLJ' < illc
PC ^t i ™e it t5 "T7™r;< «t ti^ 7? -^-»-«^-i*.*- j- ({({! -5{st «t; ?^2ec i J'i'i S5t i" ^iSftS !c' "t
-------
8.12 Summary
The Keyword Interface is a powerful query building tool operated through the ISPF
Editor. Search criteria and parameters must be expressed in the IDEA Keyword
Query Language (IKQL) in order to be understood by IDEA. (See Figure 8-15 for
an example of a keyword query.) This chapter and Appendix C: Data Elements in
IDEA Shadow Files contain information on proper keyword syntax and data elements
used by IDEA.
• . ,A.1;y *&t m t 4Mvi • A yftk^Bai:
Figure 8-15. Example Keyword Query.
Each Keyword query must have three statements: INPUT, SELECT, and OUTPUT.
Follow these steps to build a Keyword query:
1. Use < Tab > or the arrow keys to move your cursor down to first open line on a
blank EDIT SCREEN. Type the word INPUT and provide the appropriate
keyword: LINKED (default), NONLINKED, LINKED NONLINKED.
2. Type SELECT below or after the INPUT statement. Provide the following infor-
mation: three letter database ID, database element, Boolean operator, data
value(s).
The SELECT statement should have the following format:
database, element Bo clean-operator data-value
8-30
IDEA User's Guide
February 29, 1996
-------
3. Provide an OUTPUT statement after the SELECT statement by typing OUTPUT
followed by REPORT arid a report'name: 1A, IB, 2, SUMMARY, or USR
report-name.
Note: There may only be one INPUT statement and one OUTPUT statement.
"SELECT" may be entered only once.
Chapter 8. Conducting a Search Using Keywords
8-31
-------
8-32 IDEA User's Guide February 29, 1996
-------
Chapter 9. Managing Keyword Queries and the ISPF Editor
This chapter provides instruction on ISPF (Interactive System Productivity Facility)
Edit Commands.
9.1 Introduction to the ISPF Editor
When using the EDIT SCREEN (see Figure 9-1) in the Keyword Interface, you are
in the ISPF editor mode. ISPF is a mainframe word processor that is used to con-
struct and execute IDEA queries. ISPF edit commands are divided into two groups:
line commands and primary commands. Line commands, which are entered by typing
over the line numbers on the left side of the screen, enable you to insert, delete, copy,
and move lines. Primary commands are entered at the COMMAND prompt at the
top of the ISPF edit screen and they allow you to exercise some control over the
EDIT environment.
Figure 9-1. Edit Screen
Chapter 9. Managing Keyword Queries and the ISPF Editor
9-1
-------
9.2 Keyword Queries and the ISPF Line Editor
Table 9-1 lists the most common ISPF Line Edit Commands. Each command will be
discussed in the sections below. Line commands are used to edit data and are entered
by typing over the 6-digit number on one or more lines. Single character commands
operate on a line (e.g., C to copy a line, I to insert a line) and double character com-
mands work on a block of lines (e.g., DD on the first line to be deleted, DD on the
last line to be deleted).
Table
I
D
C
M
R
A
B
X
9-1. Line Edit Commands
Insert a line
Delete this line
Copy this line
Move this line
Repeat this line
Place after this line
Place before this line
Exclude a line
9.2.1 Inserting and Deleting Lines
Commands for Inserting Lines
I Insert a single line following this line.
IK Insert n lines (where n is an integer between 1 and 99999) following this line.
1. Use the arrow keys or < Tab > to place the cursor at the left most character of
the line number.
2. Type I and press < Enter > and ISPF will add a line following the line where the
cursor is. IDEA will continue to add lines as long as you continue to use them.
To get out of Insert mode, press < Enter > two times in a row.
3. To add more than one line, just type I followed by the number of lines you want
to add (e.g., type 18 to add eight lines below the line the cursor is on) and press
< Enter > . The new lines will be without numbers; ISPF will fill in the numbers
when you press < Enter >.
Commands for Deleting Lines
9-2
IDEA User's Guide
February 29, 1996
-------
D Delete this line.
D« Delete n lines (where n is an integer between 1 and 99999)
DD Identifies the first and last lines of a block to be deleted.
1. Use the arrow keys or < Tab > to place the cursor under the left most character
of the line number you want to delete.
2. Type D and press < Enter > and ISPF will remove that line.
3. To delete more than one line, type D followed by the number of lines you want to
remove (e.g., type D8 to delete eight lines including the line the cursor is on) and
press < Enter > . The lines that were below the deleted lines will be moved up and
renumbered by ISPF to fill the empty space.
4. To delete a block of lines, type DD on the first line to be deleted. Press < Tab >
or the arrow keys to move to the^last line to be deleted, type DD and press
< Enter >. The lines that were below the deleted lines will be moved up and
renumbered by ISPF to fill the empty space.
9.2.2 Copying, Moving, and Repeating Lines
Destination of Moved or Copied Lines
A Place After this line
An Repeat the copy or move n times (where n is an integer between 1 and 99999)
After this line.
B Place Before this line
B« Repeat the copy or move n times (where n is an integer between 1 and 99999)
Before this line.
Copying Lines
C Copy this line.
C« Copy n lines (where n is an integer between 1 and 99999).
CC Identifies the first and last lines of a block to be copied.
Chapter 9. Managing Keyword Queries and the ISPF Editor 9-3
-------
To Copy a line or lines of your query, you must tell ISPF which line(s) you want to
copy and where you want the line(s) to go. Copy allows the text to exist in both its
original and new location.
1. Use the arrow keys or < Tab > to place the cursor under the left most character
of the line number you want to copy.
2. Type C and press < Enter > . The line will be held in memory and a message will
be displayed in the top right corner of the screen announcing MOVE/COPY IS
PENDING. Use the arrow keys or < Tab > to position the cursor at the destina-
tion. Type A for After or B for Before and press < Enter > to complete the copy.
3. To copy more than one line, type C followed by the number of lines you want to
copy (e.g., type C8 to copy eight lines including the line the cursor is on) and
press < Enter >. The lines will be held in memory and a message will be dis-
played in the top right corner of the screen announcing MOVE/COPY IS
PENDING. Use the arrow keys or < Tab > to position the cursor at the destina-
tion location. Type A for After or B for Before and press < Enter > to complete
the copy.
Alternatively, to copy a block of lines, type CC on the first line of the block to be
copied. Press < Tab > or the arrow keys to move to the last line of the block to
be copied. Type CC and press < Enter >. The lines will be held in memory and a
message will be displayed in the top right corner of the screen announcing
MOVE/COPY IS PENDING. Use the arrow keys or < Tab > to position the
cursor at the destination location. Type A for After or B for Before and press
< Enter > to complete the copy.
Moving Lines
M Move this line.
M« Move n lines (where n is an integer between 1 and 99999).
MM Identifies the first and last lines of a block to be moved.
To Move a line or lines of your query, you must tell ISPF which line(s) you want to
move and where you want the line(s) to go.
1. Use the arrow keys or < Tab > to place the cursor under the left most character
of the line number you want to move.
2. Type M and press < Enter >. The line will be held in memory and a message will
be displayed in the top right corner of the screen announcing MOVE/COPY IS
PENDING. Use the arrow keys or < Tab > to position the cursor at the destina-
9-4 IDEA User's Guide February 29, 1996
-------
tion. Type A for After or B for Before and press < Enter > to complete the
move.
i
3. To move more than one line, type M followed, by the number of lines you want to
move (e.g., type M8 to move eight lines including the line the cursor is on) and
press < Enter >. The lines will be held in memory and a message will be dis-
played in the top right corner of the screen announcing MOVE/COPY IS
PENDING. Use the arrow keys or < Tab > to position the cursor at the destina-
tion location. Type A for After or B for Before and press < Enter > to complete
the move.
•f '
Alternatively, to move a block of lines, type MM on the first line of the block to
be moved. Press < Tab > or the arrow keys to move to the last line of the block
to be moved. Type MM and press < Enter > . The lines will be held in memory
and a message will be displayed in the top right corner of the screen announcing
MOVE/COPY IS PENDING. Use the arrow keys or < Tab > to position the
cursor at the destination location. Type A for After or B for Before and press
< Enter > to complete the move.
Repeating Lines
R Repeat this line.
RK Repeat this line n times (where n is an integer between 1 and 99999).
RR Repeat a block of lines.
RR« Repeat a block of lines n times (where n is an integer between 1 and 99999).
To Repeat a line or lines of your query, you must tell ISPF which line(s) you want to
repeat. Repeat is used to duplicate a line or group of lines.
1. Use the arrow keys or < Tab > to place the cursor under the left most character
of the line number you want to repeat.
2. Type R and press < Enter >. The line will be duplicated in the next line.
3. To repeat one line multiple times, type R followed by the number of times you
want to duplicate the line, (e.g., type R8 to repeat one line, eight times) and press
< Enter >.
4. To repeat a block of lines, type RR on the first line of the block to be repeated.
Press < Tab > or the arrow keys to move to the last line of the block to be
repeated. Type RR and press < Enter > . The lines will be duplicated.
Chapter 9. Managing Keyword Queries and the ISPF Editor 9-5
-------
9.2.3 Excluding Lines
A feature of the ISPF Editor is the ability to exclude lines from display. The lines are
not deleted. They remain in virtual storage, but are not displayed on the screen.
Excluding Lines
X Exclude this line
Xn Exclude n lines (where n is an integer between 1 and 99999) starting with this
line.
XX Identifies the first and last line of a block to be excluded.
Redisplaying Excluded Lines
F Display the first line of the excluded block.
F« Display the first n lines (where n is an integer between 1 and 99999) of excluded
data.
L Display the last line of the excluded block.
Ln Display the last n lines (where « is an integer between 1 and 99999) of excluded
data.
Use X or XX to exclude one or more lines of data from being displayed on the screen.
1. Example of Excluding Lines:
000016
000017
X00018 /* This single line will be excluded.
OR
XX0007 /* This block of lines 7 through 14
000008 /* will be excluded.
000013
XX0014
000015
9-6 IDEA User's Guide February 29, 1996
-------
Figure 9-2 shows the results of excluding lines 7-14 and line 18 from the query
in Figure 9-1 .
Figure 9-2. Query Lines Excluded From Display
2. Example of the F Line Command:
Typing an F on the dashed line will display the first of the 8 excluded lines. In
this case, line 7 would be displayed.
600806
F - -
000015
8 LINE(S) NOT DISPLAYED
Typing F followed by a number, will display that number of lines starting with the
first line. In this case lines 7 through 10 would be displayed.
000006
F4 - -
000015
8 LINE(S) NOT DISPLAYED
An F on lines other than excluded lines is ignored. If the number used with an F
is greater than the number of excluded lines, all of the excluded lines will be dis-
played.
3. Example of the L Line Command:
Chapter 9. Managing Keyword Queries and the ISPF Editor
9-7
-------
Typing an L on the dashed line will display the last of the 8 excluded lines. In this
case, line 14 would be displayed.
000006
L - -
000015
8 LINE(S) NOT DISPLAYED
Typing L followed by a number, will display that number of lines starting with the
last line. In this case lines 11 through 14 would be displayed.
000006
L4 - -
000015
8 LINE(S) NOT DISPLAYED
An L on lines other than excluded lines is ignored. If the number used with an L is
greater than the number of excluded lines, all of the excluded lines will be displayed.
9.2.4 Adding Comments to a Query
If you want to identify your query in a way that is understandable and easy to read,
you can add "comments" that will not be a part of the query for processing purposes,
but will remind you of the query's contents.
Simply type /* followed by your comments (see Figure 9-1). ISPF ignores anything
to the right of /* on the same line.
9.3 Using ISPF Primary Commands
Primary commands are entered at the COMMAND prompt at the top of the ISPF
EDIT SCREEN. They allow you to exercise some control over the Edit environment.
In many instances, ISPF primary commands correspond to PF keys, such as the fol-
lowing: END, RETURN, UP, DOWN, LEFT, and RIGHT.
Table 9-2 is a list of the most common ISPF primary edit commands. The com-
mands that are marked with an asterisk (*) are explained more fully in Sections 9.3.2,
Combining Queries - 9.3.5, Scrolling Data .
9-8
IDEA User's Guide
February 29, 1996
-------
Table 9-2. Primary Edit Commands
Command
CANCEL (CAN)
CHANGE (CHG) (C)
COPY (*)
CUT (*)
DELETE (DEL) (*)
DOWN(*)
END
EXCLUDE (EX)
FIND (F)
GO
HELP
LEFT (*)
MOVE
PASTE (*)
RESET (RES)
RETURN
RCHANGE
RFIND
RIGHT (*)
RETRIEVE
SAVE
SPLIT
SWAP
UPC)
Function Key
PF8/PF20
PF3/PF15
PF1/PF13
PF10/PF22
PF4/PF16
PF6/PF18
PF5/PF17
PF11/PF23
PF12/PF24
PF2/PF14
PF9/PF21
PF7/PF19
Description
Returns to previous screen without saving any
changes.
Replace the specified string with another string.
Duplicates lines from another member into the
current member.
Places selected lines into a paste buffer (lines are
selected with the C line edit command.
Deletes lines from the display.
Scrolls down by the amount set at the SCROLL
or COMMAND prompt.
Saves Changes and returns to the previous
screen.
Excludes lines from the display.
Finds the specified string.
Instructs IDEA to run a query.
Displays information about the current ISPF
screen.
Scrolls left by the amount set at the SCROLL or
COMMAND prompt.
Moves the contents of an entire member into
the current member and deletes the moved
member.
Place selected lines from buffer to specified
location (which is specified using the line edit
commands A (After) or B (Before)).
"Clean-up" the edit display.
Returns directly to the previous Primary Option
Menu.
Repeats the previous CHANGE command.
Repeats the previous FIND command.
Scrolls, right by the amount set at the SCROLL
or COMMAND prompt.
Moves the cursor to the first input field on the
screen and retrieves the last command entered.
Saves changes to the current screen (without
exiting).
Splits the screen into two sessions.
Moves the cursor from one session to the other
in the split screen mode.
Scrolls up by the amount set at the SCROLL or
COMMAND prompt.
Chapter 9. Managing Keyword Queries and the ISPF Editor
9-9
-------
9.3.1 Copying Lines From One Query to Another
The ISPF edit CUT function (see Section 9.2.2, Copying, Moving, and Repeating
Lines) allows you to copy lines within the same document. In the course of your
query writing, you may also want to transfer lines or groups of lines from one query
to another. To copy lines from one query to another, follow these steps:
1. Use the arrow keys or < Tab > to place the cursor at the left most character (on
the line number) of the line that you want to copy and type C over the number.
To copy more than one line, just type C followed by the number of lines you
want to copy (e.g., type C8 to copy eight lines including the line the cursor is on).
The lines you are copying will remain intact in the original query.
An alternate way of copying several lines is to type CC over the line numbers of
both the first and last lines you want to copy. After doing this, continue with
step #3.
2. Use the < Home > or < Tab > key to place the cursor at the COMMAND
prompt. Type CUT followed by < Enter > and ISPF will copy the line(s) into a
paste buffer for storage until you choose a final destination. A message will
appear in the upper right corner of the screen telling you how many lines were
cut.
Note that each time you use the CUT command, the lines are being copied and
placed into the paste buffer. When another range of lines is added to the buffer,
the message n Plus n Lines Cut (n= any number) appears at the top right of the
screen. You may, therefore, copy several ranges of lines and move them all
together.
3. Use the END command (or PF3) to exit the EDIT SCREEN and select the library
and member (see Sections 5.2, Managing Queries Using the Member List and 5.4,
Summary) to which you want to transfer the lines.
4. Choose the location where you want the copied lines to be placed. Move the
cursor to the left most character (on the line number) of the line above or below
where you want to put the copied text.
If you want the copied text to come after the line that the cursor is on, then type
A; if you want it before, type B.
9-10
IDEA User's Guide
February 29, 1996
-------
5. Use the < Home > or < Tab > key to place the cursor at the COMMAND
prompt. Type PASTE followed by < Enter > and the copied lines will appear in
the location you selected.
9.3.2 Combining Queries
The ISPF Editor enables you to copy an entire query (member) into a another query
(member) without cutting and pasting. The following steps assume that both queries
will be in the same library (see Section 5.1, Selecting an IDEA Library).
1. Start with the query into which you want to copy the other query. Choose the
location where you want the copied query to be placed. Use < Tab > or the
arrow keys to move the cursor to the left most character on the line above or
below where you want to put the copied text,
If you want the copied text to come after the line that the cursor is on, then type
A; if you want it before, type B.
2. Use the < Home > or < Tab > key to place the cursor at the COMMAND
prompt. Type COPY followed by a < space > and the member (query) name that
you want to copy. Press < Enter > and the copied query will appear in the
location you selected.
9.3.3 Deleting Excluded or Non-Excluded' Lines
The DELETE command is used to delete lines from the query being edited. DEL
may be used as an abbreviation.
The format for the DELETE command issued from the COMMAND prompt is:
DELETE ALL X Deletes all excluded lines from the query.
DELETE ALL NX Deletes all non-excluded lines from the query.
93.4 Clearing a Query from the ISPF Editor
If you want to erase a query without leaving the EDIT SCREEN, you can use the
Delete line command.
1. Use the arrow keys or < Tab > to place the cursor on the left most character (on
the line number) of the first line of your query.
Chapter 9. Managing Keyword Queries and the ISPF Editor 9-11
-------
2. Type D followed directly by a number that is greater than or equal to the number
of lines used by your query and press < Enter >.
935 Scrolling Data
Edit allows you to scroll up and down through the data. If the data area is too wide
to fit on the screen, you can also scroll left and right.
To scroll, enter one of the four scroll commands: UP, DOWN, LEFT, or RIGHT.
UP (PF7/PF19)
DOWN (PF8/PF20)
LEFT (PF10/PF22)
RIGHT (PF11/PF23)
move toward the top of the data
move toward the bottom of the data
move toward the first column of the data
move toward the last column of the data
To change the number of lines or columns being scrolled, change the scroll amount
field, located in the upper right corner of the EDIT SCREEN, as shown in Figure 9-3
-/* .S3fi8£a'l4^^BB^'S€sa?4i
Figure 9-3. Edit Screen With Scroll Prompt
9-12 IDEA User's Guide
February 29, 1996
-------
You can change the scroll amount by typing over the current value with a new
amount. If you enter MAX or M at the SCROLL prompt, ISPF redisplays the pre-
vious value following the scroll operation. If you enter any other scroll amount, that
amount remains effective until you change it or until you begin a new function.
If the value entered into the scroll amount field is not valid, an error message is dis-
played. Either correct the scroll amount, or take an action other than scrolling.
Valid scroll amounts are:
PAGE(P) Scroll by one page,,
HALF (H) Scroll by half a page.
n Scroll n lines (« between 1 and 9999).
MAX (M) Scroll to the top, bottom, left, or right margin.
CURSOR (CSR) Scroll until the cursor reaches the top, bottom, left, or
right edge of the screen.
DATA (D) Scroll by a page minus one line when scrolling up or
down or by a page minus one column when scrolling
left or right.
For scrolling purposes, a "page" is the amount of data currently visible on the screen.
In split screen mode, for example, a browse display might have 12 lines by 80
columns of scrollable data. In this case, a scroll amount of HALF would scroll up or
down by 6 lines, or left or right by 40 columns.
You can temporarily override the scroll amount, without changing the scroll amount
field in two different ways:
• Type a scroll direction and a scroll amount at the COMMAND prompt, and
press < Enter > (e.g., DOWN 5 or RIGHT MAX).
• Type a scroll amount at the COMMAND prompt and then press a scroll PF key
rather than pressing < Enter > .
Generally, you can combine scrolling with other actions by entering a command and
then pressing a scroll PF key (instead of the < Emter > key). Both the action and the
scroll will be processed.
Chapter 9. Managing Keyword Queries and the ISPF Editor 9-13
-------
9.4 Summary
The ISPF Editor is a mainframe word processor that is used to construct and execute
IDEA queries. ISPF edit commands are divided into two groups: line commands
and primary commands.
Edit line commands are typed over one or more line numbers on the left side of the
EDIT SCREEN and enable you to insert, delete, copy, and move lines. Single char-
acter commands operate on a line (e.g., C to copy a line, I to insert a line) and
double character commands work on a block of lines (e.g., DD on the first line to be
deleted, DD on the last line to be deleted).
Primary commands are entered at the COMMAND prompt at the top of the ISPF
EDIT SCREEN. They allow you to exercise some control over the EDIT environ-
ment, such as scrolling data or copying lines from other queries.
9-14
IDEA User's Guide
February 29, 1996
-------
Chapter 10. IDEA Standard Reports
This chapter instructs IDEA users on the different, report formats that are standard to
IDEA, and how to access, navigate, print, save, and exit them.
10.1 Choosing a Standard Report Format
IDEA reports are standard in the sense that the report formats and the type of infor-
mation presented in them are predetermined. In other words, a query defines criteria
for selecting facilities, but does not determine which facility data are presented in the
standard reports. Although users may select facilities based on a specific data
element, the data from that element does not necessarily appear in the resulting
reports. This chapter contains examples of the report formats and identifies each
data element used in IDEA standard reports. Chapter 11, IDEA User-Specified
Reports describes user-specified reports, which ena.ble users to create customized
reports.
IDEA currently allows users to choose from among four standard report formats.
Reports 1A and IB list information on individual facilities; Report 2 focuses on the
noncompliance/violation status of facilities; the Summary Report shows total facility
counts by EPA region and program along with information on toxic substances
released. The following pages describe these report formats in greater detail.
10.1.1 Report 1A
Report 1A provides a brief description of the facilities selected by your query. The
organization of the information in this report differs for Linked, Nonlinked, and
Linked nonlinked queries. In short, Linked queries return information organized by
facility whereas Nonlinked queries return information organized by the databases
from which the information was retrieved. Linked Nonlinked searches return reports
including combinations of both.
Linked
When running a Linked query, the information in Report 1A is organized into two
components: the facility heading and database information. Within the heading for
each facility, IDEA provides the FINDS identification number, facility name, address,
city, state, zip code, longitude, and latitude.
Chapter 10. IDEA Standard Reports 10-1
-------
Each facility heading is followed by pertinent information from the individual data-
bases. In Report 1A, this database information includes: name of the database,
name for the facility within the database, identification number for the facility within
the database, a facility's noncompliance or violation status, and a chart of the
number and type of EPA actions taken with regard to the facility in the past three
years. Examples of these EPA actions are evaluations, inspections, citations of vio-
lations, administrative actions, and judicial actions.
Nonlinked
A Nonlinked query returns information only from the databases addressed by your
query. Report 1A organizes this information in capsules containing the following:
the database name, the name for the facility within the database, the identification
number for the facility within the database, the facility's noncompliance or violation
status, and a chart of the number and type of EPA actions taken with regard to the
facility in the past three years. Examples of these EPA actions are evaluations,
inspections, citations of violations, administrative actions, and judicial actions.
Linked Nonlinked
Selecting both Linked and Nonlinked will generate a two part report. The first part is
organized in the Linked format described above and contains information on facilities
with valid FINDS identification numbers that match all of the selection criteria. The
second part is organized in the Nonlinked format described above and contains infor-
mation on facilities ^without valid FINDS identification numbers that match any
selection criteria.
The screens hi the following sections illustrate the reports generated by a sample
query built using GO Names to find facilities that are in aluminum-related industries.
(This is merely an exercise that has no basis in fact regarding any planned or on-
going enforcement initiatives.)
10-2 IDEA User's Guide February 29, 1996
-------
U.S. ENVIRONMENTAL PROTECTION AGENCY 08/26/93 Page 1
INTEGRATED DATA FACILITY-SPECIFIC COMPLIANCE PROFILE REPORT 1A
FINDS Id: ALD008162950 Fac. Name: ALUMINUM COMPANY OF AMERICA AL City: MOBILE State: AL
Address: ALABAMA STATE DOCKS BLVD Zip: 36601 Lat: 30.719 Long: 88.042
RCRIS Handler Id: ALD008162950 Year No. Eva! . No. NOVs No. Ms No.JAs
Name: ALUMINUM CO OF AMERICA CY91 '0000
TSD Facility Status: HPV? NO CY92 0000
Owner Operator Type: P Exist. Date: CY93 0000
PCS Permit No: AL0002976 Issue Date: 1990/10 Year All Viols Eff.Viols Inspections No. NOVs No.AAs No.JAs
Fac. Name: AL STATE DOCKS / MUD LAKES CY91 0 0 1 0 0 0
Active Minor Discharger CY92 000000
Expired Date: 1995/10 CY93 0 01 0 0 _ 0
AFS CDS Plant ID: 0109708003 Plant Name: ALUMINUM CORP OF AM.
Source Compl.
IN COMPLIANCE
Status
- INSPECTION
Air Program Desc.
SIP SOURCE
Qtrly Compl Status
33333333
Year
1991
1992 '
1993
No.Insp.
3
2
1
No. NOVs
0
0
0
No. Ms
0
0
0
No.JAs
- 0
0
0
DUNS Number: 8162950 Ult: 1339472 Status: Branch Subsidiary? No
Business: Aluminum Company of America Hierarchy Level: 1 Started in
Sales Volume: $ Mfg? No SIC Code(s): 5169,
FINDS Id: ALD031618069 Fac. Name: MOWBRAY ENGINEERING COMPANY IN City: GREENVILLE State: AL
Address: OCT OF 300 BEELAND & 2ND ST Zip: Lat: 34.993 Long: 85.308
Civil Docket Case Name Case Number Type Case Law Ovrall S1:a. Initiated To DOJ Filed Concluded
NORMAN PARKER/MOWBRAY ENGINEER04-86-0034 BNK CERCLA CASE CLOSED 1986/06 1989/01
Civil Docket Case Name Case Number Type Case Law Ovrall S1;a. Initiated To DOJ Filed Concluded
ALABAMA POWER (MOWBRAY ENGINEE04-89-0035 CIV CERCLA CONCLUDED 1990/12 1991/05
CERCLIS Site Name: MOWBRAY ENGINEERING CO Cal Year 1990 1991 1992 1993
NPL Status: F No. Admin. Actions: 0000
Site Classification: No. Judic. Actions: 0000
Figure 10-1. DEA Standard Report 1A
Report 1A provides cryptic information about the facilities selected by your query.
Sample 1A reports for each IDEA data system are given below. The report field
name is shown in bold followed by its description, the name of the data element used
(in parentheses), and a list of possible values, where appropriate.
Chapter 10. IDEA Standard Reports 10-3
-------
10.1.1.1 AFS Report 1A Elements
1. AFS CDS Plant ID: 0109788383 Plant Name: ALUHINUN CORP OF AH.
2. Source Compl. Status Air Program Desc. Qtrly Compl Status
IN COMPLIANCE - INSPECTION SIP SOURCE 33333333
Year No.Insp. No.NOVs No.AAs No.JAs
1991 3000
1992 2000
1993 1080
Figure 10-2. AFS Report 1A Elements
LINE 1
CDS Plant ID A ten character plant identifier required to assign compliance informa-
tion to plants in the AIRS Facility Subsystem. The ten characters =
2-digit numeric State Code + 3-digit FIPS County Code + 5 character
CDS Plant ID. (AFS.AFSID)
Plant Name The name associated with a plant at a given location in AFS.
(AFS.PNME)
CHART
Year Calendar year (CY) as opposed to fiscal year (FY).
No. Insp. Number of inspections. (A count of AFS. ANT 1 with 1A or 5C and
AFS.DTA1 in the appropriate calender year)
No. NOVs Number of Notices of Violation (NOVs). (A count of AFS. ANT 1 with
6A or 7C and AFS.DTA1 in the appropriate calender year)
No. AAs Number of Administrative Actions. (A count of AFS.ANT1 with IB, 2B,
3B, 7E, 8A, 8C, or 9A and AFS.DTA1 in the appropriate calender year)
No. JAs Number of Judicial Actions. (A count of AFS.ANT1 with ID, IE, 2D, 4B,
5B, 6B, or 9C and AFS.DTA1 in the appropriate calender year)
LINE 2
Source Compl. Status EPA Plant/Point Compliance Status ~ a one character code
indicating whether a plant or point is in compliance, not in compliance, or
has an unknown compliance status. This field is used when an EPA Com-
pliance status value differs from the compliance status value submitted by a
10-4
IDEA User's Guide
February 29, 1996
-------
state. The compliance status for a plant is generated to reflect the worst-
case compliance status of any pollutant regulated by an AIR program and
is maintained on the plant AIR program pollutant records. (AFS.DCS1)
(possible values)
Unknown compliance status
In violation - no schedule
In compliance - source test
In compliance - inspection
In compliance - certification
Meeting compliance schedule
In violation - not meeting schedule
In violation - unknown with regard to schedule
No applicable state regulation
In compliance - shut down
Unknown with regard to procedural compliance
In violation with regard to both emissions and procedural compliance
In compliance, with procedural requirements
In violation with regard to procedural compliance
Unknown with regard to both emissions and procedural compliance
a
Air Program Desc The regulatory AIR Program(s) authorizing and associated with an
action taken by a local, state or federal regulatory agency and to which a
plant or point is subject. (AFS.APC1)
(possible values)
SIP Source
SIP Source under federal jurisdiction
Non-Federally reportable source
CFC Tracking
PSD
NSR
NESHAP
NSPS
Qtrly Compl Status The quarterly compliance status for the facility, for the last eight
quarters, for the Air program to the left, (each digit is a separate value of
AFS.SCH1)
Chapter 10. IDEA Standard Reports 10-5
-------
A Unknown With Regard To Procedural Compliance
B In Violation With Regard To Both Emissions And Procedures
C In Compliance With Procedural Requirements
M In Compliance - CEMS
W In Violation With Regard To Procedural Compliance
Y Unknown With Regard To Both Emissions And Procedural Co
0 Unknown Compliance Status
1 In Violation - No Schedule
2 In Compliance - Source Test
3 In Compliance - Inspection
4 In Compliance - Certification
5 Meeting Compliance Schedule
6 In Violation - Not Meeting Schedule
7 In Violation - Unknown With Regard To Schedule
8 No Applicable State Regulation
9 In Compliance - Shut Down
10-6
IDEA User's Guide
February 29, 1996
-------
10.1.1.2 CER (CERCLIS) Report 1A Elements
1. CERCLIS Site Name: HOWBRAY ENGINEERING CO Cal Year 1990 1991 1992 1993
2. NPL Status: F No. Admin. Actions: 0000
3. Site Classification: No. Oudic. Actions: 0000
Figure 10-3. CER (CERCLIS) Report 1A Elements
LINE 1
Site Name The official site name for a hazardous waste site or an unanticipated
removal (incident). The official name can be the one used in the federal
register at the time of the NPL proposal or, for sites not on the NPL
(National Priorities List), designated by the region. For unanticipated
removals not occurring at a previously identified hazardous waste site (e.g.,
an oil spill), the official name is designated by the region. (CER.0104)
CHART
Cal Year Calendar year (CY) as opposed to fiscal year (FY).
LINE 2
NPL Status Indicator that categorizes a site's NPL status, for statistical analysis and
reporting purposes. (CER.0305)
D Deleted from the final NPL
F Currently on the final NPL
N Not on NPL
O Not valid site or incident as defined in CERCLIS (this code can be used for
regional management purposes)
P Proposed for NPL
R Removed from proposed NPL
S Pre-proposal site
No. Admin. Actions Number of Administrative Actions. (A count of CER. 1732 with
AC, AV, CA, FI, RR, SO, or UA and CER.1716 or CER.1717 in the
appropriate calender year.)
LINE 3
Chapter 10. IDEA Standard Reports 10-7
\
-------
Site Classification Code which identifies the overall programmatic classification for all
NPL sites as determined by the region after the completion of a PRP
search. (CER;0226)
F Fund lead
FE Federal enforcement
ND No determination
NG Fund lead negotiation
SE State enforcement
No. Judic. Actions Number of Judicial Actions. (A count of CER.1732 with CB, CC,
CD, CL, SD, SF, SV, or SX and CER.1716 in the appropriate calender
year, or CER.1732 with JG or TE and CER.1717 in that year.)
10-8 IDEA User's Guide February 29, 1996
-------
10.1.1.3 DCK (Civil Docket) Report 1A Elements
Civil Docket Case Name
NORMAN PARKER/HOWBRAY ENGINEER
Case Number Type Case Law Ovrall Sta. Initiated To DOJ Filed Concluded
04-86-0034 BNK CERCLA CASE CLOSED 1986/06 1989/01
Figure 10-4. DCK (Civil Docket) Report 1A Elements
Case Name The name of the case as it is referred to in the litigation report or com-
plaint. (DCK.CSNM)
Case Number A unique identifier assigned to each case. The number is assigned by
Regional Docket Control and consists of a responsible office code, the
fiscal year the case is opened or initiated, and a four-digit sequentially
assigned number (example: 01-84-0012:). (DCK.CSNO)
Type Case A code indicating the type of case or action taken. (DCK.TYPC)
ACC Access order
ASH Special handling
AUK Unknown
AUR Under review
BNK Bankruptcy !
CIA Civil ADMEND CONS
CIC Civil contempt
CIT Citizen case
CIV Civil
CLIST Contractor listing
COL Collection action
EAR EPA Action required
FAD Federal facility agreements
MIS Misc proceedings
PRN Pre-referral negotiation
SDWANON SDWA Notice of Non Compliance
SDWANOV SDWA Notice of Violation
SSO Steel Stretch Out
TSCANON TSCA Notice of Non Compliance
TSCANOV TSCA Notice of Violation
104E CERCLA 104E AO info and access request
Chapter 10. IDEA Standard Reports
10-9
-------
105 MPRSA 105 Comp and penally order
106 CERCLA 106 (AO) for response action
107L CERCLA 107L filing of lien
109A CERCLA 109A Class I AO for penalties
109B CERCLA 109B CLASS II AO for penalties
11005 MWTA 11005 compliance and penalty order
113 CAA 113 Notice_pf Violation
113A CAA 113A Admin Order (AO)
H3D CAA 113D delayed compliance order
114 CAA 114 information request letters
12 FIFRA 12 unlawful acts
120 CAA 120 Notice of Noncompliance
122/104 Adm. Order for investigative studies
122G CERCLA 122G Admin. Deminimis cost recov settlement
122H CERCLA 122H Admin. Order for cost recovery
13 FIFRA 13 SSUR order
14 FIFRA 14 (AO) for comp and penalties
1414G2 SDWA 1414 PWS comp order 1st time
1414G3 SDWA 1414 PWS (AO) for compliance
Law A code indicating the laws under which the case is proceeding.
(DCK.LAWS)
AKA Anti-Kickback Act
APA Administrative Procedures Act
ATA Anti-Trust Act
BANKR Bankruptcy
CAA Clean Air Act
CAAEM CAA mobile, emissions
CAAIN CAA mobile, inspection
CAARE CAA mobile, recall
CAATA CAA mobile, tampering
CAAVA CAA mobile, vapor
CBRA Coastal Barrier Resources Act
CERCLA Superfund
CIVIL Civil Rights Act of 1964
CLA Comp. & Liab. Act of 1980
CLF Common Law of Fraud
CLN Common Law of Nuisance
CONST Constitution
CSRA Civil Service Reform Act
CWA Clean Water Act
CWHSS Contract Work Hours & Safety Standards
10-10 IDEA User's Guide
February 29, 1996
-------
CZMA Coastal Zone Management Act
C1001 Know making false stmts
C1341 Mail fraud
C1505 C1505
DBA Davis-Bacon Act
EAJA Equal Access to Justice Act
EPCA Energy Policy Conservation Act
EPCRA Emergency Planning and Community Right to Know Act
ESA Endangered Species Act
FCA False Claims Act
FCCA Federal Claims Collection Act
FFDCA Federal Food, Drug, and Cosmetic Act
FGCAA Federal Grant and Coop Agreement Act
FIFRA Fed Insect, Fun. & Rod. Act
FLSA Fair Labor Standards Act
FOIA Freedom of Information Act
FPPA Farmland Protection Policy Act
FTCA Federal Tort Claims Act
HATCH Hatch Act
ICA Intergovernmental Cooperation Act
IGA Inspector General's Act
IPA Intergovernmental Personnel Act
MPCEC Military Personnel/Civ Employees Claims Act
MPRSA Mar. Prot., Res. & Sane. Act
MVICS Motor Vehicle Info. And Cost Savings Act
MWTA Medical Waste Tracking Act
NCA Noise Control Act ,
NEPA National Environmt. Policy Act
NHPA National Historic Preservation Act
OTH Other
PA Privacy Act
PFCRA Program Fraud Civil Remedies Act
RC.RA Res. Conserv. & Rec. Act
REFA Rivers & Harbor Act, 1899
RFA Regulatory Flexibility Act
RFPA Right to Financial Privacy Act
SARA Superftmd Amendment and Reauthorization Act, 1986
SCA Service Control Act
SDWA Safe Drinking Water Act
TSA Trade Secrets Act
TSCA Toxic Substances Control Act
URRPA Unifrm. Reloc. Assist & Real. Prop. Asq. Act
4 Proc. Under assistance title
40CFR 4OCFR
Chapter 10. IDEA Standard Reports
10-11
-------
Overall Sta. A code and corresponding description indicating how far the case has
progressed. (DCK.OSTA)
CASE CLOSED
OPENED
PRN
RET TO REG
TAKEN
AT EPA HQ
ATDOJ
AT US ATTY
FILED CRT
CONCLUDED
Case closed
Opened
PRN ~
Returned to region
Taken
At EPA-HQ
AtDOJ
At US ATTY
Filed in court
Concluded
Initiated The date that EPA issued the action. (DCK.CDMD)
To DOJ The date that the case was sent to the Department of Justice.
(DCK.CDOJ)
Filed The date that the case was filed in District Court. (DCK.CFLD)
Concluded The date the case was concluded. (DCK.CCNC)
10-12 IDEA User's Guide February 29, 1996
-------
10.1.1.4 DUN (Dun & Bradstreet) Report 1A Elements
DUNS Number: 8162950 UH: 1339472 Status: Branch Subsidiary? No
Business: Aluminum Company of America Hierarchy Level: 1 Started in
Sales Volume: $ Hfg? No SIC Code(s): 5169
Figure 10-5. DUN (Dun & Bradstreet) Report 1A Elements
LINE 1
DUNS Number A Data Universal Numbering System (DUNS) random numeric serial
number. (DUN.DCNO)
Ult Ultimate Number -- the DUNS number of the topmost firm of a "Family-
Tree" group of companies. The field will either contain data or blanks.
(DUN.ULNO)
Ultimate records show a repetition of their own DUNS number. Their
DUNS number is repeated in this field so that a common sort and/or
match area is available for headquarters and branch records.
Status Indicates the status of the business. (DUN. STAT)
NOTHQ/BRANCH DUN.STAT=0
HEADQUARTERS DUN.STAT = 1
BRANCH DUN.STAT=2
Subsidiary?. Indicates whether the business is a subsidiary or not. (DUN.SUBI)
Yes DUN.SUBI = 3
No DUN.SUBI = 0
LINE 2
Business The correct legal name of the business. (DUN.DNME)
Hierarchy Level A hierarchy indicator with possible values 1-4. (DUN.HIER)
Chapter 10. IDEA Standard Reports 10-13
-------
Started in Gives the year that the business started. (DUN.YRST) This field appears
only when facility status is either NOT HQ/BRANCH or HEADQUAR-
TERS.
LINES
Sales Volume The annual sales volume of the business in dollars. (DUN.SALESV)
This field appears only when facility status is either NOT HQ/BRANCH or
HEADQUARTERS.
Mfg? Whether manufacturing is done at this address.(DUN.MFGI)
Yes DUN.MFGI = 0
No DUN.MFGI = 1
SIC Code(s) The Standard Industrial Classification (SIC) Code system categorizes
business establishments based upon the type of activity done by that estab-
lishment at that location. Each SIC consists of a four-digit code, defined
by the US Government. (DUN.SIC1, DUN.SIC2, DUN.SIC3)
10-14 IDEA User's Guide February 29, 1996
-------
10.1.1.5 ERN (ERNS) Report 1A Elements
1. ERNS Discharger Id: TXQ0266633 • Spills -- last five years: 2
2. Discharger: EXXON CO USA Host recent: 05/19/92
3. Deaths: Injuries: 1 Evacuations: Damages: $13000
Figure 10-6. RN (ERNS) Report 1A Elements
LINE 1
ERNS Discharger Id A unique number for the ERNS Discharger (ERN.OWNID).
IDEA derives this number from the EELNS Discharger ID (ERN.DID),
DOWNID (ERN.DOWNID), and the OWNID (ERN.OWNID) fields.
The Discharger State abbreviation prefixes this number. (ERN. STATE)
Spills -- last five years Total Number of Spills for this Discharger in the last five
years.
LINE 2
Discharger Name of the Discharger organization. (ERN.DORG)
Most recent Date of the most recent incident for this Discharger. (ERN.DTSPI)
LINE 3
Deaths The total number of fatalities resulting from releases for this Discharger.
(ERN.DEATHS)
Injuries The total number of injuries resulting from releases for this Discharger.
(ERN.INJS)
Evacuations The total number of evacuation resulting from releases for this
Discharger (ERN.EVACS) and/or an indication that evacuations were nec-
essary (ERN.EVAC).
Note: If the total number of evacuations is not present in the ERNS data,
this field will appear as EVACUATIONS REQ'D.
Chapter 10. IDEA Standard Reports 10-15
-------
Damages The estimated dollar amount of property damage resulting from releases for
this Discharger (ERN.PROPDMG) and/or an indication that damages
occurred (ERN.DAM AGES). Note: If the amount of damages is not
present in the ERNS data, this field will appear as PROPERTY
DAMAGE.
10-16 IDEA User's Guide February 29, 1996
-------
10.1.1.6 FFI (FFIS) Report 1A Elements
Federal Facility Id: AL-68Q030926 Name: EASTERN ENVIRONMENTAL Addr: 1504 A AVE MONTGOMERY
Figure 10-7. FFI (FFIS) Report 1A Elements
Federal Facility Id The EPA identification code for the federal facility. (FFI.EPID)
Name The name of the facility. (FFI.FNME)
Addr Street address and city for the facility. (FFI.STR1 and FFI.CITY)
Chapter 10. IDEA Standard Reports 10-17
-------
10.1.1.7 FIN (FINDS) Report 1A Elements
1. FINDS Id: ALD008162950 Fac. Name: ALUMINUM COMPANY OF AMERICA At City: MOBILE State: AL
2. Address: ALABAMA STATE DOCKS BLVD Zip: 36601 Lat: 30.719 Long: 88.042
Figure 10-8. FIN (FINDS) Report 1A Elements
LINE1
FINDS Id EPA ID Number. (FIN.EPID)
Fac. Name Facility Name. (FIN.FNME)
City City where the facility is located. (FIN.FCTY)
State State where the facility is located. (FIN.STAT)
LINE 2
Address The facility's street address. (FIN.STR1)
Zip
The facility's ZIP code. (FIN.FZIP)
Lat
The facility's latitude in degrees. (FIN.LATD)
Long The facility's longitude in degrees. (FIN. LONG)
10-18 IDEA User's Guide
February 29, 1996
-------
10.1.1,8 LST (Contractor Listing Docket) Report 1A Elements
1. LST Case Number: 02-91-L034 Case Name: EXXON BAYWAY REFINERY
2. Case Type: Mandatory Listing Case Status: Removed
3. Basis for Listing: CWA/Federal Court Order
4. Case Opened: 03/25/91 Case Initiated: 03/25/91 Case Listed: 06/26/91 Case Closed: 02/04/92
5. HQ Attorney: BUFILL, L. Regional Attorney: MORALES, D.
Figure 10-9. LST (Contractor Listing Docket) Report 1A Elements
LINE 1 ,
Case Number Unique identifier assigned in sequential order by Headquarters Docket
Control. (LST.CSNO)
Case Name Name of the case as referred to by attorneys. In many cases, this is also
the name of the facility. (LST.CSNM)
LINE 2
Case Type Whether a case listing is required by law or is made at the discretion of
EPA. (LST.TYPC)
Discretionary Case Listing
Mandatory Case Listing
Case Status Case status comments (LST.CSCM)
OPENED
INITIATED
PROPOSAL NOTICE - LISTING
LISTING HEARING REQUESTED
APPEAL TO OGC - LISTING
LISTED
REMOVAL REQUESTED
NOTICE OF DETERMINATION - REMOVAL
REMOVAL HEARING REQUESTED
APPEAL TO ADMINISTRATOR - REMOVAL
REMOVED
CONCURRENT LISTING AND REMOVAL
WITHDRAWN BY RECOMMENDING PERSON - LISTING
AA DECLINES TO PROCEED WITH LISTING
CE DETERMINES NOT TO LIST
LINE 3
Chapter 10. IDEA Standard Reports 10-19
-------
Basis for Listing The law the contractor was convicted under (either the Clean Air
Act or the Clean Water Act) and the Court Action that started the listing
procedure. (LST.BLAW and LST.BACT)
FEDERAL COURT CONVICTION
COMPLAINT FILED
FEDERAL COURT ORDER _
NOTICE OF NONCOMPLIANCE (CAA ONLY)
STATE COURT CONVICTION
STATE COURT ORDER
VIOLATION OF ADMINISTRATIVE ORDER
LINE 4
Case Opened The date when EPA Headquarters received information about a case.
The date must be earlier than or the same as the earliest listing event date
(mm/dd/yy). (LST.DCOP)
Case Initiated The date of the earliest initiating event date for a case (mm/dd/yy).
(LST.DCIN)
Case Listed The effective listing date for a facility (mm/dd/yy). (LST.DCLS)
Case Closed The date of the earliest closing event date. It is calculated from listing or
removal events (mm/dd/yy). (LST.DCOL)
LINE 5
HQ Attorney The last name and first initial of the EPA headquarters attorney
assigned to the case. (LST.HQNM)
Regional Attorney The last name and first initial of the EPA region attorney assigned
to the case. (LST.RGNM)
10-20 IDEA User's Guide
February 29, 1996
-------
10.1.1.9 NCD (NCDB) Report 1A Elements
1. NCDB Site Name: ALUMINUM CO OF AMERICA-RIVERDALE Facility Function: DI Pestacide Estab Number:
2- Importer Name: Schools Inspected: SIC Codes : 9998
3. Respondent Name: ALUMINUM CO OF AMERICA
4. ' YEAR No. of No. of No. of No. of Statute
5. Inspections NONS Adm Act Jud Act Violated
INSPECT 1990 1000 TSCA
Figure 10-10. NCD (NCDB) Report 1A Elements ~
LINE 1
Site Name The name of an inspection site. (NCD.NAME with
NCD.NAMETYP= 'SITE')
Facility Function Facility Function Code (NCD.FACILIT)
FIFRA:
BK Broker
CA Certified Commercial Applicator
DL Dealer
DS Drift Site
DT Distributor
LB Laboratory
MK Marketplace
OP Other Parties
PA Certified Private Applicator
PD Producer
PT Port of Entry
RG Registrant
RU Rup Dealer
SA Supervised Applicator
TS Target Site
UA Uncertified Applicator
US User
TSCA:
Chapter 10. IDEA Standard Reports 10-21
-------
BK
CV
DA
DH
DI
DL
DM
DP
DR
DT
LB
MI
MN
PC
PS
PT
ST
US
Broker
Conveyor
Permitted Disposer - Alternative Methods
Permitted Disposer - High Efficiency Boilers
Permitted Disposer - Incinerator
Permitted Disposer - Landfill
Permitted Disposer - Dredge/Sludge Material
Disposer
Permitted Disposer - Research/Develop
Distributor
Laboratory
Manufacturer/Importer
Manufacturer
Processor
Secondary Processor
Port of Entry
Storer
User
Pesticide Estab Number Pesticide producer establishment number ~ the EPA registra-
tion number identifying pesticide producing establishments.
(NCD.EPESTAB)
LINE 2
Importer Name Name of importer. (NCD.NAME with
NCD.NAMETYPE= 'IMPORTER')
Schools Inspected Number of schools inspected. (NCD.SCHOOLS)
SIC Codes Up to six 4-digit standard industrial classification (SIC) codes.
(NCD.SICLIST)
LINES
Respondent Name The name of the respondent. (NCD.NAME with
NCD.NAMETYP = 'RESPOND')
LINEs 4 & 5
10-22 IDEA User's Guide February 29, 1996
-------
YEAR Calendar year, (based on NCD.INSPE>TE, NCD.REFDATE,
NCD.MAISSUE; or NCD.AOISUUE)
No. of Inspections Number of inspections. (Count of NCD.INSPDTE's (date of
inspection.)
No. of NONS Number of Notices of Npncompliance. (Count of NCD.ACTNTYP =
'NON' and NCD.MAISSUE or NCD.AOISSUE in the given calender year,
or NCD.IACTNTY = 'NON' and NCD.INSPDTE in the given calender
year.)
No. of Adm Act Number of Administrative Actions. (Count of NCD.ACTNTYP
starting wh 'C', excluding 'CCR', and NCD.MAISSUE or NCD.AOISSUE
in the given calender year, or NCD.IACTNTY starting with 'C', excluding
'CCR', and NCD.INSPDTE in the given calender year.)
No. of Jud Act Number of Judicial Actions. (Count of NCD.ACTNTYP = 'CCR',
and NCD.MAISSUE or NCD.AOISSUE in the given calender year, or
NCD.IACTNTY = 'CCR', and NCD.INSPDTE in the given calender
year.)
Statute Violated The name of the statute that was violated. (Based on
NCD.LEGISLA)
Chapter 10. IDEA Standard Reports 10-23
-------
10.1.1.10 OSH Report 1A Elements
1. OSHA Activity Link: CA 111765970
2. Name: INSERT FACILITY NAME HERE
3. Employees at site: 60
4. Lost Workday Injury Rate: 0.00
Inspections — last five years
Health: 0 Penalties: $0
Safety: 1 Violations: 0
Serious Violations: 0
Figure 10-11. OSH Report 1A Elements
LINE 1
OSHA Activity Link An IDEA derived link between OSHA inspections. Although
every attempt has been made to link inspections of the same facility
together, a single facility may have several Activity Links, due to limita-
tions in the data. (OSH.ESTABNR)
LINE 2
Name The name of the establishment. (OSH.ESTAB)
Health The number of health inspections in the last five years, (count of
OSH.ACTIVTY with OSH.DTOPEN in the last five years and
OSH.INSPCAT = H.)
Penalties The sum of the total penalties for the inspections in the last five years.
(sum of OSH.AMTPEN values, for inspections with OSH.DTOPEN in the
last five years)
LINES
Employees at site The number of employees at the site on the most recent inspection.
(OSH.SITEMPL)
Safety The number of safety inspections in the last five years, (count of
OSH.ACTIVTY with OSH.DTOPEN in the last five years and
OSH.INSPCAT = S.)
Violations The total number of violations cited on inspections conducted in the last
five years, (sum of OSH.VIOLS for inspections with OSH.DTOPEN in the
last five years)
10-24 IDEA User's Guide
February 29, 1996
-------
LINE 4
Lost Workday Injury Rate The lost workday injury rate calculated on the most recent
inspection. (OSH.LWDI)
Serious Violations The total number of serious violations cited on inspections con-
ducted in, the last five years, (sum of OSH.SRVIOLS for inspections with
OSH.DTOPEN in the last five years)
Chapter 10. IDEA Standard Reports 10-25
-------
10.1.1.11 PCS Report 1A Elements
1. PCS Permit No: ALQQ02976 Issue Date: 1990/10 Year All Viols Eff.Viols Inspections No.NOVs
2. Fac. Name: AL STATE DOCKS / HUD LAKES CY91 0010
3. Active Minor Discharger CY92 0000
4. Expired Date: 1995/10 CY93 0010
No. Ms No.JAs
0 0
0 0
0 0
Figure 10-12. CS Report 1A Elements
LINE 1
Permit No The NPDES identification number. (PCS.NPDES)
Issue Date The actual date the permit was issued (PCS.PTAC with PCS.PTEV =
'P4099')
CHART
Year Calendar year (CY) as opposed to fiscal year (FY).
All Viols Total number of violations. (A count of PCS.MVDT dates in the appro-
priate calender year with a PCS.MVIO present.)
Eff. Viols Number of effluent violations. (A count of PCS.MVDT dates in the appro-
priate calender year with a PCS.MVIO equal to E90 (Numeric Violation).)
Inspections Number of inspections. (A count of PCS.DTIN (inspection dates) in the
appropriate calender year.)
No. NOVs Number of Notices of Violations (NOVs). (A count of PCS.ENAC with 20
or 83 and PCS.ENDT in the appropriate calender year.)
No. AAs Number of Administrative Actions (AAs). (A count of PCS.ENAC with
AA, AC, AE, AF, Al, A3, AS, A7, 21, 23, 56, 62, 72, 75, 76, 80, 81, 84
through 90, 96, or 97 and PCS.ENDT in the appropriate calender year.)
No. JAs Number of Judicial Actions (JAs).). (A count of PCS.ENAC with 19, 25,
26, 35, 36, 37, 38, 58, 64, or 71 and PCS.ENDT in the appropriate calender
year
LINE 2
10-26 IDEA User's Guide
February 29, 1996
-------
Fac. Name The name of the entity located at the facility's physical address.
(PCS.PNAM and PCS.PNM2) .
LINE 3
Active Active/Inactive discharger indicator. (PCS.IACC)
Minor Discharger Major/Minor discharger indicator. (PCS.MADI)
LINE 4
Expired Date The date the this permit will expire. (PCS.PTAC with PCS.PTEV equal
to T5099'.)
Chapter 10. IDEA Standard Reports 10-27
-------
10.1.1.12 RCR (RCRIS) Report 1A Elements
1. RCRIS Handler Id: ALD008162950 • Year No.Eval. No.NOVs No.Ms No.JAs
2. Name: ALUMINUM CO OF AMERICA CY91 0 0 0 ' 0
3. TSD Facility Status: HPV? NO CY92 0000
4. Owner Operator Type: P Exist. Date: CY93 0000
Figure 10-13. RCR (RCRIS) Report 1A Elements
LINE1
Handler Id Handler ID number - usually the same as the EPA ID number.
(RCR.ID)
CHART
Year Calendar year (CY) as opposed to fiscal year (FY).
No. Eval. Number of Evaluations. (A count of RCR.ETYPE with RCR.EVALDTE
in the appropriate calender year.)
No. NOVs Number of Notices of Violations (NOVs). (A count of RCR.ENFTYPE
equal to 120 with RCR.EDATE in the appropriate calender year.)
No. AAs Number of Administrative Actions. (A count of RCR.ENFTYPE with
values in the range from 200 to 399 with RCR.EDATE in the appropriate
calender year.)
No. JAs Number of Judicial Actions. (A count of RCR.ENFTYPE with values in
the range from 400 to 699 with RCR.EDATE in the appropriate calender
year.)
LINE 2
Name Handler name in RCRIS. (RCR.NAME)
LINES
10-28 IDEA User's Guide February 29, 1996
-------
TSD Facility Status A code indicating that the handler is engaged in the treatment,
storage, or disposal of hazardous waste. There can be up to three values
listed on the report, one each for treatment, storage, and disposal.
(RCR.TSD)
X is engaged in TSD
N not engaged in TSD, verified
blank not engaged in TSD, unverified
HPV? Whether or not the facility is a High Priority Violator (HPV). (based on
RCR.CPVIOL)
LINE 4
Owner Operator Type A code indicating the owner/operator type. (RCR.COTYPE)
F
S
P
I
c
M
D
O
Federal
State
Private
Indian
County
Municipal
District
Other
Exist. Date Existence date — the date that operation of the facility commenced, or the
date construction on the facility commenced, or the date that operation is
expected to begin. (RCR.HEXDATE)
Chapter 10, IDEA Standard Reports 10-29
-------
10.1.1.13 TRI Report 1A Elements
1. TRI Id: 528Q8LHNHCHIGHW Facility Name: ALCOA
2. YR Chem Count Lbs:NP Air Pt Air Water UG Inj. Land POTW Off-Site Total
1991 17 195305 1870900 3270 0 750 0 175720 2245945
Figure 10-14. TRI Report 1A Elements
LINE1
Id TRI facility identifier. A generated facility identification using facility
name, address, and ZIP code. (TRI.TFID)
Facility Name The name of the facility. (TRI.HNME)
LINE 2
YR The reporting year. (TRI.RPYR)
Chem Count Number of chemicals released by the facility, (count of TRI.TCID's)
Lbs: Indicates that the values for the following fields are in Ibs.
NP Air Amount of non-point source emissions to the air. (based on TRI.MREST's
withTRI.CREL=l)
Pt Air Amount of point source emissions to the air. (based on TRI.MREST's with
TRI.CREL = 2)
Water Amount released to water, (based on TRI.MREST's with TRI.CREL= 3)
UG Inj. Amount released by way of underground injection, (based on
TRI.MREST's with TRI.CREL=4)
Land Amount released to land, (based on TRI.MREST's with TRI.CREL= 5)
POTW Amount released to publicly owned treatment works (POTW). (based on
TRI.MREST's with TRI.CREL= 6)
10-30 IDEA User's Guide February 29, 1996
-------
Off-Site Amount disposed of off-site, (based on TRI.MREST's with TRI.CREL= 7)
Total The sum of the amounts from the release media cited in the chart: NP Air,
Pt Air, Water, UG Inj., Land, POTW, and Off-Site, (sum of
TRI.MREST's)
10.1.2 Report IB
Report IB provides a detailed description of the facilities selected by your query. The
organization of the information in this report differs for Linked, Nonlinked, and
Linked nonlinked queries. Linked queries return information organized by facility
whereas nonlinked queries return information organized by the databases from which
the information was retrieved. Linked Nonlinked searches return a combination of
both.
Linked
When running a Linked query, the information in Report IB is organized into two
components: the facility heading and database information. Within the heading for
each facility, IDEA provides the FINDS identification number, facility name, address,
city, state, zip code, longitude, and latitude.
Each facility heading is followed by pertinent information from the individual data-
bases. In Report IB, this database information includes: the database name, name
for the facility within the database, identification number for the facility within the
database, and the facility's noncompliance or violation status. Also presented is a
history of the number and type of EPA actions taken with regard to the facility
during all of the years for which information is available. Examples of these EPA
actions are evaluations, inspections, citations of violations, administrative actions,
and judicial actions.
Nonlinked
A Nonlinked query returns information only from the databases addressed by your
query. Report IB contains the following: the database name, the name for the
facility within the database, the identification number for the facility within the data-
base, the facility's noncompliance or violation status, and a history of the number
and type of EPA actions taken with regard to the facility in the years for which infor-
mation is available. Examples of these EPA actions are evaluations, inspections, cita-
tions of violations, administrative actions, and judicial actions.
Chapter 10. IDEA Standard Reports 10-31
-------
Linked Nonlinked
There are two parts to the Report IB format resulting from a Linked Nonlinked
query. The first part is organized in the Linked format described above and contains
information on facilities with valid FINDS identification numbers that match all of
the selection criteria. The second part is organized in the Nonlinked format described
above and contains information on facilities without valid FINDS identification
numbers that match any selection criteria.
The screens in the following sections illustrate the reports generated by a sample
query built using GO Names to find facilities that are in aluminum-related industries.
Note: this is the same example used in Section 10.1.1, Report 1A .
U.S. ENVIRONMENTAL PROTECTION AGENCY 08/26/93 Page 1
INTEGRATED DATA FACILITY-SPECIFIC COMPLIANCE PROFILE REPORT IB
+ + + + + + + + + + + + +—
FINDS Id: ALD008162950 Fac. Name: ALUMINUM COMPANY OF AMERICA AL City: MOBILE State: AL
Address: ALABAMA STATE DOCKS BLVD Zip: 36601 Lat: 30.719 Long: 88.042
Resource Conservation and Recovery Information System (RCRIS) Summary
Handler ID: ALD008162950 Handler Name: ALUMINUM CO OF AMERICA Address: ALABAMA STATE DOCK RD
City: MOBILE County: ALQ97 State: AL Zip: 36652
Sic code(s): 3334 2819
Owners(s)/0perator(s) Name Owner/Operator Indicator
OWNERNAME CO
OPERNAME CP
Generato- Indicator: 1 Transporter Indicator: TSD Indicator: Source: N
RCRIS Handler Id: ALD008162950 Year No.Eval. No.NOVs No.AAs No.JAs
Name: ALUMINUM CO OF AMERICA CY91 0 0 0 0 . •
TSD Facility Status: HPV? NO CY92 0000
Owner Operator Type: P Exist. Date: CY93 0000
U.S. ENVIRONMENTAL PROTECTION AGENCY 08/26/93 Page
INTEGRATED DATA FACILITY-SPECIFIC COMPLIANCE PROFILE REPORT IB
Permit Compliance System(PCS) Summary
Permit Number: AL0002976 Consolidated ID: Facility Name: AL STATE DOCKS / MUD LAKES
City:HOBILE County: MOBILE State: AL
SIC Code: 2819
Permit Date Issued: 1990/10 Permit Date Expired: 1995/10 Major Discharge Indicator:
Current Year Noncompliance Status Auto.:
Current Year Noncompliance Status Man.:
PCS Overall Summary
PCS Permit No: AL0002976 Issue Date: 1990/10 Year All Viols Eff.Viols Inspections No.NOVs No.AAs No.JAs
Fac. Name: AL STATE DOCKS / MUD LAKES CY91 0 0 1 00 0
Active Minor Discharger CY92 Q 0 0 0 0 0
Expired Date: 1995/10 CY93 0 0 1 0 0 G
Figure 10-15. IDEA Standard Report IB
10-32 IDEA User's Guide February 29, 1996
-------
Report IB provides a detailed description of the facilities selected by your query.
Sample reports for each IDEA data system are given below. The report field name is
shown in bold followed by its description, the name of the data element used (in
parentheses), and a list of possible values, where appropriate.
Chapter 10. IDEA Standard Reports 10-33
-------
10.1.2.1 AFS Report IB Elements
AIR FACILITY SUBSYSTEM (AFS) SUMMARY
1. CDS Plant ID: Q109708Q03 Plant Name: ALUMINUM CORP OF AM. Address: AL STATE DOCKS
2. City: MOBILE County: 097 State: ALABAMA
3. Primary SIC Code: 2819 Secondary SIC Code: 0 EPA Classification Code: Al Govt. Facility Code Desc:
4. Sign.Viol.Flag 1: Sign.Viol.Flag 2: Sign.Viol.Flag'3: Sign.Viol.Flag 4:
5. Plant Compliance Status: IN COMPLIANCE - INSPECTION
6. Air Program: SIP SOURCE
7. Plant Historical QTR/FY Plant Compliance Status QTR/FY Plant Compliance Status
Compliance Status: 04/91 IN COMPLIANCE - INSPECTION 01/92 IN COMPLIANCE - INSPECTION
02/92 IN COMPLIANCE - INSPECTION 03/92 IN COMPLIANCE - INSPECTION
04/92 IN COMPLIANCE - INSPECTION 01/93 IN COMPLIANCE - INSPECTION
02/93 IN COMPLIANCE - INSPECTION 03/93 IN COMPLIANCE - INSPECTION
8.
Pol 1utant
CO
N02
PT
PX
S02
VOC
Pollutant
Compliance
Status
3
3
3
3
3
3
National Actions Description
STATE INSPECTION
STATE INSPECTION
STATE INSPECTION
STATE INSPECTION
STATE INSPECTION
AFS Overall Summary —
Pollutant
Classification
UK
UK
UK
Al
UK
Al
AQCR
Attain/Nonattain
Status
A
A
A
A
A
A
Date Achieved
02/27/86
07/10/86
08/13/86
10/22/86
12/16/86
Penalty Amount
10. AFS CDS Plant ID: 0109708003 Plant Name: ALUMINUN CORP OF AM.
11. Source Compl. Status Air Program Desc. Qtrly Compl Status
12. IN COMPLIANCE - INSPECTION SIP SOURCE 33333333
Year
1991
1992
1993
No.Insp.
3
2
1
No.NOVs
0
0
0
No. Ms
0
0
0
No.JAs
0
0
0
Figure 10-16. AFS Report IB Elements
LINE1
CDS Plant ID A ten character plant identifier required to assign compliance informa-
tion to plants in the AIRS Facility Subsystem. The ten characters consist
of a 2-digit State code, a 3-digit County code, and a 5-character CDS Plant
ID. (AFS.AFSID)
Plant Name Name of the plant. (AFS.PNME)
Address Plant street/mailing address. (AFS.STRT)
LINE 2
10-34 IDEA User's Guide
February 29, 1996
-------
City Plant city name. (AFS.CYNM)
County Plant county number from CDS Plant ID. (derived from AFS.AFSID)
State Plant State name, (derived from AFS.AFSID)
LINE 3
Primary SIC Code Primary 4-Digit Standard Industrial Classification Code.
(AFS.SIC1)
Secondary SIC Code Secondary 4-Digit Standard Industrial Classification Code.
(AFS.SIC2)
EPA Classification Code Code indicating plant-level emissions classification per
Alabama Power Decision "Major Source" definition. (AFS.DCL1)
Al Actual or Potential Controlled Emissions, > 100 tons/year
A2 Actual Emissions < 100 tons/year, but Potential Uncontrolled Emissions > 100
tons/year
B Potential Uncontrolled Emissions < 100 tons/year
UK Unknown
El Unregulated Pollutant Actual or Potential Controlled Emissions > 100 tons/year
E2 Unregulated Pollutant Actual Emissions < 100 tons/year
Govt. Facility Code Desc Indicator of Federal, State, or local government ownership
or operation. (AFS.GOVT)
0 Not owned or operated by a Federal, State, or local government
1 Owned or operated by the Federal Government
2 Owned or operated by the State
3 Owned or operated by the County
4 Owned or operated by the Municipality
5 Owned or operated by the District
LINE 4
Sign. Viol. Flag 1 Status code indicatong a major source "Significant Violator", and
lead enforcement agency of current violation. (AFS.SVI1)
Sign. Viol. Flag 2 "Significant Violator" status of previous violation. (AFS.SVI2)
Chapter 10. IDEA Standard Reports 10-35
-------
Sign. Viol. Flag 3 "Significant Violator" status of 2nd most previous violation.
(AFS.SVI3)
i
Sign. Viol. Flag 4 "Significant Violator" status of 3rd most previous violation.
(AFS.SVI4)
E EPA has lead enforcement
S State has lead enforcement
B EPA/State shared enforcement
X Lead enforcement not determined
C Source w/SVIL = B that changed Compliance Status Code from 1 or 6 to 5, 7,
or 0
D Source w/SVIL = B that changed Compliance Status Codefrom 1 or 6 to 2, 3, 4,"
8, or 9
F Source w/SVIL = E that changed Compliance Status Code from 1 or 6 to 5, 7,
or 0
G Source w/SVIL = E that changed Compliance Status Codefrom 1 or 6 to 2, 3, 4,
8, or 9
T Source w/SVIL = S that changed Compliance Status Code from 1 or 6 to 5, 7, or
0
U Source w/SVIL = S that changed Compliance Status Code from 1 or 6 to 2, 3, 4,
8 or 9
LINE 5
Plant Compliance Status Indicator of plant compliance/noncompliance, generated to
reflect the worst case compliance status of any pollutant regulated by an
AIR Program. (Derived from AFS.DCS1, which takes the same values as
AFS.DCAP. See the list of values for Pollutant Compliance Status for a
list of possible entries here.)
LINE 6
Air Program AIR Program Code = Indicator/description of the regulatory air
program to which the plant is subject. (AFS.APC1 Table Value)
Acid Precipitation AFS.APC1=A
Native American AFS.APC1 = I
MACT (Section 63 NESHAPS) AFS.APC1 = M
Title V Permits AFS.APC1 = V
SIP AFS.APC1=0
SIP FederalJurisdiction AFS.APC1 = 1
Non-Federally Reportable AFS.APC1 = 3
CFC Tracking AFS.APC1=4
10-36 IDEA User's Guide February 29, 1996
-------
PSD AFS.APC1 = 6
NSR AFS.APC1 = 7
NESHAP AFS.APC1 = 8
NSPS AFS.APC1 = 9
LINE?
Plant Historical Compliance Status
QTR/FY The quarter and fiscal year of the plant compliance status to the right.
(AFS.HDT1)
Plant Compliance Status Indicator of AIR Program compliance/noncompliance for
the previous eight quarters, generated to reflect the worst-case compliance
status of any pollutant regulated by the AIR Program. (Derived from
AFS.SCH1, which takes the same values as AFS.DCAP. See the list of
values for Pollutant Compliance Status for a list of possible entries here.)
LINES
Pollutant 5-position code identifying a pollutant applicable to an AIR Program.
(AFS.PLAP)
Note
Type TEXT AFS.PLAP at the Command prompt to see a list of pos-
sible values and their translations.
Pollutant Compliance Status Code indicating pollutant conpliance/noncompliance.
(AFS.DCAP)
0 Unknown Compliance Status
1 In Violation - No Schedule
2 In Compliance - Source Test
3 In Compliance - Inspection
4 In Compliance - Certification
5 Meeting Compliance Schedule
6 In Violation - Not Meeting Schedule
7 In Violation - Unknown with Regard to Schedule
8 No Applicable State Regulation
9 In Compliance - Shut Down
Chapter 10, IDEA Standard Reports 10-37
-------
A Unknown with Regard to Procedural Compliance
B In Violation with Regard to both Emissions and Procedural Compliance
C In Compliance with Procedural Requirements
M In Compliance - GEMS
W In Violation with Regard to Procedural Compliance
Y Unknown with Regard to both Emissions and Procedural Compliance
*
Pollutant Classification Code indicating individual criterion pollutant classification per
Alabama Power Decision "Major Source" definition. (AFS.DATT)
AQCR attain/Nonattain Status Code indicating whether a plant emits a criterion
pollutant for which its Air Quality Control Region is non-attainment.
(AFS.DCAP)
A Attainment Area for Given Pollutant
N Non-attainment for Primary and Secondary Pollutant Standards for a Given
Pollutant
1 Non-attainment for Primary SO2 Standards
2 Non-attainment for Secondary PT (Total Particulate Matter) or SO2 Standards
U Unclassified
LINE 9
National Actions Description Description of a compliance or enforcement action taken
at the plant and attributed to the AIR Program. (AFS.ANT1 Table Value)
Note
Type TEXT AFS.ANT1 at the Command prompt to see a list of pos-
sible values and their translations.
Date Achieved The date that the National Action occurred. (AFS.DTA1)
Penalty Amount The dollar amount of a penalty associated with a National Action
Type enforcement action. (AFS.PAM1)
LINEs 10 - 12
AFS Report 1A Summary: seepage 10-4 in Section 10.1.1, Report 1A for detailed
information on these fields.
10-38 IDEA User's Guide February 29, 1996
-------
10.1.2.2 CER (CERCLIS) Report IB Elements
CERCLA Information System(CERCLIS) Summary
1. EPA ID. Number: IAD005270160 Site Name: ALUMINUM COMPANY OF AMERI Address: HWY 67
2. City: RIVERDALE County: SCOTT state: IA Site/Spill Id: 07E5
3. NPL Status: N Proposed NPL Update: 00 Final NPL Update: 00
4. Federal Facility?: N Ownership Indicator: PR Site/Spill Category: M Site Classification:
5. Operable
Unit
00
Operable
Unit
01
Event
DISCOVERY
PRELIMINARY ASSESSMENT
SCREENING SITE INSPECTION
REMOVAL ACTION
ADMINISTRATIVE RECORD
Event
REMEDIAL INVESTIGATION
ADMINISTRATIVE RECORD
REMEDIAL INVESTIGATION
Lead
F
F
F
RP
F
Lead
RP
F
RP
Take Event
Over Plan.
Status
P
P
P
P
Take Event
Over Plan.
Status
P
P
Curr.
Plan.
Start
90/4
94/4
Curr.
Plan.
Start
86/4
99/4
90/2
Actual
Start
Date
07/19/90
Actual
Start
Date
08/14/86
01/09/90
Curr.
Plan.
Comp.
87/2
89/4
95/4
,99/4
Curr.
Plan.
99/4
99/4
99/4
Actual
Completion
Date
06/01/83
01/08/87
07/31/89
Actual
Completion
Date
., Remedy Enforcement Enforcement
Start Completion Compliance Operable Sought Financial Financial
6. Enforcement Activity Lead Date Date Code/GType Unit Achieved Type Amount
UNL-ORDR01
RVL-NEG 01
FE 08/18/94
FE 08/18/94 08/18/94
CERCLIS Overall Summary
Y UA
RN
00
RV1
$855,000
7. CERCLIS Site Name: ALUMINUM COMPANY OF AMERI Cal Year 1990 1991 1992 1993
8. NPL Status: N No. Admin. Actions: 1000
9. Site Classification: No. Judic. Actions: 0000
Figure 10-17. CER (CERCLIS) Report IB Elements
LINE 1
EPA ID. Number Site-unique EPA identifier. (CER.0101)
Site Name Name of the site. (CER.0104)
Address Site street address. (CER.0110)
LINE 2
City Site city name. (CER.0111)
Chapter 10. IDEA Standard Reports
10-39
-------
County Site county name. (CER.0120)
State Site Postal State Abbreviation. (CER.0002)
Site/Spill Id Site or spill identification number. (CER.0315)
LINES
NPL Status Indicator that categorizes a site's NPL status. (CER.0305)
D Deleted from the final NPL
F ' Currently on the final NPL
N Not on NPL
O Not valid site of incident
P Proposed for NPL
R Removed from proposed NPL
S Pre-proposal site
Proposed NPL Update The number of the National Priorities List update on which
the site was proposed. (CER.0308)
Final NPL Update The number of the National Priorities List update on which the
site was made final. (CER.0309)
LINE 4
Federal Faculty Code that indicates whether or not the site or incident is a federal
facility. (CER.0135)
D Status undetermined
N Not a federal facility
Y Federal facility
Ownership Indicator Code that indicates the current ownership status of the site or
incident. (CER.0136)
CO County owned
DI District owned
FF Federally owned
IL Indian lands
MN Municipality
10-40 IDEA User's Guide February 29, 1996
-------
MX
OH
PR
ST
UN
Mixed ownership
Other
Private
State owned
Unknown
Site/Spill Category The overall physical classification of the site or spill. (CER.0137)
A
B
C
D
F
G
H
I
J
L
M
N
0
P
R
T
V
w
Abandoned
Chemical plant
City contamination
Dioxin
Federal facility
Groundwater
Housing area/farm
Industrial waste treatment
Inorganic waste
Landfill
Manufacturing plant
Military related
Other
Pure lagoons
Radioactive site
Mines/Tailings
Waterways/creeks/rivers
Wells
Site Classification Code which identifies the overall programmatic classification for all
NPL sites as determined by the region after the completion of a PRP
search. (CER.0226)
F Fund lead
FE Federal enforcement
ND No determination
NG Fund lead negotiation
SE State enforcement
LINE 5
Operable Unit A designation for the operable unit at which events are occurring
(CER.1101)
Chapter 10. IDEA Standard Reports 10-41
-------
Event Name of a specific response, non-response (generic), or support event
within the pre-remedial, remedial, removal and community relations com-
ponents of the Superfund Program. (CER.2104)
Lead Code which identifies the organization with primary responsibility for the
event. (CER.2117)
CG Coast Guard
EP EPA in-house
F EPA fond-financed
FE Federal enforcement
FF Federal facilities
MR Mixed Funding Federal/RP
PS PRP Response under State
RP Responsible Party
S State, fund financed
SE State Enforcement
SN State, No fond money
SR PRP lead under state
TR Tribal lead, fond-financed
Take Over A flag which identifies those events which are or have been taken over.
(CER.2114)
Event Plan. Status This field designates an event as a primary or alternate targeted
item for the purpose of meeting a Strategic Planning and Management
System (SPMS) target. (CER/2110)
A Alternate
P Primary
Q Delayed
S Project suspended
Curr. Plan. Start Current planned start date for the event (fiscal year/quarter).
(CER.2132)
Actual Start Date The actual start date for the event. (CER.2140)
Curr. Plan. Comp. Current planned completion date for the event (fiscal
year/quarter). (CER.2133)
Actual Completion Date The actual completion date for the event. (CER.2141)
10-42 IDEA User's Guide February 29, 1996
-------
LINE 6
Enforcement Activity The abbreviated enforcement activity name. (CER.1704) See
the list of values for CER.1732, under Activity Compliance GType, for a
list of the entire enforcement activity names.
Lead The programmatic lead for a particular enforcement activity. (CER.1707)
FE Federal Enforcement
SE State Enforcement
Actual Start Date Date of transmittal of memorandum to headquarters for the start
date of an enforcement activities. (CER.1716)
Actual Completion Date The actual date when an enforcement activity is completed.
(CER.1717)
Activity Compliance Code The current status of RP regarding compliance with the
overall terms of an administrative order, settlement, or judgment.
(CER.1726)
A Converted to AC
C Close Out For Work Completed Under SETT
D No Determination
J Major Violations
N No Response
R Minor Violations
V Converted to CD
Y PRP In Compliance
Activity Compliance GType Code identifying an enforcement activity (e.g., response
negotiations, settlement actions, or litigation) performed by the federal
enforcement program or a state enforcement program. (CER.1732)
AC Admin Order On Consent
AN RD/RA Negotiations
AV Admin/Voluntary Cost Recovery
CA Consent Agreement
CB Claim In Bankruptcy Proceedings
CC CERCLA Criminal Litigation
CD Consent Decree
CL Section 106 & 107 Litigation
DD Cost Recovery Decision Document No Sue
Chapter 10. IDEA Standard Reports 10-43
-------
DL Issue Demand Letters (H)
FA Memorandum Of Agreement (H)
FC Federal Compliance Agmt (H)
FI Federal Interagency Agmt (H)
FN RI/FS Negotiation
FU Federal Memo of Understanding (H)
IL Issue Req Letters (H)
IN IAG Negotiations
JG Judicial/Civil Judgement
LP Federal Lien on PRP Properly
NB Non-Binding Allocation of Resp
NE Cost Recovery Negotiation
NI Issue Notice Letters (H)
NS NPL RP Search
NW Issue Notice of S122 Waiver (H)
PC Preparation of Cost Docm Package
PI Preliminary Injunction
RN Removal Negotiations
RP Non-NPL PRP Search
RR RCRA Order
SD State Consent Decree
SF Section 104(E) Ref Litigation
SN Issue Special Notice (H)
SO State Order
SV Section 107 Litigation
SX Section 106 Litigation
TE Temporary Restraining Order
UA Unilateral Admin Order
Remedy Operable Unit Remedy operable unit. (CER.2733)
Remedy Sought Achieved Remedy Sought Achieved. (CER.2731)
CO RI/FS
DA De Minimus Cash Out For Remedial Action
DC Cease and Desist
DD De Minimus Cash Out For Remedial Design
DE Document Exchange
DM De Minimus Cash Out For Removal
DO De Minimus Cash Out For RI/FS
DU De Minimus Cash Out For Unspecified Site Work
ER Expedited Response Action
FS Feasibility Study
10-44 IDEA User's Guide February 29, 1996
-------
IM
IN
LP
LR
MA
MD
MM
MO
NA
ND
NM
NO
NU
OH
OM
PI
PR
RA
RD
RI
RV
SE
TO
TR
TS
VA
Initial Remedial Measure (H)
Interest
Lien On Property
Long Term Response
Mixed Funding/Preauth. For Remedial Action
Mixed Funding/Preauth. For Remedial Design
Mixed Funding/Preauth. For Removal
Mixed Funding/Preauth. For RI/FS
Non-De Minimus Cash Out For Remedial Action
Non-De Minimus Cash Out For Remedial Design
Non-De Minimus Cash Out For Removal
Non-De Minimus Cash Out For RI/FS
Non-De Minimus Cash Out For Unspecified Site
Other
Operation/Maintenance
Preliminary Injunction
Premium
Remedial Action
Remedial Design
Remedial Investigation
Removal Action
Site Access
Temporary Restraining Order
Temporary Relocation ;
Treatability Studies
Cost Recovery of RA
Work
VC Cost Recovery of, Other
VD Cost Recovery of RD
VM Cost Recovery of Removal Action
VO Cost Recovery of RI/FS
VS Cost Recovery of Oversight
Enforcement Financial Type A planned and/or actual financial transaction that is
associated with activities outlined in enforcement activity type. (CER.2903)
Enforcement Financial Amount The dollar amount associated with each financial
transaction coded in enforcement financial type. (CER.2907)
LINES 7 - 9
CERCLIS Report 1A Summary: seepage 10-7 in Section 10.1.1, Report IA for
detailed information on these fields.
Chapter 10. IDEA Standard Reports 10-45
-------
10.1.2.3 DCK (Civil Docket) Report IB Elements
Civil Enforcement Docket Summary
1. Case Name: NORMAN PARKER/MOWBRAY ENGINEER Case Number: 04-86-0034
2. Type Case: BNK HQ Division:
3. Law/Section: CERCLA /107 Pollutant(s): PCB Violation(s):
4. Overall Status: C
5. Violation Detected: Case Received at HQ: Case to USA : Case Closed : 1989/01
6. Regn Atty Assigned: HQ Review : Case Filed : 1986/06 Case Returned to Region:
7. Case Referred: Case to DOJ : Case Concluded: 1989/01 Case Rereferred by Region:
8. Civil Docket Case Name Case Number Type Case Law Ovrall Sta. Initiated To DOO Filed Concluded
NORMAN PARKER/MOWBRAY EN6INEER04-86-0034 BNK CERCLA CASE CLOSED 1986/06 1989/01
Figure 10-18. DCK (Civil Docket) Report IB Elements
LINE1
Case Name The name of the case as referenced in the complaint. (DCK.CSNM)
Case Number An EPA-assigned case tracking number. (DCK.CSNO)
LINE 2
Type Case A code indicating the type of enforcement case, e.g., civil or administra-
tive. (DCK.TYPC)
Most commonly occurring codes:
10-46 IDEA User's Guide
February 29, 1996
-------
BNK Bankruptcy
CIT Citizen Case
CIV Civil .
FAD Federal Facility Agreements
MIS Misc Proceedings
PRN Pre-referral Negotiation
SDWANOV SDWA Notice of Violation
TSCANON TSCA Notice of Noncornpliance
104E5A CERCLA 104E5A AO For Access And/Or Info
106 CERCLA 106 (AO) For Coimp And Penally
113 CAA 113 Notice of Violation
113A CAA 113A Admin Order (AO)
113D CAA 113D Delayed Compliance Order
113D1 CAA 113D1 Administrative Penalty Case
114 CAA 114 Information Request Letters
122/104 Adm. Order For Investigative Studies
14 FIFRA 14 (AO) For Comp and Penalties
1414G2 . SDWA 1414 PWS Comp Order 1st Time
1414G3 SDWA 1414 PWS (AO) For Compliance
HQ Division A code indicating the EPA Headquarters Division responsible for a case.
(DCK.HQDV)
AIR Air
WAT Water
CER CERCLA
RCR RCRA
TOX Toxics
CRI Criminal
MOB Mobile (Air)
FFE Federal Facilities
LINE 3
Law/Section The law(s) and section(s) cited in the complaint. (DCK.LAWS +
DCK.SECT)
Pollutant(s) The waste material, substance or chemical involved at the facility in vio-
lation. (DCK.POLL)
Chapter 1C). IDEA Standard Reports
10-47
-------
Violation(s) A code designating the nature of the violation(s). (DCK.VIOT)
Most commonly occurring codes:
AOVIOL Administrative Order Violation
ASB Asbestos
FIFRA Federal Insecticide Fungicide and Rodenticide Act
GFR General Facility Requirements
NESHAP National Emission Standard For Hazardous Air Pollution
NOPRMT Discharge Without A Permit
.NSPS New Source Performance Standard
PCB Polychlorinated Biphenyls
PRETMT Pretreatment
PRMTVL Permit Violation
PWSM/R PWS Monitoring/Reporting
PWSMCL PWS Maximum Containment Level
REP Reporting Violations
SIP State Implementation Plan
UIC UIC/SDWA
LINE 4
Overall Status A code indicating how far the case has progressed. (DCK.OSTA)
c
0
p
s
T
I
2
3
4
5
Case closed
Opened
PRN (pre-referral negotiation)
Returned to Region
Taken
At EPA-HQ
AtDOJ
At US Attorney
Filed in court
Concluded
LINE 5
Violation detected Date violation is detected for the first time. (DCK.CVIO)
Case Received at HQ Date case is received for the time at HQ. (DCK.RCHQ)
Case to USA Date case is referred to US Attorney's Office. (DCK.CUSA)
10-48 IDEA User's Guide
February 29,1996
-------
Case Closed Date case is closed. (DCK.CLSD)
LINE 6
Regn Atty Assigned Regional attorney assigned. (DCK.CRAA)
HQ Review Date case is reviewed by HQ. (DCK.HQRV)
Case Filed Date case is filed in District Court. (DCK.CFLD)
Case Returned to Region Date case is returned to Regional Office. (DCK.CRET)
LINE 7
Case Referred Date case is referred to HQ. (DCK.CREF)
Case to DOJ Date case is referred to US Department of Justice. (DCK.CDOJ)
Case Concluded Date case is concluded. (DCK.CCNC)
Case Rereferred by Region Date case is rereferred to HQ by Regional Office.
(DCK.CRRE)
LINE 8
Docket Report 1A Summary: see page 10-9 in Section JO. 1.1, Report 1A for detailed
information on these fields.
Chapter 10. IDEA Standard Reports 10-49
-------
10.1.2.4 DUN (Dun & Bradstreet) Report IB Elements
Duns Summary
DUNS Number: 1307792 Ult: 1307792 Status: Headquarters Subsidiary? No
Business: Armstrong World Industries Hierarchy Level: 1 Started in 1860
Address: W Liberty Charlotte St Sales Volume: $ 2752700000 Hfg? Yes
Lancaster PA 17604 Total Employees: 20600
SIC Code(s): 5023 3253 3296 Empl. On Site: 4500
Figure 10-19. DUN (Dun & Bradstreet) Report IB Elements
LINE1
DUNS Number A Data Universal Numbering System (DUNS) random numeric serial
number. (DUN.DCNO)
Ult Ultimate Number — the DUNS number of the topmost firm of a "Family-
Tree" group of companies. The field will either contain data or blanks.
(DUN.ULNO)
Ultimate records show a repetition of their own DUNS number. Their
DUNS number is repeated in this field so that a common sort and/or
match area is available for headquarters and branch records.
Status Indicates the status of the business. (DUN.STAT)
NOT HQ/BRANCH DUN.STAT = 0
HEADQUARTERS DUN.STAT = 1
BRANCH DUN.STAT = 2
Subsidiary?. Indicates whether the business is a subsidiary or not. (DUN.SUBI)
Yes DUN.SUBI = 3
No DUN.SUBI = 0
LINE 2
Business The correct legal name of the business. (DUN.DNME)
Hierarchy Level A hierarchy indicator with possible values 1-4. (DUN.HIER)
10-50 IDEA User's Guide February 29, 1996
-------
Started in Gives the year that the business started. (DUN.YRST) This field appears
only when facility status is either NOT HQ/BRANCH or HEADQUAR-
TERS.
LINE 3
Address The street address, city, state and zip code of the business. (DUN.DSTR,
DUN.DCTY, DUN.DSTA, and DUN.DZIP)
Sales Volume The annual sales volume of the business in dollars. (DUN. SALESV)
This field appears only when facility status is either NOT HQ/BRANCH or
HEADQUARTERS.
Mfg? Whether manufacturing is done at this address.(DUN.MFGI)
Yes DUN.MFGI = 0
No DUN.MFGI = 1
LINE 4
Total Employees The total number of employees employed by the business.
(DUN.EMPLTOT) This field appears only when facility status is either
NOT HQ/BRANCH or HEADQUARTERS.
LINE 5
SIC Code(s) The Standard Industrial Classification (SIC) Code system categorizes
business establishments based upon the type of activity done by that estab-
lishment at that location. Each SIC consists of a four-digit code, defined
by the US Government. (DUN.SIC1, DUN.SIC2, DUN.SIC3)
On Site The total number of employees employed at this address.
(DUN.EMPLHER)
Chapter 10, IDEA Standard Reports 10-51
-------
10.1.2.5 ERN (ERNS) Report IB Elements
Eaergency Response Notification
1 EMS Discharger Id: TXB0266633
2 Discharger
EXXON CO USA
1288 SMITH ST
HOUSTON
TANK TRUCK / OVERTURNED
Source:
Transport Hade: Highway
Region:
County:
Related
Report: GBB266633
86 Date: 85/19/92
TX 77Z19
FORT BEND
Initial Report
Systen (ERNS) Hazard
Host Up-to-date
Spill Date: 95/19/92 Occurred
KINGSTON
STATE HHY 3
VACUUM TRUCK
MA
BETWEEN EX 11 S EX18
ON SCENE
D
us Substance Release
met reporting requ
Spill Region: 61
aths: Injurit
reraents
Region 1st Notified: Latitude:
County: Longitude:
s: 1 Damages: $16889
IB. Quantity Material Spilled CHRIS code
10378.88 Ibs 19939 GASOLINE: AUTOMOTIVE (4.23G PB/G GAT
11. Hcdla: Lend — SOU
12. Cause: EqulpMnt Failure
13. INJURED PERSON MAS ADMITTED TO HOSPITAL
ERNS OVERALL SUMMARY —
Quantity Material Spilled
14. ERNS Discharger Id: TXSI26B633
15. Discharger: EXXON CO USA
II. Deaths: Injuries: 1
Spills — last five years:
Most recent: 95/19/92
Evacuations: Damages:
10-20. ERN (ERNS) Report IB Elements
LINE 1
ERNS Discharger ID A unique number for the ERNS Discharger (ERN.OWNID).
IDEA derives this number from the ERNS Discharger ID (ERN.DID),
DOWNID (ERN.DOWNID), and the OWNID (ERN.OWNID) fields.
The Discharger State abbreviation (ERN. STATE) prefixes this number.
(ERN.STATE)
Report A unique sequential number assigned to each report when entered into
ERNS. (ERN.DOWNID)
Initial Report The appearance of this title indicates that the information presented is
the initial notification to ERNS. As such, the report will contain initial
accounts of releases, made during or immediately after an incident, when
exact details are often unknown. There may be multiple reports for a
single incident. (This occurs when the caller makes a second report to
update original data, or a private observer reports a release that has
already been reported by the facility.) (ERN.INIT)
Most Up-to-date The appearance of this title indicated that the initial notification
data has been updated. Note: IDEA total facilities selected are calculated
on this field. (ERN.MUD)
10-52 IDEA User's Guide
February 29, 1996
-------
met reporting requirements Indicates if the spill met the reporting requirements of the
DOT'S Office of Hazardous Materials Safety (OHMS) for all transporta-
tion related reports. Other values for this field are: ENFORCEMENT
ACTION REQUIRED and CANCELLATION LETTER FILED.
(ERN.RPTBL)
LINE 2 .
Discharger Title line for the organization considered to be the PRP (potentially
responsible party). (ERN.DORG)
Region EPA Region in which the Discharger is located. (ERN.DREGION)
Date The date of the notification report. (ERN.DTRPT)
SpiU Date The date of the spill. (ERN.DTSPI)
Occurred A description indicating if the release occurred, was planned, or was discov-
ered. (ERN.DTG)
Spill Region EPA Region in which the spill is located. (ERN.SPLREGN)
Region 1st Notified EPA Region notified of the spill. (ERN. REGION)
Latitude The geographic location of the release as expressed in degrees, minutes,
seconds latitude. (ERN.LAT)
LINE 3
Name of the Discharger organization considered to be responsible. (ERN.DORG)
The spill site city, state and zip code. (ERN.SCITY) (ERN.SST) (ERN.SZIP)
County The county where the spill occurred. (ERN.SCOUNTY)
Longitude The geographic location of the release as expressed in degrees, minutes,
seconds longitude. (ERN. LONG)
!
LINE 4
Chapter 10. IDEA Standard Reports 10-53
-------
The street address for the Discharger. (ERN.DADD)
The spill miscellaneous location. (ERN.LTEXT)
LINES
The city, state, and zip code for the discharger. (ERN.DCITY) (ERN.STATE)
(ERN.DZIP)
Description of response actions taken as a result of a notification. (ERN.ATEXT)
LINE 6
County The county where the PRP is located. (ERN.DCOUNTY)
LINE 7
Descriptive text offering information on the release. (ERN.DTEXT)
LINE 8
Source A description of the source of the release. (ERN. SOURCE)
AA
AB
AC
BA
BB
BC
BD
BE
BF
CA
CB
DA
DB
DC
DD
Dry Cargo
Liquid Cargo
Vehicle Fuel Tank
Pick Up
Platform
Van or Panel
Dump
Tractor Trailer
Tank
Airplane Fuel Tank
Airplane Cargo
Locomotive Fuel Tank
Tank Car
Flat Car
Hopper Car
10-54 IDEA User's Guide February 29, 1996
-------
DE
DF
DG
EA
EB
EC
FA
FB
FC
FD
FE
FF
FG
FH
GA
GB
GC
GD
GE
GF
GG
GH
GI
GJ
GK
GL
GM
HA
HB
HC
HD
HE
IA
IB
1C
ID
JA
Refrigerator Car
Dry Cargo
Liquid Cargo
Dry Cargo
Liquid Cargo
Vessel Fuel Tank
Private Boat
Commercial
Tow Board
Tug Boat
Roro
Containerized
Tanker
Barge
Plant
Distributor
Plant Piping .
Production
Refining
Power Plant
Hazardous Waste Site
Transformer
Railroad Yard
Consumer
Underground Storage Tank
Gasoline Station
Water Treatment
Lines
Pumping Station
Inlet
Outlet
Valve or Fitting
Production
Storage
Transport (to Shore Only)
Equipment
Air Release
LINE 9
Transport Mode The type of transportation involved with the release. (ERN.MODE)
Chapter 10. IDEA Standard Reports 10-55
-------
A Air Transport Related
F Fixed Fatality
G Rail/Highway Crossing
H Highway Related
M Marine- released from a marine vessel to inland waterway
O Offshore - spilled off the coast
P ' Pipeline Related
R Railroad
S Underground Storage Tank
T Above Ground Storage Tank
U Unknown (EPA Regions)
V Marine Vessel
Deaths The number of fatalities resulting from the release. These fatalities may
either be the result of the accident causing the release, or from exposure to
the substance released. (ERN.DEATHS)
Injuries The number of injuries resulting from the release. These injuries may either
be the result of the accident causing the release, or from exposure to the
substance released. (ERN.INJS)
Damages The estimated dollar amount of property damage resulting from releases for
this Discharger (ERN.PROPDMG) and/or an indication that damages
occurred (ERN.DAMAGES). Note: If the amount of damages is not
present in the ERNS data, but ERN.DAMAGES = Y, this field will appear
as PROPERTY DAMAGE.
LINE 10
Quantity The total quantity of the substance released, converted into pounds,
(ERN.LBS) or, if this is not available, ERN.QTYSP (the quantity) and
ERN.UNITSP (the units), will be printed out.
Material Spilled National Transportation System Center Chemical ID
(ERN.CHEMID) and the name of the substance or substances released.
(ERN.MATSP)
CHRIS Code The Chemical Hazards Response Information System (CHRIS) code of
the substance released. (ERN.CHRIS)
Quantity The quantity of the substance released, in water (ERN.QUAW) , with units
(ERN.UNITSW).
10-56 IDEA User's Guide February 29, 1996
-------
Material Spilled National Transportation System Center Chemical ID
(ERN.CHEMID) and the name of the substance or substances released.
(ERN.MATSP)
CHRIS Code The Chemical Hazards Response Information System (CHRIS) code of
the substance released. (ERN.CHRIS)
LINE 11
Media Indicates if the release affected air (ERN.MAIR), land (ERN.LAND),
water (ERN.MWATER), groundwater (ERN.MGRDWTR), fixed facility
(ERN.MFAC), or other (ERN.MOTH). Immediately following this infor-
mation, the medium to which the substance(s) were released.
(ERN.MEDCODE)
AA
AB
AC
AD
BA
BB
BC
BD
BE
CA
CB
CC
CD
CE
CF
CG
CH
CI
CJ
CK
CL
CM
DA
DB
EA
EB
EC
ED
Explosion
Evaporation
Sublimation
Spray
Ground
Roadway
Parking Lot
Concrete
Beach Water
Stream
River
Sewer
Lake
Pond
Ditch
Reservoir
Canal
Ocean
Estuary
Inlet
Creek
Irrigation
Well
Aquifer
Within Building
Within Processing System
On Concrete or Asphalt
On Ground
Chapter 10. IDEA Standard Reports 10-57
-------
LINE 12
Cause Indicates if the cause of the incident was a Transport Accident
(ERN.TRANS), Equipment Failure (ERN.EQUIP), Operator Error
(ERN.OPERR), Natural Phenomenon (ERN.NATURAL), Dumping
(ERN.DUMPING), Cause Unknown (ERN.UNKNOWN), or Other Cause
(ERN.COTH). Immediately following this information, the cause of the
incident is listed. (ERN.CAUSE)
AA
AB
AC
AD
AE
AF
AG
AH
BA
BB
BC
BD
BE
BF
BG
BH
BI
BJ
BK
BL
BM
BN
BO
BP
BQ
BR
BS
BT
BU
BV
CA
CB
CC
CD
Overturning
Collision
Fire
Explosion
Grounding
Sinking
Derailment
Pipeline Blowout
Broken Containers
Tank or Container
Valve
Flange
Hose
Fitting
Alarm
Automatic Shutoff
Dike
Pump
Hull
Well Head
Flow Line
Pipeline
Manifold
Structural
Weld
Container Leak
Lact Upset
Treater Upset
Power Failure
Power Oil Line
Improper Maintenance
Improper Operation
Improper Hose Connection
Improper Secured Flange
10-58 IDEA User's Guide
February 29, 1996
-------
CE
CF
CG
CH
CI
CJ
CK
DA
DB
DC
DD
DE
DF
EA
EB
FA
GA
GB
Improper Storage/Handling
Improper Design
Improper Training
Improper Communication
Improper Valve Handling
Overflow
Failure to Shutdown
Flooding
Freezing
Wind
Natural Seepage
Rain or Snow
Lightning
Improper Disposal
Deliberate
Unknown
Vandalism
Sabotage
LINE 13
Miscellaneous information on the release. (ERN.MTEXT)
LINEs 14-16
ERNS Report 1A Summary: see Figure 10-6 in Section 10.1.1, Report 1A for detailed
information on these fields.
Chapter 10. IDEA Standard Reports 10-59
-------
10.1.2.6 FFI (FFIS) Report IB Elements
1. FFID: IA-690319303 Name: USCG DUBUQUE MOORINGS
Z. Medium: CU Status:
3. Progress Code: 5 Compliance Status: PSDF Pollutant: SPCC Project Assessment: L
4. Federal Facility Id: IA-6903193Q3 Name: USCG DUBUQUE MOORINGS
Addr: 60 EAST FIRST ST.,
DUBUQUE
Addr: 60 EAST FIRST ST.
DUBUQUE
Figure 10-21. FFI (FFIS) Report IB Elements
LINE1
Federal Facility Id Federal facility ID number. (FFI.FFID)
Name Facility name. (FFI.FNAM)
Addr Facility street address and city name. (FFI.ADDR + FFI.CITY)
LINE 2
Medium Environmental medium. (FFI.PMED)
Status Facility status. (FFI.STFL)
LINES
Progress Code Facility progress code. (FFI.PRGC)
Compliance Status Compliance status. (FFI.CPST)
Pollutant Pollutant. (FFI.POLC)
Project Assessment Assessment of the project. (FFI.EPPA)
10-60 IDEA User's Guide
February 29, 1996
-------
10.1.2'.7 FIN (FINDS) Report IB Elements
1. FINDS Id: AL568003Q926 Fac. Name: EASTERN ENVIRONMENTAL City: MONTGOMERY State: AL
2. Address: 1504 A AVE Zip: 36114 Lat: Long:
Figure 10-22. FIN (FINDS) Report IB Elements
LINE 1
FINDS Id EPA ID Number. (FIN.EPID)
Fac. Name Facility Name. (FIN.FNME)
City Facility Location City. (FIN.FCTY)
State Facility Location State. (FIN. STAT)
LINE 2
Address Facility Street Address. (FIN.STR1)
Zip Facility ZIP Code. (FIN.FZIP)
Lat Latitude in Degrees. (FIN.LATD)
Long Longitude in Degrees. (FIN. LONG)
. Chapter 10. IDEA Standard Reports 10-61
-------
10.1.2.8 LSI (Contractor Listing Docket) Report IB Elements
1. LSI Case Number: 01-88-LQ82 Case Name: BIG APPLE WRECKING CORPORATION , INC., BRONX, NEW YORK
2. Case Type: Case Status: Withdrawn.by Recommending Person - Listi
3. Basis for Listing: CAA/Complaint Filed
CAA/Federal Court Order
CAA/Violation of Administrative Order
4. HDQtrs. Division: AIR Referred By: 01
5. Law(s)/Section(s) Violated: CAA/ 112
6. Pollutants Involved: ASBESTOS
7. Relief(s) Sought: Corrective Action
Future Compliance
8. Case Opened: 05/24/88 Case Initiated: 05/26/88 Case Listed:
9. HQ Attorney: DOHIKE, J. Regional Attorney: CALLAH, A.
Case Closed: 11/08/91
Figure 10-23. LST (Contractor Listing Docket) Report IB Elements
LINE1
LST Case Number Case Number associated with facility. (LST.CSNO)
Case Name Name of the case involving the facility. (LST.CSNM)
LINE 2
Case Type Type of case. (LST.TYPC)
Case Status Status of the case. (LST.CCST)
LINE 3
Basis for Listing Basis for listing the case. (LST.BLAW + LST.BACT)
LINE 4
HDQtrs Division The EPA headquarters division responsible for the case.
(LST.HQDV)
10-62 IDEA User's Guide
February 29, 1996
-------
AIR Air
CRI Criminal
WAT Water
MOB Mobile (Air)
Referred By The region that referred the case to EPA headquarters, (from
LST.CSNO)
LINE 5
Law(s)/Section(s) The law(s) and section(s) by whose authority a contractor is listed
(LST.LAW and LST.SECT)
LINE 6
Pollutant(s) The substance(s) that are causing the facility to be in violation.
(LST.POLL)
LINE 7
Relief(s) Sought What type of action is being sought from the violator. (LST.RLFS)
Corrective Action
Future Compliance
LINE 8
Case Opened Date the case was opened. (LST.DCOP)
Case Initiated Date the case was initiated. (LST.DCIN)
Case Listed Date the case was listed. (LST.DCLS)
Case Closed Date the case was closed. (LST.DCCL)
LINE 9
HQ Attorney Attorney at EPA Headquarters associated with the case. (LST.HQNM)
Chapter 10. IDEA Standard Reports 10-63
-------
Regional Attorney Attorney in an EPA region who is associated with the case.
(LST.RGNM)
10-64 IDEA User's Guide
February 29, 1996
-------
10.1.2.9 NCD (NCDB) Report IB Elements
National Compliance Data Base (NCDB) Summary Page
1. NCDBID: I07#1987Q62401668 Region: 07 Respondent name: ALUMINUM CO OF AMERICA
2. Facility Function: DP Pesticide Estab Number:
3. Schools Inspected: Federal Facility: N SIC Codes : 3361
4. Parent Co. Name : ALUMINUM CO OF AMERICA
5. Investigation
Number
DQ7#07-88-424
Violation
Legis Detected Violation
T CC 6PS
Date of Proposed Final # of EBE Closed/Wdrawn
SNC Action Penalty Penalty Terms Date (C/W)
YES 19880406 $34,000 $17,000 19881025/C
Figure 10-24. NCD (NCDB) Report IB Elements
LINE 1
NCDBID NCDB identifier. (NCD.NCDBID)
Region Code designating EPA Regional Office, (NCD.REGION)
Respondent(/Site/Importer) Name The name of an inspection site/facility.
(NCD.NAME with one of NCD.NAMETYP = RESPOND, SITE, or
IMPORT)
LINE 2
Facility Function A code indicating the function performed by an inspected facility,
e.g., manufacturer, producer. (NCD.FACILIT)
BK Broker
CA Certified Commercial Applicator ',
CV Conveyor
DA Permitted Disposer - Alternative Methods
DH Permitted Disposer - High Effic Boilers
DI Permitted Disposer - Incinerator
DL Dealer
DM Permitted Disposer - Dredge/Sludge Mater
DP Disposer
DR Permitted Disposer - Research/Develop
DS Drift Site
Chapter 10. IDEA Standard Reports
10-65
-------
DT
LB
MI
MK
MN
OP
PA
PC
PD
PS
PT
RG
RU
SA
TS
UA
US
Distributor
Laboratory
Manufacturer /Importer
Marketplace
Manufacturer
Other Parties
Certified Private Applicator
Processor
Producer
Secondary Processor
Port Of Entry
Registrant
RUP Dealer
Supervised Applicator
Target Site
Uncertified Applicator
User
Pesticide Estab Number The EPA registration number identifying pesticide producing
establishments. (NCD.EPESTAB)
LINES
Schools Inspected The number of schools inspected within a Local Education Agency
(LEA) that were inspected. (NCD.SCHOOLS)
Federal Facility N/Y indicator that inspection site is a federal facility.
(NCD.FEDFAC)
SIC Codes Up to six 4-digit Standard Industrial Classification Codes.
(NCD.SICLIST)
Parent Co. Name Name of the parent company of the inspected site. (NCD.NAME
when NCD.NAMETYP = PARENT)
LINE 4
Investigation Number Inspection identification number. (NCD.ACTNID)
Legis The legislation/statute code. (NCD.LEGISLA)
10-66 IDEA User's Guide February 29, 1996
-------
T
F
E
TSCA
FIFRA
EPCRA
Violation Detected The type of the action taken in response to a violation.
(NCD.ACTNTYP or NCD.IACTNTY)
ADL Advertising/Advising Letter
APN AHERA Pilot NON Program
CC Civil Admin Complaint
CCR Civil Admin Referred To DOJ
CIN Criminal Injunction
CRM Criminal Action
CSP Civil Subpoena
CSZ Civil Seizure
FNN Federal Notice Of Noncompliance
FNS Significant Federal NON - Major Action "
FRE Formal Recall
IRE Informal Recall
NOD Notice Of Detention
NOI Notice Of Intent To Terminate Estab Reg"
NON Notice Of Noncompliance
PPR PCB Permit Revocation
PPS PCB Permit Suspension
RAC D,S,M,R Of Application Certificate "
SSU Stop Sale, Use, Or Removal Order *
TER Termination Of Establishment Reg *
14W 14 (A) (2) Notice Of Warning
9WR 9 (C) (3) Notice Of Warning
Violation The type(s) of violations (up to six) cited in an enforcement action.
(NCD.VIOCDE or NCD.IVIOCDE)
Note
Type TEXT NCD.VIOCODS at the Command prompt to see a list of
possible values and their translations.
SNC Indicator of violation "significant noncompliance" status. (NCD.SNC or
NCD.ISNC)
Date of Action The date of the minor action issued. (NCD.AOISSUE,
NCD.MAISSUE, NCD.IAOISSU, or NCD.IMAISSU)
Chapter 10. IDEA Standard Reports
10-67
-------
Proposed Penalty The proposed penalty assessed in the enforcement action.
(NCD.PROPENL or NCD.IPROPEN)
Final Penalty The final penalty amount assessed for a major action.
(NCD.FNLPENL or NCD.IFNLPEN)
# of EBE Terms The number of terms under "Settlements with Conditions" which are
"Environmentally Beneficial Expenditures." (NCD.NUMEBES or
NCD.INUMEBE)
Closed/Wdrawn Date (C/W) The date that the major action is closed or withdrawn.
(NCD.CLOSED or NCD.ICLOSED with '/C', or NCD.MAWITHD or
NCD.IMAWITH with '/W')
10-68 IDEA User's Guide
February 29, 1996
-------
10.1.2.10 OSH (OSHA) Report IB Elements
Occupational Safety and Health Administration (OSHA) Inspection Report
1. OSHA Activity Link: NY 2258959
2. Inspection No: 2256959 Opened: 93/96/86 Closed: 96/17/B6 Employees at site: 457 Lost Workday Injury Rate: B.69 Region: 92
3. Name: FORD MOTOR COMPANY - GREEN ISL Health Inspection Partial SIC: 3714 MOTOR VEHICLE PARTS AND ACCESSORIES
4. Site: 75 TIBBITS AVENUE Violations: 2 Serious Violations: 2 Total Penalties-
5. Green Island NY 12831 Optional Info: State 93 7
Corporate/
Abatement Total Violation Penalty Failure Hazard Egregious
7. Violation Level Required Penalties Contested Contested To Abate Level Case Status
19191925 F93 II other 96/86/86 Abatement completed
Cited substance(s): 1591 LEAD, INORGANIC FUMES S DUSTS (AS PB)(PEL)
19191825 F94 I Other 86/86/86
Abatement completed
Cited substance(s): 1591 LEAD, INORGANIC FUMES 8 DUSTS (AS PB)(PEL)
19161825 H62 II Other 96/96/86 Abatement completed
Cited substanca(s): 1591 LEAD, INORGANIC FUMES & OUSTS (AS P8)(PEL)
9. Accident Source of Injury Substance Contributing to Accident
Nonhospitalized injury CHEM LIQUIDS/VAPORS 2466 TOLUENE - SKIN
Nonhospitali zed injury CHEM LIOUIDS/VAPORS 2468 TOLUENE - SKIN
'*•Inspection No:19743276Opened: 96/83/81closed: 87/87/81Employees at site:TsiPLost Workday Injury Rate:ill
Name: FORD MOTOR CO GREEN ISLAND PLA Safety Inspection Comprehensive SIC: 3714 MOTOR VEHICLE PARTS AND ACCESSORIES
Site: 75 TIBBETTS AVE Violations: 1 Serious Violations: 1 Total Penalties-
Green Island NY 121B3
Corporate/
Abatement Total Violation Penalty Failure Hazard Egregious
Violation Level Required Penalties Contested Contested To Abate Level Case status
1919.212 A93 II other 86/29/81 Abatement completed
11. OSHA OVERALL SUMMARY
OSHA Activity LinK: NY 2258959 No inspections - last five years '
Name: FORD MOTOR COMPANY - GREEN ISL
Figure 10-25. OSH (OSHA) Report IB Elements ~
LINE 1
OSHA Activity Link An IDEA derived link between OSHA inspections. Although
every attempt has been made to link inspections of the same facility
together, a single facility may have several Activity Links, due to limita-
tions in the data. (OSH.ESTABNR)
State The state in which the facility is located, used for linking purposes.
(OSH.ESTABST)
LINE 2
Inspection No A unique identifer for the OSHA inspection. (OSH.ACTIVTY)
Opened Date of opening conference or of attempted inspection. (OSH.DTOPEN)
Closed Date the case was closed. (OSH.DTCLOSE) If no value for
OSH.DTCLOSE is present, then either CASE OPEN or CASE CLOSED
will appear here, depending on the value of OSH.STATUS present.
Chapter 10. IDEA Standard Reports 10-69
-------
Employees at site The number of employees at the site of the inspection.
(OSH.SITEMPL)
Lost Workday Injury Rate The lost workday injury rate calculated on this inspection.
(OSH.LWDI)
Region From the first two characters in the reporting office identifier
(OSH.OFFICE)
LINES
Name The name of the establishment. (OSH.ESTAB)
Inspection Category The type of inspection carried out.
Health Inspection OSH.INSPCAT = H
Safety Inspection OSH.INSPCAT=S
Scope of Inspection The scope of the current inspection. (OSH.INSPSCO)
Comprehensive OSH.INSPSCO = A
Partial OSH.INSPSCO = B
Records Only OSH.INSPSCO = C
No-Inspection OSH.INSPSCO = D
SIC The primary Standard Industrial Classification (SIC) Code of the establish-
ment (OSH.SICPRIM)
LINE 4
Site The site address (OSH.SITE)
Violations The number of violations cited on the current inspection. (OSH. VIOLS)
Serious Violations The number of serious violations cited on the current inspection.
(OSH.SRVIOLS)
Total Penalties The total penalties issued on the current inspection. (OSH.AMTPEN)
LINES
10-70 IDEA User's Guide February 29, 1996
-------
City The city in which the site is located, derived from the city code.
(OSH.SITECTY)
State The state in which the site is located. (OSH.SITEST)
Zip The zip code in which the site is located. (OSH.SITEZIP)
LINE 6
Optional Info Originator The optional information originator, if present.
Area Office OSH.OPTTYPE=A
National Office OSH.OPTTYPE = N
Regional Office OSH.OPTTYPE = R
State OSH.OPTTYPE = S
Optional Info Id Code A two character identification code. (OSH.OPTID)
Optional Information The value of OSH.OPTVALU, if present, and a textual trans-
lation, if available for that value.
LINE 7
Violation The standard, regulation, or law violated. (OSH.VIOLATN)
Level The currently determined violation type.(OSH.VCURTYP)
Other OSH.VCURTYP = O
Post Settlement OSH.VCURTYP = P
Repeat OSH.VCURTYP = R
Serious OSH.VCURTYP = S
Unclassified OSH.VCURTYP = U
Willful OSH.VCURTYP = W
Abatement Required The violation abatement date (OSH.VDTABAT)
Total Penalties The sum of current penalty due to this violation (OSH.VCURPEN)
and the FTA (Failure to Abate) penalty assessed. (OSH.VFTA)
Violation Contested An X will appear if the violation was contested. (OSH.VIOLCN)
Chapter 10. IDEA Standard Reports 10-71
-------
Penalty Contested An X will appear if the penalty was contested. (OSH.VPNCN)
Failure to Abate An X will appear if a FTA (Failure to Abate) has been issued, deter-
mined by the presence of a date in OSH.VDTFTA.
Hazard Level The potential harm to the workers posed by the health or safety vio-
lation, on a 1 (low probability) to 10 (high probability) scale.
(OSH.VGRAVE)
Corporate/Egregious Case An X will appear if this is an egregious case.
(OSH.VEGREG)
Status The status of the violation listed to the left, (derived from OSH.VSTS)
Not completed, AD discretion OSH.VSTS=A
Not completed, employer out of business OSH.VSTS = E
Immediately upon receipt OSH.VSTS = I
Not completed, solicitor advised OSH.VSTS = S
Not completed, work site changed ~ OSH.VSTS = W
Abatement completed OSH.VSTS = X
LINES
Cited substance(s) The substance(s) associated with this violation, if any. Both the
numeric code for the substance and a textual description will appear, (from
OSH.HAZSUB1 through OSH.HAZSUB5)
LINE 9
Accident A short description of the severity of any accident(s) noted in this
inspection. (OSH.ACCDGRE)
No injury
Fatality
Hospitalized injury
Nonhospitalized injury
OSH.ACCDGRE = 0
OSH.ACCDGRE=1
OSH.ACCDGRE = 2
OSH.ACCDGRE = 3
Source of Injury The source of the injury caused as a result of the accident.
(OSH.ACCSRC)
10-72 IDEA User's Guide
February 29, 1996
-------
AIRCRAFT
AIR PRESSURE
ANIMAL/INS/REPT/ETC
BOAT
BODILY MOTION
BOILER/PRESS VESSEL
BOXES/BARRELS, ETC.
BUILDINGS/STRUCTURES
CHEM LIQUIDS/VAPORS
CLEANING COMPOUND
COLD (ENVIR/MECH)
DIRT/SAND/STONE
DRUGS/ALCOHOL
DUST/PARTICLES/CHIPS
ELEC APPARAT/WIRING
FIRE/SMOKE
FOOD
FURNITURE/FURNISHING
GASES
GLASS
HAND TOOL (POWERED)
HAND TOOL (MANUAL)
HEAT (ENVIR/MECH)
HOISTING APPARATUS
LADDER
MACHINE
MATERIALS HANDLG EQ.
METAL PRODUCTS
MOTOR VEHICLE (HWY)
MOTOR VEHICLE(INDUS)
MOTORCYCLE
WIND/LIGHTNING, ETC.
FIREARM
PERSON
PETROLEUM PRODUCTS
PUMP/PRIME MOVER
RADIATION
TRAIN/RAILROAD EQUIP
VEGETATION
WASTE PRODUCTS
WATER
WORKING SURFACE
OTHER
FUME
OSH.ACCSRC = 01
OSH.ACCSRC=02
OSH.ACCSRC=03
OSH.ACCSRC=04
OSH.ACCSRC=05
OSH.ACCSRC=06
OSH.ACCSRC=07
OSH.ACCSRC = 08
OSH.ACCSRC=09
OSH.ACCSRC=10
OSH.ACCSRC=11
OSH.ACCSRC=12
OSH.ACCSRC=13
OSH.ACCSRC=14
OSH.ACCSRC= 15
OSHACCSRC=16
OSH.ACCSRC=17
OSH.ACCSRC=18
OSH.ACCSRC= 19
OSH.ACCSRC=20
OSH.ACCSRC=21
OSH.ACCSRC=22
OSH.ACCSRC=23
OSH.ACCSRC=24
OSH.ACCSRC=25
OSH.ACCSRC=26
OSH.ACGSRC=27
OSH.ACCSRC=28
OSH.ACCSRC=29
OSH.ACCSRC=30
OSH.ACCSRC=31
OSH.ACCSRC=32
OSH.ACCSRC=33
OSH.ACCSRC=34
OSH.ACCSRC= 35
OSH.ACCSRC=36
OSH.ACCSRC=37
OSH.ACCSRC=38
OSH.ACCSRC=39
OSH.ACCSRC=40
OSH.ACCSRC=41
OSH.ACCS!RC=42
OSH.ACCSRC=43
OSH.ACCSRC=44
Chapter 10. IDEA Standard Reports
10-73
-------
MISTS
VIBRATION
NOISE
BIOLOGICAL AGENT
OSH.ACCSRC=45
OSH.ACCSRC=46
OSH.ACCSRC=47
OSH.ACCSRC=48
Substance Contributing to Accident The substance(s) associated with this accident, if
any. Both the numeric code for the substance and a textual description will
appear. (OSH.ACCSUB)
LINE 10
Inspection No. This block contains data for a second inspection of the same facility.
Although every attempt has
been made to try to link the inspections for a single facility together, other
inspections for this facility (determined by the OSHA Activity Link) may
appear elsewhere in this report. Inspections will appear in chronological
order (sorted by inspection number). Click above to get descriptions of the
individual fields.
LINE 11
OSHA Overall Summary See page 10-24 in Section 10.1.1, Report 1A for detailed
information on these fields.
10-74 IDEA User's Guide
February 29,1996
-------
10.1.2.11 PCS (PCS) Report IB Elements
Permit Compliance System(PCS) Summary
1. Permit Number: IA0003395 Consolidated ID: Facility Name: ALUMINUM COMPANY OF AMERICA -
2. City:RIVERDALE County: SCOTT State: IA
3. SIC Code: 3355
4. Permit Date Issued: 1991/02 Permit Date Expired: 1996/02 Major Discharge Indicator: M
5. Current Year Noncompliance Status Auto.: ER
6. Current Year Noncompliance Status Man.: C
7. Enforcement Action Act. Action Action Status
Lead Date Status Date
NOTICE OF VIOLATION/NOV 1 S 09/05/91
NOTICE OF VIOLATION/NOV 1 S 10/26/92
8. Numeric Violations (E90) Count fay Parameter
Parm CY91 CY92 CY93 Parameter Description
01105 0 1 0 ALUMINUM, TOTAL (UG/L AS AL)
PCs Overall Summary
9. PCS Permit No: IA0003395 Issue Date: 1991/02 Year All Viols Eff.Viols Inspections No.NOVs No.AAs No.JAs
IB. Fac. Name: ALUMINUM COMPANY OF AMERICA - CY91 001100
11. Active Major Discharger CY92 111100
12. Expired Date: 1996/02 CY93 000000
Figure 10-26. PCS (PCS) Report IB Elements <
LINE 1
Permit Number The NPDES identification number. (PCS.NPDES)
Facility Name The name of the permitted facility. (PCS.PNAM and PCS.PNM2)
LINE 2
City City Name. (PCS.CYNM)
County County Name. (PCS.CNTN)
State Postal State Abbreviation, (derived from PCS.NPDES)
LINE 3
SIC Code 4-Digit Standard Industrial Classification Code(s). (PCS.SIC2)
LINE 4
Chapter 10. IDEA Standard Reports 10-75
-------
Permit Date Issued Date that the permit issued. (PCS.PTAC with
PCS.PTEV= P4099)
Permit Date Expired Date that the permit expired. (PCS.PTAC with
PCS.PTEV=P5099)
Major Discharge Indicator Code identifying a facility as either a major or minor
discharger. (PCS.MADI)
blank Minor discharger
M Major Discharger
LINE 5
Current Year Noncompliance Status Auto. Up to four codes identifying quarterly
reportable noncompliance based on system-generated DMR analysis for
major facilities. (PCS.CYQS)
LINE 6
Current Year Noncompliance Status Man. Up to four codes identifying quarterly
reportable noncompliance for major or minor facilities; manually set.
(PCS.CYMS)
C Compliant
D NC-SNC DMR Non-Recpt
E NC-SNC Effluent Viol
N NC-RNC Violins Only
P Resolved Pending
R Resolved
S NC-SNC Comp Schd Vio
T NC-SNC Comp Schd Rpt
LINE?
Enforcement Action Description of compliance or enforcement actions, (derived from
PCS.ENAC)
Act. Lead The compliance or enforcement action lead agency. (PCS.EATP)
Action Date Date of compliance or enforcement actions. (PCS.ENDT)
'10-76 IDEA User's Guide February 29, 1996
-------
Action Status Status description of compliance or enforcement actions, (derived from
PCS.ENST)
Status Date Date of the latest enforcement action status. (PCS.ESDT)
LINE 8
Farm Parameter code for the parameter in violation. (PCS.VPRM)
CY## Number of violation occurrences of PCS.MVIO = E90 (Numeric Violation)
with the monitoring date (PCS.MVDT) in the specified calendar year.
Parameter Description Description of the Parameter code, (from VPRM Table
Values)
LINEs 9 - 12
PCS Report 1A Summary: see page 10-26 in Section 10.1.1, Report IA for detailed
information on these fields.
Chapter 10. IDEA Standard Reports 10-77
-------
10.1.2.12 RCR (RCRIS) Report IB Elements
Resource Conservation and Recovery Information System (RCRIS) Summary
1. Handler ID: AKD68B85B781 Handler Name: MAPCO NORTH POLE REFINERY
2. City: NORTH POLE County: AK898 State: AK Zip: 99765
3. Existence Date: 1974/97/81 SIC Code(s): 1311
4. Owners(s)/0perator(s) Naiae Owner/Operator Indicator
HAPCO ALASKA PETROLEUM INC CO
5. Generator Indicator: 1 Transporter Indicator: TSD Indicator: X Source: E
2 X N
Address: 1188 H & H LN
6. Evaluation Type Respons. Evaluation Violation Viol. Viol.
Agency Date Area Class Prty.
STATE 83/65/87 TSD-GW HONIT 1
EPA 81/27/88
COHPL EVAL INSPECTION
3888(A) ORDER - INIT
COHPL EVAL INSPECTION
COHPL EVAL INSPECTION
Act.Date Enforcement
Resolved Action Type
81/86/89 STATE ADM REFERRAL TO EPA
Respons. Enf.Action
Agency Date
STATE 84/82/87D6W
STATE 86/21/98 SEN-ALL REQ. 1 18/29/98 NOTICE OF VIOL - INF
-Enforcement Actions without an Evaluation or Violation Match
NOTICE OF VIOL - INF EPA 12/19/85
VERBAL WARNING - IMF STATE 87/29/91
STATE
18/69/90GER
7. RCRIS Handler Id: AKD8B885B781
8.
9.
10.
Hasc: HAPCO NORTH POLE REFINERY
TSD Facility Status: X HPV? NO
Owner Operator Type: P Exist. Date:
Year No
CY92
CY93
CY94
.Eval. NorNOVs No.AAs No.JAs
8
8
8
8 0 a
888
888
Figure 10-27. RCR (RCRIS) Report IB Elements
LINB1
Handler ID Handler ID Number; usually the same as the EPA ID Number.
(RCR.ID)
Handler Name Handler's Name. (RCR.NAME) .
Address Location Street. (RCR.LOCST1 and RCR.LOCST2)
LINE 2
City Location City Name. (RCR.LCITY)
County Location County Code. (RCR.CDE)
State Location Postal State Abbreviation. (RCR.LSTATE)
Zip Location ZIP Code. (RCR.LZIP)
10-78 IDEA User's Guide
February 29, 1996
-------
LINE 3
Existence Date Existence Date for the facility. (RCR.HEXDATE)
SIC Code(s) The Standard Industrial Classification (SIC) code(s) listed for this
facility. (RCR.SICCODE)
LINE 4
Owner(s)/Operator(s) Name Name of current or jprevious owner(s) of operators)
(RCR.CONAME)
Owner/Operator Indicator Code indicating current or previous owner or operator
(RCR.COIND)
CO Current Owner
CP Current Operator
PO Previous Owner
PP Previous Operator
LINES
Generator Indicator Code indicating activity status of hazardous waste generation
(RCR.GEN)
1 Large Quantity Generators
2 Small Quantity Generators
3 Conditionally Exempt Small Quantity Generators
4-9 Other state regulated generators
N Not a generator, verified
Blank Unverified
Transporter Indicator Code indicating activity status of hazardous waste transportion
(RCR.TRANS)
C Transports wastes for hire (i.e., commercial transport)
S Transports wastes for self
X Transports wastes, but commercial status is unknown
N Not a transporter, verified
Blank Unverified
Chapter 10. IDEA Standard Reports 10-79
-------
TSD Indicator Code indicating activity status of hazardous waste treatment, storage
or disposal. (RCR.TSD)
X TSD
N Not a TSD, Verified
Blank not a TSD, Unverified
Source Code indicating source of the information in the generator/transporter/tsd
fields to the left. (RCR.SOURCE)
N Notification
A Part A
R Annual/Biennial Report
E EPA Inspection
S State Inspection
LINE 6
Evaluation Type Type of evaluation. (RCR.ETYPE)
Respons. Agency Agency responsible. (RCR.EVALAGN)
Evaluation Date Date of evaluation. (RCR.EVALDTE)
Violation Area Violation area. (RCR.VAREA)
BCE BIF Standards To Control Emissions
BDT BIF Standards For Direct Transfer
BIS BIF Interim Status Standards
BPS BIF Permit Standards
BRR BIF Standards For Regulation Of Residue
CAS TSD-C/A Compliance Schedule
CSS Compliance Schedule Violation
DCH TSD-Chemical/Physical/Biological
DCL TSD-Closure/Post-Closure Requirements
DCP TSD-Continquency Plan Requirements
DFR TSD-Financial Reponsibility Requirement
DCS TSD-General Standards
DGW TSD-Groundwater Monitoring Requirements
DIA Incinerator Waste Analysis
10-80 IDEA User's Guide
February 29, 1996
-------
DIN TSD-Incineration Requirements
DLB TSD-Land Ban Requirements
DLF TSD-Landfills Requirements
DLT TSD-Land Treatment Requirements
DMC TSD-Containers Requirements
DMI Incinerator Monitoring And Inspection
DMR TSD-Manifest Requirements
DOP Incinerator Operating Requirements
DOR TSD-Other Requirements (Impl.)
DOT TSD-Other Requirements (Oversight)
DPB TSD-Part B Permit Application
DPP TSD-Preparedness/Prevention Requirement ,
DPS Incinerator Performance Standards
DSI TSD-Surface Impoundments Requirements
DTR TSD-Tanks Requirements
DTT TSD-Thermal Treatment Requirements
DWP TSD-Waste Piles Requirements
FEA Former Enforcement Agreements
GER Generator-All Requirements (Oversight)
GGR Generator-General Requirements
GLB Generator-Land Ban Requirements
GMR Generator-Manifest Requirements
GOR Generator-Other Requirements (Impl.)
GPT Generator-Pre-Transport Requirements
GRR Generator-Recordkeeping Requirements
GSC Generator-Special Conditions
GSQ Generator-Small Quantity Generator
TGR Transporter-General Requirements
TMR Transporter-Manifest/Recordkeeping
TOR Transporter-Other Requirements (Impl.)
TRR Transporter-All Requirements (Oversight)
TWD Transporter-Haz. Waste Discharge
Violation Class Violation class. (RCR.VCLASS)
Violation Prty. Violation priority. (RCR.VPRTY) Values will be either High Priority
Violator (HPV) or Blank.
Action Date Resolved Action date resolved. (RCR.VACTDTE)
Enf. Action Type Enforcement action type. (RCR.ENFTYPE)
Resp. Agency Responsible agency. (RCR.ENFAGN)
Chapter 10. IDEA Standard Reports
10-81
-------
Enf. Action Date Enforcement action date. (RCR.EDATE)
LINEs 7-10
RCRIS Report 1A Summary: seepage 10-28 in Section 10.1.1, Report IA for
detailed information on these fields.
10-82 IDEA User's Guide
February 29, 1996
-------
10.1.2.13 SET (SETS) Report IB Elements
SITE ENFORCEMENT TRACKING SYSTEM (SETS) SUMMARY
1. Site ID. Number: ALD031618069 Site Name: MOWBRAY ENGINEERING CO Street: JCT OF 2ND & BEELAND STS
2. City: GREENVILLE State: AL Zip Code: 36037
3. PRP Name / Addressee Address City State Zip Date of General Notice
ALABAMA POWER COMPANY
ROBERT E HUFFMAN 600 NORTH 18TH STREET BIRMINGHAM AL 35291 03/10/89
ARAB ELECTRIC COOPERATIVE
JOE VAN BUNCH P.O. BOX 426 ARAB AL 35016 03/10/89
BLACK WARRIOR
M.D. BLACK P.O. BOX 779 DEMOPOLIS AL 36732 03/10/89
BALDWIN COUNTY EMC
JOSEPH G. DOBBS HIGHWAY 59 SUMMERDALE AL 36580 03/10/89
MORGAN STREET SELMA AL 36307 03/10/89
Figure 10-28. SET (SETS) Report IB Elements ~~~
LINE 1
Site ID. Number SETS identifier. (SET.SITEID)
Site Name The official site name for a hazardous waste site. (SET.SITENM)
Street Site street address. (SET.STREET)
LINE 2
City Site city name. (SET.CITY)
State Site postal state abbreviation. (SET.STATE)
Zip Code Site ZIP code. (SET.ZIP)
LINE 3
PRP Name/Addressee Name of Potential Responsible Party (PRP). (SET.PRPNAME
and SET.ADDRSEE)
Address Street/mailing address of PRP. (SET.STREET1)
Chapter 10. IDEA Standard Reports 10-83
-------
City PRP city name. (SET.ADCITY)
State PRP Postal State Abbreviation. (SET.ADSTATE)
Zip PRP ZIP code. (SET.ADZIP)
Date of General Notice/Special Notice Date of General Notice Letter issued, and/or
Special Notice Letter issued. (SET.GNLDATE and SET.SNLDATE)
10-84 IDEA User's Guide February 29, 1996
-------
10.1.2.14 TRI (TRIS) Report IB Elements
TOXIC RELEASE INVENTORY SUMMARY PAGE
1. Facility ID: 52808LMNMCHIGHW Facility Name: ALCOA
2. SIC Codes: 3353 3355 3533
Address: 4879 STATE ST.
3. Reporting Year: 1987
CasID. No. Chemical/Mixture Name
000020086 COPPER COMPOUNDS
000020064 CHROMIUM COMPOUNDS
000020122 MANGANESE COMPOUNDS
001344281 ALUMINUM OXIDE
000075092 DICHLOROMETHANE
001310732 SODIUM HYDROXIDE (SOLUTION)
NUMMARY fnr» Al 1 TRT FMT^TflN's
Fugitive or
Non-point
Air Emissns
250
250
250
44000
10000
0
Stack or
Underground
Point Air Discharge
Emissions To
32000
1600
11000
0
0
0
Water
0
0
0
0
0
0
Injection
0
0
0
0
0
0
Releases
to Land
0
0
0
0
0
0
Discharge
to POTW
0
0
0
0
0
0
Transfers
to Off site
Location
12000
0
2600
0
0
0
Total
Releases^
Transfers
44250
1850
13850
44000
10000
0
—————— ——oUFlrlHM IUI ML.L ll\l LrilodlUHO — —- - -.
4. TRI Id: 52808LMNMCHIGHW Facility Name: ALCOA
YR Chem Count Lbs:NP Air Pt Air
1991 17 195305 1870900
Water UG
3270
In j . Land
0 750
POTW
0
Off-Site
175720
Total
2245945
Figure 10-29. TRI (TRIS) Report IB Elements
LINE1
Facility ID The TRIS identifier. (TRI.TFID) i
Facility Name The name of the regulated facility. (TRI.HNME)
Address The street address of the regulated facility. (TRI.HSTR)
LINE 2
SIC Codes The Standard Industrial Classification Code(s) reported by the facility.
(TRI.SICD)
LINE 3 (Chemical Release Data - Repeating data block for each reporting year)
Reporting Year The four digit year period for which the facility is reporting chemical
releases. (TRI.RPYR)
CasID. No. The TRIS chemical identification number; corresponding to the Chemical
Abstracts Service (CAS) registry number, with the exception of chemical
mixtures which have unique TRIS number. (TRI.TCID)
Chapter 10. IDEA Standard Reports
10-85
-------
Chemical/Mixture Name The description of the TRIS chemical identification number.
(TRI.NAME)
Fugitive or Non-point Air Emissions The quantity of chemical in pounds, released as
non-point air emissions. (TR1.MREST for TRI.CREL = 1)
Stack or Point Air Emissions The quantity of chemical in pounds, released as point air
emissions. (TRI.MREST for TRI.CREL = 2)
Discharge To Water The quantity of chemical in pounds, released to receiving streams
or water bodies. (TRI.MREST for TRI.CREL = 3)
Underground Injection The quantity of chemical in pounds, released via underground
injection wells on-site. (TRI.MREST for TRI.CREL = 4)
Releases to Land The quantity of chemical in pounds, released to land on-site, e.g.,
landfills, application farming, surface impoundments. (TRI.MREST for
TRI.CREL = 5)
Discharge to POTW The quantity of chemical in pounds, released off-site to publicly
owned treatment works (POTWs). (TRI.MREST for TRI.CREL = 6)
Transfer to Offsite Location The quantity of chemical in pounds, transfered to off-site
disposal, treatment, or storage facilities. (TRI.MREST for TRI.CREL =
7)
Total Releases & Transfers The quantity of chemical in pounds, released to any media
or transferred off-site. (TRI.TREST)
LINE 4
TRIS Report 1A Summary: see page 10-30 in. Section 10.1.1, Report 1A for detailed
information on these fields.
10-86 IDEA User's Guide
February 29, 1996
-------
10.13 Report 2
Report 2 is a multimedia table that contains the following information on selected
facilities: EPA facility identification number, name, state, and violation status. This
report will indicate if a facility is a significant noncomplier (SNC) in the CWA,
FIFRA, EPCRA 313, and TSCA programs; a high priority violator (HPV) according
to the RCRA program; or a significant violator (SV) according the CAA program. It
also contains the following civil docket information: case number, case name, and
overall status. The total number of facilities and violators for each database are listed
at the bottom of Report 2.
Note:
In the case of a Linked Nonlinked query, Report 2 will first present the facili-
ties with valid FINDS identification numbers that match all of the selection
criteria, followed by the facilities without valid FINDS identification numbers
that match any selection criteria.The screens in the following sections illustrate
the report generated by a sample query built using GO Names to find facilities
that are in aluminum-related industries. (This is merely an exercise that has
no basis in fact regarding any planned or on-going enforcement initiatives.)
EPA Id.
Number
AL08GB162958
ALD831618669
AL56B8B38926
IAD9B5278169
Facility Name
ALUMINUM COMPANY OF AMERICA ALCOA
MOHBRAY ENOINEERINC COMPANY IN AL
EASTERN ENVIRONMENTAL
ALCOA
U.S. ENVIRONMENTAL PROTECTION AGENCY
INTEGRATED DATA SYSTEM. REPORT 2
MULTI-MEDIA SI6NIFICANT NONCOMPLIER/SI6NIFICANT VIOLATOR REPORT
CIVIL DOCKET DATA
Air Hater RCRA Pest Toxic EP313
State SV? SNC? HPV? SNC? SNi:? SNC? Case Number Case Nane
Overall Status Laus Cited
84-86-9934 NOI1MAN PARKER/MOHBRAY ENGINEER CASE CLOSED CERCLA
94-89-9935 ALABAMA POHER (MOHBRAY ENOINEE CONCLUDED
CERCLA
TOX
97-84-8026 ALUMINUM COMPANY OF AMERICA, R
CERCLA
87-85-8189 ALCOA
RCRA
87-88-0199 ALCOA - MISSISSIPPI RIVER POOL
CERCLA
07-BB-6125 ALUMINUM COMPANY OF AMERICA, R
TSCA
NJD862837931 EXXON BAYWAY CHEMICAL PLANT
EP 92-98-8174
EXXON CORP CONCLUDED
82-92-8282 EXXON CO, USA
CAA
02-92-8228 EXXON COMPANY, USA
EPCRA
CHA
Total Number of Facilities:
Total Air Significant Violators:
Tota Hater Significant Non_compliers:
Tota RCRA High Priority Violators:
Tota FIFRA Significant Non_compliers:
Tota TSCA significant Non_co«pl i ers:
Tota EP313 Significant Non_compliers:
End of Report
5 ' .
1
1
9
8 •'
1
1
FINDS Report 2 Elements
Chapter 10. IDEA Standard Reports
10-87
-------
EPA Id. Number EPA Facility Identification Number (FIN.EPID)
Facility Name Facility/Site Name (FINrFNME)
State Postal State Abbreviation (FIN.STAT)
Media-Program Noncompliance Indicators
Air SV? Is this facility flagged in AFS as a "Significant Violator"? (based on the
codeAFS.SVIl)
Blank not a SV
AIR SV (AFS.SVI1 = E,S,B,X,C,F,T)
Water SNC? Is this facility flagged in PCS as having current violations which consti-
tute "Significant Noncompliance"? (based on the code PCS.LRNC)
Blank not a SNC
WTR SNC (PCS.LRNC = D,E,S,T)
RCRA HPV? Is this facility flagged in RCRIS as having unresolved violations which
constitute "High Priority Violations"? (based on the code RCR.CPVIOL)
Blank not a HPV
WST HPV(RCR.CPVIOL = 9)
Pest SNC? Does this NCDB facility have current or historical violations which con-
stitute FIFRA "Significant Noncompliance"? (based on the code
NCD.SNC)
Blank not a SNC
PES SNC (NCD.LEGISLA= F; NCD.SNC = Y)
Toxic SNC? Does this NCDB facility have current or historical violations which con-
stitute TSCA "Significant Noncompliance"? (based on the code NCD.SNC)
Blank not a SNC
TOX SNC (NCD.LEGISLA = T and NCD.SNC = Y)
1
10-88 IDEA User's Guide February 29, 1996
-------
EP313 SNC? Does this NCDB facility have current or historical violations which con-
stitute EPCRA Section 313 "Significant Noncompliance"? (based on the
code NCD.SNC)
Blank not a SNC
EP SNC (NCD.LEGISLA= E and NCD.SNC = Y)
Civil Docket Report 2 Elements
Case Number Civil Enforcement (C/E) Docket Case Number (DCK.CSNO)
Case Name The case name as present in the complaint (DCK.CSNM)
Overall Status Civil Enforcement Docket Case Overall Status: an indicator of where
the case falls in the judicial process "pipeline" (DCK.OSTA)
Blank Indicates an administrative case.
FILED CRT Case has been filed with the court.
CONCLUDED Case litigation has been concluded by some action,
e.g., withdrawal, dismissal, consent decree, court order,
etc.
CASE CLOSED All aspects of the ease have been satisfied.
Laws Cited Civil Enforcement Docket Case Laws Cited: An indicator of the law(s)
cited in the judicial complaint (or the regulatory authority for an adminis-
trative action). Values typically correspond to the acronym for the Federal
legislation being cited, e.g., CAA = Clean Air Act (DCK.LAWS)
10.1.4 Summary Report
The Summary Report has five distinct sections.
!
• The first section is a chart showing the number of facility counts by program and
by EPA region.
• The second section lists the number of selected facilities that are in compliance
and not in compliance by program.
• The third section gives the total number of enforcement actions taken on selected
facilities by program. ;
Chapter 10. IDEA Standard Reports 10-89
-------
• The fourth section shows facility counts by region and by Standard Industrial
Classification (SIC) code.
• The fifth section totals toxic substance release information for the selected facili-
ties by pollutant and by year.
I— Caution
The Summary Report should be selected only if a Linked query is being run. Due
to the nature of this report, it may present misleading information if selected with
a Nonlinked query
The screens in the following sections illustrate the report generated by a sample query
built using GO Names to find facilities that are in aluminum-related industries. (This
is merely an exercise that has no basis in fact regarding any planned or on-going
enforcement initiatives.) _
10-90 IDEA User's Guide
February 29, 1996
-------
U.S. Environmental Protection Agency
Summary Report
1.
PRG
AFS
CER
DCK
DUN
FFI
FIN
LSI
NCD
PCS
RCR
SET
TRI
Number of Facilities Selected by Region and Program
I
0
0
Q
0
Q
0
0
0
0
Q
0
0
II
1
1
1
0
0
1
1
1
1
1
0
1
III
0
Q
Q
Q
Q
0
Q
Q
0
0
0
0
IV
1
1
1
1
1
3
0
0
1
2
1
0
V
0
0
0
0
0
0
0
0
0
0
0
0
VI
0
0
0
0
0
0
0
0
0
0
0
0
VII
1
1
1
0
0
1
0
1
1
1
0
2
VIII
0
0
0
0
0
0
0
0
0
0
0
0
IX
0
0
0
0
0
0
0
0
0
0
0
0
X
0
0
0
0
Q
0
0
0
0
0
0
0
TOTAL
3
3
3
1
1,
5
1
2
3,
4
1
3
2.
Complianee Status of Facilities by Program
AFS RCR PCS
All Three
Facs
+ Facs
in
Not
Compliance
in Compliance
2
1
( 67%)
( 33%)
4
0
(100%)
( 0%)
2
1
( 67%)
( 33%)
2
0
( 67%)
( 0%)
s Total Number of Facs 343
3. Number of Enforcement Actions by Program
AFS
RCR
PCS
CER
Year NOV/NONS Admin Oudic NOV/NONS Admin Judic NOV/NONS Admin Judic Admin Judic
1990
1991
1992
1993
0
0
0
0
6,
1
1
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
1
0
0
0
1
0
0
0
0
0
1
0
0
0
0
0
0
0
Number of Open Civil Docket Cases
0
4.
Summary of SIC Codes by Region
SIC
I II III IV V VI VII VIII IX X Totals Parameter Description
2819
2869
2911
3334
3341
3353
3355
3533
4931
5171
5541
TOTALS
0
CHEMICALS
0
0
0
0
0
0
0
0
0
0
0
0
1
1
0
0
0 ,
0
0
1
1
1
5
0
0
0
0
0
0
0
0
0
0
0
0
1
0
0
1
0
0
0
0
0
0
0
2
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
1
1
1
0
0
0
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
1
•1
1
1
1
1
1
1
1
1
1
11
INDUSTRIAL INORGANIC CHEMICALS
INDUST. ORGANIC CHEMICALS NEC
PETROLEUM REFINING
PRIHARY PRODUCTION OF ALUMINUM
2NDARY SMELT/NONFERROUS METALS
ALUMINUM SHEET, PLATE AMD FOIL
ALUMINUM ROLLING & DRAWING NEC
OIL FIELD MACHINERY
ELEC & OTHER SERVICES COMBINED
PETROLEUM BULK STATIONS & TERM
GASOLINE SERVICE STATIONS
Figure 10-31. IDEA Standard Summary Report
Chapter 10. IDEA Standard Reports
10-91
-------
5. Summary of TRI Releases by Pollutant and Year
Pollutant Name TCID Year Emissions ^^B
ACETONE 000067641 1987
1988
1989
1990
1991
ALUMINUM OXIDE 001344281 1987
1988
AMMONIA 007664417 1987
1988
1989
1990
1991
ANTIMONY COMPOUNDS 000020008 1989
BARIUM COMPOUNDS 000020020 1987
1988
1989
1990
139,950
139,500
87,500
94,568
72,500
1,860,000
271,000
213,981
212,746
194,800
110,884
113,377
430
2,760
830
1,576
1,601
Figure 10-32. Summary Report (Continued)
Summary Report Elements
TABLE 1
PRG EPA Program/Data System
AFS AIRS Facility Subsystem
CER CERCLIS
DCK Civil Docket
DUN Dun & Bradstreet
FFI Federal Facility Information System
FIN FINDS
LST Contractor Listing Docket
NCD National Compliance Database
PCS Permit Compliance System
RCR RCRIS
SET Site Enforcement Tracking System
TRI Toxic Chemical Release Inventory System
I-X
EPA Regions (FIN.REGN)
TABLE 2
10-92 IDEA User's Guide
February 29, 1996
-------
Facs in Compliance AFS/RCR/PCS Number of facilities returned that are in compli-
ance in this database. The percentages indicate the percentage of the total
number of facilities selected that are in compliance in this database.
(AFS.SVI1, RCR.CPVIOL, or PCS.LRNC)
Facs not in Compliance AFS/RCR/PCS Number of facities returned that are not in
compliance in this database. The percentages indicate the percentage of
the total number of facilities selected that are not in compliance in this
database. (AFS.SVI1, RCR.CPVIOL, or PCS.LRNC)
Facilities in Compliance - All Three The total number of facilities (calculated by
counting FIN.EPIDs) that are in compliance with AFS, RCR and PCS.
Facilities not in Compliance - All Three The total number of facilities (calculated by
counting FIN.EPIDs) that are not hi compliance with AFS, RCR and PCS.
Total Facilities - All Three The total number of facilities meeting your Select criteria,
and hi all three databases (AFS, PCS, and RCR). This is usually not equal
to the sum of the numbers above. The reason for this is that the numbers
above are the total number of facilities in, or not in, compliance in all three
databases. Thus facilities not hi compliance with one or two of the three
databases, but not all of them, do not appear above.
TABLE 3
NOV/NONS The number of Notices of Violation/Notices of Noncompliance in the
indicated calender year, in the indicated database. (AFS.ANTI = 1A or 5C,
RCR.ENFTYPE= 120, or PCS.ENAC==20 or 83)
Admin Number of administrative actions.
AFS AFSANTl = IB, 2B, 3B, 7E, 8A, 8C, or 9A and AFS.DTA1 in the indicated
calender year.
RCR RCR.ENFTYPE in the range from 200 to 399 and RCR.EDATE in the indi-
cated calender year.
PCS PCS.ENAC=AA, AC, AE, AF, AI, A3, A5, A7, 21, 23, 56, 62, 72, 75, 76, 80,
81, 84 through 90, 96, or 97 and PCS.ENDT in the indicated calender year.
CER CER.1732 with AC, AV, CA, FI, RR, SO, or UAand CER.1716 or CER.1717
in the appropriate calender year.
Judic Number of judicial actions
Chapter 10. IDEA Standard Reports 10-93
-------
AFS AFS.ANTI = 1 D,l E,2D,4B,5B,6B, or 9C and AFS.DTA1 in the indicated
calender year.
RCR RCR.ENFTYPE in the range from 400 to 699 and RCR.EDATE in the indi-
cated calender year.
PCS PCS.ENAC= 19, 25, 26, 35, 36, 37, 38, 58, 64, or 71 and PCS.ENDT in the
indicated calender year.
CER CER.1732 with CB, CC, CD, CL, SD, SF, SV, or SX and CER.1716 in the
appropriate calender year, or CER.1732 with JG or TE and CER.1717 in that
year)
TABLE 4
SIC Standard Industrial Classification Code (AFS.SICC, PCS.SIC2,
RCR.SICCODE, or TRI.SICD)
I-X
EPA Regions (FIN.REGN)
Parameter Description SIC code definition
TABLE 5
Pollutant Name English name of chemical (TRI.NAME)
TCID Toxic chemical identification number (TRI.TCID)
Year Reporting year (TRI.RPYR)
Emissions Emissions in pounds (TRI.TREST)
10.2 Accessing and Navisatins Reports
After running a report, the QUERY STATUS SCREEN will appear (see
Figure 10-33). On this screen, IDEA displays the following: the time of day when it
finished running the query, the number of facilities found in the search, whether or
not they are in FINDS (i.e., have valid FINDS identification numbers), and a chart
indicating the databases relevant to the search. This chart varies for Linked, Non-
linked, and Linked Nonlinked queries.
10-94 IDEA User's Guide
February 29, 1996
-------
Figure 10-33. Query Status Screen
In the case of Linked and Linked Nonlinked searches, the chart contains a combina-
tion of "counts" and percentages for each database relevant to a search. The counts
are the number of facilities that meet at least one of your criteria for that database
but do not have valid FINDS identification numbers. The percentage measures these
counts with respect to the total number offaciliti.es meeting at least one of your cri-
teria in that database (including both facilities with and without valid FINDS identifi-
cation numbers). This chart allows users to gauge the percentage of facilities
excluded from a search due to missing FINDS linkages.
Because Nonlinked searches do not access FINDS, the chart in this case contains the
facility counts but not the percentages. For more information on the relationship
between a query and the number of facilities selected, refer to Chapter 2, IDEA:
What it Does & How it Works.
From the QUERY STATUS SCREEN, users can choose to go back and modify a
search (END or PF3) or go forward and view the reports (press < Enter > ). These
choices are displayed at the bottom of the screen. The reports are viewed in the
BROWSE mode and are organized according to the formats selected earlier (see
Figure 10-34).
Chapter 10. IDEA Standard Reports
10-95
-------
BROWSE.-
COH
issae
IHTESRATSJ BAtA ,
Name: MftRlME 'COS
TS& ^
Owner
PCS Psnnlt Ko.jvw
Fac . Nattter , U . , JS : "
Acti ve' Haj or-, l>
Expired Datfei 19BBjf8&.
f>CS fermit
Fac.
Figure 10-34. An Example of Report 1A
Regardless of the report format selected, the title line of the BROWSE SCREEN will
provide the following information:
REPORT the report format you selected
IN PROGRESS/COMPLETE the status of your report
MAX the number of lines currently in your report
LINE the number of the first line visible on the screen
COL the range of columns you are currently viewing
Multiple report formats may be chosen at the same time. To move from one report
to another in the BROWSE mode, type SW (switch) at the COMMAND prompt and
press < Enter >.
Use the commands in Table 10-1 to view your report in the BROWSE mode.
10-96 IDEA User's Guide
February 29,1996
-------
Table 10-1. Commands for Navigating Reports
Commands
Descriptions
UP PF7/PF19
DOWN
PF8/PF20
LEFT
PF10/PF22
RIGHT
PF11/PF23
END PF3/PF15
SWAP
PF9/PF21
MANEUVERING
Arrow keys
< Home >
M(ax) + UP
M(ax) +
DOWN
M(ax) +
RIGHT
+ LEFT
Scrolls up by the amount set at the SCROLL prompt, or by the number of lines
entered at the COMMAND prompt.
Scrolls down by the amount set at the SCROLL prompt, or by the number of
lines entered at the COMMAND prompt.
Scrolls left by the amount set at the SCROLL prompt, or by the number of
lines entered at the COMMAND prompt.
Scrolls right by the amount set at the SCROLL prompt, or by the number of
lines entered at the COMMAND prompt.
Saves and returns to the previous screen.
Moves the cursor from a position in one screen to the same position in another
using the split-screen mode.
THE CURSOR
Use arrow keys for all directions
Use < Tab > key to move to the next input field.
Use < Home > to move to the top-left input field.
Scrolls up to the first top line of a report;
Scrolls down to the last bottom line of a report;
Scrolls to the right marge of a report;
—Scrolls to the left marge of a report. .
10.3 Printing Reports
1. Query reports may be printed after a "COMPLETE" report is generated. Check
the center of the BROWSE SCREEN'S title line for the word "COMPLETE."
This will indicate that IDEA has finished processing the query report. If "IN
PROGRESS" is displayed, press < Enter > every few seconds until "COMPLETE"
appears. IDEA allows users to print part or all of a report by specifying line
numbers (see Figure 10-35).
Chapter 10. IDEA Standard Reports
10-97
-------
'flROWSE - Report?
RCRIS Handler iB'i \.Jtf^^,
Naitte: MARIHE CORPS" Wg'iEB C
- TSD
Owner- aB&rat&*'!$ie!i''F"yEi
'•' PCS "Pennit Mo: J*Afi|&^5|
Active
PCS Permit Won
Fac. Nafflfri ECS
Figure 10-35. Report 1A
2. Type PRINTO at the COMMAND prompt and press < Enter >. The
PRINT/SAVE PARAMETER SCREEN will pop up (see Figure 10-36).
10-98 IDEA User's Guide
February 29, 1996
-------
f^ftHlfif; !'^^!|^1^^^^fli^!^^|' f |!| \
ftJ,*iS*. At the TO LINE NO. prompt, type the MAX number that appears at
the upper right corner of the BROWSE screen and press < Tab >. The MAX
number corresponds to the final line of the report when it is "COMPLETE".
4. IDEA also allows users to print just a portion of the report. Printing only part of
a report is useful if a complete report contains unneeded information. Within the
BROWSE mode, a continuous block of information can be printed. For example,
lines 1 through 23 can be printed. However, you cannot print lines 1 through 23
and lines 46 through 69 at the same time. To print a portion of the report, type
in the number of the first line of the block to be printed and < Tab > to the TO
LINE NO. prompt. Type the ending line number and press < Tab >.
5. At the FOR PRINTING - BIN prompt, type your site specific BIN number and
< Tab > to the DESTINA- TION prompt. Type your site specific printer desti-
nation ID (or press < Tab > to send your print to the HOLD queue) and
< Tab > to the NO. OF COPIES prompt. Type the number of original copies
you wish to receive and press < Enter >. The default setting for print destination
is HOLD and the default for the number of copies is 1.
Chapter 10. IDEA Standard Reports
10-99
-------
helpful hint
If you choose to send your output to the HOLD queue (or if you press < Enter >
too early and send it there by mistake), you must then let the system know to
which printer you want the output to be routed by using the System Display and
Search Facility (SDSF).
Take the following steps to release your print job from the HOLD queue:
1. To access SDSF, type SDSF at the COMMAND line of any Keyword screen.
This will bring up the SDSF Primary Option Menu pictured in Figure 10-37.
V1S3M3 ---•-»«"•"•-•«""-«
COMMAND INPUT "==4
Type an option b'r
„,, v- :~l-*Cf\
Figure 10-37. SDSF Primary Option Menu Screen
2. Type O at the COMMAND prompt and press < Enter > to "display jobs in the
JES2 output queue." Look for your user ID and batch job number (JOBxxxxx)
under the JOBNAME and Jobid headings, as in Figure 10-38.
10-100 IDEA User's Guide
February 29, 1996
-------
Figure 10-38. SDSF Output Queue Screen
3. Press < Tab > to move the cursor down to your print job, then over to the DEST
column. The text should read R255, which simply means that your print job is in
the HOLD queue. Type over R255 with the identifi- cation number of the printer
at your site or one of the options listed below, and press < Enter > two times.
Destination options:
WIC Prints at the Washington Information Center (WIG) at EPA Headquar-
ters, Washington, DC.
LOCAL Prints at the National Computer Center (NCC), Research Triangle
Park, NC.
RMTO Same as LOCAL.
R + RP# Prints at the designated remote printer. Here RP# is the ID for the
remote printer. To view a list of the remote printers available to IDEA
users:
a. Exit IDEA and type ISPF 3.4 at the TSO READY prompt. The
DATA SET LIST UTILITY SCREEN will appear.
b. Type JUSD.REMQTE.DATA at the DSNAME LEVEL prompt;
press < Enter >. The DS LIST SCREEN will appear.
c. < Tab > down and type B (Browse) next to the
JUSD.REMOTE.DATA member. Press < Enter > to view the list
of remote printers.
d. When you are finished, use the RETURN command (PF4) to go to
the ISPF/PDF PRIMARY OPTION MENU. Type X to return to
the READY prompt.
Chapter 10. IDEA Standard Reports
10-101
-------
helpful hint
The first time you press < Enter > in step 3 a message reading
COMMAND ISSUED will appear in the upper right hand corner of
the screen, and the printer destination you just typed in will change
backtoR255. Don't panic! When you press < Enter > the second
time, the correct destination will again be displayed. (Compare
Figure 10-39 with Figure 10-40&period.)
'S5SF OUTPUT
CQWWND I WOT ==*>
NP aOBNAME Jdisid"." Oest
Figure 10-39. SDSF Output Queue - "Command Issued" Screen
Figure 10-40. SDSF Output Queue - Print Destination Changed Screen
If you decide not to print your job, type a P (Purge) under the NP
column on the line of the job you want to cancel; press < Enter >.
Warning: a purged record can not be recovered.
4. To exit SDSF, use the END command or PF3 two times. You will return to the
Keyword screen from which you issued the SDSF command in step 1.
10-102 IDEA User's Guide
February 29, 1996
-------
10.4 Savins Reports
1. Query reports may be saved after a "COMPLETE" report is generated. Check the
center of the BROWSE screen's title line for the word "COMPLETE." This will
indicate that IDEA has finished processing the query report. If "IN PROGRESS"
is displayed, press < Enter > every few seconds until "COMPLETE" appears.
Position the cursor at the COMMAND prompt.
2. Type SAVE at the COMMAND prompt and press < Enter >. The
PRINT/SAVE PARAMETER SCREEN will pop up (see Figure 10-36).
3. IDEA allows users to save part of a report or all of it. Saving only part of it is
useful if the complete report contains unneeded information. However, BROWSE
mode offers limited saving options. Only a continuous block of information can
be saved. For example, you can save lines 5 through 20, but not lines 5 through
20 and lines 30 through 40 at the same time using this facility. You may save to a
dataset (Step 4) to perform more advanced editing.
To save a block of the report, at the FROM LINE NO. prompt, type in the
number of the first line in the block to be saved or type 1 to start at the beginning
of the report. Press < Tab > . At the TO LINE NO. prompt, type the last line
number of the block to be saved or type in the MAX number which appears at
the upper right of the BROWSE screen and press < Enter > .
4. At the FOR SAVING ENTER DSN OR DSN (MEMBERNAME) prompt, a
dataset or membername must be entered to identify the name of this report and
where it will be stored.
10.5 Exitins Reports
To exit the BROWSE SCREEN and get back to the INTERFACE SELECTION
SCREEN at any time, follow these procedures:
• Use the END command (PF3 key) to back out of the program screen by screen.
• Use the RETURN command (PF4 key) to return to the OFFICE OF EN-
FORCEMENT DATA INTEGRATION PRIMARY MENU, then type I for
IDEA at the OPTION prompt to get back to the IDEA WELCOME SCREEN,
or type X to exit to the TSO READY prompt.
Chapter 10. IDEA Standard Reports 10-103
-------
• Type =X at the COMMAND prompt to go directly to the TSO READY
prompt, then type LOGOFF to exit TSO.
10.6 Summary
IDEA offers users four standard reports, which have been designed to address dif-
ferent informational needs. Since each is designed to display predefined categories
that may or may not be relevant to a particular investigation, IDEA users should
understand these report formats before selecting one. Section 10.1, Choosing a
Standard Report Format describes the standard report formats in detail.
Report 1A Provides a brief description of the facilities selected by your query.
Selecting linked, Nonlinked, or Linked Nonlinked will affect the organization of the
report.
Report IB Provides a detailed description of the facilities selected by your query.
Selecting linked, Nonlinked, or Linked Nonlinked will affect the organization of the
report.
Report 2 A multimedia table that indicates if a facility selected by your query is listed
as a significant noncomplier (SNC), a high priority violator (HPV), or a significant
violator (SV).
Summary Report Consists of five distinct sections which provide facility count totals.
The remaining sections of Chapter 10, IDEA Standard Reports provide information
on accessing and navigating, printing, saving, and exiting IDEA reports.
10-104 IDEA User's Guide
February 29, 1996
-------
Chapter 11. IDEA User-Specified Reports
This chapter explains how to construct a columnar report of your own design and
format, called a User-specified Report. You, the user, specify what data will appear
in the report, how the data will be ordered, and what summary information you
would like to see. You also have control over the formatting of the report and can
provide a customized report title and column headings.
11.1 Overview of IDEA User-specified Reports (USRs)
The IDEA Standard Reports described in Chapter 10, IDEA Standard Reports, are
pre-programmed to supply specific types of data airranged in a fixed format, meaning
that only certain data will appear on a given report and the format will be controlled
by the program. The IDEA User-specified Report (USR) option provides you with
the ability to specify what data are to be displayed and offers you a new degree of
control over the appearance of the data in the report.
The data in a USR are arranged in columns. You can specify a heading for each
column, the width of the column, and the justification of the data values within the
column. You have control over the order in which the data appear, and what, if any,
summary information is to be calculated and displayed.
IDEA User-specified Report requests are typed into your query using the ISPF/PDF
editor in the Keyword Interface. Additional keywords have been added to the IDEA
Keyword Query Language (IKQL) in order to provide you with maximum flexibility
in developing and formatting the USR.
11.2 A Basic USR Request
The following sections detail how to get started using the User-specified Reporting
(USR) capability, by explaining how to write the simplest type of USR. This type of
USR is limited to requests for IDEA data elements and output from custom USR
functions, on what is called the Detail Line. Once we have described the overall
structure of a simple USR, we will describe how to customize such a report, by
adding a title, specifying your own column headings and widths, and formatting the
data.
Chapter 11. IDEA User-Specified Reports 11-1
-------
11.2.1 Report Layout
In a User-specified Report, the values retrieved for the data elements (or expressions)
that you request will appear in columns. In a basic User-specified report, which we
will consider to be limited to requests for IDEA data elements and output from
custom USR functions, the order and structure of the data on the Detail Line will
depend on the hierarchical relationships between the data values.
On the Detail Line, all data for a given facility will appear together, before data for
the next facility are shown. In the Linked portion, a "facility" is determined by an
EPA Identification Number (a value of FIN.EPID). In the Nonlinked portion, a
"facility" is determined by the local ID, or case number, at the top of the hierarchy of
the database in question (e.g., a value of AFS.AFSID or DCK.CSNO).
To better illustrate the hierarchical relationships that can occur between data values,
let us assume for the moment that all the columns in the report will contain the
values of data elements, and that these elements are all from the same database. If
data elements from more than one database are requested, the behavior described
below will happen independently in the columns from each database.
There are four levels of hierarchy in the IDEA Shadow Databases (See Table 11-1).
Each of the IDEA databases has been partitioned into disjoint groups, each of these
groups occupying one of these four levels. The level that a data element occupies in
the hierarchy is determined by the group to which it belongs.
Table 11-1. Levels of Hierarchy in IDEA Shadow Databases
Level
1
2
3
4
Description
Major- valued,
Major- valued,
Minor-valued,
Minor-valued,
Non-repeating Group
Repeating Group
Non-repeating Group
Repeating Group
In Appendix C, Data Elements in IDEA Shadow Files, groups on the major level are
marked with "(A)", and groups on the minor level, with "(B)". Groups containing
repeating fields have a "Y" in the REPEATING? column, an "N" otherwise.
The two most important groups in the hierarchy of a database are those containing
the primary major data element and the primary minor data element, which are on
levels one and three, respectively. The primary major data element, in most data-
bases, is the facility id, or case number, uniquely identifying a facility or case. The
values of (the primary minor data element divide the data that on the minor level for
11-2
IDEA User's Guide
February 29, 1996
-------
a single facility or case (a single value of the primary major data element) into disjoint
parts.1
Suppose, for example, we run a Linked query looking for TRIS polluters of heavy
metals into water, that are in reportable or significant noncompliance with PCS, and
requesting the data elements shown in Figure 11-1 .
&
-------
Figure 11-2. IDEA User Specified Report Output
The first set of values of the level three data elements that were requested (the
reporting year and chemical ID) print on the first line, and the level four values (the
release estimate, in pounds) associated with these level three values, if there are any,
will start on this line, and continue printing out until they are exhausted for this set
of level three values. On the following line, the next set of values for the level three
data elements is printed out, with the values of the level four data element associated
them starting to print out on this line, and continuing until exhausted for this set of
level three values. This process will continue until the level three (and four) values
are exhausted for this facility. Then the data for the next facility would begin.
Note that the only data that will appear is the data for the data elements you request.
Because we ran the query Linked, for example, all the facilities that were found have
FINDS IDs, even though we didn't print them out. Because of the contents of our
Select criteria, we also know that these facilities are either NCs or SNCs in PCS.
Futhermore, it should be noted that most of the release estimates printed are not for
the water medium. Be warned, however, that if you request the medium to be printed
out also (TRI.CREL), it will lengthen your report considerably (unless you do some-
thing clever with the RESTRICT keyword; see Section 11.3.1, Restricting Report
Data).
11-4
IDEA User's Guide
February 29, 1996
-------
11.2.1,1 Elements of a Basic USR Request
A basic User-specified Report request consists of the following elements, included in
the OUTPUT section of your query:
REPORT report-name
[TITLE "title"]
[HEADER OFF/JUSTIFY HEADINGS [L/C/R]] ,
DETAIL LINE
detailfieldl [HEADING][WIDTH][START[LENGTH]]...
detailfieldZ ...
etc.
Each of these elements will be explained in the following sections.
11.2.1.2 The OUTPUT Statement - Requesting a USR
Keywords: OUTPUT, REPORT
Syntax:
OUTPUT REPORT report-name
[USR specifications]
[output destination]
The OUTPUT statement is the sequence of keywords that instructs the IDEA system
on what report formats are desired and where the output should be directed. As
explained in Chapter 8, Conducting a Search Using Keywords, the basic OUTPUT
statement consists of the OUTPUT keyword followed by REPORT, the desired report
format, and instructions for redirecting the output. Additional report formats are
requested by repeating the REPORT keyword. (Review Section 8.6, Output Report
Selection, and Section 8.7, Specifying Report Destinations, for complete details.)
The name of a USR is provided by the user; e.g. MY-REPORT or VIOLATORS.
You can choose any name, subject to the following restrictions:
1. USR names can not contain any spaces.
Chapter 11. IDEA User-Specified Reports 11-5
-------
2. The designations 1A, IB, 2, and SUMMARY are reserved for the IDEA Standard
Reports (See Chapter 10, IDEA Standard Reports). Any other designation will
be interpreted by the IDEA system as a request for a User-specified Report.
The user-provided USR name will appear on the report as part of the standard IDEA
boilerplate, shown in Figure 11-3 below.
Figure 11-3. The IDEA Report Boilerplate
The specifications for the USR (i.e. all other USR keywords) must immediately follow
the USR name. Instructions for redirecting the output should be placed at the end of
the USR listing. For example, the statement:
OUTPUT REPORT 1A
REPORT MY-REPORT
(USR specifications)
PRINT
signals IDEA that the user wishes to view Standard Report 1A on the terminal screen
and that a USR called MY-REPORT is to be directed to the HOLD queue for
printing.
11.2.1.3 The Detail Line
Keyword: DETAIL LINE
Syntax: DETAIL LINE
datafieldl [HEADING/WIDTH/...]
datafield2 [HEADING/WIDTH/...]
etc.
11-6
IDEA User's Guide
February 29, 1996
-------
— Important! ———^—————————^—^—
The DETAIL LINE keyword is a required element in a USR request.
The Detail Line is an essential part of an IDEA User-specified Report request. It is
here that you specify the data fields you wish to use in your report. The arguments
that follow each data field (field modifiers) instruct the IDEA system on how you
want the data for the field to be displayed, if at all.
Three types of data fields can appear on the Detail Line: data elements, DEFINE
statements, and expressions. The sample USR query in Figure 11-8 shows an
example of each. !
DATA ELEMENTS
Data elements are specified in the same manner as your query selection cri-
teria: the 3-character database identifier followed by a period and the data
element name (dbi.element; e.g., FIN.EPID).
DEFINE STATEMENTS
DEFINE statements have the form:
DEFINE fieldname expression.
(See lines 4 through 8 in Figure 11-8 .) The name of a DEFINE field
(fieldname) must consist of only one word and can contain up to 11 charac-
ters.
Caution
DEFINE field names must be unique (within a given query)! If you
assign a different expression to a name that has already been used, you
will receive an error when you attempt to run your query.
EXPRESSIONS
An expression on the Detail Line can consist of any valid expression utilizing
parentheses, any numeric data elements accessed by IDEA, certain built-in
USR functions such as the ENFACTSQ function (Section 11.2.3, Custom
USR Functions), and the basic arithmetic operators: addition ( + ), sub-
traction (-), multiplication (*), and division (/).
• Note that a function by itself constitutes an expression.
• An expression need not be enclosed in parentheses.
• Any named field (dbi.element or a DEFINE field name) can be used
inside functions and expressions.
Chapter 11. IDEA User-Specified Reports 11-7
-------
11.2.2 Customizing a Basic USR Request
Many things can be done to improve the appearance of a User-specified report. A
title can be added to the top of each page. Columns can be modified in several ways:
headings can be whatever you like, and can be set to be right- or left-justified rather
than centered, and column widths can be increased or reduced. Or, if you intend to
use the data obtained in a spreadsheet, you may want to suppress printing of the
header after the first page.
11.2.2.1 Specifying a Report Title
Keyword: TITLE
Syntax: TITLE "Text of User-specified Title"
You can add a customized title to a USR using the TITLE keyword followed by the
desired text. Enclose the text in quotation marks if it consists of more than one
word. To create multiple lines or subtitles, repeat the TITLE keyword for each new
line. The following sequence in a USR request will produce the title in Figure 11-4 .
OUTPUT REPORT HEAVYMETALS
TITLE "Report on Facilities with TRI Releases of Some Heavy Metals"
TITLE "to Water, and PCS Reportable or Significant NonCompliance"
»,r, •^.".Tury-'i i<'^s.y
IMTESRAIEtf-DATA FJIClLJ'
.,. . -
-X - - -, l , ,, •',,":':"<'« I y}'\
REPORT QH • FA£3 LIl!|£S',1IlF
C C yL (( (H5\( «-I^ V t
Figure 11-4. USR with Customized Title
As shown in Figure 11-4 , the title will b e positioned below the report boilerplate,
which is centered across the first 80 columns for display on your terminal and across
the actual width of the report for printing.
11-8
IDEA User's Guide
February 29, 1996
-------
11.2,2.2 Controlling the Report Header
There are three parts to the header of an IDEA User-specified Report: the IDEA
report boilerplate, the user-specified report title, and the column headings (see
Figure 11-5).
sJ.,!J{A.{^.j,~..^,*$V* u~ ;£&,..(i,ji,&lwJ\ ,'< cjw« t!iT= A('t..(t (& :.. ,t <>& < c- ((
Figure 11-5. The IDEA USR Header
You can control the formatting of the header using the following keywords.
Keyword: HEADER OFF
Syntax: HEADER OFF
By default, the entire header appears at the top of each page of the USR. The
HEADER OFF keyword will cause the header to appear only once, at the beginning
of the report.
Keyword: JUSTIFY HEADINGS
Syntax: JUSTIFY HEADINGS L/C/R
This keyword is used to justify the column headings: L= Left, C = Center, R= Right.
If JUSTIFY HEADINGS is not specified, the column headings will be centered by
default.
Chapter 11. IDEA User-Specified Reports
11-9
-------
Note: The JUSTIFY HEADINGS keyword applies to the column headings only. It
has no effect on the other two components of the report header, nor does it
determine the justification of the data within the column (see JUSTIFY,
Section 11.2.2.3, Formatting the Report Data).
11.2.2.3 Formatting the Report Data
Keyword: HEADING
Syntax: {datafield} HEADING "Column Heading"
The data in IDEA User-specified Reports are arranged in columns - one column for
each data field to be displayed (see Section 11.2.1, Report Layout, for details). You
can specify a column heading for each data field in your USR by using the
HEADING keyword.
• Enclose the text of your column heading in quotation marks if it consists of more
than one word.
• To create multiple lines or subheadings, repeat the HEADING keyword for each
new line.
If you do not specify a custom column heading, the default heading will be the field
name (dbLelement or Define_name). If the field consists of a plain expression, the
default heading will be the expression itself.
Keyword: WIDTH
Syntax: {datafield} WIDTH n
WIDTH specifies the number of positions to be reserved for the column width. This
keyword can be used to truncate lengthy data fields or to create extra space between
columns in your report. (By default, 1 space will automatically be inserted between
columns.)
11-10 IDEA User's Guide
February 29, 1996
-------
The default width for a given column is the greatest of the length of the column
heading, the substring length (see LENGTH below), if specified, and the external
length of the data element (see Appendix C, Data Elements in IDEA Shadow Files, for
listings).
Keywords: START, LENGTH
Syntax: {datafield} START n [LENGTH m]
START and LENGTH specify that only a portion (substring) of the data value is to
be printed.
— Warning! ————————————^——.^_^__^_^__
The START and LENGTH keywords apply to character data fields only. (See
Appendix C, Data Elements in IDEA Shadow Files, for data types of IDEA data
elements.)
START denotes the position in the data value (counting from the left) from which to
start printing; the default is position 1.
LENGTH denotes the length of the substring (the total number of positions) to print;
the default is the external length of the data element.
• The length of a substring must be less than or equal to the column width, if speci-
fied using the WIDTH keyword. ,
• If WIDTH is not specified, the width of the column will be the greater of the
column heading length and the substring length.
— Warning! ——^—•^————-^————^——^——^——-^—-—
The substring length must be less than or equal to the external length of the data
element. If you specify a greater length, you will receive an error when you
attempt to run your query.
Keyword: JUSTIFY
Syntax: {datafield} JUSTIFY [L/C/R]
Chapter 11. IDEA User-Specified Reports
11-11
-------
JUSTIFY determines the positioning of the data value within the column - L= Left,
C= Center, R= Right. If JUSTIFY is not specified, the default justification is right-
justification for numeric data fields and left-justification for character fields.
Note that JUSTIFY will determine the justification of the data within the given
column only; the justification of the column heading is controlled using the JUSTIFY
HEADINGS keyword described in Section 11.2.2.2, Controlling the Report Header,
above.
Keyword: DECIMALS
Syntax: {datafield} DECIMALS n
DECIMALS specifies the number of digits to the right of a decimal point to be
printed. This keyword can be used to modify numeric data fields only. Figure 11-6
shows the initial example, with some customizing. Notice that the HEADING
keyword has been used repeatedly for several of the columns, to create column
headings having multiple lines.
808001 8WPUT
588882 TITLE "Report «nr,,Ff
000003,TITtE "to "" ~~"*"'
B08BB* DETAfL LIKE
688886 TRI,STeB
0(30067 -WJ
' 0S8810
f 000011 INPUT;
" 808812 '
800013
B888I4
I-000015
V'80SBI6
•i 000017 )
088818'/
• 000819
808826 /*
000.021
i .088822
Figure 11-6. Simple USR with Title and Formatting
11-12 IDEA User's Guide
February 29, 1996
-------
The output for this request is shown in Figure 11-7 .
^^^^B^Sft^t^.^^ll^^S/11^
Figure 11-7. Simple USR with Title and Formatting
11.2.3 Custom USR Functions
The following functions provided with the User-specified Reporting capability add
two useful time-saving features to USRs. ENFACTS gives you a count of enforce-
ment actions recorded for a single FIN.EPID, for which you would otherwise need to
run a separate USR. TEXT gives you English translations of the codes for many
IDEA data elements.
Both of these functions can be used on the Detail Line. The value that ENFACTS
returns will be printed on the same level as the FIN.EPID for the facility. The text
description returned by TEXT will be printed on the same level as the argument.
Chapter 11. IDEA User-Specified Reports
11-13
-------
Function: ENFACTSQ
Syntax: ENFACTS (database, acting agency, number of years)
Valid Inputs:
Database: AFS, DCK, NCD, PCS, RCR
Acting Agency: F (federal) or S (state)
Number of Years: any integer between 1 and 10
The ENFACTS ("enforcement actions") function returns, for the given database, the
number of federal or state enforcement actions (judicial and administrative) against a
facility in the specified number of years (computed from the current month). For
example, Figure 11-8 shows a USR request using the ENFACTS function.
:ee,9BB2 DETAIL ui^.jirjr
I&*^Mek##M8i&cit&lf. ggg^ijij J l^ gjj^
V ti ^it£. . {J i * A'f5 P * A' %MJjx
-------
Function: TEXTQ
Syntax: TEXT (dbi. element)
Valid Inputs: Any data element (dbi.element) that has a decoding table in IDEA,
or can use another data element's decoding table. (See the dis-
cussion below on how to see a list of decoding tables.)
The TEXT function takes a value for the specified data element, looks up the value in
the decoding table for the element, and returns an English-language description of the
meaning of the given value. If the specified value is not found in the decoding table
for the data element, the value itself will be returned.
Figure 11-9 shows the output from Figure 11-6 , if TRI.TCID is replaced by
TEXT(TRI.TCID) WIDTH 15.
Figure 11-9. Using the Text function
Chapter 11. IDEA User-Specified Reports
11-15
-------
To see a listing of data elements that have translation tables, type TEXT INFO at the
Command prompt. (See Figure 11-10.)
******
saaa&i
86*8852 TITLE "REPUTE
$a0ea3 TiTLrB?8'*
809854 BEJAIL LINE
80 W5
808836
m
8088B8 TfS
'HBffll ' TRIJS,
' '
INPUT
'808812 { t*
'; 609613
'- 8S88I4- (
-------
Vf^^S^^if. .fm^m\ri^.-"''. ifsiV"J
Figure 11-11. Top of Decoding Tables List
The same navigational tools available in report browsing are available here. Hit PF8
to page down through the list, and PF7 to page up. Type FIND 'string' to go to a
particular place in the list (e.g., type FIND 'TRI' to go to the TRI data elements in
the list). Hit PF5 to repeat a find action. Hit PF3 when you're done looking at the
list.
The decoding tables themselves may be browsed by typing TEXT dbLelement at the
Command prompt and pressing < Enter > ..
11.3 Controlling USR Report Output
Once use of basic USR requests has been mastered, the user may want to learn how
to use some of the features provided with the User-specified Reporting capability for
manipulating the output in more dramatic ways than those described above. The
features described in the following sections enable users to:
1. restrict the data printed to only values they are interested in,
2. sort the data printed into a useful ordering, and
Chapter 11. IDEA User-Specified Reports
11-17
-------
3. request summary information on sorted output.
11.3.1 Restricting Report Data
Keyword: RESTRICT
Syntax: RESTRICT
dbi.element {operator} (list of values}
[AND/OR dbi.element {operator} {list of values}]
etc.
Valid Operators: =, EQ, LT, GT, LE, GE, IN, MOD
The RESTRICT section can be used to restrict the output of the report to only those
values of the data elements that you are interested in. This capability is especially
useful in eliminating unwanted level three (and their corresponding level four) data
values from a report.
I Note
It is important to remember the difference between your SELECT criteria and
your RESTRICT section. Your SELECT criteria selects the facilities for which
you want report(s). Your RESTRICT section limits the data that is printed on
those facilities. Never use the RESTRICT section to do what should have been
done in your SELECT criteria.
11-18 IDEA User's Guide
February 29, 1996
-------
f?l?,wiflHi!^f®'l w «*SP«I?
s.'.'^-hf"<.i''. ' I !& *.&
Ls? £ .MUfs "BsS'i stLS\i5t> ^ft--*^-i^fk*:ij*-n-fti.rt •±**-£*-r**p^'£**i
Figure 11-12. RESTRICT Keyword Section
In Figure 11-12 we use the RESTRICT keyword to restrict the output to heavy
metals we are interested in, to data after 1989, and (this is the "clever" use of
RESTRICT mentioned earlier) to prevent release media with no release amounts
from printing.
Chapter 11. IDEA User-Specified Reports
11-19
-------
Figure 11-13. Use of Restrict Keyword
11.3.2 Sorting the Report Data
Keyword: SORT
Syntax: {datafield} SORT [A/D]
The SORT keyword is used to order the values of the data field it modifies ~
A=Ascending, or D = Descending. If neither A nor D is specified, the default is to
sort the values in ascending order.
SORT can be used to modify any data field on the Detail Line.
The hierarchy of the SORT fields (i.e. the precedence with which they are sorted) will
be determined by the order in which they are specified. For example, the first
11-20 IDEA User's Guide
February 29, 1996
-------
sequence shown below will sort the data for the retrieved facilities by reporting year
in ascending order and then by TRI Chemical Name in ascending order. The second
sequence will sort the data for the facilities first by chemical, then by reporting year.
(Compare Figure 11-14 and Figure 11-15.)
DETAIL LINE 1
TRI.RPYR SORT
TRI.NAME SORT
Figure 11-14. Sorting by Reporting Year, then Chemical
DETAIL LINE
TRI.NAME SORT
TRI.RPYR SORT
Chapter 11. IDEA User-Specified Reports
11-21
-------
p7. rrrp --_„* .<-,-,<« .sr«.r
t ' L , ! r f ~- ' t'Kii" , < r'| ^'V^'X "'i'^
1 'W.owi«orj «AiJJt , .:.'..,,.'-••'.';,
''ALUHlHilH'oXIOi , ,,^X;'
-------
I Note
It is important to remember the difference between fields on the Summary Line
and fields on the Detail Line. Summary Line fields will only be displayed at each
change in the value of a SORT field, therefore the Summary Line summarizes the
information on the Detail Line. Whereas items on the Detail Line apply to
facility data, items on the Summary Line generally encompass multiple facilities.
The same three types of fields - data elements, DEFINE statements , and expressions
- that appear on the Detail Line can also be used on the Summary Line subject to the
following restrictions:
1. DEFINE fields from the Detail Line and data elements (dbi.element) can stand
alone, or be part of a numeric expression, on the Summary Line only if they are
specified as SORT fields on the Detail Line. However, any data element or
DEFINE field can be used within a statistical function on the Summary Line.
2. Each DEFINE field name must be unique. DEFINE names used on the Detail
Line can not be re-defined on the Summary Line.
3. Expressions on the Summary Line can consist of any valid combination of paren-
theses, the basic arithmetic functions, the IDEA statistical functions COUNTQ
SUM(), MEANQ, MAXIMUMQ, MINIMUMQ, and STDDEVQ (see Section
11.3.3.1, Statistical Functions), as well as the built-in USR function ENFACTS
(see Section 11.2.3, Custom USR Functions), if it is a SORT field, and the
NOB REAK keyword (see Section 11.3.3.2, Controlling Where Summary Informa-
tion Appears) is not used. ,
Data fields on the Summary Line will accept a subset of the field modifiers accepted
by fields on the Detail Line, subject to some restrictions. These are: SORT
HEADING, WIDTH, START, LENGTH, JUSTIFY, and DECIMALS. (See
Section 11.2.2.3, Formatting the Report Data, for details.)
— Caution '
The SORT keyword may be used on the Summary Line only if the entire sup-
pressed, using SORT on the Summary Line will cause an error when you attempt
to run your query.
11.3.3.1 Statistical Functions
• With the exception of COUNTQ, the statistical functions listed below are for use
with numeric data fields only. (See Appendix C, Data Elements in IDEA Shadow
Files, for a listing of data element types.)
• IDEA statistical functions can be used only on the Summary Line.
Chapter 11. IDEA User-Specified Reports 11-23
-------
IDEA statistical functions operate on the values of the specified field occurring
since the last break. If you do not declare any SORT fields having summary
breaks on the Detail Line, these functions will operate on the values of the given
field across all facilities in the report. The arguments for the statistical functions
do not need to appear on the Detail Line.
Function: COUNTQ
Syntax: COUNT (summaryfield)
Usage: Summary Line only
The COUNT function counts the number of non-blank occurrences of the specified
field in the column (potentially across facilities) since the last summary break. For
example, the query syntax:
DETAIL LINE
TRI.RPYR SORT .
TRI.TCID
SUMMARY LINE
TRI.RPYR
COUNT(TRI.TCID)
might result in the output shown in Figure 11-16 :
11-24 IDEA User's Guide
February 29, 1996
-------
Figure 11-16. Using COUNTQ on the Summary Line
Funtion: SUM()
Syntax: SUM (summaryfield)
Usage: Summary Line only
The SUM function adds up the data values of the indicated field occurring since the
last summary break.
Functions: MAXIMUMQ, MINIMUMQ
Syntax: MAXIMUM (summaryfield)
Syntax: MINIMUM (summaryfield)
Usage: Summary Line only
Chapter 11. IDEA User-Specified Reports
11-25
-------
MAXIMUMQ and MINIMUMQ return the maximum and minimum value, respec-
tively, of the specified field occurring since the last summary break.
Function: MEANQ
Syntax: MEAN (summaryfield)
Usage: Summary Line only
This function computes the mean, or average, value of the given field since the last
summary break.
Function: STDDEVQ
Syntax: STDDEV (summaryfield)
Usage: Summary Line only
The STDDEV ("standard deviation") function computes the standard deviation of the
values of the given field occurring since the last summary break.
In the following example, we take the data printed out in Figure 11-13 , sort it by
reporting year, release chemical, and release media, and request summary information
using some of the functions from this section. (See Figure 11-17.)
11-26 IDEA User's Guide
February 29,1996
-------
rsi ,'ftf frft&ftiyg%s
Figure 11-17. USR With Request for Summary Information
Some of the output for the USR request in Figure 11-17 is shown in Figure 11-18 .
Figure 11-18. USR Output With Summary Information
Chapter 11. IDEA User-Specified Reports 11-27
-------
11.3.3.2 Controlling Where Summary Information Appears
Summary information requested on the Summary Line will appear by default at each
change in the value of a SORT field, interspersed throughout the Detail Line output,
after which the Detail Line output will resume. The keywords in this section make it
possible to change these defaults.
Keyword: NOBREAK
Syntax: {datafield} SORT [A/D] NOBREAK
The NOBREAK keyword is used to signal the IDEA system that you do not wish to
display summary information each time there is a change in the value of the modified
SORT data field.
If you do not break on any SORT fields, but you do specify SUMMARY LINE
fields, the Summary will appear at the end of the report.
Keyword: PAGE
Syntax: {datafield} SORT [A/D] PAGE
The PAGE keyword will instruct IDEA to start a new page whenever there is a
change in the value of the modified data field. PAGE can only be used with fields
that have been sorted using the SORT keyword. The keywords NOBREAK and
PAGE cannot be used to modify the same SORT field.
Keyword: SUPPRESS
Syntax: DETAIL LINE [SUPPRESS]
•
SUPPRESS is an optional argument to the keyword DETAIL LINE. It will suppress
the display of all DETAIL LINE fields, allowing you to view only summary informa-
11-28 IDEA User's Guide February 29, 1996
-------
tion. Figure 11-19 shows the report generated by the sample query in Figure 11-17
with its Detail Line suppressed (compare with Figure 11-18).
' i'
-------
Chapter 8, Conducting a Search Using Keywords, and Chapter 9, Managing Keyword
Queries and the ISPF Editor for a more detailed treatment of the subject.
11.4.1 Report Design Considerations
The keywords described in this chapter have been developed to provide you with
maximum flexibility in constructing user-specified reports. Because the options are so
numerous, careful planning is required in order to produce a meaningful, useful
report.
Of primary concern is the order in which the data values will appear. Do you want
to order or sort the records so that they can be grouped by common values of a
particular data element? For instance, would it be beneficial to have the report sorted
first by state and then by facility name? If so, list the state field (e.g. FIN.STAT)
first on the Detail Line, then the name field (e.g. TRI.HNME), and follow each with
the SORT keyword.
You should also consider whether or not you want summary information to appear
when there is a change in the value of the sorted field. If you do not, you must
follow the sorted field with the NOBREAK keyword. Use the SUMMARY LINE
keyword to tell the system that you want a count, sum, or other function(s) per-
formed and the results displayed.
You have now determined the organizational structure of your report and are ready
to add other features to enhance its appearance and readability.
At this point you should think in terms of the data elements you want to appear on
the report and consider, for each element, the width of the column. Keep in mind
that for each data element specified, a column will be reserved for the data to print.
Some data elements, like facility name, can be defined as 40 or even 60 characters. It
is frequently unnecessary to print all of the characters. For example, you may wish
to print only the first 20 or 30 characters. Naturally, if you do not wish to specify a
width, the length specified in the database will be used (see Appendix C, Data Ele-
ments in IDEA Shadow Files, Length column).
Use the HEADING keyword to add a column heading for each data element
(column) requested. Like the TITLE keyword, HEADING can be used multiple
times to produce a multi-line column heading. As an example, suppose that state is
one of the data elements requested and you wish to keep the column only 2 charac-
ters wide. You could request a heading as follows:
HEADING S HEADING T HEADING A HEADING T HEADING E
11-30 IDEA User's Guide February 29, 1996
-------
This will cause the word STATE to be printed vertically.
To have the data values centered, or right- or left-justified in the column, use
JUSTIFY; to have only a particular portion of a value printed, use START and
LENGTH; and to indicate the number of decimal places for a numeric value, use
DECIMALS.
Use these and the other field modifiers to create your most readable and informative
report. '
11.4.2 Preparing a Query in the ISPFfPDF Editor
USR requests must be added to a query using the ISPF/PDF editor. To reach the
ISFP EDIT SCREEN, you must choose the Keyword Interface option from the
INTERFACE SELECTION SCREEN. IDEA will then ask you to select a library in
the INPUT LIBRARY SELECTION SCREEN, shown in Figure 11-20 .
r— Caution
When working in the INPUT LIBRARY SELECTION SCREEN, do not press
< Enter > until you are finished editing the options on the screen; otherwise,
IDEA will take you to the next screen. If < Enter >. is pressed accidently, press
PF3 or type END at the COMMAND prompt and press < Enter > to return to
the INPUT LIBRAR Y SELECTION SCREEN.
Figure 11-20. Library Selection Screen
Press < Enter > to accept the default values listed at the LIBRARY NAME and the
LIBRARY STATUS(Shr/New/Old) prompts, or choose a different library as directed
in Section 5.1, Selecting an IDEA Library. The MEMBER LIST SCREEN for the
given library will appear (see Figure 11-21). (If you have not created any queries in
this library up to now, there will be no entries under the headings.)
Chapter 11. IDEA User-Specified Reports
11-31
-------
MEMBER LIST -.
, COMMAND =«i>'
, USE "BX
QUERY3
QUERY?
,, QUER¥&
Figure 11-21. Member List Screen
Section 5.2, Managing Queries Using the Member List, explains the commands that
allow you to browse, create, retrieve, rename, describe, and delete the queries in your
Member List. These commands are repeated below in Table 11-2 for your conven-
ience. They should be typed to the left of the member name or at the COMMAND
prompt followed by a space and the member name.
Table 11-2. Library Member List Commands
B query
E (or S) query
R query
U query
D query
Browse/Read the query; no editing possible.
Edit/Select an existing query or create a new one in
the editor.
Rename the query.
Update the query description.
Delete the query from the MEMBER LIST.
You can add a USR request to an existing query by typing E or S next to the query
name, or you can choose to work with a brand new query. To create a new query,
type E at the COMMAND prompt, press < Space >, and type the name of the new
query (for example, E USRQUERY)-
— helpful hint
Query names can be up to eight characters long. They can include numbers and
letters, but not special characters such as @#$%\ -•&*()"?/!.
After you make your selection on the MEMBER LIST SCREEN, press < Enter >,
and the EDIT SCREEN will appear. If you chose to create a new query, the EDIT
SCREEN will be empty. You can use GO Names (Chapter 6, Conducting a Search
11-32 IDEA User's Guide
February 29, 1996
-------
Using GO Names) and/or GO MenuA (Chapter 7, Conducting a Search Using GO
MenuA) to construct your query, or you can type the query in by hand. If you select
an existing query from the Member List, it will be displayed on the EDIT SCREEN,
as shown in Figure 11-22 .
Figure 11-22. Example Query in the ISPF Edit Screen
11.4.3 Adding the USR Request to the Query
The syntax for your USR request discussed in this chapter should follow the
OUTPUT keyword in your query. Every USR request will contain the keywords
REPORT and DETAIL LINE, but can vary considerably otherwise. The overall
structure of a USR request, with optional ingredients in brackets, is as follows:
OUTPUT REPORT report-name
[TITLE "title"]
[HEADER OFF/JUSTIFY HEADINGS] ,
DETAIL LINE [SUPPRESS]
dbi .element/expression [SORT[NOBRiEAK/PAGE]/WIDTH/...]
etc.
[SUMMARY LINE
summaryfield [SORT/WIDTH/HEADING/...]
etc.] ;
[output destination]
Chapter 11. IDEA User-Specified Reports
11-33
-------
Inserting your USR request, in with your standard report request(s), can be accom-
plished with the line edit commands discussed in Section 9.2, Keyword Queries and the
ISPF Line Editor. (See Table 11-3.)
Table 11-3. Line Edit Commands
I Insert a line
D Delete this line
C Copy this line
M Move this line
R Repeat this line
A Place after this line
B Place before this line
X Exclude a line
11.5 Running Queries and Viewing Reports
To run your query, use < Home > or < Tab > to move your cursor to the
COMMAND prompt on the EDIT SCREEN, type GO, and press < Enter >. IDEA
will process the query and display the QUERY STATUS SCREEN shown below in
Figure 11-23 . On this screen, IDEA displays the following: the time of day when it
finished running the query, the number of facilities found in the search, whether or
not they are in FINDS (i.e., have valid FINDS identification numbers), and a chart
indicating the databases relevant to the search. This chart varies for Linked, Non-
linked, and Linked Nonlinked queries.
11-34 IDEA User's Guide
February 29, 1996
-------
Figure 11-23. Query Status Screen
In the case of Linked and Linked Nonlinked searches, the chart contains a combina-
tion of "counts" and percentages for each database relevant to a search. The counts
are the number of facilities that meet at least one of your criteria for that database
but do not have valid FINDS identification numbers. The percentage measures these
counts with respect to the total number of facilities meeting at least one of your cri-
teria in that database (including both facilities with and without valid FINDS identifi-
cation numbers). This chart allows users to gauge the percentage of facilities
excluded from a search due to missing FINDS linkages.
Because Nonlinked searches do not access FINDS, the chart in this case contains the
facility counts but not the percentages. For more information on the relationship
between a query and the number of facilities selected, refer to Chapter 2, IDEA:
What it Does & How it Works.
If you are satisfied with the number of facilities selected by your query, press
< Enter > and IDEA will deliver the information to your screen according to the
report format(s) designated on the OUTPUT line of your query.
Reports are presented to you in BROWSE mode, which allows you to view, print, or
save data, but not alter it (see Figure 11-24).
Chapter 11. IDEA User-Specified Reports
11-35
-------
BROWSE -
..
Issue eoa»Bftd
. _ „ ™t?ew. 1^1 ii-jC,! j 1, 3^{J
4-1 '„ ' / ^'iK^-Tt
* L „ c' ! El- ll-1'' ' "(" ' '*' *~!'CtP \ ^'S-S'
. 4J"r;,;r;;^|||tg
- , •>-.*: «,:i;J'W-MW-s
= -. .--='-;-.-^-,;4,^,4&,j?s,
," i - - ,-, c, -t^ >r J <* ?•
-,| ,,-,,,'•!. ,,,^,^-^y^^
': ", , J.V-1 - -2
' ' -•' j-"s'" <- ... ^V-^ •
..REPORT „
^..Wffi^gjEgll
''•'I FIN" EPIO'^-VTT^i-r
" 2 FIN ' '" " -"!'J""'"
" 3 TRI
4 m . icnr .;";;,;,v^^i
S TRI,,, MREST " " " ""
it-6 rar , Hfl^^, ;;;•:•. ^.r..^^^,^;^
'„? ',", BEUEASE r.^i*^^1^^
• 8 ' TO SREi •"." "l>4 -y^<^»^«*
Figure 11-24. Viewing a USR in Browse Mode
Regardless of the report format(s) selected, the title line of the BROWSE SCREEN
will provide the following information:
BROWSE the mode you are in
REPORT the report format you selected
IN PROGRESS/COMPLETE the status of your report .
MAX
the number of lines currently in your report
LINE
the number of the first line visible on the screen
COL
the range of columns you are currently viewing
If you selected multiple report formats, type SW (switch) at the COMMAND prompt
and press < Enter > to switch to the next report.
Use the commands in Table 11-4 to view your report in the BROWSE mode.
11-36 IDEA User's Guide
February 29,1996
-------
Table 11-4. Commands for Navigating Reports
Commands
Descriptions
UP PF7/PF19
DOWN
PF8/PF20
LEFT
PF10/PF22
RIGHT
PF11/PF23
END PF3/PF15
SWAP
PF9/PF21
MANEUVERING
Arrow keys
M(ax) + UP
M(ax) +
DOWN
M(ax) +
RIGHT
M{ax) + LEFT
Scrolls up by the amount set at the SCROLL prompt, or by the number of lines
entered at the COMMAND prompt.
Scrolls down by the amount set at the SCROLL prompt, or by the number of
lines entered at the COMMAND prompt.
Scrolls left by the amount set at the SCROLL prompt, or by the number of
lines entered at the COMMAND prompt.
Scrolls right by the amount set at the SCROLL prompt, or by the number of
lines entered at the COMMAND prompt.
Saves and returns to the previous screen.
Moves the cursor from a position in one screen to the same position in another
using the split-screen mode.
THE CURSOR
Use arrow keys for all directions
Use < Tab > key to move to the next input field.
Use < Home > to move to the top-left input field.
Scrolls up to the first top line of a report;
Scrolls down to the last bottom line of a report;
Scrolls to the right marge of a report;
Scrolls to the left marge of a report.
11.6 Printing Reports
Query reports may be printed after a "COMPLETE" report is generated. Check
the center of the BROWSE SCREEN'S title Me for the word "COMPLETE."
This will indicate that IDEA has finished processing the query report. If "IN
PROGRESS" is displayed, press < Enter > every few seconds until "COMPLETE"
appears. IDEA allows users to print part or all of a report by specifying line
numbers (see Figure 11-25). .
Chapter 11. IDEA User-Specified Reports
11-37
-------
, 1 '~-f'''^^^^^fA''f&'f,ft^l'f'4^nfvtK»''iMVS •«SN4i!
. ALBB881615SB T. ft.; Ml llERMU Cife Q r;1,;.;^feOMJ^
'i , , .-:__"!.«.,j> Mifrps hatT|ii'C^1v^^^*A;',''"'''';1
••'...,,« jjj • ^ ,,_,j * K |i^ t,i^K,,vy 4,gy,, -j ; ,• s, ,S,.,,TV s < , & ^i*s \«
: ..'., .,T fRaatKMLd**Jir^^M«*j5a^,
Figure 11-25. A "Complete" USR
2. Type PRINTO at the COMMAND prompt and press < Enter >. The
PRINT/SAVE PARAMETER SCREEN will pop up (see Figure 11-26).
Figure 11-26. Print/Save Parameter Screen
3. IDEA allows users to print part or all of a report by specifying line numbers. To
print the entire report, type 1 at the FROM LINE NO. prompt and press
< Tab >. At the TO LINE NO. prompt, type the MAX number that appears at
11-38 IDEA User's Guide
February 29, 1996
-------
the upper right corner of the BROWSE screen and press < Tab > . The MAX
number corresponds to the final line of the report when it is "COMPLETE".
4. IDEA also allows users to print just a portion of the report. Printing only part of
a report is useful if a complete report contains unneeded information. Within the
BROWSE mode, a continuous block of information can be printed. For example,
lines 1 through 23 can be printed. However, you cannot print lines 1 through 23
and lines 46 through 69 at the same time. To print a portion of the report, type
in the number of the first line of the block to be printed and < Tab > to the TO
LINE NO. prompt. Type the ending line number and press < Tab >.
5. At the FOR PRINTING - BIN prompt, type your site specific BIN number and
< Tab > to the DESTINATION prompt. Type your site specific printer destina-
tion ID (or press < Tab > to send your print to the HOLD queue) and < Tab >
to the NO. OF COPIES prompt. Type the number of original copies you wish to
receive and press < Enter >. The default setting for print destination is HOLD
and the default for the number of copies is 1.
| helpful bint
If you choose to send your output to the HOLD queue (or if you press
< Enter > too early and send it there by mistake), you must then let the
system know to which printer you want the output to be routed by using the
System Display and Search Facility (SDSF).
Take the following steps to release your print job from the HOLD queue:
1. To access SDSF, type SDSF at the COMMAND line of any Keyword screen.
This will bring up the SDSF Primary Option Menu pictured in Figure 11-27 .
Chapter 11. IDEA User-Specified Reports 11-39
-------
PREFIXED*.
Type an option
Figure 11-27. SDSF Primary Option Menu Screen
2. Type O at the COMMAND prompt and press < Enter > to "display jobs in the
JES2 output queue." Look for your user ID and batch job number (JOBxxxxx)
under the JOBNAME and Jobid headings, as in Figure 11-28 .
SUSP OUTPUT
•COMMAND INPUT
MP 006NAME
OID24' JOBB722&
Figure 11-28. SDSF Output Queue Screen
3. Press < Tab > to move the cursor down to your print job, then over to the DEST
column. The text should read R255, which simply means that your print job is in
the HOLD queue. Type over R255 with the identification number of the printer
at your site or one of the options listed below, and press < Enter > two times.
Destination options:
WIC Prints at the Washington Information Center (WIC) at EPA Head-
quarters, Washington, DC.
11-40 IDEA User's Guide
February 29,1996
-------
LOCAL Prints at the National Computer Center (NCC), Research Triangle
Park, NC.
RMTO
Same as LOCAL.
R + RP# Prints at the designated remote printer. Here RP# is the ID for the
remote printer. To view a list of the remote printers available to
IDEA users:
a. Exit IDEA and type ISPF 3.4 at the TSO READY prompt. The
DATA SET LIST UTILITY SCREEN will appear.
b. Type JUSD.REMOTE.DATA at the DSNAME LEVEL prompt;
press < Enter >. The DS LIST SCREEN will appear.
c. < Tab > down and type B (Browse) next to the
JUSD.REMOTE.DATA member. Press < Enter > to view the
list of remote printers.
d. When you are finished, use the RETURN command (PF4) to go
to the ISPF/PDF PRIMARY OPTION MENU. Type X to return
to the READY prompt
helpful hint
The first time you press < Enter > in step 3 a message reading COMMAND
ISSUED will appear in the upper right hand: corner of the screen, and the
printer destination you just typed in will change back to R255. Don't panic!
When you press < Enter > the second time, the correct destination will again
be displayed. (Compare Figure 11-29 with Figure 11-30 .)
Figure 11-29. SDSF Output Queue - "Command Issued" Screen
Chapter 11. IDEA User-Specified Reports
11-41
-------
' SDSF OUTPUT ALL' cisssfesV M:
'--eOtWID INPOT,- ""'"
^NP JDBNUE %MJid
Figure 11-30. SDSF Output Queue - Print Destination Changed Screen
If you decide not to print your job, type a P (Purge) under the NP column on the
line of the job you want to cancel; press < Enter >. Warning: a purged record
can not be recovered.
4. To exit SDSF, use the END command or PF3 two times. You will return to the
Keyword screen from which you issued the SDSF command in step 1.
11.7 Savins Reports
1. Query reports may be saved after a "COMPLETE" report is generated. Check the
center of the BROWSE screen's title line for the word "COMPLETE." This will
indicate that IDEA has finished processing the query report. If "IN PROGRESS"
is displayed, press < Enter > every few seconds until "COMPLETE" appears.
Position the cursor at the COMMAND prompt.
2. Type SAVE at the COMMAND prompt and press < Enter >. The
PRINT/'SAVE PARAMETER SCREEN will pop up (see Figure 11-26).
3. IDEA allows users to save part of a report or all of it. Saving only part of it is
useful if the complete report contains unneeded information. However, BROWSE
mode offers limited saving options. Only a continuous block of information can
be saved. For example, you can save lines 5 through 20, but not lines 5 through
20 and lines 30 through 40 at the same time using this facility. You may save to a
dataset (Step 4) to perform more advanced editing.
To save a block of the report, at the FROM LINE NO. prompt, type in the
number of the first line in the block to be saved or type 1 to start at the beginning
of the report. Press < Tab > . At the TO LINE NO. prompt, type the last line
number of the block to be saved or type in the MAX number which appears at
the upper right of the BROWSE screen and press < Enter >.
4. At the FOR SAVING ENTER DSN OR DSN (MEMBERNAME) prompt, a
dataset or membername must be entered to identify the name of this report and
where it will be stored.
11-42 IDEA User's Guide
February 29, 1996
-------
11.8 Exitins Reports
Type END at the COMMAND prompt or press PF3 to return to the EDIT SCREEN
after viewing, printing, and/or saving your report(s).
To exit the Keyword Interface at any time, you have the following options:
• To save your current query, use the END command (PF3 key) to back out of the
program screen by screen.
• If you wish to exit without saving your work, type CANCEL at the COMMAND
prompt of the EDIT SCREEN, then use END or PF3 to back out screen by
screen.
• Use the RETURN (PF4) command to return to the OFFICE OF ENFORCE-
MENT DATA INTEGRATION PRIMARY MENU (your current work will be
saved). You can then type I for IDEA at the OPTION prompt to get back to the
IDEA WELCOME SCREEN or type X to exit to the TSO READY prompt.
•
• To go directly to the TSO READY prompt, type =X at the COMMAND,
prompt. (Your work will be saved automatically.)
11.9 Summary
In addition to offering a selection of pre-defined Standard Reports, the IDEA system
provides its users with a facility for creating customized columnar reports, called
User- specified Reports or USRs. The USR capability allows users to specify what
data will appear in the report, how the data will be ordered, what kind of summary
information will be generated, and how the report will be formatted.
User-specified Report requests are added to queries in IDEA'S Keyword Interface via
the ISPF editor and, like the queries, are written using the IDEA Keyword Query
Language. The set of USR keywords has been designed to provide maximum versa-
tility in specifying the content and appearance of reports. For this reason, successful
user-specified reporting requires careful planning and design. Users should consider
the report's intended purpose, the order in which the data will be most effectively
presented, and the overall appearance and readability of the report. Familiarity with
the EPA program offices and knowledge of the data contained in the corresponding
IDEA databases is also helpful in choosing appropriate data to display in the report.
Chapter 11. IDEA User-Specified Reports 11-43
-------
When these considerations are taken into account, User-specified Reports allow
IDEA users create meaningful and useful reports with a personal touch.
11-44 IDEA User's Guide
February 29, 1996
-------
Appendix A. Access and Security Procedures for IDEA
The following information details the procedures for obtaining access to enforcement
sensitive data in IDEA and security requirements. This information includes the
IDEA policy memorandum, which was originally published in October 1991 by
Gerald A. Bryan, Director, Office of Compliance Analysis and Program Operations.
Following the policy memorandum are sample access memoranda that authorize indi-
vidual EPA User-IDs to gain Sensitive Access to IDEA. Revisions to the original
procedure have been "redlined".
The IDEA system supports two levels of access to the EPA program office enforce-
ment data: Non-sensitive Access and Sensitive Access. This two-tiered level of
access is in accordance with EPA communication policies that encourage broad
access to information. OE in conjunction with each national system administrator
has identified the data that each program office has determined is enforcement sensi-
tive, i
NON-SENSITIVE ACCESS
Non-sensitive Access is granted to persons or agencies, which includes other Federal
and State agencies, who have a valid EPA mainframe User-ID. However, access to
enforcement sensitive data is blocked while access to all other relevant enforcement
data is allowed.
SENSITIVE ACCESS
Users authorized for Sensitive Access are governed by the provision of EPA Order
3120.1 (issued September 20, 1985). This Order, entitled "Conduct and Discipline,"
and its Attachment, entitled "Guidance on Corrective Discipline," prescribe policies
and penalties regarding breaches of security regulations or practice.
The policy memorandum describing the Access and Security procedures for IDEA is
reproduced in its entirety below.
Appendix A. Access and Security Procedures for IDEA A-1
-------
MEMORANDUM
SUBJECT: Access and Security Procedures for EPA's
Integrated Data for Enforcement Analysis (IDEA) Capability
FROM: Gerald A. Bryan, Director
Office of Compliance Analysis and Program Operations
TO: Deputy Regional Administrators, I - X
Headquarters Enforcement Office Directors
Acting Deputy Assistant Administrator
Enforcement Counsels
Regional Counsels, I - X
Office of General Counsel
' Office of Information and Resources Management
Office of Inspector General
Director, National Data Processing Division
Regional Information Resources Management Branch Chiefs, I - X
Steering Committee on the State/Federal Enforcement Relationship
This memorandum addresses access and security for the enforcement data
integration capability under development by the Office of Enforcement (OE). It also
addresses limitations on the use of information gathered through the data integration
capability, known as Integrated Data for Enforcement Analysis (IDEA).
The fundamental integration capability was established in early 1991, and
refinements to IDEA will continue for the foreseeable future. This is a significant step
forward for the enforcement program, and with it we enter an exciting time of testing new
approaches to enforcement. These new uses and demands will point to data deficiencies
that will need to be addressed. In recognition of the evolving nature of IDEA, the
procedures set forth in this memorandum are considered interim procedures and will be
subject to modification as new technical capabilities become available.
Background
The Agency's Enforcement 4-Year Strategic Plan and the Enforcement in the
1990's project identified the need for an integrated data capability. The Plan emphasized
the importance of data integration efforts to support enforcement targeting activities, case
screening, case development, litigation support, and settlement negotiations. Developing
IDEA to meet these information needs for the enforcement community will be OE's top.
priority for system development and implementation.
The inability of environmental enforcement personnel at the Federal and State levels
to readily integrate compliance and enforcement information contained in the Agency's
various national mainframe data systems through an automated means also was identified
to the Congress by the President for FY 1990 as an Agency material weakness under the
Federal Managers Financial Integrity Act (FMFIA). OE, with cooperation from the Office
of Information and Resources Management (OIRM), the media program offices, and the
Regional offices, has been working over the past year to develop IDEA. OE was able to
report through the FMFIA reporting process that as of January 31, 1991, a computer
software capability had been established which is able to integrate compliance and
enforcement information from eight national data systems. When fully developed, IDEA
will provide a means to retrieve, view displays at a terminal, and print information from
A-2 IDEA User's Guide February 29, 1996
-------
the various compliance and enforcement data systems in an interactive and highly flexible
automated environment.
Overview of Proposed Implementation Approach for IDEA
•
In accordance with EPA policies that encourage broad access to information, OE intends to provide
access, known as Non-Sensitive Access, as soon as possible in FY 1992, to persons or agencies who have
a valid EPA mainframe User-ID. However, the IDEA software has the ability to access all of the infor-
mation contained in the national enforcement databases, including information considered to be enforce-
ment sensitive. To protect enforcement sensitive information from improper use or release, OE plans to
control access to the full IDEA capability, known as Sensitive Access, through restrictions that will be
placed on authorizations for individual EPA User-Ids (see Attachment 1, Section II and Attachments 2(a)
- 2(d) for procedures for gaining authorization to Sensitive Access). IDEA Users authorized for Sensitive
Access are governed by the provisions of EPA Order 3120.1 (issued September 20, 1985). This Order,
entitled "Conduct and Discipline," and its Attachment, entitled "Guidance on Corrective Discipline," pre-
scribe policies and penalties regarding breaches of security regulations or practice. The relevant pro-
visions of the Order are found under heading #3 on page A-4 of the Appendix.
The eight national systems are the Air Facility System (Clean Air Act), the Permit Compliance System
(Water - NPDES), HWDMS/RCRIS (RCRA), CERCLIS (Superftmd), the Toxics Release Inventory, the
Enforcement DOCKET, the FFIS (Federal facilities), and the Facility Index System.
•
OE will develop a method that blocks access to enforcement, sensitive information but which continues to
permit access to all other information and provide for the foil range of proposed uses for EPA, State, and
local personnel. The security method will be developed reflecting the outcome of database reviews that
OE will conduct with each national system administrator to identify the data that each program has
determined are enforcement sensitive.
Limitations on Use of Information Retrieved through IDEA
While IDEA represents a major step forward in making information accessible, users need to keep in
mind that IDEA has been designed primarily to assist enforcement personnel in enforcement targeting,
case screening, case development, litigation support, and settlement negotiations; but there is significant
potential for misinterpretation of information obtained through IDEA. As each program system acces-
sible through the integration capability is unique, knowledge of statutory provisions, program definitions,
data relationships, and sound professional judgment will be required to accurately interpret information
that is retrieved.
The automated data systems accessible through IDEA do not contain all of the information that an indi-
vidual needs in order to accurately assess program performance. The data accessible through IDEA are
a subset of information on program performance, and without the use of other non-automated informa-
tion or without dialogue with appropriate EPA enforcement program personnel and State officials, accu-
rate conclusions about performance cannot be developed. Also, due to the dynamic nature of the
automated databases that form the basis of this capability, and due to the timing of data retrievals, data
may not precisely match data reported in other EPA reports.
IDEA is not intended to replace any EPA automated information system or reporting procedures.
Existing quality assurance/quality control procedures for each program information system will not be
duplicated, altered, or circumvented. For management accountability reports and other official displays
of quantitative enforcement information (e.g., tallies of administrative actions), OE will continue to rely on
the Agency's Strategically Targeted Activities for Results System ( STARS) reporting process. The quan-
titative STARS reports are based on well established and defined State and Regional reporting processes,
data retrieval dates, and discrepancy reconciliation processes, that cannot be duplicated or replaced by
IDEA.
Appendix A. Access and Security Procedures for IDEA A-3
-------
Conclusion
The procedures set forth in this memorandum and its attachments are considered interim and will be
revised as necessary. Questions on the general approach for implementation of IDEA should be directed
to Bruce Rothrock (202 564-2504) or Bob Greenspun (202 564-2506), and questions regarding training
or user access should be directed to the IDEA User Support Line (202 564-2475).
A.I Attachments
A-4
IDEA User's Guide
February 29, 1996
-------
Office of Enforcement Procedures for
Access and Security for
Integrated Data for Enforcement Analysis (IDEA)
This document addresses access and security procedures for the enforcement data
integration capability (hereafter referred to as Integrated Data for Enforcement Analysis
(IDEA)). In recognition of the evolving nature of IDEA, the procedures set forth below
are considered interim procedures and will be subject to modification as new technical
capabilities become available.
I. Overview of Proposed Implementation Approach for IDEA
The IDEA software has the ability to access all of the information contained in the
national enforcement databases, including information considered to be enforcement
sensitive. To protect enforcement sensitive information from improper use or release, the
Office of Enforcement (OE) plans to control access to the full IDEA capability, known as
Sensitive Access, through restrictions that will be placed on authorizations for individual
EPA User-ID's (see Section II below and Attachments 2(a) - 2(d) for procedures for
gaining authorization to Sensitive Access). IDEA Users authorized for Sensitive Access
are governed by the provisions of EPA Order 3120.1 (issued September 20, 1985). This
Order, entitled "Conduct and Discipline," and its Attachment, entitled "Guidance on
Corrective Discipline," prescribe policies and penalties regarding breaches of security
regulations or practice. The relevant provisions of the Order are found under heading III
below.
In accordance with EPA policies that encourage broad access to information, OE
intends to establish a second level of access, known as Non-Sensitive Access, as soon as
possible in FY 1992. OE will develop a method that blocks access to enforcement
sensitive information but which continues to permit access to all other information and
provide for the full range of proposed uses for EPA, State, and local personnel. The
security method will be developed reflecting the outcome of database reviews that OE will
conduct with each national system administrator to identify the data that each program has
determined are enforcement sensitive.
II. Process for Obtaining Authorization for Access to Non-Sensitive Information
i
EPA's National Computer Center (NCC) is responsible for controlling EPA
mainframe computer User-Ids. EPA employees and State or local officials seeking to
obtain an EPA User-ID should contact the ADP coordinator or account manager for their
office or Region. The ADP coordinator or account manager will use the NCC's new
on-line user registration system, to create a new User-ID interactively.
Persons or agencies outside of EPA that seek to obtain an EPA User-ID should call
703-487-4830 to begin the process of establishing an NCC account.
III. Process for Obtaining Authorization for Access to Sensitive Information
1. EPA Regions - The Regions will determine which of their employees have a
need-to-know sensitive information in order to conduct targeting, screening, case
development, litigation support, and settlement negotiations. To authorize a Regional
employee's EPA mainframe User-ID for access to sensitive information, the employee and
the Deputy Regional Administrator (DRA) will need to submit to the Director of Office
of Enforcement and Compliance Assurance, Office of Compliance a letter (a sample letter
is included in Attachment 2(a)) requesting access. Upon receipt of the letter and
Appendix A. Access and Security Procedures for IDEA A-5
-------
completion of user training provided by OE, the employee User-ID will be authorized.
2. EPA Headquarters Enforcement Program Offices - The Headquarters enforcement program offices
will determine which of their employees have a need-to-know sensitive information in order to
conduct targeting, screening, case development, litigation support, and settlement negotiations. To
authorize an employee's EPA mainframe User-ID for access to sensitive information, the employee
and the employee's Office Director will need to submit to the Director Office of Enforcement and
Compliance Assurance, Office of Compliance a letter (a sample letter is included in Attachment 2(b))
requesting access. Upon receipt of the letter and completion of user training provided by OE, the
employee User-ID will be authorized.
3. EPA Office of Enforcement - OE will determine which of its employees have a need-to-know sensitive
information in order to conduct targeting, screening, case development, litigation support, and settle-
ment negotiations. To authorize an employee's EPA mainframe User-ID for access to sensitive infor-
mation, the employee and the employee's Office Director will need to submit to the Director Office of
Enforcement and Compliance Assurance, Office of Compliance a letter (a sample letter is included in
Attachment 2(c)) requesting access. Upon receipt of the letter and completion of user training pro-
vided by OE, the employee User-ID will be authorized.
4. EPA Contractor Employees - The Regional or Headquarters office will determine which of their con-
tractor employees have a need-to-know sensitive information in order to conduct targeting, screening,
case development, litigation support, and settlement negotiations. To authorize a contractor employ-
ee's EPA mainframe User-ID for access to sensitive information, the contractor employee, their con-
tract project officer, and the appropriate EPA senior official (i.e., Hie Deputy Regional Administrator
or Headquarters Office Director) will need to submit to the Director Office of Enforcement and Com-
pliance Assurance, Office of Compliance a letter (a sample letter is included in Attachment 2(d))
requesting access. Upon receipt of the letter and completion of user training provided by OE, the
contractor employee's User-ID will be authorized.
5. List of Users with Sensitive Access - OE will maintain a list of users whose EPA User ID's have
been authorized for sensitive access. The Headquarters program system administrators will be kept
informed of approved User-ID's, unless they prefer to have concurrence prior to approval.
Figure A-l. Attachment 1
A-6 IDEA User's Guide February 29, 1996
-------
MEMORANDUM
SUBJECT: Request for Authorization of EPA Mainframe User-ID
FROM: Name of Employee, Title, Program, EPA Mainframe User-ID
THROUGH: ,
Deputy Regional Administrator
Region
TO: Elaine Stanley, Director
Office of Enforcement and Compliance Assurance
Office of Compliance
With this memorandum, we request that the EPA User ID (User ID) for (employee
name) be authorized for Sensitive Access to the OECA's Integrated Data
for Enforcement Analysis (IDEA) system. This request is based on our determination that
Mr ./Ms. needs-to-know and have access to sensitive information in order to
conduct assigned duties in targeting, screening, case development, litigation support, and
settlement negotiations.
Mr ./Ms. recognizes that this level of access will permit retrieval of
information that is enforcement sensitive and confidential. His/She agrees to treat all
information retrieved through this capability as confidential, for internal EPA use only, and
subject to program office verification. If Sensitive Access is jpranted, the Region agrees
that such access will be terminated in the event that his/her duties in the Region no longer
support the need-to-know this information, or his/her employment by EPA has ceased.
The Region further acknowledges that it is responsible for notifying OECA when the
User-ID's sensitive access right is to be terminated. We understand that IDEA Users
authorized for Sensitive Access are governed by the provisions of EPA Order 3120.1
(issued September 20, 1985). We also understand that this Order, entitled "Conduct and
Discipline," and its Attachment, entitled "Guidance on Corrective Discipline" prescribe
policies and penalties regarding breaches of security regulations or practice.
The applicants) for sensitive access recognizes that he or she is
responsible for safeguarding reports that may contain confidential
or enforcement sensitive data. This includes the proper use, storage, and
disposal of printouts, the RACF protection of any personal libraries on the
EPA mainframe, and RACF protection of their JES2 output queue, which
may contain output reports waiting to be printed or purged.
Figure A-2. Attachment 2(a) - Sample EPA Regional memorandum
Appendix A. Access and Security Procedures for IDEA A-7
-------
MEMORANDUM
SUBJECT: Request for Authorization of EPA Mainframe User-ID
FROM: Name of Employee, Title, Program, EPA Mainframe User-ID
THROUGH:
, Enforcement Office Director
TO: Elaine Stanley, Director
Office of Enforcement and Compliance Assurance
Office of Compliance
With this memorandum, we request that the EPA User-ID for (User ID) for
(employee name) be authorized for Sensitive Access to the OECA's
Integrated Data for Enforcement Analysis (IDEA) system. This request is based on our
determination that Mr./Ms. needs-to-know and have access to sensitive
information in order to conduct assigned duties in targeting, screening, case development,
litigation support, and settlement negotiations.
Mr./Ms._
recognizes that this level of access will permit retrieval of
information that is enforcement sensitive and confidential. He/She agrees to treat all
information retrieved through this capability as confidential, for internal EPA use only, and
subject to program office verification. If Sensitive Access is granted, this office agrees
that such access will be terminated in the event that his/her duties no longer support the
need-to-know this information, or his/her employment by EPA has ceased. This office
further acknowledges that it is responsible for notifying OECA when the User-ID's
sensitive access right is to be terminated. We understand that IDEA Users authorized for
Sensitive Access are governed by the provisions of EPA Order 3120.1 (issued September
20, 1985). We also understand that this Order, entitled "Conduct and Discipline," and its
Attachment, entitled "Guidance on Corrective Discipline" prescribe policies and penalties
regarding breaches of security regulations or practice.
The applicants) for sensitive access recognizes that he or she is
responsible for safeguarding reports that may contain confidential
or enforcement sensitive data. This includes the proper use, storage, and
disposal of printouts, the RACF protection of any personal libraries on the
EPA mainframe, and RACF protection of their JES2 output queue, which
may contain output reports waiting to be printed or purged.
Figure A-3. Attachment 2(b) - Sample EPA Headquarters Program Office Memorandum
A-8
IDEA User's Guide
February 29, 1996
-------
MEMORANDUM
SUBJECT: Request for Authorization of EPA Mainframe User-ID
'
FROM: Name of Employee, Title, Program, EPA Mainframe User-ID
THROUGH: , OE Office Director
TO: Elaine Stanley, Director
Office of Enforcement and Compliance Assurance
Office of Compliance
With this memorandum, we request that the EPA User-ID for (User ID) for
(employee name) be authorized for Sensitive Access to the OECA's
Integrated Data for Enforcement Analysis (IDEA) system. This request is based on our
determination that Mr./Ms. needs-to-know and have access to sensitive
information in order to conduct assigned duties in targeting, screening, case development,
litigation support, and settlement negotiations.
Mr./Ms. recognizes that this level of access will permit retrieval of
information that is enforcement sensitive and confidential. He/She agrees to treat all
information retrieved through this capability as confidential, for internal EPA use only, and
subject to program office verification. If Sensitive Access is granted, this office agrees
that such access will be terminated in the event that his/her duties no longer support the
need-to-know this information, or his/her employment by EPA has ceased. This office
further acknowledges that it is responsible for notifying OECA when the User-ID's
sensitive access right is to be terminated. We understand that IDEA Users authorized for
Sensitive Access are governed by the provisions of EPA Order 3120.1 (issued September
20, 1985). We also understand that this Order, entitled "Conduct and Discipline," and its
Attachment, entitled "Guidance on Corrective Discipline" prescribe policies and penalties
regarding breaches of security regulations or practice.
The applicants) for sensitive access recognizes that he or she is
responsible for safeguarding reports that may contain confidential
or enforcement sensitive data. This includes the proper use, storage, and
disposal of printouts, the RACF protection of any personal libraries on the
EPA mainframe, and RACF protection of their JES2 output queue, which
may contain output reports waiting to be printed or purged.
Figure A-4. Attachment 2(c) - Sample Office of Enforcement Memorandum
Appendix A. Access and Security Procedures for IDEA A-9
-------
MEMORANDUM
SUBJECT: Request for Authorization of EPA Mainframe User-ID
FROM: Name of Employee, Tide, Program, EPA Mainframe User-ID
THROUGH:
EPA Project Officer
Deputy Regional Administrator or Headquarters Office Director
TO: Elaine Stanley, Director
Office of Enforcement and Compliance Assurance
Office of Compliance
With this memorandum, we request that the EPA User-ID for (User ID) for
(contractor employee name) be authorized for Sensitive Access to the OECA's
Integrated Data for Enforcement Analysis (IDEA) system. This request is based
on our determination that Mr ./Ms. needs-to-know and have access to
sensitive information in order to conduct assigned duties in targeting, screening, case
development, litigation support, and settlement negotiations.
Mr ./Ms. recognizes that this level of access will permit retrieval of
information that is enforcement sensitive and confidential. He/She agrees to treat all
information retrieved through this capability as confidential, for internal EPA use only, and
subject to program office verification. If Sensitive Access is granted, the
Region/Headquarters Office agrees that such access will be terminated in the event that
his/her duties no longer support the need-to-know this information, or his/her employment
by EPA contractor has ceased, or he/she has breached the security of this information,
regardless of intent. The Region/Headquarters Office further acknowledges that it is
responsible for notifying OECA when the User-ID's sensitive access right is to be
terminated.
The applicants) for sensitive access recognizes that he or she is
responsible for safeguarding reports that may contain confidential
or enforcement sensitive data. This includes the proper use, storage, and
disposal of printouts, the RACF protection of any personal libraries on the
EPA mainframe, and RACF protection of their JES2 output queue, which
may contain output reports waiting to be printed or purged.
cc: Contractor Project Officer
Figure A-S. Attachment 2(c) - Sample EPA Contractor Employee Memorandum
A-10 IDEA User's Guide February 29, 1996
-------
Appendix B. Database Descriptions
B.I AFS
System Name: AIRS Facility Subsystem \
\
Acronym: AFS
Regulation for Data Collection: Clean Air Act
System Owner/Operator: Office of Compliance, U.S EPA.
Data Contact: Mark Antell (202) 564-5003
System Contact: Chuck Isbell (919) 541-5448
System Platform/Software: IBM ES9000 Mainframe / ADABAS
Data Owner(s): Planning and Targeting Division (U.S. EPA), EPA regional offices
and other delegated regional agencies.
Data Update Schedule: Daily
System Description: The AIRS Facility Subsystem (AFS) is a component of the
Aerometric Information Retrieval System (AIRS). AIRS is a computerized
database management system for airborne pollution in the United States
consisting of four subsystems. Each subsystem addresses a different (but in
many cases related) aspect of the Clean Air Act regulatory requirements.
AFS contains emissions, compliance, and enforcement data on stationary
sources of air pollution. Regulated sources cover the spectrum from large
industrial facilities to relatively small operations such as dry cleaners (auto-
mobiles and other mobile air pollution sources are tracked by a different
AIRS Subsystem (AMS)). IDEAs AFS file currently does not contain any
data on Class B air facilities or on facilities which are solely asbestos demo-
lition and/or renovation contractors.
While AFS maintains data at several levels of detail on an air source,
IDEA focuses on the data at the plant-level. Plant-level data treats the
entire facility as one unit, rather than looking at individual emission points,
processes, or stacks. Data reported at the plant level include:
• General Source Information — identification number, name, location,
etc.
• Plant Compliance Status — plant-wide, worst case status.
• Significant Violator information.
• Air Program Information -- a repeating block of data addressing each
regulatory area a facility is subject to-(e.g., SIP, NSPS, NESHAP,
PSD). Each Air program offers data on the following: Historical Com-
pliance Status - quarterly for past two years (1992 to present).
Appendix E3. Database Descriptions B-1
-------
Pollutant information -- identifiers, classifications, compliance status,
etc. Action/Activity Data -- inspections, enforcement actions, etc (1978
to present). Operating Status. Appendix C presents the AFS data ele-
ments in related groups which parallel the data's hierarchical relation-
ships.
B.2 CER
System Name: CERCLA Information System
Acronym: CERCLIS
Regulation for Data Collection: Comprehensive Environmental Response, Compen-
sation, and Liability Act (as amended)
System Owner/Operator: Office of Emergency and Remedial Response, U.S. EPA
System Contact: CERCLIS Hotline (703) 908-2066
System Platform/Software: IBM ES9000 Mainframe/SYSTEM 2000
Data Owner(s): U.S. EPA (non-delegated program)
Data Update Schedule: Monthly
System Description: The Comprehensive Environmental Response, Compensation,
and Liability Act Information System (CERCLIS) contains the official
inventory of CERCLA sites, and integrates data from the Superfund
removal, site assessment, remedial, and enforcement programs. CERCLIS
supports site project management, program budget negotiations, account-
ability negotiations, and reporting. CERCLIS data are structured based on
an "operable unit" organization.
An operable unit (OU) is formally defined in the CERCLA National Con-
tingency Plan (NCP); but for practical purposes, it typically represents
some physical aspect of the CERCLA site (e.g., dividing large sites into
smaller units) or of the clean-up required (e.g. surface clean-up,
groundwater, etc.). A site can have one operable unit or as many as the
project officer deems necessary (up to OU 99) to remediate the site. Oper-
able units are numbered starting from OU 00 which is designated as the
"site-wide" OU containing removal, pre-remedial, and enforcement informa-
tion. Sites not included on the National Priorities List (NPL) usually have
only an OU 00, since full clean-up can be achieved through a removal
action, or because after pre-remedial evaluation, it is determined that no
further federal action is necessary.
IDEA'S standard CERCLIS report IB displays data based on the OU
structure; however, most reports show enforcement data with the events
using the links feature of WasteLAN (the PC data entry system for
CERCLIS). This data can also be displayed after the last OU (due to a
B-2
IDEA User's Guide
February 29, 1996
-------
limitation of the CERCLIS database hierarchy). The most commonly
queried/displayed data include the following:
• General Site/Incident Information -- identification number, name,
location, etc.
• Site Assessment -- discovery, preliminary assessments, site screening
inspections, etc.
• Removal -- removal activities.
• Remedial — remedial investigation/feasibility studies, Record of Deci-
sion, remedial design, remedial action, long-term response, etc.
• Enforcement - PRP searches, negotiations, administrative and judicial
actions, etc.
Appendix C presents the CERCLIS data elements in related groups which
parallel the data's hierarchical relationships and System 2000 structure.
B.3 DCK
System Name: Civil Enforcement Docket System
Acronym: DOCKET
Regulation for Data Collection: Enforcement Sections of Environmental Statutes under
EPA's responsibility
System Owner/Operator: Office of Compliance, U.S. EPA
System Contact: Merle Miller (202) 564-4114 <
System Platform/Software: IBM ES9000 Mainframe/AD ABAS
Data O\vner(s): U.S. EPA (non-delegated program)
Data Update Schedule: Postponed Indefinitely ;
System Description: The Civil Enforcement Docket System (DOCKET) is a case
activity tracking and management system for both civil, judicial, and
administrative federal EPA enforcement cases. Case information is sup-
plied and updated by EPA's Offices of Regional Counsel and Office of Civil
Enforcement case attorneys. The basic structure of a DOCKET record
focuses on an enforcement case. It is assigned a case number (unique to
DOCKET; not the same as the DOJ case number) and a case name which
identifies the defendant (or principal defendant if more than one is named
in the complaint). In the case of administrative actions, the record
includes the nature of the violation, statute(s) involved, attorneys assigned,
and milestone dates (e.g., the date the order was issued). Judicial actions
contain information similar to that for administrative actions, but include
more detailed milestone dates, as well as a place to indicate that a case has
been amended (e.g., to include additional violations or defendants). IDEA
contains a subset of the DOCKET data which includes:
Appendix B. Database Descriptions B-3
-------
• General Case Information - Case number, Case name, HQ Division,
etc.
• Case Attorney Names -- EPA/Region, EPA/HQ, DOJ.
• Violation Information ~ Law/Section, Pollutant(s), Violation Date, etc.
• Defendant Name(s)
« Milestone Dates ~ Referred to DOJ, Filed, Concluded, etc.
• Amendment Information -- Amendment Type, Milestone Dates.
DOCKET tracks enforcement actions taken against companies or indi-
viduals. Therefore, the DOCKET case name may not exactly corre-
spond to the facility name where DOCKET records are linked via
FINDS to facility records from other program office data systems.
Appendix C presents the DOCKET data elements in related groups which
parallel the data's hierarchical relationships.
B.4 DUN
System Name: Dun and Bradstreet Marketing Services ~ Identifier File
Acronym: DUNS
Regulation for Data Collection: N/A (Leased Commercial Vendor Product)
System Owner/Operator: Office of Information and Resources Management, U.S.
EPA
System Contact: Bryce Gerlach (800) 424-2495 or (703) 845-2729 or Donna Cecil
(703) 845-2731 of Dun&Bradstreet Corporation
System Platform/Software: IBM ES9000 Mainframe/ADABAS
Data Owner(s): The Dun and Bradstreet Corporation
Data Update Schedule: To Be Determined
System Description: The Dun and Bradstreet Marketing Services (D&B) ~ Duns
Market Identifier File (DMI) is a commercial vendor product which is
leased by EPA's Office of Information and Resources Management. It is a
static file extracted from the full D&B database, and contains basic identifi-
cation data for all business establishments tracked by D&B. IDEA extracts
a subset of the Identifier File: it includes only those businesses (AND all
businesses in their corporate "families") which are linked via FINDS to any
program office facility record. The IDEA DUNS file includes:
• Identifying Information — DUNS Number, Name, Address.
• Industry Classification -- up to six SIC Codes.
• Corporate Family Linkage ~ Parent Number and Ultimate Number.
The hierarchical relationship of DUNS Numbers should permit simple
IDEA queries to retrieve information about all the businesses/facilities
B-4 IDEA User's Guide February 29, 1996
-------
for a given company. In practice, the linkages between DUNS and
FINDS are incomplete (at this time). This requires additional steps to
be taken to retrieve "corporate profile" data from IDEA. The data ele-
ments that IDEA accesses are listed in Appendix C in related groups
which parallel the data's hierarchical relationships.
B.5 ERN
System Name: Emergency Response Notification 'System
Acronym: ERNS
Regulation for Data Collection: None
System Owner/Operator: EPA Headquarters & Regions, Coast Guard, and Depart-
ment of Transportation
System Contact: IDEA User Support (202) 564-2475
System Platform/Software: VAX
Data Owner(s): Primarily Department of Transportation and EPA
Data Update Schedule: Daily
System Description: The Emergency Response and Notification System (ERNS) is a
national computer database and retrieval system that is used to store infor-
mation on release notifications of oil and hazardous substances. ERNS
contains reports of incidents as initially reported to the National Response
Center (NRC), the ten EPA Regions, or the U. S. Coast Guard (USCG).
It provides data that can be used to analyze spills and to support emer-
gency planning efforts by Federal, State, and local governments.
ERNS contains information on specific releases of oil and hazardous sub-
stances. Examples of notification information in ERNS and available
through IDEA include:
• Discharger identification
• Date of release
• Material released
• Cause of release
• Damage/injuries/deaths
• Amount released
• Source of release
• Incident location
• Response actions taken
• Authorities notified
Appendix B. Database Descriptions B-5
-------
• Environmental medium into which the release occurred
ERNS tracks reports of spills. The ERNS basic unit is a report rather than
an incident, which means that a single incident can appear more than once.
An update on the incident might be added to the system after the event
took place and the original report was entered. An update might appear as
a separate report. ERNS data can be obtained through the GO NAMES
utility of the Keyword Interface and standard reports 1A & IB. ERNS
data is not linked using FINDS; therefore, it is necessary to run ERNS
queries as NONLINKED or LINKED NONLINKED.' This situation is
especially important when combining GO NAMES and GO MENUA
keywords. ERNS data elements that are accessed by the IDEA system are
listed in Appendix C organized by related groups which parallel the data's
hierarchical relationships.
B.6 FFI
System Name: Federal Facilities Information System
Acronym: FFIS
Regulation for Data Collection: N/A
System Owner/Operator: Office of Federal Facilities Enforcement, Office of Enforce-
ment, U.S. EPA
System Contact: Don Franklin (202) 260-5908
System Platform/Software: DOS-based microcomputer/dBASE
Data Owner(s): U.S. EPA (non-delegated program)
Data Update Schedule: Annually
System Description: The Federal Facilities Information System (FFIS) is an auto-
mated system used by both the EPA and other executive agencies. The
FFIS serves as a tool for monitoring and planning projects which are
intended to bring federal facilities into compliance with current environ-
mental regulations or to maintain compliance. The FFIS provides the fol-
lowing:
• An inventory of all federal facilities for which pollution abatement
projects have been reported to the Office of Management and Budget
(OMB) through EPA.
• The compliance status of any facility with applicable regulations.
• Information on projects planned or initiated to bring the facility into
compliance with current regulations, to maintain compliance, or to
achieve compliance with future regulations.
• Budget information as required by OMB for the A-I06 report. The
FFIS database stores information on the nature of the problem that
each project must correct, the reason for initiating the project, its envi-
ronmental impact, its estimated cost, and an evaluation of the adequacy
B-6 IDEA User's Guide February 29, 1996
-------
of the project regarding design, timing, and funding. Budget informa-
tion required by OMB is available. Although data may be added to the
system throughout the year, the major updates occur in January and
July. Data may also be updated in September, in preparation for the
OMB report. Appendix C present!? the FFIS data elements in related
groups which parallel the data's hierarchical relationships.
B.7 FIN
System Name: Facility Index System
Acronym: FINDS
Regulation for Data Collection: N/A
System Owner/Operator: Office of Information and Resources Management, U.S.
EPA
System Contact: FINDS Information Hotline (800) 908-2493 or Daisy Berlingeri (703)
235-5576
System Platform/Software: IBM ES9000 Mainframe/ADABAS
Data Owner(s): U.S. EPA~(non-delegated program)
Data Update Schedule: To Be Determined
System Description: The Facility Index System (FINDS) is a computerized inventory
of facilities regulated by the EPA. FINDS contains two types of informa-
tion about each facility:
• Facility identification data, such as its unique EPA ID number, name,
and physical address.
• Pointers to other sources of information— EPA program office data-
bases which contain more detailed information about the regulated
facility. Currently, FINDS is updated by performing periodic "reconcil-
iations" between the FINDS records and those of the program office
data systems. For each program office facility record, an effort is made
to link it to an existing FINDS EPA Facility ID Number, or to assign
it a new EPA Facility ID Number when sufficient identifying informa-
tion exists to determine that it is a new facility to FINDS. The types of
data FINDS maintains include:
• EPA Facility ID Number — a unique and meaningless number
assigned to each facility.
• FINDS Facility Name ~ may match or differ from the program office
facility name. ;
• Address ~ Street, City, County, State, EPA Region, Latitude, Longi-
tude, and Attributes.
• System-Code — a code to uniquely identify a program office database.
Appendix K. Database Descriptions B-7
-------
System-ID ~ the ID number that the program office database uses
may differ from the EPA ID Number. Because EPA program offices
may apply their own definition of what constitutes a facility, FINDS
may link one or more System Identifiers to the same EPA ID Number.
FINDS problems for the IDEA user include inaccurate links with
program office facility records and incomplete linkages, owing to
incomplete or ambiguous facility name and address information in the
EPA program systems who provide the facility information to FINDS.
FINDS > Appendix C presents the FINDS data elements that are
accessed by IDEA in related groups which parallel the data's hierar-
chical relationships.
B.8 LST
System Name: Contractor Listing Docket, a subsystem of the Office of Enforcement
Consolidated Docket System.
Acronym: LST
Regulation for Data Collection: Clean Air Act sect. 306, Clean Water Act sect. 508
and 40 C.F.R. Part 15
System Owner/Operator: Office of Compliance and the Contractor Listing Program,
U.S. EPA.
System Contact: Robert Meunier (202) 260-8025
System Software: Contractor Listing Docket is an AD ABAS system which uses soft-
ware written in NATURAL. The software was designed by Computer Sci-
ences Corporation in 1989.
Data Update Schedule: Postponed Indefinitely
System Description: The Contract Listing Docket system is a case activity tracking
system. It was designed to assist the Office of Enforcement in tracking,
managing, and reporting information about Contract Listing Cases from
the point they are initiated and developed until they are concluded. Con-
tractor Listing Cases are managed by the Contractor Listing Program
which is located in the Criminal Enforcement Counsel Division of the
Office Criminal Enforcement, Office of Enforcement.
The LST data elements that are accessed by IDEA are listed in Appendix C
in related groups which parallel the data's hierarchical relationships.
B-8
IDEA User's Guide
February 29, 1996
-------
B.9NCD
System Name: National Compliance Database
Acronym: NCDB
Regulation for Data Collection: Federal Insecticide., Fungicide, and Rodenticide Act
(FIFRA), Toxic Substances Control Act (TSCA), Emergency Planning and
Community Right To Know Act (EPCRA) Section 313.
System Owner/Operator: Office of Compliance, U.S. EPA.,
System Contact: Bob Zisa (202) 564-5048
System Platform/Software: PC/LAN; dBASE 3+ , Clipper compiled
Data Owner(s): U.S. EPA (partially-delegated program)
Data Update Schedule: Monthly
System Description: The National Compliance Database tracks compliance and
enforcement data under the Federal Insecticide, Fungicide, and Rodenticide
Act (FIFRA), the Toxic Substances Control Act (TSCA), and the Emer-
gency Planning and Community Right To Know Act (EPCRA) Section
313. NCDB is the national repository for data from the regional
FIFRA/TSCA Tracking System (FTTS), which resides on LANs in the
regional Pesticides and Toxics Branches, The Office of Prevention, Pesti-
cides and Toxic Substances (OPPTS) uses NCDB to track compliance and
enforcement data and to provide standardized and ad hoc reports. The
major data sets include the following:
• Inspection \
• Case Review
• Enforcement Action
• Settlement Term Other datasets include Import, Sample, Referral, Mul-
tiple Actions, Milestones, and Grants.
NCDB data elements that are accessed by IDEA are listed in Appendix C
organized in groups which reflect the structure of the data.
B.10 PCS
System Name: Permit Compliance System
Acronym: PCS
Regulation for Data Collection: Clean Water Act, National Pollution Discharge Elimi-
nation System Program
System Owner/Operator: Office of Compliance, U.S. EPA.
Appendix B. Database Descriptions B-9
-------
System Contact: PCS User Support (202) 564-7277
System Platform/Software: IBM ES9000 Mainframe/ADABAS
Data Owner(s): U.S. EPA and delegated state agencies
Data Update Schedule: Biweekly
System Description: The Permit Compliance System (PCS) is an automated informa-
tion management system maintained by the Office of Compliance to track
permit compliance and enforcement status of facilities regulated by the
National Pollutant Discharge Elimination System (NPDES) under the
Clean Water Act. PCS is designed to support the NPDES program at the
state, regional, and national levels. Currently PCS tracks more than 75,000
active NPDES permits and an equal number of inactive ones. The PCS
includes the following data types:
• Permit facility data
• Descriptions of outfalls (pipes)
• Monitoring requirements for each outfall
• Reported measurement values
• Compliance schedules
• Compliance schedule violations
• Inspection information
• Pretreatment audit
• Pretreatment Performance Summary (PPS)
• Enforcement actions
• Evidentiary hearings
• Grants
• Permit tracking events
• Single Event Violations
• Inspection Scheduling
Appendix C presents the PCS data elements in related groups which par-
allel the data's hierarchical relationships.
B.11RCR
System Name: Resource Conservation and Recovery Information System
Acronym: RCRIS
Regulation for Data Collection: Resource Conservation and Recovery Act
B-10 IDEA User's Guide
February 29, 1996
-------
System Owner/Operator: Office of Solid Waste, Office of Solid Waste and Emergency
Response, U.S. EPA
System Contact: RCRA Hotline (800) 424-9346
System Platform/Software: IBM ES9000 Mainframe/FOCUS
Data Owner(s): U.S. EPA and delegated State Agencies
Data Update Schedule: Monthly
System Description: The Resource Conservation and Recovery Information System
(RCRIS) is the national program management and inventory system of
RCRA hazardous waste handlers. Handlers fit one or more of the fol-
lowing categories: treatment, storage and disposal facilities (TSDFs), large
quantity generators (LQGs), small quantity generator (SQGs), and trans-
porters. RCRIS contains: i
• general information on all handlers (e.g., name, address, activity type);
• permitting and corrective action program status, and SIC code informa-
tion for TSDFs only;
• enforcement and compliance actions for specific facilities, regardless of
type, which have been subject to ktspections or other enforcement
activity. The information in RCRIS is created by States and Regions
for their program implementation purposes. Those portions of the data
which are relevant for national program oversight and management are
contained in the RCRIS national oversight database from which IDEA
extracts its information. In RCRIS documentation, data which is iden-
tified as "core" or "conditional core" is contained in the national over-
sight database. The RCRIS data elements accessed by IDEA are listed
in Appendix C.
B.12 SET
System Name: Site Enforcement Tracking System
Acronym: SETS
Regulation for Data Collection: Comprehensive Environmental Response, Compen-
sation, and Liability Act (as amended)
System Owner/Operator: Office of Compliance, IJ.S. EPA.
System Contact: Alicia Corley (202) 564-5013
System Platform/Software: IBM ES9000 Mainframe/ FOCUS
Data Owner(s): U.S. EPA •
Data Update Schedule: Continuously
Appendix E3. Database Descriptions B-11
-------
System Description: The Site Enforcement Tracking System is a database manage-
ment system designed to track the names and addresses of potentially
responsible parties (PRPs) who have been issued CERCLA sections 106 &
107 "General" notice letters, or CERCLA section 122 "Special" notice
letters. General Notice Letters inform the PRPs of their potential liability
for the costs of response work associated with the investigation and control
of actual or threatened releases of hazardous substances. Special Notice
Letters inform PRPs of EPA's decision regarding remedy selection at a
CERCLA site (or portion thereof), and extend an opportunity to meet with
EPA to facilitate a settlement for remediation activities at the site. The
types of data maintained include:
• Site name and address.
• PRP name.
• Date of General Notice Letter.
• Date of Special Notice Letter.
• Notice Letter Addressee name and address. SETS data elements
accessed by the IDEA system are listed in Appendix C organized in
groups that reflect the structure of the data.
B.13 TRI
System Name: Toxic Chemical Release Inventory System
Acronym: TRIS
Regulation for Data Collection: Emergency Planning and Community Right-to- Know
Act
System Owner/Operator: Office of Pollution Prevention and Toxics, Office of Pre-
vention, Pesticides and Toxic Substances, U.S. EPA
System Contact: TRIS User Support (703) 816-4434 or EPCRA Hotline (800)
535-0202
System Platform/Software: IBM ES9000 Mainframe / ADABAS
Data Owner(s): U.S. EPA
Data Update Schedule: Annually
System Description: The Toxic Chemical Release Inventory System (TRIS) is the first
national database which contains information on toxic pollution by manu-
facturing industries. As mandated by the Emergency Planning and Com-
munity Right-to-Know Act of 1986, the TRIS is publicly accessible. It
provides the public and government with information about possible chem-
ical hazards in their communities and thus promotes planning for response
to chemical accidents.
B-12 IDEA User's Guide February 29, 1996
-------
Manufacturing facilities covered by the 1986 act must report to EPA and
to state the amounts of more than 300 specified toxic chemicals that they
release directly to the air, water, or land, or that they transfer to off-site
facilities which treat or dispose of wastes.
Data in the TRIS include the following:
• Facility identification.
• Off-site locations to which wastes containing toxic chemicals are trans-
ferred.
• Chemical-specific information.
• Activities/uses of chemicals.
• Maximum amount of chemicals on-site at any one time.
• Releases on-site.
• Waste treatment methods and efficiency.
• Pollution prevention actions.
Appendix C presents the TRIS data elements in related groups which par-
allel the data's hierarchical relationships.
B.14 ZIP
System Name: 1990 Census of Population and Housing - Summary Tape File 3B
Acronym: STF 3B
System Owner/Operator: U.S. Department of Commerce, Bureau of the Census
System Contact: IDEA User Support (202) 564-2475
System Platform/Software: CD ROM, in dBase III +
Data Update Schedule: Static
System Description: STF 3B provides ZIP Code data derived in the 1990 Census for
the 5-digit ZIP Codes within each state, including county portions of the
ZIP Codes. Because ZIP Codes are administrative units established by the
United States Postal Service (USPS) fo:r the efficient delivery of mail, they
therefore do not generally respect political or census statistical area bound-
aries. ZIP Codes usually do not have clearly identifiable boundaries, often
serve a continually changing area, are changed periodically to meet postal
requirements, and do not cover all of the land area of the United States.
The first three digits identify a major city or sectional distribution center,
and the last two digits generally signify a specific post office's delivery area
or point.
Appendixes. Database Descriptions B-13
-------
The types of statistics available for each ZIP Code include total popu-
lation, ethnic demographics, median incomes, fraction employed, and per-
centages of families and households in certain income brackets.
Appendix C presents the ZIP data elements in related groups which parallel
the data's hierarchical relationships.
B-14 IDEA User's Guide . February 29, 1996
-------
Appendix C. Data Elements in IDEA Shadow Files
This Appendix presents the data elements included in IDEA'S "shadow files," or
copies of the EPA Program Office database files. The following points should be
kept in mind when referencing these data element listings:
_M
1. Not all of the data available from the Program Office data systems may be
included in the IDEA shadow files.
2. A data element must be indexed in order to be used as an IDEA query selection
criterion. Refer to the INDEXED? column to see whether the data element you
wish to use as a SELECT criterion is indexed.1 (Data elements do not need to be
indexed to be printed out in a User- specified Report.)
3. Bolded data elements were created for IDEA retrieval use and do not exist as such
in the Program Office databases.
I
4. Data elements are on the major level of their database if the GROUP of which
they are a member is marked with an A in parens "(A)" They are on the minor
level of their database if their GROUP is marked with a B in parens "(B)".
5. Data elements in the same GROUP (or LEVEL in the CERCLIS database) are
all either repeating fields or not. Refer to the REPEATING FIELD? column for
the data element's group (or level) to see whether it is a repeating field. In
repeating groups, the data element(s) which uniquely determine the record, the
"keyed" elements, are marked with a K in parens "(K)".
6. In most databases, a set of values for the elements in a group will comprise a
"record". In the PCS and RCR databases, however, certain groups (called
"portmanteau" groups) include more than one type of record. The "non-keyed"
elements of these groups are marked with a numeric value in parens, denoting the
type of record in which they occur. !
The file listings follow the same basic format: for each data element in IDEA are
listed its GROUP (or LEVEL in CERCLIS); a REPEATING FIELD indicator for its
group: (Y)es or (N)o; its ELEMENT NAME; an INDEXED indicator: (Y)es or
(N)o; an Enforcement SENSITIVE indicator: (Y)es, (S)ometimes, or (N)o; a generic
indicator of the data TYPE (see Table C-l); the (external) LENGTH of the data
field; and a brief DESCRIPTION of the data element.
1 Two exceptions to this rule are DCK.RSOF and LST.RSOF, which are indexed, but cannot be used as Select criteria.
Appendix C. Data Elements in IDEA Shadow Files C-1
-------
Table C-l. Descriptions of Data Types
Code
Char
Date
Num
Intg
Text
Data Type
Character
Date
Numeric
Integer
Text
Description
May include alphabetic or numeric data
Expresses the date as a string of numbers; check the
description for the specific format
Only numeric data may be present; may be integer
decimal format
or
Only integer numeric data may be present
Essentially the same as Char; unique to CERCLIS
C.1 AFS-AIRS Facility Subsystem Data Elements (7/95)
Group Repeat Element
Record? Name
AFS ID(A) N
PGM CODE(B) N
SOURCE(A) N
HIST COMPILE) Y
POLLUTANT(B) Y
ACTIONS(B) Y
AFSID
APC1
REGN
AQCA
PNME
STRT
CYNM
SIC1
SIC2
SICC
SVI1
SVI2
SVI3
SVI4
DCS1
DCL1
GOVT
VIOLQTR
INSPDAY
HDT1(K)
SCH1
PLAP(K)
DCAP
DCLP
DATT
RUDT
TURN
DTA1(K)
ACSEQ(K)
ANT1
PAM1 '
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N)
Y
Y
Y
Y
N
N
N
Y
Y
Y
Y
N
N
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
S
S
S
S
Char
Char
Char
Num
Char
Char
Char
Num
Num
Num
Char
Char
Char
Char
Char
Char
Char
Num
Num
Date
Char
Char
Char
Char
Char
Date
Num
Date
Num
Char
Num
Length Description
10
1
2
3
26
30
30
4
4
4
1
1
1
1
1
2
1
2
5
4
1
5
1
2
1
4
4
7
4
2
7
AFS Identifier: State-County-Plant Number
Air Program Code
Region
Air Quality Control Region Number
Plant Name
Plant Street Address
Plant City
Primary SIC Code
Secondary SIC Code
SIC Code (Primary Or Secondary)
Significant Violator Flag 1
Significant Violator Flag 2
Significant Violator Flag 3
Significant Violator Flag 4
EPA Compliance Status
EPA Classification Code
AFS Governmental Facility Code
# Qtrs In Violation - Last 2 Years
Days Since Last Inspection
Historical Compliance Date (YYQQ)
Historical Compliance Status
Pollutant Code
Pollutant Compliance Status
Pollutant Classification
Attainment/Non-Attainment Indicator
Repeat Violation Date (YYQQ)
Turnover Compliance Flag
Date Achieved (YYMMDD)
Sequence Number
National Action Type
Penalty Amount
C-2
IDEA User's Guide
February 29, 1996
-------
C.2 CER-CERCLA Information Svstem Data Elements (7195}
Level Repeat Element
Record? Name
0 N 0000
0001
0002
0101
0104
0110
0111
0112
0120
0121
0130
0135
0136
0137
0140
0201
0204
0205
0206
0207
0226
0299
0300
0301
0304
0305
0307
0308
0309
0310
0311
0312
0313
0314
0315
0322
0323
.0326
0327
0350
0364
0399
0400
0491
0492
0493
0494
0495
0496
0497
0498
0500
0510
0511
0512
0142
0151
0152
0153
0139
Index? Enforc Data Length Description
(Y/N) Sens? Type
(Y/S/N)
-
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N •
N
N
N
Y
Y
Y
N
Y
Y
Y
Y
Y
N
N
N
N
N
Y
Y
Y
N
N
N
N
Y
N
N
N
N
N
N
N
N
N
Y
Y
N
Y
Y
N
N
N
N
-
S
s
S
s
s
s
s
s
s
s
s
s
s
s
s
s
s
Y
Y
Y
S
Y
S
S
S
s
s
s
s
s
s
s •
s
s
s
s
s
Y
s
s
s
Y
Y
Y
Y
Y
Y
Y
Y
. Y
S
S
s
s
-
s
s
s
-
Char 2
Char 2
Char 12
Char 40
Char 40
Char 25
, Char 9
Char 25
Char 3
Char 2
Char 1
Char 2
Char 1
Char 4
Text 60
Char 20
Char 10
Char 20
Char 10
Char 2
Date 6
Date 6
Char 1
Char 1
Char 1
Char 1
Char 2
Char 2
Intg 2
Intg 2
Intg 2
Intg 2
Intg 2
Char 4
Char 7
Char 8
Char 1
Char 1
Char 4
Char 8
Char 1
Intg 5
Char 6
Char 1
Char 1
Char 2
Char 3
Char 4
Char 5
Char 10
Char 1
Date 6
Char 6
Char 3
Char 1
Char 1
Char 1
Char 1
Char 2
Entry
Entry-Region
Entry-State
Entry-EPA Id
Emery-Name
Entey-Street
Entey-City
Entty-Zip Code
Enlxy-County Name
Enlxy-County Code
Entry-Congressional District
Entry-Federal Facility Flag
Entry-Ownership Indicator
Entry-Site Incident Category
Entry-Standard Metropolitan Statistical Area
Entry-Description
Entry-RPM/OSC Name
Entry-RPM/OSC Phone
Entry-Regional Contact Name
Entry-Regional Contact Phone
Entry-Classification
Entry-Original Load Date (MMDDYY)
Entry-Last Update (MMDDYY)
'Entry-Name Source
Entry-Federal Facilities Docket Flag
Entry-National Priorities List (NPL) Status
Entry-Incident Type
Entry-Proposed NPL Update Number
Entry-Final NPL Update Number
Entry-Source Count: NOTIS
Entry-Source Count STS
Entry-Source Count: HWDMS
Entry-Source Count Composite
Entry-Source Count: Other
Entry-IFMS Identification Number
Entry-Latitude
Entry-Longitude
Entry-Lat/Long Source
Entry-Lat/Long Accuracy
Entry-S/I Dioxin Tier
Entry-USGS Hydro Unit
Entry-RCRA Facility
Entry-Aggregate Case Budget Obligation
Entry-Regional Fieldl
Entry-Regional Field2
Entry-Regional Fields
Entry-Regional Field4
Entry-Regional Fields
Entry-Regional Field6
Entry-Regional Field?
Entry-Regional Fields
Entry-Selection Criteria
Entry-Date (MMDDYY)
Entry-Time
Entry-User Id
Entry-USACE Flag
Entry-Federal Agency PRP Flag
Entry-State PRP Flag
Entry-Municipal PRP Flag
Entry-Historical Indicator
Appendix C. Data Elements in IDEA Shadow Files
C-3
-------
Level
Repeat Element
Record? Name
0141
0143
0203
0102
0144
0103
0145
0146
Y 1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1142
1139
Y 2100
2101
2102
2103
2104
2105
2106
2107
2108
2109
2110
2111
2113
2114
2115
2116
2117
2118
2120
2121
2122
2123
2130
2131
2132
2133
2137
2138
2139
2140
2141
2157
2158
2159
2160
2161
2162
2163
2164
2165
Index? Enforc Data Length Description
(Y/N) Sens? Type
(Y/S/N)
N
Y
Y
Y
N
N
N ,
N
-
Y
N
Y
N •
N
N
N
N
Y
Y
N
Y
Y
Y
Y
Y
N
-
Y
Y
Y
N
N
N
Y
Y
N
Y
Y
N
Y
Y
Y
Y
Y
N
N
N
N
Y
Y
Y
Y
N
Y
N
Y
Y
N
N
N
N
N
N
N
N
N
.
Y
S
8
Y
S
Y
Y
-
S
S
S
S
S
Y
Y
Y
S
S
S
S
S
-
-
.
-
-
S
S
S
S
Y
S
S
S
S
S
S
Y
S
Y
Y
S
S-
Y
Y
Y
Y
S
S
• s
S
s
s
_
s
s
s
s
Y
Y
Y
Y
Y
Y
S
Char 2
Char 1
Char 9
Char 12
Char 1
Text 5
Char 3
Date 4
—
Char 2
Char 2
Char 14
Char 30
Text 60
Char 2
Char 6
Char 2
Char 3
Date 6
Char 6
Char 4
Char 16
Char 3
Char 19
Char 1
Char 2
—
Char 3
Char 17
Char 1
Char 30
Text 20
Text 10
Char 8
Char 5
Char 2
Char 1
Char 2
Char 3
Char 3
Char 1
Char 1
Char 2
Char 2
Date 6
Date 6
Char 3
Char 3
Date 6
Date 6
Char 3
Char 3
Char 1
Char 2
Char 2
Date 6
Date 6
Char 20
Char 10
Char 10
Char 10
Char 2
Char 2
Char 4
Char 6
Char 4
Entry-Top Chain
Entry-Cost Recovery Indicator
Entry-Section Code
Entry-Finds Id
Entry-Link Audit Flag
Entry-Site Ref Number
Entry-NFRAP Indicator
Entry-NFRAP Date
Operable Units
Operable Unit-Id
Operable Unit-Alias Link
Operable Unit-Concatenation Key
Operable Unit-Name
Operable Unit-Description
Operable Unit-Regional Fieldl
Operable Unit-Regional Field2
Operable Unit-Regional Fields
Operable Unit-User Id
Operable Unit-Date (MMDDYY)
Operable Unit-Time
Operable Unit-Enforcement Activity Type
Operable Unit-Enf Activity Concatenation Key
Operable Unit-Enf Remedy Activity
Operable Unit-Enf Remedy Concatenation Key
Operable Unit-USACE Flag
Operable Unit-Historical Indicator
Events
Event-Type
Event-Concatenation Key
Event-Qualifier
Event-Name
Event-SCAP Note
Event-Short Name
Event-Activity Link
Event-Type Sort
Event-Removal Approval Authority
Event-Planning Status
Event-Generic Type Code
Event-State Percentage Share Of Costs
Event-Takeover Flag
Event-First Start Indicator
Event-First Complete Indicator
Event-Event Lead
Event-Event Category
Event-Original Planned Start Date (MMDDYY)
Event-Orig Planned Complete Date (MMDDYY)
Event-Original Planned Start FY/Quarter
Event-Orig Planned Completion FY/Quarter
Event-Current Planned Start Date (MMDDYY)
Event-Cur Planned Complete Date (MMDDYY)
Event-Current Planned Start FY/Quarter
Event-Current Planned Completion FY/Quarter
Event-VAM Flag
Event-Link Chain
Event-Historical Indicator
Event-Actual Start Date (MMDDYY)
Event-Actual Completion Date (MMDDYY)
Event-Regional Contact Name
Event-Regional Contact Phone
Event-Cooperative Agreement Number
Event-Cooperative Amendment Number
Event-Regional Fieldl
Event-Regional Field2
Event-Regional Field3
Event-Regional Field4
Event-Dummy 01 (Activity Type)
C-4
IDEA User's Guide
February 29, 1996
-------
Level Repeat Element
Record? Name
2166
2167
2168
2170
2171
2172
2145
2146
2147
2148
2149
2150
2151
2152
2153
2154
2155
2156
2124
2125
2134
2135
2142
2143
2144
1901
1902
1911
1912
1913
1914
1915
1916
1917
1918
1919
1920
1921
1922
1923
1924
1925
1927
1928
1931
1932
1933
1934
1935
1936
1937
1938
1940
1941
1942
2173
2174
2175
3 Y 3100
3101
3102
3104
3105
3108
3109
3110
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N)
N
N
N
Y
N
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Y
Y
Y
N
N
N
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Y
Y
'N
N
-
Y
Y
N
N
N
Y
Y
S
s
S
s
s
s
Y
S
Y
Y
Y
S
S
s
s
Y
Y
S
-
-
-
-
-
-
S
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
-
-
-
-
-
Y
Y
Y
Y
Y
Y
Y
Chaf
Char
Char
Date
Char
Char
Char
Char
Char
Char
Char
Intg
Intg
Intg
Intg
Char
Char
Char
Char
Char
Char
Char
Char
Date
Char
Char
Char
Date
Intg
Intg
Intg
Intg
Intg
Intg
Intg
Intg
Char
Char
Char
Char
Char
Char
Char
Char
Intg
Intg
Intg
Intg
Intg
Intg
Intg
Intg
Date
Char
Char
Char
Char
Char
—
Char
Char
Char
Text
Text
Char
Char
Length Description
16
3
19
6
6
3
4
11
20
10
20
5
5
5
5
3
20
4
2
2
2
2
1
6
4
17
1
6
5
5
5
5
5
5
5
5
20
2
20
10
20
10
25
2
2
2
2
2
3
3
3
3
6
6
1
1
2
3
-
3
20
30
20
10
8
5
Event-Dummy 02 (Concatenation)
Event-Dummy 03 (Remedy Activity)
Event-Dummy 04
Event-Date (MMDDYY)
Event-Time
Event-User Id
Everit-(IAG)Interagency Agreement Number
Event-Dummy 05
Event-Corps Contact Name
Event-Corps Contact Phone
Event-Contractor
Event-Dummy 06
Event-Dummy 07
Event-Dummy 08
Event-Dummy 09
Event-Corps District Code
Event-Corps District Name
Event-Dummy 10
Event-Original Planned Start FY
Event-Original Planned Completion FY
Event-Current Planned Start FY
Event-Current Planned Completion FY
Event-USACE Lead Qualifier/Asgn-To
Event-USACE Lead Qualifier/Asgn-Date (MMDDYY)
Eveiit-USACE IAG Amendment Number
Event-USACE Project Key
Event-USACE Project Type
Event-USACE Line Item Review (MMDDYY)
Event-IAG Funding Level
Event-IAG In-House Expended-Past Month
Event-IAG In-House Expended-Total
Event-IAG In-House Obligated Amount
Event-IAG Contract Expended-Past Month
Event-IAG Contract Expended-Total
Event-IAG Contract Obligated Amount
Event-USACE Estimated RA Cost
Event-USACE O & M Contractor Name
Event-USACE Performed By
Event-USACE Contractor Contact Name
Event-USACE Contractor Contact Phone
Event-USACE Onsite Engineer
Event-USACE Onsite Engineer Phone
Event-USACE Contractor City
Event-USACE Contractor State
Event-Construction Percent-To-Date Actual
Event-Construction Percent-To-Date Scheduled
Event-Constr Percent-To-Date Last Month
Event-Constr Percent-To-Date Last FY
Event-Constr Calendar Days Actual
Event-Constr Calendar Days Current
Event-Constr Calendar Days Pending
Event-Constr Calendar Days Original
Event-USACE Date (MMDDYY)
Event-USACE Time
Event-USACE Flag
Event-EPA Priority
Event-Action Type
Event-Action Sequence
Subcvents
Subevent-Id
Subsivent-Concatenation Key
Sub«vent-Name
Subevent-SCAP Note
Sub«vent-Short Name
Subovent-Activity Link
Subevent-Id Sort
Appendix C. Data Elements in IDEA Shadow Files
C-5
-------
Level
4
5
3
3
Repeat Element
Record? Name
3111
3120
3121
3122
3123
3124
3125
3126
3127
3128
3129
3131
3132
3133
3134
3135
3136
3137
3138
3140
3141
3142
3143
3144
3145
3146
3147
3148
3139 -
Y 3500
3501
3502
3503
3504
3505
3506
Y 3510
3511
3512
3513
3514
3515
3516
Y 2190
2191
2192
2193
2194
2195
2196
2197
Y 3200
3201
3202
3203
3204
3205
3206
3207
3208
3218
3220
3225
3228
3229
3230
Index? Enforc Data
(Y/N) Sens? Type
. (Y/S/N)
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Y
Y
Y
Y
Y
N
N
N
N
N
N
N
Y
N
-
N
Y
N
N
Y
N
-
N
Y
N
N
N
N
-
Y
Y
Y
N
N
N
Y
-
Y
Y
Y
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
-
Y
-
-
Y
-
-
Y
Y
Y
-
-
-
-
Y
-
-
-
Y
Y
Y
Y
Y
Y
-
Y
Y
Y
Y
Y
Y
-
Y
Y
Y
Y
Y
Y
Y
-
S
s
Y
Y
S
Y
Y
Y
Y
S
Y
Y
Y
S
Char
Date
Date
Date
Date
Date
Date-
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Date
Char
Char
Char
Char
Char
Char
Char
Char
Char
—
Char
Char
Date
Char
Char
Char
—
Char
Char
Char
Date
Char
Char
—
Char
Char
Char
Date
Char
Char
Char
—
Char
Char
Char
Char
Char
Char
Char
Char
Char
Date
Char
Char
Char
Intg
Length Description
2
6
6
6
6
6
6
3
3
3
3
2
2
4
6
4
16
3
19
6
6
3
2
2
2
2
3
1
2
-
3
23
6
6
2
3
-
2
25
60
6
6
3
-
33
6
10
6
6
3
16
-
3
1
6
10
20
1
10
4
3
6
3
6
1
5
Subevent-Generic Type
Subevent-Original Start Date (MMDDYY)
Subevent-Original Completion Date (MMDDYY)
Subevent-Current Start Date (MMDDYY)
Subevent-Current Completion Date (MMDDYY)
Subevent-Actual Start Date (MMDDYY)
Subevent-Actual Completion Date (MMDDYY)
Subevent-Original Start FY/Quarter
Subevent-Original Completion FY/Quarter
Subevent-Current Start FY/Quarter
Subevent-Current Completion Date FY/Quarter
Subevent-Regional Fieldl
Subevent-Regional Field2
Subevent-Regional Fields
Subevent-Regional Field4
Subevent-Enforcement Activity Type
Subevent-Enf Activity Concatenation Key
Subevent-Enf Remedy Activity
Subevent-Enf Remedy Concatenation Key
Subevent-Date (MMDDYY)
Subevent-Time
Subevent-User Id
Subevent-Original Start FY
Subevent-Original Completion FY
Subevent-Current Start FY
Subevent-Current Completion FY
Subevent-Owner
Subevent-USACE Flag
Subevent-Historical Indicator
Subevent Comments
Subevent Comment-Id
Subevent Comment-Concatenation Key
Subevent Comment-Date (MMDDYY)
Subevent Comment-Time
Subevent Comment-Type Code
Subevent Comment-User Id
Subevent Comment Line
Subevent Comment Line-Number
Subevent Comment Line-Concatenation
Subevent Comment Line-Text
Subevent Comment Line-Date (MMDDYY)
Subevent Comment Line-Time
Subevent Comment Line-User Id
Event Valid Financial
Event Valid Fin-Acct/Doc Control Number
Event Valid Fin-Document Control Number
Event Valid Fin-Account Number
Event Valid Fin-Date (MMDDYY)
Event Valid Fin-Time
Event Valid Fin-User Id
Event Valid Fin-Acn/Dcn Concatenation
Financial
Financial-Id
Financial-Type
Financial-Document Control Number
Financial-Account Number
Financial-Concatenation Key
Financial-IFMS Flag
Financial-Obligating Document Number
Financial-Subobject Class
Financial-Planned Obligation FY/Quarter
Financial-Date (MMDDYY)
Financial-Fund Priority Status
Financial-Work Assignment/IAG Number
Financial-Event Budget Source
Financial-Amount
C-6
IDEA User's Guide
February 29, 1996
-------
Level Repeat Element
Record? Name
3238
3239
3240
3241
3242
3244
3245
3246
3247
3248
3249
3250
3231
3232
3233
3209
3234
3219
3251
3252
3253
3254
3255
3256
4 Y 3600
3601
3602
3603
3604
3605
3606
5 Y 3610
3611
3612
3613
3614
3615
3616
3 Y 2420
2421
2422
2423
2424
2425
2430
2431
2432
2433
2434
2435
2436
3 Y 3300
3301
3302
3303
3304
3305
3306
4 Y 3310
3311
3312
3313
3314
3315
3316
3 Y 3400
Index? Enforc Data Length Description
(Y/N) Sens? Type
(Y/S/N)
Y
Y
Y
N
N
N
N
N
N
Y
N
Y
N
N
Y
Y
N
N
N
N
N
N
N
N
-
N
Y
N
N
Y
N
-
N
Y
N
N
N
N
-
Y
Y
Y
N
Y
N
N '
N
N
N
N
N
-
N
Y
N
N
Y
N
-
N
Y
N
N
N
N
-
Y
Y
Y
Y
Y
Y
Y
Y
-
S
S
S
S
S
S
Y
Y
S
-
-
-
-
-
-
-
Y
Y
Y
Y
Y
Y
-
Y
Y
Y
Y
Y
Y
-
S
S
S
S
S
S
S
S
S
S
S
S
-
Y
Y
Y
Y
Y
Y
-
Y
Y
Y
Y
Y
Y
-
Text 8
Char 5
Char 2
Char 20
Char 30
Char 6
Char 6
Char 6
Char 6
Date 6
Char 6
Char 3
Intg 5
Intg 5
Char 1
Char 16
Char 2
Char 2
Char 4
Char 6
Char 7
Char 9
Char 8
Char 8
—
Char 3
Char 23
Date 6
Char 6
Char 2
Char 3
—
Char 2
Char 25
Char 60
Date 6
Char 6
Char 3
—
Text 6
Text 23
Char 2
Char 3
Text 17
Char 12
Char 2
Char 3
Char 4
Char 6
Date 6
Char 3
—
Char 3
Char 20
Date 6
Char 6
Char 2
Char 3
—
Char 2
Char 22
Char 60
Date 6
Char 6
Char 3
—
Financial-Vehicle Abbreviation
Financial-Vehicle
Financial-FY
Financial-Contractor Name
Financial-Note
Financial-Regional Fieldl
Financial-Regional Field2
Financial-Regional Fields
Financial-Regional Field4
Financial-Update Date (MMDDYY)
Firiancial-Update Time
Financial-User Id
Fkiancial-IFMS Open Commitment
Financial-Total Open Commitment
Financial-IFMS Final Obligation
Financial-Acn/Dcn Concatenation Key
Financial- Work Assignment Amendment Number
Financial-Historical Indicator
Financial-Budget FY
Financial-Fund
Financial-Organization
Fin.ancial-Pgm Element
Financial-Site Project
Financial-Cost Organization
Financial Comments
Financial Comment-Id
Financial Comment-Concatenation Key
Financial Comment-Date (MMDDYY)
Financial Comment-Time
Financial Comment-Type Code
Financial Comment-User Id
Financial-Comment Line
Financial Comment Line-Number
Financial Comment Line-Concatenation
Financial Comment Line-Text
Financial Comment Line-Date (MMDDYY)
Financial Comment Line-Time
Financial Comment Line-User Id
Event Link Record
Event Link Record-Identifier
Event Link Record-Concatenation Key
Event Link-Chain
Event Link-Type
Event Link-Key
Event Link-EPA Id
Event Link-Operational Unit
Event Link-Event
Event Link- Activity
Event Link Record-Time
Event Link Record-Date (MMDDYY)
Event Link Record-User
Event Comments
Event Comment-Id
Event Comment-Concatenation Key
Event Comment-date (MMDDYY)
Event Comment-Time
Event Comment-Type Code
Event Comment-User Id
Event Comment Line
Event Comment Line-Number
Event Comment Line-Concatenation Key
Event Comment Line-Text
Event Comment Line-Date (MMDDYY)
Event Comment Line-Time
Event Comment Line-User Id
Technical Information
Appendix C. Data Elements in IDEA Shadow Files
C-7
-------
Level
4
3
3
3
3
Repeat Element
Record? Name
3401
3402
3403
3404
3405
3406
3407
3408
3409
3410
3411
3415
3418
3419
3420
3421
3422
3439
3424
3425
3426
3427
3428
3429
3431
Y 3440
3441
3442
3444
3445
3446
3447
3448
Y 3700
3701
3702
3703
3704
3705
3706
3707
3709
3710
3711
3712
3713
Y 2180
2181
2182
2187
2188
2189
Y 2500
2501
2503
2504
2505
2506
2507
2511
2512
2513
2514
2515
2516
Y 1980
Index? Enforc Data Length Description
(Y/N) Sens? Type
(Y/S/N)
Y
N
N
N
N
N
N
N
N
N
N
N
Y
Y
Y
N
N
N
N
N
N.
N
N
N
Y
.
Y
N
Y
N
N
N
N
-
Y
N
N
N
N
Y
N
N
N
Y
N
Y
-
Y
Y
N
N
N
-
Y
N
N
N
N
N
Y
Y
N
N
N
N
-
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
_
Y
Y
Y
Y
Y
Y
Y
_
Y
Y
Y
Y
Y
Y
-
-
Y
Y
Y
S
S
S
S
.
Y
Y
Y
Y
-
Y
Y
Y
Y
Y
-
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
-
-
Char 2
Char 2
Char 2
Char 2
Char 2
Char 2
Char 2
Char 2
Char 2
Char 2
Char 2
Char 1
Char 23
Char 24
Date 6
Char 6
Char 3
Char 2
Char 2
Char 1
Date 6
Char 4
Intg 6
Char 5
Char 21
—
Char 3
Intg 4
Text 27
Char 6
Date 6
Char 3
Char 2
—
Char 10
Char 40
Char 40
Date 6
Char 6
Text 31
Char 3
Char 2
Char 4
Char 1
Char 2
Char 21
—
Char 12
Char 29
Date 6
Char 6
Char 3
—
Char 4
Date 6
Intg 6
Char 5
Char 1
Char 2
Char 21
Char 14
Char 6
Date 6
Char 3
Char 2
—
Tech Information-Type
Tech Information-Qualifier 1
Tech Information-Qualifier 2
Tech Information-Qualifier 3
Tech Information-Qualifier 4
Tech Information-Qualifier 5
Tech Information-Qualifier 6
Tech Information-Qualifier 7
Tech Information-Qualifier 8
Tech Information-Qualifier 9
Tech Information-Qualifier 10
Tech Information-Type Suffix
Tech Information-Locate Key
Tech Information-Concatenation Key
Tech Information-Date (MMDDYY)
Tech Information-Time
Tech Information-User Id
Tech Information-Historical Indicator
Tech Information-Contaminated Medium Code
Tech Information-Capping Only
Tech Information-Service Date (MMDDYY)
Tech Information-Contaminating Material
Tech Information-Technology Volume
Tech Information-Volume Unit Of Measure
Tech Info-Material Concatenation Key
Receptors
Receptors-Type Of Affected Population
Receptors-Affected Population
Receptors-Concatenation Key
Receptors-Record Time
Receptors-Record Date (MMDDYY)
Receptors-Record User
Receptors-Historical Indicator
Event Chemicals
Event Chemical-CAS Number
Event Chemical-Name
Event Chemical-Common Name
Event Chemical-Date (MMDDYY)
Event Chemical-Time
Event Chemical-Concatenation Key
Event Chemical-User Id
Event Chemical-Historical Indicator
Event Chemical-Contaminating Material Id
Event Chemical-Category
Event Chemical-Contaminated Medium Code
Event Chemical-Material Concatenation Key
RCRA
RCRA-Offsite Id
RCRA-Concatenation Key
RCRA-Date (MMDDYY)
RCRA-Time
RCRA-User Id
Materials
Materials-Id
Materials-Initial Technology Date (MMDDYY)
M aterials-V olume
Materials-Unit Of Measure
Materials-Needs Future Handling
Materials-Contaminated Medium Code
Materials-Concatenation Key
Materials-Medium Concatenation Key
Materials-Record Time
Materials-Record Date (MMDDYY)
Materials-Record User
Materials-Historical Indicator
Event Narrative
C-8
IDEA User's Guide
February 29, 1996
-------
Level
2
3
1
2
1
2
1
Repeat Element
Record? Name
1981
1982
1983
1984
1985
1986
Y 2300
2301
2302
2303
2304
2305
2306
Y 2310
2311
2312
2313
2314
2315
2316
Y 1200
1201
1202
1204
1212
1213
1214
1205
1219
Y 2200
2201
2202
2210
2211
2212
2213
2222
2223
2270
2272
2273
2274
Y 1300
1301
1302
1303
1304
1305
1306
Y 1310
1311
1312
1313
1314
1315
1316
Y 1400
1401
1402
1403
1404
1405
1406
1407
1408
1410
Index? Enforc , Data Length Description
(Y/N) Sens? Type
(Y/S/N)
N
Y
N
N
N
N
-
N
Y
N
N
Y
N
N
Y
N
N
N
N
-
Y
Y
Y
Y
N
N
N
N
-
Y
Y
N
Y
Y
N
Y
Y
N
N
N
N
-
N
Y
N
N
Y
N
-
N
Y
N
N
N
N
-
Y
N
N
N
N
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
-
Y •
Y
Y
Y
-
Y
-
Y
Y
Y
Y
Y
Y
-
S
S
S
S
S
S
-
-
-
S
S
S
S
S
S
S
S
S
S
S
S
-
Y
Y
Y
Y
Y
Y
-
Y
Y
Y
Y
Y
Y
-
Y
S
S
Y
Y
S
S
S
S
Char 4
Char 21
Text 74
Date 6
Char 6
Char 3
—
Char 3
Char 17
Date 6
Char 6
Char 2
Char 3
—
Char 2
Char 19
Char 60
Date 6
Char 6
Char 3
—
Char 2
Char 14
Char 40
Date 6
Char 6
Char 3
Char 1
Char 2
—
Char 2
Char 16
Char 40
Char 25
Char 9
Char 2
Char 7
Char 8
Text 60
Date 6
Char 6
Char 3
—
Char 3
Char 15
Date 6
Char 6
Char 2
Char 3
—
Char 2
Char 17
Char 60
Date 6
Char 6
Char 3
—
Char 6
Text 60
Date 6
Date 6
Date 6
Char 10
Char 18
Char 16
Date 6
Event Narrative-Line Number
Event Narrative-Concatenation Key
Event Narrative-Text
Event Narrative-Date (MMDDYY)
Event Narrative-Time
Event Narrative-User Id
Operable Unit Comments
Op Unit Comment-Id
Op Unit Comment-Concatenation Key
Op Unit Comment-Date (MMDDYY)
Op Unit Comment-Time .
Op Unit Comment-Type Code
Op Unit Comment-User Id
Operable Unit Comment Line
Op Unit Comment Line-Number
Op Unit Comment Line-Concatenation
Op Unit Comment Line-Text
Op Unit Comment Line-Date (MMDDYY) '
Op Unit Comment Line-Time
Op Unit Comment Line-User Id
Aliases
Alias-Id
Alias-Concatenation Key
Alias-Name
Alias-Date (MMDDYY)
Alias-Time
Alias-User Id
Aliai;-USACE Flag
Alias-Historical Indicator
Alias Location
Alias Location-Sequence Number
Alias; Location-Concatenation Key
Alias-Street
Alias-City
Alias-Zip
Alias-State
Alias-Latitude
Alias-Longitude
Alias-Description
Alias Location-Date (MMDDYY)
Alias; Location-Time
Alias: Location-User Id
Entry Comments
Entry Comment-Id
Entry Comment-Concat Key
Entry Comment-Date (MMDDYY)
Entry Comment-Time
Entry Comment-Type Code
Entry Comment-User Id
Entry-comment Line
Entry Comment Line-Id
Entry Comment Line-Concat Key
Entry Comment Line-Text
Entry Comment Line-Date (MMDDYY)
Entry Comment Line-Tune
Entry Comment Line-User Id
Regional-Utility
Regional Utility-Code
Regional Utility-Description
Regional Utility-Datel (MMDDYY)
Regional Utility-Date2 (MMDDYY)
Regional Utility-DateS (MMDDYY)
Regional Utility-Free Field
Regional Utility-Concat Key
Regional Utility-Locate Key
Regional Utility-Date (MMDDYY)
Appendix C. Data Elements in IDEA Shadow Files
C-9
-------
Level Repeat Element
Record? Name
1411
1412
1419
1 Y 1700
1701
1702
1703
1704
1705
1706
1707
1708
1709
1710
1711
1712
1713
1714
1715
1716
1717
1718
1719
1720
1721
1722
1723
1724
1725
1726
1727
1728
1729
1730
1731
1732
1733
1738
1739
' 1740
1741
1742
1743
1734
1735
1736
1737
1744
1745
1746
1747
1748
1749
1774
1775
2 Y 2710
2711
2712
2713
2714
2718
2719
2720
2 Y 2730
2731
2732
Index?
(Y/N)
N
N
N
-
Y
Y
Y
Y
Y
N
Y
N
N
N
N
N
N
N
N
Y
Y
N
Y
N
N
N
N
N
Y
Y
Y
Y
N
Y
Y
Y
N
Y
N
N
N
N
N
N
N
N
N
Y
Y
N
N
N
N
N
N
_
N
N
Y
Y
N
N
N
_
Y
Y
Enforc
Sens?
(Y/S/N)
S
S
_
-
S
S
S
S
S
S
S
Y
Y
Y
Y
Y
Y
Y
Y
S
S
Y
Y
Y
Y
Y
S
S
Y
Y
Y
S
S
.
S
S
S
S
S
Y
Y
Y
_
_
-
_
-
Y
Y
Y
Y
Y
-
.
_
.
Y
Y
Y
Y
Y
Y
Y
.
Y
Y
Data Length Description
Type
Char 6
Char 3
Char 2
—
Char 4
Char 16
Char 6
Text 10
Char 8
Char 30
Char 2
Date 6
Char 3
Date 6
Char 3
Date 6
Char 3
Date 6
Char 3
Date 6
Date 6
Char 1
Char 2
Intg 3
Char 1
Char 20
Char 20
Char 10
Char 1
Char 1
Date 6
Date 6
Char 6
Char 4
Char 16
Char 2
Char 3
Char 2
Char 2
Char 2
Char 2
Char 4
Char 6
Char 2
Char -2
Char 2
Char 2
Char 60
Char 10
Char 79
Char 15
Text 10
Char 1
Char 2
Char 3
—
Char 1
Date 6
Char 4
Char 20
Date 6
Char 6
Char 3
—
Char 3
Char 21
Regional Utility-Time
Regional Utility-User Id
Regional Utility-Historical In
Enforcement Activities
Enf Act-Type
Enf Act-Concatenation Key
Enf Act-Sort
Enf Act-Abbreviation
Enf Act- Activity Link
Enf Act-Name
Enf Act-Lead
Enf Act-Original Planned Start Date (MMDDYY)
Enf Act-Original Planned Start FY/Quarter
Enf Act-Orig Planned Complete Date (MMDDYY)
Enf Act-Original Planned Complete FY/Quarter
Enf Act-Current Planned Start Date (MMDDYY)
Enf Act-Current Planned Start FY/Quarter
Enf Act-Cur Planned Complete Date (MMDDYY)
Enf Act-Current Planned Complete FY/Quarter
Enf Act-Actual Start Date (MMDDYY)
Enf Act-Actual Complete Date (MMDDYY)
Enf Act-Judicial Civil Type
Enf Act-Negotiation/Litigation Outcome
Enf Act-Number RP Defendants
Enf Act-Full/Partial Settlement
Enf Act-SCAP Note
Enf Act-Contact Name
Enf Act-Contact Phone
Enf Act-Planning Status
Enf Act-Compliance Status
Enf Act-Compliance Change Date (MMDDYY)
Enf Act-Date (MMDDYY)
Enf Act-Time
Enf Act-Enforcement Activity Type
Enf Act-Enf Activity Concatenation Key
Enf Act-Generic Type
Enf Act-User Id
Enf Act-Link Chain
Enf Act-Historical Indicator
Enf Act-Regional Fieldl
Enf Act-Regional Field2
Enf Act-Regional Fields
Enf Act-Regional Field4
Enf Act-Original Planned Start Fy
Enf Act-Original Planned Complete Fy
Enf Act-Current Planned Start Fy
Enf Act-Current Planned Complete Fy
Enf Act-OECM Case Name
Enf Act-OECM Case Number
Enf Act-DOJ Case Name
Enf Act-DOJ Case Number
Enf Act-Outcome Short Name
Enf Act-VAM Flag
Enf Act-Action Type
Enf Act-Action Sequence
Enforcement Activities Compliance
Enf Act Compl-Status
Enf Act Compl-Status Change Date (MMDDYY)
Enf Act Compl-Status Sequence Number
Enf Act Compl-Status Concatenation Key
Enf Act Compl-Date (MMDDYY)
Enf Act Compl-Time
Enf Act Compl-User Id
Enforcement Remedy Action Sought
Enf Rem-Remedy Action
Enf Rem-Concatenation Key
C-10 IDEA User's Guide
February 29, 1996
-------
Level Repeat Element
Record? Name
2733
2741
2742
2743
2744
2745
2746
2747
2748
2749
2750
2751
2752
2753
2754
2755
2756
2757
2734
2735
2736
2738
2739
2760
2761
2762
2763
2764
2765
2766
2767
2768
2769
2 Y 2770
2771
2772
2773
2774
2775
2779
2 Y 2800
2801
2802
2803
2804
2805
2806
2807
2808
2809
2810
2811
2812
2813
2814
2815
2816
2817
2818
2819
2820
2821
2822
2823
2839
3 Y 3800
Index? Enforc Data Length Description
(Y/N) Sens? Type
(Y/S/N)
Y
N
N
N
N
N
N
N
N
N
N
Y
N
Y
N
N
N
N
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
-
Y
Y
Y
N
N
N
-
Y
Y
N
N
N
N
N
N
N
N
Y
Y
Y
N
N
N
N
Y
N
N
Y
N
N
N
-
- Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
-
Y
-
Y
Y
-
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
-
Y
Y
Y
Y
Y
-
-
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
-
-
Y
Y
Y
Y
Y
-
-
-
-
CKar 2
Char 2
Char 2
Char 2
Char 2
Char 2
Char 2
Char 2
Char 2
Char 2
Char 2
Date 6
Char 6
Char 3
Char 2
Char 2
Char 4
Char 6
Char 14
Char 4
Text 10
Char 17
Char 2
Text 10
Text 10
Text 10
Text 10
Text 10
Text 10
Text 10
Text 10
Text 10
Text 10
—
Char 5
Char 21
Date 6
Char 6
Char 3
Char 2
—
Char 3
Char 19
Text 10
Char 30
Date 6
Char 3
Date 6
Char 20
Date 6
Char 3
Char 1
Char 8
Char 5
Char 2
Char 2
Char 4
Char 6
Date 6
Char 6
Char 3
Char 2
' Char 2
Char 2
Char 2
—
Enf Rem-Operable Unit Indicator
Enf Rem-Qualifier 1
Enf Rem-Qualifier 2
Enf Rem-Qualifier 3
Enf Rem-Qualifier 4
Enf Rem-Qualifier 5
Enf Rem-Qualifier 6
Enf Rem-Qualifier 7
Enf Rem-Qualifier 8
Enf Rem-Qualifier 9
Enf Rem-Qualifier 10
Enf Rem-Date (MMDDYY)
Enf Rem-Time
Enf Rem-User Id
Enf Rem-Fieldl
Enf Rem-Field2
Enf Rem-Field3
Enf Rem-Field4
Erf Rem-Operable Unit Concatenation Key
Enf Rem-Special
Enf Rent-Remedy Short Name
Enf Rem-Event Concatenation Key
Enf Rem-Historical Indicator
Enf Rem-Qualifier Short Namel
Enf Rem-Qualifier Short Name2
Enf Rem-Qualifier Short NameS
Enf Rem-Qualifier Short Name4
Enf Rem-Qualifier Short NameS
Erif Rem-Qualifier Short Name6
Enf Rem-Qualifier Short Name?
Enf Rem-Qualifier Short NameS
Enf Rem-Qualifier Short Name9
Enf Rem-Qualifier Short NamelO
Enforcement Statutes
Enf Stat-Statute
Enf Stat-Concatenation Key
Enf Stat-Date (MMDDYY)
Enf Stat-Time
Erf Stat-User Id
Erf Stat-Historical Indicator
Enforcement Milestone
Erf' Ms-Milestone
Erf Ms-Concatenation Key
Erf' Ms-Abbreviation
Erf Ms-Name
Erf Ms-Planned Date (MMDDYY)
Enf Ms-Planned FY/Quarter
Erf Ms-Actual Date (MMDDYY)
Erf Ms-SCAP Note
Erf Ms-Original Planned Date (MMDDYY)
Erf Ms-Original Planned FY/Quarter
Enf Ms-SPMS Target Status
Enf Ms-Activity Link
Erf Ms-Sort
Enf Ms-Regional Fieldl
Enf Ms-Regional Field2
Erf Ms-Regional Fields
Erf Ms-Regional Field4
Erf Ms-Date (MMDDYY)
Erf' Ms-Time
Erf Ms-User Id
Erf Ms-Generic Type
Erf Ms-Planned FY
Erf Ms-Original Planned FY
Erf Ms-Historical Indicator
Enforcement Milestone Comment
Appendix C. Data Elements in IDEA Shadow Files
C-11
-------
Level
4
2
2
3
4
2
Repeat Element
Record? Name
3801
3802
3803
3804
3805
3806
Y 3810
3811
3812
3813
3814
3815
3816
Y 1790
1791
1792
1793
1794
1795
1796
1797
Y 2900
2901
2902
2903
2904
2905
2906
2907
2908
2909
2910
2911
2912
2913
2914
2915
2916
2917
2918
2919
2920
2921
2922
2939
Y 3900
3901
3902
3903
3904
3905
3906
Y 3910
3911
3912
3913
3914
3915
3916
Y 2440
2441
2442
2443
2444
2445
2450
Index? Enforc Data Length Description
(Y/N) Sens? Type
' (Y/S/N)
N
Y
N
N
Y
N
-
N
Y
N
N
N
N
_
Y
Y
Y
N
N
N
Y
-
Y
Y
Y
N
N
N
N
Y
N
N
Y
N
N
N
N
N
N
Y
Y
' N
N
N
N
-
N
Y
N
N
Y
N
-
N
Y
N
N
N
N
-
Y
Y
Y
N
Y
N
Y
Y
Y
Y
Y
Y
-
Y
Y
Y
Y
Y
Y
-
Y
Y
Y
Y
Y
Y
Y
-
Y
S
S
S
S
S
S
Y
Y
Y
S
S
S
Y
•-.
-
-
Y
Y
Y
.
Y
_
-
Y
Y
Y
Y
-
Y
-
Y
Y
Y
Y
Y
Y
-
S
S
S
S
S
S
Char 3
Char 22
Date 6
Char 6
Char 2
Char 3
—
Char 2
Char 24
Char 60
Date 6
Char 6
Char 3
—
Char 32
Char 6
Char 10
Date 6
Char 6
Char 3
Char 16
—
Char 3
Char 19
Char 1
Date 6
Char 3
Date 6
Intg 5
Char 5
Char 3
Char 30
Date 6
Char 6
Char 3
Char 2
Char 2
Char 4
Char 6
Char 1
Char 6
Text 8
Char 2
Char 2
Char 2
—
Char 3
Char 22
Date 6
Char 6
Char 2
Char 3
—
Char 2
Char 24
Char 60
Date 6
Char 6
Char 3
—
Text 6
Text 22
Char 2
Char 3
Text 17
Char 12
Enf Ms Comment-Id
Enf Ms Comment-Concatenation Key
Enf Ms Comment-Date (MMDDYY)
Enf Ms Comment-Time
Enf Ms Comment-Type Code
Enf Ms Comment-User Id
Enforcement Milestone Comment Line
Enf Ms Comment Line-Number
Enf Ms Comment Line-Concatenation Key
Enf Ms Comment Line-Text
Enf Ms Comment Line-Date (MMDDYY)
Enf Ms Comment Line-Time
Enf Ms Comment Line-User Id
Enforcement FMS Valid Financial
Enf FMS Valid Fin-Concatenation Key
Enf FMS Valid Fin-Document Control Number
Enf FMS Valid Fin- Account Number
Enf FMS Valid Fin-Date (MMDDYY)
Enf FMS Valid Fin-Time
Enf FMS Valid Fin-User Id
Enf FMS Valid Fin-Acn/Dcn Concatenation
Enforcement Financial
Enf Fin-Id
Enf Fin-Concatenation Key
Enf Fin-Type
Enf Fin-Planned Date (MMDDYY)
Enf Fin-Planned Fy/Quarter
Enf Fin-Record Date (MMDDYY)
Enf Fin-Amount
Enf Fin-Contract Vehicle
Enf Fin-Funding Status
Enf Fin-Note
Enf Fin-Date (MMDDYY)
Enf Fin-Time
Enf Fin-User Id
Enf Fin-Regional Fieldl
Enf Fin-Regional Field2
Enf Fin-Regional Fields
Enf Fin-Regional Field4
Enf Fin-Budget Source
Enf Fin-Work Assignment lag Number
Enf Fin-Vehicle Abbreviation
Enf Fin-Planned Fy
Enf Fin- Work Assignment Amendment Number
Enf Fin-Historical Indicator
Enforcement Financial Comment
Enf Fin Comment-Id
Enf Fin Comment-Concatenation Key
Enf Fin Comment-Date (MMDDYY)
Enf Fin Comment-Time
Enf Fin Comment-Type Code
Enf Fin Comment-User Id
Enforcement Financial Comment Line
Enf Fin Comment Line-Number
Enf Fin Comment Line-Concatenation Key
Enf Fin Comment Line-Text"
Enf Fin Comment Line-Date (MMDDYY)
Enf Fin Comment Line-Time
Enf Fin Comment Line-User Id
Enforcement Link Record
Enf Link Record-Identifier
Enf Link Record-Concatenation Key
Enf Link-Chain
Enf Link-Type
Enf Link-Key
Enf Link-Epa Id
C-12 IDEA User's Guide
February 29,1996
-------
Level Repeat Element
Record? Name
2451
2452
2453
2454
2455
2456
2 Y 2600
2601
2602
2603
2604
2605
2606
2607
2608
2618
2620
2625
2628
2629
2630
2638
2639
2640
2641
2642
2644
2645
2646
2647
2648
2649
2650
2631
2632
2633
2609
2634
2619
2651
2652
2653
2654
2655
2656
3 Y 3920
3921
3922
3923
3924
3925
3926
4 Y 3930
3931
3932
3933
3934
3935
3936
2 Y 2950
2951
2952
2953
2954
2955
2956
Index? Enforc Data Length Description
(Y/N) Sens? Type
. (Y/S/N) |
N
N
N
N
N
N
...
Y
Y
Y
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
N
Y
Y
Y
N
N
N
N
N
N
Y
N
Y
N
N
Y
Y
N
N
N
N
N
N
N
N
-
N
Y
N
N
Y
N
.
N
Y
N
N
N
N
-
N
Y
N
N
Y
N
S
S
S
S
S
S
-
S
S
Y
Y
S
Y
Y
Y
Y
S
Y
Y
Y
S
Y
Y
Y
Y
Y
_
-
-
-
S
S
S
-
Y
-
Y
Y
-
-
-
-
-
-
-
-
S
S
S
S
-
S
-
S
S
S
S
S
S
-
Y
Y
Y
Y
Y
Y
Char 2
Char 3
Char 4
Char 6
Date 6
Char 3
—
Char 3
Char 1
Char 6
Char 10
Char 19
Char 1
Char 10
Char 4
Char 3
Date 6
Char 3
Char 6
Char 1
Intg 5
Text 8
Char 5
Char 2
Char 20
Char 30
Char 6
Char 6
Char 6
Char 6
Date 6
Char 6
Char 3
Intg 5
Intg 5
Char 1
Char 16
Char 2
Char 2
Char 4
Char 6
Char 7
Char 9
Char 8
Char 8
—
Char 3
Char 22
Date 6
Char 6
Char 2
Char 3
—
Char 2
Char 24
Char 60
Date 6
Char 6
Char 3
—
Char 3
Char 19
Date 6
Char 6
Char 2
Char 3
Enf Link-Operable Unit
Enf Link-Event
Enf Link-Activity
Enf Link Record-Time
Enf Link Record-Date (MMDDYY)
Enf Link Record-User Id
Enforcement FMS
Enf FMS-Id
Enf FMS-Type
Enf FMS-Document Control Number
Enf FMS-Account Number
Enf FMS-Concatenation Key
Enf FMS-FMS Flag
Enf FMS-Obligating Document Number
Enf FMS-Subobject Class
Enf FMS-Planned Obligating Fy/Quarter
Enf FMS-Date (MMDDYY)
Enf FMS-Fund Priority Status
Enf FMS-Work Assignment lag Number
Enf FMS-Event Budget Source
Enf FMS-Amount
Enf FMS-Vehicle Abbreviation
Enf FMS-Vehicle
Enf FMS-Fy
Enf FMS-Contractor Name
Enf FMS-Note
Enf FMS-Regional Fieldl
Enf FMS-Regional Field2
Enf FMS-Regional Fields
Enf FMS-Regional Field4
Enf FMS-Update Date (MMDDYY)
Enf FMS-Update Time
Enf FMS-User Id
Enf FMS-FMS Open Commitment
Enf FMS-Total Open Commitment
Enf FMS-FMS Final Obligation
Enf FMS-Acn/Dcn Concatenation Key
Enf FMS-Work Assignment Amendment Number
Enf FMS-Historical Indicator
Enf FMS-Budget FY
Enf FMS-Fund
Enf FMS-Organization
Enf FMS-Pgm Element
Enf FMS-Site Project
Enf FMS-Cost Organization
Enforcement FMS Comments
Enf FMS Comment-Id
Enf FMS Comment-Concatenation Key
Enf FMS Comment-Date (MMDDYY)
Enf FMS Comment-Time
Enf FMS Comment-Type Code
Enf FMS Comment-User Id
Enforcement FMS Comment Line
Enf FMS Comment Line-Number
Enf FMS Comment Line-Concatenation
Enf FMS Comment Line-Text
Enf FMS Comment Line-Date (MMDDYY)
Enf FMS Comment Line-Time
Enf FMS Comment Line-User Id
Enforcement Activities Comment
Enf Act Comment-Id
Enf Act Comment-Concatenation Key
Enf Act Comment-Date (MMDDYY)
Enf Act Comment-Time
Enf Act Comment-Type Code
Enf Act Comment-User Id
Appendix C. Data Elements in IDEA Shadow Files
C-13
-------
Lcvd
3
1
1
I
1
Repeat Element
Record? Name
Y 2960
2961
2962
2963
2964
2965
2966
Y 1500
1501
1502
1503
1504
1505
1509
Y 1570
1571
1572
1573
1574
1575
1576
1577
1578
Y 1000
1001
1002
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
Y 0990
0991
0992
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N)
.
N
Y
N
N
N
N
-
Y
Y
N
N
N
N
-
Y
N
N
Y
N
N
N
N
-
Y
N
N
N
N
N
N
N
N
N
N
Y
N
Y
-
Y
Y
.
Y
Y
Y
Y
Y
Y
-
Y
Y
Y
Y
Y
-
-
Y
Y
Y
Y
Y
Y
Y
-
-
S
Y
S
S
S
S
S
-
S
S
8
S
S
S
-
S
S
Char
Char
Char
Date
Char
Char
—
Char
Char
Date
Char
Char
Char
—
Char
Char
Char
Char
Char
Date
Char
Char
—
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char.
Char
Date
Char
Char
—
Char
Char
Length Description
_
2
21
60
6
6
3
-
4
16
6
6
3
2
-
2
1
1
14
6
6
3
2
—
14
10
60
10
11
10
2
6
6
1
2
4
6
3
-
4
5
Enforcement Activities Comment Line
Enf Act Comment Line-Number
Enf Act Comment Line-Concatenation Key
Enf Act Comment Line-Text
Enf Act Comment Line-Date (MMDD YY)
Enf Act Comment Line-Time
Enf Act Comment Line-User Id
PRP Agency
PRP Agency-Code
PRP Agency-Concatenation Key
PRP Agency-Date (MMDDYY)
PRP Agency-Time
PRP Agency-User Id
PRP Agency-Historical Indicator
Media
Media-Contaminated Medium Code
Media-Goal Attained
Media-Threat Eliminated
Media-Concatenation Key
Media-Record Time
Media-Record Date (MMDDYY)
Media-Record User Id
Media-Historical Indicator
Latitude Longitude
Lat-Lon-Concat-Key
Lat-Lon-Description-Code
Lat-Lon-Description-Text
Lat-Lon-Latitude
Lat-Lon-Longitude
Lat-Lon-Method-Type
Lat-Lon-Method-Data
Lat-Lon-Method-Scale
Lat-Lon-Accuracy
Lat-Lon-Accuracy-Units
Lat-Lon-Data-Source
Lat-Lon-Date
Lat-Lon-Time
Lat-Lon-User-Id
IDEA
IDEA-Name
IDEA-State/County
C.3 CRM-Criminal Docket Data Elements (7195)
Group
CASE(A)
DEF(B)
CASE(A)
Repeat Element
Record? Name
N STTE
CSNO
N INDX
N CITY
REGN
CSNM
PLAW
MMED
CLEV
CRES
REAS
DAOP
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N)
Y
Y
N
Y
Y
N
Y
Y
Y
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
Char
Char
Num
Char
Char
Char
Char
Char
Char
Char
Char
Date
Length Description
2
9
4
15
2
60
5
1
1
2
2
8
State
Case Number
Index
City
Region
Case-Name
Primary Law
Multi-Media
Case-Level jflk
Case-Result ^^B
Case-Reason ^^^
Case Opened Date (YYYYMMDD)
C-14 IDEA User's Guide
February 29, 1996
-------
Group
MED(A)
LAW(A)
DEF(B)
CIT(B)
ANC(B)
Repeat Element
Record? Name
RTSL
ORDT
DRDT
URDT
GJID
CLDT
Y MEDC(K)
Y LAWS(K)
SECT(K)
N DFNM
CTNO
DFME
DFTY
DICT
DFLV
DFRS
CRME
DAID
DAPL
DAAP
DASN
FINE
IMPR
IMPS
PROB
CTMD
Y CITX(K)
STTS
STSS
CICT
CRCD
Y ANCI(K)
ANTS
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N)
N
N
N
N
N
Y
Y
Y
Y
N
Y
Y
Y
N
Y
Y
Y
N
N
N
N
N
N
N
N
' N
Y
Y
N
N
N
N
N
N
N
' N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
, Date
Date
Date
Date
Date
Date
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Date
Date
Date
Date
Num
Num
Num
Num
Char
Num
Char
Char
' Num
Num
Char
Char
Length Description
8
8
8
8
8
8
1
5
6
50
20
1
1
4
1
2
1
8
8
8
8
9
5
5
5
1
4
10
15
4
4
10
15
Referral To State Date (YYYYMMDD)
Office of Criminal Enforcement-Refer-Date (YYYYMMDD)
Department of Justice-Refer-Date (YYYYMMDD)
US Attorney-Refer-Date (YYYYMMDD)
Grand Jury-Initiated-Date (YYYYMMDD)
Case-Closed-Date (YYYYMMDD)
Media Code
Law
Section
Defendant Name
Court Docket Number
Defendant Media
Defendant Type
District Court
Defendant Level
Defendant Result
Criminal Media
Charges Filed Date (YYYYMMDD)
Plea. Agreement Date (YYYYMMDD)
Appeal Filed Date (YYYYMMDD)
Sentenced Entered Date (YYYYMMDD)
Fine
Imprisonment
Imprisonment Served
Probation
Citation Media
Citation Index
Statute-Title-Citation
Statute-Subsection
Citation-Count of Indictments
Citation-Count of Resulting Convictions
Ancillary Citation
Ancillary Subsection
C.4 DCK-Enforcement Docket Data Elements (7195)
Group
RESP OFFC(A)
CASE NUM(B)
CASE(B)
Repeat Element
Record? Name
N RSOF
N CSNO
N TYPC
CCAT
CSNM
SUBNAME
HQDV
SPCASE3
CSST
REGN
NPLS
RSLT
FPLT
CRCA
ASTA
' OSTA
SSID
AISS
CAFO
CVIO
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N)
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
Y
S
S
S
S
S
S
S
S
S
S
S
S
S
S
Y
S
S
Y
Y
Y
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Num
Num
Char
Char
Char
Date
Date
Date
Length Description
2
10
7
1
60
10
3
4
2
2
1
2
9
9
2
1
4
4
4
4
Responsible Office
Case Number
Typs Case
Case Category
Case Name
Cast; Name (First 10 Characters)
HQ Division
Case Category + HQ Division
Stats
Region
National Priorities List
Case Disposition
Assessed Federal Penalty
Cost Recovery Assessed
Administration Overall Status Code
Enforcement Overall Status Code
Site Spill Identifier
Issued (YYMM)
Final Order Issued (YYMM)
Violation Detected (YYMM)
Appendix C. Data Elements in IDEA Shadow Files
C-15
-------
Group
LAWS(B)
POLLUTANT(B)
VIOLTYPE(B)
PLAINTIFF(B)
INTBRVENOR(B)
DEFENDANT(B)
AMENDMNT(B)
COMMBNT(B)
Repeat Element
Record? Name
Y
Y
Y
Y
Y
Y
Y
Y
CDMD
CRAA
CPRN
CPRC
CPRH
CPRD
CREF
RCHQ
HQRV
CDOJ
CUSA
CFLD
CCNC
CLSD
CRET
CRRE
PART
LAWS(K)
SECT(K)
POLL(K)
VIOT(K)
PLTF(K)
INTV(K)
DFNM(K)
ANUM(K)
ATYP
DINT
DDOJ
DCNC •
DFLD
DPLT
PGNM(K)
LNNM(K)
CSTX
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N)
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
Y
Y
N
N
Y
N
Y
N
N
N
N
Y
N
N
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
S
S
S
Y
Y
S
S
S
S
S
Y
Y
S
Y
S
Y
Y
S
S
Y
Y
Y
Y
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Char
Char
Char
Char
Char
Char
Char
Char
Num
Char
Date
Date
Date
Date
Num
Num
Num
Char
Length Description
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
1
7
7
20
6
40
40
40
2
1
4
4
4
4
9
4
4
60
First Demand Letter Sent (YYMM)
Regional Attorney Assigned (YYMM)
Mini-Lit Package Sent (YYMM)
Mini-Lit Package Received HQ (YYMM)
Mini-Lit Package Reviewed HQ (YYMM)
Mini-Lit Package Reviewed DOJ (YYMM)
Referred (YYMM)
Received HQ (YYMM)
HQ Review (YYMM)
To DOJ (YYMM)
To US Attorney (YYMM)
Filed Court (YYMM)
Concluded (Civil) (YYMM)
Closed (YYMM)
Returned To Region (YYMM)
Re-referred (YYMM)
Partial Indicator
Law - Section
Section
Pollutant
Violation Type
Plaintiff Name
Plaintiff - Intervenor
Defendant Name
Amendment Number
Amendment Type
Date Initiated (YYMM)
Date To DOJ (YYMM)
Date Concluded (YYMM)
Date Filed (YYMM)
Decree Penalty
Page Number
Line Number
Comments - Case Summary Only
C.5 DUN-Dun & Bradstreet Data Elements (7195)
Group Repeat Element
Record? Name
DNUM(B) N DCNO
COMPANY(B) N DNME
SCNM
DSTR
DCTY
DSTA
DZIP
REGN
CNTY
STCNTY
SALESV
ESTRNG
EMPLTOT
ACTRNGT
EMPLHER
ACTRNGH
YRST
STAT
SUBI
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N)
Y
N
N
N
N
N
Y
Y
N
Y
Y
N
Y
N
Y
N
N
N
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Num
Char
Char
Char
Char
Char
Num
Char
Num
Char
Num
Char
Num
Char
Num
Char
Date
Char
Char
Length Description
9
30
30
25
20
2
5
2
3
6
15
1
9
1
9
1
4
1
1
Company Number
Business Name
Second Name
Street Address
City 'Name
State Abbreviation
Zip Code
Region
County FIPS Code
State/County (SS/CCC)
Sales Volume
Code for est/range
Total number of Employees
Code for act/range total
Employees Here '
Code for act/range here
Year Started (YYYY)
Status
Subsidiary Indicator
C-16 IDEA User's Guide
February 29, 1996
-------
Group Repeat Element
Record? Name
MFGI
ULNO
HQNO
DPNO
ULNOFOR
DPNOFOR
HIER
DIAS
DDAT
SIC1
LAT
LONG
LONGLAT
LLMATCH
REGL
SIC2
SIC3
SIC4
SIC5
SIC6
SICC
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N) *
N
Y
Y
Y
Y
Y
N
N
N
N
N
N
Y
N
Y
N
N
N
N
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Char
Num
Num
Num
Num
Num
Num
Num
Date
Num
Num
Num
Num
Char
Char
Num
Num
Num
Num
Num
Num
Length Description
1
9
9
9
9
9
2
9
6
4
5
5
10
1
1
4
4
4
4
4
4
Manufacturing Indicator
Ultimate Number
Headquarters Number
Parent Number
Ultimate Number Foreign (*future
use*)
Parent Number Foreign (*future use*)
Hierarchy Code
Diais Code
Date Of D&B Report (YYMMDD)
SIC Code-1
Latitude In Degrees
Longitude In Degrees
Longitude + Latitude
Lat/Long Match Code
Facility Regulated? (In FINDS)
SIC Code-2
SIC Code-3
SIC Code-4
SIC Code-5
SIC Code-6
SIC Code (any of SIC1 thru SIC6)
C.6 ERN-Emersencv Response Notification System Data Elements (7195)
Group
OOIREPT(A)
002REPT(B)
DSCHG(A)
020REPT(B)
Repeat Element
Record? Name
N STATE
DID
N DTRPT
TMRPT
OWNID
Y DOWNID(K)
DORG
DORGT
DADD
DCOUNTY
DFIPSCO
DCITY
DST
DSTCNTY
DZIP
DPH1
DPH2
DUNS
DREGION
N INIT
MUD
SRC
RSOURCE
RNAME
RNO
RNO2
TRANSNR
MULT
MREPCNT
MCASE
MCASEID
FOLLWUP
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N)
N
N
Y
N
Y
N
N
Y
N
N
N
N
Y
Y
Y
N
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Char
Num
Date
Num
Num
Num
Char
Char
Char
Char
Num
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Num
Char
Num
Char
Length Description
i
2
8
8
4
9
9
32
2
70
20
3
32
2
5
10
17
17
12
2
1
1
2
1
20
12
12
20
1
3
12
8
5
Id State
Discharger Id
Report Date (YYYYMMDD)
Report Time
Unique Identifier
OWNID - Minor Value Link
Discharger Organization
Discharger Organization Type
Discharger Address
Discharger County
Discharger County FIPS Code - Derived
Discharger City
Discharger State
Discharger State/County Code
Discharger Zip
Discharger Phone 1
Discharger Phone 2
Dun & Bradstreet
Discharger Region - Derived
Initial Report
Most Up To Date Report
Agency Receiving Initial Report
EPA Reporting Source Agency Type
EPA Reporting Source Agency Name
Report Number
Case NBR Assigned To Regional
EPA Unique Identifier
Multiple Report Indicator
Multiple Report Count
Multiple Case NBR
Multiple Case Id
Followup Codes
Report
Appendix C. Data Elements in IDEA Shadow Files
C-17
-------
Group Repeat Element
Record? Name
FOLLWCT
CRTYPE
CRNO
DTSPI
TMSPI
DTGTYPE
DNAME
SPILLER
DTDSCVR
MATS
JURI
RPTBL
DTCANCL
HMIS
ERRC
DTHC
ISTAT
DTMEMO
MEMAPPR
ENF1
ENF2
ENF3
ENF4
ENF5
DTPOLR
MONITOR
INVEST
TDDNBR
PHONAST
ERACTVT
DTERA
ERAOSC
DTENTRY
DTCHNG
SPILL(B) N SAMELOC
SCOUNTY
SFIPSCO
SCITY
SST
SSTCNTY
SZIP
SPLREGN
LOCATE
LAT
LONG
QUADLAT
QUADLON
DISTANC
CUNITS
COMPASS
SECTION
TOWN
RANGE
FIELD
BLOCK
MILPOST
MTRLS(B) Y MTRLSEQ(K)
CHEMID
MATSP
CHRIS
UNDOT
CAS
QTYSP
UNITSP
LBS
QUAW
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N)
N
Y
Y
Y
N
N
N
N
Y
N
Y
Y
N
N
N
N
Y
N
N
N
N
N
N
N
N
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
Y
Y
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Y
N
Y
Y
Y
Y
N
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Num
Char
Char
Date
Num
Char
Char
Char
Date
Char
Char
Char
Date
Char
Char
Date
Char
Date
Char
Char
Char
Char
Char
Char
Date
Char
Char
Char
Char
Char
Date
Char
Date
Date
Char
Char
Num
Char
Char
Char
Char
Char
Num
Num.
Num
Char
Char
Num
Char
Char
Char
Char
Char
Char
Char
Char
Num
Num
Char
Char
Char
Num
Num
Char
Num
Num
Length Description
3
1
12
8
4
1
32
1
8
1
1
1
8
3
1
8
1
8
1
2
2
2
2
2
8
1
1
9
1
1
8
20
8
8
1
20
3
32
2
5
10
2
8
4
4
1
1
5
2
3
10
20
10
25
15
5
1.
5
32
3
6
10
6
3
6
6
Count Of Report Updates
Continuous Release Type
Continuous Release Number
Date Spill (YYYYMMDD)
Time Spill
Spill Observation Type
Discharger Name (Individual)
Caller Is Discharger
Discovery Date (YYYYMMDD)
Materials Released Ind
Jurisdiction
Reportable
Date Cancel Letter (YYYYMMDD)
HMIS Code
Data Error Code
Date Hardcopy (YYYYMMDD)
Incident Status
Superfund Action Memo Date (YYYYMMDD)
Superfund Action Memo Approved
Enforcement Activity Code 1
Enforcement Activity Code 2
Enforcement Activity Code 3
Enforcement Activity Code 4
Enforcement Activity Code 5
Pollution Report Issued Date (YYYYMMDD)
On Scene Monitoring
Release Investigation
Technical Direction Doc NBR
Telephone Assistance
Superfund Compr Accomp Plan Activity
Date Of Emer Resp Activity (YYYYMMDD)
Emer Response On-Scene Coordinator
Date Of Entry (YYYYMMDD)
Date Of Change (YYYYMMDD)
Spill At Caller/Discharger Site
Spill County
Spill Location County Code - Derived
Spill City
Spill State
Spill Location State/County Code
Spill Zip
EPA Region Where Spill Occurred
Latitude/Longitude
Latitude
Longitude
Latitude Quadrant
Longitude Quadrant
Distance From City
Distance From City Units
Compass Heading
Section
Township
Range
Field Id
Block Id
Milepost
Material Spilled Sequence Nbr
Nat'l Transportation Sys Cntr Chem-id
Material Spilled
Chemical Hazards Response Info Sys Code
DOT Hazardous Substance Code
Chemical Abstracts Svc Registry Number
Quantity Spilled
Quantity Spilled Units
Quantity In Pounds
Quantity In Water
C-18 IDEA User's Guide
February 29, 1996
-------
Group Repeat Element
Record? Name
UNITSW
DETLS(B) N CONTANR
TANKCNT
TANKCAP
TUNITS
FACCAP
FUNITS
MODE
MODE!
MODE2
VID
SOURCE
MAIR
MLAND
MWATER
MGRDWTR
MFAC
MOTH
MEDCODE
MEDDESC
TRANS
EQUIP
OPERR
NATURAL
DUMPING
UNKNOWN
COTH
CAUSE
INJS
DEATHS
EVAC
EVACS
DAMAGES
PROPDMG
ROAD
FLIGHT
THREAT1
THREAT2
THREATS
THREAT4
THREAT5
ACTN(B) N CNEPA
CNSTLOC
CNDSCH
CNUSCG
CNOTH
CNUNK
CNOTIF
NTSBHWY
NTSBPIP
NTSBRR
RSPAOHM
RSPAOPS
DOTFRA
DOTFAA
DOTOMCS
MISCNRC
MISCDOE
MISCFEM
MISCDOD
MISCATS
MISCOSH
MISCTEC
AGENCY
TMOTH
REGION
Index? Enforc Data Length Description
(Y/N) Sens? Type
(Y/S/N)
N
N
N
N
N
N
N
Y
N
N
N
Y
Y
Y
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
.N
N
N
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Char 3
Char 1
Num 3
Num 6
Char 3
Num 6
Char 3
Char 1
Char 1
Char 1
Char 20
Char 2
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 2
Char 40
Char, 1
Char 1
'Char 1
Char 1
Char 1
Char 1
Char 1
Char 2
Num 3
Num 3
Char 1
Num 5
Char 1
Num 6
Char 1
Char 1
Char 2
Char 2
' Char 2
Char 2
Char 2
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 30
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1 .
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 40
Num 4
Char 2
Quantity In Water Units
Container Type
Tank Count
- Tank Capacity
Tank Capacity Units
Facility Capacity
Facility Capacity Units
Transport Mode
Transport Mode 1
Transport Mode 2
Vehicle Id
Source Code
Medium - Air
Medium - Land
Medium - Water
Medium - Groundwater
Medium - Facility
Medium - Other
Medium Code
Medium Description
Trans Accident
Equipment Failure
Operator Error
Natural Phenomenon
Dumping
Cause Unknown
Other Cause
Cause Code
Injuries
Deaths
Evacuation Ind
Number Of Evacuations
Damage Ind
Property Damage $
Road Closure
Flight Pattern Altered
Threat Code 1
Threat Code 2
Threat Code 3
Threat Code 4
Threat Code 5
EPA Notified By Caller
State/Local Govt Notified By Caller
Discharger Notified By Caller.
US Coast Guard Notified By Caller
Other Agency Notified By Caller
Unknown If Parties Notified By Caller
Other Agency Notified By Caller
NTSB Highway Administration Notified
NTSB Pipeline Safety Notified
NTSB Railway Administration Notified
RSPA/OHM Notified
RSPA/OPS Notified
Department Of Transportation FRA Notified
Department Of Transportation FAA Notified
Department Of Transportation OMCS Notified
Nuclear Regulatory Commission Notified
Department Of Energy Notified
FEMA Notified
Department Of Defense Notified
ATSDR Notified
OSHA Notified
Chemtrec Notified
Other Agency Notified
Time Other Agencies Notified
EPA Region Initially Notified
Appendix C. Data Elements in IDEA Shadow Files
C-19
-------
Group Repeat Element
Record? Name
TMEPA
CGU
TMCGU
RNAME1
RNAME2
RNAME3
RAGCY1
RAGCY2
RAGCY3
DO
TEXT(B) N ATEXT
DTEXT
LTEXT
MTEXT
MTEXTX
Index? Enforc Data
(Y/N) Sens? Type
_CY/S/N)
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
. N
N
N
N
N
N
N
N
N
Num
Char
Num
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Length Description
4
5
4
30
30
30
1
1
1
20
142
255
142
255
29
Time EPA Notified
Coast Guard Unit
Time Coast Guard Notified
Responding Agency 1
Responding Agency 2
Responding Agency 3
Responding Agency 1
Responding Agency 2
Responding Agency 3
Code
Code
Code
National Response Center Duty Officer
Action Text
Description Text
Location Text
Miscellaneous Text
Miscellaneous Text
CJ FFI-Federal Facilities Information Svstem Data Elements (7195)
Group
FF ID(A)
PROJ NUM(B)
FACL(A)
PROJECT(B)
LAWS(B)
Repeat Element
Record? Name
N FFID
AGCY
AGBU
N PRJN
N REGN
REGK
FNAM
DDAC
STRT
CITY
ZIPC
CTRY
N PNAM
PMED
STFL
PRGC
CMFY
CRFF
CPST
POLC
AGFA
EPPA
FCRQ
Y STTE(K)
SECN(K)
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N)
Y
Y
Y
Y
Y
Y
Y
N
N
Y
Y
N
N
Y
Y
Y
N
N
Y
Y
N
N
N
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Char
Char
Char
Char
Char
Chat.
Char
Char
Char
Char
Num
Char
Char
Char
Char
Char
Date
Char
Char
Char
Char
Char
Num
Char
Char
Length Description
12
2
4
10
2
13
50
1
30
30
9
3
50
2
1
1
2
1
4
4
1
1
4
7
7
Federal Facility Id Number
Agency Code
Agency + Bureau Code
Project Number
Region
Region + State + AGBU + GS A Installation
Facility Name
Department Of Defense Agency Code
Street
City
Zip Code
Country
Project Name
Media
Status Flag
Progress Code
Completion Fiscal Year (YY)
Current Funding Flag
Compliance Status
Pollutant Category
Agency Project Assessment
EPA Project Assessment
Final Compliance Required
Statute
Section
Number + Record Type
C-20 IDEA User's Guide
February 29,1996
-------
C.8 FIN-Facttitv Index System Data Elements (1196)
Group Repeat Element
Record? Name
FAC ID(B) N EPID
NAMES(B) N UDATE
CDATE
NAME
ADDRESS
SECADDR
CITY
STATE
ZIP
REGION
CNTYCD
FEDFAC
INDLAND
SECNAME
COMMENT
VNAME
VADDR
VCITY
VSTATE
VZIP
VREGION
VCNTYCD
VLATD
VLONG
IDENT(B) Y SRCE(K)
SRID(K)
SRIDSEQ(K)
FNME
STR1
FCTY
STAT
FZIP
REGN
FCTC
STCNTY
LATD
LONG
LLACC
LLCOMM
LONGLAT
Index? Enforc Data Length Description
(Y/N) Sens? Type
(Y/S/N)
Y
Y
Y
N
N
N
N
Y
Y
Y
N
Y
Y
N
N
N
N
N
Y
Y
Y
N
N
N
N
N
N
N
N
N
Y
Y
Y
N
Y
N
N
N
N
Y
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
Char 12
Date 8
Date 8
Char 50
Char 50
Char 20
Char 30
Char 2
Num 5
Char 2
Num 3
Char 1
Char 1
Char 50
Char 60
Char 50
Char 50
Char 30
Char 2
Num 5
Char 2
Num 3
Real 5
Real 5
Char 1
Char 19
Num 3
Char 50
Char 90
Char 30
Char 2
Num 5
Char 2
Num 3
Char 6
Num 5
Num 5
Num 5
Char 60
Num 10
EPA Id
Update Date (yyyymmdd)
Create Date (yyyymmdd)
Facility Name
Facility Address
Secondary Address
City
State
ZIP Code
EPA Region
County Code
Federal Facility Indicator
Indian Land Indicator
Secondary Name
Analyst Comment (first or only line)
IDEA-voted Facility Name (all linked
IDEA-voted Facility Address
IDEA-voted City
IDEA-voted State
IDEA-voted ZIP Code
IDEA-voted Region
IDEA-voted County Code
IDEA-voted Latitude in Degrees
IDEA-voted Longitude in Degrees
Source File
Source Id
Sequence Number
Facility Name
Street Addressl
City
State
Zip Code
Region
FIPS County Code
databases voting)
State + FIPS County Code (SS/CCC)
Latitude In Degrees
Longitude In Degrees
Accuracy In Degrees
Lat/Long Description, Method, Comments
Longitude + Latitude
C.9 LSI-Contractor Listing Docket Data Elements (7195)
Group
RSOF(A)
CASE(B)
CASE(B)
Repeat Element
Record? Name
N RSOF
N CSNO
N TYPC
CSNM
HQDV
CSST
REGN
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N)
Y
Y
Y
N
Y
Y
Y
S
S
S
S
S
S
S
Char
Char
Char
Char
Char
Char
Char
Length Description
2
10
7
60
3
2
2
Responsible Office
Case Number
Type Case
Case Name
HQ Division
State
Region
Appendix C. Data Elements in IDEA Shadow Files
C-21
-------
Group Repeat Element
Record? Name
EPID
FTYP
RGNM
HQNM
DJNM
USNM
RCNM
GCNM
HCNM
RFIN
VIOC
CCST
DCOP
DCIN
DCLS
DCCL
SRMD
LONM
SANM
SCNM
CENM
OLNO
DRRL
DPTA
DCFA
DAAB
DPNS
DPNR
DRHR
DDES
DHEA
DCED
DCNS
DCNR
DARO
DOGD
DLIS
DAAD
DCNL
DONL
DWDR
MPRR
MRGR
MRRR
MARE
MARR
MAAR
MARC
MJDG
MLIS
MLRM
MCDM
RRRR
RRTR
RFRG
RRTA
RFAE
RRDN
RDNR
RRHR
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N)
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
N
N
Y
N
N
N
N
N
N
N
N
N
Y
N
N
N
Y
N
N
N
N
N
N
N
Y
Y
Y
Y
N
N
N
N
N
Y
N
N
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
S
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
S
S
S
Y
Y
Y
Y
Y
Y
Y
Y
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Num
Date
Date
Date
Date
Date
Char
Char
Char
Char
Char
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Date
Length Description
m
12
3
15
15
15
15
15
15
15
2
4
3
9
9
9
9
9
15
15
15
15
7
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
9
EPA Id Number ^^
Facility Type
Region Attorney
HQ Attorney
Department Of Justice (DOJ) Attorney
US Attorney
Regional Contact
Office of General Counsel (OGC) Attorney
HQ Contact
Referral Indicator
Violator Category
Contractor Case Status
Date Case Opened (YYYYMMDD)
Date Case Initiated (YYYYMMDD)
Date Case Listed (YYYYMMDD)
Date Case Closed (YYYYMMDD)
Schedule Removal Date (YYYYMMDD)
Listing Official
State Attorney
State Contact
Case Examiner
Old Case Number
Date Discretionary Recommendation Received by Listing Officer
(LO) (YYYYMMDD)
Disc Package To AEC (YYYYMMDD)
Disc Comnt From AEC (YYYYMMDD)
Disc Assitant Administrator Briefed (YYYYMMDD)
Disc Proposed NT Sent (YYYYMMDD)
Disc Proposed NT Received (YYYYMMDD)
Disc Req Hear Received (YYYYMMDD)
Disc Case Examiner (CE) Designated (YYYYMMDD) jttk
Disc Hearing (YYYYMMDD) ^B
Disc Case Examiner Decision (YYYYMMDD) ^^^
Disc Case Examiner Decision NT Sent (YYYYMMDD)
Disc Case Examiner Dec NT Received (YYYYMMDD)
Disc Appeal Req Office of General Counsel (OGC)
(YYYYMMDD)
Date of Disc Office of General Counsel (OGC) Decision
(YYYYMMDD)
Disc Listed (YYYYMMDD)
Effective Date In Notice Sent to the Facility That AA Has Declined
To List The Facility (YYYYMMDD)
Disc Case Examiner Dec Not Listed (YYYYMMDD)
Disc OGC Dec Not Listed (YYYYMMDD)
Disc Withdrawn (YYYYMMDD)
Mandatory Date That Petition For Removal Is Received From
Facility (YYYYMMDD)
Mandatory Region Review (YYYYMMDD)
Mandatory Region Rev Received (YYYYMMDD)
Mandatory AEC Review (YYYYMMDD)
Mandatory AEC Review Received (YYYYMMDD)
Mandatory AA Review (YYYYMMDD)
Mandatory AA Review Received (YYYYMMDD)
Mandatory Judgement (YYYYMMDD)
Mandatory Listed (YYYYMMDD)
Mandatory Listed And Removed (YYYYMMDD)
Mandatory Case Dismissed (YYYYMMDD)
Removal— Request Received from Contractor by Listing Officer
(YYYYMMDD)
Removal-Request To Region (YYYYMMDD)
Removal-From Region (YYYYMMDD)
Removal-Resp To AEC (YYYYMMDD)
Removal-From AEC (YYYYMMDD) ^fth
Removal-Remove Deny NT (YYYYMMDD) BV
Removal-Deny NT Rec (YYYYMMDD) ^^
Removal-Request Hearing (YYYYMMDD)
C-22 IDEA User's Guide
February 29, 1996
-------
Group
POLL(B)
LAW(B)
CFR(B)
RLFS(B)
BASI(B)
SDWA(B)
CRVL(B)
PEFA(B)
PRRM(B)
CSCM(B)
FCIN(B)
Repeat Element
Record? Name
RCDG
RHER
RCED
RCDN
RCDR
RADD
RADM
RREM
Y POLL(K)
Y LAW(K)
SECT(K)
Y CFRT(K)
CFRS(K)
Y RLFS(K)
Y BLAW(K)
BACT(K)
Y SDWAPG(K)
SDWALN(K)
SDWA
Y CRVLPG(K)
CRVLLN(K)
CRVL
Y PEFAPG(K)
PEFALN(K)
PEFA
Y PRRMPG(K)
PRRMLN(K)
PRRM
Y CSCMPG(K)
CSCMLN(K)
CSCM
Y FCINPG(K)
FCINLN(K)
FCIN
Index? Enforc Data Length Description
(Y/N) Sens? Type
(Y/S/N)
N
N
N
N
N
N
N
Y
Y
Y
Y
Y
N
Y
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Y
Y
Y
Y
Y
Y
Y
S
S
S
S
S
S
S
S
S
S
S
S
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Date 9
Date 9
Date 9
Date 9
Date 9
Date 9
Date 9
Date 9
Char 20
Char 7
Char 7
Char 5
Char 20
Char 4
Char 3
Char 3
Num 4
Num 4
Char 60
Num 4
Num 4
Char 60
Num 4
Num 4
Char 60
Num 4
Num 4
Char 60
Num 4
Num 4
Char 60
Num 4
Num 4
Char 60
Removal-Case Examiner Designated (YYYYMMDD)
Removal-Hearing (YYYYMMDD)
Removal-Case Examiner Decision (YYYYMMDD)
Removal-Case Examiner Decision NT (YYYYMMDD)
Removal-Case Examiner Decision NT Received (YYYYMMDD)
Removal-Appeal Adm Req (YYYYMMDD)
Removal-Adm Decision (YYYYMMDD)
Removed (YYYYMMDD)
Pollutant
Law
Section
Code-Fed-Reg (CFR) Title
Code-Fed-Reg (CFR) Section
Relief Sought
Bads Law
Basis Action
Standards Which Apply Page
Standards Which Apply Line
Standards Which Apply Comment
Continuing Or Recurring Viol Page
Continuing Or Recurring Viol Line
Continuing Or Recurring Viol Comment
Prerequisite Enforcement Action Page
Prerequisite Enforcement Action Line
Prerequisite Enforcement Action Comment
Proposed Remedy Page
Proposed Remedy Line
Proposed Remedy Comment
Case Status Comments Page
Case Status Comments Line
Case Status Comments Comment
Facility Information Page
Facility Information Line
Facility Information Comment
Group
Repeat Element
Record? Name
Index? Enforc Data Length Description
(Y/N) Sens? Type
(Y/S/N)
INDEP(A)
SAMPS(B)
COMMN(A)
IDENT(A)
N NCDBID
N SAMPNBR
N INVSTYP
LEGISLA
PRODUCT
REASON
REFERRL
REGION
RGNSTAT
Y NAMESEQ(K)
NAMETYP
NAME
ADDRESS
CITY
STATE
ZIP
ZIPS
SICLIST
SIC
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
N
N
Y
N
Y
N'
Y
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
Char 19
Char 3
Char 3
Char 1
Char 14
Char 3
Char 2
Char 2
Char 2
Char 1
Char 8
Char 40
Char 40
Char 20
Char 2
Char 10
Num 5
Char 29
Char 4
NCDB Identifier
Sample Number
Investigation Type Code
Legislation/Statute Code
EPA Registration Number for Product
Reason for Inspection Code
Referral Type Code
EPA Region Code
Region/State/Territory/Tribe Code
Sequence Number for Name
Name Type (Inspect, Import, etc)
Name
Street Address
City Name
State/Territory Abbreviation
ZIP Code (XXXXX-YYYY)
ZIP Code (5-digit)
SICs - up to 6 4-digit codes
SIC Code (any SIC in SICLIST)
Appendix C. Data Elements in IDEA Shadow Files
C-23
-------
Group
INSPECT(A)
REFBRRAL(A)
ACTIONS(A)
TBRMS(A)
Repeat Element
Record? Name
DUN
N AUDITS
EPESTAB
FACILIT
FED F AC
INSPDTE
INSPNBR
NBRSAMP
SCHLTYP
SCHOOLS
CASNMBR
CERTIF
CHEMFRM
CHEMNAM
ENTRYDT
ENTRYNO
INVENTY
N DESTIN
DOCCASE
ENFISSU
ENFTARG
ENFWARR
INSTARG
INSPCON
INSPECT
ORIGIN
REFDATE
REFTYPE
REFERBY
REQRECD
SAMPLES
N ABATEMN
ACTNTYP
AOISSUE
APPEAL
CHEMICL
CLOSED
DATEVAC
FNLPENL
HQCONCR
PROPENL
REFERHQ
SENTHQQ
VIOCDE
VIOCODS
CAFOMAI
CAFOREC
CAFOTHM
CAFOUS
DISACTN
FNDDEC
HEARHLD
MAISSUE
MAWITHD
REFRDOJ
SNC
ADMJUD
NUMEBES
STATUS
Y TERMSEQ(K)
COST
DUE
EBE
PPCODE
REC
Index?
(Y/N)
N
N
N
Y
Y
Y
Y
N
Y
N
Y
Y
N
N
Y
N
Y
N
N
Y
Y
Y
Y
Y
Y
N
Y
Y
N
Y
N
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
N
Y
N
N
N
N
N
N
N
Y
N
N
Y
Y
Y
Y
N
N
N
Y
N
N
Enforc
Sens?
(V/S/N)
S
s
S
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
s
Y
s
s
s
s
Data Length Description
Type
Char 11
Num 4
Char 12
Char 2
Char 1
Date 8
ChaF 5
Num 4
Char 1
Num 4
Char 10
Char 3
Char 60
Char 60
Date 8
Char 15
Char 1
Char 2
Char 15
Date 8 '
Date 8
Char 1
Date 8
Date 8
Char 13
Char 2
Date 8
Char 2
Char 20
Date 8
Char 1
Num 9
Char 3
Date 8
Date 8
Char 20
Date 8
Date 8
Num 9
Date 8
Num 9
Date 8
Date 8
Char 23
Char 3
Date 8
Date 8
Date 8
Date 8
Date 8
Date 8
Date 8
Date 8
Date 8
Date 8
Char 1
Char 1
Num 4
Char- 1
Num 4
Num 9
Date 8
Char 1
Char 3
Date 8
JMk
— •
DUNS Number With Dashes ^^
Number of Audits During Inspection
Pesticide Producer Establishment Number
Facility Function Code
Federal Facility Flag
Date of Inspection (YYYYMMDD)
Inspector Number - IIIII
Number of Samples Taken
School System Type Code
Number of Schools Inspected
• CAS Number of Chemical Investigated
Status of Chemical Srch/Recs Review
Formula of Chemical Investigated
Name of Chemical Investigated
Date of Import (YYYYMMDD)
Import Number of Chemical Investigated
TSCA Inventory Status of Chemical TARIFF N Char 10
Tariff Schedule Number
Destination of Referral Code
Docket or Case Number
Date Enforcement Action Issued (YYYYMMDD)
Date Enforcement Action Targeted (YYYYMMDD)
Enforcement Action Warranted Flag
Date Inspection Targeted (YYYYMMDD)
Date Inspection Conducted (YYYYMMDD)
Inspection Number (YYYYMMDDIIIISS)
Origin of Referral Code
Date of Referral (YYYYMMDD)
Referral Type
Referred By (Person/Company/etc.)
Date Referral Request Received (YYYYMMDD) JJjt
Samples To Be Taken flag (Y/N) Mj
Abatement Work (in dollars) ^^
Action Type Code
Date Minor Action Issued (YYYYMMDD)
Date of Appeal (YYYYMMDD)
Name of Chemical in Enforcement Action
Date Action is Closed (YYYYMMDD)
Date Action is Vacated (YYYYMMDD)
Final Penalty Assessed (dollars)
Date of HQ Concurrence (YYYYMMDD)
Proposed Penalty (dollars)
Date of Referral to HQ (YYYYMMDD)
Date Action Sent to HQ (YYYYMMDD)
Violation Codes (Max of six)
Violation Code (any Code in VIOCDE)
Date CAFO Mailed (YYYYMMDD)
Date CAFO Received (YYYYMMDD)
Date CAFO Signed (Them) (YYYYMMDD)
Date CAFO Signed (EPA) (YYYYMMDD)
Date of District Court Action (YYYYMMDD)
Date of ALJs Decision (YYYYMMDD)
Date of Hearing (YYYYMMDD)
Date Major Action Issued (YYYYMMDD)
Date Major Action Withdrawn (YYYYMMDD)
Date Action Referred to DOJ (YYYYMMDD)
Significant Noncomplier Flag
Administrative/Judicial Action Flag .'
Number of EBE Settlement Terms
Action Status (Open/Closed/Withdrawn)
Sequence Number
Cost to Respondant per EBE Term
Date Settlement Conditions Due (YYYYMMDD) JJf
Env. Beneficial Expenditure Flag ^j
Pollution Prevention Type Code
Date Settlement Conditions Term Received (YYYYMMDD)
C-24 IDEA User's Guide
February 29, 1996
-------
Group
GRANT(A)
CASESMPL(B)
MULTACTS(B)
Repeat Element
Record? Name
TERM
AMTMIT
N AGUSE
AGFOLLO
NAGUSE
NAGFOLL
EXPERIM
PROESTB
MARKET
IMPORTS
EXPORT
CERTAPL
RUPDEAL
TOTAL
PVTAPPL
COMMAPP
AGRLPLT
AGRLANL
FOREST
ORNTURF
SEEDTRE
AQUATIC
RGHTOFW
INDSTRH
PBLHEAL
REGULA
DEMORES
OTHER
N ACTWRNT
COMPDTE
DATESNT
MEDIUM
SPRODCT
VOLATIV
Y ACTNID(K)
IACTNTY
IAOISSU
ICLOSED
IFNLPEN
IPROPEN
IRGNSTA
IVIOCDE
IVIOCOD
ICAFOMA
ICAFOUS
IMAISSU
IMAWITH
IREFRDO
ISNC
IADMJUD
INUMEBE
ISTATUS
Index? Enforc Data Length Description
(Y/N) Sens? Type
(Y/S/N)
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
N
Y
N
N
Y
N
N
Y
Y
Y
Y
S
Y
S
S
S
S
S
S •
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
. s
S
s
s
s
s
s
Char 50
Num 9
Num 7
Num 7
Num 7
Num 7
Num 7
Num 7
Num 7
Num 7
Num 7
Num 7
Num 7
Num 10
Num 7
Num 7
Num 7
Num 7
Num 7
Num 7
Num 7
Num 7
Num 7
Num 7
Num 7
Num 7
Num 7
Num 7
Char 1
Date 8
Date 8
Char 3
Char 14
Char 1
Char 19
Char 3
Date 8
Date 8
Num 9
Num 9
Char 2
Char 23
Char 3
Date 8
Date 8
Date 8
Date 8
Date 8
Char 1
Char 1
Num 4
Char 1
Description of Term
Amount Mitigated for EBEs (dollars)
State Form 5700-33 H Agricultural Use Inspections
State Form 5700-33H Agricultural Followup Inspections
State Form 5700-33 H Nonagricultural Use Inspections
State Form 5700-33H Nonagricultural Followup Inspections
State Form 5700-33H Experimental Use Inspections
State Form 5700-33 H Producing Establishment Inspections
State Form 5700-33H Marketplace Inspections
State Form 5700-33H Imports Inspections
State Form 5700-33H Exports Inspections
State Form 5700-33H Certified Applicator Inspections
State Form 5700-33H RUP Dealer Inspections
State Form 5700-33H Total of All Inspections
State Form 5700-33H Private Applicators
State Form 5700-33 H Commercial Applicators
State Form 5700-33 H Agricultural/Plant Applicators
State Form 5700-33 H Agricultural/ Animal Applicators
State Form 5700-33H Forest Applicators
State Form 5700-33H Ornamental and Turf Applicators
State Form 5700-33H Seed Treatment Applicators
State Form 5700-33 H Aquatic Applicators
State Form 5700-33H Right of Way Applicators
State Form 5700-33H Industrial/Health Applicators
State Form 5700-33H Public Health Applicators
State Form 5700-33 H Regulatory Commercial Applicators
State Form 5700-33H Demonstration/Research Applicators
State Form 5700-33 H Other
Action Warranted Flag
Date Case Review Completed (YYYYMMDD)
Date Sample Sent to Lab (YYYYMMDD)
Sample Medium Code
EPA Registration Number of Sample Product
Violative Sample Flag
Case or Docket Number
Action Type Code
Date Minor Action Issued (YYYYMMDD)
Date Action is Closed (YYYYMMDD)
Final Penalty Assessed (dollars)
Proposed Penalty (dollars)
Region/State/Territory Issuing Action
Violation Codes (Max of six)
Violation Code (any Code in IVIOCDE)
Date CAFO Mailed (YYYYMMDD)
Date CAFO Signed (EPA) (YYYYMMDD)
Date Major Action Issued (YYYYMMDD)
Date Major Action Withdrawn (YYYYMMDD)
Date Action Referred to DOJ (YYYYMMDD)
Significant Noncomplier Flag
Administrative/Judicial Action Flag
Number of EBB Settlement Terms
Action Status (Open/Closed/Withdrawn)
C.ll OSH-Occuvational Safety & Health Administration Data Elements (7195\
Group
Repeat Element Index? Enforc Data Length Description
Record? Name (Y/N) Sens? Type
(Y/S/N)
ESTABLMT(A)
N
ESTABST
N
Char 2
Establishment State
Appendix C. Data Elements in IDEA Shadow Files
C-25
-------
Group Repeat Element
Record? Name
ESTABNR
ACTIVITY(B) N ACTIVTY
STEM(B) N HISTFLG
DTMOD
OFFICE
REGION
CSHOJOB
CSHO
ESTAB
SITE
SITEST
SITEZIP
SITECNT
STCNTY
SITECTY
STCITY
DTOPEN
INSPCAT
INSPTP
INSPSCO
SICPRIM
DTEXIT
STATUS
DTCLOSE
UNION
TOTEMPL
SITEMPL
INSEMPL
RPTLOCL
HRSPREP
HRSTRAV
HRSSITE
HRSSUPP
HRSRPT
HRSCONF
HRSLITG
HRSDENI
HRSTOT
ADVNTC
ESTABTP
NALINK
PREVACT
DUDTSRC
DTPEN
AMTPEN
AMTRPEN
VIOLS
SRVIOLS
LWDI
STFLG
SAFTMAN
SAFTCON
SAFTMAR
HLTHMAN
HLTHCON
HLTHMAR
EMPLINT
EMPLREP
NOINSP
DTCNTST
DTDENI
DTLAST
LOCAL
SPECPGM
MIGRANT
DUN
Index?
(V/N)
N
Y
N
N
N
Y
N
N
N
N
Y
Y
N
Y
N
Y
Y
Y
Y
Y
N
N
N
Y
N
Y
N
N
Y
N
N
N
N
N
N
N
N
N
N
Y
N
N
N
N
Y
N
Y
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Y
Enforc
Sens?
(Y/S/N)
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Data Length Description
Type
Num 9
Num 9
Char 1
Date 6
Char 7
Num 2
Char 1
Char 5
Char 30
Char 30
Char 2
Num 5
Num 3
Char 6
Num 4
Char 7
Date 6
Char 1
Char 1
Char 1
Num 4
Date 6
Char 1
Date 6
Char 1
Num 7
Num 5
Num 5
Char 9
Num 4
Num 4
Num 4
Num 4
Num 4
Num 4
Num 4
Num 4
Num 9
Char 1
Char 1
Num 9
Num 9
Char 1
Date 6
Num 9
Num 9
Num 5
Num" 5
Num 5
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Date 6
Date 6
Date 6
Char 10
Char 10
Char 1
Num 9
Activity Link For Establishment
Inspection Activity NR
History Flag
Date Last Modified (YYMMDD)
Reporting Office Id
Region
Job Title Of Compliance Officer
Compliance Officer Id
Establishment Name
Inspection Site Address
Inspection Site State
Inspection Site Zip Code
Inspection Site GSA County Code
State and County Code (SS/###)
Inspection Site GSA City Code
State and City Code (SS/####)
Date Of Opening Conf Or Attempted Insp (YYMMDD)
Safety Or Health Inspection
Inspection Type
Scope Of Inspection
Primary SIC For Establishment
Date Of Closing Conf Or Exit From Site (YYMMDD)
Case Closed?
Date Case Closed (YYMMDD)
Employees Represented By Union?
Total Number Of Employees Nationally
Number Of Employees At Inspection Site
Number Of Employees Affected By Inspection
Local Report Number
Hours Preparing For Inspection
Travel Tune
Hours On Site
Hours Employer Abatement Assistance
Hours Completing Case File
Hours Off-Site Conferences
Hours Preparing/Litigating Case
Hours Denial Activity
Total Hours All Inspection Activity
Advance Notice Given?
Establishment Ownership Type
Name/Address Link Assigned By EPA
Previous Activity NR (Discontinued)
Source Of Penalty Due Date
Date Penalties Due (YYMMDD)
Total Penalties Issued
Total Penalty Amount Remitted
Total Violations Cited
Total Serious Violations Cited
Lost Workday Injury Rate
State Flag
Manufacturing Safety Insp
Construction Safety Insp
Maritime Safety Insp
Manufacturing Health Insp
Construction Health Insp
Maritime Health Insp
Employee Enterviewed?
Employee Rep Present?
Reason For No Inspection
Date Insp Contest Received (YYMMDD)
Date Of Initial Denial Of Entry (YYMMDD)
Date Of Last Reentry After Entry Denied (YYMMDD)
Local Emphasis Program Insp
National Special Emphasis Program Insp
Migrant Farmworker Camp Insp
Dun & Bradstreet Number For Establishment
C-26 IDEA User's Guide
February 29, 1996
-------
Group Repeat Element
Record? Name
SICINSP
SICGUID
SIC
FEDAGCY
DTFTA
AMTFTA
AMTRFTA
WARRANT
REL ACTV(B) Y RELITEM(K)
RELTYPE
RELACT
RELSAFT
RELHLTH
OPTL INFO(B) Y OPTTYPE(K)
OPTID(K)
OPTVALU
DEBT(B) N DBTDTNX
DBTDTLA
DBTDTSL
DBTRSNR
DBTHOLD
PENWV
PENWRSN
PENDTCL
PENINT
PENDLQ
PENDTDC
PENDTRT
PENDCAR
PENDCHG
PENDFEE
PEN ARCH
PENDCIN
PENDCFE
PENDRVW
PENDRET
PENRVWR
PENDAOC
PENDCBS
PENDIRS
PENDCBR
FTAWV
FTAWRSN
FTADTCL
FTAINT
FTADLQ
FTADTDC
FTADTRT
FTADCAR
FTADCHG
FTADFEE
FTAARCH
FTADCIN
FTADCFE
FTADRVW
FTADRET
FTARVWR '
FTADAOC
FTADCBS
FTADIRS
FTADCBR
VIOLATIONS(B) Y VIOLKEY(K)
HSTDT(K)
HSTEVNT(K)
VDTISSU(l)
VIOLATN(l)
Index? Enforc Data Length Description
(Y/N) Sens? Type
(Y/S/N)
N
N
Y
Y
N
N
N
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Y
Y
Y
Y ,
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
. Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Num 4
Num 4
Num 4
Num 4
Date 6
Num 9
Num 9
Char 1
Char 2
Char 1
Num 9
Char 1
Char 1
Char 1
Char 2
Char 12
Date 6
Date 6
Date 6
Char 1
Char 1
Char 1
Char 1
Date 6
Num 7
Num 7
Date 6
Date 6
Char 1
Num 7
Num 7
Char 1
Num 7
Num 7
Date 6
Date 6
Char 1
Date 6
Date 6
Date 6
Date 6
Char 1
Char 1
Date 6
Num 7
Num 7
Date 6
Date 6
Char 1
Num 7
Num 7
Char 1
Num 7
Num 7
Date 6
Date 6
Char 1
Date 6
Date 6
Date 6
Date 6
Char 7
Date 6
Char 1
Date 6
Char 22
SIC Inspected
SIC Scheduled For Inspection
SIC Code (Primary, Inspected, or Scheduled)
Federal Agency Code
Date Failure-To-Abate Penalties Due (YYMMDD)
Total FTA Penalties Issued
Total FTA Penalty Amount Remitted
Anticipatory Warrant Served?
Related Activity Item Number
Related Activity Type
Related Activity Number
Fuirther Safety Insps Not Required
Further Health Insps Not Required
Optional Information Originator
Optional Information Id Code
Optional Information
Date Next Installment Due (YYMMDD)
Date Last Installment Due (YYMMDD)
Date Referred To Solicitor (YYMMDD)
Reason Referred To Solicitor
Case Held At National Office
Assessed Penalty Waived
Reaison Penalty Waived
Date Referred To Natl Offc For Coll (YYMMDD)
Interest Assessed By National Office
Delinquent Fees Assessed By National Office
Date Sent To Debt Collection Agency (YYMMDD)
Date Returned From Debt Coll Agcy (YYMMDD)
Reason Returned From Debt Collection Agency
Additional Litig Credit Report Charges
Debt Collection Agency Fees
Case Archived?
Interest Assessed By Debt Collection Agency
Delinquent Fees Assessed By Debt Collection Agency
Date Sent To Area Offc For Add! Rev (YYMMDD)
Date Return From Area Offc From Rev (YYMMDD)
Reason Sent To Area Office
Date St To Area Offc After Debt Coll (YYMMDD)
Date Sent To Credit Bureau (YYMMDD)
Date Sent To IRS (YYMMDD)
Date Recalled From Credit Bureau (YYMMDD)
Assessed Penalty Waived
Reason Penalty Waived
Date Referred To Natl Offc For Coll (YYMMDD)
Interest Assessed By National Office
Delinquent Fees Assessed By National Office
Date Sent To Debt Collection Agency (YYMMDD)
Date Returned From Debt Coll Agency (YYMMDD)
Reason Returned From Debt Collection Agency
Additional Litig Credit Report Charges
Debt. Collection Agency Fees
Case Archived?
Interest Assessed By Debt Collection Agency
Delinquent Fees Assessed By Debt Collection Agency
Date Sent To Area Offc For Addl Rev (YYMMDD)
Date Ret From Area Offc From Rev (YYMMDD)
. Reason Sent To Area Office
Date St To Area Offc After Debt Coll (YYMMDD)
Date Sent To Credit Bureau (YYMMDD)
Date Sent To IRS (YYMMDD)
Date Recalled From Credit Bureau (YYMMDD)
Violation Key
Event History Date (Penalty Or FTA) (YYMMDD)
Cause Of Activity Against Viol Record
Date Citation Issued (YYMMDD)
Std/Reg/Law Violated
Appendix C. Data Elements in IDEA Shadow Files
C-27
-------
Group
ACCIDENTS(B)
ADMIN(B)
PAYMENT(B)
Repeat Element
Record? Name
VINTTYP(l)
VCURTYP(l)
VCNT(l)
VDTABAT(l)
VCT<5f 1 >
VO 1 3^1^
VEXPOSD(l)
VINTPBN(l)
VCURPEN(l)
1 HSTVTYP(2)
HSTDTAB(2)
HSTPEN(2)
HSTACTP(2)
VGRAVE(l)
VREC(l)
VISA(l)
VDELETE(l)
VDTPNCN(l)
VIOLCN(l)
VPNCN(l)
VABTCNR(l)
VABTCNB(1)
VDTFINO(l)
VPMA(l)
VAMEND(l)
VDSPCN(l)
HAZSUBl(l)
HAZSUB2(1)
HAZSUB3(1)
HAZSUB4(1)
HAZSUBS(l)
HAZSUB
VDTFTA(l)
VFTACTN(l)
VFTA(l)
VFTAISA(l)
VDTFTCN(l)
VFTAMND(l)
VDSPFTA(l)
VEGREG(l)
HAZCAT(l)
HSTFTAN(2)
HSTFTA(2)
HSTACTF(2)
HS2FTAN(2)
HS2FTA(2)
HS2ACTF(2)
Y ACCITEM(K)
ACCNAME
ACCDGRE
ACCTASK
ACCNATR
ACCBODY
ACCSRC
ACCTYPE
ACCENV
ACCHUM
ACCVSEX
ACCVAGE
ACCOCCU
ACCSUB
Index?
(Y/N)
N
N
N
N
N
N
N
N
N
N
N
N
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Y
N
N
N
N
N
N
N
Y
N
N
N
N
N
N
N
N
N
Y
N
N
N
Y
Y
Y
Y
N
N
N
N
Y ADMTYPE(K) N
ADMDT(K) N
ADMAMT N
Y PAYTYPE(K)
PAYDT(K)
PAYPEN
N
N
N
Enforc
Sens?
(Y/S/N)
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Data Length Description
Type
Char 1
Ghar 1
Num 5
Date 6
Char 1
Num 5
Num 7
Num 7
Char 1
Date 6
Num 7
Char 1
Char 2
Char 1
Char 1
Char 1
Date 6
Char 1
Char 1
Char 1
Char 1
Date 6
Char 1
Char 1
Char 1
Char 4 '
Char 4
Char 4
Char 4
Char 4
Char 4
Date 6
Num 9
Num 7
Char 1
Date 6
Char 1
Char 1
Char 1
Char 10
Num 9
Num 7
Char 1
Num 9
Num 7
Char 1
Num 4
Char 20
Char 1
Char 1
Char 2
Char 2
Char 2
Char *2
Char 2
Char 2
Char, 1
Char 2
Char 3
Char 5
Char 1
Date 6
Num 7
Char 1
Date 6
Num 7
Initially Determined Violation Type
Currently Determined Violation Type
Number Of Instances Of Violation
Violation Abatement Date (YYMMDD)
Violation Status
Number Employees Exposed To Hazard
Initial Penalty
Current Penalty
Violation Type At Time Of Update
Abatement Date At Time Of Update (YYMMDD)
Penalty At Time Of Update
Update Action Against Penalty
Potential Harm To Workers
Related Event Code
Informal Settlement Agreement?
Violation Deleted
Earliest Contest Date (YYMMDD)
Violation Contested?
Penalty Contested?
Employer Contests Abatement?
Employee Contests Abatement?
Final Order Date (YYMMDD)
Petition To Modify Abatement Approved?
Citation Amended Prior To Contest?
Disposition Of Contested Violation
Hazardous Substance Related To Violation
Hazardous Substance Related To Violation
Hazardous Substance Related To Violation
Hazardous Substance Related To Violation
Hazardous Substance Related To Violation
Hazardous Substance (1, 2, 3, 4, or 5)
Date FTA Issued (YYMMDD)
Activity Number Of Insp FTA Assessed
FTA Penalty Assessed
Informal Settlement Agreement For FTA?
Date FTA Contested (YYMMDD)
FTA Amended Prior To Contest?
Disposition Of Contested FTA •
Egregious Case?
Unknown OSHA v6 field (Hazard Category?)
FTA History Inspection Number
FTA Penalty At Time Of Update
Update Action Against FTA Penalty
2nd FTA History Inspection Number
2nd FTA Penalty At Time Of Update
2nd Update Action Against FTA Penalty
Accident Item Number
Name Of Victim
Degree Of Injury
Assigned Task At Time Of Accident
Nature Of Injury
Part Of Body Injured
Source Of Injury
Accident Type
Environmental Factor Contributing To Accident
Human Factor Contributing To Accident
Sex Of Victim
Age Of Victim
Occupation Code Of Victim
Hazardous Substance Contributing To Accident
Administrative Data Type
Date Of Administrative Action (YYMMDD)
Administrative Assessment Applied
Payment Type
Date Payment Received (YYMMDD)
Amount Of Payment For Assessed Penalty
C-28 IDEA User's Guide
February 29, 1996
-------
Group Repeat Element
Record? Name
PAYFTA
PAY163
PAYORG
PAYBAL
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N)
N
N
N
N
Y
N
N
N
Num
Num
Char
Char
Length Description
7
9
1
1
Amount Of Payment For
Unknown OSHA v6 field
Unknown OSHA v6 field
Unknown OSHA v6 field
Assessed FTA Penalty
C.12 PCS-Permit Compliance System Data Elements
Group Repeat Element
Record? Name
NPID(A) N NPDES
PIPE(B) N DSCH
PERMIT FAC(A) N REGN
PTYP
IACC
PNAM
PNM2
NAM2
MADI
SIC2
CYNM
CNTN
INCL
TYPO
FTYP
EPST
CNTY
STCNTY
RNAM
RSTR
RCTY
RSTT
RZIP
BAS4
CITY
IADT
CFRC
FDGR
FLIM
FLAT
FLON
FLLC
FLOW
PRET
NPSC
NPFF
NPSQ
ARDT
LRNC
CYQS
CYQS1
CYQS2
CYQS3
CYQS4
PYQS
PYQS1
PYQS2
PYQS3
PYQS4
Index? Enforc Data Length Description
(Y/N) Sens? Type
(Y/S/N)
Y
Y
Y
Y
Y
N
N
N
Y
Y
N
N
Y
Y
Y
N
N
Y
N
N
N
N
Y
N
N
N
Y
Y
Y
N
N
N
Y
Y
Y
N
N
N
N
N
Y
Y
Y
Y
N
Y
Y
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N ,
N
N
N
Char 9
Char 3
Char 2
Char 1
Char 1
Char 8
Char 22
Char 30
Char 1
Num 4
Char 20
Char 20
Char 1
Char 3
Char 1
. Char 1
Num 4
Char 7
Char 30
Char 60
Char 23
Char 2
Num 5
Num 4
Num 9
Date 6
Char 5
Char 1
Char 1
Num 5
Num 5
Char 1
Char 5
Char 1
Char 1
Char 1
Char 1
Date 6
Char 1
Char 4
Char 1
Char 1
Char 1
Char 1
Char 4
Char 1
Char 1
Char 1
Char 1
NPDES Identification Number
Discharge Number From Pipe Schedule
Region
Permit Type
Activity Flag
Phonetic Facility Name (First 8 Characters)
PNM2
Facility Name - Part 2
Major/Minor Discharge Indicator
SIC Code 2
From City And State
County Name
Industrial Classification
Ownership Classification
Facility Type
EPA Or State Permit
County FIPS Code
State (from NPDES Id) And County Code (SS/#)
Name Of Facility
Street
City
State
Zip Code
River Basin Code
EPA City Code
Facility Inactive Date (YYYYMM)
CFR. Code (From SIC)
POTW With Federal Grant
Final Limits Indicator
Latitude •
Longitude •
Lat/Long Accuracy Code 1
Design Flow MGD •
Pretreatment Program Required •
NMP Final Schedule •
NMP Financial Status 1
NMP Schedule Quarter I
Archival Date (YYYYMM) •
Latest Reported Noncompliance 1
Current Year Noncompliance Status •
Current Year NC Status - 1st Quarter 1
Current Year NC Status - 2nd Quarter 1
Current Year NC Status - 3rd Quarter 1
Current Year NC Status - 4th Quarter I
Previous Year Noncompliance Status •
Previous Year NC Status - 1st Quarter 1
Previous Year NC Status - 2nd Quarter •
Previous Year NC Status - 3rd Quarter 1
Previous Year NC Status - 4th Quarter 1
Appendix C. Data Elements in IDEA Shadow Files
C-29
-------
Group
PRETRT PRF(A)
INSPECTNS(A)
PERM EVNT(A)
COMP SCHD(A)
ENF ACTNS(A)
Repeat Element
Record? Name
GYMS
CYMS1
CYMS2
CYMS3
CYMS4
PYMS
PYMS1
PYMS2
PYMS3
• PYMS4
CYNC1
CYNC2
CYNC3
CYNC4
PYNC1
PYNC2
PYNC3
PYNC4
VIOLQTR
INSPDAY
Y PSED(K)
SSNC
JUDI
FENF
IUPN
SVPU
Y DTIN(K)
TYPI(K)
SINS(K)
SIDT(K)
ICOM(2)
SlUSfl)
"*• *~e**\ *• /
CIUS(l)
NOCM(l)
PSNC(l)
NOIN(l)
MSNC(l)
SNIN(l)
PTIM(l)
ADLL(l)
EVLL(l)
Y PTEV(K)
PTAC
PTEVNT
Y VCSN(K)
VDCD(K)
CVEV(K)
CVIO(K)
CVDT(K)
SNCC
SNDC
SNCCDT
SRCC
SRDC
Y ENAC(K)
EATP(K)
ENDT(K)
ENST
ESDT
ENSTDT
ERDT
APCL
APFO
APAM
APPC
APPA
Index? Enforc
(Y/N)
N
Y
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
N
N
N
Y
Y
Y
N
N
N
N
N
N
N
N
N
N
Y
N
N
N
Y
N
N
N
N
N
N
N
Y
N
N
Y
Y
Y
N
N
Y
N
Y
Y
Y
Y
Y
Sens?
(Y/S/N)
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
S
S
S .
S
S
S
S
S
S
S
S
S
S
S
S
N
N
N
N
N
N
N
N
N
N
N
N
N
S
N
N
N
N
N
N
N
N
N
N
N
Data Length Description
Type
Char 4
Char 1
Char 1
Char 1
Char 1
Char 4
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Num 2
Num 5
Date 8
Num 4
Num 4
Num 4
Num. 4
Num 4
Date 8
Char 1
Char 1
Date 6
Char 100
Num 4
Num 4
Num 4
Char 3
Num 4
Num 4
Num 4
Date 6
Char 1
Char 1
Char 5
Date 6
Char 9
Char 2
Char 4
Char 5
Char 3
Date 6
Char 1
Date 6
Char 5
Char 1
Date 6
Char 2
Char 1
Date 8
Char 2
Date 6
Char 6
Date 6
Char 1
Date 6
Num 6
Date 6
Num 6
Current Year Noncompliance (Manual)
Current Year NC (Manual) - 1st Quarter
Current Year NC (Manual) - 2nd Quarter
Current Year NC (Manual) - 3rd Quarter
Current Year NC (Manual) - 4th Quarter
Previous Year Noncompliance (Manual)
Previous Year NC (Manual) - 1st Quarter
Previous Year NC (Manual) - 2nd Quarter
Previous Year NC (Manual) - 3rd Quarter
Previous Year NC (Manual) - 4th Quarter
Current Year Noncompliance Status, Ql
Current Year Noncompliance Status, Q2
Current Year Noncompliance Status, Q3
Current Year Noncompliance Status, Q4
Previous Year Noncompliance Status, Ql
Previous Year Noncompliance Status, Q2
Previous Year Noncompliance Status, Q3
Previous Year Noncompliance Status, Q4
# Quarters In Violation - Last 2 Years
# Days Since Last Inspection
End Date (YYYYMMDD)
# SIUS In SNC With Pretreatment Schedule
# Suits Filed Against SIUS
# NOVs And AOs Against SIUS
# Industrial Users Who Paid Penalty
# SIUS With Violation Published In Papers
Inspection Date (YYYYMMDD)
Inspection Type
Inspector Code
Scheduled Date (YYYYMM)
Comments
# Significant Industrial Users
# Categorial Industrial Users
# SIUS Without Control Mechanism
# SIUS In SNC With Pretreatment
# SIUS Not Inspected
# SIU In SNC With Self-monitoring
# SIUS In SNC With Self-monitoring/Not Inspected
Date Pretreatment Required (YYYYMM)
Adoption Of Technically-based Limits
Technical Evaluation For Local Limits
Event Code, req'd national events only
Event Actual Date (YYYYMM)
Permit Tracking Event & Actual Date
Compliance Schedule Number
Data Source Code
Event
Violation Code
Violation Date (YYYYMM)
Reportable Noncompliance For Event
Date Of Reportable Noncompliance (YYYYMM)
RNC For Event & Date Of RNC
Resolution Of Reportable Noncompliance
Resolution Date (YYYYMM)
Enforcement Action Code
Action Lead ('E' or 'S')
Action Date (YYYYMMDD)
Status Code
Status Date (YYYYMM)
Status Code & Date
Response Due Date (YYYYMM)
Administrative Penalty Class (1 or 2)
Date Final Order (YYYYMM)
Penalty Amount Assessed
Date Penalty Collected (YYYYMM)
Amount Assessed by Judicial Decision
C-30 IDEA User's Guide
February 29, 1996
-------
Group Repeat Element
Record? Name
APPD
APTC
EFFLUENTS(B) Y DRID(K)
PIPQ(K)
VLIM(K)
VPRM(K)
VMLO(K)
VSEA(K)
VMOD(K)
MVDT(K)
FLSD(l)
FLED(l)
MLSD(l)
MLED(l)
ILSD(l)
ILED(l)
STRP(l)
NRPU(l)
REUN(l)
PIAC(l)
PIDT(l)
STSU(l)
NSUN(l)
SUUN(l)
STSS(l)
NSUS(l)
SUUS(l)
NSUB(l)
LTYP(2)
LCMX(2)
LCAV(2)
LCMN(2)
LCUC(2)
LQMX(2)
LQAV(2)
LQUC(2)
LQAS(2)
LQXS(2)
LCMS(2)
LCAS(2)
LCXS(2)
LCMO(2)
LCAO(2)
LCSX(2)
LCSA(2)
LCSM(2)
LCSC(2)
LQSX(2)
LQSA(2)
LQSC(2)
ELSD(2)
ELED(2)
COLS(2)
CONP(2)
PLFN(2)
MVIO(3)
VIND(3)
ENFI(3)
NODI(3)
DMRL(3) .
MQAV(3)
MQMX(3)
MCMN(3)
MCAV(3)
MCMX(3)
VQAV(3)
Index? Enforc Data Length Description
(Y/N) Sens? Type
(Y/S/N)
Y
Y
N
N
N
Y
N
N
N
Y
N
N
N
N
N
N
N
N
N
N
N
'N
N
N'
N
N
N
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Y
Y
Y
N
N
N
N
N
N
N
N
N'
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N>
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Date 6
Num 6
Char 1
Char 1
Char 1
Char 5
Char 1
Char 1 .
Char 1
Date 8
Date 8
Date 8
Date 8
Date 8
Date 8
Date 8
Date 8
Num 3
Char 1
Char 1
Date 8
Date 8
Num 2
Char 1
Date 8
Num 2
Char 1
Date 8
Char 1
Char 8
Char 8
Char 8
Char 2
Char 8
Char 8
Char 2
Char 2
Char 2
Char 2
Char 2
Char 2
Char 1
Char 1
Num 8
Num 8
Num 8
Char 2
Num 8
Num 8
Char 2
Date 8
Date 8
Char 3
Char 1
Char 12
Char 3
Char 1
Char 1
Char 1
Char 1
Char 8
Char 8
Char 8
Char 8
Char 8
Num 5
Deadline for Penalty Payment (YYYYMM)
Total Penalty Collected
Report Designator
Pipe Set Qualifier
Limit Type/Number
Parameter Code
Monitoring Location
Seasonal Indicator
Modification Number
Monitoring Date (YYYYMMDD)
Final Limits Start Date (YYYYMMDD)
Final Limits End Date (YYYYMMDD)
Interim Limits Start Date (YYYYMMDD)
Interim Limits End Date (YYYYMMDD)
Initial Limits Start Date (YYYYMMDD)
Initial Limits End Date (YYYYMMDD)
Initial Report Date (YYYYMMDD)
Units In Reporting Period
Reporting Units
Pipe Inactive Code
Pipe Inactive Date (YYYYMMDD)
Initial DMR Date (YYYYMMDD) 1
# Units In Submission Period - EPA 1
Submission Units 1
Submission Date (YYYYMMDD) 1
# Units In Submission Period - State 1
State Submission Units 1
Next DMR Due Date (YYYYMMDD)
Limit Type/ Alpha
Concentration Maximum Limit
Concentration Average Limit
Concentration Minimum Limit
Concentration Unit Code
Quantity Maximum Limit
Quantity Average Limit
Quantity Unit Code
Quantity Average Limit Statistical Code
Quantity Maximum Limit Statistical Code
Concentration Minimum Limit Statistical Code
Concentration Average Limit Statistical Code
Concentration Maximum Limit Statistical Code
Concentration Minimum Limit Override
Concentration Average Limit Override
Concentration Maximum Limit Standard
Concentration Average Limit Standard
Concentration Minimum Limit Standard
Concentration Unit Code
Concentration Unit Code Standard
Quantity Limit Standard
Quantity Limit Code
Modification Period Start Date (YYYYMMDD)
Modification Period End Date (YYYYMMDD)
Change Of Limits Code
' Contested Parameters
Limit File (Docket) Number
Effluent Violation Code - Worst Violation
Violation Indicator
Enforcement Action Issued For DMR
Reason For No Discharge
DMR Received Late
Avera.ge Quantity
Maximum Quantity
Minimum Concentration
Concentration Average
Maximum Concentration
Percent Over Limit - Quantity Average
Appendix C. Data Elements in IDEA Shadow Files
C-31
-------
Group Repeat Element
Record? Name
VQMX(3)
VCMN(3)
VCAV(3)
VCMX(3)
VWCS(3)
SNDE(3)
SRDE(3)
SNCE(3)
SRCE(3)
Index? Enforc
(Y/N)
N
N
N
N
Y
Y
Y
Y
Y
Sens?
(Y/S/N)
N
N
N
N
N
N
N
N
N
Data
Type
Num
Num
Num
Num
Num
Date
Date
Char
Char
Length Description
5
5
5
5
5
8
8
1
1
Percent Over Limit - Quantity Maximum
Percent Under Limit - Concentration Minimum
Percent Over Limit - Concentration Average
Percent Over Limit - Concentration Maximum
Highest Percent Violation
RNC Date For DMR (YYYYMMDD)
RNC Resolution Date (YYYYMMDD)
RNC Detected
RNC Resolved
C.13 RCR-RCRA Information System Data Elements (7195)
Group Repeat Element
Record? Name
IDNUM(B) N ID
HANDLER(B) N NAME
CDE
LOCST1
LOCST2
LCITY
LSTATE
LZIP
HREGN
HUSJCEI
HUSJCA
HUCAWR
HUPMTPR
HUPMTWR
HUPCLWR
HUPPCWR
HUTRAN
HUFUL
HULAND
HUINCIN
HUSTORT
HUSML
HUCESQG
XREFID
COREID
NOTIF
HEXDATE
HOFFSIT
MAILST1
MAILST2
MCITY
MSTATE
MZIP
LANDTYP
LATD
LONG
LLSRC
HACCESS
HGER
HTRR
HDGW
HDCL
HDFR
HGLB
Index? Enforc Data Length Description
(Y/N) Sens? Type
nr/s/N)
Y
N
Y
N
N
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
»• N
N
N
N
N
N
Y
N
N
N
N
N
N
Y
Y
Y
Y
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Char 12
Char 40
Char 5
Char 30
Char 30
Char 25
Char 2
Num 5
Char 2
Char 4
Char 4
Char 4
Char 4
Char 4
Char 4
Char 4
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 1
Char 12
Char 1
Char 1
Date 8
Char 1
Char 30
Char 30
Char 25
Char 2
Num 5
Char 1
Num 5
Num 5
Char 1
Char 1
Char 1 .
Char 1
Char 1
Char 1
Char 1
Char 1
Handler Id Number (Minor Value)
Handler Name
State Code/County Code
Location Street 1
Location Street 2
Location City
Location State
Location Zip Code
Region Code
TSD Subject to CEI Universe
TSD Subject to CA Universe
CA Workload Universe
Permit/Closure/Post-closure/Progress Universe
Permit Workload Universe
Closure Workload Universe
Post-closure Workload Universe
Transporter Universe
Fully Regulated Universe
Land Disposal Universe '
Incinerator Universe '
Storage/Treatment Universe
Small Generator Universe
Conditionally Exempt Quantity Generator
(Cross Reference To Hist)
Send To Merge DB Flag
Non-Notifier Code
Existence Date (YYYYMMDD)
Off Site Waste Receipt
Official Mail Street 1
Official Mail Street 2
Official Mail City
Official Mail State
Official Mail Zip Code
Land Type
Latitude
Longitude
Longitude/Latitude Source
Bankruptcy Indicator
Generator Requirements Violation Flag
Transporter Requirements Violation Flag
Groundwater Requirements Violation Flag
Closure/Post-Clos. Requirements Violation Flag
Financial Requirements Violation Flag
Generator Landban Regulations Violation Flag
C-32 IDEA User's Guide
February 29, 1996
-------
Group Repeat Element
Record? Name
HDLB
HCAS
HDOT
HENF
CPVIOL
VIOLQTR
INSPDAY
CONTACT(B) Y CONTTYP(K)
CLAST
CFIRST
CTITLE
CPHONE
CSTRT1
CSTRT2
CCITY
CSTATE
CZIP
CADD
OWNER(B) Y HCOSEQ(K)
COIND
COTYPE
HCDATE
CONAME
COPHONE
COSTRT
COCITY
COSTATE
ZIPCODE
SIC(B) Y SICSEQ(K)
SICPRIM
SICCODE
SICSRCE
SOURCE(B) Y SOURCE(K)
RECDATE(K)
WASTSTR(K)
WASTCD(K)
WASTPRO(K)
PROCESS(K)
PROCSEQ(K)
PROCATT(K)
PROCUID(K)
GEN(l)
TRANS(l)
TSD(l)
BBL(l)
HWF1(1)
HWF2(1)
HWF3(1)
OU01(1)
OU02(1)
OUO3(1)
SUO(l)
UTILl(l)
UTIL2(1)
UTIL3(1)
AIR(l)
RAIL(l)
HIGHWAY(l)
WATER(l)
OTHER(l)
RCRADGE(l)
RCRADTR(l)
RCRADTS(l)
RCRADBB(l)
RCRASGE(l)
Index? Enforc Data
(Y/N) Sens? Type
(Y/S/N)
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
Y
N
N
N
N
N
N
N
N
N
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N -
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Char
Char
Char
Char
Char
Num
Num
Char
Char
Char
Char
Char
Char
Char
Char
Char
Num
Char
Num
Char
Char
Date
Char
Char
Char
Char
Char
Num
Num
Char
Num
Char
Char
Date
Num
Char
Char
Char
Num
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Char
Length Description
1
1
1
1
1
2
5
1
15
15
15
10
30
30
25
2
5
1
4
2
2
8
40
10
30
25
2
5
4
1
4
1
1
9
4
4
3
3
2
2
10
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
20
2
2
2
2
1
Treatment, Storage or Disposal (TSD) Landban Regulations Vio-
lation Flag
Corrective Action Compliance Flag
Other TSD Regulations Violation Flag
Formal Enforcement Agreement Violation
Significant Violation Flag
# Qtrs In Violation - Last 2 Yrs (0-8)
Days Since Last Inspection
Contact Type
Contact Last Name
Contact First Name
Contact Title
Contact Phone
Contact Street Line 1
Contact Street Line 2
Contact City
Contact State
Contact Zip Code
Contact Address Code
Owner/Operator Sequence Number
Owner/Operator Indicator
Type Of Ownership
Flag
Owner/Operator Change Date (YYYYMMDD)
Owner /Operator Name
Owner/Operator Phone
Owner/Operator Street
Owner/Operator City
Owner /Operator State
Owner/Operator Zip Code
SIC Code Sequence Number
SIC Code Primary Indicator
SIC Code
SIC Code Source
Source Of Information
Receipt Date
Waste Stream Number
Waste Code
Waste Process
Process Code
Process Sequence Number
Process Amount Type
Process Unit Identifier
Generator
Transporter
Treater/Storer/Disposer
Burner/Blender
Market To Burner Indicator
Other Marketer Indicator
Burner Indicator
Market To Burner
Other Marketer
Burner
Specification Used Oil Fuel Marketer
Utility Boiler Indicator
Industrial Boiler Indicator
Industrial Furnace Indicator
Air Transportation
Rail Transportation
Highway Transportation
Water Transportation
Other Means Of Transportation
Generator RCRA Regulatory Status Description
Transporter RCRA Regulatory Status Desc.
TSD RCRA Regulatory Status Desc.
Burner/Blender RCRA Regulatory Status Desc.
Generator RCRA Regulatory Status
Appendix C. Data Elements in IDEA Shadow Files
C-33
-------
Group
INSTRUMT(B)
BNFORCMT(B)
EVALUATN(B)
VIOLATN(B)
ORPHN(B)
Repeat Element Index?
Record? Name (Y/N)
RCRASTR(l) N
RCRASTS(l) N
RCRASBB(l) N
UIC(l) N
WAMOUNT(2) N
WAMTT(2) Y
WUOM(2) N
WDATE(2) N
PROCCOM(S) N
PROCSTA(6) N
PROCUOM(6) N
PROCAMT(6) N
PROCTU(6) N
PDATE(6) N
PROCUTP(7) N
PROCUCT(7) N
PROCUAT(7) N
PROCUUM(7) N
PROCREG(7) N
Y INST(K) Y
IAGCY(K) Y
IEDATE(K) Y
ISTAT(K) Y
CAREA(K) Y
IEMOD(K) Y
IECODE(K) Y
IEAGCY(K) Y
ISEQ(K) N
IDATE(l) N
IRDATE(1) N
IPROG(l) N
ADESC(3) N
IEADATE(4) N
IEPROG(4) N
IEVSTAT(4) N
Y CEENUM(K) Y
ENFAGN(K) Y
EDATE(K) Y
EAMTTYP(K) Y
MMCODE(K) Y
SEPSEQ(K) N
ENFTYPE(l) Y
POLLPRE(2) Y
EPENAMT(4) Y
Y EVALNO(K) Y
EVALAGN(K) Y
EVALDTE(K) Y
EVALSEQ(K) Y
ETYPE(l) Y
EVAREA(2) Y
CESTAT(2) N
CEMDESC(2) N
Y )CEVVKEY(K) Y
)EKEY(K) Y
VENFKEY(K) Y
EKBYSEQ(K) N
VAREA(l) Y
VDTEDET(l) Y
VCLASS(l) Y
VACTDTE(l) Y
VPRTY(l) Y
VSCHDTE(1) N
Y EMOD(K) Y
ECODE(K) Y
EAGCY(K) Y
Enforc
Sens?
(Y/S/N)
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
S
N
N
N
Data Length Description
Type
Char 1
Char 1
Char 1
Char 1
Num 8
Num 8
Char 1
Date 8
Char 1
Char 1
Char 1
Num 8
Num 9
Date 8
Char 1
Num 9
Num 8
Char 1
Char 1
Char 1
Char 1
Date 8
Char 1
Num 4
Char 1
Char 5
Char 1
Num 4
Date 8
Date 8
Char 1
Char 40
Date 8
Char 1
Char 2
Char 9
Char 1
Date 8
Char 2
Char 3
Char 2
Char 3
Char 3
Num 8
Char 9
Char 1
Num 9
Num 4
Char 3
Char 3
Char 2
Char 40
Char 5
Char 10
Char 10
Num 4
Char 3
Date 8
Char 1
Date 8
Char 1
Date 8
Char 1
Char 5
Char 1
^flk
•
Transporter RCRA Regulatory Status ^^
TSD RCRA Regulatory Status
Burner/Blender RCRA Regulatory Status
Underground Injection Control Indicator
Amount Of Waste
Waste Amount In Tons
Unit Of Measure
Waste Date (YYYYMMDD)
Process Commercial Indicator
Process Status
Process Unit Of Measure
Process Amount
Process Total Number of Units
Process Date (YYYYMMDD)
Process Unit Group Type
Number of Units in Process Unit Group
Total Waste Capacity Associated With Unit Group
Process Unit Group Unit Of Measure
Unit Regulatory Status (RCRA/State/Both)
Type Of Instrument
Responsible Agency (EPA/State/Joint)
Instrument Effective Date (YYYYMMDD)
Legal Authority Code
Area Code
Event Module
Event Code
Responsible Agency
Sequence Number
Instrument Issue Date (YYYYMMDD)
Instrument Revocation Date (YYYYMMDD) __
Responsible Program (RCRA/CERCLA) ^fl^
Area Description ^H0
Actual Date (YYYYMMDD) ^^
Responsible Program (RCRA/CERCLA)
Event Status
Enforcement Control Number
Responsible Agency (EPA/State/EPA Oversight)
Enforcement Action Date (YYYYMMDD)
Penalty Type Code
Multimedia Action Code
SEP (Supplemental Environmental Project/Enforcement Action
Sequence Number
Enforcement Action Type
SEP/Enforcement Milestone Code
Penalty Assessed
Evaluation Number
Responsible Agency
Evaluation Date
Evaluation Sequence; generated
Evaluation Type
Area Of Evaluation
Evaluation Status
Description
Violation Control Number
Related Evaluation Key
Enforcement Action
Sequence Number
Area Of Violation
Date Violation Determined (YYYYMMDD)
Class Of Violation
Actual Resolved Date (YYYYMMDD)
Priority Indicator ^_
Scheduled Resolved Date (YYYYMMDD) ^H
Event Module ^P
Event Code
Responsible Agency
C-34 IDEA User's Guide
February 29, 1996
-------
Group Repeat Element
Record? Name
ESEQ(K)
BADATE
EPROG
EVSTAT
PRMT SEQ(B) Y PSQN(K)
PECODE(K)
PEAGY(K)
PESEQ(K)
UNITSEQ(K)
UNITNAM(K)
PUSEQ(K)
PAPP(l)
PADATE(2)
PESTAT(2)
PSTAT
PUPROC(3)
PUPROCU(3)
PUDATE(3)
PCAP(3)
PUTOT(3)
COMMERCES)
OPSTAT(3)
LEGSTAT(3)
COMMITMT(B) Y CTYPE(K)
CFY(K)
EVCODE(K)
CID(K)
CHIDNUM(K)
CKEY(K)
CUPDT(l)
CAGCY(2)
CEFFDT(2)
CACTDT(2)
REVNO(2)
CDESC(2)
CTOTQ1(2)
CTOTQ2(2)
CTOTQ3(2)
CTOTQ4(2)
CTOTFY(2)
Index? Enforc Data Length Description
(Y/N) Sens? Type
O7S/N)
N
N
N
N
Y
Y
Y
N
N
Y
N
N
N
Y
Y
Y
Y
N
N
N
N
Y
Y
Y
Y
Y
Y
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N •
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Num 4
Date 8
Char 1
Char 2
Num 4
Char 5
Char 1
Num 4
Num 4
Char 18
Num 3
Char 12
Date 8
Char 2
Char 7
Char 3
Char 1
Date 8
Num 8
Num 9
Char 1
Char 2
Char 2
Char 3
Char 4
Char 5
Char 12
Char 12
Char 10
Date 8
Char 3
Date 8
Date 8
Num 4
Char 40
Num 4
Num 4
Num 4
Num 4
Num 4
Event Sequence Number
Actual Date (YYYYMMDD)
Responsible Program (RCRA/CERCLA)
Eveint Status
Permit Sequence Number
Activity Track/Event Code
Event Responsible Agency
Event Sequence Number
Process Unit Group Sequence
Process Unit Group Name
System-generated; used to distinguish multiple process detail record
for the same process unit group
Permit Processing Number
Actual Date Of Event (YYYYMMDD)
Event Status Code
Event Code and Event Status Code
Unit group's current TSD process
Unit of Measure of the associated design capacity
Date when process detail data record became effective
Process Design Capacity
Number Of Units Within Unit Group
Whether facility accepts haz. waste from third party
Operating Status of the process unit group
Legal Status of the process unit group
Commitment Type
Fiscal Year
Module/Event
Commitment Identifier
Handler Identifier
Commitment Link Key
Commitment Last Update (YYYYMMDD)
Responsible Agency
Commitment Effective Date (YYYYMMDD)
Commitment Acual Date (YYYYMMDD)
Revision Number
Commitment Description
Commitment Total 1st Quarter
Commitment Total 2nd Quarter
Commitment Total 3rd Quarter
Commitment Total 4th Quarter
Commitment Total Fiscal Year
Group
Repeat Element
Record? Name
Index? Enforc Data
(Y/N) Sens? Type
Length Description
(Y/S/N)
SITE(A) ~~~
PRP(B)
SITE(A)
N SITEID
N PRPCODE
N SITENM
ALIASNM
NPLFLAG
STREET
CITY
STATE
ZIP
EPAREG
LATD
LONG
Y
Y
N
N
Y
N
N
Y
Y
Y
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Char
Char
Char
Char
Char
Char
Char
Char
Num
Char
Num
Num
12
6
40
50
1
30
25
2
5
2
4
4
Site Id Number
Potentially Responsible Party Code
Site Name
Alias Name
National Priorities List (NPL)
Site Street
Site City
Site State
Site Zip
EPA Region
Latitude
Longitude
Flag
Appendix C. Data Elements in IDEA Shadow Files
C-35
-------
I
Group
PRP(B)
* •** \"/
ADDRESS(B)
,
Repeat Element
Record? Name
N PRPREGN
PRPNAME
Y ADDRSEQ(K)
ADDRSEE
TITLE
STREET1
STREET2
STREETS
ADCITY
ADSTATE
ADZIP
GNLDATE
SNLDATE
Index?
(Y/N)
Y
N
N
N
N
N
N
N
N
Y
Y
Y
Y
Enforc
Sens?
(Y/S/N)
N
N
N
N
N
N
N
N
N
N
N
N
N
Data Length Description
Type
Char 5
Char 50
Num 4
Char 50
Char 50
Char 50
Char 50
Char 50
Char 25
Char 2
Char 5
Date 8
Date 8
PRP Region
PRP Name
Addressee Sequence
Addressee Name
Addressee Title
Streetl
Street2
Streets
City
State
Zip Code
Number
General Notice Letter Date (YYYYMMDD)
Special Notice Letter Date (YYYYMMDD)
C.15 TRI-Toxic Chemical Release System Data Elements (7195)
Group
TFID(A)
DCNO(B)
FACL(A)
HFAC
-------
Group Repeat Element
Record? Name
PCTC
PCTN
TREST
RMRLSQN
RMRLSNA
RCYCACT
RCYCANA
PPADATA
ENRGYON
ENRGYCD
RCYCLON
RCYCLCD
REL REDUC(B) Y SRDRCYC(K)
CYRQ
CYRNA
PYRQ
PYRNA
FYRQ
FYRNA
SYRQ
SYRNA
RELEASE(B) Y RSEQ(K)
OREL
TEPA
GDIS
CBFI
TRNG
REST
RENA
REBC
PWTA
SPNA
STCD
LDCD
TRMT
RTRS
MREST
TREATMNT(B) Y TSEQ(K)
METHODS
METH
WECD
RICT
SETR
TREE
TREN
OPID
TRST
Index? Enforc Data Length Description
(Y/N) Sens? Type
(Y/S/N)
Y
N
Y
N
N
N
N
N
N
Y
N
Y
Y
N
N
N
N
N
N
N
N
Y
Y
N
N
N
Y
Y
N
N
N
N
N
N
Y
N
Y
N
N
Y
N
N
N
Y
N
N
N
N
N
N
N
N
N
N
N •
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Nuiil 5
Char 1
Num 11
Num 13
Char 1
Num 6
Char 1
Char 1
Char 15
Char 3
Char 15
Char 3
Char 25
Num 13
Char 1
Num 13
Char 1
Num 13
Char 1
Num 13
Char 1
Num 4
Char 1
Char 12
Char 2
Char 2
Char 2
Num 11
Char 1
Char 2
Num 5
Char 1
Char 1
Char 3
Char 3
Char 1
Num 11
Num 3
Char 31
Char 3
Char 2
Char 2
Char 2
Num 5
Char 1
Char 2
Char 1
Waste Min Percent Change
Waste Min Percent Change NA
Total Release Estimate
Remedial Release Quantity
Remedial Release Zero NA
Recycling Activity Index
Recycling Activity Index Zero NA
Additional PPA Data Indicator
Energy Onsite Process Code
Energy Onsite Process Code (for Retrieval)
Recycled Onsite Process Code
Recycled Onsite Process Code (for Retrieval)
Source Release Reduction Activities
Current Year Quantity
Current Year Zero NA
Previous Year Quantity
Previous Year Zero NA
Following Year Quantity
Following Year NA
Second Year Quantity
Second Year NA
Sequence Number
Release Medium
Transfer EPA Id Number
Transfer Site Code
Conlxolled By Facility Indicator
Release Emissions Range Code
Release Estimate
Release Estimate NA
Release Estimate Basis Code
Storm Water Percent
Storm Water Percent NA
Stream Code
Land Disposal Code
Type Of Treatment
Release Transfer Record Status
Release Estimate By Release Medium
Sequence Number
Waste Treatment Method
Waste Treatment Method (for Retrieval)
Wastestream Code
Waste Influent Concentration Code
Waste Sequence Treatment Indicator
Waste Treatment Efficiency Estimate
Waste Treatment Efficiency Estimate Na
Operating Data Indicator
Treatment Record Status
C.16 ZIP-Census Bureaus Zin Code Data Elements (1196)
Group
Repeat Element
Record? Name
Index? Enforc
(Y/N) Sens?
(Y/S/N)
Data
Type
Length Description
MINOR(B)
ZIPCODE(B)
N
N
ZIP
AREA
LAT
LONG
TYPE1
TYPE2
Y
Y
Y
Y
Y
Y
N
N
N
N
N
N
Num
Real
Real
Real
Char
Char
5
7
7
7
1
1
5 Digit Zip Code
Area in Square Miles
Latitude in Degrees
Longitude in Degrees
Type 1,2,3
Type ,1,3,5
of Zip Code
I
Appendix C. Data Elements in IDEA Shadow Files
C-37
-------
Group Repeat Element
Record? Name
STCN1
STCN2
STCN3
NAME(B) Y NSEQ
NAME
DEMOGRPH(B) N POP
MED MALE
WHITEF
BLACKF
INDIANF
ASIANF
OTHERF
HISPTOT
WHISPF
BHISPF
OHISPF
HHIBASE
HHILT15
HHI1524
HHI2534
HHI3549
HHI5074
HHIMT75
HHIMED
HHIAVE
FIBASE
FILT15
FI1524
FI2534
FI3549
FI5074
FIGT75
FIMED
FIAVE
PCI90
URBPOPF
RULPOPF
NATBRNF
FRNBRNF
EMPLOYD
UNEMPLF
HISPF
WHITF
MINTF
Index? Enforc
(Y/N)
Y
Y
Y
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Sens?
(Y/S/N)
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Data Length Description
Type
Num 5
Num 5
Num 5
Num 2
Char 25
Num 7
Num 3
Real 4
Real 4
Real 4
Real -, 4
Real 4
Num 7
Real 4
Real 4
Real 4
Num 7
Real 4
Real 4
Real 4
Real 4
Real 4
Real 4
Num 7
Num 7
Num 7
Real 4
Real 4
Real 4
Real 4
Real 4
Real 4
Num 7
Num 7
Num 7
Real 4
Real 4
Real 4
Real 4
Num 7
Real 4
Real 4
Real 4
Real 4
,4B
-m
State/County #1 ^*
State/County #2
State/County #3
Sequence Number for Names
Zip Name
Total Population
Median Age/Male
Fraction, Race = White
Fraction, Race = Black
Fraction, Race = American Indian
Fraction, Race = Asian
Fraction, Race = Other
Total population of Hispanic Origin
Fraction, White, of Hispanic Origin
Fraction, Black, of Hispanic Origin
Fraction, Other, of Hispanic Origin
Household Income Base
Fraction, Households with Income Less Than $15K
Fraction, Households with Income between $15K and $24,999
Fraction, Households with Income between $25K and $34,999
Fraction, Households with Income between $35K and $49,999
Fraction, Households with Income between $50K and $74,999
Fraction, Households with Income more than $75K
Median Household Income
Average Household Income
Family Income Base
Fraction, Families with Income Less Than $15K
Fraction, Families with Income between $15K and $24,999
Fraction, Families with Income between $25K and $34,999
Fraction, Families with Income between $35K and $49,999
Fraction, Families with Income between $50K and $74,999^jj
Fraction, Families with Income more than $75K ^H
Median Family Income ^*
Average Family Income
1990 Per-Capita Income
Fraction, Vrban Population
Fraction, Rural Population
Fraction, Native Born
Fraction, Foreign Born
Total Employed
Fraction, Unemployed
Fraction, Hispanic
Fraction, White, Non-Hispanic
Fraction, Minority
C-38 IDEA User's Guide
February 29, 1996
-------
A Appendix D. Error Messages forjhe Keyword Interface
This Appendix lists the possible error messages for a query submitted in the Keyword
Interface, gives some detail about how the error may have occurred, and suggests one
or more ways to correct each error. '
When IDEA processes a query, the system will identify errors that will prevent it
from running. If an error is present, one of the error messages included in this
appendix will appear on the screen.
Each error message will appear on the line after the one containing an error. Actual
error messages will replace the "XXX" characters listed here with the word(s) that
constitute the error.
Remember that IDEA looks for required keywords in a certain order and that some
keywords require criteria, names, or numbers in specific formats or values. For
example, even if the keyword you have used is valid, it may be out of order where it
appears in your query. (For example, if SELECT is the first keyword in a query, it
will be flagged as an error, since INPUT must appear before SELECT.) If the source
of an error cannot be determined, call IDEA User Support for assistance:
IDEA User Support Line: (202) 260-4250
Monday-Friday 9:00am to 5:30pm (eastern time)
INPUTj OUTPUT SPECIFICATIONS:
Queries cannot have more than one INPUT statement. The valid input values are
LINKED, NONLINKED, LINKED NONLINKED. To correct this error, eliminate
all but one instance of the keyword "INPUT."
The keyword OUTPUT may be used only once in a query even though multiple
reports, destinations, etc., may be specified. To correct this error, eliminate (or
combine) all but one instance of the keyword "OUTPUT."
Appendix D. Error Messages for the Keyword Interface '
D-1
-------
ERRORt
'
;> -
Security level is specified by entering SL followed by a number from 1 to 4. This line
must be before the INPUT line. If no security level is specified, IDEA will run the
query at the highest security level to which you have access.
After the required keyword SELECT, the system looks for database elements and
values. These must be present to have a valid query. To correct this error, enter
selection criteria after the keyword SELECT.
Call IDEA User Support (see below).
SECURITY SPECIFICA TIONS:
Refer to Appendix A, Access and Security Procedures for IDEA, for information on
security and access procedures.
Currently, IDEA supports four security levels: 1 through 4. One being the lowest
level of security access and four being the highest.
INPUT SPECIFICA TIONS:
; V:
Refer to Chapter 8 for information on INPUT statements.
D-2 IDEA User's Guide
February 29, 1996
-------
Refer to Chapter 8 for information on INPUT statements.
The keyword SELECT may only appear once in a query; although, you may specify
multiple criteria following SELECT. To correct this error, remove all but one
instance of "SELECT."
IDEA will only recognize three keywords after the keyword INPUT: LINKED,
NONLINKED, SELECT. Any other word will result in this message. To correct
this error, put the required keyword(s) after INPUT. If necessary, move other
keywords to the OUTPUT part of the query.
This message will appear if no database elements or values appear after the keyword
SELECT. Enter database elements and values after SELECT to correct this error.
If the last word in your SELECT criteria is a Boolean connector (AND/OR), IDEA
assumes there will be another expression in the query. To correct this error, remove
the Boolean connector or add another expression. (Recall that a comma is inter-
preted as the "OR" connector.)
Each opening parenthesis must have a corresponding closing parenthesis, and visa-
versa.
Appendix D. Error Messages for the Keyword Interface
D-3
-------
Contact IDEA User Support (see below).
VALUE SPECIFICATIONS:
No apostrophes should appear in a value list after a data element expression;
however, occasionally an apostrophe will be part of a valid value. To correct this
error, remove any invalid apostrophes.
'ERROR*
' - :"' -"'"' T'l'i" j,"' iK^f Rl^SJWiyi
. , THERE'is:?iNKir"--'~"
.'- .•LjSTJ'.'"'i^.;^i
1 ,vpi.i, v
. . ..,f=«,
^-^'.1-A!!..;.
To correct this error, compare the indicated value list with the list of valid values for
the data element and change or remove the invalid character.
To correct this error, compare the indicated value list with the list of valid values for
the data element and change the list accordingly.
The required order for database expressions and values is database abbreviation,
period, data element, equal sign, data value, comma, data value. Commas and values
are repeated until the last value in the list. This message tells you that your query
has a comma, but no value before it. This may indicate that an extra comma is
present. To correct this error, add a value in front of the comma or remove it.
,.,'' • '•." '"•" ""S/^'ik'sA'i'hi^sCK^'
<->••
" '/" ^/PftRQ^E^S^^^^iiai^llCPiS
',,,„,,.'. .'. ,'.h,,.fj,;.,. Vi >,, i».'.Hy!-y^.'.!jlSi: S ^
D-4
IDEA User's Guide
February 29, 1996
-------
Parentheses in IDEA keyword queries cannot stand alone. Refer to to Chapter 8
Chapter 8 for proper syntax.
Refer to Chapter 8 for proper connector syntax.
To correct this error limit the number of characters or contact IDEA User Support
(see below).
?,,.s!!i.,,''y!,a;,
Refer to Appendix B or contact IDEA User Support (see below).
Limit the number of characters or call IDEA User Support (see below).
Appendix D. Error Messages for the Keyword Interface
D-5
-------
Refer to Appendix B for valid data values or contact IDEA User Support (see
below).
Refer to Appendix B for valid date formats.
*- i ,, • fi & t (sfy«E| r *'«« ?' "gHs P«l 111 si £= ?; «<
The required order for database expressions and values is database abbreviation,
period, data element, equal sign, data value, comma, data value. Commas and values
are repeated until the last value in the list. This message tells you that you need to
insert a comma between two of your values or as separators between all values in the
list.
OUTPUT SPECIFICA TIONS:
The only two keywords that can follow OUTPUT are REPORT (report specification)
or JOB. Any other word will result in an error. To correct this error, put either
REPORT or JOB after OUTPUT. It may be necessary to move other keywords to
the INPUT statement or to positions after REPORT or JOB.
This message indicates the presence of an invalid keyword or a misordering of
keywords. If, for example, a query begins with SELECT, this message will appear
since INPUT must appear before SELECT. This message can also appear if a
comma if omitted in the middle of a value list, or if a Boolean operator is omitted
between two Boolean expressions, in the SELECT criteria.
D-6
IDEA User's Guide
February 29, 1996
-------
After the keyword REPORT, one of the valid report ID's must be entered, or a User
Specified Report must be requested. Currently there are five standard report ID's:
1A, IB, 2, SUMMARY, and FINDUMP. For information on the syntax of a User
Specified Report, see Chapter 11
Refer to Chapter 8 for proper destination specifications.
DATABASE ID:
This message indicates that an invalid database ID is present. Chapter 8 lists the
current database ID's.
Contact IDEA User Support (see below).
Contact IDEA User Support (see below).
DA TABASE.ELEMENT:
This error message indicates that an incorrect format is present. Refer to Chapter 8
for the correct format.
Appendix D. Error Messages for the Keyword Interface
D-7
-------
ELEMENT NAME:
^A&ii
Refer to Chapter 8 for proper data element syntax and Appendix C for data elements
used by IDEA.
Currently, only indexed data elements can be used in SELECT criteria. This message
indicates that the specified element is not indexed and therefore cannot be used.
Contact IDEA User Support fsee
In System 2000 databases, the only types of elements that can be used for retrievals
are items and functions (as opposed to records, for example). To correct this error,
you must remove the specified element from the SELECT criteria.
Check the list of elements and match them to the database you have specified, then
make the appropriate correction.
In System 2000 databases, elements are in a "tree" structure, and you may not use
elements for SELECT criteria that are higher in the tree than facilities. Remove the
specified element from the query to correct this error.
D-8 IDEA User's Guide
February 29, 1996
-------
OPERATORS (EQ, NE, LT, ETC):
Refer to Chapter 8 for a list of valid Boolean operators and the proper syntax associ-
ated with each.
EXPRESSION CONNECTORS (ANDfOR):
Refer to Chapter 8 for a list of valid Boolean connectors and the proper syntax asso-
ciated with each.
DESTINA TION KEYWORD:
Refer to Chapter 8 or contact IDEA User Support (see below).
BIN/BOX KEYWORD:
ySHHsV^W1'-'<<'•ySf^v^fsSf',!; , fsj& •"Sft '-''Si'''!•'!" 'W'^^HfeS-'I^S^'^
iitWy Mfefelr''dcyrW^,,vy'gd^/ff-jnilV,'."A.-. ''iH ':"l*gj
-jV,
Refer to Chapter 8 for proper syntax or contact IDEA User Support (see below).
JCL OVERRIDE:
Appendix D. Error Messages for the Keyword Interface
D-9
-------
This error message will appear if you try to save to a DATASET that was specified as
NEW but already exists. You must either change the name of the dataset to make it
unique or change the status to OLD by adding OLD after the dataset name.
This is the error message you will see if you write DATASET and specify either SHR
or OLD, but the dataset does not already exist. You must either change the specifi-
cation to NEW or correct the dataset name to one that already exists.
Refer to Chapter 8 for proper syntax.
ERROR,
If you use the keyword JOB in a query, you must write a complete, valid Job Card
after it. To correct this error, either remove the keyword JOB or write a Job Card
after the query.
dd KEYWORD:
If you write the keyword dd after either PRINT or DATASET, you must include
complete Job Control Language (JCL) after the query. To correct the error, either
remove dd form the query (dd is not a required keyword; defaults will be provided by
the system) or include a complete JCL statement after the query.
If you write the keyword dd after either PRINT or DATASET, you must write a
ddname after dd. You will use this same ddname in your Job Control Language
(JCL). To correct the error, include the same ddname after dd and in the JCL~or
remove dd from the query and accept the system- supplied defaults.
D-10 IDEA User's Guide
February 29, 1996
-------
If you use the keyword DATASET, you must write a dataset name or dd after the
keyword. If you write a dataset name (up to eight alphanumeric characters), IDEA
will create a dataset for you. If you specify dd, you must also write a dd statement
after the end of your query. :
IDEA User Support Line: (202) 260-4250
Monday-Friday 9:00am to 5:30pm (eastern time)
Appendix D. Error Messages for the Keyword Interface
D-11
-------
D-12 IDEA User's Guide
February 29, 1996
-------
Appendix E. The Structure of the IDEA Shadow Databases
E.I Skeletons of the IDEA Databases
The data accessed by IDEA is structured hierarchically, as shown in the following
diagrams. Each database is organized into two levels, a major level and a minor level,
although the contents of these levels varies considerably from database to database.
At the top of the hierarchy in each database is the primary major element for that
database, whose values we call the primary major values. Beneath this in the hier-
archy is the primary minor element, which can take many values for a single primary
major value. The groups for the primary major and minor data elements have double
lines around them, rather than simply a single line. The fact that the primary minor
element can take many values, so that in effect there is a copy of the structure
beneath the primary minor element for each of these primary minor values, is shown
in the diagrams by having several lines entering its box, rather than just one line.
The remainder of the data elements in the groups on the major and minor levels can
then occur either many times (a "repeating" record), or only once (a "non-repeating"
record). This is again shown by having either several lines, or simply one line,
entering the group's box.
To clarify these concepts, it may help if we note that the IDEA databases can be
separated into three categories:
1. The AFS, ERN, FFI, NCD, PCS, SET, and TRI databases are all stru ctured
similarly in that, in each, the primary major value is a facility ID number. Thus
all the data beneath it will concern this facility. The primary minor element for
each database then divides the data for this facility in disjoint parts, according to,
for example, the Air Program code, report date and time, sample number, or pipe
number, associated with the data.
2. The DCK and LST databases have as their primary major values the responsible
office for the enforcement tracking. Beneath this on their hierarchies, the case
number is the primary minor value used to organize the data.
3. The DUN, FIN, and RCR databases have as their primary major valu e the state
in which the facility is located, and as their primary minor value the facility ID
number.
Appendix E. The Structure of the IDEA Shadow Databases E-1
-------
For groups comprised of repeating records, the data elements shown in the diagrams,
called the "keyed" elements for the group, will uniquely determine the record. For
convenience, these are also marked with a parenthetical "K" in the data element
listing in Appendix C, Data Elements in IDEA Shadow Files.
In each of the databases, except for some groups in OSH, PCS, RCR, and TRI, the
elements in a group comprise a record. Some elements are not required fields in the
source databases, and hence could be blank in some records. (You will have to
consult the data dictionary for each source database to see which fields are required
fields.)
In OSH, PCS, RCR, and TRI, some groups (called "portmanteau" groups) have
several types of records, which themselves may have hierarchical relationships. The
type of record present is determined by which of the keyed elements are present in the
record. An attempt has been made to depict the hierarchy within these groups by
stacking "parents" on top of their "offspring", and not to stack otherwise.
For example, in the Instrument group in RCR, there are four different types of
records. An Instrument record has the elements INST, IAGCY, and IEDATE as its
keyed elements. The "offspring" of these records are the Legal Authority records,
which have as their keyed elements INST, IAGCY, and IEDATE, plus ISTAT and
ISEQ, and the Instrument Area records, which have INST, IAGCY, IEDATE, and
CAREA as keyed elements. These latter two types of records might be called "sib-
lings". The Instrument Area records then have as "offspring" the Corrective Action
Event records, which have as keyed elements the same keys as the Instrument Area
records, plus IEMOD, IECODE, IEAGCY, and ISEQ. In the data element listing in
Appendix C, Data Elements in IDEA Shadow Files, the non-keyed elements of these
four records are denoted by the numbers 1 through 4 in parentheses. The same is
done for the other groups of this type in OSH, PCS, RCR, and TRI.
E-2 IDEA User's Guide February 29, 1996
-------
AFS Identifier
AFSID
Air Program Code
APC1
Figure E-l. AFS Database Skeleton
Media
MEDC
Defendant
Citation
CITX
Ancillary
ANCI
Figure E-2. CRM Database Skeleton
Appendix E. The Structure of the IDEA Shadow Databases
E-3
-------
Responsible Office
RSOF
r
•}
I Case Number ||
CSNO
Case)
Laws
LAWS
SECT
Pollutant
POLL
Violation
Type
VIOT
Plaintiff
PLTF
Intervenor
INTV
Defendant
DFNM
Amendment
ANUM
Comment
PGNM
LNNM
Figure E-3. DCK Database Skeleton
Figure E-4. DUN Database Skeleton
E-4
IDEA User's Guide
February 29, 1996
-------
State and Discharger Identifier
STATE DID
Report Date and Time
DTRPT TMRPT OWNID
Report
r
Spill
~i
Material
Spilled
MTRLSEQ
Details Actions] j Text
Figure E-5. ERN Database Skeleton
Federal Facility
Id Number
FFID
Figure E-6. FFI Database Skeleton
Appendix E. The Structure of the IDEA Shadow Databases
E-5
-------
EPA Identifier
EPID
Identification Information
SRCE SRID
SRIDSEQ
Figure E-7. FIN Database Skeleton
Responsible Office
RSOF
Jo.
Case Number
CSNO
r
Case!
3 r
Pollutant
POLL
n r
Law
LAW
SECT
-\ r
CFR
CFRT
CFRS
T r
Relief
Sought
RLFS
n r
Basis Law
BLAW
BACT
n r
Standards
Which Apply
SDWAPG
SDWALN
l r
Continuing
Viol Page
CRVLPG
CRVLLN
-i r
Prerequisite
Enforc Action
PEFAP6
PEFALN
n r
Proposed
Remedy
PRRMPG
PRRMLN
n
Case Status
Comments
CSCMPG
CSCMLN
r
n
Facility
Information
FCINPG
FCINLN
Figure E-8. LST Database Skeleton
E-6
IDEA User's Guide
February 29,1996
-------
NCDB identifier
NCDBID
I COMMMi
Identification
Information
NAMESEQ
Inspection/
Import
Referral Actions
Terms
TERMSEQ
Sample Number
SAMPS
Figure E-9. NCD Database Skeleton
<~h
^ gj£
RELITt
rri
>d Optional
V Info
=M OPTTYPE
Establishment
ESTABST ESTABNR
r
1
Inspection Activity
ACTIVTY
r
[Debt|
1
i
rn m rn
Violations Records
1. Violations
VIOLKEY
2. Violation History
HSTDT HSTEVNT
Accidents Administrative Payments
ACCITEM Date pAYTYpE
ADMTYPE PAYDT
ADMDT ' '
Figure E-10. OSH Database Skeleton
Appendix E. The Structure of the IDEA Shadow Databases
E-7
-------
llNPDES Identifier
|| NPDES
1 rh
Permit Pretreatment Inspections (IN) Records
hadlrty(Hr-) Performance 1. Pretreatment Inspections
1 ' Summary (SP)
LMIN lirl
2. Inspection
SINS
3. Inspection Schedule
SIDT
Permit
Event (PE)
>
Pipe Number
1 DSCH 1
Effluents (EF) Records
1. Pipe Schedule
DRID PIPQ
2. Pipe Limits
VLIM VPRM VMLO
VSEA VMOD
3. Pipe Measurements
MVDT
rh rh
Compliance Enforcement
Schedule (CS) Actions (EA)
Violation ENAC
/CSN VDCD IAJP
CVEV CVIO
CVDT
Figure E-ll. PCS Database Skeleton
E-8
IDEA User's Guide
February 29, 1996
-------
rh
rf-i , rfi
Handler]
Contact II Owner
CONfTTYPll HCOSEQ
SIC Code
SICSEQ
Source Records
1. Source
Activity
SOURCE
RECDATE
2.Wasta
WASTSTR
3. Waste
Code
SOURCE
WASTSTR
WASTCD
4. Waste
Process
SOURCE
WASTSTR
WASTPRO
5. Faculty
Process
SOURCE
PROCESS
PROCSEQ
6. Process
Amount Type
PROCATT
7. Process
Unit Group
PROCUID
Instrument Records
11. Instrument
INJST IAGCY IEDATE
2. Legal
Authority
ISTAT
ISEQ
3. InstrumBni
Area
CAREA
4. Corrective
Action Event
IEMOD IECODE
IEAGCY ISEQ
Enforcement Records
1. Enforcement Key
Data Records
CEENUM ENFAQN
EDATE
2. SEP/
Milestone
Data
SEPSEQ
3. Multimedia
Action
MMCODE
4. Penalty
Data
EAIvTTTYP
rh rh rh rh
Evaluation Records
1. Evaluation
Type
EVALNO
EVALAGN
EVALDTE
2. Evaluation
Area
EVALNO
EVALAGN
EVALSEQ
Violation Records
1. Violation Data
CEWKEY
2. Evaluation
Link
EKEY
EKEYSEQ
3. Enfcr ctinw ill
Link
VENFKEY
EKEYSEQ
ORPN
EMOD
ECODE
EAGCY
ESEQ
Penult Sequence
Records
1. Permit
PSQN
2. Event Activity
PECODIE PEAGY
PES5EQ
Unit Groups
UNITSEQ UNITNAME
PUSEQ
rh
Commitment Records
1. Commitment
CTYPE CFY
2. Activity Tracks
and Events
EVCODE CID
3. Activity Track Link
CHIDNUM CKEY
Figure. E-12. RCR Database Skeleton
Site Id Number
S1TEID
Potentially Responsible
Party Code
PRPCODE
Figure E-13. SET Database Skeleton
Appendix E. The Structure of the IDEA Shadow Databases
E-9
-------
TRIS Facility Identifier
TFID
rn
SIC Code Records
1. Certain SIC Codes
SRPYR
2. All SIC Codes
SICD
Document Number
DCNO
Activity Use Code
AUCD
Chemical
Source Release
Reduction Activity
SRDRCYC
Release
RSEQ
Treatment
TSEQ
Figure E-14. TRI Database Skeleton
E.2 How the underlying structure affects your Select criteria
When IDEA decides whether a facility satisfies your Select criteria, it combines the
criteria at the lowest level possible. As a result, the underlying structure described
above affects how facilities are selected.
In the query below, we request a User-specified Report on facilities having Zip Code
FIN.FZIP = 21220 AND FFIS media FFI.PMED = CA, and then AND these facul-
ties with those having FFIS compliance status FFI.CPST = ESDF.
E-10 IDEA User's Guide
February 29, 1996
-------
Figure E-15. Select Criteria consulting two databases
Recall in Chapter 11, IDEA User-specified Reports, that the data elements in the
IDEA shadow databases can be on one of four levels. (See Table E-l.) You can
see, by consulting Appendix C, Data Elements in IDEA Shadow Files, that FIN.FZIP
is a level 4 data element in FIN, and FFI.PMED and FFI.CPST are data elements on
level 3 in FFI, in the same group.
Table E-l. Levels of Hierarchy in IDEA Shadow Databases
Level
1
2
3
4
Description
Major-valued,
Major-valued,
Minor-valued,
Minor-valued,
Non-repeating Group
Repeating Group
Non-repeating Group
Repeating Group
Because we are consulting more than one database when we AND the first two cri-
teria, IDEA must combine these criteria at the facility (FINDS) level. Thus any two
FIN.EPIDs with a FIN.FZIP = 21220 and a FFI.PMED = CA will match the
ANDing of the first two criteria. When these facilities are then ANDed with the
facilities having compliance status FFI.CPST= ESDF, this will also be done at the
facility level.
The User-specified Report (USR) generated by this query is shown in Figure E-16 .
Two facilities met our query criteria. Notice that the level of each data element is
printed out in the fourth column in the table at the top of the USR.
Appendix E. The Structure of the IDEA Shadow Databases
E-11
-------
- /:;
( ^^ v i ,«~? ^
of report • ,.~/."
Figure E-16. User-specified Report—Two facilities
If, however, we change line 11 in Figure E-15 to be FFI.ZIPC = 21220, we are no
longer consulting two databases in our query. (See Figure E-17.) FFI.ZIPC is a
level 1 data element in FFI.
E-12 IDEA User's Guide
February 29, 1996
-------
Figure E-17. Select criteria limited to FFIS
As a result, since FFI.ZIPC is at a higher level than FFI.PMED, IDEA will combine
these two criteria at FFLZIPC's level, the local ID (in this case, FFI.FFID) level.
IDEA will then AND these facilities with the facilities having compliance status
FFI.CPST= ESDF at the local ID level also.
The results of the query in Figure E-17 are showri below. Note that the second
facility in Figure E-16 did not meet the query criteria this time, because its occurences
of FFI.PMED = CA and FFI.CPST = ESDF are under different local IDs.
Appendix E. The Structure of the IDEA Shadow Databases
E-13
-------
Figure E-18. User-specified Report—One facility
We can get a third result by changing the parentheses in the query, so that the cri-
teria are combined in a different order. (See Figure E-19.) Note that changing this
order makes a difference even when both logical connectors are AND!
E-14 IDEA User's Guide
February 29, 1996
-------
Figure E-19. Select criteria with parentheses reversed
In this case, since the data elements FFI.PMED and FFI.CPST are in the same
group, the criteria FFI.PMED = CA and FFI.CPST= ESDF will be ANDed at that
level. Thus a facility would have to meet both of these criteria, FFI.PMED = CA and
FFI.CPST = ESDF, in the same record. (Any facilities meeting these criteria would
then be ANDed with the facilities having FFI.ZIPC = 21220 at the local ID level.)
As we can see from Figure E-16 , no facilities meet the combination of these two
criteria, so as a result, we get the following message:
Figure E-20. Query Status Screen-No facilties
Appendix E. 'The Structure of the IDEA Shadow Databases
E-15
-------
E-16 IDEA User's Guide February 29, 1996
-------
Appendix F. Accessing the User's Guide Online
This appendix takes you step by step through accessing the online version of the
IDEA User's Guide from IDEA, and through printing additional copies of the Guide
online.
F.I Accessing the User's Guide in Bookmanaser
To view the IDEA User's Guide online, first type books at any Command prompt in
IDEA and press < Enter >.
U.V, &jsl'JdJi,4Js. , WfiS',, ••.<£. '
Figure F-l. The books command
The EPA SOFTCOPY LIBRARY MAIN PANEL will appear.
Appendix F. Accessing the User's Guide Online
F-1
-------
Figure F-2. The EPA SOFTCOPY LIBRARY MAIN PANEL
Type 1 at the Command Prompt, to enter the Environmental bookshelves, and press
< Enter >. A bookshelf list will appear.
'€oirmasd"===>
Shelf Naaae',
OECA-PCS".
OECATESI
OS-RCRtS
Otf-AWPD
OWTEST
Figure F-3. Environmental Bookshelves
F-2 IDEA User's Guide
February 29, 1996
-------
Note that in addition to the OECA bookshelf, where the IDEA softcopy documenta-
tion resides, there are bookshelves here with information about PCS and RCRIS, if
you are interested.
To enter the bookshelf where the online version of the User's Guide resides,
down to the OECA bookshelf, type an S next to it, and press < Enter > . The
ENFORID bookshelf (where all IDEA bookmanager documents reside) will appear.
i-
Currently there are two IDEA bookmanager documents, the IDEA User's Guide, and
course material on how IDEA is built each month, from the program databases that
IDEA links together. Although it is available for your perusal, it is not necessary to
read the latter document to use IDEA effectively.
In the future, we plan to add the IDEA training materials (for example, the IDEA
Basic Training Student Booklet) to this bookshelf.
Figure F-4. The IDEA Bookshelf
To view the Guide online, < Tab > down to the IDEA User's Guide, type an S next
to it, and press < Enter >. The table of contents of the IDEA User's Guide will
appear.
Appendix F. Accessing the User's Guide Online
F-3
-------
Books' 6oTa" Search ^JMef ?SM
ED1TWH
. -CONTENTS
"•TABLES . ,^,».^: .j.,.,
:«', FIGURES"" " "-'"-i-li-'S! * -"
1.6 " " "
, la " '"
" 1,2
z,s , , -riiH^,io^';fr^es^y
L3,i ,,,,.j,,,!r,,,,, ,|^M^L^?K!
Figure F-5. Table of Contents of the IDEA User's Guide
In order to view any of the sections of the User's Guide online, use < PF7> and
< PF8> to scroll through the Table of Contents, place your cursor on the section
number, and press < Enter >. You can also scroll through the User's Guide using
and .
References to other sections in the User's Guide (which will be displayed in another
color if your terminal supports multiple colors), can also be used to navigate the
User's Guide. By placing your cursor on such a reference and pressing < Enter >,
you will "jump" to the section referenced.
When you are finished viewing the User's Guide, and wish to return to IDEA, press
PF3. A popup window will ask you if you wish to leave a bookmark. Type 3 (so as
not to leave a bookmark) and press < Enter >. You will return to the ENFORID
bookshelf. Press < PF3> again. A popup window will ask if you want to close the
bookshelf. Press < Enter > to close the bookshelf. Your will return to the list of
Environmental bookshelves. Press < PF3 >, and then < Enter >, again. Finally,
press < PF3 > to exit bookmanager and return to IDEA.
F-4
IDEA User's Guide
February 29, 1996
-------
F.2 Printing Additional Comes of the IDEA User's Guide
To print additional copies of the IDEA User's Guide, type PRTBOOK at any
Command prompt in IDEA, and press < Enter > . An ISPF panel, with several
prefomatted documents to choose from, will appear.
f .vssys1"' '!<<' 'rwS^f,r,r;T^',¥'*"Pl|; down to the IDEA User's Guide, type a P next to it, and press < Enter >
The EPA PRINT ROUTING SCREEN will appear.
Appendix F. Accessing the User's Guide Online
F-5
-------
8e sure the
print CJECA IBEft. ilse?-1* Sgi|e;,j;;r
from, «f atas&J: ^Af^p&U;,', "* "" "'"
If you don^t "'"'"""
Address =-=>
Figure F-7. EPA Print Routing Screen
We suggest you print the User's Guide at the National Computer Center (R90), and
have it mailed to you. Choose either S for standard 8 1/2 " x 11" paper (without
holes), or 3 for 3-holed paper. Type in your name. Type in your address (you may
use 2 lines). Type in your building, if applicable. For your bin, type Mxxx (where
xxx is your 3-character UserlD).
Note that there is no option here to specify the number of copies to be printed. If
you wish to print a large number of copies, call IDEA User Support at (202)
564-2475, and we can show you how to print many copies at once. With the method
outlined here, you are limited to printing one copy at a time.
Press < Enter > when you are finished. In the upper-right corner, in should say that
the document has been "SENT TO PRINTER." Press < PF3 > to return to IDEA.
F-6 IDEA User's Guide
February 29, 1996
-------
Glossary
AA. Administrative Action.
Account Number. This prompt occurs on the
EPA2 TSO/E LOGON SCREEN and should be
completed with a four-character code issued by the
TSSMS Office.
ADP Coordinator. For EPA employees, Auto-
mated Data Processing Coordinators establish
accounts, register users, and control the expenditure
of time sharing funds.
AFS. The AIRS Facility Subsystem (Office of
Compliance).
AIRS. Aerometric Information Retrieval System.
AND. Tells IDEA to retrieve any facility that ful-
fills the first criterion AND the second criterion.
Bin. This four-character code of the form MUBD
is used in conjunction with the printer destination
ID. If you will be unable to collect your printouts
from the destination, M instructs the people who
receive the printouts to mail them to you (use F to
indicate express mail). UID is your user ID.
Boolean Connectors. Logical connectors used
between expressions in IDEA queries.
AND tells IDEA to retrieve any facility that fulfills
the first criterion AND the second criterion.
OR tells IDEA to retrieve any facility that fulfills
the first criterion OR the second criterion.
NOT tells IDEA to retrieve any facility that does
not fulfill the following criterion.
Boolean Operator. A logical connector used within
a SELECT statement in IDEA'S Keyword Inter-
face. There are eight currently available in IDEA:
EQ (equals), GE (greater than or equal to), GT
(greater than), IN (in the range of), LT (less than),
LE (less than or equal to), and NE (not equal to).
Browse Mode. Allows you to view, print, and save
data that appears on the screen; but you cannot
alter it.
Browse Screen. An ISPF screen that allows you to
scroll vertically and horizontally through a docu-
ment without affecting the form or content of the
text. IDEA creates a Browse Screen to allow you
to view your report(s) interactively.
CAA. Clean Air Act.
CAS #. Chemical Abstract Service number.
Case Screening. Searching for facilities according
to facility name. This type of search can be done
using the GO Names utility of the Keyword Inter-
face.
Category. Au group of query criteria. There are six
categories (Location, Pollutants, Industry, Non-
compliance, Enforcement, and Facility Status)
available to you in the Menu Interface. For each
of these categories, IDEA provides pop-up screens
from which you can select criteria for your query.
CEM. Continuous Emission Monitoring.
CERCLA. Comprehensive Environmental
Response, Compensation, and Liability Act.
CERCLIS. CERCLA Information System (Office
of Solid Waste and Emergency Response).
COMMAND prompt (COMMAND = = = >).
You can type ISPF commands at this prompt.
The COMMAND prompt is available on the fol-
lowing screens: INPUT LIBRARY SELECTION
SCREEN, MEMBER LIST SCREEN, EDIT
SCREEN, NAME SELECTION MENU SCREEN,
QUERY STATUS SCREEN, and BROWSE
SCREEN.
Comments, itn the Keyword Interface EDIT
SCREEN, remarks preceded by /* on a line are not
read by the computer. Therefore, you can use this
symbol to include comment information in your
queries.
Corporate Profile. An option available in GO
Names. This option allows you to retrieve the cor-
porate parent and child relationships of facilities by
selecting all the facilities having the same ultimate
Glossary
X-1
-------
parent number in the Dun & Bradstreet Marketing
Index.
County Code. A five-character PIPS code that
consists of a two-letter postal abbreviation for a
state followed by a three-digit code that represents
a county (e.g. VA059 is for Fairfax County, VA).
Cross-Reference Numbers. These numbers/codes
are the local IDs for facility used by FINDS to
connect information on the facility across EPA
program office databases.
CWA. Clean Water Act.
Database. A source of information for your query.
In a Keyword query, the database you want IDEA
to search is the first component in your SELECT
statement. To refer to a database in a SELECT
statement, you must use the 3-character abbrevi-
ation for it:
chosen within the category pop-up windows.
Examples of data values include specific locations
such as 03755 for ZIP code, specific pollutant
names such as Toluene, pollutant codes such as
000108883, or waste amount ranges such as 20,000
to 40,000 tons.
Default. Automatic settings in IDEA. In the j
absence of a user-specified value, IDEA reverts to
default values. For example, on the PRINT/SA VE
PARAMETERS SCREEN, if you do not input a
number at the NO OF COPIES prompt, IDEA
will assume you want only one. The default setting
for this prompt is one.
Destination. The printer output station for your
office. Destinations are of the form RRP# where
the first R stands for remote and RP# for the
number of the remote printer assigned to you. If
you do not know your destination number, contact
your ADP Coordinator.
AFS - AFS
DUNS - DUN
FINDS - FIN
OSHA = OSH
SETS - SET
CERCLIS = CER
ERNS - ERN
LST = LST
PCS = PCS
TRIS = TRI
DOCKET = DCK.
FFIS = FFI
NCDB = NCD
RCRIS = RCR
Refer to Appendix B, "Database Descriptions" on
page B-l for descriptions of each of the databases.
Data Element. A name of a type of data available
in a database, such as a facility's SIC code. In the
Menu Interface, data elements are represented by
the criteria in the pop-up windows for each cate-
gory. In the Keyword Interface, they are referred
to by name after the database abbreviation in the
SELECT statement. For a list of the data elements
accessed by IDEA, refer to Appendix C, "Data Ele-
ments in IDEA Shadow Files" on page C-l .
Data values are the actual values that are stored for
each instance of a data element. For example, 5051
could be a value for a data element called SIC
code.
Dataset. ISPF storage space where you may save
queries and reports.
Data Value. The values of data elements. The
most specific criterion you can enter in your IDEA
query. In the Keyword Interface, data values are
the last components of SELECT statements. In
the Menu Interface, data values are entered or
Printouts can be mailed or express mailed to you
(see Bin for details on these specifications) from the
following destinations:
WIC Washington Information Center at EPA
Headquarters in Washington, D.C.
Local National Computer Center (NCC) at
Research Triangle Park (RTF), North Carolina.
DOCKET. Civil Enforcement Docket (Office of
Enforcement).
DSN. Dataset Name (see also Dataset).
Dun & Bradstreet Marketing Index. One of the
fourteen database copies accessed by IDEA. The
Dun & Bradstreet Marketing Index contains such
information as parent-subsidy relationships, indus-
trial classification (SIC codes), employee counts,
and sales figures for facilities. A Dun & Bradstreet
corporate profile can be obtained by using the GO
Names utility or certain keywords in the Keyword
Interface.
DUNS. Data Universal Numbering System
assigned and maintained by Dun & Bradstreet Mar-
keting Index (Office of Information Resources
Management).
X-2
IDEA User's Guide
February 29, 1996
-------
DUNS Number. A code used in the Data Uni-
versal Numbering System to identify facilities
uniquely. A DUNS Number is a non-indicative
nine-digit number assigned by Dun & Bradstreet to
identify unique business establishments. Digits one
through eight are machine-generated and assigned.
The ninth digit is a check digit which is instru-
mental in catching input errors.
Edit Screen. An IDEA screen identical to the edit
screen in ISPF, this display allows you to write and
edit Keyword Interface queries.
Element. See Data Element.
Enforcement. One of six information categories in
the Menu Interface. Criteria chosen from the
pop-up window for this category will direct IDEA
to search for facilities that have been the subjects of
enforcement actions.
EPA. Environmental Protection Agency.
EPCRA 313. Emergency Planning and
Community-Right-to-Know Act (Section 313 of
SARA Title III).
Facility. EPA defines a facility as a location entity
deliberately established as a site for designated
activities but not primarily for habitation. A
facility may have several functions or several
smaller plants and establishments operating within
its boundaries. In this situation, ID codes will be
assigned to the most comprehensive level.
Facility Index System (FENDS). Computerized
inventory of facilities regulated by the EPA.
FINDS contains two sets of information on each
facility: (1) Facility identification data - such as its
name, unique EPA ID number, and physical
address; and (2) Pointers to EPA program office
databases which contain more information about
the facility. These pointers are the local IDs for the
facility in these databases.
Facility Screening. The process of searching for a
particular facility or group of facilities by name.
This type of search can be performed with the GO
Names utility of the Keyword Interface.
Facility Status. One of six categories for building
queries in the Menu Interface. Criteria chosen
from the pop-up window for this category will
direct IDEA to search for facilities according to
their regulatory status.
Federal Managers' Financial Integrity Act
(FMFIA). A Presidential report submitted to
Congress in FY 199Q that cited the need to inte-
grate factual compliance and enforcement informa-
tion in EPA's mainframe, data systems. This act
was one of the contributing factors that led to the
development of IDEA.
FEDFAC. Federal Facility Flag in the National
Compliance Database (NCDB).
FFIS. Federal Facility Information System (Office
of Federal Facilities Enforcement).
FIFRA. Federal Insecticide, Fungicide, and
Rodenticide Act.
FEVL4S Prompt. The Facility Impact Monitoring
and Analysis System Identification prompt occurs
on the EPA2 TSO/E LOGON SCREEN and
should be completed with the four-character code,
IESYP.
FINDS. Facility Index System (Office of Informa-
tion Resources Management). See also Facility
Index System.
FMFIA. See Federal Managers Financial Integrity
Act.
GAO. General Accounting Office.
GO MenuA. This utility allows you to build a
query in the Menu Interface, generate keywords for
the query, and edit the keywords generated in the
EDIT SCREEN of the Keyword Interface. From
the Keyword Interface, you can access the GO
MenuA utility by typing GO MenuA at the
COMMAND prompt.
GO Names. A utility available in the Keyword
Interface EDIT SCREEN that allows you to
perform a search according to facility name(s)
and/or location(s) and retrieve corporate profile
information (from DUNS) on the facilities selected.
Hardwired Terminal. A terminal directly linked to
the NCC — which does not require dialing through
telephone lines.
HPV. High Priority Violator.
Glossary
X-3
-------
IDEA. Integrated Data for Enforcement Analysis
(Office of Compliance).
IG. Inspector General.
Industry. One of six information categories in the
Menu Interface. Criteria chosen from the pop-up
window for this category will direct IDEA to use
SIC codes to search for facilities according to their
industry type.
INPUT. Every query must have an INPUT state-
ment that tells IDEA how to search for facilities
that meet your query criteria. The INPUT can be
linked, Nonlinked, or Linked Nonlinked.
Input and Report Selection Screen. A pop-up
window in the Menu Interface that appears when
you select the RUN QUERY option. This screen
allows you to choose the type of input you want
for the query (Linked and/or Nonlinked) and the
report format (1A, IB, 2, and/or SUMMARY) for
the data that will be retrieved.
Input Library Selection Screen. The first screen
you see upon entering the Keyword Interface.
This screen allows you to specify the library you
will be using for your search and the status of that
library.
Integrated Data for Enforcement Analysis
(IDEA). This system, the subject of this manual,
provides two interfaces that allow the user to
retrieve information from (in most cases) copies of
fourteen EPA data systems in integrated and non-
integrated queries.
Interface. A means for the user to access the data
available through IDEA.
Interface Selection Screen. This screen allows you
to choose between the Keyword Interface, or the
Menu Interface. It is the second screen that
appears when you enter IDEA after the IDEA
WELCOME SCREEN.
ISPF. IBM's Interactive System Productivity
Facility is a mainframe word processor that is used
to construct and execute queries in the Keyword
Interface EDIT SCREEN.
JA. Judicial Action.
JCL. Job Control Language.
Keyword Interface. The more complicated and
flexible of the two interfaces available in the IDEA
system. The Keyword Interface allows you access
to the GO Names utility and GO MenuA utility as
well as the EDIT SCREEN where you can write
queries or edit existing ones. The Keyword Inter-
face allows you to form queries by using specific
syntax (keywords) for the database(s) and particular
data values for which you want IDEA to search.
LAN. Local Area Network.
Library. A place in IDEA where you can build
and store queries and reports. Libraries contain lists
of members. Members are queries or reports that
you store in your library as with files in a
WordPerfect directory.
Library Status. Determined by the user in the
Keyword Interface INPUT LIBRARY
SELECTION SCREEN. There are three options
available: NEW (for establishing a new library),
SHR (shared — the default setting which will allow
other users to access the library), and OLD (which
provides exclusive library access to the user).
Line Edit Commands. Commands that can be
issued in the line numbers of the Keyword Interface
EDIT SCREEN.
LINKED. A keyword (for the INPUT statement)
that instructs IDEA to integrate facility data using
FINDS. It may be combined with nonlinked to
report on facilities that meet the query criteria
whether or not they are in FINDS.
Linked Data. Data retrieved as the result of a
linked query. See Linked.
LINKED NONLINKED. A query type that
selects facilities that match your query criteria
whether or not they are in FINDS. Linked non-
linked queries attempt to integrate data on facilities
that are in FINDS but still reports on the ones that
are not.
Local IDs. Facility identification codes or numbers
used within the individual EPA databases.
Location. One of six information categories in the
Menu Interface. Criteria chosen from the pop-up
window for this category will direct IDEA to search
for facilities according to a specific geographical
X-4
IDEA User's Guide
February 29, 1996
-------
area - ranging from the size of an EPA region to
the area covered by a ZIP code.
LST. Contractor Listing Docket (Office of Com-
pliance).
Media. The sectors of the environment (land, air,
or water) to which a contaminant is released. See
also Multi-media.
Member. A work space in IDEA where you can
create and store queries or reports. Members are
stored in your library much Eke files in a
WordPerfect directory.
Member List Screen. This screen, that appears
after the INPUT LIBRARY SELECTION
SCREEN, lists all the members you have created in
that library. From this screen, you can choose to
(B)rowse, (E)dit, (R)ename, (U)pdate descriptions
for members, or (D)elete them one at a time.
Menu Interface. The simpler of the two interfaces
for IDEA. The Menu Interface is a structured,
graphical display that features menu-Eke pop-up
windows. These windows allow you to choose cri-
teria from different data elements and values while
constructing your query.
Multi-Media. More than one sector of the envi-
ronment (or media such as land, air, or water).
Name Selection Menu. The screen for the GO
Names utiEty. This screen, accessible through the
Keyword Interface, allows you to perform a search
for faciEties by name and/or location. Moreover,
you can specify a Dun & Bradstreet corporate
profile on the facilities your search retrieves.
National Computer Center (NCC). The
mainframe computer center located in Research
Triangle Park (RTF), NC that provides EPA with
support for scientific and administrative appEca-
tions. NCC serves EPA customers and other quaE-
fied agencies and contractors through a
telecommunications network that allows the dis-
tribution of computer services to remote locations.
For comprehensive User Support service, call NCC
User Support at one of the following telephone
numbers:
NCC User Support
from outside NC 1 800 334-2405
inside NC
NC. NoncompEer.
919 541-7862
NCC. National Computer Center (location of
EPA's ES/9000 mainframe). See also National
Computer Center.
NCC Account. A four-letter code that indicates
the account to which you are assigned. If you do
not know your NCC account, contact you ADP
Coordinator.
NCDB. National CompEance Database (Office of
CompEance).
NDPD. The National Data Processing Division is
part of the Office of Administration and Resources
Management located at the National Computer
Center.
NESHAP. National Emissions Standard for Haz-
ardous Air Pollutants.
NEW. The Ebrary status option for a new Ebrary.
NEW can be specified at the LIBRARY STATUS
prompt of the INPUT LIBRARY SELECTION
SCREEN.
Noncompliance. One of six information categories
in the Menu Interface. Criteria chosen from the
pop-up window for this category will direct IDEA
to search for faciEties according to their CompEance
record.
Noncomplier. A faciEty whose status is not in
compEance with EPA laws and/or regulations.
NONUNKED. Nonintegrated queries. In Non-
Enked queries, IDEA does not attempt to integrate
faciEty data. Instead of using FINDS as a cross-
reference mechanism, these queries search and
retrieve data from (for the most part) copies of the
program office databases. This keyword should
appear in the INPUT statement.
Nonlinked Data. Data retrieved as the result of a
nonEnked search. See Nonlinked.
Nonlinked Linked Data. See Linked Nonlinked.
NOT. NOT tells IDEA to choose any faciEty that
does not meet the criterion this word modifies.
Glossary
X-5
-------
NOV. Notice of Violation.
NPDES. (pronounced 'Nip-dees') National Pol-
lution Discharge Elimination System.
NPL. National Priorities List (under CERCLA).
NSPS. New Source Performance Standard.
OARM. Office of Administration and Resources
Management.
OC. Office of Compliance.
OECA. Office of Enforcement and Compliance
Assurance.
OffiM.
ment.
Office of Information Resources Manage-
OLD. A library status option that allows the user
exclusive access to the library. OLD can be desig-
nated at the LIBRARY STATUS prompt of the
INPUT LIBRARY SELECTION SCREEN of the
Keyword Interface.
OR. OR tells IDEA to retrieve any facility that
fulfills the first criterion OR the second criterion.
OUTPUT. The statement within a query that
specifies the destination of the query output (or
reports). Query output can be directed to your
screen, a printer, a dataset, etc.
Password. An EPA mainframe password must be
three to eight characters long and contain at least
one numeric.
PCS. Permit Compliance System (Office of Com-
pliance).
PDF. Productivity Development Facility.
PF Key. See Program Function Key.
Pointers or Links. For each facility in FINDS,
there are pointers to EPA program office databases
to which it is linked (or local IDs for the facility in
each linked system) where more information about
the facility can be obtained. The pointers are the
local IDs for the facility in these databases.
Pollutants. One of six information categories in
the Menu Interface. Criteria chosen from the
pop-up window for this category will direct IDEA
to search for facilities according to the pollutants
they have released, generated, stored, or handled.
Pop-Up Window. A type of screen that appears
after you select a query category (such as Location,
Pollutants, Industry, Noncompliance, Enforcement,
or Facility Status) or a query management option
(such as Run Query, Clear Query, Save Query, or
Retrieve Query) or issue commands to print or
save a query. Once the pop-up window appears, it
becomes the operable screen, allowing you to
choose criteria or items from it or specify data
values.
Primary Commands. Commands that can be
issued at the COMMAND prompt to perform
general editing operations such as FIND and
CANCEL.
Print/Save Parameter Screen. A pop-up window
accessible from the BROWSE SCREEN which
allows you to specify print and save information.
Procedure. This prompt, which occurs on the
EPA2 TSO/E LOGON SCREEN, should be set to
SEPATSO.
Program Function (PF) Keys. Keyboard functions
that allow you to issue commands without having
to type them at the COMMAND prompt. The PF
number given corresponds to different keys on dif-
ferent keyboards depending on the configuration.
Program Office Database. A database maintained
by one of the EPA program offices.
PRP. Potentially Responsible Party. Designation
in CERCLIS, or SETS, given to facilities thought
to be responsible for a abandoned waste site.
Query. A question or request for data according
to criteria you specify.
Query Report. See Report.
Query Retrieval Screen. A pop-up window in the
Menu Interface that appears after you select
Retrieve Query. This screen lists all the queries
that you have saved in the Menu Interface.
Query Status Screen. After you run a query and
IDEA performs the initial facility selection, IDEA
X-6
IDEA User's Guide
February 29, 1996
-------
will display this screen to notify you of the number
of facilities selected.
RACF. Resource Access Control Facility.
RCRA. Resource Conservation and Recovery
Act.
RCRIS. RCRA Information System (Office of
Solid Waste and Emergency Response).
REPORT. A keyword that specifies the query
report format (either a standard report, or user-
specified). It must follow the OUTPUT statement.
Report Format. The format of the data retrieved
by IDEA on facilities selected in accordance with
the query criteria. There are four standard report
formats currently available in IDEA: 1A, IB, 2,
and SUMMARY.
Retrieve Query. A Menu Interface option that
allows you to recall a previously saved query.
RTP. Research Triangle Park, North Carolina is
the address of the National Computer Center where
EPA's ES/9000 mainframe computer is located.
Run Query. A Menu Interface option that allows
you to process the query you have built. The
results of the search, will appear on the QUERY
STATUS SCREEN. To run a query in the
Keyword Interface, type GO at the COMMAND
prompt of the EDIT SCREEN.
SARA. Superfund Amendments and Reauthori-
zation Act.
SCROLL Prompt. A prompt on the EDIT
SCREEN that allows you to set the number of
spaces that the screen will move in any one direc-
tion per keystroke. The default is to scroll by page.
You can enter any number value to replace the
default.
SELECT. A required statement for a keyword
query. SELECT statements contain the search cri-
teria for your query.
SETS. Site Enforcement Tracking System (Office
of Solid Waste and Emergency Response).
SHR (Shared). A library status option that
enables other users to access the specified library.
SHR can be designated at the LIBRARY
STATUS prompt on the INPUT LIBRAR Y
SELECTION SCREEN.
SIC Code. The Standard Industrial Classification
code system categorizes business establishments
based upon the type of activity performed by that
establishment. Each SIC consists of a four-digit
code denned in the Standard Industrial Classifica-
tion Manual published by OMB (Office of Manage-
ment and Budget).
Significant Noncomplier. A facility that is noted as
significantly out of compliance with EPA laws
and/or regulations.
SEP. State Implementation Plan.
SNA Gateway. System Network Architecture ~ a
communications access port to the mainframe.
SNC. (pronounced 'snick') Significant
Noncomplier.
SQG. Small Quantity Generator.
Standard Industrial Classification (SIC). A four-
digit code assigned to a particular sector of industry
by the US Government. See also SIC code.
STARS. Strategically Targeted Activities for
Results System.
Targeting. Searching for all facilities that fit
certain parameters or query criteria, e.g., searching
for RCRA Generators.
TCE. Trichloroethylene.
3270 Terminal Emulation. To communicate with
EPA's mainframe computer at the National Com-
puter Center, you must have at least DEC VT100,
IBM 3270 (or a compatible terminal), or software
that can emulate one of these terminals. Your
ADP Coordinator can assist you with establishing a
communications linV to NCC.
TRI. Toxics Release Inventory.
TRIS. Toxic Chemical Release Inventory System
(Office of Pollution Prevention and Toxic Sub-
stances).
Glossary
X-7
-------
TSCA. (pronounced Tas-ka') Toxic Substances User ID. A unique identification number assigned
Control Act. to each NCC user- ^ y°u are an EPA employee,
you can obtain a user ID from your ADP Coordi-
TSD. Treatment, Storage, and Disposal (in nator.
RCRIS TSD can equal Treater, Storer, or
Disposer). Value. See Data Value.
TSO. Time Sharing Option. WIC. Washington Information Center (where
IDEA Training courses are most frequently
TSSMS. (pronounced Tiz-missO Time Sharing offered).
Services Management System.
X-8 IDEA User's Guide February 29, 1996
-------
Index
Accessing IDEA 3-2
Access policy & procedures A-l, A-2
EPA Contractor Employees A-10
EPA Office of Enforcement Employees A-9
EPA Program Office Employees A-8
EPA Regional Employees A-7
Hardware Considerations 3-2
Non-sensitive access A-l
requesting mainframe User-ID A-5
Sensitive access A-l
Using a Modem 3-4
Using SNA Gateway 3-3
AFS
Data Elements C-2
Description B-l
B
Boolean Operators/Connectors 8-10
AND 8-15
NOT 8-13
OR 4-9, 8-14
c
CERCLIS
Data Elements C-3
Description B-2
Codes
Chemical Code 4-12
Pollutant Code 4-11
SIC Code 4-16
State/County Code 4-7
Waste Code 4-12
ZIP Code 4-8
Criteria 2-1, 4-1, 4-8, 4-26, 7-1
CRM
Data Elements C-14
D
Data
Data Elements C-l
Database Descriptions B-l
Integration 2-6
Interpretation considerations A-3
Limitations on Use A-3
Data (continued)
Non-sensitive access A-1
Security 5-9
Sensitive Access A-l
STARS reporting A-3
Dataset
Definition 5-1
See Library 5-1
DOCKET
Data Elements C-l5
Description B-3
Dun & Bradstreet (or DUNS)
Data Elements C-l6
Description B-4
E
ERNS '
Data Elements C-17
Description B-5
F :
FFIS
Data Elements C-20
Description B-6
FINDS
Data Elements C-21
Description B-7
Integration 2-8
G
GO MenuA 7-1, 7-4
Editing Queries 7-8, 7-10
Exiting 7-6, 7-13
Reports 7-12
Running a Query 7-11
GO Names 7-8
Corporate Profile 6-12
Editing GO Names Queries 6-1
Exiting GO Names 6-19
looking at a go names query 6-13
Managing Queries in the ISPF Mode 6-10
Modifying a GO Names Query 6-15
Running a-GO Names Query 6-17
Searching by Facility Name 6T7
Searching for Facilities by Location 6-8
Searching for Facilities by Name and
Location 6-10
Index
X-9
-------
GO Names (continued)
Using ERNS Data 6-5
Using OSHA Data 6-5
viewing a query report 6-18
I
IDEA' 2-1
Authorization Sample Letter A-6, A-7, A-8,
A-9
Background A-2
Conclusion A-4
Implementation approach A-3
Library Security 5-9
Limitations on use of information A-3
Non-sensitive access A-l
Policy & procedures A-l
Security Overview A-3
see Accessing IDEA A-l
Sensitive access A-l
User Support 3-14
ISPF Commands 4-3, 9-1
Adding Comments 9-8
Copy 9-3, 9-10
Deleting Lines 9-2
Exclude 9-11
Excluding Lines 9-6
Find 9-7
Inserting Lines 9-2
Moving 9-3
Repeating lines 9-5
Scrolling Data 9-12
K
Keys/Keyboard Mapping 3-10
Keyword Interface
Building a Query in 9-2
Comments in Queries 8-25
DATASET 8-24
DD 8-25
Exiting 8-29
INPUT 8-6
Interface Selection Screen 8-1
JOB 8-25
OUTPUT 8-19, 11-5
ROUTE 8-25
Running a Query 8-27
Saving a Query 8-29
SELECT 8-8
Keywork Interface
Selecting an IDEA Library 5-1
L
Library
Accepting the default 5-2
Allowing others access 5-9
Defining additional libraries 5-2
Naming convention 5-2
NEW status 5-3
OLD status 5-3
Security considerations 5-9
SHR (share) status 5-2
What is a library 5-1
Linked
Integration 2-8
Linked Nonlinked
Integration 2-9
Logic 2-4
Logoff 3-15
LST
Data Elements C-21
Description B-8
M
Mainframe
Access 3-1
Logging on 3-5
Obtaining an ID 3-1
User Support 3-1, 3-5
Mainframe User-ID
EPA employee request A-5
Non-EPA employee request A-5
Member List 5-3
Creating a New Member/Query 5-4
Deleting a Member/Query 5-8
Editing an Existing Member/Query 5-6
How to name 5-4
Looking at an Existing Member/Query 5-5
Name Requirements 5-4
Renaming an Existing Member/Query 5-6
, Screen Description 5-3
When to name a member 5-4
Writing/Updating a Description 5-7
Menu Interface
Clearing a Query 4-24
Enforcement 4-3, 4-19, 4-20, 4-21
Exiting 4-31
Facility Status 4-3, 4-22, 4-23
Industry 4-2, 4-13, 4-14, 4-15, 4-16
X-10 IDEA User's Guide
February 29, 1996
-------
Menu Interface (continued)
Input and Report Selection Screen 4-27, 4-28
Interface Selection Screen 4-1, 4-31
Location 4-2, 4-4, 4-7, 4-8, 4-9
Noncompliance 4-3, 4-17, 4-18
Pollutants 4-2,4-10,4-11,4-12,4-13
Pop-up Screen 4-1, 4-3, 4-4, 4-8
Retrieving a Query 4-25
Running a Query 4-26
Saving a Query 4-25
'Viewing Reports 4-30
Menulnterface
Pop-up Screen 4-7
N
NCDB
Data Elements C-23
Description B-9
Nonlinked
Integration 2-9
o
OSHA
Data Elements
C-25
P
PCS
Data Elements C-29
Description B-9
PF Keys\Commands
Keys 3-11
Q
Query
Clearing a Query 4-24, 9-11
Combining Queries 9-11
Deleting 4-26
Editing 4-7,4-24
How 4-2
Renaming 4-26
Retrieving 4-25
Running 4-26
Saving 4-25
Query Status Screen 2-7
R
RACF
Allowing others
Definition 5-9
RCRIS
Data Elements C-32
Description B-10
s
Security
Allowing others access 5-9
Non-sensitive access A-l
Policy & procedures A-l, A-2
Sensitive access A-l
SETS
Data Elements C-35
Description B-ll
System Overview 2-12
T
TRIS
Data Elements C-36
Description B-12
u
User Support & Training 3-14
User-Specified Reports 11-1
Construction 11 -29
Custom USR Functions 11-13
DEFINE statements 11-7,11-23
Detail Line 11-6
Expressions 11-7, 11-23
Formatting 11-10
Sorting 11-20
Statistical Functions 11-23
Summary Line 11-22
USR Names 11-5
Z
ZIP
Description B-13
ZIPCODE
Data Elements C-37
5-9
Index
X-11
-------
Printed in U.S.A.
------- |