United States Office of Enforcement and 300-B-96-004e
Environmental Protection Compliance Assurance October 22, 1996
Agency Washington DC 20460 NTIS # PB96-141569
&EPA IDEA User's Guide
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 Facihty Selection 2-6
2.3.2 Integration Process 2-6
2.3.3 Query Status 2-7
2.3.3.1 Linked Quenes 2-8
2.3.3.2 Nonlmked Queries 2-9
2.3.3.3 Lmked Nonlinked Quenes 2-9
2.3.4 Detailed Data Retneval 2-9
2.3.4.1 Linked Quenes 2-10
2.3.4.2 Nonhnked Queries 2-11
2.3.4.3 Linked Nonhnked Quenes 2-11
2.4 Data Analysis Considerations 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 Obtainmg 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-il
3.3.2 Program Attention (PA) Keys 3-12
3.4 Entermg 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-I
4.1 IDEA Menu Categones 4-I
4.2 Using Menu Categories to Form Queries 4-3
4.2.1 Navigatmg 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 Quenes 4-24
4.3.1 Clearing Quenes 4-24
4.3.2 Saving Queries 4-25
4.3.3 Retneving Queries 4-25
4.4 Running Quenes 4-26
4.4.1 Input and Report Selection Screen: Choosmg Input 4-27
4.4.1.1 Linked 4-27
4.4.1.2 Nonlmked 4-27
4.4.1.3 Linked Nonlinked 4-28
4.4.2 Input and Report Selection Screen: Choosmg 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 Descnption 5-7
5.2.6 Deleting a Query from the Member List 5-8
5.3 Allowmg 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 Quenes 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 Returmng a Facility List to a Query 6-11
6.3.2 Getting a Dun & Bradstreet Corporate Profile 6-12
64 Looking at a GO Names Query 6-13
6.4.1 Modifying a GO Names Query 6-15
6.5 FOIA concerns: Excluding Nonreleasable data from GO Names 6-17
6.6 Running a GO Names Query 6-19
6.7 Viewmg a Query Report 6-19
6.8 Exiting GO Names 6-20
6.9 Summary 6-21
Chapter 7. Conducting a Search Using GO MenuA 7-1
7.1 Introduction to GO MenuA 7-1
vi IDEA User’s Guide October 22, 1996
-------
7.2 Getting Started 7-1
7.3 Using GO MenuA 7-4
7.3.1 Editing GO MenuA Quenes 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 Wnte 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 Downgrading your Secunty Level 8-20
8.8 Excluding Databases from Standard Reports 8-21
8.9 Specifying Report Destinations 8-22
8.10 Adding Comments to a Query 8-26
8.1 1 JOB, ROUTE & DD Statements 8-27
8.12 Running a Keyword Query 8-29
8.12.1 Viewing the Query Report 8-30
8.13 Exiting Keywords 8-31
8.14 Summary 8-32
Chapter 9. Managing Keyword Queries and the ISPF Editor 9-1
9.1 Introduction to the ISPF Editor 9-1
9.2 Keyword Quenes 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 Lmes From One Query to Another 9-10
9.3.2 Combmmg Quenes 9-1 1
9.3.3 Deleting Excluded or Non-Excluded Lines 9-1 1
9.3 4 Clearing a Query from the ISPF Editor 9-li
9.3.5 Scrollmg Data 9-12
9.4 Summary 9-14
Chapter 10. IDEA Standard Reports 10-I
10.1 Choosing a Standard Report Format 10-1
10.1.1 Report 1A 10-1
Contents V ii
-------
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
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 FF1 (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 lÀ Elements 10-26
10.1.1.12 RCR (RCRIS) Report lA Elements 10-28
10.1.1.13 TRI Report LA Elements 10-30
10.1.2 Report lB 10-31
10.1.2.1 AFS Report lB Elements 10-34
10.1.2.2 CER (CERCLIS) Report lB Elements 10-39
10.1.2.3 DCK (Civil Docket) Report lB Elements 10-46
10.1.2.4 DUN (Dun & Bradstreet) Report lB Elements 10-50
10.1.2.5 ERN (ERNS) Report lB Elements 10-52
10.1.2.6 FF1 (FFIS) Report LB Elements 10-60
10.1.2.7 FIN (FINDS) Report lB Elements 10-61
10.1.2.8 LST (Contractor Listing Docket) Report lB Elements 10-62
10.1.2.9 NCD (NCDB) Report lB Elements 10-65
10.1.2.10 OSH (OSHA) Report lB Elements 10-69
10.1.2.11 PCS (PCS) Report lB Elements 10-75
10.1.2.12 RCR (RCRIS) Report lB Elements 10-78
10.1.2.13 SET (SETS) Report lB Elements 10-83
10.1.2.14 TRI (TRIS) Report lB 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 Printmg 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-S
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-14
11.3 Controlling USR Report Output 11-24
11.3.1 Restnctmg Report Data 11-24
11.3.2 Sorting the Report Data 11-26
viii IDEA User’s Guide October 22, 1996
-------
11.3.3 The Summary Line 11-28
11.3.3.1 Statistical Functions 11-30
11.3.3.2 Controlling Where Summary Information Appears 11-34
11.4 Requesting a USR m the Keyword Interface 11-35
11.4.1 Report Design Considerations 11-36
11.4.2 Preparing a Query in the ISPF/PDF Editor 11-37
11.4.3 Adding the USR Request to the Query 11-39
11.5 Running Quenes and Viewing Reports 11-40
11.6 Printing Reports 11-43
11.7 Saving Reports 11-48
11.8 Exiting Reports 11-49
11.9 Summary 11-49
Appendix A. Access and Security Procedures for IDEA A-I
A. 1 Attachments A-4
Appendix B. Database Descriptions B-I
B.1 AFS B-i
B.2 CER B-2
B.3 DCK B-3
B.4 DUN B-4
B.5 ERN B-5
B.6 FF1 B-6
B.7 FIN B-7
B.8 LST B-8
B.9 NCD B-9
B.1O PCS B-10
B.!! RCR B-il
B.12 SET B-12
B.13 TRI B-i2
B.14 ZIP B-13
Appendix C. Data Elements in IDEA Shadow Files C-i
C.i AFS-AIRS Facility Subsystem Data Elements (9/96) C-2
C.2 CBG-Census Block Group Data Elements (9/96) C-3
C.3 CER-CERCLA Information System Data Elements (9/96) C-15
C 4 CRM-Crmunai Docket Data Elements (9/96) C-26
C.5 DCK-Enforcement Docket Data Elements (9/96) C-27
C.6 DUN-Dun & Bradstreet Data Elements (9/96) C-28
C 7 ERN-Emergency Response Notification System Data Elements (9/96) C-29
C.8 FF1-Federal Facihties information System Data Elements (9/96) C-32
C.9 FIN-Facility Index System Data Elements (9/96) C-33
C.10 LST-Contractor Listmg Docket Data Elements (9/96) C-33
C.! I NCD-National Compliance Database Data Elements (9/96) C-35
C.12 OSH-Occupational Safety & Health Admimstration Data Elements (9/96) C-37
C.13 PCS-Permit Compliance System Data Elements (9/96) C-41
C.I4 RCR-RCRA Information System Data Elements (9/96) C-44
C.15 SET-Site Enforcement Tracking System Data Elements (9/96) C-48
C.16 TRI-Toxic Chemical Release System Data Elements (9/96) C-49
C.17 ZIP-Census Bureau’s Zip Code Data Elements (1/96) C-SO
Contents ix
-------
Appendix D. Error Messages for the Keyword Interface D- I
Appendix E. The Structure of the IDEA Shadow Databases E- 1
E.1 Skeletons of the IDEA Databases E-I
E.2 How the underlymg structure affects your Select critena E-12
Appendix F. Accessing the User’s Guide Online F-I
F.1 Accessing the User’s Guide m Bookmanager F-I
F.2 Printing Additional Copies of the IDEA User’s Guide F-S
Glossary X- 1
Index X-9
x IDEA User’s Guide October 22, 1996
-------
Tables
3-1. Program Function Keys and PC/LAN SNA Gateway Key Map 3-1 1
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 m the Menu Interface 4-3
4-2. IDEA Standard Reports 4-29
5-I. Library Member List Commands 5-4
6-I. Library Member List Commands 6-3
6-2. Lme Editmg 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. Lme Editmg Commands 7-8
8-1. Library Member List Commands 8-3
8-2. JSPF 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 m IDEA Shadow Databases 11-2
11-2. Library Member List Commands 11-38
11-3. Lme Edit Commands 11-40
11-4. Commands for Navigating Reports 11-43
C-i. Descriptions of Data Types C-2
E-1 Levels of Hierarchy in IDEA Shadow Databases E-13
Tables Xi
-------
xii IDEA User’s Guide October 22, 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 Retneval 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 ISO 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 Pnmary 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. Mam 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-li
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 Retneval 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-I. Interface Selection Screen 5-1
5-2. Input Library Selection Screen 5-2
5-3. Member List Screen 5-3
5-4 Edit Screen 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 Descnption 5-8
5-8. Member List Screen - Deleting a Member 5-9
5-9. READY Screen - RACF Commands 5-10
6-I. 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-1 1
6-7. Dun & Bradstreet Keywords 6-13
6-8. A GO Names Query in the Edit Screen 6-14
6-9. GO Names 1 Facility Count - - No Corporate Profile 6-18
6-10. Query Status Screen 6-19
6-11. Report 1A in Browse Mode 6-20
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. Noncomphance Cntena 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-1 1
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 Decodmg 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-23
8-10. SDSF Output Queue Screen 8-24
8-11. SDSF Output Queue Screen - “Command Issued” 8-25
8-12. SDSF Output Queue Screen - Print Destination Changed 8-25
8-13. Query Status Screen 8-30
8-14. Report 1A (Browse Mode) 8-31
8-15. Example Keyword Query. 8-32
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. IDEA Standard Report 1A 10-3
10-2. AFS Report 1A Elements 10-4
10-3. CER (CERCLIS) Report LA 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 LA Elements 10-15
10-7 FF1 (FFIS) Report 1A Elements 10-17
10-8. FIN (FINDS) Report 1A Elements 10-18
10-9. LST (Contractor Listing Docket) Report IA Elements 10-19
10-10 NCD (NCDB) Report 1A Elements 10-21
10-1 1 OSH Report lA Elements 10-24
10-12 CS Report IA Elements 10-26
10-13. RCR (RCRIS) Report 1A Elements 10-28
xiv IDEA User’s Guide October 22, 1996
-------
10-14. TRI Report IA Elements 10-30
10-15. IDEA Standard Report lB 10-33
10-16. AFS Report lB Elements 10-34
10-17. CER (CERCLIS) Report lB Elements 10-39
10-18. DCK (Civil Docket) Report lB Elements 10-46
10-19. DUN (Dun & Bradstreet) Report lB Elements 10-50
10-20. ERN (ERNS) Report lB Elements 10-52
10-21. FF1 (FFIS) Report lB Elements 10-60
10-22. FIN (FINDS) Report lB Elements 10-61
10-23. LST (Contractor Listing Docket) Report lB Elements 10-62
10-24. NCD (NCDB) Report lB Elements 10-65
10-25. OSH (OSHA) Report lB Elements 10-69
10-26. PCS (PCS) Report lB Elements 10-75
10-27. RCR (RCRIS) Report lB Elements 10-78
10-28. SET (SETS) Report lB Elements 10-83
10-29. TRI (TRIS) Report lB 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 lA 10-98
10-36. Prmt 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 m USR 11-3
11-2. IDEA User SpeciuIed 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 Formattmg 11-13
11-7. Simple USR with Title and Formatting 11-14
11-8. USR request using “Across” function 11-15
11-9. TRIS Release Data “Across” the Page 11-16
11-10. Example of Use of ENFACTS 11-18
11-il. Using the Text function 11-20
11-12. TEXT INFO Command 11-21
11-13. Top of Decoding Tables List 11-22
11-14. TRIS Facility Ids with SIC codes 11-23
11-15. TRIS Facilities with voted SIC codes 11-24
11-16. RESTRICT Keyword Section 11-25
11-17. Use of Restrict Keyword 11-26
11-18. Sorting by Reporting Year, then Chemical 11-27
11-19. Sorting by Chemical, then Reporting Year 11-28
11-20. Using COUNTO on the Summary Line 11-31
11-21. USR With Request for Summary Information 11-33
11-22. USR Output With Summary Information 11-34
11-23 Example USR With Detail Line Suppressed 11-35
11-24. Library Selection Screen 11-37
Figures XV
-------
11-25. Member List Screen 11-38
11-26. Example Query m the ISPF Edit Screen 11-39
11-27. Query Status Screen 11-41
11-28. Viewing a USR in Browse Mode 11-42
11-29. A “Complete” USR 11-44
11-30. Prmt/Save Parameter Screen 1 1-44
11-31. SDSF Primary Option Menu Screen 11-46
11-32. SDSF Output Queue Screen 1 1-46
11-3 3. SDSF Output Queue - “Command Issued” Screen 11-47
11-34. SDSF Output Queue - Print Destination Changed Screen 11-48
A-i. 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 and Compliance
Assurance Memorandum A-9
A-S. Attachment 2(d) - Sample EPA Contractor Employee Memorandum A-JO
A-6. Attachment 2(e) - Sample State Enforcement Agency Employee
Memorandum A-I I
E-1. AFS Database Skeleton E-3
E-2. CBG Database Skeleton E-3
E-3. CRM Database Skeleton E-4
E-4. DCK Database Skeleton E-4
E-5. DUN Database Skeleton E-5
E-6. ERN Database Skeleton E-5
E-7 FF1 Database Skeleton E-6
E-8. FIN Database Skeleton E-6
E-9. LST Database Skeleton E-7
E-1O. NCD Database Skeleton E-8
E-11 OSH Database Skeleton E-8
E-12. PCS Database Skeleton E-9
E-13 RCR Database Skeleton E-1O
E-14. SET Database Skeleton E-lO
E-15. TRI Database Skeleton E-lI
E-16. ZIP Database Skeleton E-l I
E- 17 Select Cnteria consulting two databases E- 12
E-18. User-specified Report--Two facilities E-14
E-19. Select cntena limited to FFIS E-l5
E-20. User-specified Report--One facility E-16
E-2 1. Select cntena with parentheses reversed E- 17
E-22. Query Status Screen--No facilties E-l7
F-i. 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 pnnung F-S
F-7 EPA Print Routing Screen F-6
xvi IDEA User’s Guide October 22, 1996
-------
Chapter 1. Introduction
This chapter provides a bnef descnption of the background of IDEA, its intended
use, and the basic features of the IDEA User’s Guide.
1.1 Backjiround of the IDEA System
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 mvolved in
EPA enforcement or comphance 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 identif mg 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 EPA’s top management as an Office
of Enforcement material weakness under the Federal Managers Financial Integnty
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 retneve 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 screemng 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 1 Introduction 1-1
-------
Identif i the Multi-Media Enforcement Profile for a specified facility or company.
• Case Development
• Litigation Support
• Settlement Negotiations
• Enforcement/Inspection Targetmg:
Identify compliance monitonng/enforcement candidates for an industry-specific
enforcement initiative.
Identify comphance monitonng/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 mtended to aid and mstruct users of Integrated Data for
Enforcement Analysis (IDEA) by explaining procedures for accessing the system,
building queries, retneving 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 buildmg
tools. These chapters on query buildmg are modular m design so users can find
enough basic information m 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
mformation on managing libranes, the ISPF editor, and IDEA Reports. IDEA users
1-2 IDEA User’s Guide October 22, 1996
-------
will need to refer to the appendices for access and secunty procedures, detailed infor-
mation on database descnptions, data elements used by IDEA, and error messages.
1.3 Summary
IDEA was developed in response to a defined need for data integration across vanous
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 expenenced users.
It contams detailed information on IDEA ’s design features, query buildmg, and
IDEA reports.
Chapter 1 Introduction 1-3
-------
1-4 IDEA User’s Guide October 22, 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 retnevmg
information and returns it to you in the form of an IDEA report.
When you construct an IDEA query, you select the critena 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 accordmg to its name, location, the chemicals it releases, and other ct -i-
tena 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 cntena are integral to the search?
What criteria can be used to help narrow the search?
Forethought m 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 retneve 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 cntena you set This task can be performed by
Chapter 2 IDEA What it Does & How it Works 2-1
-------
usmg 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 m 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 m Chapter 6, Conducting a Search Using GO Names, allows
you to generate queries m 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 retneve facility
data, including corporate profile data.
GO MenuA, covered m Chapter 7, Conducting a Search Using GO MenuA, is a utility
m the Keyword Interface that allows you to build a query m 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, descnbed 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 m 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 by 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
retnevals.
IDEA currently provides access to data from the following databases:
AFS AIRS Facility Subsystem (Office of Compliance),
2-2 IDEA User’s Guide October 22, 1996
-------
CERCLIS CERCLA Information System (Office of Solid Waste and Emergency
Response),
CRM Cnminal 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 Information 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 S ’czion 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 descnptions of these databases
and how to reach user assistance for each. Appendix C, Data Elements en iDEA
Shadow Files provides a list of the data elements m the IDEA copies of the databases.
Chapter 2 IDEA What it Does & How it Works 2-3
-------
Note: When analyzing data retneved 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 .
2.3 How IDEA Processes Oueries
The pnncipal utility of IDEA is its ability to access and integrate enforcement data
on facilities across EPA program office databases m addition to data systems mam-
tamed by other government agencies.
Suppose you are mterested in retrieving data on facilities classified as current Signif-
icant Noncompliers and Violators m 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 Pnority Violators m RCRIS (the
RCRA Information System tracks hazardous waste handlers under RCRA). IDEA
will locate facilities that meet these cntena m all three databases.
Figure 2-1 below illustrates the way IDEA mtegrates data. The intersection repres-
ents those facilities that are current Significant Noncomphers 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 retneve the
noncompliers from each database separately and compare the three hsts to determine
the common set of facilities. Searchmg 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 October 22, 1996
-------
There are three data retneval (or input) options available to you in IDEA.
• Linked,
• Nonlinked, and
• Linked Nonlinked.
If you choose the Lmked 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 retneve
data on facilities withm 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 quenes, IDEA selects facilities that meet query cntena 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 retneval 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
Intersection
Figure 2-1. IDEA Data Integration
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 cntena. When the example above is run,
IDEA searches RCRIS, PCS, and FINDS for facihties that are Generators, Major
Dischargers, and located m Mame, respectively. See Figure 2-2 for an illustration of
this step.
Note: Nonhnked quenes ignore FINDS. When the example query is run as a Non-
linked query, IDEA does not search the FINDS database. Since there is no
mechamsm for comparing these facilities without FINDS, Boolean connectors
are not applied to Nonhnked searches; so Figure 2-3, Integration Process
applies only to Linked and Linked Nonlmked quenes.
23.2 Integration Process
When IDEA mtegrates facility data, a two step process is involved. Once IDEA has
gathered the local IDs for the facilities selected in Linked and Linked Nonhnked
queries, it uses FINDS to locate EPA IDs for them. Then IDEA apphes 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 cntena. In order to meet all of
the query cntena, a facility would have to be a RCRA Generator AND a PCS Major
Discharger AND be located m Maine according to FINDS. Refer to Figure 2-3
below.
Databases
Groups of
Local IDs
Selected
Figure 2-2. Initial Facility Selection
2-6 IDEA User’s Guide
October 22, 1996
-------
Groups of
Local IDs
Selected
Local IDs
Converted
to EPAJDS
(where
possible)
Boolean
Connectors
Applied
Figure 2-3. Integration Process
Note: FINDS serves dual purposes m 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 Nonhnked queries, it is also used as a cross-referencmg mechamsm
to locate the EPA IDs of facilities selected from other databases.
2J.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
-------
1. - QUERY STATUS SCREEN - -
2. COMMAND
3. 16:12:45.49 - 796 Faci ties s&ected ano ir FfJDS
4. 16:12:45.49 - 3077 Facilities selected and not in F: DS
5. Counts (percentages), by database, of facilities selected but
6. not present in INOS:
7. P05 59 8) RCR 248 ( 1)
8. ..... FI ; ( 0)
9. Press ENTER to continue, END to reLurn to sLdrt
Figure 2-4. Query Status Screen
This screen always shows the title (line 1), the COMMAND prompt (line 2), the
number of facilities that were selected from the query (lines 3 & 4), the names of the
EPA databases that were searched and some statistics about the search for each of
them (lines 7 & 8), and directions on how to continue (line 9). The information
shown on this screen depends on the kind of query that was run (i.e., Linked, Non-
linked, and Linked Nonlinked). The display for lines 3 to 8 varies for each type of
data retrieval or input. Figure 2-4 is the result of running the query Linked Non-
linked and contains all of the elements of the QUERY STA TUS SCREEN.
2.3.3.1 Linked Queries
Because IDEA only reports on facilities that are in FINDS for this type of query,
Linked queries generate a QUERY STA TUS SCREEN that shows the number of
facilities selected and in FINDS (line 3) as well as the “counts” and “percentages” for
each database (lines S to 8) searched. “Counts” is the number of facilities that
matched at least one of the query criteria for that database but were not selected
because they are not linked in FINDS.
For example, 596 facilities that are Major Dischargers in PCS were excluded from the
number of facilities that will be reported on because they are not in FINDS.
Although Linked queries do not report on facilities that are not in FINDS, you can
get reports on these facilities by running the query Linked Nonlinked. The “percent-
ages” (noted in parentheses to the right of the number of counts) indicate the total
percentage of facilities that met at least one of the query criteria for that database but
were excluded due to poor FINDS links. Eight percent of the facilities that are
Major Dischargers in PCS were excluded from the query because they were not in
2-8 IDEA User’s Guide October 22. 1996
-------
FINDS. In other words, the 596 facthties 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 cntena. Of the 92 percent of PCS facilities evaluated (approximately 6854
facilities), 796 of them meet all the query cntena. Seven hundred and mnety-six facil-
ities that are Major Dischargers in PCS and in FINDS are also Generators in RCRIS
and located in Mame.
2J.3.2 Nonfinked Queries
Nonhnked queries ignore FINDS; therefore, the QUERY STATUS SCREEN for
these quenes 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, Nonlmked quenes select more facili-
ties than the other query types When the example query is run Nonhnked, 282,495
facilities are selected as opposed to 796 for Linked and a total of 3873 (those in
FINDS and not in FINDS) for Lmked Nonlmked.
2.3.3.3 Linked Non/inked Queries
Since these quenes are combinations of Linked and Nonhnked quenes, the QUERY
STA TUS 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).
23.4 Detailed Data Retrieval
Before presenting you with a report containing data on the facilities selected from the
query, IDEA must first retneve the data. The amount of work IDEA has done up to
now is small m comparison to the work it will do in the next step when it performs
the detailed data retneval. This process differs for Linked, Nonhnked, and Linked
Nonlinked queries.
Chapter 2 IDEA What it Does & How it Works 2-9
-------
EPA.IDs of facilities
for which report(s)
will be generated
Sample FINDS
Pointers
EPA
Databases
EPA.ms of
facilities selected
and in FThDS
EPAJD =MED000791681
RCR.JD = MED000791681
PCS.ID = ME00022764
PCS.]D =ME00022861
AFSID =2303100002
TRLID = 03906PRT WROUTE
Figure 2-5. Detailed Data Retrieval
2.3.4.1 Linked Queries
For Linked quenes, IDEA retneves data only for the facilities that are in FINDS and
meet the query cnteria. As illustrated m 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.
Dunng the detailed data retneval, IDEA pulls up report data for the facility from
each of the databases to which it is linked m FINDS, whether or not these databases
were searched as part of the initial facility selection.
( Doc1 ni ) ( NCDB) Cc1 cLIs ) (svrs
2-10 IDEA User’s Guide
October 22, 1996
-------
2.3.4.2 Nonlinked Queries
Figure 2-5, Derailed 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 Nonlmked, the initial facility selection would take place, as illustrated in
Figure 2-2, then the report data would be retneved separately for the facilities
selected from RCRIS and PCS.
2.3.4.3 Linked Non/inked 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 Lmked query (i.e., are not m
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 facthty. For the Nonhnked facili-
ties, IDEA only retneves 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 retneved.
It is very easy to misinterpret the mformation obtained through IDEA. The data
accessed by IDEA are useful subsets of information on each program’s performance.
To amve 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 retneval dates, and discrepancy reconciliation proc-
esses that cannot be duplicated or replaced by IDEA.
The selection cntena utilized by IDEA is based on EPA’s subjective assessment of the
types of information that will be most useful m 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 cnteria 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 vanous
objective cntena 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 appropnate 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 ongmal data-
bases. When analyzing data, consult EPA Headquarters, regional enforcement
program, state personnel, and nonautomated information sources.
2-12 IDEA User’s Guide October 22, 1996
-------
Chapter 3. Accessing’ IDEA on the EPA IBM Mainframe
This chapter instructs users on how to access EPA ’s IBM mainframe computer and
descnbes the hardware/software requirements needed for this access. Additionally,
users are mstructed on how to access IDEA.
3.1 Mainframe Access
IDEA runs on EPA’s IBM mamframe computer at the National Computer Center
(NCC) in Research Tnangle Park (RTP), 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 gam access to the IDEA system, and an appropnate
hardware/software link to the mainframe.
For detailed information on gaming access to the IBM mainframe, see the EPA
Guide to NCC Services , issued by the Office of Admimstration 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 Processmg (ADP) Coordinator. ADP Coordinators estab-
lish accounts, register users, and control the expenditure of time sharmg 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 afithate who does not
have a user ID, contact your EPA representative to obtain one. If you do not
have an EPA contact, call The National Technical Infonnation Service (NTIS) at
703-487- 4630.
3.1.2 Obtaining IDEA Authorization
Once you have a mainframe user ID, you will need to request additional authon-
zation to gain access to IDEA. To do so, submit a memorandum to the Office of
Comphance (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/Software Considerations
To communicate with the IBM mainframe computer at the NCC, you must have one
of the following:
• IBM 3270 or compatible tetminal
• DEC VTIOO 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 mamframe 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 October 22, 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
mstructions for gaining access to the mainframe.
I. 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 3270 EMULATION SCREEN or MAINFRAME/3090 ACCESS
SCREEN, select the MOD 2 -SCREEN SIZE - 24 x 80 option by pressmg 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 mstructed to simultaneously press
the left and keys to switch from the LAN to Mainframe
Mode. Refer to Section 3.2, Logging on to EPA ’s Mainframe for additional
mstructions on keyboard mappmgs
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-lme cables and a full-screen session is
already established. A hardwired terminal does not require dialing through the tele-
phone lines or using the A UTOMAXX WORKSTA TJON MENU to access the NCC.
To estabhsh 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-
Dlayed. If it is not, press the or 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 hsted in Seaion 3.1, Mainframe Access
Chapter 3 Accessing IDEA on the EPA IBM Mainframe 3-3
-------
NETMAIN U.S. E.nvironmerz& Protection Agency Date: 87/27/93
• Menu System True: I0 36:34
• Tenninal: 12315311
Loginode: MZSDL NQ
Please enter selection or coniiiand and then press ENTER.
1. INFORNIATION News Alerts and User Memos
2. SYSTEM MENU System Selection Menu
3. MAIL EPA Electronic Mail for 3270
4. APPLICATiONS PA Applications Menu
5. TNTFP-AGEN V Trter—AgPncy Anplirations Menu
6. PUBLIC Public Access Applications Menu
WARNING: The use of this computer is for official Government business only.
Unauthorized use of this computer is a criminal offense under Title 18
Juiited States Code, Section 641, and may subject violators to a fine of
u.p to S10 ,000, or imprisonment of up to 18 years, • r both.
coniiiand ---
• Optional Quick Logon - USERID
PASSWORD ==>
El /F13=Hel p F5/F 17—Refresh F12/F24=Cancel
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 October 22, 1996
-------
• Your communication software should emulate a VT100-type terminal.
• Commumcation parameters should be 7 data bits, 1 stop bit, even panty 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 Loj ’in on to EPA’s Mainframe
Once you have estabhshed a link to EPA’s mainframe, it is necessary to “logon” to
the system. These mstructions 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
-------
NETMAIN U.S. Environmental Protection Aqency Date: 07/27/ 3
Men System Time: iO:3 :34
Terminal: T23i5311
Logmode: M2SDLON
Please enter selection or conrnand and ther press ENTER.
1. INFORMATION News Alerts and User Memos
2. SYSTEM MENU System Selection Menu
3. MAIL EPA Electronic Mail for 3270
::H:. 4. APPLIcATIONS EPA Applications Menu
5. I TEP.-AGENCY Inter-Aqency Applications Menu
6. PUBLIC Public Access Applications Menu
WARNING: The use of this cornpute is for official Government business on’y.
Unauthorized use of this compute- is a criminal offense under Title 18
United States Code, Section 641, and may subject violators to a fine of
up tc $10,080. or imprisonment of up to 10 years, or both.
on and ===> ISO
Optional Quick Logon - USERID ===
PASSWORD >
F1/F13=Help F5JF.17.=:Refresh F12/F24=Cancei
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
key to move the cursor to the USERID prompt. Type your three char-
acter user ID and press the key again to move the cursor to the PASS-
WORD prompt. Type your password and press .
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 October 22, 1996
-------
- EPA2 TSO/E LOGON - PASSWORD EXPIRED
PF1/PFI3 ==> Help PF3fPF15 ==> Logoff PAl Attefltion PA2 ==> Reshow
E1 ’ TER LOGON PARAMETERS BELOW: RACF LOGON PARAMETERS:
USERID ===>
PASSWORD === NE DASSWORD ===>
PROCEOURE SEPATSO GROUD IDENT ===
ACCT NMBR ===> ** .
FIMAS == IES ’P BIN NUMBER ===>
SIZE SVSOJT DEST —>
COMMAND ==>
ENTER AN “S ’ BEFORE EACH OPTION DESIRED BEt OW
-NOMAIL -NONOTICE -NOSUMMARY -CANCEL
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
. 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 .
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.
1’ype the required information, using to move between fields. Press
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.
ICH700 0II PQG LAST ACCESS AT 14:25:24 ON TUESDAY. AUGUST 10. 1993
1KJ56455 1 PO LOGON IN PROGRESS AT l5:22:4 O AUGUST :10, 1993
93/08/06: DATA MANAGEMENT SMS CONVERSION (REVISED) - SEE NEWS ALERTS
93/08/04 NATURAL V224 IMPLEMENTATION DEFERRED - SEE NEWS ALERT2
93/07/30: A LIST OF RECENTLY RELEASED EPA MEMOS - SEE NEWS ALERT4
93/07/27: MVS/ESA, JES2, TSO/E AVAILABLE FOR TEST - SEE NEWS ALERT1S
93/07/19: SAS/C REL 5..SBC AVAI ABLE FOR TEST SEE NEWS ALERT7
93/07/07: IMPLEMENTATION OF RACF PROTECTALL - SEE NEWS ALERTS
93/07/06: UMAIL FOR RACF PROTECTALL VIOLATIONS - SEE NEWS ALERT9
93/06/25: HWOM FIMAS CODE DEACTIVATED (REVISED) - SEE NE !S ALERT3
93/83/23: JUSD DATA SETS BEING UPDATED - SEE NEWS ALERTI
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 S YSTEM
3-8 IDEA User’s Guide October 22, 1996
-------
SCREEN (see Figure 3-5 wifi appear once your terminal has been linked to the
EPA mainframe.
NETMAIN U.S. Enviranmenta Protect on Agency Date; 67/27/93
Menu System Time: 10:36: 4
Terminal: 12315311
Logmode: .M2SDLCNQ
Please enter selection or conrand and then press ENTER.
1. INFORMATION News Alerts and User Memos
2. SYSTEM MENU System Selection Menu
3. MAIL EPA Eiectroni.c Mail for 3270
4. APPLICATIONS EPA Applications Menu
5. INTER-AGENCY Inter-Agency Applications Menu
6. PUBLIC Public Access Applications Menu
WARNING: The use of this con puter is for official Government business on’y..
Unauthorize.d use of this computer is a criminal offense under Title 18
United States code 4 Section 541 . and may subject violators to a fine of
up to 510,000, or imprisonment of uo to 10 years, or both.
Coimnand === ISO
Optional Quick Logor -. USERID ===
PASSWORD ===>
FI/F13=Relp F5ff17=Refresh F12/F24 Cancel
Figure 3-5. U.S. Environmental Protection Agenc Menu System Screen
2. At the COMMAND prompt, type TSO (for Time Sharing Option) and press the
key to move the cursor to the USERID prompt. Type your three char-
acter user ID and press the key again to move to the PASSWORD
prompt. Type your password and press . A logon confirmation message
and System News Alert messages wifi appear (see Figure 3-6), followed by a
READY prompt.
It 7 0 8OiIPQG LAS1 ACCESS Al l4:25: 4 ON...T.UESDAY, AUGUST 10, 1993
1K356455 1 PQG LOGON IN PROGRESS Al 15:22:45 ON AUGUST 10, 1993
93/88/05: DATA MANAGEMENT SMS CONVERSION (REVISED) - SEE NEWS ALERT8
93/08/04: NATURAL V224 IMPLEMENTATION DEFERRED - SEE NEWS ALERT?
93/07/38: A LIST OF RECENT:LY:RELEASED EPA MEMOS - SEE NEWS AL [ R14
93/07/27: MVS/ESA , JES2 , TSO/E AVAILABLE FOR TEST - SEE NEWS ALERT1O
93/07/19: SAS/C REL 5.50C AVAI .BLE FOR TEST - SEE NEWS ALERT7
93/07/07: IMPLEMENTATION OF RACF PROTECTALL - SEE NEWS ALERTS
93 /0 /06: UMAIL FOR RACF PROTECTALL VIOLATIONS - SEE NEWS ALERT9
:93 6/25: .HWDM FIMAS CODE DEACTIVATED (REVISED) - SEE NEWS ALERT3
93/03/23; JUSO DATA SETS BEING UPDATED - SEE NEWS ALERTI
READY
Figure 3-6. TSO News Alert/READY Screen
Chapter 3. Accessing IDEA on the EPA IBM Mainframe 3-9
-------
3.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 line of
the screen. The cursor will be positioned at the PASSWORD prompt, and you wifi
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.
EPA2 TSO/E LOGO PASSWORD NOT AUTHORIZED
PF1/°F13 ==> Help PF3/PF15 Logoff PAl ==> Attention PA2 ==> Reshow
ENTER LOGON PARAMETERS BELOE: RACE LOGON PARAMETERS:
USERID
PASSWORD === NEW PASSWORD ===>
PROCEDURE === GROUP IDENT ===>
ACCT NMBR
FIMAS BIN NUMBER ===>
SUE SVSOUT DEST
COMMAND
ENTER AN LIS BEFORE EACH OPTION DESIRED BELOW
•-NOMAIL -NONOTICE -NOSUF 1ARY -CANCEL
Figure 3-7. TSO LOGON Screen
3.3 Keyboard Mappinjis
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 October 22, 1996
-------
33.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 Mallhframe 3270 PF key mapping. The followmg (Table 3-]) shows the
default key command and descnption for both IBM 3270 termmals (PF keys) and
most Personal Computers (F keys) with a LAN connected to the SNA Gateway.
Table 3-I. Program Function Keys and PC/LAN SNA Gateway Key Map
Command
Description
IBM 3270 Ter-
nunal Keys
PC/LAN SNA
Gateway Keys
ISPF HELP
Displays information about the current
screen
PFI/PF13
Fl
SPLIT SCREEN
Splits the screen into two ISPF ses-
slons
PF2/PF14
F2
END
Saves changes and returns to the pre-
vious screen in edit mode. Returns to
the previous screen in browse mode
PF3/PF15
F3
RETURN
Returns directly to the previous
Primary Option Menu
PF4/PFI6
F4
RFIND
Repeats the previous FIND
command
PF5/PF17
F5
RCHANGE
Repeats the previous CHANGE
command m edit mode
PF6/PFI8
F6
UP
Scrolls Up by the amount set at the
SCROLL or COMMAND prompt
PF7/PF19
F7
DOWN
Scrolls Down by the amount set at the
SCROLL or COMMAND prompL
PF8/PF2O
F8
SWAP
Moves the cursor from one screen to
the other in the split screen mode
PF9/PF21
F9
LEFT
Scrolls Left by the amount set at the
SCROLL or COMMAND prompt
PF1O/PF22
FlO
RIGHT
Scrolls Right by the amount set at the
SCROLL or COMMAND prompt
PF11/PF23
Fli
RETRIEVE
Moves the cursor to the first input
field on the screen and retrieves the
last command entered
PFL2/PF24
F12
Table 3-2 contains the same mformation for computers usmg Crosstalk’ and Kermit 2
instead of SNA Gateway.
I WIC-developed Crosstalk XVI TCP XTK command file, with VTLOO emulation and on
2 WIC-developed Kermit-MS 2.30 TCP KMK take file, with VTIO2 emulation and on
Chapter 3 Accessing IDEA on the EPA IBM Mainframe 3-11
-------
Table 3-2. Program Function Keys and Crosstalk/Kermit Key
Command
Descnpuon
IBM 3270
Terminal
Keys
Crosstalk /
Kermit Keys
ISPF HELP
Displays information about the current
screen.
PF1/PF13
Fl or
Keypad I
SPLIT SCREEN
Splits the screen into two ISPF ses-
sions
PF2/PF14
F2 or
Keypad 2
END
Saves changes and returns to the pre-
vious screen in edit mode Returns to
the previous screen in browse mode.
PF3/PF15
F3 or
Keypad 3
RETURN
Returns directly to the previous
Primary Option Menu
PF4/PFI6
F4 or
Keypad 4
RFIND
Repeats the previous FIND
command
PF5/PF17
F5 or
Keypad 5
RCHANGE
Repeats the previous CHANGE
command in edit mode
PF6/PF18
F6 or
Keypad 6
UP
Scrolls Up by the amount set at the
SCROLL or COMMAND prompt
PF7/PF19
F7 or
Keypad 7
DOWN
Scrolls Down by the amount set at the
SCROLL or COMMAND prompt
PF8/PF2O
F8 or
Keypad 8
SWAP
Moves the cursor from one screen to
the other m the split screen mode.
PF9/PF21
F9 or
Keypad 9
LEFT
Scrolls Left by the amount set at the
SCROLL or COMMAND prompt.
PF1O/PF22
FlO or
Keypad 0
RIGHT
Scrolls Right by the amount set at the
SCROLL or COMMAND prompt
PF11/PF23
Fl or
Keypad.
RETRIEVE
Moves the cursor to the first mput
field on the screen and retrieves the
last command entered
PF12/PF24
F2 or
Keypad *
3.3.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 withm IDEA. These keys are noted in Table 3-3.
Table 3-3 (Page 1 of 2). Program Attention Keys
Command
IBM 3270 Terminal
Keys
PC/LAN SNA Gateway Keys
Attn - Reset Keyboard
right
Attn - Attention Interrupt
+
pressed simultaneously
Enter - Transfers data to the
computer
Numeric key pad or right
Delete Character
<9>
Delete End of Field
3-12 IDEA User’s Guide October 22, 1996
-------
Table 3-3 (Page 2 of 2). Program Attention Keys
Delete End of Line
Home - Move Cursor to first
input field
+
keys
pressed simultaneously
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
left +
Reshow -Reshow the last full
screen image displayed by
ISPF
3.4 Enterinj the IDEA System
1. To access IDEA, type IDEA and press at the READY prompt. This
step will take you to the IDEA WELCOME SCREEN (see Figure 3-8).
- - - ----——- -——- -——-- iDE eip Menu -- -- --— - -- - --
COMMAND SCROLL === CSP
****************** Welcome To
*
1111111 DODUC EEEEEE AAAA
0 .0 E A A
* •. 1 0 0 EEEE AAAAAA *
* I D 0 E A A
* 11111111 0000D EEEEEE A A
*
Enter one of the following or the COMMAND line *
*
* 0 - Database Status H - Helpline Info U - User Documentation
*
* Or., enter the name of the SEWS ALERT you wish to read, or just *
* press ENTER to continue with IDEA.
Scroll down for more ************************* *********************** **** **
@@1BRER 930389.1025 Report 1B/R RIS Data Error from June 92 CLM
•@@CERPRB 930269.1 131 ERCLIS was unavailable 8 Feb until 11250 Feb RXG
@ALTBACK 930269.1128 Alternate interface is bacl RXG
ALERT O1 920522.0749 News Alert Navigation GWL
ALER102 9205e8.15e5 March1992 IULAUsers Advisory Meeting GWL
NEWSTUFF 920522.8751 New IDEA Features / Enhancements . WL
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 564-2475
Monday-Friday 9:00am to 5:00pm (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 . The IDEA DATABASE STA TUS 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.
iDEA Database Status Screen
OP 1AND
The databases are current as of the following dates:
AFS Ju 18, 1995 AQG Jul 17, 1995
Jul 10, 1995 CRM Jul 18, 1995
DCK Jul 19, 1995 DUN Jul 17, 1995
ERN Jul 1, 1995 FF1 Feb 14. 1995
FIN Jul 17, 1995 LST Apr 17, 1995
N D iun 30, 1995 OSH Jul 18. 1995
PcS Jul 17, 1995 RCR Jul 17, 1995
SET Jul 18, 1995 TRI Jul 15, 1995
ZIP May 12, 1993
Press ENTER to return to the main menu
Figure 3-9. Database Status Screen
To return to the IDEA WELCOME SCREEN, press .
3-14 IDEA User’s Guide October 22, 1996
-------
• To obtain HELPLINE INFORMATION, type H at the COMMAND prompt
and press . 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 .
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., ALERTO2) and press ,
To return to the IDEA WELCOME SCREEN, press .
• From the IDEA WELCOME SCREEN, press to continue IDEA query
processing. The INTERFACE SELECTION SCREEN will be displayed. At this
screen, you indicate how you want to commumcate with IDEA and what basic
type(s) of quenes you wish to develop. To learn more about quenes and how
IDEA integrates data, refer to Chapter 2, IDEA What it Does & How it Works.
3.5 Loj iiw 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 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).
Y3u 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 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 to exit the IBM Mainframe.
Chapter 3 Accessing IDEA on the EPA IBM Mainframe 3-15
-------
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 entenng commands and navigatmg withm 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 October 22, 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 Catejiories
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.
INTERFACE SELECTION SCREEN
COMMAND ===>
IDEA currentl.y supports two interfaces with which to construct and
run queries. They are described briefly below..
K - KEYWORD-VALUE Interface: >> lISPF_likeu.full_power interface;
F >> Maxin im flexibility and complete database variable access;
> Uses the POE text editor to construct keyword/value queries;
> Interface for runninq facility nan searches (‘GO NAMES”).
A - MENU A interface: >> Uses selection menus and pop-i p windows;
>> Provides option/value lists 1roinwt ich to build cueries;
>> Easier to use, but less flexibility than KEYWORD-VALUE.
NOTE: in order to use this interface., you imist be able to use
your terminal s PE Key equivalents for ‘End’, ‘Up’, and “Do ii’.
::. See the IDEA Neipline for more information on PF Keys).
Enter interface Option === A
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 ofthe six categories follow.
Date; 7/27/ 3 IJEA Jse : UID
Create/Add a query by enterin an “S’ next to
— Location . More: +
— Pollutants .
— Industry .
— Noncompflance .
. — Enforcement .
Run Ouery .
— Ciear Ouery
— Save uery
— Retrieve Query
PFK1/13: HELP
PFK3/15: END
PFK7/19: Page Up
K8 ‘ € e Do r
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 October 22, 1996
-------
NONCOMPLIA NtE
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).
ENFOR CEMENT
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 Prionties
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-I) 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
Mode
Description
END PF3/PF15
Edit &
Browse
Returns to the previous screen
RETURN
PF4/PFL6
Edit &
Browse
Returns direciiy to the previous Primary Option Menu
UP PF7/PF19
Edit &
Browse
Scrolls up by the amount set at the SCROLL or
COMMAND prompt.
DOWN PF8JPF2O
Edit &
Browse
Scrolls down by the amount set at the SCROLL or
COMMAND prompt
To maneuver the
cursor around
IDEA screens
Use arrow keys for all directions, use key to
move the cursor from prompt to prompt; use
to move the cursor to the top-left prompt
To reset the key-
board when it locks
up
key, key with R; right key, or
key dependmg on your keyboard configuration
4.2 Usinji Menu Categories to Form Oueries
IDEA quenes are formed in the Menu Interface by selectmg categones from the
MAIN MENU SCREEN. Each category contams 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 . This
sequence is used whenever you want to make a selection from any IDEA Menu.
After you choose a category, the main wmdow for that category will pop up in front
of the ongmal MAIN MENU SCREEN that was shown in Figure 4-2. The fol-
lowing sections will provide you with a detailed descnption of each of the six query-
buildmg categones and their pop-up wmdows. Since the procedure is basically the
same for all six categones, a step-by-step presentation will only be given for Location.
Sections 4.2.3, Pollutants Category through 4.2.7, Facilny Status Category provide
details regarding the other five categones.
4.2.2 Location Category
Let’s say that you want to focus your search on the EPA-regulated facihties 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 to move the cursor over the underscore
mark to the left of the category. Then type S followed by .
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 October 22, 1996
-------
nate: 07/27/93 IDEA Use : UID
- . - Location -.
Finished? (v/N): N Clear? ( i/N):
Create/Add a query Date Elements Values
S Location
— Pollutants
— Industry Region IN — - — (Range of Regions)
— Noncompliance = — — — (individual Regions)
Enfor:ement State =
— Facility Status ip Code =
— State/County o e = — / —
/
_/ —
/
/
Run Q erv
— Clear Query
— Save Query
— Retrieve Query
P Kl /l3: HELP
PFK3/i5: END
PFK7/19: Page Up
PFK8/20: Page Down
Figure 4-3. Menu Interface with Location Category
This pop-up window gives you several options for choosing the geographic region
you will search:
• You can perform a search of EPA Regions by entering the two-digit EPA
Region number as a range, e.g., Regions 02-05, or as individual Regions.
Always remember to include a zero before Regions 1-9.
• Since EPA Regions cover several states, IDEA also lets you search by state or
states; simply enter the two-character state abbreviation(s) used by the Postal
Service.
• If you would like to be more specific, IDEA gives you the option of con-
ducting a search by county or counties. To do so, type in the State county
code in the appropriate spaces. The State county code is a five-position code
consisting of the two-letter state abbreviation followed by a three-digit
number. Follow the example below to learn how to fmd county codes.
• Finally, you can narrow your search even more by using five-digit ZIP Codes.
2. If you would like to see the list of states in each of the EPA regions, use
to move the cursor to one of the fields reserved for entering an Individual Region
code. Type a? over the underscore mark and press . 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
-------
Date: 07/25/94 IDEA User: WLW
. -------- Location
rin sned? (V/N) N C ear? (V/N) N
Create/Add a query ! Data Elements Values
s Location
Poliutan:s . - --
— Industry I Renion Codes
Noncomplianc I A 2-digit code which rerresents an PA Regional Office
— Enforcement
— Facility Sta Finisned? (V/N): N Next Coce : —
I S Code Description
— O Boston, MA (CT, MA, ME, NH, RI, VT)
2 Ne : York, NY (NJ, NY, PR, VI)
— Run Query I — 03 Philadelphia, PA. Dc. GE. MD, PA, VA. WV
— Clear Query I 04 Atlanta, GA AL, FL, GA. KY, MS. NC, SC, TN)
— Save Query — 05 chicago, L CIL, IN, MI, MN, OH, WI)
Retrieve Due — OS Dallas, TX CAR. LA, NM, OK, TX) :E
PFKI/13: HELP — 07 Kansas City, flU (IA, KS. MU, NE)
PFk3/15: END — 8 Denver, CO (CO. l IT, ND, SD, UT, WY).
PFK7/19: Page U I — 0 Sar Francisco, CA (AS. AZ, CA, CM, GD, HI, NV)
PFKB/20: Page D — 10 Seattle. WA (AK, ID , OR, WA)
Figure 4-4. Location Category with Region codes
3. Once you are in the window shown in Figure 4-4 , you can select Individual
Region(s) on which to focus your search. Use 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 to get back to the
FINISHED? (Y/N) prompt, type a V over the default value, and press .
(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 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 . (Remember: PF7 scrolls the
page up and PF8 scrolls the page down.)
5. To select a county code, use 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 or type a? over the underscore mark of
the county code then press . 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 October 22, 1996
-------
Date: 08/15/93 . -.
. t Counzy Codes
Finis A 2-character State Code and 3-d git Count\! Code
Create/Add a query ! Data
s Location Finisned? (Y/N): N Next Code:
• — Pollutants S Code Descript on
• — Industry Regic -
— Noncompliance — 00001 ADAMS, COLORADO
— Enforc.emer t State 00003 ALA! ’IOSA, COLORADO
— Facility Status Zip C — O005 ARAPAHOE, G:OLORADO
State 00007 ARcHULETA, COLORACO
00009 BACA, COLORADO
— 00011 BENT. COLORADO
— 00013 BOULDER, COLORADO
00015 CHAFFEE, COLORADO
• — Run Query — 00017 CHEYENNE, COLORADO
— Clear uerv . s 00019 CLEAR CREEK. COLORADO
Save Query . — 0821 CONEJOS, COLORADO
Re:trieve Query . — 00023 COSTILLA. cOLORADO
PFIU/13 : HELP . — O025 CROWLEY, COLORADO
PFK3/15: END . — 0.0027 CUSTER, COLORADO
PFK7/19: Page Up . — O029 DELTA, COLORADO
PFKB/20: Page.Down s 00031 DENVER, COLORADO
Figure 4-5. Location Category with County Codes
6. The easiest way to include a county code in your query is to use 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
If you have finished your selections, you can now exit the pop-up window.
Use or to move the cursor to the FINISHED? (YIN)
prompt and type V followed by .
8. Let’s say you decide that a two-county search is too large for your purpose. So
ycu 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
V next to the CLEAR? (YIN) 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 pop-up window, but only some, you would have to over the entries
you no longer wanted in the Location category window.
Chapter 4. Conducting a Search Using the Menu Interlace 4-7
-------
Date: 08/lô/93 IDEA User: UlD
• . Location
Finisnea? (Y/N): N. Clear V/N): v
Create/Add a query Data Elements Values
S Location -
— Pollutants
• Industry Region IN - — (Range of Regions)
— Noncompliance — — — — — (Individual Recions)
— Enforcement State =
— Facility Status Zlp Coue =
State/County Code = O / 019 CLEAR cREEk, COLORADO I
O / 031 DENVER COLORADO
/
Rui Query
— Clear Query
Save Query
— Retrieve Query
PFKI/:13 : HELP
P1K3/.15: END . -
PFK7/19: Page Up
PFKO/20: Page Dowr
Figure 4-6. County Codes and Clear command
9. Now enter the ZIP Code in the appropriate spaces and . 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 fmd the right
one anyway!)
10. If you are satisfied with the location criteria that you selected for your query, use
or to move the cursor to the top of the pop -up window that
you are in, type V next to the FINISHED? (Y/N) prompt and press .
— helpful hint
To exit a pop-up window, type V at the FINISHED? (YIN) prompt, followed
by .
11. From here you wifi 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 October 22, 1996
-------
Date: 8/i6/93 IDEA User: UID
create/Add a query by entering an s next to:
Location . More: —
IPonutants . VOL have created a query, using the following crter a:
— Indust y . - -
Noncornpliaice - Location:
— Enforcement . Zip odes(s): 8 2O2
— Facility Status
Run Quer\’ . ... . . .: :::
Clear Query
— Save Query
Retrieve Query
PFK1R3: HELP
PFK3R5: END
PiK7/19: Page Up
PFK8/28: Paqe Down
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 Interlace 4-9
-------
In this example if you were to enter anything m addition to the ZIP code of the city
of Denver (80202), for mstance the State name (CO), you would receive more facility
names than you mtended (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
m the following manner. Fmd any facility in Colorado State OR EPA Region 8 OR
Denver County OR ZIP Code 80202. As you can see, the number of facilities m 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
i•— helpful hint
To select a menu category, use to move the cursor over the underscore
mark to the left of the category. Then type S followed by .
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 wmdow
looks like Figure 4-9:
Figure 4-8. The map of EPA Region 8
4-10 IDEA User’s Guide
October 22, 1996
-------
Date 08/U3/93 IDEA User: U1C
- - Pollutants -.
in shed? v/N): N lear (Y/N): N
Create I Systems Data Elenents Values
Loc :
s o’ AFS (Air) Pol 1 utant Codes =
— md I Pollutant Ciass fication = — —
— Non I Attain/Non-Attain = — — — —
— Enf ! Pollutant con l. Status = — — — —
— Fac PCS (Water) Meas.fviol. Parameters =
Violation Types = — —
I RCRIS (Solia Waste) Waste codes =
Waste Aint. (in ton) IN ________ ________
Waste process =
I TRI Toxic Release) C iemica Codes =
— Run Release Medium
le I Reporting Years = — — —
— Say Release Amo nt (in lbs.) IN ________ ________
Ret
FFK1/13: HELP
FFK3/15: END
PFK7/l9: Page Up
PFKB/20: Page Down . ..
Figure 4-9. Menu Interface with Pollutant Category
As you can see by the systems listed at the left side of the box, the Pollutant Cate-
gory lets you conduct your search according to air, water, and solid waste pollutants
as well as toxic releases. While this category pop-up window is used in much the
same fashion as the Location pop-up box, it does have some differences. The fol-
lowing paragraphs will help you maneuver through the Pollutant pop-up window and
use it to create a query.
The AFS (Air) system allows you to perform a search according to:
• Pollutant Codes - A code of up to five characters that represents a certain
pollutant or group of pollutants (e.g. BZ= Benzene, OACID = Organic Acids).
You can choose two per search. Enter? for a multi-page listing of pollutant
codes.
• Pollutant Classification - A code of up to two characters that indicates the amount
of actual or potential emissions from a facility. You can choose two per search.
Enter? for a listing of classification codes.
• Attainment/Non-Attainment - A one-character code that indicates whether a plant
emits a criteria pollutant for which its county is in non-attainment. You can
enter up to four per search. Enter? for a listing of codes.
Chapter 4. Conducting a Search Using the Menu Interface 4-11
-------
• 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.fViol. 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 hstmg 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 charactenstics (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 nght of the word IN, enter the lower value. On
the underscore spaces to the nght of those, enter the higher value. Do not add
commas m 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 contamers, 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 cntena:
• Chemical Codes - Nme-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 October 22, 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 hsting of the codes.
• Reporting Years - Enter a four-digit year. You can enter up to three years. Type
? for a hst of the available years.
• Release Amount (in lbs.) - This entry requires you to enter a range of contaminant
amounts. On the underscore marks to the nght of the word IN, enter the lower
value. On the underscore spaces to the nght 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? (YIN) prompt, followed by
.
4.2.4 industry Category
r— helpful hint
To select a menu category, use to move the cursor over the underscore
mark to the left of the category. Then type S followed by .
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
-------
Date: O8/ 3/93 IDEA User: UlD
. ---------- ----------- Industry
I Finished? (Y/N): N Cear? (Y, N): N
CreatejA d a query by I Elements Values
— Location . I ——-
— Pollutants . SIC Codes iN - (SIC Ranae) I
s Industry . = (mdv SIC)
Noncompliance
— Enfor emert . ------•• - -
— Facility Status
— Run Qierv
Clear Query •
— Save uery
— Retrieve Quer ’
P K1./13: HEL
P K3/15: END
PPK7/i9: Pane Up
PFKBf2O: Page Dowr
Figure 4-10. Menu Interface with Industry Category
In order to use the Industry Category for your query, you must enter the SIC for the
range of industries or industry you wish to search. Let’s say, for example, that you
want to find EPA-regulated facilities that are engaged in the metal mining industry.
Since this is a broad sector of industry, your first step is to use 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 .
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
. In this case, it is MINING (see Figure 4-11).
4-14 IDEA User’s Guide October 22, 1996
-------
.Date 08/23/93 -—---—-- -
I - SIC Codes c Ranges)
I A code made up of two individual SIC codes, to identify
Create/Add a query I broader industry categories (i.e., industry ranges)
— Location I Finished? Y/ 1) H Next Value: mining________________
— Pollutants ! S Code Description
s Indu try .1. --
— Noncompliance 1 — 1 0191 A cult .u ’al Production - Crops
— Enforcement — 0211,0291 Agricultural Production - Livestock
— Facility Status — 0711,0783 Agricultural Services
0811,0851 Forestry
I 0912,0971 Fishing,i-hiriting, and trapping
1011,1899 Metal Mining
I — 1111,1112 Antracite Mining
— 1221 1241 Bitunnnous coal and lignite milling
Run Query 1311,1389 Oil and Gas extraction
• — Clear Query 1411,1499 Mining and quarrying of nonmetallic mine
• — Save Query — 1521,1542 Building construction - gen. contractors
Retrieve Query I * 1611,1629 Construction other than building constru
PFK1/13 HELP — 1711,1799 Construction - special trade c•ontractor:
PFK3/15: END L * 2011,2899 Food and kindred products
PFK7/18: Page Up I — 2111,2141 Tobacco manufacturers
PF 8/20: Page Down I — 2211,2299 Textile mill products
Figure 4-11. Industry Category: Searching for SIC Range of Mining Industry
A list of SIC ranges that contain the word “mining” will appear. Select “Metal
Mining” and type V at the FINISHED? (Y/N). IDEA wifi take you back to the
Industry pop-up window with your selection of SIC range for “Metal Mining” (see
Figure 4-12).
Chapter 4. Conducting a Search Using the Menu Interface 4-15
-------
Date: 08/23/93 . - - - - -
- SIC Codes (Ranges)
A code made up of two indivduai SIC codes, to iuentity
Create/Add a query broaoer industr y categories (i.e., industry ranges)
* Location Finished? (YIN): V Next Value: _______________________
Po iu .tants S Code Descniotion
S Industry
— Noncompliance s 10i1.109g Metal Mining
— Enfo’cement — 1111,1112 Antracite Mining
— Facility Status — 1221,i2 1 Bituminous coe. and lignite milling
— 11 j40 Mln1nC and quarrtlng of nonneL ’1c mine
Run Query :
Clear Query . ... ...
— Save Query I .
Retrieve Query
PFK I/13: HELP
PFK3/15: END
PFK7/19: Page Up
PFK8/20: Page Down
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 and type? next to it followed by
. A list of general SICs will pop up. You could type in LEAD at the
NEXT VALUE: prompt and press . 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 V at the FINISHED? (Y/N) prompt, followed by
.
4.2.5 Noncompliance Category
4-16 IDEA User’s Guide October 22, 1996
-------
r— helpful hint
To select a menu category, use to move the cursor over the underscore
mark to the left of the category. Then type S followed by .
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.
Date: 8/2 /93 IDEA User: UI
- . Noncompliance (NC)
• ! Finished’ (Y/N : N Clear? (Y/N : N
• Create/A ! Law s) System Date Elements Values
Locat -.•-.••..-.. -
_Pollu 2 or n ore All 2 or More Laws: NC — SNC —
— Indus cAA AFS in Violation —
s Nonco ! Significant Violation Status —
— Enfor ! EPA Compliance Status = — — — —
— Facil ! Significant Violation Flagl =
CWA PCS Reportable Noncompliance —
Significant Noncomp’iance —
Current Year 1st Quarter = — -- - — -
Noncompliance: 2nd Quar er =
3rd Quarte
— kun Q ! 4th Quarter =
• — Clear ! RCRA RCRIS Unresolved Violations (Exc. High P) —
— Save ! Unresolved High Priority Violations —
— Ret’i FIFRA NCDB FIF A: NC — SNC —
PFK1/13: TSCA TSC .A NC — SNC —
PFK3/l5: ! EPCRA 313 EPcRA (313): NC — SNC —
PFKJ/19:
PFK8/20: Page Down
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 cntenon to search for all facilities in violation of CAA.
Type S to activate this critenon.
• Significant Violation Status - Use this cntenon to search for all Significant Viola-
tors under CAA. Type S to activate this cntenon.
• 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 Flagi - 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 cnterion to search for all facility
noncomphers under CWA. Type S to activate this criterion.
• Significant Noncompliance - Use this option to search for all Significant
Noncomphers under CWA. Type S to activate this cntenon.
• 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 Prionty violations. Type S to activate this cntena.
• Unresolved High Priority Violations - Use this criteria to search for all facilities
classified as High Pnonty 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
cntena to search for all facilities classified as NCs or SNCs under FIFRA, TSCA
or EPCRA 313. Type S to activate the cntena.
4-18 IDEA User’s Guide October 22, 1996
-------
helpful hint
To exit a pop-up window, type V at the FINISHED? (Y/N) prompt, followed by
.
4.2.6 Enforcement Category
r helpful hint
To select a menu category, use to move the cursor over the underscore
mark to the left of the category. Then type S followed by .
The Enforcement pop-up window, displayed in Figure 4-14 , provides you with an
array of options to use in your query formation.
D . Enforcement
- ! Finished? Y/N : N Clear? (Y/N.):
Lawcs) .:Systern Data Eiements Values
— ! 2 or more Al ] NOVS — Administrative Action Ji dicial Action —
Date: IN f/to/f
— ! CAA AFS Nat’l Act. Type =
— Enf. Act. Date IN / — / — to — / — I —
s ! ERCLA cERCL:s Enf. Act. Type =
— Act. Start Date IN — / — / — to — / — / —
Act. Crnpl. Date IN — / — / — to — / — / —
eWA P S Enf. Act. Code = — — —
Enf. Act. Type = —
Enf. Act. Date IN / — I to — / — /
RCRA R RIS •Enf. Act. Type =
— Respons. Agcy. = — —
— ! Enf. Act. Date IN / — / — to — / — / —
— TSCA/ NCDB Statute Viol. = — —
— ! FIFRA/ Enf. Act. Type = — —— —
P ! EPCRA 313 Enf. Act. .:Date IN — / — I — to — / — I
P ! ALL. LAWS DOCKET Law _______ _______ _______
P (Jud.Only) Date Filed IN — I — / — to — / — I —
P ! Date Concluded IN — / — •/ — to — / — / —
Figure 4-14. Menu Interface with Enforcement Category
As indicated by the laws listed on the left hand side of the box, the Enforcement
category allows you to form a query according to enforcement actions taken under
CAA, CERCLA, CWA, RCRA, TSCA, FIFRA, or EPCRA 313. The Enforcement
pop-up window is managed much like the others, with a few exceptions. Most
notably, this category allows you to choose a range of dates for the enforcement
action you are seeking. When entering a date, always use the pattern mm/ddyv
Chapter 4. Conducting a Search Using the Menu Interface 4-19
-------
(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), Admmistrative Action, or Judicial Action, and speci-
fying the date of the action by entenng a range of dates in the appropnate spaces.
Under CAA, you can conduct a search according to:
• Nat’l Act. Type - a code of up to two characters mdicatmg 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 cntena:
• 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 m 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 critena:
4-20 IDEA User’s Guide October 22, 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 listmg 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 all drawn from
the same database, NCDB. When you choose to search this database (by searchmg
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 cntena available regardmg these
statutes are:
• Enforcement Action Type - a code of up to three characters that indicates the type
of enforcement action for which you are searching. 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 appropnate 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 three of these codes. Type? to see
a listmg.
You can also search the docket by the date that any enforcement action was filed or
concluded.
helpful hint
To exit a pop-up wmdow, type V at the FINISHED? (YIN) prompt, followed by
.
4.2.7 Facility Status Category
Chapter 4 Conducting a Search Using the Menu Interface 4-21
-------
i— helpful hint
To select a menu category, use to move the cursor over the underscore
mark to the left of the category. Then type S followed by .
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.
Date: 08/0 . raci1it Statis
Finish? (Y/N : N Clear (Y/N : N
Law(s) System Data Elements Values
create/Add I
Locatlo I CM AFC Class A SIPfWSPS/I’1ESHAP —
— Po luta Air Program =
— Industr I Source Classification — —
— NOflcOTTh ! CEROLA CERCLIS NPL Status = — — —
— Enforce I Site Classification — ——
s Facilit incident Type = — —
FEDFAC (A ] 1) FF 1S Feoera Agency —
CWA PCS Active, Major Discharger —
Fdciiitv Type — —. —.
industrial Class. = — — —
Ownership Type —
— Run Que .L RCRA RcRIS Transprter Universe -
— Clear Q I Fully Reg. Gen . Univ. —
— Save Qu Land Disposal Universe —
— Retrie Incinerator Universe —
PFK1/13: H I Storage/Treatment Uni. — 1
PFK3/15: E ! Small Generator Uni. —
PFK7/1O: P 1 TScA/FIFRA/ NcDB Facility Funct on = — —
PFKB/20: P EPCRA 313
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 October 22, 1996
-------
o 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:
o 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.
o 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.
o Incident Type - A one-character code that mdicates whether an incident was an oil
spill. There are only two codes; type ? to see a listing.
To retneve 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.
Concermng CWA, you can build a query along the following lines:
o Active, Major Discharger - Use this cntena to search for all Active, Major Dis-
charges under CWA. Type S to activate this cntena.
o 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.
o 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.
o Ownership Type - A three-character code that indicates whether a facility is feder-
ally, pnvately, 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 umverses are: transporter, fully regulated
Chapter 4 Conducting a Search Using the Menu Interlace 4-23
-------
generator, land disposal, incmerator, 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 hstmg of the codes.
, helpful hint
To exit a pop-up window, type V at the FINISHED? (Yf N) prompt, followed by
4.3 ManaRinhj Oueries
The key to managmg your query is the four options at the bottom left of the MAIN
MENU SCREEN (above the PF key mdicators, see Figure 4.2). Like the categories
above, these commands work by typing S to the left of the desired command followed
by .
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 nght of the screen announcmg that
the Query has been cleared. To remove the message from the screen, press
.
2. To clear all the data elements or values m a category pop-up wmdow, select that
category and use and/or to place your cursor at the CLEAR?
(Y/N) prompt. Type V followed by and the window will be cleared.
3. To erase one data value or element that you have chosen, select that category and
over the undesired characters.
4-24 IDEA User’s Guide October 22, 1996
-------
4.3.2 Saving Queries
The SAVE QUERY command wifi 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 wifi appear at the lower left telling you the “Query
has been saved as....” To remove the message from the screen, press .
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.
Date: 08/10/93 IDEA User: UlD
Oreate/ I Query Retrieval
Lo a ! ! re +
Poll ! S Name Description
-— Indu
_Nonc NEW2
— Erifo ! — OSHA1 this is just a test
Faci TEST?
TEST3
I TEST4
_Run I
Clea!
Save!
s Retr!
PFKI/13
PFK3/15
PFK7/19 I
PFK8/20 I
Figure 4-16. Query Retrieval Screen
Retrieval is carried out b 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
. A small box will show up to ask CONFIRM QUERY DELETION
(YIN). Type V to confirm your delete command or type N to cancel it, then press
.
You can update the name and/or the optional description of a saved query by typing
a U next to it and pressing . You may then change the name on the first
line, or 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 until you are satisfied with your modifications.
4.4 Running Oueries
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 , the
screen will change to the title screen shown in Figure 4-17.
— Caution
Be sure not to push until you make all of your choices on this screen;
otherwise, wifi instruct the system to begin running your query.
Date: 07/27/93 IDEA User: UI.D
Create/Add a query by entering an S next to:
— Location . More: +
— P:ollutants . You tiave created a query, usinq the following criteria:
Industry .
— Noncompliance . Location:
• — Enforcement . . State(s): CA
— Facility Sta
Input and Report Selection ! 743 921
Input
V LINKED integrated Data ! iance
S Run Query ! NONLIN D Non-integrated Data iance
— Clear Query lance
— Save Query Report
Retrieve Que I
PFK1/13: HELP V 1A Report 1A
PFK3/15: END lB Report lB
PFK7/l9 : Paqe U — 2 Report 2
PFK8/20: Page B I SU*IARY Report
Figure 4-17. Input and Report Selection Screen
4-26 IDEA User’s Guide October 22, 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 Nonhnked. When you choose Linked, Nonlinked, or both, you are tellmg IDEA
what type of information to retneve: data that has been mtegrated using FINDS
(linked data), non-integrated data from the separate databases (nonhnked data), or a
combination of the two.
4.4.1.1 Linked
After you specify select cntena and mdicate linked data, IDEA searches for a facility
or facilities that meet those cntena. For each facility retneved, IDEA tnes to find the
identification number for that facility m the Facility Index System (FINDS). Linked
is the default; that is, if you do not choose Nonhnked or Linked Nonhnked, IDEA
will retneve data that has been integrated using FINDS. Linked data may not be
complete since FINDS does not contain data for all facthties.
4.4.1.2 Non/inked
If you choose nonhnked data, IDEA will not use FINDS to integrate information.
The information retneved by IDEA will come from different individual databases
indicated by your query. The benefit of choosing Nonlmked 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.
r•— helpful hint
Since nonlinked data was retneved 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 Nonlhzked
You can combme Linked and Nonlinked in your query to get both integrated and
nonintegrated data. Type an S next to both Linked and Nonhnked 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 cntena and are linked using
FINDS. The second section will consist of the facilities that meet your cntena within
each of the particular databases but have not been linked usmg FINDS. Data in the
first section will not be repeated in the second.
r helpful hint
Since nonhnked data was retrieved from different mdividual 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 Nonhnked 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 mtegrated data.
4.4.2 input and Report Selection Screen: Choosing Reports
After choosing a Linked or Nonhnked 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, 1B, 2, or Summary. Short descriptions
of the formats are given m 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 October 22, 1996
-------
Table 4-2. IDEA Standard Reports
There are currently four standard IDEA report formats 1A, I B, 2, and Summary
REPORT IA
A brief report of individual facilities Organized by the linked database, IDEA displays the
facility name and database idenLifier, location and other business information, noncompliance
or violation status, and enforcement mformation
REPORT lB
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 comphance 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 format, Report 1A; you can then over-
write it and select other reports. Once you are satisfied with your selection, press
to instruct IDEA to begm runmng your query.
When finished, IDEA will present you with the QUERY STATUS SCREEN. An
example of a QUERY STA TUS 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
-------
- QUERY ST TL;S SCREEN -
COMMAI D
13:34:38.34 Facilities selected and in FINDS
Counts (percentages), by database, of facilities selected but
excluded because they were not present in FINDS:
AFS 60 ( 35) PCS 1342 ( 70)
R R 0 ( 0) TR.I U C 0)
i FIN 0 ( 0 :;. . .. .
Press ENTER to continue, END to return to start
Figure 4-18. Query Status Screen
— Caution
4.4.3 Viewing the Query Reports
If you press 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, PF1O to scroll left, and PF11 to scroll right. You can also type in SW at the
COMMAND prompt to switch to the next report. Lpon reading the last report gen-
4-30 IDEA User’s Guide
October 22, 1996
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 STA TUS
SCREEN.
-------
erated, entering SW at the COMMAND prompt will bring you back to the first
report.
BROWSE - Report: IA Complete--- MAX 008054 LINE 08800880 COL 001 880
COMMAND
Issue con nand RINTO to print, or SAVE to save to dataset.
TO OF DATA ******* *******.*******************
1 U.S. ENVIR.O MENTAL PROTEC
INTEGRATED DATA FACILITY-SPECIFIC CO
FINDS Id; C0D098706795 Fac. Name; JACK PINE MINING CO/BLACK EAGL City: I
Ad ress 2 MI SW ON CHICAGO CREEk RD Zip:
RCRIS Handler Id: C0D000706796 Year Pio.Eval. No.NOVs 1.10.
Name; JACK PINE MINING CO BLACK EAGLE MILL CY92 0 0
TSD Facility Status: HPV? NO DYQ3 0 0
OwnerOperator Type: P Exist. Date: C
PCS :Permit No: c00028797 Issue Date: 1987/04 Year All .Viols Eff.Viois Inspe
Fac. Name: JACK PINE MINING CO/BLACK EAGL CY92 0 0
Active Minor Discharger Cv93
Expired Date: 1992/06 “94 8
÷ + + ±-.--------+ + - -
Figure 4-19. Report lÀ.
4.5 Exitinji the IDEA Menu Inter face
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
INTERFACE SELECTION SCREEN.
• Use the PF4 key to return to the OFFICE OF ENFORCEMENT DA TA INTE-
GRA TION 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 descnbes the IDEA Menu Interface. The Menu Interface is the simples
means of retnevlng information with IDEA. The convenient pop-up windows allow
you to form quenes according to your search cntena from different databases inte-
grated by IDEA.
The Menu Interface has six categones: 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 retneve the data and build an efficient query.
You can manage your quenes 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,
retneve, or even clear your query.
4-32 IDEA User’s Guide October 22, 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.
— Caution
When working in the iNPUT LIBRARY SELECTION SCREEN, do not press
until you are finished editing the options on the screen; otherwise,
IDEA will take you to the next screen. If is pressed accidently, press
PF3 or type END at the COMMAND prompt and press to return to
the INPUT LIBRARY SELECTION SCREEN.
INTERFACE SELECLON SCREEN - -- -.
cOMMAJ 1D
IDEA currently supports two interfaces with thich to construct and
run queries. They are described briefly below.
• K - KEYWORD-VALUE interface: > “ISPF-iike” full-power interface;
Maxin im flexibility and complete database variable access;
>> Uses the PDF text editor to construct keyword/value queries.;
>> Inte face for runnin g facility name searches (“GO NAMES”).
A - MENU A Interface: >> Uses selection menus and pop-up windows;
>> Provides option/value lists from which to build queries;
>> Easier to use 1 but less flexibility than KEYWORD-VALUE.
NOTE: .T1 order to use this interface, you imist be able to use
your terminal’s PF Key equivalents for “End”, “Up’, and “Down”.
See the IDEA Helpline for n re information on PF Keys).
Enter Interface Option ==> K
Figure 5-1. Interface Selection Screen
Chapter 5. Managing Libraries 5-1
-------
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.
- -. iI PUT LIBRARY SEIcTION SCREEN --88j2 / 3 17 . 3(RXG)
: COMMAND ===>
L 4 brary Name === UiDACCT.QJER ;.SPE S
I , \ —- .-. L1D
For
Directory Elocks ===> 008
Figure 5-2. Input Library Selection Screen
Ifyou want to form a new library, type over the default library name with the name
ofyour 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 ofthe 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 STATU S(Shr/New/Old) prompt.
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.
5-2 IDEA User’s Guide October 22, 1996
-------
By changing the status to OLD, you will be given exclusive access to the library. If
you are creati ng 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 LIBRAR Y 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.
MEMBER LIS UIDACCT.QUERY.SPECS ROW I TO 20 OF 2
. COMF4AND ===> S cROLL ===> PAGE
USE “B,E,R,U,D” LEF T OF NAME.
NAMF CHANGED OESCRIPT:ON I D
JERRYMEM 93e912.1421 Training Example PQG
. KODAK 938912.1421 Kodak Corporation (class example) PQG
NC 930912.1423 Non-Compli ance Lqgic PQG
NEWBATCH 9309 12. 1423 Batch Job PQG
. PEBMAIL 930912.1423 Mail Message from PEB PQG
RCRAHP 930912.1424 RCRIS Logic POG
. RHONE 930912.1424 RhoT )e-Poulenc Example PQG
RPTTEST
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,
whiLh 5 111 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 d , 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 m your library like a book on a shell 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) will 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 ManaRin2 Queries UsinR 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 COM MAND 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 Browse/Read the query; no editing possible.
E (or S) query Edit/Select an existing query or create a new one in
the editor.
R query Rename the query.
U query Update the query descnption.
D query Delete the query from the MEMBER LIST.
5.2.1 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 October 22, 1996
-------
1 . To create a new query (member) press < Tab > or < Home > to move the cursor
next to the COMMAND prompt ofthe MEMBER LIST SCREEN (see
Figure 5-3).
2. Type E (or S) and < Space > , foflowed by a name of up to eight letters or
numbers for the query you are creating (e.g., F NEWQUERY). Special characters
or spaces cannot be used when writthg the member name.
3. Press < Enter > and the EDIT SCREEN will appear (see Figure 5-4) in which
you can construct a query.
EDIT ---- UIDACC.QUERV.SPECS(NEWQUERY) - Oi. 0E3 COLUMNS 001 872
COMMAND ===> SCROLL === PAGE
. - ?** * ***************************** TO ’ 0 DATA
I I fi ll : . • • • • . .
I I . . . : . . ;: . .
h u ll .. . . . . .. . .
*k***Sc *k* *** ** * * ***t**k * **k* *** * RflTTflK I flR fl Tt *k*t*** **********1c* k t***
Figure 5-4. Edit Screen
522 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 query (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 BRO J ’VSE SCREEN (see Figure 5-5 will be displayed.
Chapter 5. Managing Libraries 5 -5
-------
BROWSE -- U1DACOT.QUER \.SPE OS(GLAXO) -. - ------- LINE 80009000 CCL 001 080
COMMAND ==> SCROLL == > PAGE
TOP OF DATA
/* 930819 1115 Names Searct found 25 names. /
f’ Name: CtAXO */
OUTPUT REPORT IA
It’IPUT LINKED
SELECT FIN.EPID=
C0D11405175 8 , .f:* GALAXIE AUTO BODY (RCR */
1NDC5895.6723, f GALAXIE CORP (RCR) /
LA 0071941439 , / GALAXIE MARINE SVC INC (R R) */
MNDG85668946, :./.* GALAX!E AUTO SALES (R R) /
NC0065655599, 1* GLAXO INC. (RCR) */
NC010174 8215, / GLAXO INC. (RcR) */
NC 0981920762 , f GLAXO INC (RCR) */
NCD982094526, / GLAXO, INC. (RCR) *f
NCD982094997, i GLAXO. INC. (RCR) *1
NCD 86223 51, / GLAXO, INC. (PCS /
NCD991278730 , /* GLAXO INC. R R) .:*/
NCIflEA14O4O5, /* GLAXO INC (AFS) */
N30051077251. / GALAXIE CHEMICAL CORP (RCR) /
NJD981 882819, / GALAXIE COLLISION INC (ROR */
NYt 981132392, R GALAXIE CLEANERS , INC. R R) *1
TX0045586450, /* GALAXE BOAT WORKS (R R ) */ ______
Figure 5-5. Browse Screen
5.2.3 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 .
2. An existing query may also be edited by typing E or S and the member name on
the COM MAND line and pressing .
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
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 October 22, 1996
-------
2. Type R (see Figure 5-6> and you will be in position to type over the existing
name. Use to erase any undesired characters.
3. When you are satisfied with the new name, press and the member
name will be updated with the new name. Remember that you may not use
special characters or spaces in query names.
MEMBER LIST UIDACCT.QUERY.SPECS ROW I TO 20 OF 29
Mt4AND === SCROLL ===> 3 AGE
USE ‘ B,E,R ,U,U” LEFT OF NAME.
NAME CHANGED DES RIPTION ID
newname 930912.14i2. ery•on Alyes.ka Pipelines P.QG
ATLANTA 930912.1414 Test Example for Region 4 Training P00
CARRIER 930912.1414 Query on Carrier Corporation PQG
CHEVRON 930912.1414 Query on Chevron Corp FOG
COMPLY 930912.1414 compliance Logic for Cut/Paste PQG
DOCKET 930912.1414 Docket Logic P00
PUNS 930912.1414 in :& Bradstreet Inf rmaeion PQG
FEDEX 930912.1419 Memo to P 1CC P00
FINDUMP 930912.1419 Program for doing Finds PQC
GAYLORD 930912.1419 Query for Gaylord Corporation P. G
GLAXO 930912.1419 Query for Glaxo PQG
F. GONAMES 930912.1421Query on Wake County. NC P00
JERRYMEM 930912.1421 Traimng Example PQG
KODAK 930912.1421 Kodak Corporation (class example) P00
NC 930912.1423 Nor. - Oompiiance Logic PQG
NEWBATCH 930912.1423 Batch Job .•P•QG
PEBMAIL 930912.1423 M& I Message from FEB P 00
•RGRAHP 930912.1424 RCRIS Logic P00
RHONE 930912.1424 Rhone Poulenc.e Example PQG
RPTTEST
Figure 5-6. Member List Screen - Renaming a Member
5.2.5 Writing/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
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 . 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 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 to erase any unwanted characters.
MEMBER LIS T --• UIDAC.CT.OUERY.SPECS ROt! I TO 20 OF 29
COMMAND S2ROLL ==> PADE
USE ‘B .E,R.U,D’ LEFT OF NAME.
NAME CHANGED DESCRIPTION ID
U ALYESKA .9.30912.1412 Type new description here.. PQG
ATLANTA 930912.1414 Test Exanip e for Region 4 Training POD
CARRIER 930912.1414 Query on Carrier Corporation PQG
CHEVRON 930912.1414 Query on chevron Corp PQG
COMPLY 930912.1414 compliance Logic for Cut/Paste PQG
DOCKET 930912J4]4 Docket •L gic PQG
DUNS 930912.1414 Dun & Bradstreet Information PQG
FEDEX 930912.1419t1en to NCC POG
FINDUMP 930912.1419 Program for doing Finds PQG
GAYLORD 930c;12.1419 Query for Gaylord Corporation POD
GLAXO 938912.1419 Query for Glaxo PQG
GONAMES 930912.1421 Query on Wake County .NC PQG
JERRYMEM 930912.1421 Training Example PQG
KODAK 930912.1421 Kodak Corporation (class example) PO.G
• NC 930912.1423 Non—Compliance Logic POD
NEWBATCH 930912.1423 Batch Job PQG
PE MAI 930912.1423 Mail Message from PEB PQG
RCRAHP 930912.1424 RCRIS Logic POG
• RHONE 930912.1424 Rhone-Pou ence Example PQG
RPTTEST
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
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 .
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 . 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 October 22, 1996
-------
MEMBER LIST - LIDACCT.QUER\ SPECS ROW T 20 OF 29
COMMAND ===> SCROLL PAGE
USE 8!R,U .I LEFT OF NAME.
NAME CHANGED DESC iPT1ON ID
U ALVESKA **DELETED**.
ATLANTA 930912.1414 Test Example for Region 4 Training PQG
cARRIE 9389i2.1 14 Query on Carrier Corporation PUG
CHEVRON 30912. 1.414 Query on Chevron Corp PQG
COMPLY 930912.1414 Comp 1 iance Logic for Cut/Paste PQG
DOCKET 930912.1414 Docket togic PQG
BUNS 930912.1414 Dun & Bra street Information PUG
FEDEX 930912. 1419 Memo to NCC PQG
FINDUMP 930912.1419 Program for doing Finds PUG
I GAYLORD 930912.1419 Query for Gaylord Corporation P06
GLAXO 399i2.1419 Query for Giaxo PUG
GONAMES 930912.1421 Query on Wake County.,, NC PQG
JERRYMEM 938912.1421 Training. Example PUG
KODAK 930912.1421 Kodak Corporation (class example) P06
NC 930912.1423 Non—compliance Logic PUG
NEWBATCH 930912.1423 Batch Job PQG
PEBMAIL 938912.1423 Mail Message from PEB PQG
.RGRAHP 930912.1424 RCRIS Logic PQG
RHONE 938912.1424 Rhone-Pouience Example PUG
RPTTEST
Figure 5-8. Member List Screen - Deleting a Member
5.3 Al1owin 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; the 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
-------
ICH7 08 01I UID LAST ACCESS AT 10:51:20 ON PPJDA’;. AUGUST 12 1994
1K356455 1 UID L000N IN PROGRESS AT i8:5b:3 ON AUGUST 12, 1994
I 94/08/li: PRODUCTION SINGLE IMAGE TEST AUGUST.I3TH - SEE NEWS ALEP.T15
94 /08/10 CICS 3 3 0/NCC N C RE L CEMEW AVA L BLE SEE u:
94/08/09: DF/HSM DOWN FOR MAINTENANCE .: SEE NEWS ALERTS
94/08/08: NSC UPGRADE FOR: RTP ,BAYCiT ,Wi (REVISED) . . SEE NEWS ALERT16
94/CO/OD S’trSORT PEL 3 50 .J ILABL T:STING SEF NEWS A EPTI2
94/08/05:A LIST Of RECENTLY RELEASED EPA MEMOS *- SEE NEWS ALERTI
:94/88/84: lEE CENTRAL ENCYCLOPEDIA BATCH DEADLOCKS - SEE .NE ALERT1I
94/08/02: EASYTRIEVE PLUS REL . .ID AVAIL FO TEST - SEE NEWS ALERTS
94/87/18: ADABAS S L VERSION 1.5.1 IMPLEMENTATION - SEE NEWS ALERT1O
94I 7/ii: NDPt; OPERATIONAL DI:RECTIVES MANUAL ONLINE. - SEE..NEWS ALERT3
Q /C, 1 RACF IF1DLEME r: flP TAPE J T SETS SE: MEl S ALEPT2
Q4/Co/ 3 NE RELEAs: 3 A AB. S SQL 5 NEWS A_ERT13
94/C3/ OD NCC CHAtGI k PROFILES TO Fb - N 0 D s:E NE 1S A_E Ti4
94/ 0 5/05: RACF PROTECTALL IMPLEME:NTEDON 11/30/93.. - SEE NEWS ALERT7
94/84/ 06:.NOTIFIcATION OF UP Ot•iING NCC CNANGES - SEE NEWS ALERT4 .
READY . .
.:ALD ‘UID.ACCT.*’ UACC(READ) AUDIT(NONE) NOWARNING
READY
PE UID.ACCT.XI ID A036 ACCESScUPDATE)
READY
Figure 5-9. READY Screen - RACF Commands
1. Type ALD FUID.ACCT.*# UACC(READ) AUDIT(NONE) NOWARNING where
UID and ACCT are your user ID and account number, and press . The
READY prompt will be returned.
2. Type PE #UID.ACCT.*# ID(A036) ACCESS(UPDATE) and press . 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 October 22. 1996
-------
Chapter 5 Managing Libraries 5-11
-------
5-12 IDEA User’s Guide October 22, 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 flexibthty 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 library m the iNPUT LiBRARY SELECTION SCREEN. Your IDEA
library is where you will build and store your quenes The next few paragraphs
descnbe 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
-------
- - INPUT LBRARY SELECTION SCREEN --Q8/O / 3 IQ.83(RXG)
COMMAND ===>
Library Name === UIDACcT.QUERY.SPECS
Library Status(Shr/New/Old) SHR
For “New ” Only
Tracks 005
E irectory Blocks === OB B
Figure 6-1. Library Selection Screen
— Caution
When working in the INPUT LIBRARY SELECTION SCREEN, do not press
until you are fmished editing the options on the screen; otherwise,
IDEA will take you to the next screen. If is pressed accidently, press
PF3 or type END at the COMMAND prompt and press 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 to erase leftover characters.
Once you are satisfied with your library name, press 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 . If you do not, a message wifi 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 October 22, 1996
-------
When you are satisfied with the library status, press , 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.
MEMBEF: LIST .:UIDACCT UERV SPECS ROW 1 TO 12 OF 12
CO iAND === E NEWQUERY SCROLL === CSR
USE UB ,E 4 R ,U DI LEFT OF NAME.
NAME CHANGED DESCRIPTION 10
930702.1432 YWORD QUER LEAD POLLUTERS BW
OREFNG 930714.1727 0LORADO REFINING GO NAMES QUERY BW
NEWFILE 930525.1024 BWW
NE 1 930526.1700 “NEW” QUERY BWW
NEW2 930601.1122 BWW
.NE it3 930611.1111 B•WW
NEW4 930611.1117 BWW
NEWS 930611.1147 BWW
WEW5 930708.1729 VERSION 6 OF “NEW” QUERY BWW
NEW7 930723.1404 BW I
5151 930726.1454 BWW
ZIPCODE 930714.1809 LIP CODE BASED SEARCH BW
BOTTO$I OF DATA ******************** ***** ,‘*****
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-], 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 Browse/Read the query; no editing possible.
E (or S) query Edit/Select an existing query or create a new one in
the editor.
R query Rename the query.
U query Update the query description.
D query Delete the que 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.
EDIT -——- 1iIDALC.OjER .SPECS(QUERY1A) - Ui.O ) COLUMNS 9Q1 072
COMMAND == > GO NAMES . SCROLL = = PAGE
. *$c**k;k TOP O DATA
*. ..* .... BOTTOM OF DATA I
Figure 6-3. Edit Screen
6.2 Usin it GO Names to Form Oueries
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 October 22. 1996
-------
Data Options
- NAME SELECT1Ot1 METIU -
COMMAND ===
Name ===>
Words Required(ALL/ANY) ===> ALL
More less-likely names when worus have 3 or fewer consonants(Y/N) ===> N
3ther values that may be QRed together and the
resu ANDed with the name above
State(SS) or
County(SSCCC) = =>
Regior =‘-=‘ ===>
ZIP Code ===> ===
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 (or use your Arrow keys to position
the cursor anywhere on the action bar). Press to pull down a menu of the
data selection options available (see Figure 6-5).
Chapter 6. Conducting a Search Using GO Names
6-5
-------
Data Options
.1 1. All available data. W J4E SEL CT1Uh HEJ4U
2. Exclude ERN
3. Exclude OSH
.4. Exclude ERN and OSH
Words Required(ALL/ANY) ===> ALL
More less-likely namesw ’hen words have 3 or fewer consonants(!1/ N) == 4 ’J
Other values that may be ORed together and the
result .ANDed with the name above
State SS) or ==> ===> ===> ==>
County(SSCCC) == > === >
Reg ior === ===> = => = > = => == >
ZrP Code == > => == > .. .
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
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 4, “Exclude ERN and
OSH,” wifi 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.
Because the ERNS and OSHA data are not linked using FINDS,
run ERNS or OSHA queries as Nonlinked or Linked Nonlinked.
should be considered when combining GO Names and GO MenuA
Section 7.3.2, Combining GO MenuA and GO Names Queries).
it is necessary to
This situation
keywords (see
6-6
IDEA User’s Guide
October 22, 1996
-------
r— helpful hint
The selection you make at the Data Options action bar will remain in effect for all
GO Names quenes until you change the selection or exit the IDEA system.
You can make your “Data Options” selection either before you specif ’ the GO
NAMES search cntena or after you have specified your cntena and received the “
names selected” information (see Section 6.2.2, Searching for Facilities by Name).
6.2.2 Searching for Facilities by Nanw
— Caution
While you are using the GO NAMES NAME SELECTION MENU, do not press
the key until you have finished typing in all the necessary information.
Pressing will instruct IDEA to run the name search function, so use the
key and arrow keys to navigate the screen.
GO Names uses a soundex algonthm 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 m an effort to find facilities that sound like the one you
entered. If a facility name matches this pattern, it will appear in the hst 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., Schiage or Lock).
To form a query according to facility name alone, take the following steps:
1 Use or the arrow keys to move the cursor to the nght of the NAME
prompt.
2. Enter the name that you want IDEA to search for, and press ,
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 retneve the
names of those facilities which have any of the chosen words m their titles. If you
enter Schiage Lock and select ANY, IDEA will list those facility names that include
either word: Schiage OR Lock. If, on the other hand, you decide to select ALL
words (or leave it as the default), GO Names will only retneve facility names that
contain all the chosen words. In this case, IDEA puts a Boolean AND between the
words. Usmg our example again, if you chose the ALL option you would only get
facilities with both the words Schiage AND Lock in their titles.
1 helpful hint
Once you have typed in the facility names you want IDEA to search for, press
; 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.23 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 m a specified
geographic area. This can be useful for looking at all facilities m 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,
quenes 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 begm a location search, use the arrow keys or press to place the cursor
two spaces to the right of the prompt you are answering. Enter the appropnate
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 October 22, 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 Interlace (see Section
4.2.2, Location Cazegory).
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 through mne. You may enter up to seven
EPA regions per search. Tins is the least specific location cntenon 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 critenon m GO Names.
When you are using GO Names, IDEA inserts a Boolean OR between all of the
location entnes that you have chosen. In other words, IDEA will retneve all the
facilities in each of the geographic areas you have selected. Thus, you should be as
specific as possible to avoid callmg up more facilities than you need.
For example, if you want to find all the EPA regulated facilities in M ontgomery
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 m addition to (OR) all facilities m NI ontgomery
County, MD As you can imagine, you would have to sift through far more facility
names (all the facility names in Region 3 m tins example) than you had planned. On
the other hand, Boolean ORs come m handy when you need to find all facilities in
Virginia and Maryland, for example, or Virginia m addition to Montgomery County,
MD.
r- helpful hint
When you are satisfied with your entnes, press the 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.
r— helpful hint
Enter the facility name and location values just as described in the previous two
sections, press and IDEA will run your name search.
See Section 6.3, Managing Queries in the JSPF Editor Mode, to learn what to do with
a query after usmg GO Names.
6.3 Manazi,w Queries in the ISPF Editor Mode
After you tell IDEA to run the name search by pressing 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 ongmally
entered.
6-10 IDEA User’s Guide October 22, 1996
-------
Data Options
NAME SELECTION MENU
COMMAND
Name ===> ScH1..A E LOCK
Worus Reouired(ALLIANY) ===> A_L
More less-likely names when words i ave 3 or fewer consonants(V/ ) ===> N
Cther values that may be Ored together aric the
result ANDed with the name dbove
State(SS) or ===> CA ===>
County(SSCCC) ===> ===>
Region ===>
ZIP Code == > ===> ===>
6 possibilities
Return Names to Query: Y(es), A(l1), M(ax) ===‘ Corp. Prof. V/N) ===> N
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, and pressed : 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.
63.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:
Schiage Lock Co (RCR CAD98209356)
A(ll) 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:
Schiage Lock Co (RCR CAD98209356)
Schiage 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
Schiage Lock Co (RCR CAD98209356)
2481 Bayshore Blvd
San Francisco CA 94134 09 075
Schiage Lock Company (NCD CAD983647785)
2401 Bayshore Blvd
San Francisco CA 94134 09
6.3.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 (dependmg 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 retneved.
Producing the query depends on an exlstmg 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 facihties that share a corporate relationship with the facilities that matched your
GO Names cntena. Figure 6-7 illustrates two of these headings in a query.
6-12 IDEA User’s Guide October 22, 1996
-------
EDIT ---- UIDACCT.OUE V.SPECS(SCHLAGE) - COLUMNS 001 072
COMMAND = => SCROLL === PAGE
** *** ** * ***, ***** * TOP OF DATA
900801 / 930816 1932 Names Search found 6 names. /
008902 /* Name: SCHLAGE LOCK /
000993 / StC : CA */
998004 OUTPUT REPORT 1A
000805 INPUT LIN
000006 SELECT DUN.ULNO=
000807
090808 /* no DUNs number */
/ . ****** *_********** .***1
0.00910 / AD983547785. SCHLAGE LOCK CO wco /
900911 f 24924 HUMPHRIES RD *1
000812 /* TECATE CA. 91980 09
900013 / SCHLAGE LOCK COMPANY (FIN) *f
0 988i•4 1+ 073 /
000915
00081€
000917 / not in a corp. tree /
000018 /********* **** ***-*** !
900919 /* CAD982039356, LA USD LOCKE HIGH SCHOOL (RCR) *1
090020 /* 325 E 111TH ST *1
000921 f LOS ANGELES CA 90861 09 037 */
Figure 6-7. Dun & Bradstreet Keywords
6.4 Lookinr ’ at a GO Names Query
Once you have returned the facility list to your query by selecting Y, A, or M, and
CORP. PROF. I or N, and pressing , 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 ouery, 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 not 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
-------
EDIT UIBACcT.QUERY.SPEcS(OUERY I) - COLUMNS 08.1 072
COMMAND ===> SCROLL == PAGE
****** ** ******* ** TOP OF DAIA
•0 00 00I / 950925 1445 Names Search found S names. /
088002 f Name: SCHLAGE LOCK */
880003 /* keg: 08 */
098 4 OUTPUT REPORT 1A
089005 INPUT LINKED NONLINKED
080005 SELECT FIN.EPID=
008007 COD0825574 0, / SCHLAGE LOGE COMPANY (RCR C0D082 557420) */
008098 C0 1DEA023684 , / SOH AGE LOCK COMPANY (PCS COP 0 0 0001) */
008009 S0 088 09 O9I5 O /* LUCK SCHOOL DISTRICT (NCD C05#020294W 101101A ) *1
090010 OR ER .OWNID=.
008011 117707, /* SGHLAGE LOCK CO cERN 117707) *1
000812 38158. /* SGHAGE LOCK ERN 238158) *1
908013 350702 /* SCH AGE LOCK COMPANY (ERN 238748) */
.*********************** **** BOTTOM OF DATA * ******k***k**************
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 October 22, 1996
-------
6.4.1 Mod jfying 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 enter; it does not attempt an exact
character-for-character match. For this reason, you 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 COM MAND 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
m the first facility listed in the above query (Figure 6-8), the one with EPA ID
number C0D082657420. You would perform the following steps to delete lines 8
through 13 and edit the query:
1. Use 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. or arrow down to the last line of the block you wish to delete (line
000013, the last line m 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 to delete the block of lines
4 Use and the arrow keys to move the cursor to the end of the EPA ID
number in line 000007, and over the comma to remove it
Chapter 6 Conducting a Search Using GO Names 6-15
-------
— helpful hint
Table 6-3 below highlights several other commands available for use m the EDIT
SCREEN, mciudmg 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 I SPF Editor features mtroduced m this
Chapter.
Table 6-3. ISPF Keys and Commands (default vaiues)
Command
Mode
Description
END PF3/PFL5
Edit
Saves changes and returns to the previous screen.
(Returns to the previous screen without saving when in
Menu Interface)
Browse
Returns to the previous screen
RETURN
PF4/PFJ6
Edit & Browse
Returns directly to the previous Primary Option
Menu.
UP PF7/PF19
Edit & Browse
Scrolls up by the amount set at the SCROLL or
COMMAND prompt
DOWN PF8/PF2O
Edit & Browse
Scrolls down by the amount set at the SCROLL or
COMMAND prompt
LEFT PFJOfPF22
Edit & Browse
Scrolls left by the amount set at the SCROLL or
COMMAND prompt
RIGHT PF1 1/PF23
Edit & Browse
Scrolls right by the amount set at the SCROLL or
COMMAND prompL
To maneuver the
cursor around
IDEA screens
Use arrow keys for all directions, use key to
move the cursor from prompt to prompt, use
to move the cursor to the top-left prompt
To reset the keyS
board when it locks
up
key; key with R, right ,
depending on your keyboard configuration
Report IA 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 typmg
in REPORT on the same line and specifymg 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
If you delete the last facility in a hst of facilities, you must make sure that there
are no commas in the entry that is last in the resulting list. Note that the facthties
in lines 7, 8, 11, and 12, of Figure 6-7 have commas, but the entries in lines 9 and
13 do not.
6-16 IDEA User’s Guide
October 22, 1996
-------
See Table 6-4 for a bnefdescnption of the different report formats available in
IDEA.
Table 6-4. IDEA Standard Reports
There are currently four standard IDEA report formats 1A, 1 B, 2, and Summary
REPORT IA
A brief report of mdividual facilities Orgamzed 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 lB
A more detailed presentation of information on individual facilities, mcluding historical and
programmatic data such as dates and results of inspections, specific toxic substances reported,
and details of enforcement actions
REPORT 2
A hnked 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 FOIA concerns: Exciudinji Nonreleasable data from GO Names
This section applies only to EPA employees that have access to enforcement sensitive
and confidential data through IDEA. If you do not have this level of access, no
nonreleasable data will appear in any report you run in IDEA.
If you have enforcement sensitive/confidential access, but you want to run an IDEA
GO Names report for someone else (who does not have that level of access), type GO
NAMES I instead of GO NAMES, at the COMMAND prompt when you enter the
NAME SELECTION MENU. This will have two effects
1. Any facilities that would normally have appeared as the result of a GO Names
retrieval, but are enforcement sensitive (e.g., a DOCKET case still in the planning
stages) or confidential (e.g., DUNS and OSHA data are not currently releasable
through IDEA), would not appear in the query that is generated.
2. The keywords “SEC 1” would appear at the top of the generated query, so that
any nonreleasable data for the facilities that you do get in GO NAMES 1 will not
appear in your report(s). Users that do not have access to enforcement sensitive
or confidential data through IDEA have a secunty access equal to 1.
Chapter 6 Conducting a Search Using GO Names 6-17
-------
Note
The keywords “SEC 1” can be used in any query, to exclude nonreleasable data
from your report(s). Simply add them to the top of the query, before typing GO.
Two differences to note between GO Names and GO Names 1:
1. Since OSHA data is not currently releasable through IDEA to non-EPA users
(i.e., it is confidential), the option of excluding OSHA data does not appear under
Data Options, as it is already excluded.
2. Since DUNS data is not currently releasable through IDEA to non-EPA users
(because the contract between EPA and Dun & Bradstreet does not allow it), the
option of running a corporate proffle will not be available. Therefore, the Corp.
Prof. prompt will not appear. (Compare Figure 6-9 with Figure 6-6.)
• Data Options : . : . ::.
NAME SELECTION MENU :
COM AND
Name === SDHLAGE LOCK
Words Required(ALL/ANV) ALL
:$ore less-likely names when words have 3 or fewer consonants(Y/N) ===> .N
Other values that n v be :Ored together and the
result ANDe with the name above
State(SS) or ===> CA ===>
County(SSCCC) ===> ===>
Region === ===> ===>
ZIP Code
possibilities
Return Names to Query: Y es), A(ll), M(ax) ===
Figure 6-9. GO Names 1 Facility Count -- No Corporate Profile
6-18 IDEA User’s Guide October 22, 1996
-------
6.6 Runninj 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-10.
QUERY STATUS SCREEN
COMMAND ===
14:47:01.92 - 1 Facility selected and in FINDS
Counts (percentages), by ddL bdse , of facilities selet.t.ed but
. xc1uded because the ’ were not present in FINDS:
Press ENTER to continue, END to return to start
Figure 6-10. Query Status Screen
6.7 Viewinji a Query Report
Ifyou choose to see the reports, IDEA will deliver information to your screen
acccrdmg to the format(s) you selected earlier. The report is presented to you in the
BROWSE mode (see Figure 6-11) 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, PF1O to scroll left, and PF11 to scroll right. Ifyou 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.
Chapter 6. Conducting a Search Using GO Names 6-19
-------
BROWSE - Report: IA- ifl Progress MAX 000023 LINE 00800080 C DL 801 080
OUMMAND
Issue coi nand PRINTO to print, or SAVE to save to data.set.
******* ************************* TOP OF DATA **** **k **** ********** ********
1 U.S. ENVIRONMENTAL PROTEC
INTEGRATED DATA FACILITY-SPE •IFIC Co
FINDS Id: .CO0 082E57420 Fac. Name: SCRLAGE LOcK CO. itv: S
Address: 3999 HANCOcI EXPRESSWAY Zip.:
RCRIS Handler Id: 00D082557420 Year No.Evai . No.NOVs No.
Name: SCHLAGE LOCK COMPANY CY93 0 :0
TSD Facility Status: HPV? NO CY94 0 0
O rner Operator Type: P Exist. Date: CY95 0 0
AFS CDS Plant ID: 8804100045 Plant Name: SCH.LAGE LOCK COMPANY Year N
Source Compi. Status Air Program Desc.Qtrly compi Status 1993
IN COMPLIANCE - INSPECTION SIP SOURCE 33333333 1994
1995
Civil Docket Case Name Case Number: Type Case Law Ovrall S
S cHLAGE LOCK COMPANY :08-87-0029 CIV WA CASE CLO
Figure 6-11. Report 1A in Browse Mode
6.8 Exitinji 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).
6-20 IDEA User’s Guide October 22, 1996
-------
6.9 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 algonthm that recognizes conso-
nant character stnngs 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
facthty information to the ISPF editor where it can be reviewed, edited, or run as a
query.
Chapter 6 Conducting a Search Using GO Names 6-21
-------
6-22 IDEA User’s Guide October 22, 1q96
-------
Chapter 7. Conducting a Search Using GO MenuA
IDEA ’s GO MenuA utility allows you to build a query m the Keyword Interface by
using the Menu Interface.
7.1 Introduction to GO MenuA
The GO MenuA utility allows you to build a query in the Menu Interface and edit it
m the Keyword Interface. The Menu Interface is the simplest means of retneving
mformation from IDEA. It provides convement pop-up windows for you to form
queries simply by selecting cntena 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 quenes from scratch
according to almost any criteria found in the lmked IDEA databases. This wide
range of choices gives you the ability to form very detailed quenes involving many
vanables. 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 convemence 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 Getti,w 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 hbrary 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 7 Conducting a Search Using GO MenuA 7-1
-------
— Caution
When working in the INPUT LiBRARY SELECTION SCREEN, do not press
until you are fmished editing the options on the screen; otherwise,
IDEA will take you to the next screen. If is pressed accidently, press
PF3 or type END at the COMMAND prompt and press to return to
the INPUT LIBRARY SELECTION SCREEN.
INPUT LIBRARY sELEcTION SCREEN --08/24/93 17.03(RXG
COMfrIAND
Jbrary Name ===> UIDACCT.QUERY.SPEOS
Library Status Shr/New/Od) === SUP
For ‘New’ Only
Tracks === 005
Directory Blocks ===> 008
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 ; 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 October 22, 1996
-------
1EMBER LIST - UIDAcCT.QUERY.SPECS ROW 1 TO 12 0 12
cOMMAt D ===> E NEWQUERY SCROLL ===> CSR
USE ‘B.E , ,U,D LEFT OF NAME.
NPJIE CHANGED DESCRIPTION E
QUEWI1 930702.1432 UID
QUE Y2 930714.1727 U 1
QUERY3 930525.1024 u Ir
QUERY4 930526. 780 UIJ
QUERY5 930601.1122 UID
QUERY6 930611.1111
QUE V7 930611.1117 UID
QUERYB 930611.H47 UI
QUERV9 930708.1729
BOTOM OF DATA *********************t**** ** **
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-], Member List Commands below. They
should be typed to the left of the member name or at the COM MAND prompt fol-
lowed by a space and the member name.
Table 7-1. Library Member List Commands
B query Browse/Read the query; no editing possible.
E (or S) query Edit/Select an existing query or create a new one in
the editor.
R query Rename the query.
U query Update the query description.
D query Delete the query from the MEMBER LIST.
To create a query, type E at the COMMAND prompt, press , type the
name of the new query (for example, E NEWQUERY as in Figure 7-2), and press
.
helpful hint
Query names can be up to eight characters long including numbers and letters but
not special characters such as @# % &*O ?/!.
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
-------
7.3 Usinj i 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.
F OIl ---- UIOACCT.QUERV.SPECS(NEWQUERV) COLUMNS 001 872
; COMMAND == > GO NienuA SCROLL ===> PAGE
. ****** ***z* . ********** •***** *** **** c TOP OF DATA ***** ******* * * **** ±*** **
... : .. •. •:: . : : . : . : : ...:... • . . ::: : : .
: - * * * ************ ** *** **** * * * *** BOTTOM OF DATA
Figure 7 -3. Blank Edit Screen
As shown in Figure 7-4 , the MAIN MENU SCREEN ofthe Menu Interface will
appear. With this utility, you can select criteria from the Menu Interface, and GO
MenuA wifi generate a Keyword query for you back in the Keyword Interface.
7 -4 IDEA User’s Guide October 22, 1996
-------
Date: 99/22/93 IDEA User: DID
Create/Add a query by entering an “S’ next to:
— Location . More:
— Pollutants
Industry
— Nonconi 1iance
— Enforcement
— Facility Status
— Rur Query
— Clear Query
— Save Query
Retrieve Query
PFKI/13: HELP . -
PFK3/15: END
PF1 7/19: Page Up
PFKB/28: Page Down
Figure 7-4. Main Menu Screen
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 fmd 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.
— helpful hint
To choose a category in the Menu Interface, use to move the cursor to
the left of the category name, then type S (for select) followed by . This
sequence is used whenever you want to make a selection from the IDEA Menu
Interface.
Chapter 7. Conducting a Search Using GO MenuA
7-5
-------
Date: 08/18/93 IDEA User: UID
create/Add a query by entering ar: S ’ next to:
— Location . More: ÷
Pollutants . You tiave reatec a query, using the following criteria:
industry .
— Noncompliance . Noncomp .ance:
— Enforcement . . (AFS) In.Vioiation -
— Facility Status . (AFS) Significant Violation Status
• . (PCS) Renortable Noncompliance
• . (PCS) Significant Noncompliance
• . (RCR) Unresolved Violation exc. High Priority)
• . (RCR) Unresolved High Priority Violation
• . (NCD) FIFRA - Non Compliance
— Run Query . . (NOD) FIFRA - Significant Non compliance
Clear Query . . (NCD) TOSA - Non Compliance
— Save Query . . (NOD) TOSA - Significant Non ccrnipiiance
— Retrieve Query • . (NOD) EPCRA - Non Compliance
PFK1/13: HELP . . (MCD) EPCRA - Significant Non Co npliance
PFK3/.].5: END
PFK7/19: Page Up
PFKS/2G: Page Down
Figure 7-5. Noncompliance Criteria in the Menu Interface
i— helpful hint
When you are satisfied with the content of your query, type S next to RUN
QUERY, and press .
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, 1B, 2, SUMMARY), and press .
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 October 22. 1996
-------
EDIT ---- UIDACCLQUERY.SPECS(NEWQUERV) - COLUMNS 801 072
COMMAND === SCROLL === HALF
** *** *** TOP OF DATA
000001 /* *1
@00002 /
000003 / Keywords generated by Menu A Interface
008804 /* *1
900005 / 1994.08.11 09 ,07.55 *1
• ooooo6 / *1
• ooeooi / *1
008008 OUTPUT REPORT 1A
800009 INPUT LINKED SELECT
808010 ( / paren before MenuA keywords for convenience i:n further combining
800011 f* Noncompliance keywords ‘/
000812 ((AFS.DCS1=1.5,7, ,W OR AFS.SVU=E,S,8 .X,C,F.T) OR
000913 ((PCS LRNc D.,E,N,S T & PC5.MADI=M & Pc5 :IACC A)) O.R
000014 .RCR.cPVIOL=X OR RCR.cPVIOL=9) OR ••
000015 ((.NcQ.LEGISLA=F AND NOT NcD.SNC=Y) OR (NCD.LEGISLA=F AND NCD.SNC=Y) OR
000016 (NCD.LEGISLAT AND NOT NCD.SNCY) OR (NCD.LEG1SLAT AND NcD.SNC Y) OP.
000017. NCD.LEGlSLA=E AND NOT NcD.SNc=Y) OR (NCD.LEGISLA=E AND NDD.SNC=Y)))
800818 ) / paren after MenuA keywords for convenience in further combining
.**** BOTTOM OF DATA ** ************************
Figure 7-6. Edit Screen with keyword logic
The GO MenuA keywords that are displayed are in the following format:
• Lines 000001 to 000007 -- Comment lines that highlight the keywords generated
by GO MenuA always precede the keywords. Comment lines also precede some
sections of keywords in order to indicate from which Menu category they came,
as in Line 000010.
• Lines 000008 & 000009 -- Contain the OUTPUT, INPUT, and SELECT state-
ments that are necessary for any query.
OUTPUT -- Indicates that you will receive output in the form of
Reports 1A, Report 2, and Report Summary. For more information
on these reports, refer to Chapter 10, IDEA Standard Reports.
INPUT -- Indicates that the input data that IDEA will use to process
your query will be linked, which means that FINDS will be used to
integrate data taken from the different databases (as opposed to non-
linked or linked nonlinked). For information on these options, refer
to Chapter 2, IDEA. What it Does & How it Works.
SELECT -- Selection criteria that IDEA will use when it searches for
facilities in the copies of the program office databases. In this case,
the selection criteria are the noncompliance criteria that were selected
from GO M enuA in Figure 7-5.
Chapter 7. Conducting a Search Using GO MenuA 7-7
-------
• Lme 000010 -- A comment Ime 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 usmg GO MenuA, you have several
options. You can edit the query, add more cntena to it (by accessmg the GO Names
utility, by running GO MenuA agam, or advanced users might add Keyword logic of
their own), or run it as it is.
73.1 Editing GO MenuA Queries
The ISPF EDIT SCREEN is a scroffing display format that allows you to type over
or delete any data that is displayed. You can edit the lines m the query with the
commands m 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 quenes m detail.
Table 7-2. Line Editing Commands
C Copy this line
M Move this line
D Delete this line
CC, MM, DD Mark starting and endmg lines for copying, moving,
or deletmg a block of lines.
Cn,Mn,Dn Copy, Move, Delete next n lines (mcludmg this line)
A Place moved/copied line(s) after this line
B Place moved/copied line(s) before this line
I Insert a line after current line
In 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 usmg the GO
Names utility. To access this utility, type GO NAMES at the COMMAND prompt,
and press .
7-8 IDEA User’s Guide October 22, 1996
-------
— Caution
While you are using the GO NAMES NAME SELECTION MENU, do not press
the key until you have fmished typing in all the necessary information.
Pressing will instruct IDEA to run the name search function, so use the
key and arrow keys to navigate the screen.
Enter name and/or location parameters in the NAME SELECTION MENU
SCREEN, and press . 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 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 . IDEA will display the number of possible matches
for your new criteria.
Data Options
NAME SELECTION MENU
CO WAND
Name ===> CAMPBELL SOUP
Words Required ALL/ANY) ===> ALL
More less-likely names when words have 3 or fewer consonants(Y/N) ==> N
Other values that may be ORed together and the
result ANDed with the name above
State(SS or ===>•NJ ===>
County(SSCCC) ===>
Region ===> ===> ===>
71P .. . ..
te
Re .urn NWfl w i . uerv: Y(esJ, ACtI), M(ax) ===> Corp. Prof.(Y/N) ——--> N
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 , 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 ---- UIDACCT . UE•RY.SPECS(NEWOU RY) COLUMNS 001 072
OOMMAND > SCROLL > PAGE
****** ************* k************* TOP OF DATA
000901 / .9408il 1803 Names Search found 4 names. ‘/
009002 /* Name: CAMPBELL SOUP */
008003 t Ste: NJ
000804 OUTPUT REPORT 1A REPORT 2 REDORT S4JMMARY
000085 iNPUT LINKED
000806 SELECT FTN.EPID=
000807 CA80 0 0112532. CAMPBELL SOUP cOMPANY(OUN 001288042) /
008908 N3D001288042 , :/* CAMPBELL SOUP cOMPANY (RCR) /
008999 N3D902481273, /* CAMPBELL SOUP COMPANY (RCR) *1
008010 t JD00395195i /* CAMPBELL SOUP COMPANY (RCR) /
800911 / *1
000812 / *1
008013 /* Keywords generated by Menu A interface *1
000014 /*
008015 /* 1994.98.11 00.07.55
008816 /*
000817 /* - --. -
009818 OUTPUT REPORT 1A
000019 INPUT LINKED SELEcT
008820 ( /* paren beforeNenuA keywords for convenience in further conthining
008021 1* Noncompliance keywords */
008822 ((AFS.DCS1=1,6.7.B ,W O AFS.SV11 E,S , ,X,C,F,T) OR
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 October 22. 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 . Then type AND, and press 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 itself), and press .
Figure 7-9 shows the sample query after these changes have been made.
EDIT ---- U IDACCT.QIJERY.SPECS(NEWQUERY) COLUMNS 001 072
COMMAND === SCROLL === PAGE
****** TOP OF DATA *** * * ** * * * * * * ** * *** * *** *** * *
008081 / 940811 1083 Names Search found 4 names. /
008802 / Name: CAMPBELL SOUP */
000803 /* StC : NJ */
000004 OUTPUT REPORT 1A
880085 INPUT LINKED
• 008006 SELECT FIN.EPID=
880807 CA8000112532, /* CAMPBELL SOUP COMPANY (DUN 001288842) */
008008 NJ0001288842, f CN 1PBELL SOUP COMPANY (RcR) */
088809 NJ00 0248 1273, ! cAMPBELL SOUP COMPANY R R) /
008010 NJ0003951951 f ’ CAr .1PBEL SOUP COMPANY (RcR) /
888811 AND
008812/* *1
000013 / *1
008014 /* Keywords generated by MenuA Interface
008015 /* *1
088016 /* 1994.88.11 89.07.55 *1
080017 /* *1
008018 /*
000019 ( / ‘ paren before MenuA keywords for convenience in further combining
088020 /* Noncompliance keywords */
000821 AFS.:OCS11,6,7,:B. ,WOR AFSSVU=E,S,B,X ,C,F,T) OR
008822 PCS.LRNC=O,E,N,S,T & PCS.MADI M & PCS. IACC=A)) OR
Figure 7-9. Edit Screen with changes shown
7.4 Runnin a GO MenuA Ouery
To run the query, use or to move your cursor to the
COMMAND prompt, type GO, and press . From this point, IDEA will
process the query and display the QUERY STA TUS 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
-------
- QUER; STATUS ScREEN - -
COMMAND
10:36 :24.27 - 2 Facilities selected and in FINDS
counts (percentages), by atabase, of facilities selected but
excluded because they were not present in FINDS:
A S 428 ( 14) FIN 0 ( 0)
PCS 9698 ( 57) RCR 54 ( 1)
NCD 23170 ( 32)
Press ENTER to continue. END to return to start
Figure 7-10. Query Status Screen
7.5 Viewinj 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-1] ). To maneuver through the report, use PF7 to page
up, PF8 to page down, PF1O 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 October 22. 1996
-------
B. OWSE Report.: IA-- --- - In Progress MAX 800023 LINE 08008800 COL 801 080
COMMAND ==>
Issue coninand PRINTO to print., or SAVE to save to dataset..
********************************* TOP OF DATA * *******************************
I LS. E WIRONMENTAL PROTEC
INTEGRATED DATA FACILITY-SPECIFIC CO
- SOUl- COMPANY City:
Address: 1188 W. 15TH ST. Zip: 72701
RCRIS Hand 1er Id: ARD806353312 Year No.Eval. No.NOVs No.
Name: CAMPBELL SOUP CO 0Y92 0 0
TSD Facility Status: 4PV? NO CY93 8 0
Owner OperatoriType: P E,nst. Date: CY94 0 0 :
PCS Penriit No: AR0801520 Issue Date: 1975103 .Year Mi Viols Eff.Viois Inspe
Fac. Name: CAMPBELL SOUP CO CY.92 0 0
inactive Minor Discharger CY93 .0 0
Expired Date: 1989/03 CY94 .0 0
AFS CDS Plant ID: 0514380810 Plant Name: CA 1PBELL SOUP COMPANY Year N
Source ompl. Status Air Program Desc. Qtrly Compi Status 1992
Figure 7-11. Report 1A in Browse Mode
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.6 Exiting 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 cntena
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-
blmg 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 October 22, 1996
-------
Chapter 8. Conductinj a Search Usin r ’ Keywords
This chapter provides detailed mformation on IDEA Keyword Queries.
8.1 Introduction to IDEA Keywords
The Keyword Interface allows you to conduct a search accordmg to almost any en-
tena that can be found in the linked IDEA databases. This wide range of choice
gives you the ability to form very detailed quenes involving many vanables; 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 cntena you have and use the IDEA Keyword
Query Language (I KQL) 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.
— Caution
When working m the INPUT LIBRARY SELECTION SCREEN, do not press
until you are finished editing the options on the screen; otherwise,
IDEA will take you to the next screen. If is pressed accidently, press
PF3 or type END at the COMMAND prompt and press to return to
the INPUT LIBRARY SELECTION SCREEN.
Chapter 8 Conducting a Search Using Keywords 8-1
-------
- - INPUT LIBRARY SELECTION SCREEN -—0E/2 /93 i7. 3(RXG )
COMMAND ==a
Library flame ==a UiDAC T.QUERY.SPE S
Library Status (Shr/New/O d == > S I4R
F r ‘New Only
Tracks ===> 005
Directory Blocks 0 08
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 ; 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 wifi 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 October 22, 1996
-------
MEMBER LIST - UIDACCT.QUERY.SPECS ROW 1 TO 12 OF 12
COMMAND = = E NEWQUERY SCROLL ===> CSP
USE ‘ B.E,R U ‘ LEFT OF NAME.
•NAME CHANOED DESCRIPTION •ID
DEW 930702.1432 KEYWORD QUERY LEAD POLLUTERS BWW
OREFNc 930714.1727 COLORADO REFINING GO NAMES QUERY
NE14FILE 930525.1024 .0 1 4W
NEW1 93 05a6. 170 8 NEW’ QUERY BWW
NE142 930601.1122 BWW
NEW3 938b11.I111 Bww
t4E 1 44 930611.1117 BWW
NEW5 93061L1147 8 1 4W
NEW6 930708.1 729 VERSION 6 OF ‘ 1 NEW’ QUERY 814W
NEW7 938723.1404 BWW
5151 930726.1454 BWW
ZIPCODE 930714.1809 ZIP CODE BASED SEARCH 8 1 4 W
BOTTOM OF DATA
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 Browse/Read the query; no editing possible.
E (or 5) query Edit/Select an existing query or create a new one in
the editor.
R query Rename the query.
U query Update the query description.
D query Delete the query from the MEMBER LIST.
After you select a query to edit, or create a new one, press . IDEA will
bring you to the EDIT SCREEN illustrated in Figure 8-3.
Chapter 8. Conducting a Search Using Keywords 8-3
-------
Table 8-2 (Page 2 of 2). ISPF Keys and Commands (default values)
Command
Mode
Description
LEFT PF1O/PF22
Edit & Browse
Scrolls left by the amount set at the SCROLL or
COMMAND prompt.
RIGHT PF11/PF23
Edit & Browse
Scrolls right by the amount set at the SCROLL or
COMMAND prompt.
RETRIEVE
PF12/PF24
Edit & Browse
Moves the cursor to the first input field on the screen
and retrieves the last command entered.
FIND
Edit & Browse
Locates the first line containing a specified character
or string of characters.
CHANGE
Edit
Changes the first occurrence of a character(s) to
another character(s).
SAVE
Edit
Saves your work and remains in the edit session.
Browse
Refer to the Saving Reports portion of Chapter 10.
CANCEL
Edit
Ends an edit session without saving any changes.
8.2 Usinj, Keywords to Write Oueries
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.
EDIT ---- UIDACcT .QUERY.SPECS(EXAMPLE) COLUMNS 801 072
c.OMMAND ===> SCROLL PAGE
*k ** ** ** ** * ****** TOP OF DATA
000901 OUTPUT REPORT 1A REPORT SUMMARY fk REPORT IA AND SUMMARY .1*
0 0002 IIWUT L1N D /* LINKED /
9L9Ø993 SELECT
008804 RCR.LSTATE=PA / RCR PENNS’ftVANIA /*
000805 AND
00e8O TRI.TCID=000102883 /*.TOLUENE TRI ID #
008907 AND
08808 RcR.WNITT.GT 10500 / RCR WASTE AMOUNTS /
90890g
0 0010 /* END OF QUERY /*
**.**** BOTTOtI OF DATA ********************* ******
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).
(Note: the OUTPUT statement
Lines 5 and 7 show the Boolean connector AND.
can appear before the INPUT statement.) Lines 4, 6, and 7 show data element
names and values.
8-5
Chapter 8. Conducting a Search Using Keywords
-------
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 cntena, is a
necessary component of every Keyword query. It will affect how many facilities may
be selected and how the output will be orgamzed. 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 these apostrophes will turn into line numbers. If you
press before completing your query, insert lines by typing i on a line
number; press . This will insert a [ me after that line.
Use or the arrow keys to move your cursor down to the first open ime 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 quenes.
8.2.1.1 Using Linked and Non/inked Keywords
When you include the keywords LINKED and/or NONLINKED m your query, you
are tellmg 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 retneve data that has been integrated using
FINDS.
8-6 IDEA User’s Guide October 22, 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 NONLINKED 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, IDEA 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 retneve data that has been integrated by FINDS and data that has not been inte-
grated by FINDS.
This INPUT cntena will generate two parts to reports IA, 1B, and 2. The first part
will contain those facilities that meet all your selection cntena 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, but facilities
may.
Note that all the facilities in the second section were selected because they fulfill only
the cntena 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 cnteria for the query will follow.
The required keyword SELECT should follow the INPUT statement and directly
precede your Keywords search cntena. 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 descnption and their IDEA abbreviations, are
listed m Table 8.3 below.
Table 8-3 (Page 1 of 2). Database Select Codes
IDEA
Abbrev
iation
Database
Description
AFS
AIRS Facility Subsystem
Information regarding airborne pollution in the U.S
The AFS contains emission and compliance data on
individual facilities
CER
CERCLA Information
System
Information regarding the official inventory of CERCLA
sites, including enforcement, financial and site/incident
data
DCK
Civil Docket
Tracking system of enforcement case activity, including
court- related information, violation, and penalty data
DUN
Dun & l3radstreet Mar-
keting Index
Information regarding corporations and their locations,
parent- subsidiary relationships, industrial classification,
and sales figures
ERN
Emergency Response
Notification System
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
FF1
Federal Facilities Index
System
Information about environmental regulatory projects that
target federal facilities, including compliance status and
budget data
FIN
Facilities Index System
A computerized inventory of facilities under EPA regu-
lation Provides facility EPA ID numbers as well as
pointers to other databases
LST
Contractor Listing
Docket
Information on contractors that have been hsted as meli-
gible for EPA contracts under CAA and CWA
8-8 IDEA User’s Guide October 22, 1996
-------
Table 8-3 (Page 2 of 2). Database Select Codes
IDEA
Abbrev
iation
Database
Description
NCB
National Compliance
Data Base (for FIFRA,
TSCA, EPCRA 313)
Compliance data under FIFRA, TSCA, and EPCRA
313 including inspections, case reviews, and enforcement
actions
OSHA
Occupational Safety and
Health Admuustration
Contains OSHA inspections data, including types of vio-
lations, substances involved, actions required, accidents,
and penalties
PCS
Permit Compliance
System
Contains permit compliance and enforcement informa-
lion under NPDES of CWA, including inspection data,
facility data, monitoring information and description of
outfalls (pipes)
RCR
RCRA Information
System
Contains tracking of RCRA handlers and information
on compliance monitoring and enforcement, corrective
action, handler IDs, perrmuing, and facility management
planning.
SET
Site Enforcement
Tracking System
Contains tracking of the names and addresses of PRPs
who have been issued CERCLA 104 general’ notice
letters, or CERCLA 122 speciaF’ notice letters, date of
letters, and Notice Letter Addressee name and address
TRI
Toxic Chemical Release
Inventory
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 mformation from
the Toxic Chemical Release Inventory, you would type TRI after the INPUT and
SELECT statements, like this:
INPUT LINKED
SELECT
TR I
Directly after the database identifier is entered, type a penod (.) 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 mdicate
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 quenes (refer
to the Index column m Appendix C, Data Elements in IDEA Shadow Files).
Havmg selected specific data elements, you can define your search by identif ’ing 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 Ushtg a Bookan 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 after database.element and type in the appropnate 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 m
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 October 22, 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 placmg a Boolean OR between the values you list In
other words, IDEA will retneve 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 tnchloroethylene (TRI code 000079016) then you would enter the followmg
SELECT statement (Note: the “=“ sign may be used interchangeably with EQ):
SELECT
TRI.TCID = 800108883, 001330207, 080079016
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 usmg
the data element LSTATE set equal (EQ) to PA. On the other hand, if you were
interested m searching for RCRIS facilities that were not m 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
mcluded in a range of values that you specify. The IN operator allows you to
perform an indefinite search. For example, if you typed m 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).
Chapter 8 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 specthed. 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 LI 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 1800
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 followmg SELECT state-
ment:
SELECT
RCR.WAMTT GE 1000
8-12 IDEA User’s Guide October 22, 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 meanmg. For
instance, the major discharge indicator (MADI) field 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 withm 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 m the SELECT statements above.
Other examples are ZiP codes, two-letter state abbreviations, chemical codes, signif-
icant violator status, Standard lndustnal Classification codes (SICs), dates of enforce-
ment actions, amounts of waste releases, etc.
When you have fmished composing your SELECT statement, it should have the same
format as the followmg expression:
SELECT
database.element Boolean-operator data-value
This is the basic format for any SELECT statement.
8.3 Using Boolean Connectors in a Onery
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 mtricate quenes you will have to learn to use Boolean ORs, ANDs and
other connectors, as well as parentheses.
OR The Boolean OR tells IDEA to retneve a facility record Wit fulfills one cntenon
OR a second cntenon, OR a third, etc. Use the OR as a connector between
database.element expressions. IDEA mterprets commas between data values as ORs,
so spelling out OR is not necessary when you are setting value cntena in the same
data element.
To demonstrate, let’s say you are searching for all RCRA facilities that are either in
the transporter umverse or the land disposal umverse. The data elements for these
critena are HUTRAN and HULAND, respectively, and these cntena are selected by
typing X after the = sign. So, remembermg to insert the Boolean OR, the SELECT
cnteria would look like this.
SELECT
RCR.HUTRAN = X OR
RCR.HULAND = X
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 October 22, 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 mstance, 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 withm the same database,
when commas (ORs) are not appropriate. Let’s say for mstance that you are looking
for all IRIS facilities that produce both toluene AND trichloroethylene:
SELECT
TRI.TCID = 000188883 AND
TRI.TCID = 080079016
Use the Boolean connector AND between “database.element Boolean-operator data-
value” statements in order to select facilities according to one cntenon AND a second
criterion AND a third, etc.
8.4 Usinji Parentheses in a Query
IDEA pnontizes 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 m 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 m 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 m 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 UsinR the TEXT command to help you build your query
One of the pnmary 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 m Appendix C, Data Elements in IDEA
Shadow Files does not tell you enough about 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 memonzed,
and need to look up the code for toluene. Type TEXT INFO at the Command
prompt in any IDEA screen. This will bring up a list, m 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 October 22, 1996
-------
BROWSE -- Table information - LiNE 00000080 CCL 001 083
COMMAND •== > S P.OLL ===> PAGE
lOP O DATA
J O Table Entries Arg len Txt len Updated AThas
AFS ANTI 21 2 53 19950123
AFS APC1 12 1 25 2.9950123
FS DATT 10 1 68 19958123
AFS DCAP 16 1 .68 19950123
AFS DCLP 18 2 75 19958123
AFS DCLI DCLP
AFS OCSI D AP
AFS GOVT 5 1 55 19950123
FS PLAP 116 5 48 .19950123
AFS SCH1 S D AP
AGO .D8 . 2 1 7 2.9950510
.AGG SIC 1698 2 50 19940909
AGO T ID 380 9 50 19958510
CE O - database taDles not present
ER - database tables not present
ORM DFRS 28 2 72 .1995:0417
cRM LAWS .33 5 50 19950417
M MEUC 11 1 19 19950417
cRM REGN 11 2 38 19950417
cRM SUE 57 2 35 19950417 - -
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..)
BROWSE - Table inforinati oi Max 260 LINE 00000241 OL 001 880
CO*1AND = =
conrnand PRINTO to print, or SAVE to save to dataset.
RCR PSTAT 698 7 40 19950317
RCR SIC ODE 1099 2 68 19950317
RCR VAREA EVAREA
SET - database tables not present
TRI AUCD 13 2 28 19940809
TRI ENRGYCD 4 3 29 19950713
TRI LDCD 4 3 34 19940809
TRI MAXC 11 2 34 19940809
TRI METH 103 . 3 :57 1994.0813
TRI METHODS METH
TRI RCYcL .CD 16 3 53 19940813
TRI REBC 7 2 56 19940809
TRI SICO 1719 4 100 19950713
TRI T ID 388 9 54 19950713
TRI TRMT . METH
TRI TRNG 5 2 69 19940809
R1 WECD 4 2 46 19940809
I RI 1AC 5 2 40 19940889
I TRI fl ICD 8 2 50 19940809
ZIP - database tables not present
BOTTOM OF DATA **************************** **
Figure 8-6. Bottom of Decoding Tables List
Chapter 8. Conducting a Search Using Keywords 8-17
-------
INote that 11(1. hAD has such a translation table available. Press Ff3 to exit this
list, and type TEXT TRLTCID at the Command prompt. A list of all valid codes for
TRI.TCID and their values appears in browse mode. (See Figure 8-7.)
BROWSE - Table information -•----- iax 382 LINE 80 0000DU COL 001 080
COMMAND == >
Issue coriiiiand PRINTO to print, r SAVE to save to dataset.
TOP OF OPTA
Element Arqument ==> Result text
TRLTCID ‘ m i ‘ ==> “:ETHYLENEBiSDITHIOCARBAMIC ACID, SALTS AND ESTER
TRI.TCID ‘ => 9WARFARIN AND SALTS
TRI.TCID “No b “ ==> ‘ANTIMONY COMPOUNDS
TRLTCID “N820 >:UARSEN IC COMPOUNDS
TRI.TCID “:N04 8 ‘ = > “BARIUM COMPOUNDS
TRLTCID uN050 ! > “BERYLLIUM COMPOUNDS
T1 I.TCID “ 14078 ==> “CADMIUM COMPOUNDS
TRLTcID “14884 ‘ “CHLOROPHENOLS
• TR1.TCID 9 ’ 090 ‘ ==> “CHROMIUM COMPOUNDS
• TRI .TCID “N0 5 “ COBALT COMPOUNDS
TRLTCID “Ni OD “ ==> “COPPER COMPOUNDS
TRI.TCID “14106 “CYANIDE COMPOUNDS
TRLTC.ID “N230 ‘ ==> “GIYCOL ETHER:S
TRI.TcID “14420 “ ==> “LEAD COFIDOUNDS
TRLTCID “14450 “ ==> “MANGANESE COMPOUNDS
TRI.TCID “14458 “MERCURY COMPOUND.S
TRI.TCID “N495 “ ==> “NICKEL COMPOUNDS
• TR1.TCID “N575 “ ==> “POLYBROMINATED BIPHENYLS ( PBBS
Figure 8-7. Top of TRI.TCID Decoding Table
Type FIND TOLUENE at the Command prompt. Press PF5 (the “repeat fmd” key)
until you get to just plain “toluene.” Note that the code for “toluene” is 000108883.
(See Figure 8-8.) Press PF3 to exit this list.
8-18 IDEA User’s Guide October 22, 1996
-------
• 8RO 1SE - Table information - Max 382 CHARS ‘TOLUENE’ FOUND
CO 4AHD
Issue coruiand PRINTO to print, or SAVE to save to dataset.
TR I.TCID “000108781” =•=> “MELAMINE
TRLTcIO “080108883” ==> “TOLUENE
TRI .TCT.D “000102907’ ==> “ HLOROBENZENE
T1 I.TCID “008108952’ ==> “-PHENOL
TRI.TCID ‘ooeiog en ==> ‘2-METHYLPVRI.DINE
TRI.TCID ‘000189773’ ==> “MALoNON:TRILE
1RI.ICIO “U001U98b4 ” ==> “2-MEIHOXYE [ HANCL
TRLTCID “.088118805” ==> “2-ETHOXVETHANOL
TRI .TCI.D “000110827” ==> “CYCLOHEXANE
TRLTCID 11080110061 1 1 ==> “ YRIDINE
T •Ri.TCID “000111422’ ==> “DIETHANOLAMINE
TRLTCID “08811144.4” => “BIS(2—CHLOROETHYL) ETHER
TRLTcID “000111911” — “BIS 2-CHLOROETf OXY)METHANE
TRIJCIO “009114261’ ==> “ ROPOXUR
TRLTCID ‘:0091i5071” > “PROPYLENE
IRLICID “.008115322” ==> “.DICOFOL
TRI.TCID “008117793” ==> “2-AMINOANTHRAQUINONE
TRLT ID “000117817” ==> “.DI(2-ETHYLHEXYL) PHT•HALATE
TRI.TCID 000i17840” = > “N-DIOCTYL PHTHALATE
TR 1JCID “.888118741” ==> “HEXACHLORUBENZENE
TRI.TcID “008119904” ==> “3,3’-DIMETHOXYBENZIDIHE
Figure 8-8. Code for TRI.TCID for Toluene
8.6 Output Report Selection
The keyword OUTPUT is another necessary component in your query. The
OUTPUT statement must immediately precede the 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 -Spec fled 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 and
the desired format (1A, 1B, 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 1B, 2, and Summary, the OUTPUT line should look like
this:
OUTPUT REPORT lB 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.9, Spe fyzng 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, LB, 2, and Summary
REPORT IA
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 lB
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 Downc!radin your Security Level
This section apphes only to EPA employees that have access to enforcement sensitive
and confidential data through IDEA. If you do not have this level of access, no
nonreleasable data will appear in any report you run m IDEA.
Keyword:
SECURITY
(abbreviated SEC)
Syntax:
SECURITY
n (where 1n4)
If you have enforcement sensitive/confidential access, but you want to run an IDEA
report for someone else (who does not have that level of access), type SEC 1 at the
top of your query
This keyword will temporarily downgrade your secunty status, for this query only, to
the level of secunty that pubhc users have. By using this keyword only releasable
data will appear m your report(s). (One effect of this is that you will not have any
8-20 IDEA User’s Guide October 22, 1996
-------
access to certain databases (e.g., OSHA and DUNS) which are nonreleasable in their
entirety.)
8.8 Excludini! Databases from Standard Reports
For occasions when you want to run a multimedia search in IDEA, but don’t want
thousands of pages of output for databases you aren’t interested in, we have devel-
oped the keywords INCLUDE and EXCLUDE.
Keywords:
EXCLUDE,
INCLUDE (abbreviated EXCL, INCL)
Syntax:
EXCL/INCL dbl
db2...
These keywords allow you to run a Linked query, but then only include a restncted
list of databases in Standard reports 1A and/or lB. The keywords can be used in two
ways:
1. Either before the list of report(s), in which case it would apply to all of the
report(s) requested, or
2. after specific report(s), m which case the keyword only applies to those specific
report(s).
For example, for a given linked query, the following OUTPUT section
OUTPUT INCLUDE FIN AFS PCS REPORT 1A REPORT lB
would result in two standard reports, both of which having only FIN, AFS, and PCS
data, but no data from any other IDEA databases. However, the following
OUTPUT section
OUTPUT REPORT 1A INCLUDE FIN AFS
REPORT 1A INCLUDE FIN PCS
generates two standard reports, both in lA format, that contain data from different
sets of databases: the first report with data from FIN and AFS, the second report
with data from FIN and PCS.
Chapter 8 Conducting a Search Using Keywords 8-21
-------
The EXCLUDE keyword is used similarly. However, the report(s) will contain data
from all IDEA databases except the databases hsted.
8.9 Specifyinji 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
destmation after the OUTPUT statement. You will then have the option of saving or
prmtmg when you view the report(s) (see Section 8.12.1, Viewing the Query Report).
Simply type SAVE or PRINTO at the COMMAND prompt, press , then
answer the prompts on the PRiNT/SAVE PARAMETER SCREEN that appears.
This method of pnntmg and saving reports is explained more fully m 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 m 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
prmter, or a dataset - per REPORT statement. For example:
OUTPUT REPORT 1A REPORT 1A PRINT
This OUTPUT statement will send one copy of Report 1A to your terminal screen
and one copy to be pnnted.
PRINT
To pnnt 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 descnbed in Section 8.12, 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 mstructions. You
must then let the system know to which printer you want the output to be routed by
P8-22 IDEA User’s Guide October 22, 1996
-------
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 wifi bring up the SDSF PRIMARY OPTION MENU SCREEN pictured in
Figure 8-9.
ViR3 43 SDSF PRiMARY OPTION MENU
COMMAND INPUT ===> SCRO L ===> PAGE
PREFIX=UID* DEST= ALL) O JNER=*
Type an option or coiimand and press Enter.
LOG - Display the system log
DA -. Display active users of the system.
I - Display jobs n the JES2 input queue
0 - Display jobs n the JES2 output queue
H - Display jobs in the JES2 held output queue
ST - Display status of jobs in the JES2 queues
PP - Display JES2 printers on this syste!r
TWIT - Display JES2 initiators on this system
TUTOR - Short course on SDSF (ISPF only)
END - Exit SDSF
Licensed Materials - Property of 18M
5665-488 (C) Copyright ThM. Corp. 1981, 1992. All rights reserved.
US Government Users Restricted Rights - Use, duplication or
- disclosure restricted by GSA ADP Schedule Contract with IBM corp.
Figure 8-9. SDSF Primary Option Menu Screen
2. Type 0 at the COMMAND prompt and press 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.
Chapter 8. Conducting a Search Using Keywords 8-23
-------
SDSF OUTPUT ALL CLASSES ALL FORMS LINES 802 LII .E 1- (1)
COMMAND NPUT === SCROLL == FADE
N JOONAME o id Dest C Form FCB UCS Writer Tot-Rccs Status Device
U1D24 30807224 R255 A S D 802
Figure 8-10. SDSF Output Queue Screen
3. Press 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 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:
a. Exit IDEA and type ISPF 3.4 at the TSO READY prompt. The
DA TA SET LIST UTILITY SCREEN will appear.
b. Type JUSD.REMOTE.DATA at the DSNAME LEVEL prompt;
press . The DS LIST SCREEN will appear.
c. down and type B (Browse) next to the
JUSD.REMOTE.DATA member. Press to view the list
of remote printers.
8-24 IDEA User’s Guide October 22, 1996
-------
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 ofthe 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.)
. SDSF:OUTPUT ALL CLASSES ALL FORMS LINES O2 COMMAND ISSUED
COMMAND INPUT ===> SOROLL === PAGE
. NP JOBNAME Jobid Dest C Form FCB UCS Writer Tot-Reds Status Device
U1D24 J0807224 R255 A STD 802
Figure 8- 1 1. SDSF Output Queue Screen - “Command Issued”
: SOSF OUTPUT ALL CLASSES ALL LINES 598 LINE I-i (1)
: COMMAND INPUT == > SCROLL ===> PAGE
i NP JOBNAME Jobid Dest C Fcrm FC UCS Writer Tot-Rcds Status Device
U1D24 J0B07224 RMTO A ST [ I 802 R605.P
Figure 8- 12. SDSF Output Queue Screen - Print Destination Changed
Ifyou 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.
Chapter 8. Conducting a Search Using Keywords 8-25
-------
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.
DA TASET
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 lB to an existmg library called QUERY.REPORTS and
you have decided to name the member SEARCH!. Your OUTPUT line would
resemble the following:
OUTPUT REPORT lB 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.10 AddinR Comments to a Query
To identify your query m 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 f
The sequence / makes IDEA ignore anything to the nght of the two characters on
the same line. Comments can appear anywhere m the query on separate comment
lines or on the same Ime with executable IDEA expressions. You may also find this
sequence useful when you are trying to refine queries Instead of deletmg an
8-26 IDEA User’s Guide October 22, 1996
-------
expression from the query, you can lust 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.11 JOB. ROUTE & DD 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 wnte 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 m 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=(l,1)
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
Chapter 8 Conducting a Search Using Keywords 8-27
-------
statements that will be copied from the query mto 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 lB PRINT REPORT 2
INPUT LINKED SELECT (criteria)
//uuuxx JOB (aaaafffff,bbbb) ‘%%IDEA’ ,REGION=2M,PRTY=2,TIME=2,
II MSGLEVEL=(O,O)
/*ROUTE PRINT HOLD
/*JOBPARM LINES=100
where uuu is the User Id, xx is an optional letter or number suffix to help identif ’ the
job in the output queue, aaaa is the account number, fifiFis 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 followmg:
SYSOUT=A , REC FM=VBA, LRECL=259 , BLKS I ZE=23900
IDEA’s provides four DATASET DD statements.
For a new partitioned dataset (PDS):
f/RaaaOUT DD DSN=bbb.bbb(bbb),
DISP=(,CATLG,DCB=(RECFM=VB,LRECL=259,BLKSIZE=23310),
II SPACE=(TRK,(5 0,5O,1O))
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.
For a new non-PDS:
//RaaaOUT DD DSN=bbb.bbb,
DISP=(,CATLG,DCB=(RECFM=VB,LRECL=259,BLKSIZE=23310),
1/ SPACE=(TRK,(50,50))
For an existing PDS:
8-28 IDEA User’s Guide October 22, 1996
-------
//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 DATASET. 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 lB DD=REPTO1 REPORT 2
INPUT LINKED SELECT (criteria)
//REPTO1 DD UNIT=DISK,DSN=uuuaaaa.dataset(myreport) ,DISP=(,CATLG),
II sPACE=(TRK,(le,1e,3) ,RECFM=VBA,LRECL=259,BLKSIZE=23476
8.12 Ruirninji a Keyword Ouerv
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 or to
move the cursor to the COMMAND prompt; type GO followed by .
From here, IDEA processes the query and then presents the QUERY STATUS
SCREEN, shown below in Figure 8-13.
Chapter 8 Conducting a Search Using Keywords 8-29
-------
- QUERY STATJS SCREEN - - --
COMMAND ===>
13:34:3 6.34 - 5 Facilities se 1 ected aid in FINDS
Counts (percentages, by database, of faciiities selected but
excluded because they were not presen in FINDS:
AFS 60 ( 35) PCS 134! ( 70)
RCR 0( 0) TRI 0( 0)
IN..: ( 0)
Press ENTER to continue, END to return to start
Figure 8-13. Query Status Screen
If you are satisfied with the number of facilities that your query has turned up then
press 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.12.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, FF8 to page
down, PF1O 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-30 IDEA User’s Guide October 22, 1996
-------
BROWSE - Report: 1A - In Progress MAX:090023 LIME 80000800 cOL 00 880
COMMAND ===>
Issue conrnan PRINTO to print, or SAVE t save to dataset.
******t **t** ****t******k******* TOP OF DATA
1 ILS. ENVIRONMENTAL PROTEC
• ‘T ATEO DATA FACILiTY SPE TFTr Co
FINDS Id: •CADE8L uc. wue. - LAG r O city:
• Address: .2401 BAY SHORE BLVD Zip: 94134
RCRIS Handler Id: cA0009111212 Year .No.Eval. No.NOVs No.
Name: SCHLAGE LOCK CO CY92 :0 0
ISO Facility Status: HP NO CY93 0 0
Owner Operator Type: P Exist. Date: cY94 0 0
TRI Id: 4i34SCHLG2401B Facility Name: SC:HLAGE LOCK CO.
Y Chem count Lbs: NP Air Pt Air Water UG Inj. Land P01W Off-
i 2 2 13255 5 0 0 0 0 8
UUHS Nunther: 9111212 Name: ScHLAGZ LOCK COMPANY Started in 1q74
Figure 8-14. Report 1A (Browse Mode)
8.13 Exitinj r Keywords
To exit Keywords at any time, use one of the procedures listed below.
• 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 wifi be
saved). 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 X at the COMMAND line to go directly to the TSO READY prompt
(your work will be saved automatically).
8-31
Chapter 8. Conducting a Search Using Keywords
-------
8.14 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.
EDIT ---- UI AC T.GJER T .SPECS(EXAMPLE) COLUMNS O O7
OMM D ===> SCROLL == PAGE
****** ************ ** ** c * ** TOP OF DATA ************* *** ************
800BO1 OUTPUT REPORT lB REPORT SUMMARV /* REPJRT 1A AND SUMMARY /*
000002 INPUT LINKED /* LINKED /*
000003 SELECT
008004 RcR. LSTATE PA / CR PENNSYLVANIA /*
000005 AND
008806 TRI.TcID=00 0 108883 / TOLUENE TRI ID # /
009 07 AND
008008 RO•R.WAMTT GT 10580 / RCR WASTE AMOUNTS /*
ooeoog
000810 / END OF QUERY /*
****** ************************* ** BOTTOM OF DATA **********************.******
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 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 Boolean-operator data-value
8-32 IDEA User’s Guide October 22, 1996
-------
3. Provide an OUTPUT statement after the SELECT statement by typing OUTPUT
followed by REPORT and a report name: 1A, 1B, 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-33
-------
8-34 IDEA User’s Guide October 22, 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.
EDIT ---- U1DACCT. UERY.SPECS(GP) GOLUMNS 001 872
COMMAND ===> SCROLL = = PAGE
****** ***************************** TOP OF DATA
000001 /* 930813 1448 Names Search found 3 names. /
088802 / Name: GEORGIA-PACIFIC *1
008803 / StC: GA121 ‘
000894 OUTPUT RE°ORT 1A
008805 INPUT LINKED
900006 SELECT IIN.EPID=
L..0 08 007 GAD 84273110., /* GEORGIA PACIFIC CORPORATION (NED) */
000888 f 133 PEACHTREE, NE *1
008089 /* ATLANTA GA 38303 04
000810 / GEORGIA-PAcIFIC CORPORATION (DUN) /
008011 /* 133 PEACHTREE ST NE *1
800812 f GA 30303 04 121 */
008013 /* 133 PEACHTREE RD (F
@00814 /* 30334 */
000015 GAD984306910 /* GEORGIA PACIFIC CORP (R R /
908016 /‘ 1460 ELLSWORTH IND DR *1
000017 /* ATLANTA GA 30325 84 121 */
@80918 /* 1468 ELLSWORTH INDUST DR (F
****** BUTTON OF DATA *************** ***** ****
Figure 9-1. Edit Screen
Chapter 9. Managing Keyword Queries and the ISPF Editor 9-1
-------
9.2 Keyword Oueries and the ISPF Line Editor
Table 9-I lists the most common JSPF Line Edit Commands. Each command will be
discussed in the sections below. Lme 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 msert 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 9-1. Line Edit Commands
I Insert a line
D Delete th.is line
C Copy this line
M Move this line
R Repeat this line
A Place after this line
B 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.
in Insert n lines (where n is an integer between 1 and 99999) following this line.
I. Use the arrow keys or to place the cursor at the left most character of
the line number.
2. Type I and press 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 two tunes 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
. The new lines will be without numbers; ISPF will fill in the numbers
when you press .
Commands for Deleting Lmes
9-2 IDEA User’s Guide October 22, 1996
-------
D Delete this line.
Dn 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 to place the cursor under the left most character
of the line number you want to delete.
2. Type D and press 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 . 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
or the arrow keys to move to the last line to be deleted, type DD and press
. 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 I and 99999)
After this line.
B Place Before this line
Bn Repeat the copy or move n times (where n is an mteger between I and 99999)
Before this line.
Copying Lines
C Copy this line.
Cn 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 imes of your query, you must tell ISPF winch 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 to place the cursor under the left most character
of the line number you want to copy.
2. Type C and press . The hne 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 to position the cursor at the destina-
tion. Type A for After or B for Before and press 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 mcludmg the line the cursor is on) and
press . The lines will be held m memory and a message will be dis-
played m the top nght corner of the screen announcing MOVE/COPY IS
PENDING. Use the arrow keys or to position the cursor at the destina-
tion location. Type A for After or B for Before and press to complete
the copy.
Alternatively, to copy a block of lines, type CC on the first line of the block to be
copied. Press or the arrow keys to move to the last line of the block to
be copied. Type CC and press . The lines will be held in memory and a
message will be displayed m the top right corner of the screen announcing
MOVE/COPY IS PENDING. Use the arrow keys or to position the
cursor at the destination location. Type A for After or B for Before and press
to complete the copy.
Moving Lines
M Move this line.
Mn Move n lines (where n is an mteger between 1 and 99999).
MM Identifies the first and last tines 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 to place the cursor under the left most character
of the line number you want to move.
2. Type M and press . The line will be held in memory and a message will
be displayed in the top nght corner of the screen announcing MOVE/COPY IS
PENDING. Use the arrow keys or to position the cursor at the destma-
9-4 IDEA User’s Guide October 22, 1996
-------
tion. Type A for After or B for Before and press to complete the
move.
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 mcludmg the line the cursor is on) and
press . The lines will be held in memory and a message will be dis-
played in the top nght corner of the screen announcmg MOVE/COPY IS
PENDING. Use the arrow keys or to position the cursor at the destina-
tion location. Type A for After or B for Before and press to complete
the move.
Alternatively, to move a block of knes, type MM on the first line of the block to
be moved. Press or the arrow keys to move to the last line of the block
to be moved. Type MM and press . The lines will be held in memory
and a message will be displayed in the top nght corner of the screen announcing
MOVE/COPY IS PENDING. Use the arrow keys or to position the
cursor at the destination location. Type A for After or B for Before and press
to complete the move.
Repeating Lines
R Repeat this line.
Rn Repeat this line n times (where n is an integer between 1 and 99999).
RR Repeat a block of lines.
RRn 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 duphcate a line or group of lines.
1. Use the arrow keys or to place the cursor under the left most character
of the line number you want to repeat.
2. Type R and press . 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
w ’nt to duplicate the line, (e.g., type R8 to repeat one line, eight times) and press
.
4 To repeat a block of lines, type RR on the first line of the block to be repeated.
Press or the arrow keys to move to the last line of’ the block to be
repeated. Type RR and press . 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.
Fn 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 n is an integer between I 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:
eeeei
eeoe 17
xOeOl8 /* This single line will be excluded.
OR
xx0007 /* This block of lines 7 through 14
eoeeos /* will be excluded.
008013
xxOO 14
000815
9-6 IDEA User’s Guide October 22, 1996
-------
Figure 9-2 shows the results of excluding lines 7 - 14 and line 18 from the query
in Figure 9-1.
• EDIT ---- UIDACcT.QUERY.SPECS(GP) COLUMNS 901 072
COMMAND ===> SCROLL PAGE
****** * ******k**-****k******k*** TOP OF DATA ******** **************- **
009001 / 930Q25 1411 Nanies Search founu 3 na s. /
000802 / Name: GEORGIA-PACIFIC /
009003 / StC: DM21 /
000004 OUTPUT REPORT IA
000805 INPUT LINKED
080805 SELECT FIN. EPLD
B LINE(S .NOT DISPLAYED
000815 GAD98430691 8 /* GEORGIA pACIFIC CORP RGR) /
00G0l / 1450 ELLSWORTH IND DR
000817 / ATt ANTA GA 30325 04 121 */
I LINE(S) NOT DISPLAYED
** *** ** * *** ********** BOTTOM OF DATA ** *********i¼*k *********
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.
000006
F 8 LINE(S) NOT DISPLAYED
000015
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 8LINE(S)NOTDISPLAYED
000015
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 8 LINE(S) NOT DISPLAYED
000015
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 8 LINE(S) NOT DISPLAYED
080016
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 identif ’ 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 Ime.
9.3 Usi,w ISPF Primary Commands
Primary commands are entered at the COMMAND prompt at the top of the JSPF
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 I SPF primary edit commands. The com-
mands that are marked with an astensk ( ‘ ) are explained more fully in Sections 9.3.2,
Combining Queries - 9.3.5, Scrolling Data.
9-8 IDEA User’s Guide October 22, 1996
-------
Table 9-2. Primary Edit Commands
Command
Function Key
Description
CANCEL (CAN)
Returns to previous screen without saving any
changes
CHANGE (CHG) (C)
Replace the specified string with another string
COPY (*)
Dupheates lines from another member into the
current member
CUT (*)
Places selected hnes into a paste buffer (lines are
selected with the C line edit command
DELETE (DEL) ()
Deletes lines from the display
DOWN(*)
PF8/PF2O
Scrolls down by the amount set at the SCROLL
or COMMAND prompt.
END
PF3JPF15
Saves Changes and returns to the previous
screen
EXCLUDE (EX)
Excludes lines from the display
FIND (F)
Finds the specified string
GO
Instructs IDEA to run a query
HELP
PF1/PF13
Displays information about the current ISPF
screen
LEFT ()
PF1O/PF22
Scrolls left by the amount set at the SCROLL or
COMMAND prompt.
MOVE
Moves the contents of an entire member into
the current member and deletes the moved
member
PASTE (‘)
Place selected lines from buffer to specified
location (which is specified using the line edit
commands A (After) or B (Before)).
RESET (RES)
Clean-up the edit display
RETURN
PF4/PFI6
Returns directly to the previous Primary Option
Menu.
RCHANGE
PF6/PF18
Repeats the previous CHANGE command
RFIND
PFS/PF17
Repeats the previous FIND command.
RIGHT (*)
PF1 1/PF23
Scrolls right by the amount set at the SCROLL
or COMMAND prompt.
RETRIEVE
PF12/PF24
Moves the cursor to the first input field on the
screen and retrieves the last command entered
SAVE
Saves changes to the current screen (without
exiting)
SPLIT
PF2/PFI4
Splits the screen into two sessions
SWAP
UI-’ ()
PF9JPF21
Moves the cursor from one session to the other
in the split screen mode
PF7/PF19
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 wrltmg, 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 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 mcludmg the line the cursor is on).
The lines you are copying will remam intact in the onginal 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 or key to place the cursor at the COMMAND
prompt. Type CUT followed by and ISPF will copy the line(s) mto 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 mto the paste buffer. When another range of lines is added to the buffer,
the message n Plus n Lmes Cut (n = any number) appears at the top nght 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 October 22, 1996
-------
5. Use the or key to place the cursor at the COMMAND
prompt. Type PASTE followed by and the copied lines will appear in
the location you selected.
93.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 quenes
will be in the same hbrary (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 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 or key to place the cursor at the COMMAND
prompt. Type COPY followed by a and the member (query) name that
you want to copy. Press and the copied query will appear in the
location you selected.
933 Deleting Excluded or Non-Excluded Lines
The DELETE command is used to delete hnes 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.
I Use the arrow keys or 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 .
9.3.5 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) move toward the top of the data
DOWN (PF8/PF2O) move toward the bottom of the data
LEFT (PF1O/PF22) move toward the first column of the data
RIGHT (PF11/PF23) 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
EDIT ---- U1DACcT.OUERY.SPECS(GP) -. - -• COLUMNS
0MMAND => SCROLL = PAGE
k***k* ** *** **;¼ * ** ******* ** TOP OF DATA ****k*-*** ct**
000901 / 938812 144.8 Names Search found 3 names.. /
900802 / Name: GEORGIA-PACIFIC /
000903 /* StO: GA121 /
$08004 OUTPUT REPORT 1A
808905 INPUT LINKED
00090.6 SELECT FJLEPID=
008907 GAD984273110. /* GEORGIA PACIFIC CORPORATION /
008008 / 133 PEACHTREE, NE
000999 /* ATLANTA GA 30303 04
000010 /* GEORGIA-PACIFIC CORPORATION ( DUN) /
000811 / 133 PEACHTREE ST NE
008012 /* AT_Ar4TA GA 30303 04 121 */
D00913 / ‘ 133 PEACHTREE RD (F
000014 38334 */
000015 GA09843069 10 J GEORGIA PACIFIC CORP (RCR) *1
008016 /* 1460 ELLSWORTF. IND OR
900817 / ATLANTA GA 30325 94 121 /
000018 j 1460 ELLSWORTH 1NDUST DR (F
BOTTOM OF DATA
Figure 9-3. Edit Screen With Scroll Prompt
9-12 IDEA User’s Guide October 22, 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 followmg 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 (n between 1 and 9999).
MAX (M) Scroll to the top, bottom, left, or nght margm.
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 mmus one column when scrolling
left or right.
For scrolling purposes, a “page” is the amount of data currently visible on the screen.
In spht 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 ovemde 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 (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 .
Generally, you can combine scrollmg with other actions by entering a command and
then pressmg a scroll PF key (instead of the 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 quenes. 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. Smgle char-
acter commands operate on a line (e.g., C to copy a line, I to msert 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 copymg lines from other quenes.
9-14 IDEA User’s Guide October 22, 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 Choosinj. a Standard ReDort Format
IDEA reports are standard in the sense that the report formats and the type of infor-
mation presented m them are predetermined. In other words, a query defines cntena
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 enable users to create customized
reports.
IDEA currently allows users to choose from among four standard report formats.
Reports 1A and lB hst 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 IA
Report 1A provides a brief descnption of the facilities selected by your query. The
organization of the information m this report differs for Linked, Nonlinked, and
Linked nonlinked queries. In short, Linked quenes return information orgamzed by
facility whereas Nonlinked quenes return information organized by the databases
from which the mformation was retneved. Linked Nonlmked searches return reports
including combinations of both.
Linked
When running a Linked query, the information m Report 1A is organized mto two
components the facility headmg 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 facthty 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 facthty 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 Nonhnked 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 m 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 Nonhnked will generate a two part report. The first part is
organized in the Linked format descnbed above and contams information on facilities
with valid FINDS identification numbers that match all of the selection cntena. The
second part is organized in the Nonlmked format described above and contains infor-
mation on facilities without valid FINDS identification numbers that match any
selection cntena.
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 mdustnes.
(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 October 22, 1996
-------
U.S. ENVIRONMENTAL PROTECTION AGENCY 08/26/93 Page
INTEGRATED DATA FACILITY—SPECIFIC COMPLIANCE PROFILE REPORT 1A
4 4 + + + I. + + + + + + +___
FINDS Id: AL0008162950 Fac. Name: ALUMINUM COMPANY OF AMERICA AL City: MOBILE State: AL
Address: ALABAMA STATE DOCKS BLVD Zip: 36601 Let: 30.719 Long: 88.042
RCRIS Handler Id: AL0008162950 Year No.Eval. No.NOVs No.AAs No.JAs HPV
Name: ALABAMA STATE DOCKS BLVD CV91 2 1 0 0 V
TSD Facility Status: X CY92 3 0 0 0 V
Darner Operator Type: P CY93 3 1 0 0 V
Current HPV? YES CV94 2 3 0 0 V
Existence Date: 1980/05 CY95 3 1 0 0 V
CY96 4 1 0 0 V
PCS Permit No: AL8002976 Issue Date: 1990/10 Year All Viols Eff.Viols Inspections No.NOV5 No.AAs No.JAs
Fac. Name: AL STATE DOCKS / MUD LAXES CV91 0 0 1 0 0 0
Active Minor Discharger CV92 0 0 8 0 0 0
Expired Date: 1995/10 CV93 0 0 1 0 0 0
AFS CDS Plant ID: 0109708003 Plant Maine: ALUMINUN CORP OF AK. Year No.Insp. No.NOV5 No.AA5 No.JAs
Source Compl. Status Air Program Desc. Qtrly Compl Status 1991 3 0 0 0
IN COMPLIANCE - INSPECTION SIP SOURCE 33333333 1992 2 0 0 0
1993 1 0 0 0
DUNS Number: 8162950 Ult: 1339472 Status: Branch Subsidiary 7 No
Business: Aluminum Company of America Hierarchy Level. 1 Started in
Sales Volume: $ Hfg 7 No SIC Code(s): 5169
+ 4 + + + + + + + + + +
FINDS Id: ALDO31618069 Fac. Name: HOWORAY ENGINEERING COMPANY IN City GREENVILLE State: AL
Address: JCT OF 300 BEELAND & 2ND ST Zip: Let: 34.993 Long: 85.308
Civil Docket Case Name Case Number Type Case Law Ovrall Sta. Initiated To DOJ Filed Concluded
NORMAN PARKER/HOWBRAV ENGINEERO4-86—9034 BNK CERCLA CASE CLOSED 1986106 1989/01
Civil Docket Case Name Case Number Type Case Law Ovrall Ste. Initiated To DO.) Filed Concluded
ALABAMA POWER (HOWBRAV ENGINEEB4-89—0835 CIV CERCLA CONCLUDED 1990/12 1991/05
CERCLIS Site Name: HOWBRAY ENGINEERING CO Cal Year 1990 1991 1992 1993
NPL Status: F No. Admin. Actions: 0 0 0 0
Site Classification: No. Judic. Actions: 6 0 0 0
Figure 10-1. IDEA Standard Report IA
Report 1A provides cryptic information about the facilitIes selected by your query.
Sample IA reports for each IDEA data system are given below. The report field
name is shown in hold followed by its descnption, the name of the data element used
(in parentheses), and a list of possible values, where appropnate.
Chapter 10 IDEA Standard Reports 10-3
-------
10.1 .1 .1 AFS Report JA Elements
1.
AFS COS
Plant
ID: 8189708003 Plant Nane:
ALUHINUN CORP OF
All.
Year
No.insp.
No.NDVs
No.AAs
No.JAs
2.
Source
Compl.
Status
Air Program
Desc. Qtrly Compi Status
1991
3
0
0
0
IN CDHPLIANCE — INSPECTION
SIP
SOURCE
33333333
1992
1993
2
1
0
0
0
0
0
0
Figure 10-2. AFS Report IA Fiemcnts
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.ANT1 with IA, 2A, 5C or 6C
and AFS.DTA i in the appropnate calender year)
No. NOVs Number of Notices of Violation (NOVs). (A count of AFS.ANT1 with
6A or 7C and AFS.DTA I in the appropnate calender year)
No. AAs Number of Administrative Actions. (A count of AFS.ANTI with 1B, 28,
3B, 7E, 8A, 8C, or 9A and AFS.DTA1 in the appropnate calender year)
No. JAs Number of Judicial Actions. (A count of AFS.ANT1 with 1D, lE, 2D, 4B,
5B, 6B, or 9C and AFS.DTAI m the appropriate calender year)
LINE 2
Source Compl. Status EPA Plant/Point Comphance Status -- a one character code
indicating whether a plant or point is m compliance, not in comphance, or
has an unknown compliance status. This field is used when an EPA Com-
pliance status value differs from the comphance status value submitted by a
10-4 IDEA User’s Guide October 22, 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 mamtamed on the plant AIR program pollutant records. (AFS.DCSI)
(possible values)
Unknown compliance status
in violation - no schedule
in compliance - source test
in compliance - mspect lon
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
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 Trackmg
PSD
NSR
NESHAP
NSPS
Qtrly Compi 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 Pr cedural Compliance
B In Violation With Regard To Both Emissions And Procedures
C In Comphance With Procedural Requirements
M In Compliance - CEMS
W In Violation With Regard To Procedural Compliance
V Unknown With Regard To Both Emissions And Procedural Co
0 Unknown Compliance Status
I 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
No Applicable State Regulation
9 In Compliance - Shut Down
10-6 IDEA User’s Guide October 22, 1996
-------
10.1 .1 .2 CER (CERCLJS) Report IA Elements
1. CERCL1S Site NameS NOWBRAY ENGINEERING CO Cal Year 1990 1991 1992 1993
2. NPL Status: F No. Adam. Actions: 0 0 0 0
3. Site Classification: No. Judmc. Actions 0 0 0 0
Figure 10-3. CER (CERCLIS) Report IA Elements
LINE 1
Site Name The official site name for a hazardous waste site or an unanticipated
removal (mcident). 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 Pnorities 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 NotonNPL
0 Not vahd 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 AdmLmstrative Actions. (A count of CER.1732 with
AC, AV, CA, FL, RR, SO, or UA and CER.l716 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 determmed by the region after the completion of a PRP
search. (CER.0226)
F Fund lead
FE Federal enforcement
ND No determination
NC 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 appropnate calender
year, or CER.1732 with JG or TE and CER.1717 m that year.)
10-8 IDEA User’s Guide October 22, 1996
-------
10.1 .1 .3 DCK (Civil Docket) Report JA Elements
Civil Docket Case Name Case Number Type Case Law Ovrall Sta. Initiated To 00. ) Filed Concluded
NORMAN PARKER/MOWBRAV ENGINEER 04—86—0034 BNIK CERCLA CASE CLOSED 1986/06 1989/01
Figure 10-4. DCK (Civil Docket) Report IA 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 Civii
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 penalty order
106 CERCLA 106 (AO) for response action
107L CERCLA 107L filing of hen
109A CERCLA 109A Class I AO for penalties
109B CERCLA 109B CLASS 11 AO for penalties
11005 MWTA 11005 compliance and penalty order
113 CAA 113 Notice of Violation
I 13A CAA 1 13A Admin Order (AO)
I 13D CAA 1 13D 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 Adrnin Demminns cost recov settlement
122H CERCLA 122H Adinin Order for cost recovery
13 F IFRA I3SSURorder
14 FIFRA 14 (AO) for comp and penalties
14 14G2 SDWA 1414 PWS comp order 1st time
14 14G3 SDWA 1414 PWS (AO) for compliance
Law A code indicatmg the laws under which the case is proceedmg.
(DCK.LAWS)
AKA Anti-Kickback Act
APA Administrative Procedures Act
ATA Anti-Trust Act
BANKR Bankruptcy
CAA Clean Air Act
CAAEM CAA mobile, enussions
CAA IN CAA mobile, inspection
CAARE CAA mobile, recall
CAATA CAA mobile, tampering
CAAVA CAA mobile, vapor
CBRA Coastal Bamer 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 October 22, 1996
-------
CZMA Coastal Zone Management Act
CIODI Know making false stmts
C 1341 Mail fraud
C 1505 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 I-latch 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 & Sanc Act
MV ICS Motor Vehicle Info. And Cost Savings Act
MWTA Medical Waste Tracking Act
NCA Noise Control Act
NEPA National Environmt Policy Act
NHPA National Histonc Preservation Act
0TH Other
PA Privacy Act
PFCRA Program Fraud Civil Remedies Act
RCRA Res. Conserv, & Rec. Act
REFA Rivers & Harbor Act, 1899
RFA Regulatory Flexibility Act
RFPA Right to Financial Privacy Act
SARA Superfund Amendment and Reauthonzation 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
4OCFR 4OCFR
Chapter 10 IDEA Standard Reports 10-11
-------
Overall Sta. A code and corresponding descnption indicating how far the case has
progressed. (DCK.OSTA)
CASE CLOSED Case closed
OPENED Opened
PRN PRN
RET TO REG Returned to region
TAKEN Taken
AT EPA HQ At EPA-l-IQ
AT DOJ At DOJ
ATUSATFY AtUSATTY
FILED CRT Filed in court
CONCLUDED 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 October 22, 1996
-------
10.1 .1 .4 DUN (Dun & Bradstreet) Report IA Elements
DUNS Number: 8162950 Ult: 1339472 Status: Branch Subsidiary’ No
Business: Aluminum Company of iierica Hierarchy Level: 1 Started in
Sales Volume: S Hfg’ No SIC Code(s): 5169
Figure 10-5. DUN (Dun & Bradstreet) Report IA Elemenis
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)
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 DUNSUBI3
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.
LINE 3
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 manufactunng is done at this address.(DUN.MFGI)
Yes DUN MFGIO
No DUN.MFGI1
SIC Code(s) The Standard Industnal Classification (SIC) Code system categonzes
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 October 22, 1996
-------
10.1 .1 .5 ERN (ERNS) Report IA Elements
1. ERNS Discharger Id:
TX00266633
Spills --
last five years: 2
2.
Discharger: EXXON
CO USA
host recent: 05/19/92
3.
Deaths:
lnjuries
1 Evacuations:
Daniages. 510000
Figure 1O- . RN (ERNS)
Report IA Elements
LINE 1
ERNS Discharger Id A unique number for the ERNS Discharger (ERN.OWNID).
IDEA denves this number from the ERNS 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 orgamzation (ERN.DORG)
Most recent Date of the most recent incident for this Discharger, (ERN.DTSPI)
LINE 3
Deaths The total number of fatahties resultmg from releases for this Discharger.
(ERN.DEATHS)
Injuries The total number of mjunes resultmg from releases for this Discharger.
(ERN. INJS)
Evacuations The total number of evacuation resultmg 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 mdication that damages
occurred (ERN.DAMAGES). 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 October 22, 1996
-------
10.1 .1 .6 FF1 (FFJS) Report íA Elements
Federal
Facility Id:
AL-680030926
Nanie: EASTERN ENVIRONMENTAL Addr: 1504 A AVE MONTGOMERY
Figure
10-7. F
Fl (FFIS
) Report IA 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 1 0-17
-------
10.1.1.7 FIN (FINDS) Report JA Elements
1. FINDS Id: AL0688162950 Fec. Name: ALUMINUM COMPANY OF AMERICA AL City: MOBILE State: AL
2. Address: ALABAMA STATE DOCKS BLVD Zip: 36601 Let: 30.719 Long: 88.042
Figure 10-8. FIN (FINDS) Report IA Elements
LINE I
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 m degrees. (FIN.LONG)
10-18 IDEA User’s Guide October 22, 1996
-------
10.1 .1 .8 LST (Contractor Listing Docket) Report JA Elements
1.
LST Case Number: 02—91-Le34
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, 0.
Figure 10-9. LST (Contractor Lasting Docket) Report IA 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 hsting 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 listmg
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 mformation 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 mmatmg 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 October 22, 1996
-------
10.1.1.9 NCD (NCDB) Report L4 Elements
1.
NCDB
Site Name:
ALUMINUM CO OF
AHERICA-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 1
0
0
0
TSCA
Figure 10-10. NCD (NCDR) Report IA 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 Broker
CV Conveyor
DA Permitted Disposer - Alternative Methods
DH Permitted Disposer - High Efficiency Boilers
D I Permitted Disposer - Incinerator
DL Permitted Disposer - Landfill
DM Permitted Disposer - Dredge/Sludge Material
DP Disposer
DR Permitted Disposer - Research/Develop
DT Distributor
LB Laboratory
Ml Manufacturer/importer
MN Manufacturer
PC Processor
PS Secondary Processor
PT Port of Entry
ST Storer
US User
Pesticide Estab Number Pesticide producer establishment number -- the EPA registra-
tion number identifymg 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 mdustnal classification (SIC) codes.
(NCD.SICLIST)
LINE 3
Respondent Name The name of the respondent. (NCD.NAME with
NCD.NAMETYP = ‘RESPOND’)
LINEs 4 & 5
10-22 IDEA User’s Guide October 22, 1996
-------
YEAR Calendar year. (based on NCD.INSPDTE, NCD.REFDATE,
NCD.MAISSUE, or NCD.AOISUUE)
No. of Inspections Number of mspections. (Count of NCD.INSPDTE’s (date of
inspection.)
No. of NONS Number of Notices of Noncompliance. (Count of NCD.ACTNTYP =
‘NON’ and NCD.MAISSUE or NCD.AOISSUE m the given calender year,
or NCD.IACTNTY = ‘NON’ and NCD.INSPDTE in the given calender
year.)
No. of Adm Act Number of Admimstrative Actions. (Count of NCD.ACTNTYP
starting wh ‘C’, excluding ‘CCR’, and NCD.MAISSUE or NCD.AOISSUE
m the given calender year, or NCD.IACTNTY starting with ‘C’, excludmg
‘CCR’, and NCD.INSPDTE m 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 OSI-! Report IA Elements
1.
OSHA Activity
Link: CA
111765970
Inspections ——
last
five years
2.
Name: INSERT
FACILITY NAME
HERE
Health:
0
Penalties:
SO
3.
Employees at
site:
60
Safety:
1
Violations:
0
4.
Lost Workday
injury Rate:
0.00
Serious
Violations:
0
Figure 10-il. OSH Report IA Fietnents
LINE 1
OSHA Activity Link An IDEA denved 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 imuta-
tions m 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 m 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)
LINE 3
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 m 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 October 22, 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 senous violations cited on inspections con-
ducted in the last five years. (sum of OSH.SRVIOLS for mspections with
OSH.DTOPEN in the last five years)
Chapter 10 IDEA Standard Reports 10-25
-------
10.1 .1 .1 1 PCS Report JA Elements
1. PCS Pennit
No:
AL 8 2976 Issue
Date:
1990/10
Year All Viols
Eff.Viols
Inspections
No.NOV5
No.AAs
No.JAs
2.
Fac. Name: AL
STATE DOCKS / HUD LAKES
CY91
0
0
1
0
0
0
3.
Active
Hinor Discharger
CY92
0
0
0
0
0
0
4.
Expired
Date:
1995/10
CY93
0
0
1
0
0
0
Figure 10-12. Cs Report IA Elements
LINE I
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-
pnate calender year with a PCS.MVIO present.)
Elf. Viols Number of effluent violations. (A count of PCS.MVDT dates m the appro-
pnate calender year with a PCS.MVIO equal to E90 (Numenc Violation).)
Inspections Number of mspections. (A count of PCS.INSPDTE (mspection dates) m
the appropnate calender year.)
No. NOVs Number of Notices of Violations (NOVs). (A count of PCS.ENAC with 20
or 83 and PCS.ENDT m the appropnate calender year.)
No. AAs Number of Administrative Actions (AAs). (A count of PCS.ENAC with
AA, AC, AE, AF, Al, A3, A5, 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 m the appropnate calender
year
LINE 2
10-26 IDEA User’s Guide October 22, 1996
-------
Fac. Name The name of the entity located at the facility’s physical address.
(PCS.NAM 1)
LINE 3
Active Active/Inactive discharger mdicator. (PCS. IACC)
Minor Discharger Major/Mmor discharger mdicator. (PCS.MADI)
LINE 4
Expired Date The date the this permit will expire. (PCS.PTAC with PCS.PTEV equal
to ‘P5099’.)
Chapter 10 IDEA Standard Reports 10-27
-------
10.1.1.12 RCR (RCRJS) Report JA Elements
1.RCRIS Handler Id: H1D800722686
Year
No.Eval.
No.NOVs
No.AAs
No.JAs
HPV’
2.
Name: SAFETY KLEEN CORP
4—055—01
CY9I
2
1
0
0
Y
3.
TSD Facility Status: X
CY92
3
0
0
0
V
4.
mer Operator Type: P
CY93
3
1
0
0
Y
5.
Current HPV? YES
CY94
2
3
0
0
V
6.
Existence Date: 1980/05
CY95
CY96
3
4
1
1
0
0
0
0
V
Y
Figure 10-13. RCR (RCRIS) Report IA Elements
LINE 1
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 appropnate 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 m the appropnate
calender year.)
No. JAs Number of Judicial Actions. (A count of RCR.ENFTYPE with values m
the range from 400 to 699 with RCR.EDATE in the appropriate calender
year.)
HPV? A flag mdicating whether the handler was a high priority violator during
the appropnate calender year. (Indicates the existence of a
RCR.VDTEDET with RCR.VPRTY =9 prior to or dunng the appropriate
calender year, with RCR.VACTDTE either not present, or during, or after
the end of the given calender year.)
LINE 2
10-28 IDEA User’s Guide October 22, 1996
-------
Name Handler name m RCRIS. (RCR.NAME)
LINE 3
TSD Facility Status A code indicating that the handler is engaged m 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 m TSD. unverified
LINE 4
Owner Operator Type A code mdicatmg the owner/operator type. (RCR.COTYPE)
F Federal
S State
P Private
I Indian
C County
M Municipal
D District
o Other
LINE 5
Current HPV? Whether or not the facility is a High Pnonty Violator (HPV). (based
on RCR.CPVIOL, a data element derived using RCR.VDTEDET,
RCR.VACTDTE, and RCR.VPRTY)
LINE 6
Existence 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 JA Elements
1. TR1 Id: 528O8LHNNCHIGHW Facility Name: ALCOA
2. YR Chem Count Lbs:NP Air Pt Air Water UG Inj. Land P01W Off-Site Total Recovd
1991 17 195305 1870980 3270 0 750 0 175720 2245945 723276
Figure 10-14. TRI Report IA Elements
LINE 1
Id TRI facility identifier. A generated facility identification usmg facility
name, address, and ZIP code. (TRI.TFID)
Facility Name The name of the facility. (TRI.HNME)
LINE 2
YR The reportmg year. (TRI.RPYR)
Chem Count Number of chemicals released by the facility. (count of TRI.TCID’s)
Lbs: Indicates that the values for the followmg fields are in lbs.
NP Air Amount of non-point source emissions to the air. (based on TRI.MREST’s
with TRI.CREL= I)
Pt Air Amount of point source emissions to the air. (based on TRI.M REST’s with
TRI.CREL= 2)
Water Amount released to water. (based on TRI.M REST’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 (P01W). (based on
TRI.M REST’s with TRI.CREL= 6 or 8)
10-30 IDEA User’s Guide October 22, 1996
-------
Off-Site Amount disposed of off-site, not mcludmg amounts recycled or recovered.
(based on TRI.M REST’s with TRI.CREL= 7, with TRI.TRMT not equal
to M20, M24, M26, M28, M93, M56, or M92)
Total The sum of the amounts from the release media cited in the chart: NP Air,
Pt Air, Water, UG lnj., Land, POTW, and Off-Site. (sum of
TRI. M REST’s)
Recov’d The amount recycled or recovered. (based on TRI.M REST’s with
TRI.CREL= 7, with TRI.TRMT = M20, M24, M26, M28, M93, M56, or
M 92)
10.1.2 Report lB
Report lB provides a detailed descnption of the facilities selected by your query. The
organization of the information m this report differs for Linked, Nonhnked, and
Linked nonhnked quenes. Lmked queries return mformauon organized by facility
whereas nonhnked quenes return information organized by the databases from which
the information was retneved. Lmked Nonlinked searches return a combination of
both.
Linked
When running a Linked query, the information in Report lB is organized into two
components: the facility heading and database mformation. Withm 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 mformation from the individual data-
bases. In Report 1B, 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.
Non/inked
A Nonhnked query returns information only from the databases addressed by your
query. Report lB contains the following: the database name, the name for the
Chapter 10 IDEA Standard Reports 10-31
-------
facility within the database, the identification number for the facility withm 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.
Linked Nonlinked
There are two parts to the Report lB format resultmg from a Linked Nonhnked
query. The first part is organized in the Linked format described above and contains
infonnation on facilities with valid FINDS identification numbers that match all of
the selection criteria. The second part is organized in the Nonlmked 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 industnes.
Note: this is the same example used m Section 10.1.1, Report JA.
10-32 IDEA User’s Guide October 22, 1996
-------
U.S. ENVIRONMENTAL PROTECTION AGENCY 08/26/93 Page
INTEGRATED DATA FACILITY-SPECIFIC COMPLIANCE PROFILE REPORT lB
+ + 4 + + + + + 4—-
FINDS Id: ALD0O8162958 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) Suninary
Handler ID: ALD008162950 Handler Name: ALUMINUM CO OF AMERICA Address: ALABAMA STATE DOCK RD
City: MOBILE County: AL097 State: AL Zip: 36652
Sic code(s): 3334 2819
Owners(s)/Operator(s) Name Owner/Operator Indicator
OWNERNAHE CO
OPERNAME CP
Generator Indicator: 1 Transporter Indicator: TSD Indicator: Source: N
RCRIS Handler Id: AL0008162950 Year No.Eval. No.NOVs No.AAs No.JAs HPV
Name: ALUMINUM CO OF AMERICA CY91 2 1 0 0 Y
TSO Facility Status: X CY92 3 0 0 0 Y
Dimer Operator Type: P CY93 3 1 0 0 Y
Current HPV YES CY94 2 3 0 0 Y
Existence Date: 1980/05 CY95 3 1 0 0 Y
CY96 4 1 0 0 Y
U.S. ENVIRONMENTAL PROTECTION AGENCY 08/26/93 Page 2
INTEGRATED DATA FACILITY-SPECIFIC COMPLIANCE PROFILE REPORT lB
Permit Compliance Systetii(PCS) Suninary
Permit Nwnber: AL0002976 Consolidated ID: Facility Name: AL STATE DOCKS / MUD LAKES
City:MOBILE 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 Nan.:
PCS Overall Suimnary
PCS Permit No: AL0802976 Issue Date: 1990/10 Year All Viols Eff.Viols Inspections No.NOVs No.AA5 No.JAs
Fac. NameS AL STATE DOCKS / MUD LAKES CY91 0 0 1 0 0 0
Active Minor Discharger CY92 0 0 0 0 0 0
Expired Date: 1995/10 CY93 0 0 1 0 0 0
Figure 10-15. IDEA Standard Report lB
Report 1 B provides a detailed descnption of the facilities selected by your query.
Sample reports for each IDEA data system are given below. The report field name is
shown m bold followed by its descnption, the name of the data element used (in
parentheses), and a hst of possible values, where appropnate.
Chapter 10 IDEA Standard Reports 10-33
-------
10.1 .2.1 AFS Report lB Elements
AIR FACILITY SUBSYSTEM (AFS) SUMMARY
1. CDS Plant ID: 0109708003 Plant Name: ALUMINUN CORP OF AN. Address: AL STATE DOCKS
2. City: MOBILE County: 097 State: ALABAHA
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
SIP SOURCE
1 QTR/FY
04/91
02/92
04/92
02/93
8.
Pollutant
Pollutant Compliance
Status
CO 3
N02 3
PT 3
Px 3
S02 3
VOC 3
Pollutant
Classification
UK
UK
UK
Al
UK
Al
AQCR
Attain/Nonattain
Status
A
A
A
A
A
A
9. National Actions Description
STATE INSPECTION
STATE INSPECTION
STATE INSPECTION
STATE INSPECTION
STATE INSPECTION
AFS Overall Sumary
Date Achieved Penalty Miount
02/27/86
07/10/86
08/13/86
10/22/86
12/16/86
18. AFS CDS Plant ID: 0109708003
11. Source Coinpi. Status
12. IN COMPLIANCE - INSPECTION
Figure 10-16. AFS Report lB Fiements
LINE 1
Year
1991
1992
1993
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/mailmg address. (AFS.STRT)
LINE 2
6. Air Program:
7. Plant Ilistorica
Compliance Status:
Plant Compliance Status
QTR/FY
Plant Compliance Status
IN
COMPLIANCE - INSPECTION
01/92 IN COMPLIANCE - INSPECTION
IN
COMPLIANCE - INSPECTION
03/92 IN COMPLIANCE - INSPECTION
IN
COMPLIANCE - INSPECTION
01/93 IN COMPLIANCE - INSPECTION
IN
COMPLIANCE — INSPECTION
03/93 IN COMPLIANCE - INSPECTION
Plant Name: ALUHINUN CORP OF AM.
Air Program Desc. Qtrly Compl Status
SIP SOURCE 33333333
No. Insp.
No.NOVs
No.AAs
No.JAs
3
0
0
0
2
0
0
0
1
0
0
0
10-34 IDEA User’s Guide
October 22, 1996
-------
City Plant city name. (AFS.CYNM)
County Plant county number from CDS Plant ID. (derived from AFS.AFSID)
State Plant State name. (denved from AFS.AFSID)
LINE 3
Primary SIC Code Primary 4-Digit Standard Industrial Classification Code
(A FS .S1 Cl)
Secondary SIC Code Secondary 4-Digit Standard Industnal 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)
o Not owned or operated by a Federal, State, or local government
I 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 mdicatong a major source “Significant Violator”, and
lead enforcement agency of current violation. (AFS.SVI I)
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” tatus of 2nd most previous violation.
(AFS.SVI 3)
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 i or 6 to 5, 7,
or 0
D Source w/SVIL = B that changed Comphance Status Codefrom 1 or 6 to 2, 3, 4,
8, or 9
F Source w/SV1L = 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 wJSVIL = 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. (Denved 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 entnes here.)
LINE 6
Air Program AIR Program Code = Indicator/descnption of the regulatory air
program to which the plant is subject. (AFS.APCI Table Value)
Acid Precipitation AFS APCI = A
Native American AFS APCI = I
MACT (Section 63 NESHAPS) AFS APCI = M
Title V Permits AFS APCI V
SIP AFSAPCI=0
SIP Federal Jurisdiction AFS APCI
Non-Federally Reportable AFS APCJ 3
CFC Tracking AFSAPCI ”4
10-36 IDEA User’s Guide October 22, 1996
-------
PSD AFS.APCI=6
NSR AFSAPCI=7
NESHAP AFSAPCI=8
NSPS AFSAPCI=9
LINE 7
Plant Historical Compliance Status
QTR/FY The quarter and fiscal year of the plant compliance status to the nght.
(AFS .H DT 1)
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. (Denved 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 entnes here.)
LINE 8
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 mdicatmg pollutant conphance/noncomphance
(AFS.DCAP)
0 Unknown Compliance Status
I In Violation - No Schedule
2 In Compliance - Source Test
3 In Compliance - Inspection
4 In Comphance - 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 RequLrements
M in Compliance - CEMS
W In Violation with Regard to Procedural Compliance
V 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 cntenon
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
Non-attainment for Primary 502 Standards
2 Non-attainment for Secondary PT (Total Particulate Matter) or S02 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.PAM 1)
LINEs 10 - 12
AFS Report IA Summary see page 10-4 in Section 10.1.1, Report JA for detailed
information on these fields.
10-38 IDEA User’s Guide October 22, 1996
-------
10.1 .2 .2 CER (CERCLJS) Report lB Elements
CERCLA Information System(CERCLIS) Sunonary
1. EPA ID. Number: 1A0805270160 Site Name: ALUMINUM COMPANY OF AHERI Address: HWY 67
2. City: RIVERDALE County: SCOTT StateS 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: N Site Classification:
5. Operable Take Event Curr. Actual Curr. Actual —
Unit Event Lead Over Plan. Plan. Start Plan. Completion
_________ ___________________________ Status Start Date Camp. Date
00 DISCOVERY F 06/01/83
PRELIMINARY ASSESSMENT F P 87/2 01/88/87
SCREENING SITE INSPECTION F P 89/4 07/31/89
REMOVAL ACTION RP P 90/4 07/19/90 95/4
ADMINISTRATIVE RECORD F P 94/4 99/4
Operable Take Event Curr. Actual Curr. Actual
Unit Event Lead Over Plan. Plan. Start Plan. Completion
_________ ___________________________ Status Start Date Comp. Date
01 REMEDIAL INVESTIGATION RP P 86/4 08/14/86 99/4
ADMINISTRATIVE RECORD F 99/4 99/4
REMEDIAL INVESTIGATION RP p goiz 01/09/90 99/4
Actual Actual Activity Remedy Remedy Enforcement Enforcement
Start Completion Compliance Operable Sought Financial Financial
6. Enforcement Activity Lead Date Date Code/Olype Unit Achieved Type Amount
UNL-ORDR01 FE 08/18/94 Y UA R $855,000
08 RV1
RVL-NEG 01 FE 08/18/94 08/18/94 RN
CERCLIS Overall Suninary
7. CERCLIS Site Name: ALUMINUM COMPANY OF AMERI Cal Year 1990 1991 1992 1993
8. NPL Status: N No. Admin. Actions: 1 0 0 0
9. Site Classification: No. .]udic. Actions: 0 0 0 0
Figure 10.17. CER (CERCLIS) Report lB Elements
LINE I
EPA ID. Number Site-umque EPA identifier. (CER.0101)
Site Name Name of the site. (CER.0104)
Address Site street address. (CER.0I 10)
LINE 2
City Site city name. (CER.0lI1)
Chapter 10 IDEA Standard Reports 10-39
-------
County Site county name. (CER.0 120)
State Site Postal State Abbreviation. (CER.0002)
Site/Spill Id Site or spill identification number. (CER.03 15)
LINE 3
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 NotonNPL
0 Not valid site of incident
P Proposed for NPL
R Removed from proposed N PL
S Pre-proposal site
Proposed NPL Update The number of the National Pnonties List update on which
the site was proposed. (CER.0308)
Final NPL Update The number of the National Pnorities List update on which the
site was made final. (CER.0309)
LINE 4
Federal Facility Code that indicates whether or not the site or incident is a federal
facility. (CER.01 35)
D Status undetermined
N Not a federal facility
V Federal facility
Ownership Indicator Code that mdicates the current ownership status of the site or
mcident. (CER.0 136)
CO County owned
Dl District owned
FF Federally owned
IL Indian lands
MN Municipahty
10-40 IDEA User’s Guide October 22, 1996
-------
MX Mixed ownership
OH Other
PR Private
ST State owned
UN Unknown
Site/Spill Category The overall physical classification of the site or spill. (CER.0137)
A Abandoned
B Chemical plant
C City contammation
D Dioxm
F Federal facility
G Groundwater
H Housing area/farm
Industrial waste treatment
J Inorganic waste
L Landfill
M Manufacwring plant
N Military related
0 Other
P Pure lagoons
R Radioactive site
T M ines [ Taihngs
V Waterways/creeks/rivers
W 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
NC Fund lead negotiation
SE State enforcement
LINE 5
Operable Unit A designation for the operable umt at which events are occurnng.
(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 org mzation with primary responsibility for the
event. (CER.2117)
CC Coast Guard
EP EPA in-house
F EPA fund-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 fund money
SR PRP lead under state
TR Tribal lead, fund-financed
Take Over A flag which identifies those events which are or have been taken over.
(CER.21 14)
Event Plan. Status This field designates an event as a primary or alternate targeted
item for the purpose of meetmg a Strategic Planning and Management
System (SPMS) target. (CER.21 10)
A Alternate
P Primary
Q Delayed
S Project suspended
Curr. Plan. Start Current planned start date for the event (fiscal year/quarter).
(CER.2 132)
Actual Start Date The actual start date for the event. (CER,2l40)
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.2 141)
10-42 IDEA User’s Guide October 22, 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 regardmg 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 SET!’
D No Determmation
.1 Major Violations
N No Response
R Minor Violations
V Converted to CD
Y PRP In Comphance
Activity Compliance GType Code identifymg 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 Admm/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)
Fl Federal Interagency Agmt (H)
FIN Rl/FS Negotiation
FU Federal Memo of Understanding (H)
IL Issue Req Letters (H)
IN JAG Negotiations
JG Judicial/Civil Judgement
LP Federal Lien on PRP Property
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
P1 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 umt. (CER.2733)
Remedy Sought Achieved Remedy Sought Achieved. (CER.2731)
CO RI/FS
DA De Minunus Cash Out For Remedial Action
DC Cease and Desist
DD Dc Minimus Cash Out For Remedial Design
DE Document Exchange
DM De Mmimus Cash Out For Removal
DO De Mmimus Cash Out For Rl/FS
DU De Minunus Cash Out For Unspecified Site Work
ER Expedited Response Action
FS Feasibility Study
10-44 IDEA User’s Guide October 22, 1996
-------
IM Initial Remedial Measure (H)
IN Interest
LP Lien On Property
LR Long Term Response
MA Mixed Funduig/Preauth For Remedial Action
MD Mixed Fundmg/Preauth For Remedial Design
MM Mixed Funduig/Preauth For Removal
MO Mixed Funding/Preauth For Rl/FS
NA Non-De Minimus Cash Out For Remedial Action
ND Non-Dc Minimus Cash Out For Remedial Design
NM Non-Dc Mmimus Cash Out For Removal
NO Non-De Mminius Cash Out For RI/FS
NU Non-De Minimus Cash Out For Unspecified Site Work
OH Other
OM Operation/Mamtenance
P1 Preliminary Injunction
PR Premium
RA Remedial Action
RD Remedial Design
RI Remedial Investigation
RV Removal Action
SE Site Access
TO Temporary Restraining Order
TR Temporary Relocation
TS Treatability Studies
VA Cost Recovery of RA
VC Cost Recovery of, Other
VD Cost Recovery of RD
YM Cost Recovery of Removal Action
VO Cost Recovery of R1/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: see page 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 lB Elements
Civil Enforcement Docket Sunonary
1.
Case Name: NORMAN PARKER/NOI4BRAY ENGINEER Case Number: 04-86—8034
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 DDJ : Case Concluded: 1989/01
Case
Rereferred
by Region:
8.
Civil Docket Case Nane Case Number Type Case Law Ovrall Sta.
initiated To DO.] Filed
Concluded
NORMAN PARKER/NOWBRAY ENGINEERO4—86-0034 BNK CERCLA CASE CLOSED
1986/06
1989/01
Ftgure 10-18. DCK (Civil Docket) Report lB Elements
LINE 1
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 mdicattng the type of enforcement case, e.g., civil or admimstra-
tive. (DCK.TYPC)
Most commonly occurnng codes:
10-46 IDEA User’s Guide October 22, 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 Noncomphance
104E5A CERCLA 1O4ESA AO For Access And/Or Info
106 CERCLA 106 (AO) For Camp And Penalty
113 CAA 113 Notice of Violation
113A CAA ll3AAdminOrder(AO)
II 3D CAA 11 3D Delayed Compliance Order
113D 1 CAA 113D1 Administrative Penalty Case
114 CAA 114 Information Request Letters
122/104 Adm Order For Investigative Studies
14 FIFRA 14 (AO) For Camp and Penalties
1414G2 SDWA 1414 PWS Cornp Order 1st Time
14 14G3 SDWA 1414 PWS (AO) For Compliance
HQ Division A code mdicatmg the EPA Headquarters Division responsible for a case.
(DCK.HQDV)
AIR Air
WAT Water
CER CERCLA
RCR RCRA
TOX Toxics
CR1 Criminal
MOB Mobile (Air)
FFE Federal Facilities
LINE 3
Law/Section The law(s) and section(s) cited m the complaint. (DCK.LAWS +
DCK.SECT)
Pollutant(s) The waste matenal, substance or chemical mvolved at the facility m vio-
lation. (DCK.POLL)
Chapter 10 IDEA Standard Reports 10-47
-------
Violation(s) A code designating the nature of the violation(s). (DCK.VIOT)
Most commonly occumng 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 Polychiorinated 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 Case closed
0 Opened
P PRN (pre-referral negotiation)
S Returned to Region
T Taken
At EPA-HQ
2 ALDOJ
3 At US Attorney
4 Filed in court
S 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 October 22, 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 m Distnct 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 m Section 10.1.1, Report IA for detailed
mformation on these fields.
Chapter 10 IDEA Standard Reports 10-49
-------
10.1 .2 .4 DUN (Dun & Bradstreet) Report lB Elements
Duns
Suninary
DIJNS Number: 1307792 U1t: 1307792
Status. Headquarters Subsidiary No
Business: Armstrong World Industries
Hierarchy Level:
I Started
in 1860
Address: W Liberty Charlotte St
Sales Volume: S
2752700000
M1g 7 Yes
Lancaster PA 17604
Total Employees:
20600
SIC Code(s): 5023 3253 3296
Ejnpl. On Site:
4500
Figure 10.19. DUN (Dun & Bradstreet) Report lB Elements
LINE 1
DUNS Number A Data Umversal Numbering System (DUNS) random numenc senal
number. (DUN.DCNO)
lilt 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 busmess. (DUN.STAT)
NOT HQ/BRANCH DUN.STAT=O
HEADQUARTERS DUN.STAT= 1
BRANCH DUN.STAT=2
Subsidiary?. Indicates whether the business is a subsidiary or not. (DUN.SUBI)
Yes DUN.SUBI3
No DUN.SUBIO
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 October 22, 1996
-------
Started in Gives the year that the busmess 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.MFGIO
No DUN.MFGII
LINE 4
Total Employees The total number of employees employed by the busmess.
(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
busmess 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 lB Elements
Eoergency Response Noti Es cation Systea (ERAS) Hazardous Substance Rel easP
I ERAS Discharger Id 1089256633 Report 998266633 Initial Report st Up-to-date met reporting requirements
2 Discharger R,çion 06 Data 05/19/90 Spill Sate 00/10182 Occurred Spill ROgiOn 01 Region 1st Hotified Latitude
3 ESAOSI Co 009 IIIRGSTON MA County Longitude
4 1288 DM119 ST STATE IROY S 0 (151009 E l II & (010
S HOUSTON TX 71210 ROCUIII TRUCk 08 SCEHE
6 CDunty FORT BEND
7 TONE TRUCE / OVERTURNES
0 SOurce
9 Transport MAde Highosy RelateD Seaths Injuries I Damages 018888
68 QuantIty Materiel Spilled CHRIS Code Quantity Material Spilled CHRIS Code
58370 08 lbs 88030 ONSOLIPIE AlITRASIIVE (4 230 78/0 OAT
11 MAd,. lend .- SOIL
12 Cause Epuipeent FaIlure
03 18JUN50 PERSON WAS ADMITTED TO HOSPIIAL
EONS OVERALL SDM4H.RY
14 EONS Discharger Id I000266023 Spills -- lest fini yearn 2
IS Discharger EOAO9 SA USA Most recent 85/19/92
06 Diaths Injuries I Ecacoations Damagis 618808
Fkgane 80-20 ER!’5 (ERNS) Repool lB Oleariila
LINE I
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 mto
ERNS. (ERN.DOWNID)
Initial Report The appearance of this title indicates that the information presented is
the mitial 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 October 22, 1996
-------
met reporting requirements Indicates if the spill met the reportmg requirements of the
DOT’s Office of Hazardous Matenals 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)
Spill Date The date of the spill. (ERN.DTSPI)
Occurred A descnption indicatmg 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 m 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 m 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 nuscellaneous location. (ERN.LTEXT)
LINE 5
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 Dry Cargo
AB Liquid Cargo
AC Vehicle Fuel Tank
BA Pick Up
BB Platform
BC Van or Panel
BD Dump
BE Tractor Trailer
BF Tank
CA Airplane Fuel Tank
CB Airplane Cargo
DA Locomotive Fuel Tank
DB Tank Car
DC Flat Car
DD Hopper Car
10-54 IDEA User’s Guide October 22, 1996
-------
DE Refrigerator Car
DF Dry Cargo
DG Liquid Cargo
EA Dry Cargo
EB Liquid Cargo
EC Vessel Fuel Tank
FA Private Boat
FB Commercial
FC Tow Board
FD Tug Boat
FE Roro
FF Containenzed
FG Tanker
FH Barge
GA Plant
GB Distributor
GC Plant Piping
GD Production
GE Refining
GF Power Plant
GG Hazardous Waste Site
Gil Transformer
GI Railroad Yard
GJ Consumer
GK Underground Storage Tank
GL Gasoline Station
GM Water Treatment
HA Lines
HB Pumping Station
HC Inlet
HD Outlet
HE Valve or Fitting
IA Production
lB Storage
IC Transport (to Shore Only)
ID Equipment
JA 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 Facility
C Rail/Highway Crossing
H Highway Related
M Marine- released from a marine vessel to inland waterway
0 Offshore - spilled off the coast
P Pipeline Related
k 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)
Injunes The number of injuries resulting from the release. These mjunes 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 resultmg from releases for
this Discharger (ERN.PROPDMG) and/or an mdication 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 mto pounds,
(ERN.LBS) or, if this is not available, ERN.QTYSP (the quantity) and
ERN.UNITSP (the units), will be pnnted 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 October 22, 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.CH RI 5)
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 followmg this mfor-
mation, the medium to which the substance(s) were released.
(ERN.MEDCODE)
AA Explosion
AB Evaporation
AC Sublimation
AD Spray
BA Ground
SB Roadway
BC Parking Lot
BD Concrete
BE Beach Water
CA Stream
CB River
CC Sewer
CD Lake
CE Pond
CF Ditch
CG Reservoir
CH Canal
Cl Ocean
CJ Estuary
CK Inlet
CL Creek
CM lrngation
DA Well
DB Aquifer
EA Within Building
EB Within Processing System
EC On Concrete or Asphalt
ED 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.NATU RAL), 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 Overturning
AB Collision
AC Fire
Al) Explosion
AE Grounding
AF Sinking
AG Derailment
AH Pipeline Blowout
BA Broken Containers
BB Tank or Container
BC Valve
BD Flange
BE Hose
BF Fitting
BC Alarm
BH Automatic Shutoff
BI Dike
BJ Pump
BK Hull
BL Well Head
BM Flow Line
BN Pipeline
BO Manifold
BP Strucwral
BQ Weld
BR Container Leak
BS Lact Upset
BT Treater Upset
BU Power Failure
B\’ Power Oil Line
CA Improper Maintenance
CB Improper Operation
CC Improper Hose Connection
CD Improper Secured Flange
10-58 IDEA User’s Guide October 22, 1996
-------
CE Improper Storage/Handling
CF Improper Design
CG Improper Training
CH Improper Communication
CI Improper Valve Handling
CJ Overflow
CK Failure to Shutdown
DA Flooding
DB Freezing
DC Wind
DD Natural Seepage
DE Rain or Snow
DF Lightning
EA Improper Disposal
EB Deliberate
FA Unknown
GA Vandalism
GB 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 IA for detailed
information on these fields.
Chapter 10 IDEA Standard Reports 10-59
-------
10.1.2.6 FF1 (FFJS) Report lB Elements
1.
FF10: IA-690319303 Name: USCG DUBUQUE MOORINGS
Addr:
60 EAST FIRST
ST.
DUBUQUE
2.
Hed,wn: C’A Status:I
3.
Progress Code: 5 Compliance Status: PSOF Pollutant:
SPCC Project
Assessment:
L
4.
Federal Facility Id: IA-69031g303 Name: USCG
DUBUQUE
MOORINGS
Addr:
60
EAST
FIRST
ST.
DUBUQUE
Figure 10-21. FF1 (FFIS) Report lB Elements
LINE 1
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. (FF1. PM ED)
Status Facility status. (FFI.STFL)
LINE 3
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 October 22, 1996
-------
10.1.2.7 FIN (FINDS) Report lB Elements
1.
FINDS Id:
AL5680030926
Fec.
Name:
EASTERN ENVIRONMENTAL City: MONTGOMERY State AL
2.
Address:
1504 A AVE
Zip:
36114
Lat: Long:
Figure 10-22.
FIN (FINDS) Report
lB Elements
LINE I
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 LST (Contractor Listing Docket) Report lB Elements
1. LST Case Number: O1-88—L002 Case Name: BIG APPLE WRECKING CORPORATION , INC., BRONX, NEW YORK
2. Case Type: Case Status: Withdrawn by Recoimiending Person - Listi
3. Basis for Listing: CAA/Complaint Filed
CM/Federal Court Order
CM/Violation of Administrative Order
4. HDQtrs. Division: AIR Referred By: 01
5. Law(s)/Section(s) Violated: CAAJ 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: Case Closed: 11/08/91
9. HQ Attorney: DOHIKE, J. Regional Attorney: CALLAN, A.
Figure 10-23. LST (Contractor L stnig Docket) Report lB Elements
LINE 1
LST Case Number Case Number associated with facility. (LST.CSNO)
Case Name Name of the case mvolving 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 October 22, 1996
-------
AIR Air
CR] 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 authonty a contractor is listed.
(LST.LAW and LST.SECT)
LINE 6
Pollutant(s) The substance(s) that are causing the facility to be m 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 m an EPA region who is associated with the case.
(LST.RGNM)
10-64 IDEA User s Guide October 22, 1996
-------
10.1.2.9 NCD (NCDB) Report lB Elements
1.
2.
3.
4.
National
NCOBID: 107#1987062401668 Region: 07 Respondent name:
Facility Function: OP Pesticide Estab Number:
Schools Inspected: Federal Facility: N SIC Codes
Parent Co. Name : ALUMINUM CO OF AMERICA
Compliance Data Base (NCDB) Sunmary Page
ALUMINUM CO OF ANERICA
: 3361
5.
Investigation Violation
Number Legis Detected Violation
D07#07—88-424 I CC 6PS
SNC
YES
Date of
Action
19880406
Proposed
Penalty
$34,000
Final of EBE
Penalty Terms
$17,000
Closed/Wdrawn
Date (C/W)
19881025/C
Figure 10-24. NCD (NCDB) Report lB Elements
LINE 1
NCDBID NCDB identifier. (NCD.NCDBID)
Region Code designatmg 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 mdicatmg the function performed by an mspected facility,
e.g., manufacturer, producer. (NCD.FACI LIT)
BK Broker
CA Certified Commercial Applicator
CV Conveyor
DA Permitied Disposer - Alternative Methods
DH Permitted Disposer - High Eflic 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 Distributor
LB Laboratory
Ml Manufacturer/Importer
MK Marketplace
MN Manufacturer
OP Other Parties
PA Certified Private Applicator
PC Processor
PD Producer
PS Secondary Processor
PT Port Of Entry
RG Registrant
RU RUP Dealer
SA Supervised Applicator
TS Target Site
UA Uncertified Applicator
US User
Pesticide Estab Number The EPA registration number identif ’ing pesticide producing
establishments. (NCD.EPESTAB)
LINE 3
Schools Inspected The number of schools inspected within a Local Education Agency
(LEA) that were mspected. (NCD.SCHOOLS)
Federal Facility N/Y indicator that inspection site is a federal facility.
(NCD.FEDFAC)
SIC Codes Up to six 4-digit Standard Industnal Classification Codes.
(NCD . SIC LI ST)
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 .ACTNI D)
Legis The legislation/statute code. (NCD.LEGISLA)
10-66 IDEA User’s Guide October 22, 1996
-------
I TSCA
F FIFRA
E 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
NOl 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 “sigmuicant 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.EMAISSU)
Chapter 10 IDEA Standard Reports 10-67
-------
Proposed Penalty The proposed penalty assessed m the enforcement action.
(NCD.PROPENL or NCD.IPROPEN)
Final Penalty The fmal 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 ‘fC’, or NCD.MAWITHD or
NCD.IMA WITH with ‘/W’)
10-68 IDEA User’s Guide October 22, 1996
-------
10.1 .2 .10 OSH (OSHA) Report lB Elements
Occupeticnel loVely end Health Adoinistratien (SlAv) Insoection Reoert
CI lIA Activity Line NT 2250959
2 lnsoection No 2250959 Coened 63/66/65 Closed AN/I l/S O Eanloyees at site 451 Lost Aoraday Injury Rote 6 96 Region 02
3 Name FORD ACIOR CI1QAiIT - GREEN ISL Asaith Inspection Parti at SIC 3114 SAIlOR VEVICLE PARTS AILS ACCESSORIES
a Site 75 TIDBITS AVENUE Violations 2 Serious Violetiens 2 Iota 1 Penalties
5 Omen Island OF 12931 Optional Info Stats 03 2
Co re a ret 0/
Abetaoent Total Vi elation Panel ty Foil urn Aboard Egregious
7 Violation Leunl Sa ouirad Psnelties Contsstsd Contustod To Abets Level Case Status
19101925 F03 II other 06/09/96 Abateaaat comelsted
0 Cited substance(s) 1591 LEAD. INORGANIC FWEI & GUSTS (AS PR) (PEL)
19191925 P64 I Other 96/96/90 Abatement coanlated
Cited substance(s) 1591 LEVO, INOV0090C FwtS A GUSTS (AS PB) (PLt)
19191025 V02 II Other 0 0/66/OS AUateaent comeleted
Cited substance(s) 1591 LEAD. IROVIARIC FOES U GUSTS (AS P D) (PEL)
S Accident Source of Injury Substance Contributino to Acci dent
Aonhosoitaliosd injury CAGN LISUIGS/VAPOOS 2466 IOLUENE . SKIN
Aonhospitelioed injury CREM LIOUIOS/VA.POSS 2469 ISLUENE . SKIN
10 Insoocti SO NO 19t43276 Goened 06/03/61 Closed 92/92/61 ERDI oyees 01 5i to 296 teat Voroday Injury Rote 0 99 Region 02
Name FORD MOTOR CO GVUES lItHE PLA Safaty Insoection CoanrnVenslae SIC 3719 SAIlOR VERICLE PANTS A lit ACCESSORIES
Site 75 T990E1TS RyE Violations I Serious Violations I Total Paneltiss
Green Island Rn toll )
Co ro 0 ret e/
Abatement local Violation Penalty Foil urn Vaoard Eoreoi ous
Violetnon Level Rntuired Penalties Conteated Contested lo Abate Level Case ltotuS
1916 212 A63 II Other 66/29/61 Abasement co o rlntad
I I OSA A OVERALL SIOMKRRY
01KV Activity Line RI 2259959 No inspections - - Feat fiae yeors
home FORD PCtOS CWQAIiY . GREEN 1St
F,oro 90-25 OSH (OSHA ) Report 98 D Is
LINE 1
OSHA Activity Link An IDEA denved link between OSHA inspections. Although
every attempt has been made to link inspections of the same facility
together, a smgle 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 hnking purposes.
(OSH.ESTABST)
LINE 2
Inspection No A umque identifer for the OSHA inspection. (OSH.ACTIVTY)
Open id 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 mspectlon.
(OSH.SITEMPL)
Lost Workday Injury Rate The lost workday injury rate calculated on this inspection.
(OSH.LWDI)
Region From the first two characters m the reporting office identifier
(OSH.OFFICE)
LINE 3
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 mspection. (OSH.INSPSCO)
Comprehensive OSH INSPSCO = A
Partiai OSHINSPSCOB
Records Only OSH INSPSCOC
No-Inspection OSI-L INSPSCO = D
SIC The pnmary Standard lndustnal 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)
LINE 5
10-70 IDEA User’s Guide October 22, 1996
-------
City The city in winch the site is located, denved from the city code.
(OSH.SITECTY)
State The state m 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 onginator, if present.
Area Office OSH.OPTTYPE = A
National Office OSH.OVTTYPE = N
Regional 0111cc OSH.OVITYPE R
State OSHOPTTYPE=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 OSHVCURTYPO
Post Settlement OSH.VCURTYP= P
Repeat OSH.VCURTYP=R
Serious OSH VCURTYPS
Unclassi lieil OSI-I 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. (OSI-I.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 m 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)
LINE 8
Not completed, AD discretion
Not completed, employer out of business
Immediately upon receipt
Not completed, solicitor advised
Not completed, work site changed
Abatement completed
OSH VSTS=A
OSHVSTS=E
OSHVSTS=1
OSH VSTS=S
OSH VSTS=W
OSH VSTS=X
Cited substance(s) The substance(s) associated with this violation, if any. Both the
numenc code for the substance and a textual descnption will appear. (from
OSH.HAZSUB1 through OSH.HAZSUB5)
LINE 9
Accident A short descnption of the severity of any accident(s) noted m this
inspection. (OSH.ACCDGRE)
No injury
Fatality
Hospitalized injury
Nonhospitalized injury
Source of Injury The source of the
(OSH.ACCSRC)
OSH.ACCDGRE = 0
OSH.ACCDGRE= 1
OSH ACCDGRE=2
OSH ACCDGRE=3
injury caused as a result of the accident.
10-72 IDEA User’s Guide
October 22, 1996
-------
AIRCRAFT OSI-l ACCSRC=01
AIR PRESSURE OSH.ACCSRC=02
ANIMAL / INS/REPT/ETC OSH ACCSRC=03
BOAT OSHACcSRC=04
BODILY MOTION OSH.ACcSRC=05
BOILER/PRESS VESSEL OSH.AC CSRC=06
BOXES/BARRELS, ETC. OSH.ACCSRC=07
BUILDINGS/STRUCTURES OSH.ACCSRC = 08
CHEM LIQUIDS/VAPORS OSH ACCSRC=09
CLEANING COMPOUND OSH ACcSRC= 10
COLD (ENVIR/MECH) OSH ACcSRC= 11
DIRT/SAND/STONE OSH.ACcSRC= 12
DRUGS/ALCOHOL OSH.ACcSRC= 13
DUST/PAR11CLES/CHIPS OSH ACcSRC= 14
ELEC APPARAT/WIRING OSH ACCSRC= 15
FIRE/SMOKE OSH.ACCSRC= 16
FOOD OSH.ACCSRC= 17
FURINITUREJFURNISHING OSH.ACCSRC =18
GASES OSH.ACCSRC= 19
GLASS OSH.ACCSRC=20
I-lAND TOOL (POWERED) OSH.ACCSRC= 21
HAND TOOL (MANUAL) OSH.ACcSRC=22
HEAT (ENVIR/MECH) OSI-LACCSRC=23
HOISTING APPARATUS OSH.ACCSRC=24
LADDER OSH.ACcSRC= 25
MACHINE OSH ACCSRC=26
MATERIALS HANDLG EQ. OSH ACCSRC=27
METAL PRODUCTS OSI-LACCSRC=28
MOTOR VEHICLE (HWY) OSH.ACCSRC=29
MOTOR VEHICLE(INDUS) OSH.ACcSRC =30
MOTORCYCLE OSH.ACcSRC= 31
WIND/LIGHTNING, ETC. OSH ACCSRC= 32
FIREARM OSH ACCSRC= 33
PERSON OSHACcSRC=34
PETROLEUM PRODUCTS OSH.ACCSRC= 35
PUMP/PRIME MOVER OSH.ACCSRC= 36
RADIATION OSH.ACCSRC=37
TRAIN/RAILROAD EQUIP OSH ACCSRC= 38
VEGETATION OSH ACCSRC= 39
WASTE PRODUCTS OSH.ACCSRC=41)
WATER OSH.ACCSRC=41
WORKING SURFACE OSH ACCSRC=42
OTHER OSHACcSRC=43
FUME OSH.ACcSRC=44
Chapter 10 IDEA Standard Reports 10-73
-------
MISTS OSH.ACcSRC=45
VIBRATION OSH ACCSRC=46
NOISE OSHACCSRC=47
BIOLOGICAL AGENT 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 m chronological
order (sorted by inspection number). Chck above to get descriptions of the
individual fields.
LINE 11
OSHA Overall Summary See page 10-24 in Section 10.1.1, Report IA for detailed
information on these fields.
10-74 IDEA User’s Guide October 22, 1996
-------
10.1 .2 .1 1 PCS (PCS) Report lB Elements
Permit Compliance System(PCS) Suninary
1. Permit Number: 1A8003395 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: H
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/85/91
NOTICE OF VIOLATION/NOV 1 S 10/26/92
8. Numeric Violations (Ego) Count by Parameter
Parm CY91 CY92 CY93 Parameter Description
01105 0 1 0 ALUMINUM, TOTAL (UG/L AS Al)
PCS Overall Sunonary
9. PCS Permit No: 1A0 003395 Issue Date: 1991/02 Year All Viols Eff.Vmols Inspections No.NOVs No.Ms No.JAs
10. Fec. Name: ALUMINUM COMPANY OF AMERICA — CY91 0 0 1 1 0 0
Ii. Active Major Discharger CY92 1 1 1 1 0 0
12. Expired Date: 1996/02 CY93 0 0 0 0 0 0
Figure 10-26. PCS (PCS) Report lB Elements
LINE I
Permit Numher The NPDES identification number. (PCS.NPDES)
Consolidated ID Corresponds to a data element m PCS that is not part of the IDEA
extract, This field is always blank.
Facility Name The name of the permitted facthty. (PCS.NAM1)
LINE 2
City City Name. (PCS.CYNM)
County County Name. (PCS.CNTN)
State Postal State Abbreviation. (denved from PCS.NPDES)
LINE 3
SIC Code 4-Digit Standard lndustnal Classification Code(s). (PCS.SIC2)
Chapter 10 IDEA Standard Reports 10-75
-------
LINE 4
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 facthty 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 identifymg quarterly
reportable noncompliance based on system-generated DMR analysis for
major facilities. (PCS.CYQS)
C Comphant
D NC-SNC DMR Non-Recpt
E NC-SNC Effluent Viol
N NC-RNC Violins Only
P Resolved Pendmg
R Resolved
S NC-SNC Comp Schd Vio
T NC-SNC Comp Schd Rpt
LINE 6
Current Year Noncompliance Status Man. Up to four codes identifying quarterly
reportable noncompliance for major or minor facilities; manually set.
(PCS.CYM S)
C Compharit
D NC-SNC DMR Non-Recpt
E NC-SNC Effluent Viol
N NC-RNC Violtns Only
P Resolved Pendmg
R Resolved
S NC-SNC Camp Schd Via
T NC-SNC Camp Schd Rpt
10-76 IDEA User’s Guide October 22, 1996
-------
LINE 7
Enforcement Action Descnption of compliance or enforcement actions. (denved from
PCS.ENAC)
Act. Lead The compliance or enforcement action lead agency. (PCS.EATP)
Action Date Date of compliance or enforcement actions. (PCS.ENDT)
Action Status Status descnption of comphance or enforcement actions. (denved from
PCS.ENST)
Status Date Date of the latest enforcement action status. (PCS.ESDT)
LINE 8
Parm Parameter code for the parameter in violation. (PCS.PARAMTR)
CY# 4 Number of violation occurrences of PCS.MVIO= E90 (Numenc Violation)
with the morutonng date (PCS.MVDT) m the specified calendar year.
Parameter Description Description of the Parameter code. (from PCS.PARAMTR
Table Values)
LINEs 9 - 12
PCS Report 1A Summary. see page 10-26 in Section 10.1.1, Report JA for detailed
information on these fields.
Chapter 10 IDEA Standard Reports 10-77
-------
10.1 .2 .1 2 RCR (RCRJS) Report lB Elements
Resource Conservation and Recovery information System (RCRIS) Summary
1. Handler ID. XXD999999999 Handler Name. FORD MOTOR CO Address 2019 FORO RD
2. City. SHEFFIELD County XX833 State. XX Zip 12345
3. Existence Date. 1974/67/61 Sic code(s) 3714 3361
4. Owners(s)/Operatur(s) Nase Owner/Operator Indicatur
DWNERNAME CD
DPERNAME CP
5 Generator indicator 1 Transpurter Indicator: TSD indicator Source. N
6 Evaluation Type Respons Evaluation Violatiun Viol Viol Act.Date Enforcement Respons Enf.Actiun
Agency Date Area Class Prty. Resolved Action Type Agency Date
OTHER tVALUATION STATt 66/85/92 GtN—ALL REQ 1 HPV 07/20/94 Verbal informal STATE 86/11/92
COMPL EVAL INSPECTION STATE 81/21/93 GEN—ALL REQ 1 HPV 07/20/94 verbal Informal STATE 86/11/92
SAMPLING INSPECTION STATt 09/21/93 GtN—ALL RtQ 1 HPV 67/28/94 verbal Informal STATE 86/11/92
OTHER EVALUATION STATE 63/81/96 GEN-ALL REQ 1 04/26/96 Written Informal STATE 64/62/gb
TSD-OTHER 1 04/26/96 Written Informal STATE 84/62/96
1 RCRIS Handler Id XX0999999999 Year Ns.Eval Ns NDVs No.AAs No JAs HPV 7
8. Name. FORD MOTOR CO CY91 6 6 8 6 N
9. TSD Facility Statue CV92 1 8 8 8 V
18. Owner Operator Type. P CV93 2 8 8 0 V
1.1. Current HPV? NO CV94 8 0 8 8 V
12. Existence Date 1974/87 CY9S 8 8 8 8 N
CY96 1 1 9 8 N
Figure 10-27. RCR (RCRIS) Repon LB Elements
LINE 1
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 October 22, 1996
-------
LINE 3
Existence Date Existence Date for the facility. (RCR.HEXDATE)
SIC Code(s) The Standard Industnal Classification (SIC) code(s) hsted for this
facility. (RCR.SICCODE)
LINE 4
Owner(s)/Operator(s) Name Name of current or previous owner(s) of operator(s).
(RCR.CONAME)
Owner/Operator Indicator Code indicating current or previous owner or operator.
(RCR.COIND)
CO Current Owner
CP Current Operator
PD Previous Owner
PP Previous Operator
LINE 5
Generator Indicator Code indicating activity status of hazardous waste generation.
(RCR.GEN)
I 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
Transportor 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 NotaTSD,Verilied
Blank not a TSD, Unverified
Source Code mdicating source of the information in the generator/transporter/tsd
fields to the left. (RCR.SOURCE)
N Notification
A PartA
R Annual/Bienmal 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 Comphance Schedule
CSS Comphance Schedule Violation
DCH TSD-Chemical/ Physical/Biological
DCL TSD-Closure/Post-Closure Requirements
DCP TSD-Contmquency Plan Requirements
DFR TSD-Ftnancial Reponsibility Requirement
DGS TSD-General Standards
DGW TSD-Groundwater Monitoring Requirements
DIA incinerator Waste Analysis
10-80 IDEA User’s Guide October 22, 1996
-------
DIN TSD-Incineration Requirements
DLB TSD-Land Ban Requirements
DL,F TSD-Landfills Requirements
DLT TSD-Land Treatment Requirements
DMC TSD-Contamers Requirements
DM1 lncmerator Monitormg And Inspection
DMR TSD-Mamfest Requirements
DOP Incinerator Operating Requirements
DOR TSD-Other Requirements (Impi.)
DOT TSD-Other Requirements (Oversight)
DPB TSD-Part B Permit Apphcation
DPP TSD-Preparedness/Prevenuon Requirement
DPS Incinerator Performance Standards
DS1 TSD-Surface impoundments Requirements
DTR TSD-Tanks Requirements
DTF TSD-Thermai Treatment Requirements
DWP TSD-Waste Piles Requirements
FEA Former Enforcement Agreements
CER Generator-All Requirements (Oversight)
GGR Generator-General Requirements
GLB Generator-Land Ban Requirements
GMR Generator-Manifest Requirements
GOR Generator-Other Requirements (Impi)
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 (Impi.)
TRR Transporter-All Requirements (Oversight)
TWD Transporter-Haz Waste Discharge
Violation Class Violation class. (RCR.VCLASS)
a s1
2 Qass2
P Pending
Violation Prty. Violation pnority. (RCR.VPRTY) Values will be either High Pnonty
Violator (HPV) or Blank.
Action Date Resolved Action date resolved. (RCR.VACTDTE)
Chapter 10 IDEA Standard Reports 10-81
-------
Eni. Action Type Enforcement action type. (RCR.ENFTYPE)
Resp. Agency Responsible agency. (RC R. EN FAGN)
Eni. Action Date Enforcement action date. (RCR.EDATE)
LINEs 7-12
RCRIS Report lÀ Summary: see page 10-28 in Section 10.1.1, Report JA for
detailed information on these fields.
10-82 IDEA User’s Guide October 22, 1996
-------
10.1 .2 .13 SET (SETS) Report lB Elements
Figure 10-28. SET (SETS) Report lB Elements
LINE I
Street: JCT OF 2ND & BEELAND STS
State Zip Date of General Notice
AL 35291 03/10/89
AL 35016 03/10/89
AL 36732 03/10/89
AL 36580 03/10/89
AL 36307 03/10/89
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)
1. Site ID. Number: ALD031618069
2. City: GREENVILLE
3. PRP Name / Addressee
ALABAMA POWER COMPANY
ROBERT E HUFFHAN
ARAB ELECTRIC COOPERATIVE
JOE VAN BUNCH
BLACK WARRIOR
M.D. BLACK
BALDWIN COUNTY EMC
JOSEPH G. DOBBS
SITE ENFORCEMENT TRACKING SYSTEM (SETS) SUMMARY
Site Name: MOWBRAY ENGINEERING CO
State: AL Zip Code. 36037
Address City
600 NORTH 18TH STREET BIRMINGHAM
P.O. BOX 426 ARAB
P.O. BOX 779 DENOPOLIS
HIGHWAY 59 SUMMERDALE
MORGAN STREET SELMA
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 October 22, 1996
-------
10.1.2.14 TRI (TRJS) Report lB Elements
TOXIC RELEASE INVENTORY SIJ44ARY PACE
Fan I ty ID 520981POIT4CHOCRE fad I ty Weee ALCOA Address 4870 STATE ST
2 SIC Codes 3353 3355 3533
3 Reporting Year 1887 Fogltia or Stncr or Underground Irensfors Total
____________________ Nor—point Point Air Oischerge Injection Releases Dischei-ge to Dffsite RoleasesS Ricycled/
CasiO No Cheaical/Miaturn Rare Air Emissns Eeissions To Water to Lend to P01W Location Transfers Retoserod
080828806 COPPER C QOURDS 258 32888 0 8 8 8 12888 44258 0
800070864 CHR II LDI C OUAOS 258 1589 8 8 8 8 8 1858 0
888878122 MANDASESE C QOU0OS 258 11888 e e 8 8 2580 13850 832348
881344261 ALUPSINUM OXIDE 44888 0 8 8 8 8 5 44888 8
088875882 OICNLORUMETHAIIE 18888 0 0 0 0 0 8 18808 8
001318732 UnClEaN KYOROXIDE (SOLUTION) 8 0 8 0 0 0 I 0
Trend TaS.l for All Charmcel/Miatures 54758 44680 8 0 0 8 14680 113850 832340
SW4NARY mr ALL TRI EMISSIONS
4 TEl Id 52800LNre4CFIOGIEW Facility Rear ALCOA
YR Chea Count Lbs NP Air Pt Air Water UT Inj Land POTS Off-Site loSe 1 Recou
1991 11 195305 070080 3270 I 750 0 175720 2245845 723220
Figure 10-29 TRI (TRIS) Repofl lB Elements
LINE 1
Facility ID The TRIS identifier. (TRI.TFID)
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 Industnal Classification Code(s) reported by the facility.
(TRI .SJCD)
LINE 3 (Chemical Release Data - Repeating data block for each reporting year)
Reporting Year The four digit year penod for which the facility is reporting chemical
releases. (TRI.RPYR)
Cash. No. The TRIS chemical identification number; correspondmg to the Chemical
Abstracts Service (CAS) registry number, with the exception of chemical
mixtures which have umque TRIS number. (TRI.TCID)
Chemical/Mixture Name The descnption of the TRIS chemical identification number
(TRI.NAME)
Chapter 10 IDEA Standard Reports
10-85
-------
Fugitive or Non-point Air Emissions The quantity of chemical m pounds, released as
non-point air emissions. (TRI.M REST for TRI.CREL = 1)
Stack or Point Air Emissions The quantity of chemical in pounds, released as point air
emissions. (TRI.M REST for TRI.CREL = 2)
Discharge To Water The quantity of chemical in pounds, released to receiving streams
or water bodies. (TRI.M REST for TRI.CREL = 3)
Underground Injection The quantity of chemical m pounds, released via underground
injection wells on-site. (TRI.M REST 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. Does not include quantities that
were recycled or recovered. (based on TRI.MREST’s with TRI.CREL= 7,
with TRI.TRMT not equal to M20, M24, M26, M28, M93, M56, or M92)
Total Releases & Transfers The quantity of chemical in pounds, released to any media
or transferred off-site. (sum of TRI.M REST’s with TRI.CREL= 1, 2, 3, 4,
5, 6, or 8, or TRI.CREL= 7, with TRI.TRMT not equal to M20, M24,
M26, M28, M93, M56, or M92)
Recycled/Recovered The quantity of chemical in pounds, that was recycled or recov-
ered. (sum of TRI.MREST’s with TRI.CREL 7, with TRI.TRMT =
M20, M24, M26, M28, M93, M56, or M92)
LINE 4
TRIS Report 1A Summary: see page 10-30 m Section 10.1.1, Report IA for detailed
information on these fields.
10-86 IDEA User’s Guide October 22, 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 pnonty violator (HPV) according
to the RCRA program, or a significant violator (SV) according the CAA program. It
also contams the following civil docket information. case number, case name, and
overall status. The total number of facilities and violators for each database are hsted
at the bottom of Report 2.
Note: In the case of a Linked Nonhnked query, Report 2 will first present the facili-
ties with vahd FINDS identification numbers that match all of the selection
cntena, 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 industnes. (This is merely an exercise that has
no basis in fact regarding any planned or on-going enforcement mitiatives.)
U S ENVIROI ’ MTAL PROTECTION AGENCY 99 /25/96 Page I
En orceaent Confi donti al - For EPA Internal Use Only
INTEGRATED DATA SYSTEM REPORT 2
IMJLTI-i€OIA SICNIFICAAT NOIICU ’QIIERJSIONIF ICANT VIOLATOS REPORT
JUDICIAL DOCKET DATA
EPA Id Air Water RENA Pest Toxic EP3I3
Nx ei - FacIlity Nasa State SN’ RACY HPV? SECT SaC’ SAC’ Case NoNAer Case Nan, Oeerall States tech Cited
0JD982]R 5738 02 P0 1 11-9 (0CC PHNA Co CU P0111 PAAN’A OE A Ol EP 02-78-8899 C I OUPOI IT CASE CLOSED ClAW
82-88-0493 DUPONT DC NE9(UP.S & CO. El CASE CLOSED SCM
82.68-8783 DUPONT DC I IO9(URS El & CO TSCA
82-98-92211 1 1 OUPOAT C)QAUT C hAD
82-91-8231 C I DUPONT (CAN(ER) CM
82-114-9149 DUPONT CE NE9(UR EPCRA
1190894336798 ADIRTON STEEL CORP IN AIR 4S1 93-78-9824 NATIONAL STEEL CORPORATION CASE CLOSED ClAW
83-18-8841 NATIONAL STEEL CORP CASE CLOSED CM
83-91-8142 NATIONAL STEEL (ATIRION 019151 ACRA
83-91-8288 4096104 STEEL CORP RCRA
93-91-9289 NEWTON STEEL CORP AC M
93-92-9966 NATIONAL OTL/AIERTON_(CIC) CASE CLOSED CM
93-86-8797 4019108 STEEL CORP CASE CLOSED CM
93-97-8881 NATIONAL STEEL. WEIRTON DIV CM
93-91-0432 4019100 STEEL CORPORATION EPCRA
93-91-0441 ADIRTON STE(L CORPORATION CERCLA
U S ENVIROPOEN1AL PROTECTION AGENCY 99/25/95 Page 2
Enforee nt Confide,tlal - For EPA Internal Use Only
INTEGRATED DATA SYSTEM REPORT 2
Total NaMer of Facilities 2
Total Air SignifiCant Violators
Total Aster Signifincant IioTCoepliers 9
Total ACM Nigh PriorIty Violators 2
Total FIFRA Si9ni ficast Ntn tONAl ierS 9
Total TSCA Significant Nan ca .pliers N
Total EP]I 3 Si gni fi cant Non CONAI ars I
End of Report
Fi we 80-30 IDEA S1 ard kaçnt 2
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 (FIN.FNME)
State Postal State Abbreviation (FIN.STAT)
Media-Program Noncompliance Indicators
Air SV? Is this facthty flagged m AFS as a “Sigmficant Violator”? (based on the
code AFS.SVI 1)
Blank not a SV
AIR SV (AFS.SVI 1 = E,S,B,X,C,F,T)
Water SNC? Is this facihty flagged in PCS as having current violations which consti-
tute “Significant Noncomphance”? (based on the code PCS.LRNC)
Blank not a SNC
WTR SNC (PCS.LRNC= D,E,S,T)
RCRA HPV? Is this facility flagged m RCRIS as havmg unresolved violations which
constitute “High Priority Violations” 9 (based on the code RCR.CPVIOL)
Blank notaHPV
WST HPV (RCR.CPVIOL=9)
Pest SNC? Does this NCDB facility have current or historical violations which con-
stitute Fl FRA “Significant Noncompliance”? (based on the code
NCD.SNC)
Blank not a SNC
PES SNC(NCD.LEGISLAF; 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)
10-88 IDEA User’s Guide October 22, 1996
-------
EP313 SNC? Does this NCDB facility have current or histoncal 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 m the complaint (DCK.CSNM)
Overall Status Civil Enforcement Docket Case Overall Status: an mdicator of where
the case falls m 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 case 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 m 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 facthty counts by region and by Standard Industnal
Classification (SIC) code.
• The fifth section totals toxic substance release information for the selected facth-
ties by pollutant and by year.
— 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 imsleadmg 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 fmd facilities that are in aluminum-related industnes. (This
is merely an exercise that has no basis in fact regardmg any planned or on-gomg
enforcement initiatives.)
10-90 IDEA User’s Guide October 22. 1996
-------
U.S. Environmental Protection Agency
Sunnnary Report
1. Number of Facilities Selected by Region and Program
PRO I II III IV V VI VII VIII IX X TOTAL
AFS 0 1 0 1 0 0 1 0 0 0 3
CER 0 1 0 1 0 0 1 0 0 0 3
DCK 0 1 0 1 0 0 1 0 0 0 3
DUN 0 0 0 1 0 0 0 0 0 0 1
FF1 0 0 0 1 0 0 0 0 0 0 1
FIN 0 1 0 3 0 0 1 0 0 0 5
LST 0 1 0 0 0 0 0 0 0 0 1
NCD 0 1 0 0 0 0 1 0 0 0 2
PCS 0 1 0 1 0 8 1 0 0 0 3
RCR 0 1 0 2 0 0 1 0 0 0 4
SET 0 0 0 1 0 8 0 0 0 0 1
TRI 0 1 0 0 0 0 2 0 0 0 3
2. Compliance Status of Facilities by Program
AFS RCR PCS All Three
Eacs in Compliance 2 ( 67%) 4 (108%) 2 ( 67%) 2 ( 67%)
+ Facs Not in Compliance 1 ( 33%) 0 ( 0%) 1 ( 33%) 0 ( 0%)
Total Number of Facs 3 4 3 3
3. Number of Enforcement Actions by Program
AFS RCR PCS CER
Year NOV/NONS Ad nin Judic NOV/NONS Admin Judic NOV/NONS Admin Judic Adniin Judic
1990 0 6 0 0 0 0 0 0 0 1 0
1991 0 1 0 0 0 0 1 0 0 0 0
1992 0 1 0 0 0 0 1 1 0 0 0
1993 0 0 0 0 0 0 0 0 0 0 0
Number of Open Civil Docket Cases 0
4. Swmnary of SIC Codes by Region
SIC I II III IV V VI VII VIII IX X Totals Parameter Description
2819 0 0 0 1 0 8 0 0 0 0 1 INDUSTRIAL INORGANIC CHEMICALS
CHEHI CALS
2859 0 1 0 0 0 8 0 0 0 0 1 INDUST. ORGANIC CHEMICALS NEC
2911 0 1 0 0 0 0 8 0 0 0 1 PETROLEUM REFINING
3334 0 0 0 1 0 0 0 8 0 0 1 PRIMARY PRODUCTION OF ALUMINUM
3341 0 0 0 0 0 0 1 0 0 0 1 2NDARY SHELTJNONFERROUS METALS
3353 0 0 0 0 0 0 1 8 0 0 1 ALUMINUM SHEET, PLATE AND FOIL
3355 0 0 0 8 0 0 1 0 0 0 1 ALUMINUM ROLLING & DRAWING NEC
3533 0 0 0 0 0 0 1 8 0 0 1 OIL FIELD MACHINERY
4931 0 1 0 0 0 0 0 0 0 8 1 ELEC & OTHER SERVICES COMBINED
5171 0 1 0 0 0 0 0 0 0 0 1 PETROLEUM BULK STATIONS & TERM
5541 0 1 0 0 0 0 0 0 0 0 1 GASOLINE SERVICE STATIONS
TOTALS 8 5 0 2 0 0 4 0 0 0 11
Figure 10-31. IDEA Standard Summary Report
Chapter 10 IDEA Standard Reports 10-91
-------
5. Sumary of TRI Releases by Pollutant and Year
Pollutant Name TCID Year Emissions
ACETONE 0000676.41 1987 139,950
1988 139,500
1989 87,500
1990 94,568
1991 72,500
ALUMINUM OXIDE 001344281 1987 1,860,000
1988 271,000
AMMONIA 007664417 1987 213,981
1988 212,746
1989 194,800
1990 110,884
1991 113,377
ANTIMONY COMPOUNDS 000020008 1989 430
BARIUM COMPOUNDS 008020020 1987 2,760
1988 830
1989 1,576
1990 1,601
Figure 1(1-32. Summary Report (Continued)
Summary Report Elements
TABLE 1
PRG EPA Program/Data System
AFS AIRS Facility Subsystem
CER CERCL IS
DCK Civil Docket
DUN Dun & Bradstreet
FF1 Federal Facility Information System
FIN FINDS
LST Contractor Listmg Docket
NCD National Compliance Database
PCS Permit Compliance System
RCR RCRIS
SET Site Enforcement Tracking System
TRI Toxic Chemical Release lnventory System
I--X EPA Regions (FIN.REGN)
TABLE 2
10-92 IDEA User’s Guide October 22, 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’ facthties 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 m this database. The percentages indicate the percentage of
the total number of facihties 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 in compliance with AFS, RCR and PCS.
Total Facilities - All Three The total number of facilities meeting your Select cntena,
and in 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, comphance in all three
databases. Thus facilities not m 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)
Adniin Number of administrative actions.
AFS AFS ANTI =1 B, 2B, 3B, 7E, 8A. 8C, or 9A and AFS.DTAI in the indicated
calender year
RCR RCR ENETYPE in the range from 200 to 399 and RCR.EDATE in the indi-
cated calender year
PcS PcS.ENAC=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 indicated calender year
CER CER.1 732 with AC, AV, CA, Fl, 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=1D,1E,2D4B,SD,6B, or 9C and AFS DTAI 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 Industnal 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 (TR1.NAME)
TCID Toxic chemical identification number (TRI.TCID)
Year Reporting year (TRI.RPYR)
Emissions Emissions m pounds (TRI.TREST)
10.2 Accessin g and NaviRatin Reports
After running a report, the QUERY STATUS SCREEN will appear (see
Figure 10-33). On this screen, IDEA displays the followmg: the time of day when it
finished running the query, the number of facilities found in the search, whether or
not they are m FINDS (i.e., have valid FINDS identification numbers), and a chart
indicating the databases relevant to the search. This chart vanes for Linked, Non-
linked, and Lmked Nonlmked quenes.
10-94 IDEA User’s Guide October 22, 1996
-------
- QUERY S’ATUS SCREEN -
COMMAND = =>
i4:@ e9.01 - 1 Facility selected and in INDS
Counrs (percentages), ny database, of fac iities selectec ut
excluoed because they were not present in FINDS:
AFS 19 ( 13) CS 6305 ( 61)
R R 15 ( 1) MCD 1405 ( 31)
FIN 0( 0)
Press ENTER to continue, END to return to start
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 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.
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 ). 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 - Repor: IA- Iii Progress MAX 000022 LINE 00000000 COL 001 OOE.
COMMAND ===>
Issue coimnanc PRINTO to print, or SAVE to save to ataset.
*********************. ****** **** TOP OF DATA * ********* **********************
I U.S. ENVIRONMENTAL PROTEC
INTEGRATED DATA FACILITY-SPECIFIC Co
FINDS Id: VA1170024722 Fac. Name: USMC 0EV & ED COMMAND City: 0
Address: BLDG 2004 . Zip:
..RCRIS Handier Id: VA1170024722 Year No.Eval. No.NOVs No.
Name: MARINE CORPS 0EV & ED COtIMAND CYg2 0 2
TSD Facility Status: X HPV? NO Y93 0 0
Owner Operator Type: F Exist. Date: 1917/05 Y94 .0 0
PCS Pennit No: WA0002151 Issue Date: 1985/09 Year All Vials Eff.Viois Inspe
Fac. Name: .U. S.M. C. DEVLOPMENT &EDUC•AT I Y92 264 2
Active Major Discharger EY93 227 2
Expired Date: 1990/09 C 94 57 2
PCS Permit No: VA0928363 Issue Date: 1986/06 Year All Viols Eff.Viols Inspe
Fac. Name: U.S. MARINE CORPS BASE-HAl WSID Y92 31 19
Figure 10-34. An Example of Report 1A
Regardless of the report format selected, the title line of the BRO WSE SCREEN wifi
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 .
Use the commands in Table 10-1 to view your report in the BROWSE mode.
10-96 IDEA User’s Guide October 22, 1996
-------
Table 10-1. Commands for Navigating Reports
Commands Descriptions
UP 1< PFI9> Scrolls up by the amount set at the SCROLL prompt, or by the
number of lines entered at the COMMAND prompt
DOWN 1< PF2O> Scrolls down by the amount set at the SCROLL prompt, or by
the number of Imes entered at the COMMAND prompt
LEFT 1< PF22> Scrolls left by the amount set at the SCROLL prompt, or by the
number of lines entered at the COMMAND prompt.
RIGHT /< PF23> Scrolls right by the amount set at the SCROLL prompt, or by the
number of lines entered at the COMMAND prompt
END / Saves and returns to the previous screen
SWAP /< PF2I> Moves the cursor from a position m one screen to the same posi-
tion m another usmg the split-screen mode
MANEUVERING THE CURSOR
Arrow keys Use arrow keys for all directions
Use key to move to the next input field
Use to move to the top-left input field
M(a.x) + Scrolls up to the first line of a report,
M(a.x) + Scrolls down to the last line of a report,
M(ax) + Scrolls to the nght margin of a report,
M(axl + Scrolls to the left margin of a report.
10.3 PrintinQ 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 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
-------
BROWSE Report: 1A.-—---- - In Progress MAX 800 23 LLNE 9 C Le 086
COMMAND ===‘
• Issue coninand PRINTO to print, or SAVE to save to dataset.
TOP OF DATA *****k* *************** **k*******:
US. ENVIRONMCNTAL PROTEC
I.INTEGRATED DATA FACILITY-SPECIFIC CO
FIND.S Id.: VA1170 24722 •Fac. Narne USMC DEV&.EO COMMAND City: Q
Address: BLOC 2804 Zip:
RCRIS Handler Id: VA1176824722 Year No.EvaL NQ.NOVS No.
Name: MARINE CORPS 0EV & ED COMMAND CV92 0 2
TSD Facility Status: X HPV? NO CY93 0 •
Owner Operator Type: F Exist.. Date: 1917/05 CY94 0 0
PC P rnit No: VA0602151 Issue Date: 1905/09 Year All Viols £ff.V ols inspe
Fa a.. N iie: U. S.M. C. OEVLOPMENT &EB1JCATI CY 2 264 2
Acti ie Major Discharger CY93 2.27 2
Expired Elate: 1990/09 CY94 57 2
PCS Permit No: VA0028363 Issue Date: 198 /06 Year AliViols EffViols Inspe
Faa. Name: U.S. MARINE CORPS BASE-MAINSID CV92 31
Figure 10-35. Report IA
2. Type PRINTO at the COMMAND prompt and press . The
PRINT/SAVE PARAMETER SCREEN will pop up (see Figure 10-36).
10-98 IDEA User’s Guide October 22, 1996
-------
BROWSE - Report: IA- In Progress MAX 000023 LINE 00000000 CCL @01 000
COMMAND ===> printo
P”irt/Save Parameter Screen
* * *
Rrom line no .=== to line no.= =
_______ For printing
Bin
FINDS I Destination > HOLD
Addres No. of copies
RCRISH
t4ame! For saving enter DSN or DSN(menibernarne)
ISO
Owiie
PCS Permit No: \fA0002i51 Issue Date: 1905/09 Year All Viols E f.Viols Inspe
Fac. Name: U.. S.M. C. DEVLOPMENT EOUCATI Y92 264 2
Active Major Discharger CY9 227 2
Expired Date: 1990/09 CY94 57 2
PCS Permit No: VA0028363 Issue Date: 1985/06 Year A1 Viols Eff.Vicls Inspe
Fac. Name: U.S. MARINE CORPS BASE-MAINSID cY92 31 19
Figure 10-36. 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
. At the TO LINE NO. prompt, type the MAX number that appears at
the upper right corner of the BRO WSE screen and press . The MAX
number corresponds to the fmal 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 to the TO
LINE NO. prompt. Type the ending line number and press .
5. At the FOR PRINTING - BIN prompt, type your site specific BIN number and
to the DESTINA- TION prompt. Type your site specific printer desti-
nation ID (or press to send your print to the HOLD queue) and
to the NO. OF COPIES prompt. Type the number of original copies
you wish to receive and press . 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
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.
V1R3M3 50SF P1 IMARY OPTION MENU
COMMAND INPUT === SCROLL === PAGE
PREFIX=UID* DEST (ALL) OWNER
Type an option or conn nd and press Enter.
LOG - Display the system 109
- Display act ve users of the system
I - Thsplav jobs in the .JES2 input queue
0 - Display jobs in the JES2 output queue
:H - Display jobs in the JES2 held output queue
ST - Display status of jobs in the JES2 queues
PR - Display .1FS2 printers on this system
INIT - Di splay JES2 initiators on this system
TUTOR - Short course on 50SF (ISPF only)
END - Exit 50SF
Licensed Materials - Property of IBM
56 5-488 (C) Copyright IBM Corp. 1981, 1992. All rights reserved.
US Government Users Restricted Rights - Use, duplication or
disclosure restricted by GSA AOP Schedule Contract with IBM corp.
Figure 10-37. SDSF Primary Option Menu Screen
2. Type 0 at the COMMAND prompt and press 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 October 22. 1996
-------
SDSF UUT UT .LL CLASSES ALL FORMS LINES 802 LINE 1-1 (1)
COMMAND INPUT => SCROLL === PAGE
NP JOBNAME Jobia Dest C Form CB UCS Writer Tot-Rcds Status Device
U 1024 J0B87224 R255 A STO
Figure 10-38. SDSF Output Queue Screen
3. Press 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 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:
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 . The DS LIST SCREEN will appear.
c. down and type B (Browse) next to the
JUSD.REMOTE.DATA member. Press to view the list
of remote printers.
d. When you are finished, use the RETURN command (PF4) to go to
the JSPF/PDF PRIMARY OPTION MENU. Type X to return to
the READY prompt.
Chapter 10. IDEA Standard Reports 10-1 01
-------
— helpful hint
The first time you press 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 the second
time, the correct destination will again be displayed. (Compare
Figure 10-39 with Figure 10-40&period.)
SDSF OUTPUT ALL CLASSES ALL OR LINES 802 COMMAND ISSU
OOMM ND INPUT === SCROLL === PAGE
NP JOBNAME Jobid Dest C Form FCB UCS Writer Tot -Rcds Status Device
UID2 JOB@7224- R255 A STD 802
Figure 10-39. SDSF Output Queue - “Command Issued” Screen
SDSF OUTPUT ALL CLASSES ALL FORMS LINES 599 LINE 1-i (1)
COMMAND INPUT === SCROLL PAGE
JOBNAME Jobid Dest C Form FCB UCS Writer Tot-Rcds Status Device
U1024 J0807224 RMT O A SIC. 0 02 R6 05.P
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 .
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 October 22, 1996
-------
10.4 Savinr! 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 processmg the query report. If “IN PROGRESS”
is displayed, press every few seconds until “COMPLETE” appears.
Position the cursor at the COMMAND prompt.
2. Type SAVE at the COMMAND prompt and press . The
PRINT/SA VE PARAMETER SCREEN wifi 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 contams 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 usmg 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 m the
number of the first line in the block to be saved or type I to start at the beginning
of the report. Press . At the TO LINE NO. prompt, type the last line
number of the block to be saved or type m the MAX number which appears at
the upper right of the BROWSE screen and press .
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 Exitin r 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-1 03
-------
• 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 categones
that may or may not be relevant to a particular investigation, IDEA users should
understand these report formats before selecting one. Section 10.], Choosing a
Standard Report Format descnbes the standard report formats in detail.
Report 1A Provides a brief descnption of the facilities selected by your query.
Selecting linked, Nonhnked, or Linked Nonlinked will affect the organization of the
report.
Report lB Provides a detailed descnption of the facilities selected by your query.
Selecting linked, Nonlmked, or Linked Nonlmked will affect the organization of the
report.
Report 2 A multimedia table that indicates if a facility selected by your query is hsted
as a significant noncompher (SNC), a high pnority 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 October 22, 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 formattmg of the report and can
provide a customized report title and column headmgs.
11.1 Overview of IDEA User-specified Reports (USRs )
The IDEA Standard Reports descnbed in Chapter 10, IDEA Standard Reports, are
pre-programmed to supply specific types of data arranged 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 withm 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
m 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 Nonlmked 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 m the IDEA Shadow Databases (See Table 11-I).
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 m
the hierarchy is determined by the group to which it belongs
Table 11-1. Levels of Hierarchy in IDEA Shañow Datahases
Level
Descnption
1
Major-valued, Non-repeating Group
2
Major-valued, Repeating Group
3
Minor-valued, Non-repeating Group
4
Minor-valued, 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 October 22, 1996
-------
a single facility or case (a single value of the primary major data element) into disjoint
parts.’
Suppose, for example, we run a Linked query looking for TRIS polluters of heav\
metals into water, that are in reportable or significant noncompliance with PCS, and
requesting the data elements shown in Figure 11-1
000801 OUTPUT REPORT HEAVVMETALS
000902 DETAIL LINE
08003 T I.TFID
000004 TR1.S100
000005 TRI.RPVR
000906 TRI.TcID
0U8907 IRI .MRESI
000008
@00009 INPUT LINKED SELECT
000010 ( / paren before MenuA keywords f 0 r convenience in further combining
900811 BEGINNING OF POLLUTION KEYWORDS
000012 ( / POLLUTANT = ZINc, HRO$ ’tLLJM NICKEL, SILVER
.008013 (TRI .TC1O = 007440 5697440473,007449020,•007448224 AND
009914 T.RLc EL 3 ) / RELEASE MEDIUM = WATER
000015
000916 END OF POLLUTION KEYWORDS ******************
.900017 AND
000018 / Noncompliance keywords */
000819 (((PCS.LRNC=D,E.N,S.T & PcS.MA 1=M & PCS.IACC=Afl)
080020 ) / paren after MenuA keywords for convenience in further combining
Figure 11-1. Data elements requested in USR
The data would print out in the manner shown in Figure 11-2. (We should note that
this is only the top of the report. The report for the above query, at the time of this
writing, was over 39000 lines!) Level one data (the TRIS facility ID) would all
appear on the first line for that facility. The level two (repeating) data (the SIC
industry code) would begin printing out on the first line, and continue printing out
until it was exhausted, for that facility.
1 The primary minor data element is non-repeating in the sense that it only takes one value in the copy of the minor level that it
creates.
Chapter 11. IDEA User-Specified Reports 11-3
-------
1 U.S. ENVIRONMENTAL PROTECTID AGENCY 0.3/08/ 95
ENFORCEMENT CONFIDENTIAL - FOR EPA INTERNAL USE ONLY
INTEGRATED DATA FACILITY-USER SPECIFIED REPORT HEAVYMETAL
TRI TRI TRI TRI TRI
TFID SI D RPYR TCID MREST
359e4 LFST174SC 33 1987 080098828 118
3300 1987 007664382 250
3312 1987 087664939 546
1987 801310732 250
1987 007647010 250
1987 007440020 647
3 1
861 9
1987 807440666 3883
1430
42640
311435
1987 007439g55 5563
Figure 1 1-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.
Furthermore, 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 October 22. 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:
[ OUTPUT] REPORT report-name
[ TITLE “title”]
[ HEADER OFF/JUSTIFY HEADINGS [ L/C/R]]
DETAIL LINE
detailfieldi [ HEADING] [ WIDTH] [ START [ LENGTU]]...
detailfield2
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
[ U SR 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.9, 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 restnctions
1 USR names can not contain any spaces
Chapter 11 IDEA User-Specified Reports 11-5
-------
2. The designations 1A, 1B, 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.
U S Environmental Protection Ager cy 04/25/94
nfarcemeiit Confideiitial - For PA Internal Use Only
i:: i :: ::
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 (abbreviated DETAIL or DETA)
Syntax: DETAIL LINE
datafieldi [ HEADING/WIDTH’...]
datafield2 [ HEADING/WIDTH, ...]
etc.
11-6 IDEA User’s Guide October 22, 1996
-------
Important!
The DETAIL LINE keyword is a required element m a USR request.
The Detail Line is an essential part of an IDEA User-specified Report request. It is
here that you specif ’ 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 Lme: data elements, DEFINE
statements, and expressions. The sample USR query in Figure 11-10 shows an
example of each.
DATA ELEMENTS
Data elements are specified m the same manner as your query selection cn-
tena: the 3-character database identifier followed by a penod and the data
element name (dbi.element; e.g., FIN.EPID).
DEFINE S TA TEMENTS
DEFINE statements have the form:
DEFINE fieldname expression.
(See lines 4 through 8 in Figure lI-JO.) The name of a DEFINE field
(fieldname) must consist of only one word and can contam up to 11 charac-
ters. The DEFINE keyword is optional, but we recommend that you use it
for the sake of legibility
— Caution
DEFINE field names must be umque (withm a given query)! If you
assign a different expression to a name that has aheady 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 numenc data elements accessed by IDEA, certain built-rn
USR functions such as the ENFACTSO function (Section 11.2.3, Custom
USR Functions), and the basic anthmetic operators: addition (+), sub-
traction (-), multiplication ( ), and division (/).
• Note that a function by itself constitutes an expression.
• An expression need not be enclosed rn parentheses.
Chapter 11 IDEA User-Specified Reports 11-7
-------
• Any named field (dbi.element or a DEFINE field name) can be used
inside functions and expressions.
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”
‘IRONMENTAL PROTECTION AGENCY :.
ENT CONFIDENTIAL - FOR EPA INTERNAL JS
ACJLITY-USER SPECI ItD RE ORT
REPORT ON FACILITIES WITH TR1S RELEASES OF SOME HEAVY METALS
TO WATERS AND PcS REPORTABLE OR SIGNIFICANT NONCOMPLIANCE
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 October 22, 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).
U.S. ENVIRONMENTAL PROTECTION AGENCY 11/23/94
ENFORCEMENT .OON IDENT1AL - FOR EPA INTERNAL USE ONLY
INTEGRATED DATA FACILITY-USER SPECIFIED REPORT HEAVYMETAL
REPORT ON FACILITIES WITH TRIS RELEASES OF SOME HEAVY METALS
TO WATER, A1 D PCS REPORTABLE OR SiGN IOANT NONcOMPLIANcE
TRI TRI TRI TRI TRI TRI
TEID HNME 5100 RPYR TCID MREST
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
HEADER OFF keyword will cause the
of the report.
the top of each page of the
header to appear only once,
USR.
at the
The
beginning
Keyword: JUSTIFY HEADINGS
Syntax: JUSTIFY HEADINGS L
/C/R
Chapter 11. IDEA User-Specified Reports 11-9
-------
This keyword is used to justify the column headings: L = Left, C = Center, R = Right.
If JUSTIFY HEADINGS is not specified, the column headings wifi be centered by
default.
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 (abbreviated HEAD)
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 /1.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 Wit 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 (dbi.element or Define_name). If’ the field consists of a plain expression, the
default heading will be the expression itself
Keyword:
WIDTH (abbreviated WI)
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
11-10 IDEA User’s Guide October 22, 1996
-------
columns in your report. (By default, I space will automatically be inserted between
columns.)
The default width for a given column is the greatest of the length of the column
heading, the substnng 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 (abbreviated
ST), 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 substrmg (the total number of positions) to print;
the default is the external length of the data element.
• The length of a substrmg 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 substrmg 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.
Chapter 11 IDEA User-Specified Reports 11-11
-------
Keyword:
JUSTIFY
(abbreviate
d JU)
Syntax:
{datafield}
JUSTIFY
EL/C/RI
JUSTIFY determines the positionmg of the data value within the column -- L= Left,
C=Center, R= Right. If JUSTIFY is not specified, the default justification is nght-
justification for numeric data fields and left-justification for character fields.
Note that JUSTIFY will determine the justification of the data withm the given
column only; the justification of the column heading is controlled usmg the JUSTIFY
HEADINGS keyword described m Section /1.2.2.2, Controlling the Report Header,
above.
Keyword:
DECI MALS (abbreviated DEC)
Syntax:
{datafield) DECIMALS n
DECIMALS specifies the number of digits to the nght of a decimal point to be
printed. This keyword can be used to modify numenc data fields only. Figure 11-6
shows the initial example, with some customrzmg. Notice that the HEADING
keyword has been used repeatedly for several of the columns, to create colunin
headings having multiple lines.
11-12 IDEA User’s Guide October 22, 1996
-------
001 OUTPUT REPORT HEAVYMETALS
00-3002 TITLE “Report on Facilities Wltr! TRI Releases of Some Heavy Metals”
1 000003 TITLE “to Water, and P05 Reportable or Significant NonCompHanc&
000804 DETAIL LINE
00005 TRI.TFID HEADING TRIS HEADING “FACILITY ID”
000006 TR1.STCD WIDTH 5 HEADING TRIS HEADING SIC
800007 TRI.RPYR WIDTH 6 HEADING TRIS HEADING REPORT HEADING YEAR
000888 TRI.TCID HEADING. IRIS HEADING CHEMICAL
800009 TRI.MREST DECIMALS I HEADING TRIS HEADING RELEASE HEADING ESTIMATE
008011 INPUT LINKED SELECT
000012 ( / .p-aren before MenuA keywords for convenience in further combining
800013 f ** BEGINNING OF POLLUTION KEYWORDS
000014
000015 (TRI .TCID = 007440666.007440473,80744 8020.007440224 AND
000816 TRI.cREL 3
000017 )
• 000018 /*** END OF POLLUTION KE ORDS
000019 AND
00882 .1* Noncompliance keywords */
008021 (((PCS.LRNC=D,E,N.S!T & P S.MADi=M & PCS. 1ACC=A))) ..:.:..
• 000022 ) / paren after IlenuA keywords for convenience in further c flbintng
Figure 11-6. Simple USR with Title and Formatting
The output for this request is shown in Figure 11-7
Chapter 11. IDEA User-Specified Reports 11-13
-------
1 U.S. .ENVI ONMENTAL PROTECTION AGENCY 03/08/95
ENFORCEMENT CONFIDENTIAL FOR EPA INTERNAL USE ONLY
INTEGRATED DATA FACILITY-USER SPECIFIED REPORT HEAVYMETA
REPORT ON FACILITIES WITH TRI RELEASES OF SOME HEAVY METAL
TO WAT:ER, AND •PCS REPORTABLE OR SIGNIFICANT NONCONPLIANCE
TRIS TRIS IRIS TRIS TRIS
:E CILITY ID SIC REPORT CHEMICAL RELEASE
YEAR ESTIMATE
359040LFST174 50 33 1987 088098828 118 .0
3300 1987 0076643B2 250.0
3312 1987 007664939 546.0
1987 8013107 2 250.0
1987 007647010 250.0
1987 007440928 .647.6
31.0
8619.8
1987 087440666 3880.0
42648 .0
311435.0
1987 8074399 5 5663.0
1172.0
L1932 .0
309993.0
1987 007439921 4659.8
1987 807440473 703.0
Figure 11-7. Simple USR with Title and Formatting
11.23 Custom USR Functions
The following functions provided with the User-specified Reporting capability are
designed to help you to create USRs that suit your needs. They can save you time,
by making it easier for you to get IDEA to count and sort data for you, and by
translating codes for you, so you don’t have to go off in search of data element dic-
tionaries to understand your reports. And, they give you ways to present data more
effectively, so that your USR can be more useful.
The functions described in this section are used on the Detail Line. ACROSSQ,
CONCATO, and DUPO give you new ways to present your data. COUNTVO,
ENFACTSO, and TRISIC() make IDEA do some counting and summarizing for you,
before the data ever gets to the Detail Line. FIRSTVO, CYRO, FYRO, CYRQTRO,
and FYRQTRO are tools for allowing you to sort data in meaningful ways. TEXT()
gives you English translations of the codes for many IDEA data elements.
11-14 IDEA User’s Guide October 22, 1996
-------
The statistical functions provided with USRs, which are used on the Summary Line
to summarize sorted Detail Line output, are documented in Section 11.3 .3.1, Statis-
tical Functions, should you want IDEA to do more calculations for you.
Function: ACROSSO
Syntax: ACROSS(dbi.elementl, dbi.element2, test value)
Valid Inputs:
Data Elements: Any two data elements in the same database,
in the same record.
Test values: Any valid value for dbi.elementl.
The ACROSSO function was created to allow the data for a single data element
(dbi.element2) to be spread across the page, rather than all in one colunm. For
example, the USR request in Figure 11-8 spreads the output for TRI.MREST
“across” the page. (See Figure 11-9.)
File Edit confirm Menu Utilities Compilers Test Help
EDIT UIDAcCT.OUERY.SPECS(ACROSS) columns 90001 99072
Command ===> Scroll == > CSR
lop of Data
880901 OUTPUT REPORT TRIRELEASE
090902 DETAIL LINE
000993 TR1.TFI D HEAD IRIS HEAD “FACILITY I C ”
090004 TRI.TCID HEAD IRIS HEAD CHEMICAL
080905 AcROSS(TRI.CREL, TRI.MREST, ‘T ’) HEAD FUGITIVE HEAD AIR
090005 ACROSS(TRI..CREL , TRI.MREST , “2”) HEAD POINT HEAD AIR
098907 ACROSS(TRI.•cREL, TRLMREST, “3’) HEAD WATER
000908 ACROSS(TRI•CREL :TRI MREST “4”) HEAD UNDERGROUND HEAD INJECTION
098909 AcROSS(TRI.CREL, TRI.MREST, “5”) HEAD LAND
009010 AcROSS(TRI.CREL , TRI.MREST.,..::I 5U) HEAD P01W
008011 AcROSS(TRI.CREL, TRI.MREST, “7”) HEAD OFFSITE HEAD TRANSFER
000012
000013 INPUT LI 1KED SElECT
000914 ( / paren before Menu keywords for convenience in further combining
009015 BEGINNING OF POLLUTION KEYWORDS
000015 (
080017 (TRI .TCID = E107440566,807448473,90744082 0,98744 8224 AND
000018 TRLCRE. = 3 ).
008019
Figure 11-8. USR request using “Across” function
Chapter 11. IDEA User-Specified Reports 11-15
-------
BROWSE - Rpt: TRIRELEASE-- In Progress MAX 800999 LINE 8008802 OL 00.1 080
COMMAND ===>
Issue coniiiand PRINTO to print, or SAVE to save to dataset.
I U.S. ENVIRONMENTAL PROTECTION AGENCY 03/19/96
ENFORCEMENT CONrIDENTIAL - FOR EPA INTERNAL USE ONLY
INTEGRATED DATA FACiLITY-USER SPECIFIED REPORT TR1RELE
TR:s TRIS FUGITIVE POINT WATER UNDERGROUND LAND
FACIL:TY ID CHEMICAL AIR AIR INJECTION
35064S 5F.RFVALLE N982 220
N420 109
• :t’J 09 0 5
001330207 15880
007647010 120090
007440666 31000
087439965 258
0 8742 P905 1
007664417 1700 5800
•N106 110
081310732
001330207 7100
N45 0 1700 760 300 430
• 007647810 52000
Figure 11-9. TRIS Release Data “Across” the Page
Function: CONCATO
Syntax: CONCAT(dbi.element, dbi.element, ...)
Valid Inputs: Any data elements storing characters, in the same database,
and in the same record. This function can handle as much as
ten data elements.
This function was created primarily so that the two PCS facility name data elements,
PCS.PNAM (the first 8 characters of the name) and PCS.PNM2 (the last 22 charac-
ters), could be joined together, or “concatenated,” in the same column. However, it
can be used to join any two same-record character fields, of any length, that you
wish.
Function: COUNTVO
Syntax: COUNTV(dbi.element)
Valid Inputs: Any data element.
11-16 IDEA User’s Guide October 22, 1996
-------
This function counts the number of values present for the data element given, subject
to your RESTRICT section (see Section 11.3.1, Restricting Report Data), if one is
present. The count will be output once for each value of FIN.EPID, for Linked
quenes, or for each permit value, for Nonhnked quenes.
Functions: CYRO, FYR()
Syntax: CYR(dbi.element), FYR(dbi.element)
Valid Inputs: Any data element that stores dates (stored either as
YYMMDD or YYYYMMDD).
These functions output either the four-digit calender year, or the fiscal year,
depending on which is used, so that you can sort data by calender year or fiscal year.
For example, given an effluents record m PCS with PCS.MVDT equal to 19901101,
FYR(PCS.MVDT) would output 1991 m its column, rather than 19901101, and
CYR(PCS.MVDT) would pnnt 1990.
Functions: CYRQTRQ, FYRQTRO
Syntax: CYRQTR(dbi.element), FYRQTR(dbi.element)
Valid inputs: Any data element that stores dates (stored either as
YYMMDD or YYYYMMDD)
These functions output either the four-digit calender year and quarter, or the fiscal
year and quarter, dependmg on which is used, so that you can sort data by calender
year quarters or fiscal year quarters. For example, given an effluents record in PCS
with PCS.MVDT equal to 19901101, FYR(PCS.MVDT) would output 1991/Qi m its
column, rather than 19901101, and CYR(PCS.MVDT) would print 1990/Q4.
Function: DUP()
Synfax: DUP(dbi.element)
Valid Inputs: Any data element.
This function allows you to print out the same data element in more than one
column. For example, you could print out the FIN.EPID in both the first and last
Chapter 11 IDEA User-Specified Reports 11-17
-------
columns by using FIN.EPID for the first column, and DUP(FIN.EPID) in the last
column. (If you simply use FIN.EPID twice, the second will be ignored.
Function: ENFACTS()
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-10 shows a USR request using the ENFACTS function.
008801 OUTPUT REPORT NUKEPLANTS
900082 DETAIL LINE
000803 F IN.EPID HEADING FINDS HEADING FACILITY ID ”
008004 DEFINE EAAFS ENFACTS(AFS,F,10) HEADING AFS HEADING ENFORO HEADING ACTIO
8 8005 DEFINE EADCK ENFACTS(DCK,F.10) HEADING DOCKET HEADING ENFURC HEADING AC
B00806 DEFINE EANCO ENFACTS(NcD,F ,10) HEADING NCDB HEADING ENFORC HEADING ACTI
000007 DEFINE EAPCS ENFACTS(PCS,F .10) HEADING PCS HEADING ENFORC HEADING AcTIO
08008 DEFINE EARCR ENFACTS(RCR,F,10) HEADING R RA HEADING ENFORC HEADING ACTI
000009 EAAFS+EADCK+EANcD EAPCS÷E•ARcR HEADING TOTAL HEAD NO ENFORC HEADING ACTI
00010
000811 INPUT LINKED SELECT
a00012 ( 1* paren before MenuA keywords for convenience in further combining
000013 BEGINNING OF LO AT1ON KEYWORDS *****************
000014
000015 FIN.REGN = 03
000016
008817 END OF LOCATION KEYWORDS * ***t**************
000018 AND
008019 BEGINNING OF INDUSTRY KEYWORDS
000020
000021 •AFS.S1CC 4911 OR
000022 PCS.SIC2 = 4911 OR
000823 RCR.SICcODE = .4911 OR
000024 TRI.S1CD = 4 ii
000025 )
000025 /***************** * END OF INDUSTRY KEYWORDS *** *
000027 ) / paren after MenuA keywords for convenience in further combining
Figure 11-10. Example of Use of ENFACTS
11-18 IDEA User’s Guide October 22, 1996
-------
It should be noted that in Figure 11-10, using DEFINE statements was not required.
It just makes typing the expression on line 9 easier!
Function: FL RSTVQ
Syntax: Fl RSTV(dbi.element)
Valid Inputs: Any data element in a repeatmg record.
This function allows you to print out only the first value encountered in a repeating
record, for a given data element, rather than all such values (subject to your
RESTRICT section, if you have one). This is used almost exclusively to make it
possible to sort data usmg a repeating value, for example, FIRSTV(FIN.REGN).
Smce IDEA now has “voted” states and regions m FINDS for each facility, this func-
tion is not used much anymore.
Function: TEXTO
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 decodmg table for the element, and returns an English-language descnption of the
meaning of the given value. If the specified value is not found m the decoding table
for the data element, the value itself will be returned.
Figure 11-11 shows the output from Figure 11-6 , if TRI.TCID is replaced by
TEXT(TRI.TCID) WIDTH 15.
Chapter 11 IDEA User-Specified Reports 11-19
-------
U.S. ENVIRONMENTAL PROTECTION AGENCY : 3/Ø /95
ENFORCEMENT CONFIDENTIAL - FOR EPA INTERNAL USE ONLY
INTE RAT O DATA FACILITY-USER SPECIFiED REPORT HEAVYMETALS
REPORT ON FACILITIES WITH TRI LEASES OF SO HEAVY METAL
TO WATER, AND PCS EPORTABLE OR SIGNiFICANT .NON OMPLI CE
TRLS IRIS IRIS IRIS TRIS
FACILITY I D SIC REPORT CHEMICAL RELEASE
YEAR ESTIMATE
35QG4GLFST.174 50 33 1027 CUMENE
3300 1987 HOSPHORIC ACID 250.0
3312 1027 SULFURIC ACID 546.0
.1987 SODIOM HYDROXID 250.0
:1027 HYDROCHLORIC AC 250.8
1087 ‘l.ICKEL 647.0
31 0
0619. 0
927 ZINC (FUME.OR D 3800.0
1430.0
42640..0
311435.0
1027 MANGANESE .5 5 0
1172.0
41932 . 0
300993.0
1027 LEAD 4659.0
1027 CHROMIUM 783.0
Figure 11-11. Using the Text function
To see a listing of data elements that have translation tables, type TEXT INFO at the
Command prompt. (See Figure 11-12.)
11-20 IDEA User’s Guide October 22, 1996
-------
• EDIT ---- UIDACCT.QUER .SPECS(BASIC2) - COLUMNS 801 072
COMMAND ===> text info SCROLL = = CSR
****** ******* *** ******* ** TOP OF DATA
009001 OUTPUT REPORT HEAVYMETALS
009002 TITLE “REPORT ON FACILITIES WITH TRI RELEASES:O SOME HEAVY METALS”
009003 TITLE “TO WATER AND PCS REPORTABLE OR SIGNIFICANT NONCOMPLIANCE’
000004 DETAIL LINE
00.0905 TRI.TFID HEADiNG TRIS HEADING “ ACILiTY ID’,
000806 TRI.SICD WIDTH 5.HEADING IRIS HEADING SIC
000007 TR1.RPYP. WIDTH 6 HEADING IRIS HEADING REPORT HEADING YEAR
809008 TRI.TCID HEADING TRIS HEADING CHEMICAL
009080 TRI.MREST DECIMALS 1 HEADING IRIS HEADING RELEASE HEADING ESTIMATE
000010
000011 INPUT LINKED SEt.E T
009012 1*. parer before MenuA keywords for convenience in further combining
009013 /* ** BEGINNING OF POLLUTION KEVW&RDS ****x***********
000014
309015 (TRI.TCID 0 07440666,097449473,00744002@,007440224 AND
000816 TRI.cREL = 3
309017
009818 /** ****** * END OF POL:LUTION KEYWORDS
000019 AND
000920 / Noncompliance keywords /
009021 (((PCS.LRNCD,E,N,S,T& PCS.MADi t4 & PCS.IACC=A)))
Figure 11-12. TEXT INFO Command
A listing of data elements having decoding tables (or being able to use another data
element’s decoding table) will then appear in browse mode. (See Figure 11-13.)
Notice that information is provided regarding the number of possible values for each
data element, the date the decoding table was last updated, etc. If this information is
not provided for a data element on the list (for example, AFS.DCL1), then the data
element does not have a decoding table of its own, but takes the same values as the
data element listed to its right in the ALIAS column. Therefore IDEA can still
decode it for you.
Chapter 11. IDEA User-Specified Reports 11-21
-------
BROWSE -- Table inforinatior - LiNE 00000000 COL 001 088
COMMAND ===> SCROLL ==> PAGE
TO OF .DMTA **
OB Table Entries Arg len xt len Updated Alias
AFS ANTi 81 2 53 19950123
AFS APC1 12 1 26 19950123
• AFS DATT 10 1 68 19950123
AFSDCAP 16 1 68 19950123
AFS DCLP 10 2 75 19950123
AFS DC L ! DCLP
•AFS OCS? D AP
AFS GOVT 6 1 55 19958123
AFS PLAP 116 5 48 19950123
AFS SCHI DCAP
AGG 08 2 1 7 19950510
A GG SIC 1698 2 50 19940999
AGG TOlD 380 9 50 19950510
OEP database tables not present
OER - database tables not present
C.RM DFRS 28 2 72 19950417
ORM LAWS 33 5 50 19950417
CRM MEDC 11 1 19 19950417
cRM REGN H 2 38 1995.0417
CRM STTE 57 2 35 199&0417
Figure 11-13. 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 dbi.element at the
Command prompt and pressing .
Function: TRISICO
Syntax: TRI SI C(integer, string, dbi.element)
Valid Inputs:
Integer: How many digits you want to compare.
Either 2, 3, or 4.
String: What you want to print out if the test fails.
Data Element Any data element storing SIC codes;
e.g., TRI.SICD or PCS.SIC2.
11-22 IDEA User’s Guide October 22, 1996
-------
Given an integer n, this function will compare all the SIC codes for a given facility
(for the data element specified), and output either the first n digits (if they all match
in the first n digits), or the string that you have specified. As the name implies, this
function was developed primarily for summarizing the TRI.SICD values present for a
facility. For example, the following USR request yields the output in Figure 11-14.
REPORT SICS
DETAIL
TRI.TFID HEAD “TRIS” HEAD “FACILITY ID”
TRI.SICD HEAD TRIS HEAD SIC HEAD YEAR WI 4
TRIS
FACILITY ID
TRIS
SIC
CODE
35O64SSFRFVALLE
““
3
3
3312
3312
359E 4GLFST174SO 33O
33
3312
3312
3312
3312
3312
3312
Figure 11-14. TRIS Facility Ids with SIC codes
Whereas the following USR request prints out the output in Figure 11-15.
REPORT TRISICS
DETAIL
TRI.TFID
HEAD “IRIS” HEAD “FACILITY ID”
TRISIC(2, “MIX”, TRI.SICD) HEAD IRIS HEAD SIC HEAD YEAR WI 4
Chapter 11. IDEA User-Specified Reports 11-23
-------
TRIS TRIS
FACILITY ID SIC
CODE
35O64SSFRFVALLE 33
• 35904G1FST174S0 MIX
356@1MNSNTCOURT 28
72451DRLNGH iY49 25
9874BNCLLSI&60W 29
94572MCLSNOLDHI 29
94565GNRLCNICHO 28
945 5RHNPL5O1Ni 28
94565SSPSCPOBOX 3
94510XXNCS3498E MIX
O634ØPFZRNEASTE 28
054B7CHRMM1i3 JE 34
ö430HNDYH1778K 33
O6511SRGNTIQOSA 34
O64O1NSMCP75LIB 33
Figure 11-15. TRIS Facilities with voted SIC codes
11.3 Controllinrz USR Report Outvut
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
3. request summary information on sorted output.
11.3.1 Restricting Report Data
11-24 IDEA User’s Guide October 22. 1996
-------
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.
— 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.
800001 OUTPUT REPORT HEAVYMETALS
008802 TITLE HReport on Facilities with •T I Releases of Son Heavy Metals”
080083 TITLE “to Water, and PCS Reportable or Significant NonCoinpUance”
000004
000005 RESTRICT
008006 TRI.TcID = 007440666,807448473 ,007440 020,.007440224 AND
000807 TRLRPVR = 1998,1991,1992,1993 AND
000008 TRI.MREST IN L99999999
000809 DETAIL LINE
000810 TRLTFID HEADING TRIS HEADING “FACILITY ID”
800811 TRLSI.CDWIDTH 5 HEADING IRIS HEADING SIC
000012 TRI. PVR WIDTH 6 HEADING TRIS HEADING REPORT HEADING VEAR
000013 TEXT(TRLTCID) HEADING TRIS HEADING CHEMICAL
000014 TRLMREST• DECIMALS 1 HEADING TRIS HEADING RELEASE HEADING ESTIMATE
000015 TRLCREL HEADING TR1S HEADING RELEASE HEADING MEDIUM
000016
800017 INPUT LINKED SELECT
000018 .( / paren before MenuA keywords for convenience in further combining
00001g BEGINNING OF POLLUTION VWQRDS *************** :
000020
900021 (TRI.T ID = 00744 666,007448473,007448 820,0074.4022 AND
Figure 11-16. RESTRICT Keyword Section
Chapter 11. IDEA User-Specified Reports 11-25
-------
in Figure 11-16 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.
I U.S. ENVIRONMENTAL PROTECTION AGENCY 03/08/95
ENFORcEMENT CONFIDENTIAL - FOR EPA INTERNAL USE ONLY
IhTEGRATED DATA FACILITY-USE. SPECIFIED REPORT HEAVYMETALS
REPORT ON FACILITIES t ITH TRI RELEASES OF SOME HEAVY METAL
TO WATERS AND PCS EPORTABLE OR SIGNIFICANT NONCOMPLIANCE
TRIS IRIS TRIS TRIS TRIS TRIS
FACILITY ID SIC REPORT CHEMICAL RELEASE RELEASE
YEAR ESTIMATE MEDI 4
.35994GLF 5T174S0 33 1998 CHROMIUM 831.0 1
3308 48.0 2
3312 3593.0 3
23010.8 5
1900 NICKEL 481.0 1
7.0 2
10180.0 3
8713.0 5
1990 ZINC (FUME
1091 NICKEL 250.0 1
5.0 2
2808.0 3
3000.0 5
35601MNSNTCOU T 2824 1991 NiCKEL 420.0 3
28 9 250.0 5
64090.0 7
1992 NICKEL 420.0 3
Figure 11-17. 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.
11-26 IDEA User’s Guide October 22, 1996
-------
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
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-18 and Figure 11-19.)
DETAIL LINE
TRI.RPYR SORT
TRI.NAME SORT
IRIS TRIS
REPORTING cHEMICAL
YEAR
1987 ALtJMINUM (FUME OR DUST)
1987 ALUMINUM OXIDE
1987 A lONIUM NITRATE (SOLUTIO
1987 CHROMIUM
1987 FORMALDEHYDE
1987 MANGANESE
1987 METHYLENEBIS(PHENYLISOCYA
1987 PHENOL.
1987 SODIUM HYDROXIDE (SOLUTIO
1987 1,i 1-TR1cHLOROETHANE
1988 ALUMINUM (FUME OR DUST)
1988 ALUMINUM OXIDE
1988 AMMONIUMF’IITRATE (SOLUTIO
1988 CHROMIIJM
1988 COPPER
Figure 11-18. Sorting by Reporting Year, then Chemical
DETAIL LINE
TRI.NAME SORT
TRI.RPYR SORT
Chapter 11. IDEA User-Specified Reports 11-27
-------
TRIS IRIS
CHEMICAL REPORTING
YEAR
ALUMINUM (FUME OR DUST) 1987
ALUMINUM (FUME OR DUST) 1988
• ALUMINUM (FUME OR DUST) 1989
• ALIJN1INUM (FUME OR DUSfl 1998
ALUMINUM OXIDE 1987
ALUMINUM OXIDE 1988
AMMONIUM NITRATE (SOLUTIO 1987
AMMONIUM NITRATE (SOLUTIO 1988
AMM NIUM NITRATE (SULUTlO 1989
AMMONIUM NITRATE (SOLUTIO 1998
•AMMONIUM NITRATE (SOLUTIO 1991
AMMONIUM NITRATE (soLuTlo 1992
AMMONIUM NITRATE (SOLUTIO 1993
BIS(2-ETHYLHEXYL) ADIPATE 1991
MS(2-ETHYLHEXYL) ADIPATE 1993
Figure 11-19. Sorting by Chemical, then Reporting Year
113.3 The Summary Line
Keyword: SUMMARY LINE (abbreviated SUMMARY or SUMM)
Syntax: SUMMARY LINE
summaryfieldi [ field modifiers]
summaryfield2 [ field modifiers]
etc.
The SUMMARY LINE keyword and its arguments are an optional part of a USR
request. If SUMMARY LINE arguments are specified, the requested summary infor-
mation will appear after each change in the value of any SORT field - at each
“break” - (as shown in Figure 11-22) or, if no SORT fields were declared on the
Detail Line, at the end of the report.
11-28 IDEA User’s Guide October 22, 1996
-------
— 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
mforrnation on the Detail Line. Whereas items on the Detail Lme apply to
facility data, items on the Summary Lme 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. Data elements (dbi.element) and DEFINE fields from the Detail Line 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 withm a statistical function on the Summary Line.
— Fundamental Concept
If you plan to use a Summary Line, reread the last item a few times until it
sinks in. Understanding why a Detail Line field must be a SORT field in order
to appear on the Summary Line is fundamental to understandmg the Summary
Line. If the field is not a SORT field, it will not have a unique value which
can be prmted on the Summary Line, when it becomes time to print it!
2. Each DEFINE field name must be umque. 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 COUNTO,
SUMO, MEANO, MAXIM UMO, MINIMUMO, and STDDEVO (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.
Data fields on the Summary Line will accept a subset of the field modifiers accepted
by fields on the Detail Line, subject to some restnctions. These are: HEADING,
WIDTH, START, LENGTH, JUSTIFY, and DECIMALS. (See Section 11.2.2.3,
Formatting the Report Data, for details.)
11.3 .3 .1 Statistical Functions
• With the exception of COUNTO, the statistical functions hsted below are for use
with numeric data fields only. (See Appendix C, Data Elements in IDEA Shadow
Files, for a listing of daa element types.)
• IDEA statistical functions can be used only on the Summary Lme.
Chapter 11 IDEA User-Specified Reports 11-29
-------
• 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 m 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 m Figure 11-20:
11-30 IDEA User’s Guide October 22, 1996
-------
TRI flU
RPYR TCID
19B7 808850000
1987 800071556
1987 000101680
1987 808108952
1987 001310732
1987 001344281
1987 006484522
1987 007429805
1987 007439965
1987 087440473
Break . STATS
R COUNT
1987 1. 10
1988 007440508 .
1988 007664939
1988 007448473
1988 007439965
1988 007429905
:::
Figure 11-20. Using COUNTO on the Summary Line
Function: SUMO
Syntax: SUM (summaryfield)
Usage: Summary Line only
The SUM function adds up the data values of the indicated rieia occurnng smce tne
last summary break.
Functions: MAXIMUMO, MINIMUMO
Syinax: MAXIMUM (summaryfield)
Syntax: MINIMUM (summaryfield)
Usage: Summary Line only
Chapter 11. IDEA User-Specified Reports 11-31
-------
MAXIMUM() and MINIMUM() return the maximum and minimum value, respec-
tively, of the specified field occurring since the last summary break.
Function: MEANO
Syntax: MEAN (summaryfield)
Usage: Summary Line only
This function computes the mean, or average, value of the given field smce the last
summary break.
Function: STDDEVO
Syntax: STDDEV (summaryfield)
Usage: Summary Line only
The STDDEV (“standard deviation”) function computes the standard deviation of the
values of the given field occurring smce the last summary break.
In the following example, we take the data printed out in Figure 11-17, 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-21.)
11-32 IDEA User’s Guide October 22, 1996
-------
008001 OUTPUT REPORT HEAVYMETALS
000902 TITLE uReport on Facilities witti TRI Releases of Some Heavy Metalsu
008803 TITLE ilto ater 3 and PCS ReportabTe or Significant NonCompliance”
000904
008805 RESTRICT
300996 TRLTCID = 9B744O666,8974473,00744 0 o2 o 087448224 AND
:039997 TRLRPYR 1998,1 91 3 19 92. 19 3.AND
009808 TRL.MREST IN gg g
908809 DETAIL LINE
000910 TRLTFIO HEADING TRIS HEADING ‘FACILITY ID”
008811 TRI. SICD WIDTH 5 HEADING TRIS HEADING SIC
080912 TRI.RPYR WIDTH 6 HEADING TRIS HEADING REPORT HEADING:YEAR SORT
008813 TRI.JCI&. HEADING TRIS HEADING CREM1CAL SORT
000914 TRLMRE$T DECIMALS 1 HEADING TRIS HEADING RELEASE HEADING ESTIMATE
080815 TRLCREL.HEADING TRIS HEADING RELEASE HEADING MEDIUM 0RT
08I4 SUMMARY
008815 TRI PYR WIDTH 6 HEADING TRIS HEADING REPORT HEADING YEAS
0800 1 TEXT(TRI..TCID) WIDTH :f ADING ThIS HEADING CHEMICAL
008819 TRI £REL HEADING TRIS HEADING RELEASE HEADING MEDIthI
00092:0 .::5UM(TRI EST)f 1999 OECI LS 2 HEADING *TOTAL TRIS ’
008821 HEADING 1 RELEASE, IN ’ HEADING ‘ THOUS. OF LBS’
000022 MEAN(TRIMREST) DECIMALS 1 F ADING LAVERAGES HEADING “IRIS RaEASE ’
008023 4EADIN.G PER FACILITY
000024 MAXI flJM TR1.MREST) DECIMALS 2:.HEADINC MAXIMUM HEADING ‘ TRIS RELEASE
008825 HEADING I PER FACILITY
Figure 11-2 1. USR With Request for Summary Information
Some of the output for the USR request in Figure 11-21 is shown in Figure 11-22.
Chapter 11. IDEA User-Specified Reports 11-33
-------
IRIS TRIS T. IS TRIS TRIS TRIS
FACILITY I D SIC REPORT CHEMICAL RELEASE RELEASE
YEAR ESTIMATE tEDIUM
359040LFST174S O 3300 1990 CHROMIUM 831.0 1
3353 1990 CHROtIIL 2508 .1.
3315 .199 0.CHROMIUM 161.0:1
46312 HCI TT32I0W 3399 1990 CHROMIUM 3349.0 1
7 0058VHSeN.1255P .3412 1990 CHROMIUM 5.01
4070&GNRLM100 I 3714 1390 CHROMIUM 5.0 1
3317. 1990 CHROMIUM 1.0 1
63S73PLSTW1O1ME 3471 1:990 CHROMIUM 5.0 1
3465 1990 CHROMIUM 253.0 1
13126LCNR LAKER 3353 1990 CHROMIUM 5.01
1218 LTCHSSPRIN 3312. 1990 CHROMIUM 220.01
13209CRC8. .STATE 3312 1:990 CHROMIUM 837.0 1
149O2PRLTR3MTRA 3714 1990 CHROMIUM 5.0 1
1390 CHROMIUM 484 8::i.
16I21SHRNSROEME 3312 1990 CHROMiUM 250.0
1990 CHROMIUM 250.0 1
TRIS T JS T.RIS TOTAL IRIS AVERAGE •M XIMUM
REPORT CHEMICAL RELEASE RELEASE, IN IRIS RELEASETRI:S RELEASE
YFAR MFDIUM THOLJS. OF I BPER ACiLITYPFR FAcILITY
1 6.91 43L8 3349.00
33 1990 CHROMIUM 48.0 2
3355 .1990 CHROMIL ’I 1700.0 2
3311 :1990 CHROMIUM 2099.8.2
49072LRSGL23 WE 3009 1990 CHROMIIfl 1 250.0 2
Figure 11-22. USR Output With Summary Information
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:
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-34 IDEA User’s Guide October 22, 1996
-------
tion. Figure 11-23 shows the report generated by the sample query in Figure 11-21
with its Detail Line suppressed (compare with Figure 11-22).
U.S. ENVIRONMENTAL PROTECTION AGENCy 10/21/96
Enforcement onf dentia1 - For EPA Internal Use Only
INTEGRATED DATA FACILiTY-USER SPECIFIED REPORT HEAVYMETALS
REPORT ON FACILITIES WITH TPJ RELEASES OF SOME HEAVY METALS
TO WATER, AND P05 REPORTABLE OR SIGNIFICANT NONCOMPLIANCE
TRIS IRIS T IS T-OTAL IRIS P.VERAGE MAXIMUM
REPORT CHEMICAL RELEASE RELEASE, IN TRIS RELEASETRIS RELEASE
YEAR MEDIUM THOUS. OF LBPER FACILITYPER FACILITY
i o CHROMflIII
431.8 3349.00
2 6.83 379 .7 2099.0 .8
3 11.36 718.3 6313.00
5 :84.4.8 14076.7 25000.90
6 3.27 1090.7 2565.00
7 423.04 12086.9 122844.00
Thtals: 535.88 5700.8 162171.00
NIOKEL
1 3.59 224.6 1278.00
2 4.29 204.4 828.80
3 29.77 1417.4 aeioo.oo
4 6.10 6100.0 6100.90
5 51.32 12830.5 32804.80
5 0.13 45.0 126.00
7 662.43 14720.8 330000.00
Thtals: 757.54 6825.6 381300.00
SILVER 1 0.00 3.0 3.00
2 0.09 47.5 90.9 . 8
6 8.72 359.5 619.00
Totals: 0.82 163.4 712.00
Figure 11-23. Example USR With Detail Line Suppressed
11.4 Regaestin a USR in the Keyword Interface
Creating a meaningful and attractive User-specified Report requires thorough plan-
ning and careful design. Section 11.4.1, Report Design Considerations, below, outlines
some of the questions you should consider when deciding how to organize and format
your report. In addition, familiarity with the various EPA program offices and know-
ledge of the data contained in the corresponding IDEA databases will be he1pfu
when choosing appropriate data elements to display in your report.
Because User-specified Report requests are added to queries using the ISPF editor,
you should be comfortable with the IDEA Keyword Interface before proceeding.
Sections 11.4.2, Preparing a Query in the ISPFPDF Editor, and 11.4.3, Adding the
USR Request to the Query, will remind you of the steps you must take to access the
Chapter 11. IDEA User-Specified Reports 11-35
-------
Keyword Interface and how to use the ISPF editor; however, you may wish to review
Chapter 8, Conducting a Search Using Keywords, and Chapter 9, Managing Keyword
Queries and the JSPF Editor for a more detailed treatment of the subject.
11.4.1 Report Design Considerations
The keywords described m this chapter have been developed to provide you with
maximum flexibility m 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 m the value of the sorted field. 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 m mmd
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-36 IDEA User’s Guide October 22, 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 ISPF/PDF 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-24.
— Caution
When working in the INPUT LIBRARY SELECTION SCREEN, do not press
until you are finished editing the options on the screen; otherwise,
IDEA will take you to the next screen. If is pressed accidently, press
PF3 or type END at the COMMAND prompt and press to return to
the INPUT LIBRARY SELECTION SCREEN.
INPLIT LIBRARY SELECTION SCREEN --88/08/93 19.83(RXG)
COMMAND
Library Name == > UIDACCT.QUERY.SPECS
Library Status(Shr/New/Old ===> SHR
For 8 New’ Only
Tracks ==> 9 O5
irectorv Blocks === 998
Figure 11-24. Library Selection Screen
Press 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-25). (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-37
-------
t4EMBE1 LIST - LJIDACCT.Q1JERY.SPECS ROW 1 TO 12 OF 12
OMMAND t NEWOIJERY SCROLL > CSR
USE B,E,R,U,D’ LEFT OF NAME.
NAME CJIANGED DESCRtPTION ID
QUERYI 3U7O2.1432 UID
QLJERY 3O714J727 I O
QIJERY3 3O525.1B24 UlD
QIJERY4 3U5Z5J7OO 1 110
QUERY5 386B1 .1122 liED
QLJERY g3o 11,111i l iED
QUERY7 38611.1317 1110
QUERY8 36 U.1147 liED
QUERY9 9 387B8.1729 U ID
BOTTOM OF DATA
Figure 11-25. Member List Screen
Section 5.2, Managing Queries Using the Member List, explams the commands that
allow you to browse, create, retrieve, rename, describe, and delete the queries in your
Member List. These commands are repeated below m 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 Browse/Read the query; no editing possible.
E (or S) query Edit/Select an existing query or create a new one in
the editor.
R query Rename the query.
U query Update the query descnption.
D query Delete the query from the MEMBER LIST.
You can add a USR request to an exlstmg query by typmg 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 , 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 @#S%\
After you make your selection on the MEMBER LIST SCREEN, press ,
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-38 IDEA User’s Guide October 22, 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 wifi be displayed on the EDIT SCREEN,
as shown in Figure 11-26.
EDIT ---- U IDACcT.QUERV.SPECS(USRQUERY) COLUMNS 001 072
COMMAND == > SCROLL HALF
* *** ** ******** ** * * **k ** TOP OF DATA
009001 *1
000002 /
900003 /* Keywords generated by Menu A literface *1
000004 i *1
800005 /* 1994.11.29 12.01.13 *1
008006 /
• 000887 /* •.. *1
088008 OUTPUT REPORT 1A
000099 INPUT LINKED SELEcT
• 008810 ( / paren before enuA keywords for convenience in further combining
000011 BEGINNING OF POLLUTION KEYWORDS
000012
000013 (TRI.TCID = 0074406664897440413 AND
008814 .(TRI.CREL = 3 AND
000815 TRI.MREST IN :1009,99999999fl
000816
000817 EN OF POLLUTION KEYWORDS
000018 AND
90801 / Noncomp lance keywords /
008020 (((PCS.LRNC=D,E,N,S.T & POS.MADI=M a PCS.IACc=Afl)
000921 ) / paren after MenuA keywords for convenience in furtner combining
Figure 11-26. Example Query in the ISPF Edit Screen
11.43 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 [ .]/WIDTH/...]
etc.
[ SUMMARY LINE
summaryfield [ SORT/WIDTH/HEADING!...]
etc.]
[ output destination]
Chapter 11. IDEA User-Specified Reports
11-39
-------
Insertmg your USR request, m with your standard report request(s), can be accom-
phshed with the line edit commands discussed m Section 9.2, Keyword Queries and the
ISFF 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 Movethishne
R Repeat this line
A Place after this line
B Place before this line
X Exclude a line
11.5 Runnjn2 Oueries and Viewin ’ Reports
To run your query, use or to move your cursor to the
COM MAND prompt on the EDIT SCREEN, type GO, and press . IDEA
will process the query and display the QUERY STA TUS SCREEN shown below in
Figure 11-27. On this screen, IDEA displays the followmg the time of day when it
finished running the query, the number of facilities found in the search, whether or
not they are m FINDS (i.e., have valid FINDS identification numbers), and a chart
indicating the databases relevant to the search. This chart vanes for Linked, Non-
linked, and Linked Nonhnked quenes.
11-40 IDEA User’s Guide October 22, 1996
-------
- QL ’ER STATUS SCREEN -
COMMAND ===>
13 :34 :36 .34 - •5 Facilities selected and in FINDS
Counts (percentages), by database, of facilities selected but
exclude ! because they were not presert in FINDS:
AFS 5 13 C 35) PcS 1341 ( 70)
RCR O( 0) TRI O( 0)
: .:. FI l l e( 3) .
Press ENTER to continue, END to return to start
Figure 1 1 -27. 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
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-28).
11-41
Chapter 11. IDEA User-Specified Reports
-------
BROWSE - Report: ADHOC---- in Pro9ress MAX 800029 LINE 00008000 CCL 001 000
COMMAND ===
Issue coni nand PRINTO to print, or SAVE to save to dataset.
************************* ******* TOP OF DATA **************** *****************
I U.S. ENVIRONMENTAL PROTECTION AGENC
ENFORcEMENT cONFIDENTIAL - FOR EPA IN
INTEGRATED DAjA FACILITY-USER SPECIFIED R
REPORT ON FACILITIES WITH TRIS RELEASES OF
AND PCS REPORTABLE OR SIGNIFICANT
• REPORT FU MAI
• OBID ELEMENT .1EV LEN COLUMN SORT T L/ DESCRIPTION / COMPUTATION
NAME EL GIN A/U TOT
1 FIN E°ID 3 28 1 Y EPA-ID
2 FIN FNME 4 20 22 FACILITY-NAME
3 TRI RPYR 3 28 43 REPORTING-YR
4 TRI TCID 3 9 64 TR1-CHEMICAL - ID
5 fRI MREST 4 0 74 Y RELEASE ESTIMATE BY RELEASE ME
6 TRI NAME 3 20 74 A CHEM-NANIE
7 RELEASE 4 28 95 Y TRI.MREST 1000 /
8 TRI CREL . . 4 20 116 RELEASE-MEDIUM
Figure 11-28. Viewing a USR in Browse Mode
Regardless of the report format(s) selected, the title line of the BROWSE SCREEN
wifi 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 mu1tip e report formats, type SW (switch) at the COMMAND prompt
and press to switch to the next report.
Use the commands in Table 11-4 to view your report in the BROWSE mode.
11-42 IDEA User’s Guide October 22, 1996
-------
Table 11-4. Commands for Navigating Reports
11.6 Printing Revorts
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 every few seconds until” COMPLETE”
appears. IDEA allows users to print part or all of a report by specifying line
numbers (see Figure 11-29).
Commands
UP /
Descriptions
DOWN /
LEFT /
RIGHT /
END /
SWAP /
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 Imes entered at the COMMAND prompt
Scrolls right by the amount set at the SCROLL prompt, or by the
number of hnes entered at the COMMAND prompt
Saves and returns to the previous screen.
Moves the cursor from a position in one screen to the same posi-
tion in another using the split-screen mode
MANEUVERING THE CURSOR
Arrow keys
M(&x)+
M(ax)+
M(ax) +
Minv +
Use arrow keys for all directions
Use key to move to the next input field
Use to move to the top-left input field
Scrolls up to the first line of a report,
Scrolls down to the last line of a report,
Scrolls to the right margin of a report,
SirMk fri the left m roin i rer inrl
Chapter 11 IDEA User-Specified Reports
11-43
-------
BROWSE - Report: ADHOC---- Complete--- MAX 802598 LINE 00008021 CDL 001 088
COMMAND ==>
Issue coniiiand PRII4TC to print, or SAVE to save to dataset.
U.S. ENVIRONMENTAL PROTECTION AGENC
ENFORCEMENT CONFIDENTIAL - FOR EPA IN
INTEGRATED DATA FACILITY-USER SPEEIFIED R
REPORT ON FACILITIES WITH TRIS RELEASE OF
AN P S REPORTABLE OR SIGNIFICANT
FINDS FINDS TRIS IRIS TRIS RELEASE TRIS
FACILiTY ID FACILITY NAME(S) REPORT CHEMICAL BY MEDIIW, IN RELEASE
YEAR THOUS. O LBS MEDIUM
AL 0008161416.T.R. MILLER MILL OM cHROMIUM 0.44 7
T R MILLER CO INC 0.05 7
I R MILLER MILL COMP
MILLER T R MILL CO I
MILLER T R MILL CO I
T. R. MILLER CO. iNC
MILLER T RMILL CONIP
ARD990 869737 CROSS OIL & REFINING ZINC (FUME 0.25 1
CROSS OIL-SMACKOVER YINC (FUME 0.25
CROSS OIL AND REFINI
Figure 11-29. A “Complete” USR
2. Type PRINTO at the COMMAND prompt and press . The
PRINT,’SA VE PARAMETER SCREEN will pop up (see Figure 11-30).
Print/Save Parameter Screen
From line no.===> to line no.===
_______ For printing
Bin
FINDS I Destination ===> OW
Addres No. of copies
RCRIS H
Name For saving enter DSN or DSN menthername
ISO
Owne
(insert USR here!)
Figure 11-30. 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
. At the TO LINE NO. prompt, type the MAX number that appears at
11-44 IDEA User’s Guide October 22, 1996
-------
the upper nght corner of the BRO WSE screen and press . The MAX
number corresponds to the final line of the report when it is “COMPLETE”.
4. IDEA also allows users to pnnt 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 I 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 to the TO
LINE NO. prompt. Type the ending line number and press .
5. At the FOR PRINTING - BIN prompt, type your site specific BIN number and
to the DESTINATION prompt. Type your site specific printer destma-
tion ID (or press to send your print to the HOLD queue) and
to the NO. OF COPIES prompt. Type the number of original copies you wish to
receive and press . The default setting for print destination is HOLD
and the default for the number of copies is 1.
— helpful hint
If you choose to send your output to the HOLD queue (or if you press
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-31.
Chapter 11 IDEA User-Specified Reports 11-45
-------
V1R3M3 - SDSR PRIMAR OPTION MENU -.
COMMAND INPUT ===> SCROLL ===> PAGE
P•REFIX=UID t DES T =(ALL) OWNER=
Type an option or connand and press Enter.
LOG - Display the system log
BA - Display active users o the system
I - Display joos in the JES2 input queue
0 - Display jobs in he JES2 output queue
H - Display jobs ir the JES2 held output queue
ST - Display st t s of jobs in the JES2 queues
PR - Display JES2 printers on this system
INIT - Display JES2 initiators on this system
T uTOR - Short course on SDSF ( SPF only)
END - Exit SDSF
Licensed Materials - Property of IB M
5565-488 (C) .opyright IBM Corp. 1981, 1992. All r ghts reserved.
US Government Users Restricted Rights - Use! duplication or
disclosure restricted by U SA ADP.Sct eduie Contract with IBM Corp .
Figure 11-3 1. SDSF Primary Option Menu Screen
2. Type 0 at the COMMAND prompt and press 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-32.
SDSF OUTPUT ALL cLASSES ALL FORMS LINES 802 LINE 1_i (1)
COMMAND INPUT ===> SCROLL ===> PAGE
NP JOBNA E Jobid Dest C Fo F B UCS Writer Tot-Rcds Status Device
U 1D24 J 0a07224 R255 A SIB **** 802
Figure 11-32. SDSF Output Queue Screen
3. Press 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 two times.
Destination options:
WIC Prints at the Washington Information Center (WIC) at EPA Head-
quarters, Washington, DC.
11-46 IDEA User’s Guide October 22, 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 . The DS LiST SCREEN will appear.
c. down and type B (Browse) next to the
JUSD.REMOTE.DATA member. Press 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 in step 3 a message reading COM MAND
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 the second time, the correct destination will again
be displayed. (Compare Figure 11-33 with Figure 11-34 .)
SDSF OUTPUT ALL CLASSES ALL FO 1S LINES 802 COMMAND ISSUED
COMMAND INPUT ===> SCROLL ===> PAGE
NP JOBNAME ,Jobid Dest C Form FCB UCS Writer Tot- cds Status Device
U1D24 J 0B07224 R255 A STD 802
Figure 11-33. SDSF Output Queue - “Command Issued” Screen
Chapter 11. IDEA User-Specified Reports 11-47
-------
SDSF OUTPUT ALL CLASSES ALL GRMS LINES 598 LINE 1- (1)
COMMAND INPUT ===> SCROLL PAGE
NP JOBNAME 1 Jobid Dest C Form FCB UCS Writer Tot-Rcds Status Device
U 1024 OBO7224 RMTO A STO 802 R505.P
Figure 11-34. 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 . 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 Savinii 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 fmished processing the query report. If”IN PROGRESS”
is displayed, press every few seconds until “COMPLETE” appears.
Position the cursor at the COMMAND prompt.
2. Type SAVE at the COMMAND prompt and press . The
PRINTI’SA VE PARAMETER SCREEN wifi pop up (see Figure 11-30).
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 . 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 BRO WSE screen and press .
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-48 IDEA User’s Guide October 22, 1996
-------
11.8 Exitinj Reports
Type END at the COMMAND prompt or press PF3 to return to the EDIT SCREEN
after viewing, prmtmg, 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 FF3 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 offenng a selection of pre-defmed 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 quenes in IDEA’s Keyword Interface via
the ISPF editor and, like the quenes, 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. Famihanty with
the EPA program offices and knowledge of the data contained in the corresponding
IDEA databases is also helpful m choosing appropriate data to display in the report.
Chapter 11 IDEA User-Spec fied Reports 11-49
-------
When these considerations are taken into account, User-specified Reports allow
IDEA users create meanmgful and useful reports with a personal touch.
11-50 IDEA User’s Guide October 22, 1996
-------
Appendix A. Access and Security Procedures for IDEA
The followmg information details the procedures for obtauung access to enforcement
sensitive data m IDEA and secunty 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 authonze indi-
vidual EPA User-IDs to gam Sensitive Access to IDEA. Revisions to the origmal
procedure have been “redlined”.
The IDEA system supports two levels of access to EPA program office enforcement
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 infor-
mation. OECA, in conjunction with each national system administrator, has identi-
fied the data that each program office has determined is enforcement sensitive.
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. Access to enforce-
ment 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 pohcy memorandum describmg the Access and Secunty procedures for IDEA is
reproduced in its entirety below.
Appendix A Access and Security Procedures for IDEA A-I
-------
MEMORANDUM
SUBJECT Access and Security Procedures for EPA’s
Integrated Data for Enforcement Analysts (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 and Compliance Assurance (OECA)
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 capabihty 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 OECA’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) OECA, 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 OECA was able to
report through the FM FIA 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 October 22, 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, OECA 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 mamframe 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, OECA 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-lds (see AU.achment 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 Disciphne, and its Attachment, entitled ‘Guidance on Corrective Disciphne, 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 (Superfund), the Toxics Release inventory, the
Enforcement DOCKET, the FFIS (Federal facilities), and the Facility Index System.
OECA will develop a method that blocks access to enforcement sensitive information but which continues
to permit access to alt 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 OECA 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), OECA will continue to
rely on the Agency’s Strategically Targeted Activities for Results System (STARS) reporting process
The quantitative 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 regardmg training
or user access should be directed to the IDEA User Support Line (202 564-2475)
A . 1 Attachments
A-4 IDEA User’s Guide October 22, 1996
-------
Office of Enforcement and Compliance Assurance Procedures for
Access and Secunty 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 and Compliance Assurance (OECA) 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 gaming authonzation to Sensitive Access )
IDEA Users authorized for Sensitive Access are governed by the provisions of EPA
Order 3120.1 assued September20, 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 Ill below
In accordance with EPA policies that encourage broad access to information, OECA
intends to estabhsh a second level of access, known as Non-Sensitive Access , as soon as
possible in FY 1992. OECA will develop a method that blocks access to enforcement
sensitive mformation 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 OECA will
conduct with each national system administrator to idenW the data that each program has
determined are enforcement sensitjve.
II. Process for Obtaining Authorization for Access to Non-Sensitive information
EPA’s National Computer Center (NCC) is responsible for controlling EPA mainframe computer
User-lds 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 NCCs 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 NTIS at 703-487-4830 to begin the
process of establishing an NCC account
Ill 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 Division Director of OECA’s
Enforcement Planning, Targeting, and Data Division a memorandum (a sample memorandum is
included in Attachment 2(a)) requesting access Upon receipt of the memorandum, the
Appendix A Access and Security Procedures for IDEA A-5
-------
employee’s 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 mformation in order to
conduct targeting, screening, case development, hLigation 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 Division Director of OECA’s Enforce-
ment Plannmg,Targeung, and Data Division a memorandum (a sample memorandum is included in
Attachment 2(b)) requesting access Upon receipt of the memorandum, the employee’s User-ID will
be authorized
3 EPA Office of Enforcement and Comphance Assurance - OECA will determine which of its
employees have a need-to-know sensitive information in order to conduct targeting, screemng, 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 Division Director of OECA’s Enforcement Planning, Targeting,
and Data Division a memorandum (a sample memorandum is included in Attachment 2(c))
requesting access Upon receipt of the memorandum, the employee’s 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, htigation 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., the Deputy Regional Administrator
or Headquarters Office Director) will need to submit to the Division Director of OECA’s Enforce-
ment Planning, Targeting, and Data Division, a memorandum (a sample memorandum is included in
Attachment 2(d)) requesting access. Upon receipt of the memorandum, the contractor employee’s
User-ID will be authorized
S. List of Users with Sensitive Access - OECA will maintain a list of users whose EPA User ID’s have
been auLhonzed 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-I. Attachment 1
A-6 IDEA User’s Guide October 22, 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 Frederick F Stiehl, Director
Enforcement Planning, Targeting, and Data Division (2222A)
Office of Compliance
With this memorandum, we request that the EPA User ID _____, assigned to employee.
___________________ be authorized for Sensitive Access to 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 Lreat 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 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 notilying 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 applicant(s) 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 ________. Office Director
TO Frederick F. Stiehl, Director
Enforcement Planning, Targeting, and Data Division (2222A)
Office of Compliance
With this memorandum, we request that EPA User-ID _____, assigned to employee:
__________________ be authorized for Sensitive Access to 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.fMs _____________________ 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 notil ing 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
Auachment, entitled ‘Guidance on Corrective Discipline’ prescribe policies and penalties
regarding breaches of security regulations or practice.
The applicant(s) 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 R.ACF 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 October 22, 1996
-------
MEMORANDUM
SUBJECT Request for Authorization of EPA Mainframe User-ID
FROM Name of Employee, Title, Program, EPA Mainframe User-ID
THROUGH ________, OECA Office Director
TO Frederick F Stiehi, Director
Enforcement Planning, Targeting, and Data Division (2222A)
Office of Compliance
With this memorandum, we request that EPA User-ID _____, assigned to employee
_________________ be authorized for Sensitive Access to OECA’s Integrated Data for
Enforcement Analysis (IDEA) system This request is based on our determination that
Mr.fMs. ___________________ 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 notiJ ing 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 secunty regulations or practice
The applicant(s) 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 and Compliance Assurance 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, Title, Program, EPA Mainframe User-ID
THROUG H _______
EPA Project Officer
Deputy Regional Administrator or Headquarters Office Director
TO Frederick F. Stiehi, Director
Enforcement Planning, Targeting, and Data Division (2222A)
Office of Compliance
With this memorandum, we request that EPA User-ID _____, assigned to contractor employee
__________________ be authorized for Sensitive Access to 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 lus /lier 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 notil ing OECA when the User-ID’s sensitive access right is to be
terminated
The applicant(s) 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 R.ACF protection of their JES2 output queue,
which may contain output reports waiting to be printed or purged.
cc Contractor Project Officer
Figure A-5. Attachment 2(d) - Sample EPA Contractor Employee Memorandum
A-1O IDEA User’s Guide October 22, 1996
-------
MEMORANDUM
SUBJECT Request for Authorization of EPA Mainframe User-ID
FROM Name of Employee, Title, Program, EPA Mainframe User-ID
THROUGH _________________
TO Frederick F. Stiehi, Division Director
Office of Enforcement and Compliance Assurance
Office of Compliance
Enforcement Planning, Targeting, and Data Division
With this memorandum, we request that EPA User-ID _______, assigned to employee
___________________ be authorized for State Sensitive Access to 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 state sensitive information in order
to conduct assigned duties m 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 State Sensitive Access is granted, the State agrees that such
access will be terminated in the event that his/her duties in the State no longer support the
need-to-know this information, or his/her employment by EPA has ceased
The State further acknowledges that it is responsible for notifying OECA when the User-ID’s
state sensitive access right is to be terminated We understand that IDEA Users authorized for
State 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 applicant(s) for State 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-6. Attachment 2(e) - Sample State Enforcement Agency Employee Memorandum
Appendix A Access and Security Procedures for IDEA A-Il
-------
A-12 IDEA User’s Guide October 22, 1996
-------
Appendix B. Database Descriptions
B.1 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
Aerometnc Information Retneval System (AIRS). AIRS is a computerized
database management system for airborne pollution m the United States
consisting of four subsystems. Each subsystem addresses a different (but m
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
mdustnal 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 facilities which are solely asbestos demolition and/or renovation
contractors, or landfills. However, as of May 1996, IDEA includes data on
facilities that are not federally reportable. As a result, IDEA includes data
on facilities which are planned, under construction, operate seasonally,
temporarily shut down, and shut down.
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 mformation
Appendix B Database Descriptions B-I
-------
• 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 Corn-
phance Status -- quarterly for past two years (1992 to present).
Pollutant information -- identifiers, classifications, compliance status,
etc. Action/Activity Data -- inspections, enforcement actions, etc (1978
to present). Operatmg 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 Liabthty Act Information System (CERCLIS) contains the official
inventory of CERCLA sites, and mtegrates 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 umt (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 larg’e sites mto
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 mcluded on the National Pnonties 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.
B-2 IDEA User’s Guide October 22, 1996
-------
IDEA’s standard CERCLIS report lB displays data based on the OU
structure; however, most reports show enforcement data with the events
using the lmks feature of WasteLAN (the PC data entry system for
CERCLIS). This data can also be displayed after the last OU (due to a
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 mvestigation/feasibthty 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 Mamframe/ADABAS
Data Owner(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 mformation 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
Appendix B Database Descriptions B-3
-------
contain information similar to that for admimstrative 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
contams a subset of the DOCKET data which mcludes:
• 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 (DM1) 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 mcludes:
B-4 IDEA User’s Guide October 22, 1996
-------
• 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 quenes to retrieve information about all the businesses/facilities
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 retneve “corporate profile” data from IDEA. The data ele-
ments that IDEA accesses are hsted 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 retneval 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
• Matenal released
• Cause of release
• Damage/injuries/deaths
• Amount released
Appendix B Database Descriptions B-5
-------
• Source of release
• Incident location
• Response actions taken
• Authonties notified
• 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 mcident can appear more than once.
An update on the incident might be added to the system after the event
took place and the ongmal 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 & lB. 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 FF1
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 rmcrocomputer/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 monitonng and planmng projects which are
intended to bring federal facilities into compliance with current environ-
mental regulations or to mamtam comphance. The FFIS provides the fol-
lowmg
• An inventory of all federal facilities for which pollution abatement
projects have been reported to the Office of Management and Budget
(0MB) through EPA.
• The compliance status of any facility with applicable regulations.
B-6 IDEA User’s Guide October 22, 1996
-------
• Information on projects planned or initiated to bring the facthty into
compliance wnh current regulations, to maintain compliance, or to
achieve compliance with future regulations.
• Budget information as required by 0MB for the A-106 report. The
FFIS database stores mformation 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
of the project regarding design, tirnmg, and funding. Budget informa-
tion required by 0MB 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, m preparation for the
0MB report. Appendix C presents the FFIS data elements m 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 Piatform/Software: IBM ES9000 Mamframe/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 umque EPA ID number, name,
and physical address.
• Pointers to other sources of information-- EPA program office data-
bases which contam more detailed mformation 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 mamtains mclude:
• EPA Facility ED Number -- a unique and meaningless number
assigned to each facility.
Appendix B Database Descriptions B-7
-------
• FINDS Facthty 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.
• 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 hnk one or more System Identifiers to the same EPA ID Number.
FINDS problems for the IDEA user include maccurate 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 ADABAS 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 Crinunal 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.
5 -8 IDEA User’s Guide October 22, 1996
-------
B.9 NCD
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.1O 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 Comphance, U.S. EPA.
Appendix B Database Descriptions B-9
-------
System Contact: PCS User Support (202) .564-7277
System Platform/Software: IBM ES9000 Mamframe/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 mamtamed by the Office of Comphance 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
• Descnptions 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 m related groups which par-
allel the data’s hierarchical relationships.
B.11 RCR
System Name: Resource Conservation and Recovery Infonnation System
Acronym: RCRIS
Regulation for Data Collection: Resource Conservation and Recovery Act
B-b IDEA User’s Guide October 22, 1996
-------
System Owner! Operator: Office of Solid Waste, Office of Solid Waste and Emergency
Response, U.S. EPA
System Contact: RCRA Hotime (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 mventory system of
RCRA hazardous waste handlers. Handlers fit one or more of the fol-
lowing categones: treatment, storage and disposal facilities (TSDFs), large
quantity generators (LQG5), small quantity generator (SQGs), and trans-
porters. RCRIS contains:
• 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 inspections or other enforcement
activity. The information m 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, U.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 B Database Descriptions B-Il
-------
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 EPAs 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 m
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 Hothne (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-
facturmg mdustnes, 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 October 22, 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 foUowmg
• 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 m 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 111+
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) for the efficient delivery of mail, they
therefore do not generally respect political or census statistical area bound-
anes. ZIP Codes usually do not have clearly identffiable boundaries, often
serve a contmually 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.
Appendix B Database Descriptions B-13
-------
The types of statistics available for each ZIP Code mclude total popu-
lation, ethnic demographics, median incomes, fraction employed, and per-
centages of families and households in certam mcome brackets.
Appendix C presents the ZIP data elements in related groups which parallel
the data’s hierarchical relationships.
B-14 IDEA User’s Guide October 22, 1996
-------
Appendix C. Data Elements in IDEA Shadow Files
This Appendix presents the data elements mcluded in IDEA’s “shadow files,” or
copies of the EPA Program Office database files. The following points should be
kept in mmd when referencing these data element listings:
1. Not all of the data available from the Program Office data systems may be
mcluded in the IDEA shadow files.
2. A data element must be indexed m 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 cnterion is indexed.’ (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 retneval use and do not exist as such
m the Program Office databases.
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 m 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 m 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 m 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-I); the (external) LENGTH of the data
field; and a bnef DESCRIPTION of the data element.
I Two exceptions to this rule are DCK.RSOF and 1ST RSOF, which are mdexed, but cannot be used as Select criteria
Appendix C Data Elements in IDEA Shadow Files C-I
-------
Table C-i. Descriptions of Data Types
Code
Data Type
Description
Char
Character
May include alphabetic or numenc data
Date
Date
Expresses the date as a string of numbers; check the
descnption for the specific format
Num
Numenc
Only numenc data may be present; may be integer or
decimal format
Intg
Integer
Only integer numeric data may be present
Text
Text
Essentially the same as Char; unique to CERCLIS
C.1 AFS-AIRS Facility Subsystem Data Elements (9/96 )
Index? Enforc
(V/N) Sens?
(V/S/N)
Group
Repeat EJement Name
Record?
Data
Type
Length Description
AFS ID(A)
N
AFSID
Y
N
Char 10
AFS Identifier State-County-Plant Number
PGM CODE(S)
N
APCI
Y
N
Char I
Air Program Code
ASTI
Y
N
Char I
Air Program Status
SOURCE(A)
N
REGN
AQCA
PNME
STRT
CYNM
SICI
SIC2
SICC
SVII
SV I2
SVI3
SVI4
DCS I
DCLI
GOVT
VIOLQTR
INSPDAY
FEDREP
STAB
OPST
Y
Y
N
N
N
Y
Y
Y
Y
N
N
N
Y
Y
Y
V
V
V
Y
V
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Char 2
Num 3
Char 26
Char 30
Char 30
Num 4
Num 4
Num 4
Char I
Char I
Char I
Char I
Char 1
Char 2
Char I
Num 2
Num 5
Char I
Char 2
Char I
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 I
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
Federally Reportable? (V/N)
AFS State Code
Operating Status (O,C,T,X,I)
HIST COMPL A)
Y
V
HMONTH(K)
HSVII(K)
HDCSI
V
V
V
N
N
N
Date 4
Char I
Char I
Date of Histoncal Compliance Extract from AFS (YYYYMM)
Histoncal Significant Violator Flag
Histoncal EPA Compliance Status
HIST COMPL(B)
Y
HDTI(K)
SCHI
Y
Y
N
N
Date 4
Char I
Historical Compliance Dale (YYQQ)
Historical Compliance Status
POLLUTANT(B)
Y
PLAP(K)
DCAP
DCLP
DAli ’
RUDT
TURN
V
V
V
V
Y
Y
N
N
N
N
N
N
Char S
Char I
Char 2
Char I
Date 4
Num 4
Pollutant Code
Pollutant Comphance Status
Pollutant Classification
Attainment/Non-Attainment Indicator
Repeat Violation Date (YYQQ)
Turnover Compliance Flag
ACTIONS(B)
Y
DTAI(K)
ACSEQ(K)
ANTI
PAMI
Y
N
Y
V
S
S
S
S
Date 7
Num 4
Char 2
Num 7
Date Achieved (YYMMDD)
Sequence Number
National Action Type
Penalty Amount (in thousands of dollars)
C-2 IDEA User’s Guide
October 22, 1996
-------
C.2 CBG-Census Block Group Data Elements (9/96 )
Group Repeat Element Name Index? Enforc Data Length Dcscnption
Record? (Y/N) Seas? Type
(V/S/N)
GEOG(A) N STATE N N Char 2 State Code
COUNTY N N Char 3 County Code
TRCTBNA N N Char 6 NSUS Tract/Bleck Numbering
DEMOGR(A) N AREALAN Y N Num 9 Land Area
AREAWAT Y N Num 9 Water Area
P010001 V N Num 9 Persons, Total
P030001 Y N Num 9 Households, Total
P040001 Y N Num 9 Persons, Urban, inside Urbanized Area
P040002 Y N Nurn 9 Persons, Urban, Outside Urbanized Area
P040003 V N Num 9 Persons, Rural
P050001 V N Num 9 Persons, Male
P050002 Y N Num 9 Persons, Female
P060001 Y N Num 9 Persons, White
P060002 Y N Num 9 Persons, Black
P060003 Y N Num 9 Persons, American Indian, Eskimo Or Aleut
P060004 Y N Num 9 Persons, Asian Or Pacific Islander
P060005 Y N Num 9 Persons, Other Race
P080001 Y N Num 9 Persons Of Hispanic Origm
P100001 V N Num 9 Persons, Not Of Hispanic Origin, White
MINORTY V N Nuin 9 Persons, Minonty
TNWH ITE Y N Num 9 Persons, Total No White
P100006 Y N Num 9 Persons, Hispanic Origin, White
POPDNSE V N Num 9 Population Density
WPPDNSE V N Num 9 White Population Density
BPPDNSE V N Num 9 Black Population Density
AIPUNSE V N Num 9 American Indian Population Density
APPDNSE V N Num 9 Asian Population Density
OPPDNSE V N Num 9 Other Population Density
HPPDNSE Y N Num 9 Hispanic Population Density
P070001 Y N Num 9 Persons, White Persons
P070002 V N Num 9 Persons, Black Persons
P070003 Y N Num 9 Persons, American Indian
P070004 Y N Nurn 9 Persons, Eskimo
P070005 V N Num 9 Persons, Aleut
P070006 V N Num 9 Persons, Chinese
P070007 V N Num 9 Persons, Filipino
P070008 Y N Num 9 Persons, Japanese
P070009 Y N Num 9 Persons, Asian Indian
P070010 V N Num 9 Persons, Korean
P070011 V N Num 9 Persons, Vietnamese
P070012 V N Num 9 Persons, Cambodian
P070013 Y N Num 9 Persons, Hmomg
P070014 V N Num 9 Persons, Laouan
P070015 Y N Num 9 Persons, Thai
P0700 16 Y N Num 9 Persons, Other Asian
P070017 Y N Num 9 Persons, Hawaiian
P0700 18 V N Num 9 Persons, Samoan
P0700 19 V N Num 9 Persons, Tongan
P070020 V N Num 9 Persons, Other Polynesian
P070021 V N Num 9 Persons, Guamaman
P070022 V N Num 9 Persons, Other Micronesian
P070023 V N Num 9 Persons, Melanesian
P070024 V N Num 9 Persons, Pacific islander, Not Specified
P070025 V N Num 9 Persons, Other Race
PSLEG5V V N Num 9 Persons Not > 5 Years Old
PSLE I7Y V N Num 9 Persons Not > 17 Years Old
PSGE I8Y V N Num 9 Persons Not < 18 Years Old
PSGE65Y V N Nun 9 Persons Not <65 Years Old
P180001 V N Num 9 Households, Family, Married Couple With Kids
P180002 V N Num 9 Households, Family, Male Householder(No Wife)
Appendix C Data Elements in IDEA Shadow Files C-3
-------
Group Repeat Element Name Index? Enforc Data Length Description
Record? (V/N) Sens? Type
(Y/S/N)
With Kids
P180003 Y N Num 9 Households, Family, Female Householder (No
Husband) With Kids
NFWK IDS V N Num 9 Households, Nonfamuly, With Kids
P180006 Y N Num 9 Households, Family, Married Couple Without Kids
P180007 Y N Num 9 Households, Family, Male Householder(No Wife)
Without Kids
P180008 Y N Num 9 Households, Family, Female Householder (No Husband)
Without Kids
NFWOKID V N Num 9 Households, Nonfamuly, Without Kids
P280001 Y N Num 9 Persons In Correctional Institutions
P280002 V N Num 9 Persons in Nursing Homes
P280003 V N Num 9 Persons in Mental Institutions
P280004 Y N Num 9 Persons In Juvenile institutions
P280005 Y N Num 9 Persons In Other Institutions
P280006 Y N Num 9 Persons in College Dormitories
P280007 V N Num 9 Persons In Military Quarters
P280008 V N Num 9 Persons ln Emergency Shelters For Homeless
P280009 V N Num 9 Persons Visible In Street Locations
P280010 Y N Num 9 Persons In Other Nonmstitutional Group Quarters
FINURB V N Num 4 Persons, Urban, Fraction imude Urban Area
FOUTURB V N Num 4 Persons, Urban, Fraction Outside Urban Area
FRURAL V N Num 4 Persons, Fraction Rural
FMALE Y N Num 4 Persons, Fraction Male
FFEMALE V N Num 4 Persons, Fraction Female
FWH1TE V N Num 4 Persons, Fraction White
FBLACK V N Num 4 Persons, Fraction Black
FAMRIND V N Num 4 Persons, Fraction American Indian
FASIAN Y N Num 4 Persons, Fraction Asian
FOTHER V N Nuni 4 Persons, Fraction Other
FHISPAN V N Num 4 Persons, Fraction Hispanic
FWHNOHS V N Num 4 Persons, Fraction White Non Hispanic
FMINOR V N Num 4 Persons, Fraction Minority
FTNWHT V N Num 4 Persons, Fraction Total Not White
FWHHISP V N Num 4 Persons, Fraction White Hispanic
FPNL5YR Y N Num 4 Fraction Persons 5 Years Old Or Younger
FPNL I7Y V N Num 4 Fraction Persons 17 Years Old Or Younger
FPNGI8Y V N Num 4 Fraction Persons Not Younger Than 18 Years Old
FPNG 5Y V N Num 4 Fraction Persons Not Younger Than 65 Years Old
FPWK ID V N Num 4 Fraction Households With Kids Single Male Or Female
Householder
FPGRQTR V N Num 4 Fraction Persons In Group Quarters
H010001 V N Num 9 Housing Units
HSNDENS V N Nuni 9 Housing Units Density
H020001 V N Num 9 Occupied Housing Units
H020002 V N Nun, 9 Vacant Housing Units
H030001 V N Num 9 Owner Occupied Housing Units
H030002 V N Num 9 Renter Occupied Housing Units
FOCCHUN V N Num 4 Fraction Occupied Housing Units
FVACHUN Y N Num 4 Fraction Vacant Housing Units
FOOCHUN V N Num 4 Fraction Owner Occupied Housing Units
FROCHUN V N Num 4 Fraction Renter Occupied Housing Units
INPTLAT N N Nuni 5 Lauude
INPTLNG N N Num 5 Longutude
NUMHH(A) N BGD200I V N Num 9 Total Households Linguistically Isolated
P290001 Y N Num 9 Enghsh Speaking Households
P290002 Y N Num 9 Linguistically Isolated Spanish Speaking Households
P290003 Y N Num 9 Not Linguistically Isolated Spanish Speaking
Households
P290004 Y N Num 9 Linguistically isolated Asian Or Pacific Island
Language Speaking Households
P290005 Y N Nuni 9 Not Linguistically Isolated Asian Or Pacific Island
Language Speaking Households
P290006 V N Num 9 Linguistically Isolated Other Language Speaking
H ouseholds
P290007 V N Num 9 Not Linguistically Isolated Other Language
C-4 IDEA User’s Guide October 22, 1996
-------
Group Repeat Element Name index? Enforc Data Length Description
Record? (V/N) Sens? Type
(V/S/N)
Speaking Households
P570001 Y N Num 9 Less Than 9th Grade Graduated Persons 25 Years
And Older
P570002 Y N Nuin 9 9th To 12th Grade, No Diploma Persons 25 Years
And Older
P570003 Y N Num 9 High School Graduated Persons 25 Years And Older
BGDZOO2 Y N Num 9 Some College, No Degree Or Associate Degree
Persons 25 Years And Older
BGD20 03 V N Nuin 9 Bachelor’s Degree Or Graduate Or Professional Degree
Persons 25 Years And Older
P8OAOOI Y N Num 9 Median Household Income In 1989
BGD2 004 V N Num 9 Total Number 01 Households With income Less Than 515k
BGD2 0 05 V N Num 9 Total Number Of Households With Income Greater
Than 815k And Less Than 825k
BGD2006 V N Num 9 Total Number Of Households With income Greater
Than 825k And Less Than 850k
BGD20 07 V N Num 9 Total Number Of Households With Income Greater
Than 850k And Less Than 875k
BGD2 00S V N Num 9 Total Number Of Households With Income Greater
Than 850k And Less Than 575k
BGD2 009 V N Num 9 Total Number OF Non White Households With income
Less Than 815k
BGD2OIO V N Num 9 Total Number Of Non White Households With Income
Less Than 25k And Greater Than 15k
BGDZOI I V N Num 9 Total Number Of Non White Households With Income
Less Than 50k And Greater Than 25k
BGD2012 Y N Num 9 Total Number Of Non White Households With income
Less Than 75k And Greater Than 50k
BGD2O I3 V N Num 9 Total Number Of Non White Households With Income
Greater Than 75k
13G02014 V N Num 9 Total Number Of White Households With Income
Less Than 815k
BGD2OI5 V N Num 9 Total Number Of White Households With Income
Less Than 25k And Greater Than 15k
BGDZO I6 V N Num 9 Total Number OF White Households With Income
Less Than 50k And Greater Than 25k
BGD2OI7 V N Num 9 Total Number 01 White Households With income
Less Than 75k And Greater Than 50k
BGDZ O IS V N Nuni 9 Total Number 01 White Households With income
Greater Than 75k
BGD2OI9 V N Num 9 Total Number OF Black Households With income
Less Than 815k
BGDZOZ O Y N Num 9 Total Number OF Black Households With income
Less Than 25k And Greater Than 15k
BGD2 O2 I V N Num 9 Total Ninnber 01 Black Households With income
Less Than 50k And Greater Than 25k
BGDZO22 V N Num 9 Total Number Of Black Households With Income
Less Than 75k And Greater Than 50k
BGDZ OZ3 V N Num 9 Total Number Of Black Households With Income
Greater Than 75k
BGDZO24 V N Num 9 Total Number Of American indian, Eskimo, Or Aleut
Households With income Less Than 515k
P820022 Y N Num 9 Total Number Of American Indian, Eskimo, Or AJeut
Households With Income Less Than 25k And Greater
Than 15k
BGD2O2S V N Num 9 Total Number Of Ainencan indian, Eskimo, Or Aleut
Households With income Less Than 50k And Greater
Than 25k
P820025 Y N Num 9 Total Number Of American Indian, Eskimo, Or Aleut
Households With Income Less Than 75k And Greater
Than 50k
BG02026 V N Num 9 Total Number Of Black American indian, Eskimo, Or Meat
Households With Income Greater Than 75k
BGDZO27 V N Num 9 Total Number Of Asian Or Pacific Ocean
Households With Income Not Less Than 515k
P820031 Y N Num 9 Total Number Of Asian Or Pacific Ocean Households
AppendIx C Data Elements in IDEA Shadow Files C-5
-------
Group Repeat EJement Name Index? Enforc Data Length Description
Record? (V/N) Sens? Type
(V/S/N)
With Income Less Than $25k And Greater Than 515k
BGD2OZ8 V N Num 9 Total Number Of Asian Or Pacific Ocean Households
With income Less Than S50k And Greater Than S25k
P820034 Y N Num 9 Total Number Of Asian Or Pacific Ocean Households
With income Less Than 575k And Greater Than 550k
BGD2OZ9 V N Nuni 9 Total Number Of Asian Or Pacific Ocean Households
- With Income Greater Than S75k
BGD2O3O V N Nuni 9 Total Number Of Other Race Households With income
Not Less Than S15k
P820040 Y N Num 9 Total Number Of Other Race Households With
Income Less Than 525k And Greater Than 515k
BG02031 V N Num 9 Total Number Of Other Race Households With Income
Less Than S50k And Greater Than 525k
P820043 Y N Num 9 Total Number Of Other Race Households With Income
Less Than 575k And Greater Than 550k
BGD2032 V N Num 9 Total Number Of Other Race Households With income
Greater Than 575k
BGDZO33 V N Nina 9 Total Number OF Households With Householder Of
Hjspamc Origin With income Not Less Than 515k
P830004 Y N Num 9 Total Number Of Households With Householder Of 1-lispanic
Origin With Income Less Than 525k And Greater Than $ 15k
BGDZO34 V N Nuni 9 Total Number Of Households With Householder 01 Hispanic
Origin With Income Less Than 550k And Greater Than 525k
P830007 Y N Num 9 Total Number Of Households With Householder Of Hispanic
Origin With Income Less Than 575k And Greater Than 550k
BGD2035 V N Nina 9 Total Number 01 Households With Householder Of Hispanic
Origin With income Greater Than 575k
PERSONS(A) N P950001 Y N Num 9 Households With Public Assistance Income
P950002 Y N Num 9 Households With No Public Assistance Income
P1 14A01 Y N Num 9 Per Capita income In 1989, Persons
P1 15A01 Y N Num 9 Per Capita income in 1989, White Persons
P115A02 V N Num 9 Per Capita Income In 1989, Black Persons
P115A03 Y N Num 9 Per Capita Income in 1989, American Indian, Eskimo
Or Aleut, Persons
P115A04 Y N Num 9 Per Capita Income In 1989, Asian Or Pacific Ocean, Persons
P1 15A05 Y N Num 9 Per Capita Income In 1989, Other Race, Persons
P1 16A01 Y N Num 9 Per Capita income in 1989, Persons Of Hispanic Origin
15 Years And Older
BGD300 I V N Nina 9 Persons In 1989 Below Poverty Level
BGD3002 V N Num 9 Persons With income In 1989 Below Poverty Level
5 Years Old And Under
BGD3003 V N Nina 9 Persons With Income In 1989 Below Poverty Level
17 Years Old And Under
BGD3004 V N Nina 9 Persons With Income In 1989 Below Poverty Level
18 Years Old And Older
BGD300 S V N Nina 9 Persons With Income In 1989 Below Poverty Level
65 Years Old And Older
BG03006 V N Nuni 9 Persons With income In 1989 Above Poverty Level
BGD3007 V N Nina 9 Persons With Income In 1989 Above Poverty Level
5 Years And Under
BG03008 V N Num 9 Persons With income in 1989 Above Poverty Level
17 Years Old And Under
BG03009 V N Nina 9 Persons With income in 1989 Above Poverty Level
18 Years Old And Older
BGD3OIO V N Nuni 9 Persons With income In 1989 Above Poverty Level
65 Years And Older
BGD3OI I V N Nina 9 White Persons With Income In 1989 Below Poverty Level
BGD3O IZ V N Nina 9 White Persons With Income In 1989 Below Poverty
Level 5 Years And Under
8GD3013 V N Nina 9 White Persons With Income in 1989 Below Poverty
Level 17 Years And Under
BGD3O I4 V N Nuni 9 White Persons With Income In 1989 Below Poverty
Level 18 Years And Older
BGD3O I5 V N Nina 9 White Persons With Income in 1989 Below Poverty
Level 65 Years And Older
BGD3016 Y N Nuni 9 White Persons With Income in 1989 Above Poverty Level
C-6 IDEA User’s GuIde October 22, 1996
-------
Group Repeat Element Name Index? Enforc Data Length Descnption
Record? (V/N) Sens? Type
(YIS/N)
BGD3OI7 Y N Nina 9 White Persons With Income In 1989 Above Poverty
Level 5 Years And Under
BGD3O IS V N Num 9 White Persons With income In 1989 Above Poverty
Level 17 Years And Under
BGD3OI9 V N Num 9 White Persons With Income In 1989 Above Poverty
Level 18 Years And Older
BGD3O2O V N Num 9 White Persons With income In 1989 Above Poverty
Level 65 Years And Older
BGD3OZ I V N Num 9 Black Persons With Income In 1989 Below Poverty Level
BGE)3022 V N Num 9 Black Persons With Income In 1989 Below Poverty Level
5 Years And Under
BGD3023 V N Num 9 Black Persons With Income In 1989 Below Poverty Level
17 Years And Under
BG93024 V N Num 9 Black Persons With Income In 1989 Below Poverty Level
18 Years And Older
BGD3O2S Y N Num 9 Black Persons With Income In 1989 Below Poverty Level
65 Years And Older
BGD3026 V N Num 9 Black Persons With Income In 1989 Above Poverty Level
BGD3027 Y N Num 9 Black Persons With Income In 1989 Above Poverty Level
Under 6 Years Of Age
BGD3O2S V N Num 9 Black Persons With Income In 1989 Above Poverty Level
Under 18 Years Of Age
BGD3029 Y N Nuni 9 Black Persons With Income In 1989 Above Poverty Level
Over 17 Years Of Age
RGD3O3O V N Num 9 Black Persons With Income In 1989 Above Poverty Level
Over 64 Years Of Age
BG03031 Y N Num 9 American indian, Eskimo Or Aleut Persons With income
In 1989 Below Poverty Level
BGD3032 Y N Num 9 American indian, Eskimo Or Aleut Persons With Income
In 1989 Below Poverty Level 5 Years And Under
BGD3033 Y N Num 9 Amencan Indian, Eskimo Or Aleut Persons With income
In 1989 Below Poverty Level 17 Years And Under
BGD3034 V N Num 9 Amencan indian, Eskimo Or Aleut Persons With income
In 1989 Below Poverty Level 18 Years And Older
BG93035 Y N Nuin 9 American Indian, Eskimo Or Aleut Persons With Income
In 1989 Below Poverty Level 65 Years And Older
BGD3036 Y N Num 9 American Indian, Eskimo Or Meat Persons With Income
In 1989 Above Poverty Level
BGD3037 Y N Num 9 American indian, Eskimo Or Aleut Persons With income
in 1989 Above Poverty Level Under 6 Years OF Age
BGD3O3S V N Num 9 American Indian, Eskimo Or Meat Persons With income
In 1989 Above Poverty Level Under 18 Years OF Age
BG93039 V N Num 9 American Indian, Eskimo Or Meat Persons With income
In 1989 Above Poverty Level Over 17 Years Of Age
BGD3O4O V N Nina 9 American Indian, Eskimo Or Meat Persons With Income
In 1989 Above Poverty Level Over 64 Years Of Age
BGD3O4 I Y N Num 9 Asian Or Pacific islander Persons With income in 1989
Below Poverty Level
BGD3O4Z V N Num 9 Asian Or Pacific islander Persons With Income in 1989
Below Poverty Level 5 Years And Under
BGD3043 V N Num 9 Asian Or Pacific islander Persons With Income In 1989
Below Poverty Level 17 Years And Under
BGD3044 Y N Num 9 Asian Or Pacific Islander Persons With Income In 1989
Below Poverty Level 18 Years And Older
BGD3045 Y N Nina 9 Asian Or Pacific Islander Persons With Income in 1989
Below Poverty Level 65 Years And Older
BGD3046 Y N Nina 9 Asian Or Pacific islander Persons With Income in 1989
Above Poverty Level
BGD3047 V N Num 9 Asian Or Pacific islander Persons With income in 1989
Above Poverty Level Under 6 Years OF Age
BGD3O4S V N Nina 9 Asian Or Pacific Islander Persons With income in 1989
Above Poverty Level Under 18 Years Of Age
BGD3049 Y N Num 9 Asian Or Pacific islander Persons With Income in 1989
Above Poverty Level Over 17 Years Of Age
BG03054) V N Num 9 Asian Or Pacific Islander Persons With Income In 1989
Above Poverty Level Over 64 Years Of Age
Appendix C Data Elements n IDEA Shadow Files C-7
-------
Group Repeat Element Name index? Enforc Data Length Descnption
Record? (YIN) Sens? Type
(Yf S/N)
BGD3O5 I Y N Num 9 Other Race Persons With Income In 1989 Below Poverty
Level
BGD3052 V N Num 9 Other Race Persons With income In 1989 Below Poverty
Level 5 Years And Under
BGD3053 V N Num 9 Other Race Persons With income In 1989 Below Poverty
Level 17 Years And Under
BGD3054 V N Num 9 Other Race Persons With income In 1989 Below Poverty
Level 18 Years And Older
BGD3055 V N Nwn 9 Other Race Persons With income In 1989 Below Poverty
Level 65 Years And Older
BGE)3056 V N Num 9 Other Race Persons With Income In 1989 Above Poverty
Level
BGD3057 V N Num 9 Other Race Persons With Income In 1989 Above Poverty
Level Under 6 Years 01 Age
BG03058 V N Num 9 Other Race Persons With Income In 1989 Above Poverty
Level Under 18 Years Of Age
BGD3OS9 V N Num 9 Other Race Persons With Income In 1989 Above Poverty
Level Over 17 Years 01 Age
BGD3O6O V N Num 9 Other Race Persons With Income In 1989 Above Poverty
Level Over 64 Years 01 Age
BGD3O6 I V N Num 9 Nonwhite Persons With Income In 1989 Below Poverty Level
BGD3062 V N Num 9 Nonwhite Persons With Income In 1989 Below Poverty
Level 5 Years And Under
BG03063 V N Num 9 Nonwhite Persons With Income In 1989 Below Poverty
Level 17 Years And Under
I3GD3064 V N Num 9 Nonwhite Persons With Income In 1989 Below Poverty
Level 18 Years And Older
BGD3O65 V N Num 9 Nonwhite Persons With Income In 1989 Below Poverty
Level 65 Years And Older
BGD3O66 V N Num 9 Nonwhite Persons With Income In 1989 Above Poverty
Level
BGD3067 V N Num 9 Nonwhite Persons With Income In 1989 Above Poverty
Level Under 6 Years Of Age
BG03068 V N Num 9 Nonwhite Persons With Income In 1989 Above Poverty
Level Under 18 Years 01 Age
BGD3069 V N Num 9 Nonwhite Persons With Income In 1989 Above Poverty
Level Over 17 Years Of Age
BGD3O7O V N Num 9 Nonwhite Persons With Income In 1989 Above Poverty
Level Over 64 Years Of Age
BGD3O7 I V N Num 9 Hispanic Ongin Persons With Income In 1989 Below
Poverty Level
BGD3072 V N Num 9 Hispanic Origin Persons With Income In 1989 Below
Poverty Level 5 Years And Under
BGD3073 Y N Num 9 Hispanic Origm Persons With Income In 1989 Below
Poverty Level 17 Years And Under
BGD3074 V N Num 9 Hispanic Origin Persons With Income in 1989 Below
Poverty Level 18 Years And Older
BGD3075 V N Num 9 Hispanic Origin Persons With Income In 1989 Below
Poverty Level 65 Years And Older
BGD3076 V N Num 9 Hispanic Origin Persons With Income In 1989 Above
Poverty Level
BGD3077 V N Nwn 9 Hispanic Origin Persons With Income In 1989 Above
Poverty Level Under 6 Years 01 Age
BGD3078 Y N Num 9 Hispanic Origin Persons With Income In 1989 Above
Poverty Level Under 18 Years 01 Age
BGD3079 V N Num 9 Hispanic Origin Persons With Income In 1989 Above
Poverty Level Over 17 Years Of Age
8GD3080 V N Num 9 Hispanic Origin Persons With Income In 1989 Above
Poverty Level Over 64 Years Of Age
P121001 V N Num 9 Ratio Of Income In 1989 To Poverty Level For
Persons For Whom Poverty Status Is Determined -
Under 0 50
P121002 Y N Num 9 Ratio Of Income In 1989 To Poverty Level For
Persons For Whom Poverty Status Is Determined -
0 50 To 0 74
P121003 Y N Num 9 RaUo Of Income In 1989 To Poverty Level For
C-B IDEA User’s Guide October 22, 1996
-------
Group Repeat Element Name Index’ Enlorc Data Length Description
Record? (V/N) Sens? Type
(Y/S/N)
Persons For Whom Poverty Status Is Determined -
075 To 099
P121004 Y N Num 9 Ratio Of Income In 1989 To Poverty Level For
Persons For Whom Poverty Status Is Determined -
1 00 To I 24
P121005 Y N Num 9 Ratio Of Income In 1989 To Poverty Level For
Persons For Whom Poverty Status Is Determined -
1 25 To 1 49
P121006 Y N Num 9 Ratio Of Income In 1989 To Poverty Level For
Persons For Whom Poverty Status Is Determined -
1 50 To 1 74
P121007 Y N Num 9 Ratio Of Income In 1989 To Poverty Level For
Persons For Whom Poverty Status Is Determined -
1 75 To I 84
P12 1008 Y N Num 9 Ratio Of Income In 1989 To Poverty Level For
Persons For Whom Poverty Status Is Determined -
1 85 To 1 99
P121009 Y N Num 9 Ratio Of Income In 1989 To Poverty Level For
Persons For Whom Poverty Status Is Determined -
2 00 And Over
H023001 Y N Num 9 Housing Units With Public System Or Private Company
Source Of Water
BGD3 O8I V N Num 9 Housing Units With Drilled Or Dug Well Water Source
H023004 V N Num 9 Housing Units With Some Other Water Source
BGD3082 V N Num 9 Housing Units Built In The Years 1980 To 90
H025004 Y N Num 9 Housing Units Built In The Years 1970 To 79
H025005 V N Num 9 Housing Units Built In The Years 1960 To 69
H025006 Y N Num 9 Housing Units Built In The Years 1950 To 59
H025007 Y N Num 9 Housing Units Built In The Years 1940 To 49
H025C 108 Y N Num 9 Housing Units Built In The Years 1939 Or Earlier
BGD3083 V N Num 4 Housing Density In Units Per Square Mile in The Years
1980 To 90
BGD3084 V N Num 4 Housing Density In Units Per Square Mile In The Years
1970 To 80
BGD3085 V N Num 4 Housing Density In Units Per Square Mile In The Years
1960 To 70
BG030 86 V N Num 4 Housing Density In Units Per Square Mile In The Years
1950 To 60
BG03087 V N Num 4 Housing Density In Units Per Square Mile In The Years
1940 To 50
BGD3088 V N Nuni 4 Housing Density In Units Per Square Mile Before 1940
H25A001 Y N Num 9 Median Year The Housing Unit Was Built
H43A OOI Y N Num 9 Median Gross Rent For The Renter Occupied Housing
Unit
H6IAO O I Y N Num 9 Median Value For The Owner Occupied Housing Unit
HOUSING(A) N H050001 Y N Num 9 For Renter Occupied Units Household Income In 1989
Under $10,000 And Gross Rent Less Than 20 Percent
H050002 Y N Num 9 For Renter Occupied Units Household Income In 1989
Under $10,000 And Gross Rent 20 To 24 Percent
H050003 Y N Num 9 For Renter Occupied Units Household Income In 1989
Under $10,000 And Gross Rent 25 To 29 Percent
H050004 Y N Num 9 For Renter Occupied Units Household Income In 1989
Under $10,000 And Gross Rent 30 To 34 Percent
H050005 Y N Num 9 For Renter Occupied Units Household Income In 1989
Under $10,000 And Gross Rent Ge 35 Percent
H050006 V N Num 9 For Renter Occupied Units Household Income In 1989
Under $10,000 And Gross Rent Percent Not Computed
H 050007 Y N Num 9 For Renter Occupied Units Household Income In 1989
Between $10,000 - $20,000 And Gross Rent Less
Than 20 Percent
H050008 Y N Num 9 For Renter Occupied Units Household Income In 1989
Between $10,000 - $20,000 And Gross Rent 20
To 24 Percent
H050009 Y N Num 9 For Renter Occupied Units Household Income In 1989
Between $10,000 - $20,000 And Gross Rent 25
To 29 Percent
Appendix C Data Elements ifl IDEA Shadow Files C-9
-------
Group Repeat Element Name index? Enforc Data Length Descnption
Record 9 (V/N) Sens? Type
(V/S/N)
H050010 Y N Num 9 For Renter Occupied Units Household Income In 1989
Between $10,000 - $20,000 And Gross Rent 30
To 34 Percent
HOSOOl I Y N Num 9 For Renter Occupied Units Household Income In 1989
Between $10,000 - $20,000 And Gross Rent Greater
Than 35 Percent
H050012 Y N Num 9 For Renter Occupied Units Household Income In 1989
Between $10,000 - $20,000 And Gross Rent Percent
Not Computed
H050013 Y N Num 9 For Renter Occupied Units Household Income in 1989
Between $20,000 - $35,000 And Gross Rent Less Than
20 Percent
H0500i4 V N Num 9 For Renter Occupied Units Household income In 1989
Between $20,000 - $35,000 And Gross Rent 20
To 24 Percent
H050015 V N Num 9 For Renter Occupied Units Household Income In 1989
Between $20,000 - $35,000 And Gross Rent 25
To 29 Percent
H050016 V N Num 9 For Renter Occupied Units Household income In 1989
Between $20,000 - $35,000 And Gross Rent 30
To 34 Percent
H050017 V N Num 9 For Renter Occupied Units Household Income In 1989
Between $20,000 - $35,000 And Gross Rent Greater
Than 35 Percent
H050018 V N Num 9 For Renter Occupied Units Household income In 1989
Between $20,000 - $35,000 And Gross Rent Percent
Not Computed
H050019 V N Nurn 9 For Renter Occupied Units Household income In 1989
Between $35,000 - $50,000 And Gross Rent
Less Than 20 Percent
H050020 Y N Num 9 For Renter Occupied Units Household Income In 1989
Between $35,000 - $50,000 And Gross Rent 20
To 24 Percent
H05002 1 V N Num 9 For Renter Occupied Units Household Income in 1989
Between $35,000 - $50,000 And Gross Rent 25
To 29 Percent
H050022 Y N Num 9 For Renter Occupied Units Household income In 1989
Between $35,000 - $50,000 And Gross Rent 30
To 34 Percent
H050023 V N Num 9 For Renter Occupied Units Household Income In 1989
Between $35,000 - $50,000 And Gross Rent
Greater Than 35 Percent
H050024 V N Num 9 For Renter Occupied Units Household Income In 1989
Between $35,000 - $50,000 And Gross Rent Percent
Not Computed
H050025 Y N Num 9 For Renter Occupied Units Household Income In 1989
Above $50,000 And Gross Rent Less Than 20 Percent
H050026 V N Num 9 For Renter Occupied Units Houtehold Income In 1989
Above $50,000 And Gross Rent 20 To 24 Percent
H050027 V N Num 9 For Renter Occupied Units Household Income In 1989
Above $50,000 And Gross Rent 25 To 29 Percent
H050028 V N Num 9 For Renter Occupied Units Household Income In 1989
Above $50,000 And Gross Rent 30 To 34 Percent
H050029 Y N Num 9 For Renter Occupied Units Household Income In 1989
Above $50,000 And Gross Rent Ge 35 Percent
H050030 Y N Num 9 For Renter Occupied Units Household income In 1989
Above $50,000 And Gross Rent Percent Not Computec
H059001 Y N Num 9 For Owner Occupied Units Household Income In 1989
Under $10,000 And Gross Rent Less Than 20 Percent
H059002 V N Num 9 For Owner Occupied Units Household Income In 1989
Under $10,000 And Owner Costs 20 To 24 Percent
H059003 V N Num 9 For Owner Occupied Units Household Income in 1989
Under $10,000 And Owner Costs 25 To 29 Percent
H059004 Y N Num 9 For Owner Occupied Units Household Income in i989
Under $10,000 And Owner Costs 30 To 34 Percent
H059005 Y N Num 9 For Owner Occupied Units Household Income in 1989
C-1O IDEA User’s Guide October 22, 1996
-------
Group Repeat Element Name Index 9 Enforc Data Length Descnpflon
Record? (V/N) Sees? Type
(V/S/N)
Under S 10,000 And Owner Costs Ge 35 Percent
H059006 V N Num 9 For Owner Occupied Units Household Income In 1989
Under $10,000 And Owner Costs Percent Not Computed
H059007 Y N Num 9 For Owner Occupied Units Household Income In 1989
Between $10,000 - $20,000 And Owner Costs Less Than
20 Percent
H059008 Y N Num 9 For Owner Occupied Units Household Income In 1989
Between $10,000 - $20,000 And Owner Costs 20 To
24 Percent
H059009 V N Num 9 For Owner Occupied Units Household Income In 1989
Between $10,000 - $20,000 And Owner Costs 25 To
29 Percent
H059010 Y N Num 9 For Owner Occupied Units Household Income In 1989
Between $10,000 - $20,000 And Owner Costs 30 To
34 Percent
H05901 I Y N Num 9 For Owner Occupied Units Household Income In 1989
Between $10,000 - $20,000 And Owner Costs Greater
Than 35 Percent
H059012 V N Num 9 For Owner Occupied Units Household Income In 1989
Between $10,000 - $20,000 And Owner Costs Percent
Not Computed
H0590 13 Y N Num 9 For Owner Occupied Units Household Income In 1989
Between $20,000 - $35,000 And Owner Costs Less Than
20 Percent
H0590l4 Y N Nurn 9 For Owner Occupied Units Household Income in 1989
Between $20,000 - $35,000 And Owner Costs 20 To
24 Percent
H059015 V N Nurn 9 For Owner Occupied Units Household Income In 1989
Between $20,000 - $35,000 And Owner Costs 25 To
29 Percent
H0590I6 V N Num 9 For Owner Occupied Units Household Income In 1989
Between $20,000 - $35,000 And Owner Costs 30 To
34 Percent
H059017 V N Num 9 For Owner Occupied Units Household Income In 1989
Between $20,000 - $35,000 And Owner Costs Greater Than
35 Percent
H059018 Y N Nuni 9 For Owner Occupied Units Household Income In 1989
Between $20,000 - $35,000 And Owner Costs Percent
Not Computed
H059019 V N Num 9 For Owner Occupied Units Household Income In 1989
Between $35,000 - $50,000 And Owner Costs Less Than
20 Percent
H059020 V N Num 9 For Owner Occupied Units Household Income In 1989
Between $35,000 - $50,000 And Owner Costs 20 To
24 Percent
H059021 V N Num 9 For Owner Occupied Units Household income In 1989
Between $35,000 - $50,000 And Owner Costs 25 To
29 Percent
H059022 V N Num 9 For Owner Occupied Units Household Income In 1989
Between $35,000 - $50,000 And Owner Costs 30 To
34 Percent
H059023 V N Num 9 For Owner Occupied Units Household Income In 1989
Between $35,000 - $50,000 And Owner Costs Greater Than
35 Percent
H059024 V N Num 9 For Owner Occupied Units Household Income in 1989
Between $35,000 - $50,000 And Owner Costs Percent
Not Computed
H059025 V N Num 9 For Owner Occupied Units Household Income In 1989
Above $50,000 And Owner Costs Less Than 20 Percent
H059026 V N Num 9 For Owner Occupied Units Household Income In 1989
Above $50,000 And Owner Costs 20 To 24 Perceni
H059027 V N Num 9 For Owner Occupied Units Household Income In 1989
Above $50,000 And Owner Costs 25 To 29 Percent
H059028 V N Num 9 For Owner Occupied Units Household Income In 1989
Above $50,000 And Owner Costs 30 To 34 Percent
H059029 V N Num 9 For Owner Occupied Units Household Income In 1989
Appendix C Data Elements in IDEA Shadow Files C-Il
-------
Group Repeat Element Name
Index? Enforc Data Length Description
Record?
(V/N) Sens? Type
(V/S/N)
Above $50,000 And Owner Costs Ge 35 Percent
For Owner Occupied Umts Household income In 1989
Above $50,000 And Owner Costs Percent Not Computed
Fraction 01 Linguistically Isolated Households
Fraction OF Linguistically Isolated English Speaking
Households
Fraction OF Linguistically isolated Spanish Speaking
Households
Fraction 01 Linguistically Not isolated Spanish Speaking
Households
Fraction Of Linguistically isolated A an Or Pacific Island
Language Speaking Households
Fraction OF Linguistically Not isolated A an Or Pacific
Island Language Speaking Households
Fraction OF Linguistically Isolated Other Language Speaking
Households
Fraction 01 LinguistIcally Not Isolated Other Language
Speaking Households
Fraction OF 25 Years Or Older Persons With Less Than
9th Grade Education
Fraction 0125 Years Or Older Persons With 9th To
12th Grade But With No Diploma Education
Fraction 0125 Years Or Older Persons With High School
Graduate Level Or Equivalent Education
Fraction 0125 Years Or Older Persons With CoUege Or
Associate Degree Level Education
Fraction 0125 Years Or Older Persons With Bachelor
Or Advanced Degree Level Education
Fraction Of Households With Less Than $15,000 income
Fraction Of Households With $15,000 To $25,000 Income
Fraction OF Households With $25,000 To $50,000 Incom 1
Fraction OF Households With $50,000 To $75,000 Incomi
Fraction OF Households With $50,000 To $75,000 Income
Fraction OF Non White Households With Less Than
$15,000 Income
Fraction OF Non White Households With Between $15,000
and $25,000 in Income
Fraction OF Non White Households With Between $25,000
And $50,000 in income
Fraction OF Non White Households With Between $50,000
And $75,000 in Income
Fraction OF Non White Households With $75,000 Or More
in income
Fraction OF White Households With Less Than $15,000
In Income
Fraction OF White Households With Between $15,000
And $25,000 in Income
Fraction 01 White Households With Between $25,000
And $50,000 In Income
Fraction Of White Households With Between $50,000
And $75,000 in income
Fraction Of White Households With More Than $75,000
In Income
Fraction Of Black Households With Less Than $15,000
In Income
Fraction OF Black Households With Between $15,000
And $25,000 In Income
Fraction Of Black Households With Between $25,000
And $50,000 in Income
Fraction Of Black Households With Between $50,000
And $75,000 in Income
Fraction Of Black Households With More Than $75,000
In income
Fraction Of American indian Households With Less Tha
$15,000 income
Fraction OF Amencan Indian Households With Between
HHFRAC(A)
H059030
Y
N
Num
9
N
BGF500I
BGF50 02
V
V
N
N
Num
Num
4
4
BGFS O O3
Y
N
Num
4
BGF50 04
V
N
Num4
BGF5 005
V
N
Num
4
BGF50 06
V
N
Num
4
BGF5 0 07
V
N
Num
4
BGF5 008
V
N
Num
4
BGF5 0 09
V
N
Num
4
BGF5OIO
Y
N
Num
4
BGF SO I1
V
N
Num
4
BGF S OI2
V
N
Nun
4
BGF5 OI3
V
N
Num
4
BGFS OI4
8GF5015
BGF S O I6
BGF5 O I7
BGF5 O I8
BGF5O I9
V
V
V
V
V
V
N
N
N
N
N
N
Num
Num
Num
Nuin
Num
Num
4
4
4
4
4
4
BGF SO2 O
V
N
Num
4
BGF5O2 I
V
N
Num
4
BGF S O22
V
N
Num
4
BGF5023
V
N
Num4
BGF5024
V
N
Nwn4
BGF SO25
V
N
Num
4
BGF5026
V
N
Nun
4
BGFS O27
V
N
Num
4
BGF5 OZ8
V
N
Num
4
BGF5029
V
N
Num
4
BGF SO3 O
V
N
Num
4
BGF5 O3I
V
N
Num
4
BGF5032
V
N
Num
4
BGF5033
Y
N
Num
4
BGF5034
V
N
Num
4
BGF5035
V
N
Num
4
C-12 IDEA User’s Guide
October 22, 1996
-------
Group Repeat Element Name index? Enforc Data Length Description
Record? (YIN) Sens? Type
(V/S/N)
$15,000 And $25,000 In income
BGF5036 V N Num 4 Fraction Of American Indian Households With Between
$25,000 And $50,000 in Income
BGF5037 V N Num 4 Fraction Of American indian Households With Between
$50,000 And $75,000 In income
BGFSO38 Y N Num 4 Fraction Of American indian, Eskimo, Or Aleut Households
With $75,000 Or More income In 1989
BGF5039 V N Num 4 Fraction Of Asian Or Pacific islander Households With
Less Than $15,000 in Income In 1989
BGF5O4O V N Num 4 Fraction Of Asian Or Pacific islander Households With
Between $15,000 And $25,000 In Income in 1989
BGF5 O41 V N Num 4 Fraction Of Asian Or Pacific islander Households With
Between $25,000 And $50,000 In Income in 1989
BGF5042 V N Num 4 Fraction Of Asian Or Pacific Islander Households With
Less Than $15,000 income in 1989
BGF5043 Y N Num 4 Fraction Of Asian Or Pacific islander Households With
More Than $75,000 income In 1989
BGF5044 V N Num 4 Fraction Of Other Race Households With Less Than
$15,000 income In 1989
BGF5045 V N Num 4 Fraction 01 Other Race Households With Between $15,000
And $25,000 In income in 1989
BGF5046 V N Num 4 Fraction OF Other Race Households With Between
$25,000 And $50,000 in Income in 1989
BGF5047 V N Num 4 Fraction OF Other Race Households With
Between $50,000 And $75,000 In income in 1989
BGF S O48 V N Num 4 Fraction OF Other Race Households With More Than
$75,000 in income in 1989
BGF S O49 V N Num 4 Fraction Of Hispame Origin Households With Less Than
$15,000 income in 1989
BGF5O5O V N Num 4 Fraction Of Hispanic Origin Households With Between
$15,000 And $25,000 In Income In 1989
BGF5 O5 I Y N Num 4 Fraction Of Hispamc Ongin Households With Between
$25,000 And $50,000 In income In 1989
BGF5052 V N Num 4 Fraction Of Hispanic Origin Households With Between
$50,000 And $75,000 In income in 1989
BGF5053 V N Num 4 Fraction Of Hispanic Origin Households With More Than
$75,000 Income in 1989
FRACPERS(A) N BGF600I V N Num 4 Fraction Of Households With Public Assistance income
BGF6002 V N Num 4 Fraction Of Households With No Public Assistance Income
BGF6 003 V N Num 4 Fraction Of Persons Below Poverty Level
BGF6004 V N Num 4 Fraction Of Persons 015 Years Or Under Below
Poverty Level
BGF60 05 V N Num 4 Fraction Of Persons 0117 Years Or Under Below
Poverty Level
BGF6 006 V N Num 4 Fraction Of Persons Of 18 Years Or More Below
Poverty Level
BGF6007 V N Num 4 Fraction Of Persons Of 65 Years Or More Below
Poverty Level
BGF6 0 08 Y N Num 4 Fraction 01 White Persons Below Poverty Level
BGF6009 V N Num 4 Fraction Of White Persons 5 Years Or Under
Below Poverty Level
BGF6O 1 O V N Num 4 Fraction Of White Persons Of 17 Years Or Under
Below Poverty Level
BGF6 O I I V N Num 4 Fraction Of White Persons Of 18 Years Or More
Below Poverty Level
BCF6O I2 V N Num 4 Fraction Of White Persons 0165 Years Or More
Below Poverty Level
BGF6 O I3 V N Num 4 Fraction Of Black Persons Below Poverty Level
BCF6 O I4 V N Num 4 Fraction Of Black Persons 5 Years Or Under
Below Poverty Level
BGF6O 15 V N Nwn 4 Fraction Of Black Persons 0117 Years Or Under
Below Poverty Level
BGF6O I6 V N Num 4 Fraction Of Black Persons 0118 Years Or More
Below Poverty Level
BGF6 O I7 V N Num 4 Fraction Of Black Persons 0165 Years Or More
Below Poverty Level
Appendix C Data Elements in IDEA Shadow Files C-13
-------
Group Repeat Element Name Index? Enforc Data Length Descnption
Record? (YIN) Sens? Type
(YIS/N)
BGF6OI8 Y N Num 4 Fraction Of Amencan Indian, Eskimo Or Aleut Persons
Below Poverty Level
BGF6O19 V N Num 4 Fraction Of Amencan Indian, Eskimo Or Aleut Persons
5 Years Or Under Below Poverty Level
BGF6O2O Y N Nwn 4 Fraction Of Amencan Indian, Eskimo Or Aleut Persons
Of 17 Years Or Under Below Poverty Level
BGF6O2 I V N Num 4 Fraction Of Amencan Indian, Eskimo Or Aleut Persons
0118 Years Or More Below Poverty Level
BGF6OZ2 Y N Num 4 Fraction Of Amencan Indian, Eskimo Or Aleut Persons
Of 65 Years Or More Below Poverty Level
BGF6023 V N Num 4 Fraction Of Asian Or Pacific Islander Persons Below
Poverty Level
BGF6024 Y N Num 4 Fraction Of Asian Or Pacific Islander Persons 5 Years
Or Under Below Poverty Level
BGF6OZ S Y N Nuin 4 Fraction Of Asian Or Pacific Islander Persons Of
17 Years Or Under Below Poverty Level
BGF6026 Y N Num 4 Fraction Of Asian Or Pacific Wander Persons Of 18
Years Or More Below Poverty Level
BGF6027 Y N Num 4 Fraction Of Asian Or Pacific Islander Persons 0165
Years Or More Below Poverty Level
BGF6OZS Y N Num 4 Fraction 01 Other Race Persons Below Poverty Level
BGF6029 Y N Num 4 Fraction Of Other Race Persons 5 Years Or Under
Below Poverty Level
BGF6O3O V N Num 4 Fraction Of Other Race Persons 0117 Years Or Under
Below Poverty Level
8GF6031 V N Num 4 Fraction Of Other Race Persons 0118 Years Or More
Below Poverty Level
BGF6032 Y N Num 4 Fraction Of Other Race Persons 0165 Years Or More
Below Poverty Level
BGF6033 V N Num 4 Fraction Of Non White Persons Below Poverty Level
BGF6034 V N Num 4 Fraction Of Non White Persons 5 Years Or Under
Below Poverty Level
BGF6035 V N Nuni 4 Fraction Of Non White Persons 0117 Years Or Under
Below Poverty Level
BGF6036 V N Num 4 Fraction Of Non White Persons 0118 Years Or More
Below Poverty Level
BGF6037 Y N Num 4 Fraction Of Non White Persons 0165 Years Or More
Below Poverty Level
8GF6038 Y N Num 4 Fraction Of Hispanic Ongin Persons Below Poverty Level
BGF6039 V N Num 4 Fraction Of Hispanic Ongm Persons 5 Years Or
Under Below Poverty Level
BGF6040 V N Num 4 Fraction Of Hispanic Ongm Persons 0117 Years Or
Under Below Poverty Level
BGF6041 Y N Num 4 Fraction Of Hispanic Origin Persons 0118 Years Or
More Below Poverty Level
BGF6042 V N Num 4 Fraction Of Hispanic Ongin Persons Of 65 Years Or
More Below Poverty Level
BGF6043 V N Num 4 Fraction Of Households With Pubhc System Water
Source
BGF6044 Y N Nuni 4 Fraction Of Households With Well Water Source
BGF6045 Y N Num 4 Fraction Of Households With Other Means Water
Source
BGF6046 V N Num 4 Fraction Of Households Built Between 1980-90
BGF6047 V N Num 4 Fraction Of Households Built Between 1970. 80
BGF6O4S Y N Num 4 Fraction Of Households Built Between 1960 - 70
BGF6049 V N Num 4 Fraction Of Households Built Between 1950-60
BGF6 O5 O Y N Num 4 Fraction Of Households Built Between 1940-50
BGF6O5 I Y N Num 4 Fraction Of Households Built Before 1940
C-14 IDEA User’s Guide October 22, 1996
-------
C.3 CER-CERCLA In formation System Data Elements (9/96 )
Level Repeat Element Name Index? Enforc Data Length Description
Record? (V/N) Sens? Type
(V/SIN)
0 N 0000 - - - Entry
0001 Y S Char 2 Entry-Region
0002 Y S Char 2 Entry-State
0101 Y S Char 12 Entry-EPA Id
0104 Y S Char 40 Entry-Name
0110 N S Char 40 Entry-Street
0111 Y S Char 25 Entry-City
0112 Y S Char 9 Entry-Zip Code
0120 Y S Char 25 Entry-County Name
0121 Y S Char 3 Entry-County Code
0130 Y S Char 2 Entry-Congressional District
0135 Y S Char I Entry-Federal Facility Flag
0136 Y S Char 2 Entry-Ownership Indicator
0137 Y S Char I Entry-Site Incident Category
0140 Y S Char 4 Entry-Standard Metropohtan Statistical Area
0201 N S Text 60 Entry-Description
0204 N S Char 20 Entry-RPM/OSC Name
0205 N S Char 10 Entry-RPM/OSC Phone
0206 N Y Char 20 Entry-Regional Contact Name
0207 N Y Char 10 Entry-Regional Contact Phone
0226 Y Y Char 2 Entry-Classification
0299 Y S Date 6 Entry-Original Load Date (MMDDYY)
0300 Y Y Date 6 Entry-Last Update (MMDDYY)
0301 N S Char I Entry-Name Source
0304 Y S Char I Entry-Federal Facilities Docket Flag
0305 Y S Char I Entry-National Priorities List (NPL) Status
0307 Y S Char I Entry-Incident Type
0308 Y S Char 2 Entry-Proposed NPL Update Number
0309 Y S Char 2 Entry-Final NPL Update Number
0310 N S lntg 2 Entry-Source Count NOTIS
0311 N S lntg 2 Entry-Source Count. STh
0312 N S lntg 2 Entry-Source Count HWDMS
0313 N S lntg 2 Entry-Source Count. Composite
0314 N S Intg 2 Entry-Source Count. Other
0315 Y S Char 4 Entry-IFMS Identification Number
0322 Y S Char 7 Entry-Latitude
0323 Y S Char 8 Entry-Longitude
0326 N S Char I Entry-Lat/Long Source
0327 N Y Char I Entry-Lat/Long Accuracy
0350 N S Char 4 Entry-S/I Dioxin Tier
0364 N S Char 8 Entry-USGS Hydro Unit
0399 Y S Char I Entry-RCRA Facility
0400 N Y Inig 5 Entry-Aggregate Case Budget Obligation
0491 N Y Char 6 Entry-Regional Field I
0492 N Y Char I Entry-Regional Field2
0493 N Y Char I Entry-Regional Field3
0494 N Y Char 2 Entry-Regional Field4
0495 N Y Char 3 Entry-Regional Field5
0496 N Y Char 4 Entry-Regional Field6
0497 N Y Char 5 Entry-Regional Field7
0498 N Y Char 10 Entry-Regional Field8
0500 Y S Char I Entry-Selection Criteria
0510 Y S Date 6 Entry-Date (MMDDYY)
0511 N S Char 6 Entry-Time
0512 Y S Char 3 Entry-User Id
0142 Y - Char I Entry-USACE Flag
0151 N S Char I Entry-Federal Agency PRP Flag
0152 N S Char I Entry-State PRP Flag
0153 N S Char I Entry-Municipal PRP Flag
0139 N - Char 2 Entry-Historical Indicator
Appendix C Data Elements in IDEA Shadow Files C-15
-------
Level Repeat Element Name Index? Enforc Data Length Descnption
Record? (V/N) Seris? Type
(V/S/N)
0141 N - Char 2 Entry-Top Chaui
0143 Y Y Char I Entry-Cost Recovery Indicator
0203 Y S Char 9 Entry-Section Code
0102 Y S Char 12 Entry-Finds Id
0144 N Y Char I Entry-Link Audit Flag
0103 N S Text 5 Entry-Site Ref Number
0145 N Y Char 3 Entry-NFRAP Indicator
0146 N Y Date 4 Entry-NFRAP Date
V 1100 - - — - Operable Units
1101 Y S Char 2 Operable Unit-Id
1102 N S Char 2 Operable Unit-Alias Link
1103 Y S Char 14 Operable Unit-Concatenation Key
1104 N S Char 30 Operable Unit-Name
1105 N S Text 60 Operable Urut-Descnpuon
1106 N Y Char 2 Operable Unit-Regional Fieldl
1107 N V Char 6 Operable Unit-Regional Field2
1108 N V Char 2 Operable Unit-Regional Field3
1109 V S Char 3 Operable Unit-User Id
1110 Y S Date 6 Operable Unit-Date (MMDDYY)
1111 N S Char 6 Operable Unit-Time
1112 Y S Char 4 Operable Unit-Enforcement Activity Type
1113 V S Char 16 Operable Unit-Enf Activity Concatenation Key
1114 V - Char 3 Operable Unit-Enf Remedy Activity
1115 V - Char 19 Operable Unit-Enf Remedy Concatenation Key
1142 V - Char I Operable Unit-USACE Flag
1139 N - Char 2 Operable Unit-Historical Indicator
Y 2100 - - — - Events
2101 V S Char 3 Event-Type
2102 Y S Char 17 Event-Concatenation Key
2103 Y S Char I Event-Qualifier
2104 N S Char 30 Event-Name
2105 N V Text 20 Event-SCAP Note
2106 N S Text 10 Event-Short Name
2107 Y S Char 8 Event-Activity Link
2108 V S Char 5 Event-Type Sort
2109 N S Char 2 Event-Removal Approval Authority
2110 Y S Char I Event-Planning Status
2111 Y S Char 2 Event-Generic Type Code
2113 N Y Char 3 Event-State Percentage Share Of Costs
2114 Y S Char 3 Event-Takeover Flag
2115 V Y Char I Event-First Start Indicator
2116 Y V Char I Event-First Complete Indicator
2117 Y S Char 2 Event-Event Lead
2118 Y S Char 2 Event-Event Category
2120 N V Date 6 Event-Original Planned Start Date (MMDDYV)
2121 N Y Date 6 Event-Orig Planned Complete Date (MMDDYY)
2122 N V Char 3 Event-Original Planned Start FY/Quarter
2123 N V Char 3 Event-Orig Planned Completion FY/Quarter
2130 Y S Date 6 Event-Current Planned Start Date (MMDDYV)
2131 Y S Date 6 Event-Cur Planned Complete Date (MMDDYV)
2132 Y S Char 3 Event-Current Planned Start FY/Quarter
2133 Y S Char 3 Event-Current Planned Completion FY/Quarter
2137 N S Char I Event-yAM Flag
2138 Y S Char 2 Event-Link Chain
2139 N - Char 2 Event-Historical Indicator
2140 Y S Date 6 Event-Actual Start Date (MMDDYY)
2141 Y S Date 6 Event-Actual Completion Date (MMDDYY)
2157 N S Char 20 Event-Regional Contact Name
2158 N S Char 10 Event-Regional Contact Phone
2159 N V Char 10 Event-Cooperative Agreement Number
2160 N Y Char 10 Event-Cooperative Amendment Number
2161 N Y Char 2 Event-Regional FieldI
2162 N Y Char 2 Event-Regional Field2
2163 N V Char 4 Event-Regional Field3
2164 N V Char 6 Event-Regional Field4
2165 N S Char 4 Event-Dummy 01 (Activity Type)
C-16 IDEA User’s Guide October 22, 1996
-------
Level Repeat Element Name index? Enforc Data Length Description
Record? (V/N) Sens? Type
(V/S/N)
2166 N S Char 16 Event-Dummy 02 (Concatenation)
2167 N S Char 3 Event-Dummy 03 (Remedy Activity)
2168 N S Char 19 Event-Dummy 04
2170 Y S Date 6 Event-Date (MMDDYY)
2171 N S Char 6 Event-Time
2172 Y S Char 3 Event-User Id
2145 N Y Char 4 Event-(IAG)lnteragency Agreement Number
2146 N S Char 11 Event-Dummy 05
2147 N Y Char 20 Event-Corps Contact Name
2148 N Y Char 10 Event-Corps Contact Phone
2149 N Y Char 20 Event-Contractor
2150 N S lntg 5 Event-Dwnmyoo
2151 N S lntg 5 Event-Dummy 07
2152 N S lntg 5 Event-Dummy 02
2153 N S lntg 5 Event-Dummy 09
2154 N Y Char 3 Event-Corps District Code
2155 N Y Char 20 Event-Corps District Name
2156 N S Char 4 Event-Dummy 10
2124 N - Char 2 Event-Original Planned Start FY
2125 N - Char 2 Event-Original Planned Completion FY
2134 Y - Char 2 Event-Current Planned Start FY
2135 Y - Char 2 Event-Current Planned Completion FY
2142 Y - Char I Event-USACE Lead QuahfierjAsgn-To
2143 N - Date 6 Event-USACE Lead Qualifier/Asgn-Date (MMDDYY)
2144 N S Char 4 Event-USACE lAG Amendment Number
1901 N Y Char 17 Event-USACE Project Key
1902 Y Y Char I Event-USACE Project Type
1911 N Y Date 6 Event-USACE Line Item Review (MMDDYY)
1912 N Y lntg 5 Event-lAG Funding Level
1913 N Y lntg 5 Event-lAG In-House Expended-Past Month
1914 N Y lntg 5 Event-lAG In-House Expended-Total
1915 N Y lntg 5 Event-lAG In-House Obligated Aniount
1916 N Y lntg 5 Event-lAG Contract Expended-Past Month
1917 N V Inig S Event-lAG Contract Expended-Total
1918 N Y lntg 5 Event-lAG Contract Obligated Amount
1919 N Y lntg 5 Event-USACE Estimated RA Cost
1920 N Y Char 20 Event-USACE 0 & M Contractor Name
1921 N Y Char 2 Event-USACE Performed By
1922 N V Char 20 Event-USACE Contractor Contact Name
1923 N V Char 10 Event-USACE Contractor Contact Phone
1924 N Y Char 20 Event-USACEOnsite Engineer
1925 N Y Char 10 Event-USACEOnsite Engineer Phone
1927 N V Char 25 Event-USACE Contractor City
1928 N V Char 2 Event-USACE Contractor State
1931 N V Intg 2 Event-Construction Percent-To-Date Actual
1932 N Y lntg 2 Event-Construction Percent-To-Date Scheduled
1933 N Y lntg 2 Event-Constr Percent-To-Date Last Month
1934 N Y lntg 2 Event-Constr Percent-To-Date Last FY
1935 N V lntg 3 Event-Consir Calendar Days Actual
1936 N V lntg 3 Event-Constr Calendar Days Current
1937 N V lntg 3 Event-Constr Calendar Days Pending
1938 N V lntg 3 Event-Constr Calendar Days Original
1940 N V Date 6 Event-USACE Date (MMDDYY)
1941 N V Char 6 Event-USACE Time
1942 V - Char I Event-USACE Flag
2173 V - Char I Event-EPA Priority
2174 N - Char 2 Event-Action Type
2175 N - Char 3 Event-Action Sequence
3100 - - - Subevents
3101 V Y Char 3 Subevent-ld
3102 V Y Char 20 Subevent-Concatenation Key
3104 N V Char 30 Subevent-Name
3105 N V Text 20 Subevent-SCAP Note
3108 N Y Text 10 Subevent-Short Name
3109 V Y Char 8 Subevent-Activity Link
3110 Y Y Char 5 Subevent-Id Sort
Appendix C Data Elements in IDEA Shadow Files C-17
-------
Level Repeat Element Name Index? Enforc Data Length Description
Record? (V/N) Sens? Type
(Y/S/N)
3111 Y Y Char 2 Subevent-Generic Type
3120 N Y Date 6 Subevent-Original Start Date (MMDDYY)
3121 N Y Date 6 Subevent-Original Completion Date (MMDDYY)
3122 N Y Date 6 Subevent-Current Start Date (MMDDYY)
3123 N Y Date 6 Subevent-Current Completion Date (MMDDYY)
3124 N V Date 6 Subevent-Actual Start Date (MMDDYY)
3125 N V Date 6 Subevent-Actual Completion Date (MMDDYY)
3126 N Y Char 3 Subevent-Original Start FYfQuarter
3127 N Y Char 3 Subevent-Original Completion FYlQuarter
3128 N Y Char 3 Subevent-Current Start FY/Quarter
3129 N V Char 3 Subevent-Current Completion Date FY/Quarter
3131 N V Char 2 Subevent-Regional Fieldl
3132 N - Char 2 Subevent-Regional Field2
3133 N Y Char 4 Subevent-Regional FieId3
3134 N - Char 6 Subevent-Regional Field4
3135 Y - Char 4 Subevent-Enforc2ment Activity Type
3136 V V Char 16 Subevent-Enf Activity Concatenation Key
3137 Y - Char 3 Subevent-Enf Remedy Activity
3138 Y - Char 19 Subevent-Enf Remedy Concatenation Key
3140 Y V Date 6 Subevent-Date (MMDDYY)
3141 N V Char 6 Subevent-Time
3142 N Y Char 3 Subevent-User Id
3143 N - Char 2 Subevent-Original Start FY
3144 N - Char 2 Subevent-Origmal Completion F)’
3145 N - Char 2 Subevent-Current Start FY
3146 N - Char 2 Subevent-Current Completion FY
3147 N V Char 3 Subevent-Owner
3148 V - Char I Subevent-USACE Flag
3139 N - Char 2 Subevent-l-Iistorical Inthcator
4 Y 3500 - - * - Subevent Comments
3501 N Y Char 3 Subevent Comment-Id
3502 V Y Char 23 Subevent Comment-Concatenation Key
3503 N Y Date 6 Subevent Comment-Date (MMDD’YY)
3504 N Y Char 6 Subevent Comment-Time
3505 V Y Char 2 Subevent Comment-Type Code
3506 N Y Char 3 Subevent Comment-User Id
5 V 3510 - - — - Subevent Comment Line
3511 N V Char 2 Subevent Comment Line-Number
3512 Y Y Char 25 Subevent Comment Line-Concatenation
3513 N Y Char 60 Subevent Comment Line-Text
3514 N Y Date 6 Subevent Comment Line-Date (MMDDYY)
3515 N Y Char 6 Subevent Comment Line-Time
3516 N V Char 3 Subevent Comment Line-User Id
3 Y 2190 - - — - Event Valid Financial
2191 Y Y Char 33 Event Valid Fm-Acct/Doc Control Number
2192 Y Y Char 6 Event Valid Fin-Document Control Number
2193 V V Char 10 Event Valid Fm-Account Number
2194 N Y Date 6 Event Valid Fin-Date (MMDDYY)
2195 N V Char 6 Event Valid Fin-Time
2196 N Y Char 3 Event Valid Fin-User Id
2197 Y Y Char 16 Event Valid Fin-AcnfDcn Concatenation
3 V 3200 - - — - Financial
3201 Y S Char 3 Financial-Id
3202 Y S Char I Financial-Type
3203 Y Y Char 6 Financial-Document Control Number
3204 Y V Char 10 Financial-Account Number
3205 V S Char 20 Financial-Concatenation Key
3206 V V Char I Financial-I FMS Flag
3207 Y Y Char 10 Financial-Obligating Document Number
3208 V V Char 4 Fmancial-Subobject Class
3218 N Y Char 3 Financial-Planned Obligation FY/Quarter
3220 V S Date 6 Financial-Date (MMDDYY)
3225 Y Y Char 3 Financial-Fund Priority Status
3228 Y V Char 6 Financial-Work Assignment/lAG Number
3229 Y V Char I Financial-Event Budget Source
3230 N S lntg 5 Financial-Amount
C-18 IDEA User’s Guide October 22, 1996
-------
Repeat Element Name
Record?
Level
Index? Enforc Data Length Description
(V/N) Sens? Type
(V/S/N)
3238
V
Y
Text
8
Financial-Vehicle Abbreviation
3239
V
Y
Char
5
Financial-Vehicle
3240
V
Y
Char
2
Financial-FY
3241
N
Y
Char
20
Financial-Cont.ractor Name
3242
N
Y
Char
30
Financial-Note
3244
N
V
Char
6
Financial-Regional Fieldi
3245
N
Y
Char
6
Financial-Regional Field2
3246
N
V
Char
6
Financial-Regional Field3
3247
N
-
Char
6
Financial-Regional Field4
3248
V
S
Date
6
Financial-Update Date (MMDDYY)
3249
N
S
Char
6
Financial-Update Time
3250
V
S
Char
3
Financial-User Id
3231
N
S
lntg
5
Financial-IFMS Open Commitment
3232
N
S
lntg
5
Financial-Total Open Commitment
3233
V
S
Char
I
Financial-IFMS Final Obligation
3209
V
Y
Char
16
Financial-Acn/Dcn Concatenation Key
3234
N
Y
Char
2
Financial-Work Assignment Amendment Number
3219
N
S
Char
2
Financial-Historical indicator
3251
N
-
Char
4
Financial-Budget FY
3252
N
-
Char
6
Financial-Fund
3253
N
-
Char
7
Financial-Organization
3254
N
-
Char
9
Financial-Pgm Element
3255
N
-
Char
8
Financial-Site Project
3256
N
-
Char
8
Financial-Cost Organization
4
V
3600
3601
3602
3603
3604
3605
3606
-
N
V
N
N
V
N
-
Y
V
Y
Y
Y
Y
—
Char
Char
Date
Char
Char
Char
-
3
23
6
6
2
3
Financial Comments
Financial Comment-Id
Financial Comment-Concatenation Key
Financial Comment-Date (MMDDYY)
Financial Comment-Time
Financial Comment-Type Code
Financial Comment-User Id
5
V
3610
3611
3612
3613
3614
3615
3616
-
N
Y
N
N
N
N
-
Y
Y
Y
Y
V
V
—
Char
Char
Char
Date
Char
Char
-
2
25
60
6
6
3
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
3
Y
2420
2421
2422
2423
2424
2425
2430
2431
2432
2433
2434
2435
2436
-
Y
V
Y
N
V
N
N
N
N
N
N
N
-
S
S
S
S
S
S
S
S
S
S
S
S
—
Text
Text
Char
Char
Text
Char
Char
Char
Char
Char
Date
Char
-
6
23
2
3
17
12
2
3
4
6
6
3
Event Link Record
Event Link Record-Identifier
Event Link Record-Concatenation Key
Event Link-Cham
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
3
V
3300
3301
3302
3303
3304
3305
3306
-
N
V
N
N
Y
N
-
V
V
V
V
Y
V
—
Char
Char
Date
Char
Char
Char
-
3
20
6
6
2
3
Event Comments
Event Comment-id
Event Comment-Concatenation Key
Event Comment-date (MMDDVY)
Event Comment-Time
Event Comment-Type Code
Event Comment-User Id
4
V
3310
3311
3312
3313
3314
3315
3316
-
N
Y
N
N
N
N
-
Y
V
V
Y
Y
V
—
Char
Char
Char
Date
Char
Char
-
2
22
60
6
6
3
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
3
V
3400
-
-
—-
-
Technical Information
Appendix C Data Elements in IDEA Shadow Files
C-19
-------
Level Repeat Element Name Index? Enforc Data Length Descnption
Record? (V/N) Sens? Type
(V/S/N)
3401 V V Char 2 Tech information-Type
3402 N Y Char 2 Tech information-Qualifier I
3403 N V Char 2 Tech information-Qualifier 2
3404 N V Char 2 Tech information-Qualifier 3
3405 N Y Char 2 Tech information-Qualifier 4
3406 N V Char 2 Tech Information-Qualifier 5
3407 N V Char 2 Tech Information-Qualifier 6
3408 N V Char 2 Tech Information-Qualifier 7
3409 N V Char 2 Tech Information-Qualifier 8
3410 N Y Char 2 Tech Information-Qualifier 9
3411 N V Char 2 Tech information-Qualifier 10
3415 N Y Char I Tech information-Type Suffix
3418 Y Y Char 23 Tech Information-Locate Key
3419 V V Char 24 Tech information-Concatenation Key
3420 Y Y Date 6 Tech Information-Date (MMDDYY)
3421 N V Char 6 Tech information-Time
3422 N V Char 3 Tech Information-User Id
3439 N - Char 2 Tech Information-Historical Indicator
3424 N V Char 2 Tech Information-Contaminated Medium Code
3425 N V Char 1 Tech Information-Capping Only
3426 N V Date 6 Tech Information-Service Date (MMDDYY)
3427 N V Char 4 Tech Information-Contaminating Material
3428 N Y intg 6 Tech Information-Technology Volume
3429 N Y Char S Tech information-Volume Unit Of Measure
3431 Y V Char 21 Tech info-Material Concatenation Key
4 Y 3440 - - — - Receptors
344i V V Char 3 Receptors-Type Of Affected Population
3442 N V lntg 4 Receptors-Affected Population
3444 Y Y Text 27 Receptors-Concatenation Key
3445 N Y Char 6 Receptors-Record Time
3446 N V Date 6 Receptors-Record Date (MMDDYY)
3447 N V Char 3 Receptors-Record User
3448 N - Char 2 Receptors-Historical indicator
3 Y 3700 - - — - Event Chemicais
3701 V Y Char 10 Event Chemical-CAS Number
3702 N Y Char 40 Event Chemical-Name
3703 N Y Char 40 Event Chemical-Common Name
3704 N S Date 6 Event Chemical-Date (MMDDYY)
3705 N S Char 6 Event Chemical-Time
3706 Y S Text 31 Event Chemical-Concatenation Key
3707 N S Char 3 Event Chemicai-User Id
3709 N - Char 2 Event Chemical-Historical indicator
3710 N Y Char 4 Event Chemicai-Contamuiating Material Id
3711 Y Y Char I Event Chemicai-Category
3712 N Y Char 2 Event Chemical-Contaminated Medium Code
3713 Y Y Char 21 Event Chemical-Material Concatenation Key
3 Y 2180 - - — - RCRA
2181 V Y Char 12 RCRA-Offsite Id
2182 Y Y Char 29 RCRA-Concatenation Key
2187 N Y Date 6 RCRA-Date(MMDDYY)
2188 N V Char 6 RCRA-Time
2189 N Y Char 3 RCRA-User Id
3 Y 2500 - - — - Materiais
2501 V Y Char 4 Materials-id
2503 N Y Date 6 Materials-initial Technology Date (MMDDYY)
2504 N Y lntg 6 Materials-Volume
2505 N Y Char S Materials-Unit Of Measure
2506 N Y Char I Materials-Needs Future Handling
2507 N V Char 2 Materiais-Contaminated Medium Code
2511 Y Y Char 21 Materials-Concatenation Key
25i2 Y Y Char 14 Materials-Medium Concatenation Key
2513 N Y Char 6 Materials-Record Time
2514 N Y Date 6 Materials-Record Date (MMDDYY)
2515 N Y Char 3 Materials-Record User
2516 N - Char 2 Materials-Historical Indicator
3 Y i980 - - —- - Event Narrative
C-20 IDEA User’s Guide October 22, 1996
-------
Level Repeat Element Name index? Enlorc Data Length Description
Record? (V/N) Sens? Type
(V/S/N)
1981 N V Char 4 Event Narrative-Line Number
1982 V Y Char 21 Event Narrative-Concatenation Key
1983 N V Text 74 Event Narrative-Text
1984 N Y Date 6 Event Narrative-Date (MMDDYY)
1985 N V Char 6 Event Narrative-Time
1986 N Y Char 3 Event Narrative-User Id
2 Y 2300 - - — - Operable Unit Comments
2301 N Y Char 3 Op Unit Comment-Id
2302 V Y Char 17 Op Unit Comment-Concatenation Key
2303 N V Date 6 Op Unit Comment-Date (MMDDYY)
2304 N Y Char 6 Op Unit Comment-Time
2305 V - Char 2 Op Unit Comment-Type Code
2306 N V Char 3 Op Unit Comment-User Id
3 Y 2310 - - — - Operable Unit Comment Lme
2311 N V Char 2 Op Unit Comment Line-Number
2312 V Y Char 19 Op Unit Comment Line-Concatenation
2313 N Y Char 60 Op Unit Comment Line-Text
2314 N Y Date 6 Op Unit Comment Line-Date (MMDDYY)
2315 N V Char 6 Op Unit Comment Line-Time
2316 N Y Char 3 Op Unit Comment Line-User Id
Y 1200 - - — - Aliases
1201 V S Char 2 Alias-Id
1202 V S Char 14 Alias-Concatenation Key
1204 V S Char 40 Alias-Name
1212 V S Date 6 Alias-Date (MMDDYY)
1213 N S Char 6 Alias-Time
1214 N S Char 3 Alias-User Id
1205 N - Char I Alias-USACE Flag
1219 N - Char 2 Alias-Historical indicator
2 V 2200 - - — - Ahas Location
2201 V S Char 2 Alias Location-Sequence Number
2202 V S Char 16 Alias Location-Concatenation Key
2210 N S Char 40 Alias-Street
2211 V S Char 25 Alias-City
2212 Y S Char 9 Alias-Zip
2213 N S Char 2 Alias-State
2222 V S Char 7 Alias-Latitude
2223 V S Char 8 Alias-Longitude
2270 N S Text 60 Alias-Description
2272 N S Date 6 Alias Location-Date (MMDDYY)
2273 N S Char 6 Alias Location-Time
2274 N S Char 3 Alias Location-User Id
Y 1300 - - — - Entry Comments
1301 N Y Char 3 Entry Comment-id
1302 Y Y Char 15 Entry Comment-Concat Key
1303 N Y Date 6 Entry Comment-Date (MMDDYY)
1304 N V Char 6 Entry Comment-Time
1305 V Y Char 2 Entry Comment-Type Code
1306 N Y Char 3 Entry Comment-User Id
2 Y 1310 - - — - Entry-comment Line
1311 N V Char 2 Entry Comment Line-id
1312 V V Char 17 Entry Comment Lme-Concat Key
1313 N Y Char 60 Entry Comment Line-Text
1314 N V Date 6 Entry Comment Line-Date (MMDDYY)
1315 N Y Char 6 Entry Comment Line-Time
1316 N V Char 3 Entry Comment Line-User Id
V 1400 - - - Regional-Utility
1401 V V Char 6 Regional Utility-Code
1402 N S Text 60 Regional Utility-Description
1403 N S Date 6 Regional Utihty-Datei (MMDDYY)
1404 N Y Date 6 Regional Utihty-Date2 (MMDDYY)
1405 N Y Date 6 Regional Utility-Date3 (MMDDYY)
1406 N S Char 10 Regional Utility-Free Field
1407 Y S Char 18 Regional Utihty-Concat Key
1408 Y S Char 16 Regional Utility-Locate Key
1410 Y S Date 6 Regional Utility-Date (MMDDYV)
Appendix C Data Elements in IDEA Shadow Files C-21
-------
Level Repeat Element Name Index? Enforc Data Length Description
Record? (YIN) Sens? Type
(V/S/N)
1411 N S Char 6 Regional Utility-Time
1412 N S Char 3 Regional Utility-User Id
1419 N - Char 2 Regional Utility-Historical In
Y 1700 - - - Enforcement Activities
1701 Y S Char 4 Enf Act-Type
1702 Y S Char 16 Enf Act-Concatenation Key
1703 Y S Char 6 Enf Act-Sort
1704 Y S Text 10 Enf Act-Abbreviation
1705 Y S Char 8 Enf Act-Activity Link
1706 N S Char 30 Enf Act-Name
1707 Y S Char 2 Enf Act-Lead
1708 N Y Date 6 Enf Act-Original Planned Start Date (MMDDYY)
1709 N Y Char 3 Enf Act-Original Planned Start FY/Quarter
1710 N Y Date 6 EnfAct-Orig Planned Complete Date (MMDDYY)
1711 N Y Char 3 Enf Act-Original Planned Complete FY/Quarter
1712 N Y Date 6 Enf Act-Current Planned Start Date (MMDD’YY)
1713 N Y Char 3 Enf Act-Current Planned Start FY/Quarter
1714 N Y Date 6 Enf Act-Cur Planned Complete Date (MMDDYY)
1715 N Y Char 3 Enf Act-Current Planned Complete FY/Quarter
1716 Y S Date 6 Enf Act-Actual Start Date (MMDDYY)
1717 Y S Date 6 Enf Act-Actual Complete Date (MMDDYY)
1718 N Y Char I Enf Act-Judicial Civil Type
1719 Y Y Char 2 Enf Act-Negotiation/Litigation Outcome
1720 N Y lntg 3 Enf Act-Number RP Defendants
1721 N Y Char I Enf Act-Full/Partial Settlement
1722 N Y Char 20 EnfAct-SCAP Note
1723 N S Char 20 Enf Act-Contact Name
1724 N S Char 10 Enf Act-Contact Phone
1725 Y Y Char I Enf Act-Planning Status
1726 Y Y Char I Enf Act-Compliance Status
1727 Y Y Date 6 Enf Act-Compliance Change Date (MMDDYY)
1728 Y S Date 6 Enf Act-Date (MMDDYY)
1729 N S Char 6 Enf Act-Tune
1730 Y - Char 4 Enf Act-Enforcement Activity Type
1731 Y S Char 16 Enf Act-Enf Activity Concatenation Key
1732 Y S Char 2 Enf Act-Generic Type
1733 N S Char 3 Enf Act-User Id
1738 Y S Char 2 Enf Act-Link Chain
1739 N S Char 2 Enf Act-Historical Indicator
1740 N Y Char 2 Enf Act-Regional FieldI
1741 N Y Char 2 Enf Act-Regional Field2
1742 N V Char 4 Enf Act-Regional Field3
1743 N - Char 6 Enf Act-Regional Field4
1734 N - Char 2 Enf Act-Original Planned Start Fy
1735 N - Char 2 Enf Act-Original Planned Complete Fy
1736 N - Char 2 Enf Act-Current Planned Start Fy
1737 N - Char 2 Enf Act-Current Planned Complete Fy
1744 Y Y Char 60 EnfAct-OECM Case Name
1745 Y V Char 10 EnfAct-OECM Case Number
1746 N Y Char 79 EnfAct-DOJ Case Name
1747 N V Char 15 EnfAct-DOJ Case Number
1746 N Y Text 10 Enf Act-Outcome Short Name
1749 N - Char I EnfAct-VAM Flag
1774 N - Char 2 Enf Act-Action Type
1775 N - Char 3 Enf Act-Action Sequence
2 Y 2710 - - —- - Enforcement Activities Compliance
2711 N Y Char I Enf Act Compl-Status
2712 N Y Date 6 Enf Act Compl-Status Change Date (MMDDYY)
2713 Y Y Char 4 Enf Act Compl-Status Sequence Number
2714 Y V Char 20 Enf Act Compl-Status Concatenation Key
2718 N V Date 6 Enf Act Compl-Date (MMDDYY)
2719 N V Char 6 Enf Act Compl-Time
2720 N V Char 3 Enf Act Compl-User Id
2 Y 2730 - - — - Enforcement Remedy Action Sought
2731 V V Char 3 Enf Rem-Remedy Action
2732 Y V Char 21 Enf Rem-Concatenation Key
C-22 IDEA User’s Guide October 22, 1996
-------
Level Repeat Element Name index? Enfore Data Length Descnption
Record? (V/N) Sens? Type
(V/S/N)
2733 Y Y Char 2 Enf Rem-Operable Unit Indicator
2741 N Y Char 2 Enf Rem-Qualifier I
2742 N Y Char 2 Enf Rem-Qualifier 2
2743 N Y Char 2 Enf Rem-Qualifier 3
2744 N Y Char 2 Enf Rem-Qualifier 4
2745 N Y Char 2 EM Rem-Qualifier 5
2744 N Y Char 2 Enf Rem-Qualifier 6
2747 N Y Char 2 Enf Rem-Qualifier 7
2744 N Y Char 2 Enf Rem-Qualifier S
2749 N Y Char 2 Enf Rem-Qualifier 9
2750 N Y Char 2 Enf Rem-Qualifier 10
2751 Y Y Date 6 EnfRem-Date(MMDDYY)
2752 N V Char 6 Erif Rem-Time
2753 V V Char 3 Enf Rem-User Id
2754 N Y Char 2 Enf Rem-Field I
2755 N Y Char 2 Enf Rem-Field?
2756 N V Char 4 EM Rem-Field?
2757 N - Char 6 Enf Rem-Field4
2734 Y Y Char 14 Enf Rem-Operable Unit Concatenation Key
2735 Y - Char 4 Enf Rem-Special
2736 N V Text 10 Enf Rem-Remedy Short Name
2738 N V Char 17 Enf Rem-Event Concatenation Key
2739 N - Char 2 Enf Rem-Historical indicator
2760 N V Text 10 Enf Rem-Qualifier Short Namel
2761 N V Text 10 Enf Rem-Qualifier Short Name2
2762 N V Text 10 Enf Rem-Qualifier Short Name3
2763 N Y Text 10 Enf Rem-Qualifier Short Name4
2764 N V Text 10 Enf Rem-Qualifier Short NameS
2765 N Y Text 10 Enf Rem-Qualifier Short Nameó
2766 N V Text 10 Enf Rem-Qualifier Short Name7
2767 N V Text 10 Enf Rem-Qualifier Short Name8
2768 N Y Text 10 Enf Rem-Qualifier Short Name9
2769 N Y Text 10 Enf Rem-Qualifier Short NamelO
2 Y 2770 - - — - Enforcement Statutes
2771 V V Char 5 Enf Stat-Statute
2772 Y Y Char 21 Enf Stat-Concatenation Key
2773 Y V Date 6 Enf Stat-Date (MMDDYY)
2774 N V Char 6 Enf Stat-Time
2775 N V Char 3 Enf Stat-User Id
2779 N - Char 2 Enf Stat-Historical Indicator
2 Y 2800 - - — - Enforcement Milestone
2801 Y V Char 3 Erif Ms-Milestone
2802 Y V Char 19 Enf Ms-Concatenation Key
2803 N V Text 10 Enf Ms-Abbreviation
2804 N V Char 30 EM Ms-Name
2805 N Y Date 6 Enf Ms-Planned Date (MMDDYY)
2806 N Y Char 3 Enf Ms-Planned FY/Quarter
2807 N V Date 6 Enf Ms-Actual Date (MMDDYY)
2808 N V Char 20 Enf Ms-SCAP Note
2809 N V DaLe 6 Enf Ms-Original Planned Date (MMDDYY)
2810 N Y Char 3 Enf Ms-Original Planned FY/Quarter
2811 V V Char I Enf Ms-SPMS Target Status
2812 Y V Char 8 Enf Ms-Activity Lmk
2813 Y V Char 5 Enf Ms-Sort
2814 N V Char 2 Enf Ms-Regional Fieldi
2815 N - Char 2 Enf Ms-Regional FieId2
2816 N - Char 4 Enf Ms-Regional Field3
2817 N Y Char 6 Enf Ms-Regional Fieid4
2818 Y Y Date 6 Enf Ms-Date (MMDDYY)
2819 N V Char 6 Enf Ms-Time
2820 N V Char 3 Enf Ms-User Id
2821 Y V Char 2 Enf Ms-Generic Type
2822 N - Char 2 Enf Ms-Planned FY
2823 N - Char 2 Enf Ms-Original Planned FY
2839 N - Char 2 Enf Ms-Historical Indicator
3 Y 3800 - - ---- - Enforcement Milestone Comment
Appendix C Data Elements in IDEA Shadow Files C-23
-------
Level Repeat Element Name Index? Enforc Data Length Descnphon
Record? (YIN) Sens? Type
(V/S/N)
3801 N V Char 3 Enf Ms Comment-Id
3802 V V Char 22 Enf Ms Comment-Concatenation Key
3803 N Y Date 6 Enf Ms Comment-Date (MMDDYY)
3804 N Y Char 6 Enf Ms Comment-Time
3805 V Y Char 2 Enf Ms Comment-Type Code
3806 N Y Char 3 Enf Ms Comment-User Id
4 V 3810 - - — - Enforcement Milestone Comment Line
3811 N Y Char 2 Enf Ms Comment Line-Number
3812 V Y Char 24 Enf Ms Comment Line-Concatenation Key
3813 N Y Char 60 Enf Ms Comment Line-Text
3814 N Y Date 6 Enf Ms Comment Line-Date (MMDDYY)
3815 N Y Char 6 Enf Ms Comment Line-Time
3816 N V Char 3 Enf Ms Comment Line-User Id
2 Y 1790 - - — - Enforcement FMS Valid Financial
1791 V V Char 32 Enf FMS Valid Fm-Concatenation Key
1792 V V Char 6 Enf FMS Valid Fin-Document Control Number
1793 V Y Char 10 Enf FMS Valid Fm-Account Number
1794 N Y Date 6 Enf FMS Valid Fin-Date (MMDDYY)
1795 N Y Char 6 Enf FMS Valid Fm-Time
1796 N V Char 3 Enf FMS Valid Fm-User Id
1797 Y Y Char 16 EnI FMS Valid Fm-AcnfDcn Concatenation
2 Y 2900 - - — - Enforcement Financial
2901 V V Char 3 Enf Fin-Id
2902 Y S Char 19 Enf Fin-Concatenation Key
2903 V S Char I Enf Fm-Type
2904 N S Date 6 Enf Fm-Planned Date (MMDDYY)
2905 N S Char 3 Enf Fin-Planned Fy/Quarter
2906 N S Date 6 Enf Fin-Record Date (MMDDYY)
2907 N S lntg 5 Enf Fm-Amount
2908 V V Char 5 Enf Fm-Contract Vehicle
2909 N Y Char 3 Enf Fm-Funding Status
2910 N Y Char 30 EnI Fm-Note
2911 V S Date 6 EnfFin-Date(MMDDYY)
2912 N S Char 6 Enf Fm-Time
2913 N S Char 3 Enf Fm-User Id
2914 N V Char 2 EnI Fm-Regional Fieldl
2915 N - Char 2 Enf Fm-Regional Field2
2916 N - Char 4 Enf Fm-Regional Field3
2917 N - Char 6 Enf Fm-Regional Field4
2918 V Y Char 1 Enf Fm-Budget Source
2919 V V Char 6 Enf Fm-Work Assignment lag Number
2920 N Y Text 8 Enf Fm-Vehicle Abbreviation
2921 N - Char 2 Enf Fm-Planned Fy
2922 N Y Char 2 Enf Fm-Work Assignment Amendment Number
2939 N - Char 2 Enf Fm-Historical Indicator
3 V 3900 - - — - Enforcement Financial Comment
3901 N V Char 3 Enf Fm Comment-Id
3902 V Y Char 22 Enf Fm Comment-Concatenation Key
3903 N Y Date 6 Enf Fm Comment-Date (MMDDYY)
3904 N V Char 6 Enf Fm Comment-Time
3905 V - Char 2 Enf Fm Comment-Type Code
3906 N V Char 3 Erif Fm Comment-User Id
4 Y 3910 - - — - Enforcement Financial Comment Lmc
3911 N V Char 2 Enf Fm Comment Line-Number
3912 Y V Char 24 Enf Fm Comment Line-Concatenation Key
3913 N V Char 60 Enf Fm Comment Line-Text
3914 N V Date 6 Enf Fm Comment Line-Date (MMDDYY)
3915 N Y Char 6 Enf Fm Comment Line-Time
3916 N V Char 3 Enf Fm Comment Line-User Id
2 V 2440 - - — - Enforcement Lmk Record
2441 V S Text 6 Enf Link Record-Identifier
2442 V S Text 22 Enf Link Record-Concatenation Key
2443 Y S Char 2 Enf Link-Chain
2444 N S Char 3 Enf Link-Type
2445 V S Text 17 Enf Link-Key
2450 N S Char 12 Enf Lmk-Epa Id
C-24 IDEA User’s Guide October 22, 1996
-------
Level Repeat Element Name index? Enforc Data Length Descnption
Record? (V/N) Sens? Type
(V/S/N)
2451 N S Char 2 Enf Link-Operable Umt
2452 N S Char 3 Enf Link-Event
2453 N S Char 4 Enf Link-Activity
2454 N S Char 6 Enf Link Record-Time
2455 N S Date 6 Enf Link Record-Date (MMDDYY)
2456 N S Char 3 Enf Link Record-User Id
2 Y 2600 - - — - Enforcement FMS
2601 Y S Char 3 Enf FMS-Id
2602 Y S Char I Enf FMS-Type
2603 Y Y Char 6 Enf FMS-Document Control Number
2604 Y Y Char 10 Enf FMS-Account Number
2605 Y S Char 19 Enf FMS-Concatenauon Key
2606 Y V Char I Enf FMS-FMS Flag
2607 Y V Char 10 Enf FMS-Obhgaung Document Number
2608 V Y Char 4 Enf FMS-Subobject Class
2618 N Y Char 3 Enf FMS-Planned Obhgatmg FyfQuarter
2620 V S Date 6 Enf FMS-Date (MMDDYY)
2625 Y Y Char 3 Enf FMS-Fund Priority Status
2628 V Y Char 6 Enf FMS-Work Assignment lag Number
2629 V V Char 1 Enf FMS-Event Budget Source
2630 N S lntg 5 Enf FMS-Amount
2638 Y V Text 8 Enf FMS-Vehicle Abbreviation
2639 V Y Char 5 Enf FMS-Vehicle
2640 Y V Char 2 EnfFMS-Fy
2641 N Y Char 20 Enf FMS-Contractor Name
2642 N Y Char 30 Enf FMS-Note
2644 N - Char 6 Enf FMS-Regional Fieldi
2645 N - Char 6 Enf FMS-Regional Field2
2646 N - Char 6 Enf FMS-Regional Field3
2647 N - Char 6 Enf FMS-Regional Field4
2648 V S Date 6 Enf FMS-Update Date (MMDDYY)
2649 N S Char 6 Enf FMS-Update Time
2650 V S Char 3 Enf FMS-User Id
2631 N - lntg 5 Enf FMS-FMS Open Commitment
2632 N V mEg s Enf FMS-Totai Open Commitment
2633 Y - Char I Enf FMS-FMS Final Obhgation
2609 V V Char 16 Enf FMS.Acn/Dcn Concatenation Key
2634 N Y Char 2 Enf FMS-Work Assignment Amendment Number
2619 N - Char 2 Enf FMS-Historical Indicator
2651 N - Char 4 Enf FMS-Budget FY
2652 N - Char 6 Enf FMS-Fund
2653 N - Char 7 Enf FMS-OrganLzauon
2654 N - Char 9 Enf FMS-Pgm Element
2655 N - Char 8 Enf FMS-Site Project
2656 N - Char 8 Enf FMS-Cost Orgaruzation
3 Y 3920 - - - Enforcement FMS Comments
3921 N S Char 3 Enf FMS Comment-Id
3922 V S Char 22 Enf FMS Comment-Concatenation Key
3923 N S Date 6 Enf FMS Comment-Date (MMDDYY)
3924 N S Char 6 Enf FMS Comment-Time
3925 V - Char 2 Enf FMS Comment-Type Code
3926 N S Char 3 Enf FMS Comment-User Id
4 V 3930 - - - Enforcement FMS Comment Line
3931 N S Char 2 Enf FMS Comment Line-Number
3932 V S Char 24 Enf FMS Comment Line-Concatenation
3933 N S Char 60 Enf FMS Comment Line-Text
3934 N S Date 6 Enf FMS Comment Line-Date (MMDDYY)
3935 N S Char 6 Enf FMS Comment Line-Time
3936 N S Char 3 Enf FMS Comment Line-User Id
2 V 2950 - - — - Enforcement Activities Comment
2951 N V Char 3 Enf Act Comment-Id
2952 V V Char 19 Enf Act Comment-Concatenation Key
2953 N V Date 6 Enf Act Comment-Date (MMDDYY)
2954 N V Char 6 Enf Act Comment-Time
2955 V V Char 2 Enf Act Comment-Type Code
2956 N V Char 3 Enf Act Comment-User Id
Appendix C Data Elements in IDEA Shadow Files C-25
-------
Level Repeat Element Name Index? Enforc Data Length Description
Record? (YIN) Seas? Type
(V/S/N)
3 Y 2960 - - - Enforcement Activities Comment Line
2961 N Y Char 2 Enf Act Comment Line-Number
2962 Y Y Char 21 Enf Act Comment Line-Concatenation Key
2963 N Y Char 60 Enf Act Comment Line-Text
2964 N Y Date 6 Enf Act Comment Line-Date (MMDDYY)
2965 N Y Char 6 Enf Act Comment Line-Tune
2966 N Y Char 3 Enf Act Comment Line-User Id
Y 1500 - - — - PRP Agency
1501 V Y Char 4 PRP Agency-Code
1502 Y Y Char 16 PRP Agency-Concatenation Key
1503 N V Date 6 PRP Agency-Date (MMDDYY)
1504 N V Char 6 PRP Agency-Time
1505 N V Char 3 PRP Agency-User Id
1509 N - Char 2 PRP Agency-Historical Indicator
Y 1570 - - — - Media
1571 Y Y Char 2 Media-Contaminated Medium Code
1572 N Y Char I Media-Goal Attained
1573 N V Char I Media-Threat Eliminated
1574 Y Y Char 14 Media-Concatenation Key
1575 N Y Char 6 Media-Record Time
1576 N Y Date 6 Media-Record Date (MMDDYY)
1577 N V Char 3 Media-Record User Id
1578 N - Char 2 Media-Historical indicator
Y 1000 - - — — Latitude Longitude
1001 Y S Char 14 Lat-Lon-Concat-Key
1002 N Y Char 10 Lat-Lon-Descripuon-Code
1004 N S Char 60 Lat-Lon-Descripuon-TexL
1005 N S Char 10 Lat-Lon-Lautude
1006 N S Char Ii Lat-Lon-Longitude
1007 N S Char 10 Lat-Lon-Method-Type
1008 N S Char 2 Lat-Lon-Method-Data
1009 N - Char 6 Lat-Lon-Method-Scale
1010 N S Char 6 Lat-Lon-Accuracy
1011 N S Char I Lat-Lon-Accuracy-Umts
1012 N S Char 2 Lat-Lon-Data-Source
1013 V S Date 4 Lat-Lon-Date
1014 N S Char 6 Lat-Lon-Time
1015 Y S Char 3 Lat-Lon-User-Id
Y 0990 - - - IDEA
0991 Y S Char 4 IDEA-Name
0992 Y S Char 5 IDEA-State/County
C.4 CRM-Criminal Docket Data Elements (9/96 )
Group Repeat Element Name index? Enforc Data Length Description
Record? (Y/N) Seas? Type
(V/S/N)
CASE4A) N SUE Y N Char 2 State
CSNO Y N Char 9 Case Number
DEF( 13) N INDX N N Num 4 Index
CASE.(A) N CITY Y N Char 15 City
REGN V N Char 2 Region
CSNM N N Char 60 Case-Name
PLAW Y N Char 5 Primary Law
MMED V N Char I Multi-Media
CLEV V N Char I Case-Level
CRES V N Char 2 Case-Result
REAS V N Char 2 Case-Reason
DAOP N N Date 8 Case Opened Date (YYYYMMDD)
C-26 IDEA User’s Guide October 22, 1996
-------
(Y/SIN)
Length Description
C.5 DCK-Enforcement Docket Data Elements (9/96 )
RESP OFFC(A)
CASE NUM(B)
CASE B)
Repeat Element Name
Record?
N RSOF
N CSNO
N TYPC
CCAT
CSNM
SUBNAME
HQDV
SPCASE3
CSST
REGN
N PLS
RSLT
FPLT
CRCA
ASTA
OSTA
SSID
AISS
CAFO
CV 10
(Y/N) Seas? Type
(Y/S/N)
Y S Char 2
Y S Char 10
Y S Char 7
Y S Char I
N S Char 60
Y S Char 10
Y S Char 3
V S Char 4
Y S Char 2
Y S Char 2
Y S Char I
Y S Char 2
V S Num9
V S Num9
Y V Char2
Y S Char I
N S Char 4
N V Date4
N V Date4
V V Date4
Responsible Office
Case Number
Type Case
Case Category
Case Name
Case Name (First 10 Characters)
HQ Division
Case Category + HQ Division
State
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)
Group Repeat Element Name Index?
Enlorc
Data
Record?
(V/N)
Sens
Type
RTSL
N
N
Date
8
Referral To State Date (YVYYMMDD)
ORDT
N
N
Date
8
Office of Crimmal Enforcement-Refer-Date (YYYYMMDD)
DRDT
N
N
Date
8
Department of Justice-Refer-Date (YYYYMMDD)
URDT
N
N
Date
8
US Attorney-Refer-Date (YYYYMMDD)
GilD
N
N
Date
8
Grand Jury-Initiated-Date (YYYVMMDD)
CLDT
V
N
Date
S
Case-Closed-Date (YYYYMMDD)
MED(A)
Y
MEDC(K)
V
N
Char
I
Media Code
LAW(A)
DEF(B)
Y
N
LAWS(K)
SECT(K)
DFNM
V
V
N
N
N
N
Char
Char
Char
5
6
50
Law
Section
Defendant Name
CTNO
DFME
DFTY
DIC1’
DFLV
DFRS
CRME
DAID
DAPL
DAAP
DASN
FINE
IMPR
IMPS
PROB
CTMD
Y
Y
Y
N
V
V
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
Char
Char
Char
Char
Char
Char
Char
Date
Date
Date
Date
Nuni9
Nuni
Nuni
Nuni
Char
20
I
I
4
I
2
I
8
8
8
8
5
5
5
I
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 (YVYYMMDD)
Sentenced Entered Date (VYYYMMDD)
Fine
Imprisonment
Imprisonment Served
Probation
Citation Media
CIT(B)
V
CITX(K)
SiTS
STSS
CICT
CRCD
V
V
N
N
N
N
N
N
N
N
Num
Char
Char
Nuni
Nurn
4
10
15
4
4
Citation Index
Statute-Title-Citation
Statute-Subsection
Citation-Count of indictments
Citation-Count of Resulting Convictions
ANC(B)
V
ANCI(K)
ANTh
N
N
N
N
Char
Char
10
15
Ancillary Citation
Ancillary Subsection
Group
Index? Enforc Data Length Description
Appendix C Data Elements in IDEA Shadow Flies
C-27
-------
Group Repeat Element Name index? Enforc Data Length Description
Record? (V/N) Sens? Type
(V/S/N)
CDMD Y Y Date 4 First Demand Letter Sent (YYMM)
CRAA Y Y Date 4 Regional Attorney Assigned (YYMM)
CPRN Y Y Date 4 Mini-Lit Package Sent (YYMM)
CPRC Y Y Date 4 Mini-Lit Package Received HQ (YYMM)
CPRH Y Y Date 4 Mini-Lit Package Reviewed HQ (YYMM)
CPRD V Y Date 4 Mini-Lit Package Reviewed DOJ (YYMM)
CREF V Y Date 4 Referred (YYMM)
RCHQ Y V Date 4 Received HQ (YYMM)
HQRV Y V Date 4 HQ Review (YYMM)
CDOJ Y V Date 4 To DOJ (YYMM)
CUSA V Y Date 4 To US Attorney (YYMM)
CFLD V S Date 4 Filed Court (YYMM)
CCNC Y S Date 4 Concluded (Civil) (YYMM)
CLSD V S Date 4 Closed (YYMM)
CRET Y V Date 4 Returned To Region (YYMM)
CRRE Y V Date 4 Re-referred (YYMM)
PART Y S Char I Partial Indicator
LAWS(B) Y LAWS(K) Y S Char 7 Law - Section
SEC (K) N S Char 7 Section
POLLUTANT(B) V POLL(K) V S Char 20 Pollutant
VIOLTYPE B) Y VIOT(K) Y S Char 6 ViolationType
PLA INTIFF(H) V PLTF(K) N V Char 40 Plaintiff Name
INTERVENOR(B) Y INTV(K) N V Char 40 Plaintiff- Intervenor
DEFENDANT(B) Y DFNM(K) V S Char 40 Defendant Name
AMENDMNT(B) V ANUM(K) N V Num 2 Amendment Number
ATYP Y S Char I Amendment Type
DINT N V Date 4 Date Initiated (YYMM)
DDOJ N Y Date 4 Date To DOJ (YYMM)
DCNC N S Date 4 Date Concluded (YYMM)
DFLD N S Date 4 Date Filed (YYMM)
DPLT V Y Num 9 Decree Penalty
COMMENT(B) V PGNM(K) N Y Num 4 Page Number
LNNM(K) N Y Num 4 Line Number
CSTX N Y Char 60 Comments - Case Summary Only
C.6 DUN-Dun & Bradstreet Data Elements (9/96 )
Group Repeat Element Name Index? Enforc Data Length Description
Record? (V/N) Seas? Type
(V/S/N)
DNUM(B) N DCNO V V Num 9 Company Number
COMPANY(B) N DNME N Y Char 30 Business Name
SCNM N Y Char 30 Second Name
DSTR N Y Char 25 Street Address
DCT’Y N V Char 20 City Name
DSTA N Y Char 2 State Abbreviation
DZIP V Y Num 5 Zip Code
REGN Y Y Char 2 Region
CNTY N V Num 3 County FIPS Code
STCNTV V V Char 6 State/County (SS/CCC)
SALESV V V Num 15 Sales Volume
ESTRNG N Y Char I Code for est/range
EMPLTOT V Y Num 9 Total number of Employees
ACTRNGT N V Char I Code for act/range total
EMPLHER V V Num 9 Employees Here
ACTRNGH N V Char I Code for act/range here
YRST N V Date 4 Year Started (VYYY)
STAT N V Char I Status
SUBI N V Char I Subsidiary Indicator
C-28 IDEA User’s Guide October 22, 1996
-------
Index? Enforc Data Length Description
Group
Repeat Element Name
Record?
(Y/N) Sens’ Type
(V/S/N)
M FG I
U LNO
HQNO
DPNO
U LNOFOR
DPNOFOR
HI ER
DIAS
DDAT
Sici
LAT
LONG
LONG LAT
LLMATCH
REG L
SIC2
SIC3
SIC4
SIC5
SIC6
SICC
N Y Charl
Y Y Nusn9
Y Y Num9
Y Y Num9
Y Y Num9
Y Y Num9
N Y Num2
N Y Num9
N Y Date6
N Y Num4
N Y Num5
N Y Num5
V V NumlO
N Y Charl
Y Y Charl
N Y Num4
N Y Num4
N V Num4
N Y Num4
N Y Nuni4
V V Nuzn4
Manufacturmg Indicator
Ultimate Number
Headquarters Number
Parent Number
Ultimate Number Foreign (*future use*)
Parent Number Foreign (*future use*)
Hierarchy Code
Dias Code
Date Of D&B Report (YYMMDD)
SIC Code-I
Latitude In Degrees
Longitude In Degrees
Longitude + Latitude
Lot/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 SICI thru SIC6)
Repeat Element Name
Record?
N STATE
DID
N DTRPT
TM R PT
OWNID
Y DOWNID(K)
DORG
DORGT
DADD
DCOUNTY
DFIPSCO
DCITY
DST
DSTCNTY
DZI P
DPHI
DPH2
DUNS
DREGION
N INIT
MUD
SRC
RSOURCE
RNAME
RNO
RNO2
TRANSNR
MU LT
MREPCNT
MCASE
MCASEID
FOLLWUP
Index? Enforc
(V/N) Sens?
( V/S/N )
N N Char2
N N Num8
Y N Date8
N N Num4
Y N Num9
N N Num9
N N Char 32
Y N Char2
N N Char 70
N N Char 20
N N Nurn3
N N Char 32
V N Char2
V N Char5
Y N Char 10
N N Char 17
N N Char 17
Y N Char 12
Y N Char2
Y N Charl
Y N Charl
Y N Char2
Y N Char I
Y N Char 20
V N Char 12
V N Char 12
V N Char 20
V N Char I
V N Num3
V N Char 12
V N NumS
N N Char5
Id State
Discharger Id
Report Date (YYYYMMDD)
Report Time
Uruque 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 I
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 Report
EPA Unique Identifier
Multiple Report Indicator
Multiple Report Count
Multiple Case NBR
Multiple Case Id
Followup Codes
C. 7 ERN Emerj !encv Resnonse Notification
Group
System Data Elements (9/96)
Data
Type
Length Description
001 REPT(A)
002 REPT(B)
DSCHG(A)
O2 OREPT(B)
Appendix C Data Elements in IDEA Shadow Files
C-29
-------
Group Repeat Element Name Index? Enfore Data Length Descnption
Record? (YIN) Sens? Type
(V/S/N) -
FOLLWCT N N Num 3 Count Of Report Updates
CRTYPE Y N Char 1 Continuous Release Type
CRNO Y N Char 12 Continuous Release Number
DTSPI Y N Date 8 Date Spill (YYYYMMDD)
TMSPI N N Num 4 Time Spill
DTGTYPE N N Char I Spill Observation Type
DNAME N N Char 32 Discharger Name (individual)
SPILLER N N Char I Caller Is Discharger
DTDSCVR Y N Date 8 Discovery Date (YYYYMMDD)
MATS N N Char I Materials Released Ind
JURI Y N Char I Jurisdiction
RPTBL Y N Char I Reportable
DTCANCL N N Date 8 Date Cancel Letter (YYYYMMDD)
HMIS N N Char 3 HMIS Code
ERRC N N Char I Data Error Code
DTHC N N Date 8 Date Hardcopy (YYYYMMDD)
ISTAT Y N Char I Incident Status
DTMEMO N N Date 8 Superfund Action Memo Date (YYYYMMDD)
MEMAPPR N N Char I Superfund Action Memo Approved
ENFI N N Char 2 Enforcement Activity Code I
ENF2 N N Char 2 Enforcement Activity Code 2
ENF3 N N Char 2 Enforcement Activity Code 3
ENF4 N N Char 2 Enforcement Activity Code 4
ENF5 N N Char 2 Enforcement Activity Code 5
DTPOLR N N Date 8 Pollution Report Issued Date (YYYYMMDD)
MONITOR Y N Char 1 On Scene Monitoring
INVEST Y N Char I Release Investigation
TDDNBR N N Char 9 Technical Direction Doe NBR
PHONAST N N Char I Telephone Assistance
ERACTVT N N Char I Superfund Compr Accomp Plan Activity
DTERA N N Date 8 Date Of Emer Resp Activity (YYYYMMDD)
ERAOSC N N Char 20 Emer Response On-Scene Coordinator
DTENTRY N N Date 8 Date Of Entry (YYYYMMDD)
DTCHNG N N Date 8 Date Of Change (YYYYMMDD)
SPILL(B) N SAM ELOC N N Char 1 Spill At Caller/Discharger Site
SCOUNTY N N Char 20 Spill County
SFIPSCO N N Num 3 Spill Location County Code - Derived
SCITY N N Char 32 Spill City
SST N N Char 2 Spill State
SSTCNTY V N Char 5 Spill Location State County Code
SZIP Y N Char 10 Spill Zip
SPLREGN V N Char 2 EPA Region Where Spill Occurred
LOCATE V N Num 8 Latitude/Longitude
LAT N N Num 4 Latitude
LONG N N Num 4 Longitude
QUADLAT N N Char I Latitude Quadrant
QUADLON N N Char I Longitude Quadrant
DISTANC N N Num 5 Distance From City
CUNITS N N Char 2 Distance From City Units
COMPASS N N Char 3 Compass Heading
SECTION N N Char 10 Section
TOWN N N Char 20 Township
RANGE N N Char 10 Range
FIELD N N Char 25 Field Id
BLOCK N N Char 15 Block Id
MILPOST N N Char 5 Milepost
MTRLS(B) Y MTRLSEQ(K) N N Num 1 Material Spilled Sequence Nbr
CHEMID Y N Nuni 5 Nat’l Transportation Sys Cntr Chem-id
MATSP N N Char 32 Material Spilled
CHRIS Y N Char 3 Chemical Hazards Response Info Sys Code
UNDOT Y N Char 6 DOT Hazardous Substance Code
CAS Y N Num 10 Chemical Abstracts Svc Registry Number
QTYSP Y N Nuni 6 Quantity Spilled
UNITSP N N Char 3 Quantity Spilled Units
LBS Y N Num 6 Quantity In Pounds
QUAW Y N Num 6 Quantity In Water
C-30 IDEA User’s Guide October 22, 1996
-------
Group Repeat Element Name Index? Enforc Data Length Description
Record? (V/N) Sens? Type
(V/S/N)
UNITSW - N N Char 3 Quantity In Water Units
DETLS(B) N CONTANR N N Char I Container Type
TANKCNT N N Num 3 Tank Count
TAN KCAP N N Num 6 Tank Capacity
TUN ITS N N Char 3 Tank Capacity Units
FACCAP N N Num 6 Facility Capacity
FUNITS N N Char 3 Facility Capacity Units
MODE V N Char I Transport Mode
MODEl N N Char I Transport Mode I
MODE2 N N Char 1 Transport Mode 2
VID N N Char 20 Vehicle Id
SOURCE Y N Char 2 Source Code
MAIR Y N Char I Medium - Air
MLAND Y N Char I Medium - Land
MWATER Y N Char I Medium - Water
MGRDWFR V N Char I Medium - Groundwater
MFAC V N Char I Medium - Facility
MOTH Y N Char I Medium - Other
MEDCODE V N Char 2 Medium Code
MEDDESC N N Char 40 Medium Description
TRANS V N Char I Trans Accident
EQUIP Y N Char I Equipment Failure
OPERR V N Char I Operator Error
NATURAL Y N Char I Natural Phenomenon
DUMPING V N Char I Dumpmg
UNKNOWN V N Char I Cause Unknown
COTH V N Char I Other Cause
CAUSE Y N Char 2 Cause Code
INJS Y N Num 3 Injuries
DEATHS V N Num 3 Deaths
EVAC Y N Char I Evacuation md
EVACS V N Num 5 Number Of Evacuations
DAMAGES Y N Char I Damage Ind
PROPDMG Y N Num 6 Property Damage S
ROAD Y N Char I Road Closure
FLIGHT V N Char I Flight Pattern Altered
THREATI N N Char 2 Threat Code I
THREAT2 N N Char 2 Threat Code 2
THREAT3 N N Char 2 Threat Code 3
THREAT4 N N Char 2 Threat Code 4
THREATS N N Char 2 Threat Code 5
AC1’N(B) N CNEPA N N Char I EPA Notified By Caller
CNSTLOC N N Char I State/Local Govt Notified By Caller
CNDSCH N N Char I Discharger Notified By Caller
CNUSCG N N Char I US Coast Guard Notified By Caller
CNOTH N N Char I Other Agency Notified By Caller
CNUNK N N Char I Unknown If Parties Notified By Caller
CNOT IF N N Char 30 Other Agency Notified By Caller
NTSBHWY N N Char I NTSB Highway Administration Notified
NTSBPIP N N Char I NTSB Pipeline Safety Notified
NTSBRR N N Char I NTSB Railway Adrmnistration Notified
RSPAOHM N N Char I RSPA/OHM Notified
RSPAOPS N N Char I RSPA/OPS Notified
DOTFRA N N Char I Department Of Transportation FRA Notified
DOTFAA N N Char I Department Of Transportation FAA Notified
DOTOMCS N N Char I Department Of Transportation OMCS Notified
MISCNRC N N Char I Nuclear Regulatory Commission Notified
MISCDOE N N Char I Department Of Energy Notified
MISCFEM N N Char I FEMA Notified
MISCDOD N N Char I Department Of Defense Notified
MISCATS N N Char I ATSDR Notified
MISCOSH N N Char I OSHA Notified
MISCTEC N N Char I Chemtrec Notified
AGENCY N N Char 40 Other Agency Notified
TMOTH N N Num 4 Time Other Agencies Notified
REGION V N Char 2 EPA Region Initially Notified
Appendix C Data Elements in IDEA Shadow Files C-31
-------
Group Repeat Element Name
Record?
TMEPA
CGU
TM CO U
RNAME I
RNAME2
RNAME3
RAGCYI
RAGCY2
RAGCY3
DO
N ATEXT
DTEXT
LTEXT
MTEXT
MTEXTX
Index? Enforc
(YIN) Sens?
( V/S/N )
N N Num4
N N Char5
N N Num4
N N Char 30
N N Char 30
N N Char 30
N N Charl
N N Charl
N N Charl
N N Char 20
N N Char 142
N N Char 255
N N Char 142
N N Char 255
N N Char 29
Time EPA Notified
Coast Guard Unit
Time Coast Guard Notified
Responding Agency I
Responding Agency 2
Responding Agency 3
Responding Agency I Code
Responding Agency 2 Code
Responding Agency 3 Code
National Response Center Duty Officer
Action Text
Description Text
Location Text
Miscellaneous Text
Miscellaneous Text
C.8 FF1-Federal Facilities In formation System Data Elements (9/96 )
index? Enforc
(V/N) Seas?
(V/S/N)
Data
Type
Length Description
TEXT(B)
Group
Repeat Element Name
Record?
Data
Type
Length Description
FF ID(A)
N
FFID
Y
N
Char
12
Federal Facility Id Number
AGCY
V
N
Char
2
Agency Code
AGBU
Y
N
Char
4
Agency + Bureau Code
PROJ NUM(B)
N
PRJN
Y
N
Char
10
Project Number
FACL(A)
N
REGN
RECK
FNAM
DDAC
STRT
CITY
ZIPC
CFRY
Y
V
Y
N
N
Y
Y
N
N
N
N
N
N
N
N
N
Char
Char
Char
Char
Char
Char
Num
Char
2
13
50
I
30
30
9
3
Region
Region + State + AGBU + GSA Installation Number + Record Type
Facility Name
Department Of Defense Agency Code
Street
City
ZipCode
Country
PROJECT(B)
N
PNAM
PMED
STFL
PROC
CMFY
CRFF
CPST
POLC
AGPA
EPPA
FCRQ
N
Y
Y
Y
N
N
Y
V
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Char
Char
Char
Char
Date
Char
Char
Char
Char
Char
Num
50
2
I
I
2
I
4
4
I
I
4
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
LAWS(B)
Y
ST1’E(K)
SECN(K)
Y
N
N
N
Char
Char
7
7
Statute
Section
C-32 IDEA User’s Guide
October 22, 1996
-------
C.9 FIN-Facility Index System Data Elements (9/96 )
Group Repeat Element Name Index? Enforc Data Length Descnption
Record? (Yf N) Seas? Type
(V/S/N)
FAC ID(B) N EPID Y S Char 12 EPA Id
NAMES(B) N U DATE Y S Date 8 Update Date (yyyymmdd)
CDATE Y S Date 8 Create Date (yyyymmdd)
NAME N S Char 50 Facility Name
ADDRESS N S Char 50 Facility Address
SECADDR N S Char 20 Secondary Address
CITY N S Char 30 City
STATE Y S Char 2 State
ZIP Y S Num 5 ZIP Code
REGION Y S Char 2 EPA Region
CNTYCD N S Num 3 County Code
FEDFAC V S Char I Federal Facility Indicator
INDLAND Y S Char I Indian Land Indicator
SECNAME N S Char 50 Secondary Name
COMMENT N S Char 60 Analyst Comment (first or only line)
VNAME N S Char 50 IDEA-voted Facility Name (all linked databases voting)
VADDR N S Char 50 IDEA-voted Facility Address
VCITY N S Char 30 IDEA-voted City
VSTATE V S Char 2 IDEA-voted State
VZIP V S Nuni S IDEA-voted ZIP Code
VREGION Y S Char 2 IDEA-voted Region
VCNTYCD N S Nuni 3 IDEA-voted County Code
VLATD N S Real 5 IDEA-voted Latitude in Degrees
VLONG N S Real 5 IDEA-voted Longitude in Degrees
IDENT(B) Y SRCE(K) N S Char I Source File
SRID(K) N S Char 19 Source Id
SRI DSEQ(K) N S Num 3 Sequence Number
FNME N S Char 50 Facility Name
STRI N S Char 90 Street Addressl
FCTY N S Char 30 City
STAT Y S Char 2 State
FZIP V S Num S Zip Code
REGN V S Char 2 Region
FCTC N S Num 3 FIPS County Code
STCNTV V S Char 6 State + FIPS County Code (SS/CCC)
LATD N S Nurn 5 Latitude in Degrees
LONG N S Nurn S Longitude In Degrees
LLACC N S Nuni 5 Accuracy In Degrees
LLCOMM N S Char 60 Lat/Long Description, Method, Comments
LONGLAT V S Num 10 Longitude + Latitude
C.1O LST-Contractor ListinR Docket Data Elements (9/96 )
Group epeat Element Name Index? Enforc Data Length L)escnpflon
Record? (V/N) Seas’ Type
(V/SIN)
RSOF(A) N RSOF Y S Char 2 Responsible Office
CASE(B) N CSNO Y S Char 10 Case Number
CASE(B) N TYPC Y S Char 7 Type Case
CSNM N S Char 60 Case Name
HQDV Y S Char 3 HQ Division
CSST Y S Char 2 State
REGN Y S Char 2 Region
Appendix C Data Elements in IDEA Shadow Files C-33
-------
Group
Repeat
Record?
Element Name
index? Enforc
(V/N) Sens?
Data
Type
Length Descnption
(V/S/N)
END
Y
S
Char
12
EPA Id Number
FTYP
Y
S
Char
3
Facility Type
RGNM
Y
S
Char
IS
Region Attorney
HQNM
Y
S
Char
15
HQ Attorney
DJNM
Y
S
Char
15
Department Of Justice (DOJ) Attorney
USNM
Y
S
Char
15
US Attorney
RCNM
Y
S
Char
15
Regional Contact
GCNM
Y
S
Char
15
Office of General Counsel (OGC) Attorney
HCNM
Y
S
Char
15
HQ Contact
RFIN
Y
S
Char
2
Referral Indicator
VIOC
N
S
Char
4
Violator Category
CCST
Y
S
Num
3
Contractor Case Status
DCOP
Y
S
Date
9
Date Case Opened (YYYYMMDD)
DC!N
Y
S
Date
9
Date Case Initiated (YYYYMMDD)
DCLS
Y
S
Date
9
Date Case Listed (YYYYMMDD)
DCCL
Y
S
Date
9
Date Case Closed (YYYYMMDD)
SRMD
Y
S
Date
9
Schedule Removal Date (YYYYMMDD)
LONM
Y
S
Char
15
Listing Official
SANM
Y
S
Char
15
State Attorney
SCNM
Y
S
Char
15
State Contact
CENM
Y
S
Char
15
Case Examiner
OLNO
N
S
Char
7
Old Case Number
DRRL
N
Y
Date
9
Date Discretionary Recommendation Received by Listing Officer
(LO) (YYYYMMDD)
DPTA
N
Y
Date
9
Disc Package To AEC (YYYYMMDD)
DCFA
N
Y
Date
9
Disc Comnt From AEC (YYYVMMDD)
DAAB
N
Y
Date
9
Disc Assitant Adjnm,st.rator Briefed (YYYYMMDD)
DPNS
Y
Y
Date
9
Disc Proposed NT Sent (YYYYMMDD)
DPNR
N
Y
Date
9
Disc Proposed NT Received (YYYVMMDD)
DRHR
N
Y
Date
9
Disc Req Hear Received (YYYYMMDD)
DDES
N
Y
Date
9
Disc Case Examiner (CE) Designated (YYYYMMDD)
DHEA
N
Y
Date
9
Disc Hearing (YYYYMMDD)
DCED
N
Y
Date
9
Disc Case Examiner Decision (YYYYMMDD)
DCNS
N
Y
Date
9
Disc Case Examiner Decision NT Sent (YYYYMMDD)
DCNR
N
Y
Date
9
Disc Case Examiner Dec NT Received (YYYYMMDD)
DARO
N
Y
Date
9
Disc Appeal Req Office of General Counsel (OGC)
(YYYYMMDD)
DOGD
N
Y
Date
9
Date of Disc Office of General Counsel (OGC) Decision
(YYYYMMDD)
DLIS
Y
S
Date
9
Disc Listed (YYYYMMDD)
DAAD
N
Y
Date
9
Effective Date In Notice Sent to the Facility That AA Has
Declined To List The Facility (YYYYMMDD)
DCNL
N
Y
Date
9
Disc Case Examiner Dec Not Listed (YYYYMMDD)
DONL
N
Y
Date
9
Disc OGC Dec Not Listed (YYYYMMDD)
DWDR
Y
Y
Date
9
Disc Withdrawn (YYYYMMDD)
MPRR
N
Y
Date
9
Mandatory Date That Petition For Removal Is Received From
Facility (YYYYMMDD)
MRGR
N
Y
Date
9
Mandatory Region Review (YYYYMMDD)
MRRR
N
Y
Date
9
Mandatory Region Rev Received (YYYYMMDD)
MARE
N
Y
Date
9
Mandatory AEC Review (YYYYMMDD)
MARR
N
Y
Date
9
Mandatory AEC Review Received (YYYYMMDD)
MAAR
N
Y
Date
9
Mandatory AA Review (YYYYMMDD)
MARC
N
V
Date
9
Mandatory AA Review Received (YYYYMMDD)
MJDG
Y
Y
Date
9
Mandatory Judgement (YYYYMMDD)
MLIS
Y
S
Date
9
Mandatory Listed (YYYYMMDD)
MLRM
Y
S
Date
9
Mandatory Listed And Removed (YYYYMMDD)
MCDM
Y
S
Date
9
Mandatory Case Dismissed (YYYYMMDD)
RRRR
N
Y
Date
9
Removal—Request Received from Contractor by Listing Officer
(YYYYMMDD)
RRTR
N
V
Date
9
Removal—Request To Region (YYYYMMDD)
RFRG
N
V
Date
9
Removal—From Region (YYYYMMDD)
RRTA
N
Y
Date
9
Removal-Resp To AEC (YYYYMMDD)
RFAE
N
V
Date
9
Removal-From AEC (YYYYMMDD)
RRDN
Y
Y
Date
9
Removal-Remove Deny NT (YYYYMMDD)
RDNR
N
V
Date
9
Removal-Deny NT Rec (YYYYMMDD)
RRHR
N
Y
Date
9
Removal-Request Hearing (YYYYMMDD)
C-34 IDEA User’s Guide
October 22, 1996
-------
P0 LL( B)
LAW(B)
CFR(B)
RLFS(B)
BAS I(B)
SDWA(B)
CRVL (B)
PEFA(B)
PRRM(B)
CSCM(B)
FCI N(B)
Repeat Element Name
Record?
RCDG
RH ER
RCED
RCDN
RCDR
RADD
RADM
RREM
Y POLL(K)
Y LAW(K)
S ECT(K)
Y CFRT(K)
C FRS C K)
Y RLFS(K)
Y BLAW(K)
BACI’(K)
Y SDWAPG(K)
SDWALN(K)
SDWA
Y CRVLPG(K)
CR V LLN( K)
CRVL
Y PEFAPG(K)
PEFALN(K)
PEFA
Y PRRMPG(K)
PRRMLN(K)
PRRM
Y CSCMPG(K)
CSCMLN(K)
CSCM
V FCINPG(K)
FCINLN(K)
FCIN
index? Enfore
(Y/N) Sens?
( V/S/N )
N Y Datc9
N Y Date9
N Y Date9
N Y Date9
N Y Date9
N Y Date9
N Y Date9
V S Date 9
Y S Char 20
Y S Char 7
Y S Char 7
Y S Char 5
N S Char 20
Y S Char 4
V S Char 3
Y S Char 3
N S Num4
N S Num4
N S Char 60
N Y Num4
N Y Num4
N Y Char 60
N V Num4
N Y Num4
N V Char 60
N Y Num4
N Y Num4
N Y Char 60
N V Num4
N Y Num4
N Y Char 60
N Y Nurn4
N Y Nuni4
N Y Char 60
C.11 NCD-National Compliance Database Data Elements (9/96 )
INDEP(A)
SAM PS C B)
COMMN(A)
Repeat Element Name
Record?
N NCDBID
N SAMPNBR
N INVSTYP
LEGISLA
PRODUCT
REASON
REFERRL
REGION
RGNSTAT
‘1 NAMESEQ(K)
NAMETYP
NAME
ADDRESS
CITY
STATE
ZIP
ZIPS
SICLIST
SIC
Index? Enforc
(YIN) Sees?
( V/S/N )
Y S Char 19
V S Char 3
V S Char 3
V S Char I
V S Char 14
Y S Char 3
Y S Char 2
Y S Char 2
Y S Char 2
N S Char I
N S Char 8
N S Char 40
N S Char 40
N S Char 20
Y S Char 2
N S Char 10
V S NumS
N S Char 29
V S 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 jState/Territory /Tribc Code
Sequence N umber for N ame
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 m SICLIST)
Group
Data
Type
Length Description
Removal—Case Examiner Designated (YYYYMMDD)
Removal-Hearing (VVYYMMDD)
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 (YYYYM M DD)
Removed (YYYYMMDD)
Pollutant
Law
Section
Code-Fed-Reg (CFR) Title
Code-Fed-Reg (CFR) Section
Relief Sought
Basis 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 Coniment.s Page
Case Status Comments Line
Case Status Comments Comment
Facility Information Page
Facility Information Line
Facility Information Comment
Group
Data
Type
Length Description
I DENT(A)
Appendix C Data Elements in IDEA Shadow Files
C-35
-------
Group Repeat Element Name Index? Enlorc Data Length Descnption
Record? (YIN) Seas? Type
(V/S/N)
DUN N S Char 11 DUNS Number With Dashes
INSPECI’(A) N AUDITS N S Num 4 Number of Audits During inspection
EPESTAB N S Char 12 Pesticide Producer Establishment Number
FACILIT Y S Char 2 Facility Function Code
FEDFAC Y S Char I Federal Facility Flag
INSPDTE Y S Date 8 Date of Inspection (YYYYMMDD)
INSPNBR Y S Char 5 Inspector Number - 11111
NBRSAMP N S Nuni 4 Number of Samples Taken
SCHLTYP V S Char I School System Type Code
SCHOOLS N S Num 4 Number of Schools Inspected
CASNMBR V S Char 10 CAS Number of Chemical Investigated
CERTIF Y S Char 3 Status of Chemical Srch/Recs Review
CHEMFRM N S Char 60 Formula of Chemical Investigated
CHEMNAM N S Char 60 Name of Chemical lnvesugated
ENTRYDT Y S Date 8 Date of Import (YYYYMMDD)
ENTRYNO N S Char 15 Import Number of Chemical Investigated
INVENTY V S Char I TSCA Inventory Status of Chemical
TARIFF N S Char 10 Tariff Schedule Number
REFERRAL(A) N DESTIN N S Char 2 Destination of Referral Code
DOCCASE N S Char 15 Docket or Case Number
ENFISSU Y S Date 8 Date Enforcement Action Issued (YYYYMMDD)
ENFTARG V S Date 8 Date Enforcement Action Targeted (YYYYMMDD)
EN FWARR V S Char I Enforcement Action Warranted Flag
INSTARG Y S Date 8 Date inspection Targeted (YYYYMMDD)
INSPCON Y S Date 8 Date Inspection Conducted (YYYYMMDD)
INSPECT Y S Char 13 Inspection Number (YYYYMMDDIIIISS)
ORIGIN N S Char 2 Origin of Referral Code
REFDATE Y S Date 8 Date of Referral (YYYYMMDD)
REFTYPE Y S Char 2 Referral Type
REFERBY N S Char 20 Referred By (Person/Company/etc)
REQRECD V S Date 8 Date Referral Request Received (YYYYMMDD)
SAMPLES N S Char I Samples To Be Taken flag (YIN)
ACF IONS(A) N ABATEMN V S Num 9 Abatement Work (in dollars)
ACTNTYP V S Char 3 Action Type Code
AOISSUE V S Date 8 Date Minor Action issued (YYYYMMDD)
APPEAL Y S Date 8 Date of Appeal (YYYYMMDD)
CHEM ICL N S Char 20 Name of Chemical in Enforcement Action
CLOSED V S Date 8 Date Action is Closed (YYYYMMDD)
DATEVAC V S Date 8 Date Action is Vacated (YYYYMMDD)
FNLPENL V S Num 9 Final Penalty Assessed (dollars)
HQCONCR V S Date 8 Date of HQ Concurrence (YYYYMMDD)
PROPENL Y S Num 9 Proposed Penalty (dollars)
REFERHQ Y S Date 8 Date of Referral to HQ (YYYYMMDD)
SENTHQQ Y S Date 8 Date Action Sent to HQ (YYYYMMDD)
VIOCDE N S Char 23 Violation Codes (Max of six)
VIOCODS V S Char 3 Violation Code (any Code in VIOCDE)
CAFOMAI N S Date 8 Date CAFO Mailed (YYYYMMDD)
CAFOREC N S Date 8 Date CAFO Received (YYYYMMDD)
CAFOTHM N S Date S Date CAFO Signed (Them) (YYYYMMDD)
CAFOUS N S Date 8 Date CAFO Signed (EPA) (YYYYMMDD)
DISACTN N S Date 8 Date of District Court Action (YYYYMMDD)
FNDDEC N S Date 8 Date of ALJs Decision (YYYYMMDD)
HEARHLD N S Date S Date of Hearing (YYYYMMDD)
MAISSUE V S Date 8 Date Major Action Issued (YYYYMMDD)
MAWITI-ID N S Date 8 Date Major Action Withdrawn (YYYYMMDD)
REFRDOJ N S Date 8 Date Action Referred to DOJ (YYYYMMDD)
SNC V S Char I Significant Noncomplier Flag
ADMJUD Y S Char I Administrative/Judicial Action Flag
NUMEBES Y S Num 4 Number of EBE Settlement Terms
STATUS V S Char I Action Status (Open/Closed/Withdrawn)
TERMS(A) Y TERMSEQ(K) N S Num 4 Sequence Number
COST N Y Num 9 Cost to Respondant per EBE Term
DUE N S Date S Date Settlement Conditions Due (YYYYMMDD)
EBE V S Char I Env Beneficial Expenditure Flag
PPCODE N S Char 3 Pollution Prevention Type Code
REC N S Date 8 Date Settlement Conditions Term Received (YYYYMMDD)
C-36 IDEA User’s Guide October 22, 1996
-------
Group Repeat Fiement Name Index? Enforc Data Length Descnption
Record? (Y/N) Sens? Type
(V/S/N)
TERM N S Char 50 Description of Terni
AMTMIT N Y Num 9 Amount Mitigated for EBE5 (dollars)
GRANT(A) N AGUSE N S Num 7 S1.ate Form 5700-33H Agricultural Use Inspections
AGFOLLO N S Nuni 7 State Form 5700-33H Agricultural Followup Inspections
NAGUSE N S Num 7 State Form 5700-33H Nonagricultural Use Inspections
NAGFOLL N S Num 7 State Form 5700-33H Nonagricultural Foflowup Inspections
EXPERIM N S Num 7 State Form 5700-33H Experimental Use Inspections
PROESTB N S Num 7 State Form 5700-33 H Producing Establishment inspections
MARKET N S Num 7 State Form 5700-33H Marketplace Inspections
IMPORTS N S Num 7 State Form 5700-33H Imports Inspections
EXPORT N S Nuni 7 State Form 5700-33 H Exports inspections
CERTAPL N S Num 7 State Form 5700-33H Certified Applicator Inspections
RUPDEAL N S Num 7 State Form 5700-33H RUP Dealer Inspections
TOTAL N S Num 10 State Form 5700-33H Total of All Inspections
PVTAPPL N S Num 7 State Form 5700-33H Private Applicators
COMMAPP N S Num 7 State Form 5700-33H Commercial Applicators
AGRLPLT N S Num 7 State Form 5700-33H Agricultural/Plant Applicators
AGRLANL N S Num 7 State Form 5700-33H Agricultural/Animal Applicators
FOREST N S Num 7 State Form 5700-33H Forest Applicators
ORNTURF N S Num 7 State Form 5700-33 H Ornamental and Turf Applicators
SEEDTRE N S Num 7 State Form 5700-33H Seed Treatment Applicators
AQUATIC N S Num 7 State Form 5700-33H Aquatic Applicators
RGHTOFW N S Num 7 State Form 5700-33 H Right of Way Applicators
INDSTRH N S Num 7 State Form 5700-33H Industrial/Health Applicators
PBLHEAL N S Num 7 State Form 5700-33H Public Health Applicators
REGULA N S Num 7 State Form 5700-33H Regulatory Commercial Applicators
DEMORES N S Num 7 State Form 5700-33H Demonstration/Research Applicators
OTHER N S Num 7 State Form 5700-33H Other
CASESMPL(B) N ACTWRNT N S Char I Action Warranted Flag
COMPDTE Y S Date 8 Date Case Review Completed (YYYYMMDD)
DATESNT Y S Date S Date Sample Sent to Lab (YYYYMMDD)
MEDIUM Y S Char 3 Sample Medium Code
SPRODCT Y S Char 14 EPA Registration Number of Sample Product
VOLATIV Y S Char I Violative Sample Flag
MULTACI’S(B) V ACTNID(K) N S Char 19 Case or Docket Number
IACTNTY Y S Char 3 Action Type Code
IAOISSU Y S Date 8 Date Minor Action Issued (YYYYMMDD)
ICLOSED Y S Date S Date Action is Closed (YYYYMMDD)
IFNLPEN Y S Num 9 Final Penalty Assessed (dollars)
IPROPEN Y S Nuni 9 Proposed Penalty (dollars)
IRGNSTA Y S Char 2 Region/State/Territory issuing Action
IVIOCDE N S Char 23 Violation Codes (Max of six)
IV1OCOI) V S Char 3 Violation Code (ally Code to IVIOCDE)
ICAFOMA N S Date 8 Date CAFO Mailed (YYYYMMDD)
ICAFOUS N S Date 8 Date CAFO Signed (EPA) (YYYYMMDD)
IMAISSU Y S Date 8 Date Major Action issued (YYYYMMDD)
IMA WITH N S Date 8 Date Major Action Withdrawn (YYYYMMDD)
IREFRDO N S Date 8 Date Action Referred to DOJ (YYYYMMDD)
ISNC Y S Char I Significant Noncomplier Flag
IADMJUD Y S Char I Administrative/Judicial Action Flag
INUMEBE Y S Nun, 4 Number of EBE Settlement Terms
ISTATUS Y S Char I Action Status (Open/Closed/Withdrawn)
C.12 OSH-OcduDational
Safety & Health Administration Data Elements (9/96)
Group Repeat
Record?
ESTABLMT(A) N
Element Name
ESTABST
index?
(V/N)
N
Enforc
Sens?
(V/S/N)
Y
Data
Type
Char
Length Descnption
2 Establishment State
Appendix C Data Elements in IDEA Shadow Files C-37
-------
Group Repeat Element Name Index? Enforc Data Length Descnption
Record? (YIN) Sens? Type
(V/S/N)
ESTABNR N Y Num 9 Activity Link For Establishment
AC1’IV ITY(B) N ACTIVTY V Y Nurn 9 Inspection Activity NR
STEM(B) N HISTFLG N V Char I History_Flag
DTMOD N V Date 6 Date Last Modified (YYMMDD)
OFFICE N Y Char 7 Reporting Office Id
REGION V V Num 2 Region
CSHOJOB N V Char I Job Title Of Comphance Officer
CSHO N Y Char 5 Compliance Officer Id
ESTAB N Y Char 30 Establishment Name
SITE N V Char 30 Inspection Site Address
SITEST V V Char 2 Inspection Site State
SITEZIP Y V Nurn 5 Inspection Site Zip Code
SITECNT N V Num 3 Inspection Site GSA County Code
STCNTY V V Char 6 State and County Code (SS/ )
SITECTY N V Num 4 Inspection Site GSA City Code
STCITY V V Char 7 State and City Code (SS/ 4ffl)
DTOPEN V Y Date 6 Date Of Opening Conf Or Attempted Insp (YYMMDD)
INSPCAT Y V Char I Safety Or Health Inspection
INSPTP V Y Char I Inspection Type
INSPSCO V Y Char I Scope Of Inspection
SICPRIM N V Num 4 Primary SIC For Establishment
DTEXIT N V Date 6 Date Of Closing Conf Or Exit From Site (YYMMDD)
STATUS N V Char I Case CIosed ’
DTCLOSE Y V Date 6 Date Case Closed (YYMMDD)
UNION N Y Char I Employees Represented By Umo&
TOTEM FL Y V Nurn 7 Total Number Of Employees Nationally
SITEMPL N Y Num 5 Number Of Employees At Inspection Site
INSEMPL N V Num 5 Number Of Employees Affected By Inspection
RPTLOCL V V Char 9 Local Report Number
I- IRSPREP N V Num 4 Hours Preparing For Inspection
HRSTRAV N V Num 4 Travel Time
HRSSITE N V Num 4 Hours On Site
HRSSUPP N V Num 4 Hours Employer Abatement Assistance
HRSRPT N V Num 4 Hours Completing Case File
HRSCONF N Y Nurn 4 Hours Off-Site Conferences
HRSLITG N Y Num 4 Hours Preparing/Litigating Case
HRSDENI N Y Nurn 4 Hours Denial Activity
HRSTOT N Y Num 9 Total Hours Al] Inspection Activity
ADVNTC N Y Char I Advance Notice Given’
ESTABTP Y Y Char I Establishment Ownership Type
NALINK N V Num 9 Name/Address Link Assigned By EPA
PREVACT N Y Nurn 9 Previous Activity NR (Discontinued)
DUDTSRC N V Char I Source Of Penalty Due Date
DTPEN N Y Date 6 Date Penalties Due (YYMMDD)
AMTPEN Y Y Num 9 Total Penalties Issued
AMTRPEN N Y Num 9 Total Penalty Amount Remitted
VIOI.S V V Num 5 Total Violations Cited
SRVIOLS V V Nuri 5 Total Serious Violations Cited
LWDI V V Num 5 Lost Workday Injury Rate
STFLG N V Char I State Flag
SAFTMAN N V Char I Manufacturing Safety lnsp
SAFTCON N Y Char I Construction Safety Insp
SAFTMAR N V Char I Maritime Safety lnsp
HLTH MAN N Y Char I Manufacturing Health Insp
HLTHCON N V Char I Construction Health Insp
HLTHMAR N V Char I Maritime Health Insp
EMPLINT N V Char I Employee Enterviewed’
EMPLREP N Y Char I Employee Rep Present’
NOINSP N Y Char I Reason For No Inspection
DTCNTST N Y Date 6 Date lnsp Contest Received (YYMMDD)
DTDENI N Y Date 6 Date Of Initial Denial Of Entry (VYMMDD)
DTLAST N Y Date 6 Date Of Last Reentry After Entry Denied (YYMMDD)
LOCAL N Y Char 10 Local Emphasis Program Insp
SPECPGM N V Char 10 National Special Emphasis Program lnsp
MIGRANT N V Char I Migrant Farmworker Camp Insp
DUN Y Y Num 9 Dun & Bradstreet Number For Establishment
C-38 IDEA User’s Guide October 22, 1996
-------
Group Repeat Element Name index? Enfore Data Length Descnption
Record? (V/N) Sens’ Type
(V/S/N)
SICINSP N Y Num 4 SIC Inspected
SICGUID N V Num 4 SIC Scheduled For Inspection
SIC V V Num 4 SIC Code (Pnmary, Inspected, or Scheduled)
FEDAGCY V V Num 4 Federal Agency Code
DTFTA N Y Date 6 Date Failure-To-Abate Penalties Due (YYMMDD)
AMTFTA N V Num 9 Total FTA Penalties Issued
AMTRFTA N V Num 9 Total ETA Penalty Amount Remitted
WARRANT Y V Char I Anticipatory Warrant Served 9
REL ACTV(B) Y RELITEM(K) N Y Char 2 Related Activity Item Number
RELTYPE N V Char I Related Activity Type
RELACT N Y Num 9 Related Activity Number
RELSAFT N V Char I Further Safety lnsps Not Required
RELHLTH N Y Char I Further Health lnsps Not Required
OPTL INFO(B) Y OP’VF’YPE(K) N Y Char I Optional information Originator
OPTID(K) N V Char 2 Optional Information Id Code
OPTVALIJ N V Char 12 Optional Information
DEBT(B) N DBTDTNX N V Date 6 Date Next Installment Due (YYMMDD)
DBTDTLA N V Date 6 Date Last Installment Due (YYMMDD)
DBTDTSL N Y Date 6 Date Referred To Solicitor (YYMMDD)
DBTRSNR N V Char I Reason Referred To Solicitor
DBTHOLD N V Char I Case Held At National Office
PEN WV N V Char I Assessed Penalty Waived
PEN WRSN N V Char 1 Reason Penalty Waived
PENDTCL N V Date 6 Date Referred To Nail Offc For Coil (YYMMDD)
PEN INT N V Num 7 Interest Assessed By National Office
PENDLQ N Y Num 7 Delinquent Fees Assessed By National Office
PENDTDC N V Date 6 Date Sent To Debt Collection Agency (YYMMDD)
PENDTRT N V Date 6 Date Returned From Debt Coil Agcy (YYMMDD)
PEN DCAR N V Char I Reason Returned From Debt Collection Agency
PENDCHG N V Num 7 Additional Litig Credit Report Charges
PEN DFEE N Y Num 7 Debt Collection Agency Fees
PENARCH N V Char I Case Archived 1
PENDCIN N V Num 7 Interest Assessed By Debt Collection Agency
PEN DCFE N Y Num 7 Delinquent Fees Assessed By Debt Collection Agency
PENDRVW N Y Date 6 Date Sent To Area OITc For Addi Rev (YYMMDD)
PEN DRET N V Date 6 Date Return From Area Offc From Rev (YYMMDD)
PENRVWR N V Char I Reason Sent To Area Office
PENDAOC N V Date 6 Date StTo Area Offc After Debt Coil (YYMMDD)
PEN DCBS N Y Date 6 Date Sent To Credit Bureau (YVMMDD)
PENDIRS N Y Date 6 Date Sent To IRS (YYMMDD)
PEN DCBR N Y Date 6 Date Recalled From Credit Bureau (YYMMDD)
FTAWV N Y Char I Assessed Penalty Waived
F1’AWRSN N Y Char I Reason Penalty Waived
FTADTCL N Y Date 6 Date Referred To Nail Ofic For Coil (YYMMDD)
FTAINT N Y Num 7 Interest Assessed By National Office
F1’ADLQ N V Nuni 7 Delinquent Fees Assessed By National Office
FTADTDC N Y Date 6 Date Sent To Debt Collection Agency (YYMMDD)
FTADTRT N Y Date 6 Date Returned From Debt Coil Agency (YYMMDD)
FTADCAR N Y Char I Reason Returned From Debt Collection Agency
FTADCH 3 N V Num 7 Additional Litig Credit Report Charges
FTADFEE N V Num 7 Debt Collection Agency Fees
FTAARCH N Y Char I Case Archived’
FTADCIN N Y Num 7 Interest Assessed By Debt Collection Agency
FTADCFE N V Num 7 Delinquent Fees Assessed By Debt Collection Agency
FTADRVW N Y Date 6 Date Sent To Area Ofic For AddI Rev (VYMMDD)
FTADRET N Y Date 6 Date Ret From Area Offc From Rev (YYMMDD)
FTARVWR N V Char I Reason Sent To Area Office
FTADAOC N Y Date 6 Date St To Area OfTc After Debt Coil (VYMMDD)
FFADCBS N Y Date 6 Date Sent To Credit Bureau (YYMMDD)
FTADIRS N Y Date 6 Date Sent To IRS (YYMMDD)
FTADCBR N Y Date 6 Date Recalled From Credit Bureau (YYMMDD)
VIOLATIONS(B) Y VIOLKEY(K) N Y Char 7 Violation Key
HSTDT(K) N V Date 6 Event History Date (Penalty Or FTA) (YYMMDD)
HSTEVNT(K) N V Char I Cause Of Activity Against Viol Record
VDTISSU(1) V Y Date 6 Date Citation Issued (YYMMDD)
VIOLATN(I) V V Char 22 Std/Reg/Law Violated
AppendIx C Data Elements fl IDEA Shadow Files C-39
-------
Group Repeat Element Name index? Enforc Data Length Description
Record? (YIN) Sens? Type
(V/S/N)
VINTTYP(l) N Y Char I Initially Determined Violation Type
VCURTYP(I) N Y Char I Currently Determined Violation Type
VCNT(I) N Y Num 5 NumberOflnstancesOfViolation
VDTABAT(1) N Y Date 6 Violation Abatement Date (YYMMDD)
VSTS(1) N V Char I Violation Status
VEXPOSD(1) N Y Num 5 Number Employees Exposed To Hazard
VINTPEN( 1) N Y Num 7 Initial Penalty
VCURPEN(I) N V Num 7 Current Penalty
HSTVTYP(2) N Y Char I Violation Type At Time Of Update
HSTDTAB(2) N Y Date 6 Abatement Date At Time Of Update (YYMMDD)
HSTPEN(2) N Y Num 7 Penalty At Time Of Update
HSTACTP(2) N Y Char I Update Action Against Penalty
VGRAVE(I) V Y Char 2 Potential Harm To Workers
VREC(l) N Y Char I Related Event Code
VISA(I) N V Char I Informal Settlement Agreement 9
VDELETE(1) N Y Char I Violation Deleted
VDTPNCN(1) N Y Date 6 Earliest Contest Date (YYMMDD)
VIOLCN(1) N Y Char I Violation Contested’
VPNCN(1) N Y Char I Penalty Contested 9
VABTCNR(I) N V Char I Employer Contests Abatement 9
VABTCNE 1) N V Char I Employee Contests Abatement 9
VDTFINO(I) N Y Date 6 Final Order Date (YYMMDD)
VPMA(1) N Y Char I Petition To Modify Abatement Approved’
VAMEND(1) N Y Char I Citation Amended Prior To Contest 9
VDSPCN(I) N Y Char 1 Disposition Of Contested Violation
I- IAZSUB I(I) N Y Char 4 Hazardous Substance Related To Violation
HAZSUB2(1) N Y Char 4 Hazardous Substance Related To Violation
HAZSUB3(1) N V Char 4 Hazardous Substance Related To Violation
I-IAZSUB4(1) N Y Char 4 Hazardous Substance Related To Violation
HAZSUBS(1) N Y Char 4 Hazardous Substance Related To Violation
I- 1AZSUB V V Char 4 Hazardous Substance (1, 2, 3, 4, or 5)
VDTFTA(I) N V Date 6 Date PTA Issued (YYMMDD)
VFTACTN(1) N V Num 9 Activity Number Of lnsp ETA Assessed
VFTA(I) N Y Num 7 FTA Penalty Assessed
VFTAISA(1) N Y Char I Informal Settlement Agreement For PTA 9
VDTFTCN(1) N Y Date 6 Date PTA Contested (YYMMDD)
VFTAMND(1) N Y Char I PTA Amended Prior To Contest 9
VDSPFTA(I) N Y Char I Disposition Of Contested FTA
VEGREG(I) V V Char 1 Egregious Case 9
HAZCAT(I) N N Char 10 Unknown OSHA v6 field (Hazard Category 9 )
HSTFTAN(2) N V Num 9 ETA History Inspection Number
HSTPTA(2) N Y Num 7 PTA Penalty At Time Of Update
HSTACTF(2) N Y Char 1 Update Action Against ETA Penalty
HS2PTAN(2) N Y Num 9 2nd PTA History Inspection Number
HS2FFA(2) N Y Num 7 2nd PTA Penalty At Time Of Update
HS2ACTF(2) N V Char 1 2nd Update Action Against PTA Penalty
ACCIDENTS(B) V ACCITEM(K) N Y Nuni 4 Accident Item Number
ACCNAME N Y Char 20 Name Of Victim
ACCDGRE V Y Char I Degree Of Injury
ACCTASK N Y Char I Assigped Task At Time Of Accident
ACCNATR N Y Char 2 Nature Of Injury
ACCBODY N Y Char 2 Part Of Body injured
ACCSRC Y V Char 2 Source Of injury
ACCTYPE V Y Char 2 Accident Type
ACCENV Y Y Char 2 Environmental Factor Contributing To Accident
ACCHUM V V Char 2 Human Factor Contributing To Accident
ACCVSEX N Y Char I Sex Of Victim
ACCVAGE N Y Char 2 Age Of Victim
ACCOCCU N V Char 3 Occupation Code Of Victim
ACCSUB N Y Char 5 Hazardous Substance Contributing To Accident
ADMIN(B) Y ADMTYPE(K) N Y Char I Administrative Data Type
ADMDT(K) N Y Date 6 Date Of Administrative Action (YVMMDD)
ADMAMT N Y Num 7 Administrative Assessment Applied
PAYMENT(B) V PAYTYPE K) N Y Char I Payment Type
PAYDT(K) N Y Date 6 Date Payment Received (YYMMDD)
PAY PEN N Y Nuth 7 Amount Of Payment For Assessed Penalty
C-40 IDEA User’s Guide October 22, 1996
-------
Repeat Element Name
Record?
PAY FTA
PAY 163
PAYORG
PAY BAL
index’ Enlorc
(V/N) Sens?
( V/S/N )
N Y Num7
N N Num9
N N Charl
N N Charl
C.13 PCS-Permit Compliance System Data Elements (9/96 )
Length Dcscnption
Group
Data
Type
Length Descnption
Amount Of Payment For Assessed FTA Penalty
Unknown OSHA vó field
Unknown OSHA v6 field
Unknown OSHA v6 field
Group
Repeat Element Name Index?
Enforc
Data
Record?
(V/N)
Sens?
(V/S/N)
Type
NPID(A)
N
NPDES
Y
N
Char 9
NPDES Identification Number
PIPE(B)
N
DSCH
V
N
Char 3
Discharge Number From Pipe Schedule
PERMIT FAC(A)
N
REGN
Y
N
Char 2
Region
PTYP
V
N
Char I
Permit Type
IACC
Y
N
Char I
Activity Flag
NAMI
N
N
Char 30
Facility Name (Concatenation of PNAM and PNMZ)
NAM2
N
N
Char 30
Facility Name - Part 2
MADI
Y
N
Char I
Major/Minor Discharge Indicator
SIC2
V
N
Num 4
SIC Code 2
CYNM
N
N
Char 20
From City And State
CNTN
N
N
Char 20
County Name
INCL
V
N
Char I
Industrial Classification
TYPO
V
N
Char 3
Ownership Classification
FTYP
V
N
Char I
Facility Type
EPST
N
N
Char I
EPA Or State Permit
CNTY
N
N
Num 4
County FIPS Code
STCNTY
V
N
Char 7
State (from NPDES Id) And County Code (SS/#)
RNAM
N
N
Char 30
Name Of Facility
RSTR
N
N
Char 60
Street
RCTY
N
N
Char 23
City
RSIT
N
N
Char 2
State
RZIP
Y
N
Num 5
ZipCode
BAS4
N
N
Nurn 4
River Basin Code
CITY
N
N
Num 9
EPA City Code
IADT
N
N
Date 6
Facility Inactive Date (YYYYMM)
CFRC
V
N
Char 5
CFR Code (From SIC)
FDGR
V
N
Char I
POTW With Federal Grant
FLIM
V
N
Char I
Final Limits Indicator
FLAT
N
N
Num 5
Latitude
FLON
N
N
Nuni 5
Longitude
FLLC
N
N
Char I
Lat/Long Accuracy Code
FLOW
V
N
Char S
Design Flow MGD
PRET
Y
N
Char I
Pretreatment Program Required
NPSC
V
N
Char I
NMP Final Schedule
NPFF
N
N
Char I
NMP Financial Status
NPSQ
N
N
Char I
NMP Schedule Quarter
ARDT
N
N
Date 6
Archival Date (YYYYMM)
CYQS
N
N
Char 4
Current Year Noncompliance Status
CYQS I
V
N
Char I
Currcnt Year NC Status - 1st Quarter
CYQS2
V
N
Char 1
Current Year NC Status - 2nd Quarter
CYQS3
V
N
Char I
Current Year NC Status - 3rd Quarter
CYQS4
V
N
Char 1
Current Year NC Status -4th Quarter
PYQS
N
N
Char 4
Previous Year Noncompliance Status
PYQSI
V
N
Char 1
Previous Year NC Status - 1st Quarter
PYQS2
V
N
Char I
Previous Year NC Status - 2nd Quarter
PYQS3
V
N
Char I
Previous Year NC Status - 3rd Quarter
PYQS4
V
N
Char I
Previous Year NC Status -4th Quarter
CYMS
N
N
Char 4
Current Year Noncompliance (Manual)
CYMSI
V
N
Char I
Current Year NC (Manual) - 1st Quarter
Appendix C Data Elements in IDEA Shadow Files
C-41
-------
Index? Enforc
(V/N) Sens ’
( Y/S/N )
V N Char I Current Year NC (Manual) - 2nd Quarter
Y N Char I Current Year NC (Manual) - 3rd Quarter
V N Char I Current Year NC (Manual) -4th Quarter
N N Char 4 Previous Year Noncompliance (Manual)
V N Char I Previous Year NC (Manual) - 1st Quarter
Y N Char 1 Previous Year NC (Manual) - 2nd Quarter
V N Char I Previous Year NC (Manual) - 3rd Quarter
V N Char I Previous Year NC (Manual) - 4th Quarter
V N Char 1 Current Year Noncomphance Status, 1st quarter (tins data
is also stored in HNC for active major dischargers)
CYNC2 V N Char I Current Year Noncompliance Status, 2nd quarter (this data
is also stored in HNC for active major dischargers)
CVNC3 V N Char I Current Year Noncompliance Status, 3rd quarter (this data
is also stored in HNC for active major dischargers)
CYNC4 V N Char I Current Year Noncompliance Status, 4th quarter (this data
is also stored in HNC for active major dischargers)
PVNC I V N Char I Previous Year Noncompliance Status, 1st quarter (this data
is also stored in HNC for active major dischargers)
PYNC2 Y N Char I Previous Year Noncompliance Status, 2nd quarter (this data
is also stored in HNC for active major dischargers)
PYNC3 V N Char I Previous Year Noncompliance Status, 3rd quarter (this data
is also stored in HNC for active major dischargers)
PVNC4 V N Char 1 Previous Year Noncompliance Status, 4th quarter (this data
is also stored in HNC for active major dischargers)
8 Facthty USGS Hydrological Basin Code
4 Facility Stream Segment
5 Facility Mileage Indicator
30 DMR Mailing Address Name of Facility
60 DMR Mailing Address Street
23 DM R M ailing Address City
2 DMR Mailing Address State
5 DMR Mailing Address Zip Code
I Headquarters Special Purpose 01
I Latest Reported Noncompliance (Current refresh data.)
I Latest Official Reported Noncomphance (Extracted from
PCS at the last QNCR due date.)
VIOLQTR Y N Num 2 # Quarters In Violation - Last 2 Years. Calculated umug
HQRTR and HNC, for active major dischargers only.
INSPDAY V N Num 5 # Days Since Last inspection
HQRTR V N Date 5 I-hstoncal Noncompliance Quarter (YYYVQ)
HNC Y N Char I Historical Noncompliance for the quarter in HQRTR
(only retained for active major djschnrgers)
N N Date 8 End Date (YYYYMMDD)
N N Num 4 # SIUS In SNC With Pretreatment Schedule
N N Num 4 # Suits Filed Against SIUS
N N Num 4 # NOVs And AOs Against SIUS
N N Num 4 # Industrial Users Who Paid Penalty
N N Num 4 SIUS With Violation Published In Papers
V S Date 8 Inspection Date (YYYYMMDD) — Corresponds to DTIA
(for PCI/Audit records), DTIN (for Inspection records),
and SDTI (for Inspection Schedule records)
INSPTYP(K) V S Char I Inspection Type — Corresponds to IATY (for PCI/Audit
records) TYPI (for Inspection records), and STYP (for
Inspection Schedule records)
INSPCOD(K) Y S Char I Inspector Code — Corresponds to INSP (for Inspection
records), and SINS (for inspection Schedule records)
SIDT(K) N S Date 6 Scheduled Date (YYYYMM)
ICOM(2) N S Char 100 Comments
S IUS(1) N S Num 4 # Significant Industrial Users
CIUS(1) N S Num 4 Categorial industrial Users
NOCM(1) N S Num 4 SIUS Without Control Mechanism
PSNC(1) N S Char 3 SIUS In SNC With Pretreatment
NOIN(1) N S Num 4 SIUS Not Inspected
MSNC(1) N S Num 4 # SIU In SNC With Self-monitoring
SNIN(1) N S Num 4 # SIUS In SNC With Self-monitoring/Not Inspected
PTIM(1) N S Date 6 Date Pretreatment Required (YYYYMM)
Group
Repeat Element Name
Record?
Data
Type
Length Description
CYMS2
CYMS3
CYMS4
PYMS
PYMSI
PYMS2
PYMS3
PYMS4
CYNCI
FHBC
FSEG
FM LG
MNAM
MSTR
MC I ’Y
MSTT
MZI P
I-IQOI
LRNC
LONC
N N Num
N N Num
N N Real
N N Char
N N Char
N N Char
N N Char
V N Num
V N Char
N N Char
N N Char
HIST COMPL(A)
PRETRT PRF(A)
I NSPECTNS(A)
V
Y PSED(K)
SSNC
JUDI
FEN F
I U PN
sVPU
Y INSPDTE(K)
C-42 IDEA User’s Guide
October 22, 1996
-------
Group Repeat Eiement Name Index? Enforc Data Length Description
Record? (V/N) Sens? Type
(V/S/N)
ADLL(1) Y S Char I Adoption Of Technically-based Limits
EVLL(I) N S Char I Technical Evaluation For Local Limits
PERM EVNT(A) Y PTEV(K) N N Char 5 Event Code, req’d national events only
PTAC N N Date 6 Event Actual Date (YYYYMM)
PTEVNT V N Char 9 Permit Tracking Event & Actual Date
COMP SCHD(A) V VCSN(K) N N Char 2 Compliance Schedule Number
VDCD(K) N N Char 4 Data Source Code
CVEV(K) N N Char 5 Event
CV 10(K) N N Char 3 Violation Code
CVDT(K) N N Date 6 Violation Date (YYYYMM)
SNCC N N Char I Reportable Noncomphance For Event
SNDC N N Date 6 Date Of Reportable Noncompliance (YYYYMM)
SNCCDT V N Char 5 RNCForEvent&DateOFRNC
SRCC N N Char I Resolution Of Reportable Noncompliance
SRDC N N Date 6 Resolution Date (YYYYMM)
ENF ACTNS(A) Y ENAC(K) Y S Char 2 Enforcement Action Code
EATP(K) Y N Char I Action Lead (‘E’ or ‘S)
ENDT(K) Y N Date 8 Action Date (YYYYMMDD)
ENST N N Char 2 Status Code
ESDT N N Date 6 Status Date (YYYYMM)
ENSTDT V N Char 6 Status Code & Date
ERDT N N Date 6 Response Due Date (YYYYMM)
APCL Y N Char I Administrative Penalty Class (I or 2)
APFO Y N Date 6 Date Final Order (YYYYMM)
APAM Y N Num 6 Penalty Amount Assessed
APPC V N Date 6 Date Penalty Collected (YYYYMM)
APPA V N Num 6 Amount Assessed by Judicial Decision
APPD Y N Date 6 Deadline for Penalty Payment (YYYYMM)
APTC V N Num 6 Total Penalty Collected
EFFLUENTS(B) V RPTDSGR(K) N N Char I Report Designator — Corresponds to DRID (for Pipe
Schedule records), PLRD (for Parameter Limits
records), and VDRD (for Measurements/Violations records)
PIPESET(K) N N Char I Pipe Set Qualifier — Corresponds to PIPQ (for Pipe
Schedule records), LIPQ (for Parameter Limits records),
and VIPQ (for Measurements/Violations records)
LM’TTYPE(K) N N Char I Limit Type/Number — Corresponds to LTYP (for
Parameter Limits records), and VLIM (for Measurementsf
Violations records)
PARAMTR(K) V N Char 5 Parameter Code — Corresponds to PRAM (for Parameter
Limits records), and VPRM (for Measurements/Violations
records)
MONLOCN(K) N N Char I Monitoring Location — Corresponds to MLOC (for
Parameter Limits records), and VMLO (for Measure-
ments/V iolations records)
SEASON(K) N N Char I Seasonal Indicator — Corresponds to SEAN (for Parameter
Limits records), and VSEA (for Measurements/Violations
records)
MODNUM(K) N N Char I Modification Number — Corresponds to MODN (for
Parameter Limits records), and VMOD (for Measure-
ments/V iolauons records)
MVDT(K) V N Date 8 Monitoring Date (YYYYMMDD)
FLSD(I) N N Date 8 Final Limits Start Date (YYYYMMDD)
FLED(I) N N Date 8 Final Lumts End Date (YYYYMMDD)
MLSD(I) N N Date 8 Interim Limits Start Date (YYYYMMDD)
MLED(l) N N Date 8 Interim Limits End Date (YYYYMMDD)
ILSD(l) N N Date 8 Initial Limits Start Date (YYYYMMDD)
ILED(I) N N Date 8 Initial Limits End Date (YYYYMMDD)
STRP(I) N N Date 8 Initial Report Date (YYYYMMDD)
NRPU(l) N N Num 3 Units In Reporting Period
REUN(l) N N Char I Reporting Units
PIAC(I) N N Char I Pipe Inactive Code
PIDT(I) N N Date 8 Pipe Inactive Date (YYYVMMDD)
STSU(I) N N Date 8 InitialDMRDate(YYYYMMDD)
NSUN(I) N N Num 2 Units In Submission Period - EPA
SUUN(I) N N Char I Submission Units
STSS(I) N N Date 8 Submission Date (YYYYMMDD)
Appendix C Data Elements in IDEA Shadow Files C-43
-------
Group Repeat Element Name index? Enfore Data Length Description
Record? (YIN) Sens? Type
(Y/S/N)
NSUS(l) N N Num 2 # Units In Submission Period - State
SUUS(1) N N Char I State Submission Units
NSUB(l) Y N Date 8 Next DMR Due Date (YYYYMMDD)
LTYP(2) N N Char I Limit Type/Alpha
LCMX(2) N N Char 8 Concentration Maximum Limit
LCAV(2) N N Char 8 Concentration Average Limit
LCMN(2) N N Char 8 Concentration Minimum Limit
LCUC(2) N N Char 2 Concentration Unit Code
LQMX(2) N N Char 8 Quantity Maximum Limit
LQAV(2) N N Char 8 Quantity Average Limit
LQUC(2) N N Char 2 Quantity Unit Code
LQAS(2) N N Char 2 Quantity Average Limit Statistical Code
LQXS(2) N N Char 2 Quantity Maximum Limit Statistical Code
LCMS(2) N N Char 2 Concentration Minimum Limit Statistical Code
LCAS(2) N N Char 2 Concentration Average Limit Statistical Code
LCXS(2) N N Char 2 Concentration Maximum Limit Statistical Code
LCMO(2) N N Char I Concentration Minimum Limit Override
LCAO(2) N N Char I Concentration Average Limit Override
LCSX(2) N N Num 8 Concentration Maximum Limit Standard
LCSA(2) N N Num 8 Concentration Average Limit Standard
LCSM(2) N N Num 8 Concentration Minimum Limit Standard
LCSC(2) N N Char 2 Concentration Unit Code
LQSX(2) N N Num 8 Concentration Unit Code Standard
LQSA(2) N N Num 8 Quantity Limit Standard
LQSC(2) N N Char 2 Quantity Limit Code
ELSD(2) N N Date 8 Modification Period Start Date (YYYYMMDD)
ELED(2) N N Date 8 Modification Period End Date (YYYYMMDD)
COLS(2) N N Char 3 Change Of Limits Code
CONP(2) N N Char I Contested Parameters
PLFN(2) N N Char 12 Limit File (Docket) Number
MV IO(3) Y N Char 3 Effluent Violation Code - Worst Violation
V IND(3) Y N Char I Violation Indicator
ENFI(3) V N Char I Enforcement Action Issued For DMR
NODI(3) N N Char I Reason For No Discharge
MQAV(3) N N Char 8 Average Quantity
MQMX(3) N N Char 8 Maximum Quantity
MCMN(3) N N Char 8 Minimum Concentration
MCAV(3) N N Char 8 Concentrauon Average
MCMX(3) N N Char 8 Maximum Concentration
VQAV(3) N N Num 5 Percent Over Limit - Quantity Average
VQMX(3) N N Num 5 Percent Over Limit - Quantity Maximum
VCMN(3) N N Num 5 Percent Under Limit - Concentration Minimum
VCAV(3) N N Num 5 Percent Over Limit - Concentration Average
VCMX(3) N N Num 5 Percent Over Limit - Concentration Maximum
VWCS(3) Y N Num 5 Highest Percent Violation
SNDE(3) V N Date 8 RNC Date For DMR (YYYYMMDD)
SRDE(3) V N Date 8 RNC Resolution Date (YYYYMMDD)
SNCE(3) Y N Char I RNC Detected
SRCE(3) Y N Char I RNC Resolved
DMRR(3) N N Date 8 Date DMR Received
DMDL(3) N N Num 2 Number of Days DMR was Late
C.14 RCR-RCRA In formation System Data Elements (9/96 )
Group Repeat Element Name index? Enforc Data Length Description
Record? (Yf N) Sens? Type
(V/S/N)
IDNUM(B) N ID V N Char 12 Handler Id Number (Minor Value)
HANDLER(B) N NAME N N Char 40 HandIer Name
C-44 IDEA User’s Guide October 22, 1996
-------
State Code/County Code
Location Street I
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
Eiustence Date (YYYYMMDD)
OfT Site Waste Receipt
Official Mail Street I
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-Cbs Requirements Violation Flag
Financial Requirements Violation Flag
Generator Landban Regulations Violation Flag
Treatment, Storage or Disposal (1’SD) Landban Regulations Vio-
lation Flag
Corrective Action Compliance Flag
Other TSD Regulations Violation Flag
Formal Enforcement Agreement Violation Flag
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 I
Contact Street Line 2
Contact City
Contact State
Contact Zip Code
Contact Address Code
Owner/Operator Sequence Number
Owner/Operator Indicator
Type Of Ownership
Owner/Operator Change Date (YYYYMMDD)
Owner/Operator Name
Group
Repeat Element Name
Record’
Data
Type
Length Description
Index? Enfore
(V/N) Sens?
(V/S/N)
V N
N N
N N
N N
V N
Y N
V N
V N
V N
Y N
V N
V N
Y N
V N
V N
Y N
V N
V N
V N
V N
V N
N N
N N
N N
N N
N N
N N
N N
N N
V N
N N
N N
N N
N N
N N
N N
V N
V N
Y N
V N
Y N
Y N
V N
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 I
Char I
Char I
Char I
Char I
Char I
Char I
Char 12
Char I
Char I
Date 8
Char 1
Char 30
Char 30
Char 25
Char 2
Num 5
Char I
Num 5
Num 5
Char I
Char I
Char I
Char I
Char I
Char I
Char I
Char I
Char I
CDE —
LOCST I
LOCST2
LCITY
LSTATE
LZI P
H REGN
H USJCEI
H USJCA
HUCAWR
HUPMTPR
HUPMTWR
HUPCLWR
HUPPCWR
HUTRAN
H U FU L
H U LAND
HUINCIN
H USTORT
HUSML
H UCESQG
XREFID
COREID
NOTIF
H EXDATE
HOFFSIT
MAI LSTI
MA! LST2
MCITY
MSTATE
M ZIP
LAN DTYP
LATD
LONG
LLSRC
H ACCESS
HOER
HTRR
HDGW
H DCL
H DFR
HGLB
H DLI3
HCAS
H DOT
H EN F
CPVIOL
VIOLQTR
INSPDAY
Y CONTFYP(K)
C LAST
CFIRST
CTITLE
CPHONE
CSTRTI
CSTRT2
CCITY
CSTATE
CZI P
CADD
V HCOSEQ(K)
COl ND
COTYPE
H C DATE
CONAME
CONTACT(B)
OWN ER(B)
V N Charl
V N Char!
V N Charl
V N Char I
V N Num2
V N Num5
V N Charl
N N Char 15
N N Char IS
N N Char 15
N N Char 10
N N Char 30
N N Char 30
N N Char 25
N N Char2
N N NumS
N N Charl
N N Num4
N N Char2
V N Char2
N N DateS
N N Char 40
Appendix C Data Elements in IDEA Shadow Files
C-45
-------
Group Repeat Element Name index? Enlorc Data Length Description
Record? (V/N) Sens? Type
(V/S/N)
COPHONE N N Char 10 Owner/Operator Phone
COSTRT N N Char 30 Owner/Operator Street
COCITY N N Char 25 Owner/Operator City
COSTATE N N Char 2 Owner/Operator State
ZIPCODE N N Num 5 Owner/Operator Zip Code
SIC(B) Y SICSEQ(K) N N Num 4 SIC Code Sequence Number
SICPR IM N N Char I SIC Code Primary Indicator
SICCODE V N Num 4 SIC Code
SICSRCE N N Char I SIC Code Source
SOURCE4B) Y SOURCE(K) V N Char I Source Of Information
RECDATE(K) V N Date 9 Receipt Date
WASTSTR(K) V N Num 4 Waste Stream Number
WASTCD(K) V N Char 4 Waste Code
WASTPRO(K) Y N Char 3 Waste Process
PROCESS(K) V N Char 3 Process Code
PROCSEQ(K) V N Num 2 Process Sequence Number
PROCATT(K) Y N Char 2 Process Amount Type
PROCUID(K) V N Char 10 Process Unit identifier
GEN(1) V N Char 2 Generator
TRANS(1) Y N Char I Transporter
TSD(i) V N Char I Treater/Storer/Disposer
BBL(1) Y N Char I Burner/Blender
HWF I(i) N N Char I Market To Burner indicator
HWF2(1) N N Char I Other Marketer indicator
HWF3(1) N N Char 1 Burner Indicator
OUOI(1) N N Char I Market To Burner
OUO2(l) N N Char 1 Other Marketer
OUO3(1) N N Char I Burner
SUO(1) N N Char I Specification Used Oil Fuel Marketer
UTILI(1) N N Char I Utility Boiler indicator
UTIL2(i) N N Char I Industrial Boiler Indicator
UTIL3(1) N N Char I industrial Furnace Indicator
AIR(1) N N Char I Air Transportation
RA 1L(i) N N Char I Rail Transportation
HIGHWAY(1) N N Char I Highway Transportation
WATER(1) N N Char I Water Transportation
OTHER(1) N N Char 20 Other Means Of Transportation
RCRADGE(1) N N Char 2 Generator RCRA Regulatory Status Description
RCRADTR(1) N N Char 2 Transporter RCRA Regulatory Status Desc
RCRADTS(1) N N Char 2 TSD RCRA Regulatory Status Desc
RCRADBB(1) N N Char 2 Burner/Blender RCRA Regulatory Status Dese
RCRASGE(1) N N Char I Generator RCRA Regulatory Status
RCRASTR(1) N N Char I Transporter RCRA Regulatory Status
RCRASTS(I) N N Char I TSD RCRA Regulatory Status
RCRASBH(1) N N Char I Burner/Blender RCRA Regulatory Status
UIC(1) N N Char I Underground injection Control Indicator
WAMOUNT(2) N N Num 8 Amount Of Waste
WAMTT(2) V N Num 8 Waste Amount in Tons
WUOM(2) N N Char I Unit Of Measure
WDATE42) N N Date 8 Waste Date (YYYYMMDD)
PROCCOM(5) N N Char I Process Commercial Indicator
PROCSTA(6) N N Char I Process Status
PROCUOM(6) N N Char I Process Unit Of Measure
PROCAMT(6) N N Num 8 Process Amount
PROCTU(6) N N Num 9 Process Total Number of Units
PDATE(6) N N Date 8 Process Date (YYYYMMDD)
PROCUTP(7) N N Char I Process Unit Group Type
PROCUCF(7) N N Num 9 Number of Units m Process Unit Group
PROCUAT(7) N N Num 8 Total Waste Capacity Associated With Unit Group
PROCUUM(7) N N Char I Process Unit Group Unit Of Measure
PROCREG(7) N N Char I Unit Regulatory Status (RCRA/State/Both)
INSTRUMT(B) Y INST(K) Y N Char I TypeOflnstrument
IAGCY(K) V N Char I Responsible Agency (EPA/State/Jomt)
IEDATE(K) Y N Date 8 Instrument Effective Date (YYYYMMDD)
ISTAT(K) V N Char I Legal Authority Code
CAREA(K) V N Num 4 Area Code
C-46 IDEA User’s Guide October 22, 1996
-------
Event Module
Event Code
Responsible Agency
Sequence Number
Instrument Issue Date (YYYYMMDD)
Instrument Revocation Date (YYYYMMDD)
Responsible Program (RCRA/CERCLA)
Area Description
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
SEPlEnforcement 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)
Event Module
Event Code
Responsible Agency
Event Sequence Number
Actual Date (YYYYMMDD)
Responsible Program (RCRA/CERCLA)
Event Status
Permit Sequence N umber
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
records 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
Group Repeat Element Name Index? Enforc
Data Length Description
Record?
(V/N)
Sens?
Type
(V/S/N)
ENFORCMT(B)
EVALUATN(B)
VIOLATN(B)
ORPHN(B)
PRMT SEQ(B)
IEMOD(K)
Y
N
Char 1
IECODE.(K)
Y
N
Char 5
IEAGCY(K)
Y
N
Char 1
ISEQ(K)
N
N
Num 4
IDATE(l)
N
N
Date S
IRDATE(1)
N
N
Date 8
IPROG(I)
N
N
Char 1
ADESC(3)
N
N
Char 40
IEADATE(4)
N
N
Date 8
IEPROG(4)
N
N
Char I
IEVSTAT(4)
N
N
Char 2
Y
CEENUM(K)
ENFAGN(K)
EDATE(K)
EAMTTYP(K)
MMCODE(K)
SEPSEQ(K)
Y
Y
Y
Y
V
N
S
S
S
S
S
S
Char 9
Char I
Date 8
Char 2
Char 3
Char 2
Y
V
V
ENFTYPE(1)
POLLPRE(2)
EPENAMT(4)
EVALNO(K)
EVALAGN(K)
EVALDTE(K)
EVALSEQ(K)
ETYPE(I)
EVAREA(2)
CESTAT(2)
CEMDESC(2)
CEVVKEY(K)
EKEY(K)
VENFKEY(K)
EKEYSEQ(K)
VAREA(I)
VDTEDET(I)
VCLASS(I)
VACFDTE(1)
VPRTY(I)
VSCHDTE(1)
EMOD(K)
ECODE(K)
EAGCY(K)
ESEQ(K)
EADATE
EPROG
EVSTAT
Y
Y
Y
Y
Y
V
V
Y
V
N
N
Y
V
V
N
V
Y
Y
Y
Y
N
Y
V
Y
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
N
N
N
N
N
N
N
Char 3
Char 3
Nuni 8
Char 9
Char I
Num 9
Num 4
Char 3
Char 3
Char 2
Char 40
Char 5
Char 10
Char 10
Num 4
Char 3
Date S
Char I
Date 8
Char I
Date 8
Char I
Char 5
Char I
Nuin 4
Date 8
Char I
Char 2
V
PSQN(K)
PECODE K)
PEAGV(K)
PESEQ(K)
UNITSEQ(K)
UNITNAM(K)
PUSEQ(K)
V
Y
Y
N
N
Y
N
N
N
N
N
N
N
N
Num 4
Char 5
Char I
Num 4
Num 4
Char 18
Num 3
PAPP(l)
PADATE(2)
PESTAT(2)
PSTAT
PUPROC(3)
PUPROCU(3)
PUDATE (3)
PCAP(3)
PUTOT(3)
COMMERC(3)
OPSTAT(3)
LEGSTAT(3)
N
N
V
Y
Y
V
N
N
N
N
V
Y
N
N
N
N
N
N
N
N
N
N
N
N
Char 12
Date 8
Char 2
Char 7
Char 3
Char I
Date 8
Num 8
Num 9
Char I
Char 2
Char 2
Appendix C Data Elements in IDEA Shadow Files
C-47
-------
Repeat Element Name
Record?
Y CTYPE(K)
CFY(K)
EVCODE(K)
CID(K)
CHIDNUM(K)
CKEY(K)
CUPDT(1)
CAGCY(2)
CEFFDT(2)
CACTDT(2)
REVNO(2)
CDESC(2)
CTOTQ1(2)
CTOTQ2(2)
CTOTQ3(2)
CTOTQ4(2)
C1’OTFY(2)
index? Enlore
(YIN) Sees?
( V/S/N )
Y N Char3
V N Char4
V N Char5
Y N Char 12
V N Char 12
V N Char 10
N N Date8
N N Char3
N N DateS
N N DateS
N N Num4
N N Char4O
N N Num4
N N Num4
N N Num4
N N Num4
N N Num4
C.15 SET-Site Enforcement Tracking System Data Elements (9/96 )
SETE(A)
PRP(B)
SETE.(A)
Repeat Element Name
Record?
N SITEID
N PRPCODE
N SITENM
AL IASNM
NPLFLAG
STREET
CITY
STATE
ZIP
EPAREG
LATD
LONG
N PRPREGN
PRPNAME
Y ADDRSEQ(K)
ADDRSEE
TITLE
STREET I
STRE E T2
STREET3
ADC ITY
ADSTATE
ADZIP
GNLDATE
SNLDATE
Index? Enforc
(V/N) Seas?
( V/S/N )
Y N Char 12
V N Char6
N N Char 40
N N Char 50
Y N Charl
N N Char 30
N N Char 25
Y N Char2
Y N Num5
V N Char2
N N Num4
N N Num4
Y N CharS
N N Char 50
N N Num4
N N Char 50
N N Char 50
N N Char 50
N N Char 50
N N Char 50
N N Char 25
Y N Char2
V N CharS
Y N DateS
Y N DateS
Site Id Number
Potentially Responsible Party Code
Site Name
Alias Name
National Priorities List (NPL) Flag
Site Street
Site City
Site State
Site Zip
EPA Region
Latitude
Longitude
PRP Region
PRP Name
Addressee Sequence Number
Addressee Name
Addressee Title
Streeti
Street2
Street3
City
State
Group
COMMITMT(B)
Data
Type
Length Descnpflon
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 N umber
Commitment Description
Commitment Total 1st Quarter
Commitment Total 2nd Quarter
Comnrmtrnent Total 3rd Quarter
Commitment Total 4th Quarter
Commitment Total Fiscal Year
Group
Data
Type
Length Deacnption
PRP(B)
ADDRESS(B)
Zip Code
General Notice Letter Date (YYYYMMDD)
Special Notice Letter Date (YYYYMMDD)
C-48 IDEA User’s Guide
October 22, 1996
-------
C.16 TRI-Toxic Chemical Release System Data Elements (9/96 )
TF ID(A)
DCNO(B)
FACL(A)
HFAC(A)
ACTV(B)
CH EM(B)
Repeat Element Name Index? Enforc
Record? (V/N) Seas?
(V/S/N)
Group
Data
Type
Length Description
S UBM ISS ION (A)
N
TFID
V
N
Char
15
TRIS Facility Identifier
N
DCNO
Y
N
Char
15
Document Control Number
N
FLAT
N
N
Num
5
Facility Latitude
LONG
N
N
Num
S
Facility Longitude
LOCN
V
N
Num
8
Latitude + Longitude
CSFC
Y
N
Num
5
State/County FIPS Code
Y
HSEQ(K)
N
N
Num
4
Historical Facility Sequence Number
HRPYR
Y
N
Date
4
Historical Location Reporting Year
1- IFRO
Y
N
Char
2
Historical Facility Region
HNME
N
N
Char
50
Historical Facility Name
SPNM
V
N
Char
50
Hietoncal Facility Name
HSTR
N
N
Char
40
Historical Facility Street
HCIT
Y
N
Char
25
Historical Facility City
HCNY
N
N
Char
25
Historical Facility County
HSTATE
Y
N
Char
2
Historical Facility State, Alpha Abbrev
HZIP
Y
N
Num
5
Historical Facility Zip, Digits 1-5
HZP2
Y
N
Nurn
4
Historical Facility Zip, Digits 6-9
V
SUBYEAR(K)
Y
N
Date
4
Reporting Year for the Submission
SUBSEQ(K)
Y
N
Num
2
Submission Sequence Number
SICD
Y
N
Num
4
SIC Code
SICIST
Y
N
Num
4
Most frequent SIC code, given reporting year
UICID
Y
N
Char
12
UIC Identification Number
RCRID
V
N
Char
12
RCRIS Handler Id
DUNSNUM
Y
N
Char
9
Dun & Bradstreet Number
NPDES
V
N
Char
9
NPDES Number
TECHNAM
N
N
Char
45
Technical Contact Name
TECHNUM
N
N
Char
10
Technical Contact Phone Number
V
AUCD(K)
Y
N
Char
2
Activity Use Code
N
RPYR
Y
N
Num
4
Reporting Year (YYYY)
RYSS
V
N
Char
3
Reporting Year + Submis on Status
STSI
V
N
Char
I
Submission Trade Secret Indicator
C1’Sl
Y
N
Char
I
Chemical Trade Secret Indicator
RFEF
N
N
Char
I
Reporting For Entire Facility
SUBS
V
N
Char
I
Submission Status
MAXC
N
N
Char
2
Maximum Amount of Chemical On-Site Code
TCID
Y
N
Char
9
TRIS Chemical Identifier
CRSN
Y
N
Num
9
Chemical Abstracts Service (CAS) Number
NAME
N
N
Char
70
Chemical Name
WMIN
N
N
Num
2
Waste Mm index
WMNA
N
N
Char
I
Waste Mu, Index NA
WMAC
N
N
Char
2
Waste Mm Action Code
MIXC
N
N
Char
70
Mixture Comp Identifier
WMCD
N
N
Char
2
Waste Mm Code
WMCY
Y
N
Num
13
Waste Mm Current Year Quantity
WMCN
N
N
Char
I
Waste Mm Current Year Quantity NA
WMPY
N
N
Num
13
Waste Mm Prior Year Quantity
WMPN
N
N
Char
I
Waste Mm Prior Year Quantity NA
PCTC
Y
N
Num
5
Waste Mm Percent Change
PCTN
N
N
Char
I
Waste Mm Percent Change NA
TREST
V
N
Num
11
Total Release Estimate
RMRLSQN
N
N
Num
13
Remedial Release Quantity
RMRLSNA
N
N
Char
I
Remedial Release Zero NA
RCYCACT
N
N
Num
6
Recycling Activity Index
RCYCANA
N
N
Char
I
Recycling Activity Index Zero NA
PPADATA
N
N
Char
I
Additional PPA Data Indicator
ENRGYON
N
N
Char
15
Energy Onsite Process Code
ENRGYCD
V
N
Char
3
Energy Onsite Process Code (for Retrieval)
RCYCLON
N
N
Char
15
Recycled Onsite Process Code
RCYCLCD
V
N
Char
3
Recycled Onsite Process Code (For Retrieval)
Y
SRDRCYC(K)
Y
N
Char
25
Source Release Reduction Activities
REL REDUC(B)
Appendix C Data Elements I l IDEA Shadow Files
C-49
-------
Repeat Element Name
Record?
CYRQ
CYRNA
PYRQ
PYRNA
FYRQ
FYRNA
SYRQ
SY RN A
Y RSEQ(K)
CREL
TEPA
ODIS
CBF I
TRNG
REST
RENA
REBC
PWI A
SPNA
STCD
LDCD
TRMT
RTRS
M REST
Y TSEQ(K)
M ETHODS
M ETH
WECD
RICT
SE1’R
TREE
TREN
OPID
TRST
Index? Enforc
(V/N) Sens?
( V/S/N )
N N Num13
N N Chari
N N NumI3
N N Chari
N N Numi3
N N Charl
N N Nuini3
N N Charl
Y N Num4
Y N Charl
N N Char 12
N N Char2
N N Char2
Y N Char2
Y N Nuin 11
N N Charl
N N Char2
N N Num5
N N Charl
N N Charl
N N Char3
Y N Char3
N N Charl
Y N Num ii
N N Num3
N N Char 31
Y N Char3
N N Char2
N N Char2
N N Char2
Y N Num5
N N Charl
N N Char2
N N Charl
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 N umber
Release Medium
Transfer EPA Id Number
Transfer Site Code
Controlled 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 N umber
Waste Treatment Method
Waste Treatment Method (for Retrieval)
Wastestream Code
Waste influent Concentration Code
Waste Sequence Treatment Indicator
Waste Treatment Efficiency Estimate
Waste Treatment Elliciency Estimate Na
Operating Data Indicator
Treatment Record Status
C.17 ZIP-Census Bureau’
s ZiD Code Data Elements (1196)
MINOR(B)
Z IPCODE(B)
N ZIP
N AREA
LAT
LONG
TYPE I
TYPE2
STCN I
STCN2
STCN3
Y NSEQ
NAME
N POP
M EDMALE
WHITEF
BLACKF
IN DIAN F
ASIAN F
OTHERF
H ISPTOT
Data
Type
Y N NumS
Y N Real 7
Y N Real 7
Y N Real 7
Y N Chari
Y N Chari
Y N Num5
Y N Num5
Y N Num5
N N Num2
V N Char 25
Y N Num7
Y N Nu m3
V N Real 4
Y N Real4
V N Real 4
Y N Real 4
Y N Real 4
Y N Num7
5 Digit Zip Code
Area in Square Miles of Zip Code
Latitude in Degrees
Longitude in Degrees
Type 1,2,3
Type 1,3,5
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 Hispamc Origin
Group
Data
Type
Length Description
RELEASE(B)
TREATMNT(B)
Group
Repeat Element Name Index? Enforc
Record? (V/N) Sens?
(V/S/N)
Length Description
NAME(S)
DEMOGRPH(B)
C-50 IDEA User’s Guide
October 22, 1996
-------
Group Repeat Element Name Index? Eaforv Data Length Description
Record? (V/N) Sens? Type
(V/S/N)
WHISPF Y N Real 4 Fraction, White, of Hispanic Origin
BHISPF Y N Real 4 Fraction, Black, of Hispanic Origin
OI-IISPF Y N Real 4 Fraction, Other, of Hispanic Origin
HHIBASE Y N Num 7 Household Income Base
HHILTI5 Y N Real 4 Fraction, Households with income Less Than 515K
J- 1H1 1524 Y N Real 4 Fraction, Households with income between 515K and $24,999
HI- 112534 Y N Real 4 Fraction, Households with Income between 525K and $34,999
HHI3549 Y N Real 4 Fraction, Households with Income between 535K and $49,999
HH 15074 Y N Real 4 Fraction, Households with Income between 550K and $74,999
HHIMT75 Y N Real 4 Fraction, Households with Income more than 575K
HHIMED Y N Num 7 Median Household income
HHIAVE Y N Num 7 Average Household Income
FIBASE Y N Nun 7 Family Income Base
FILTI5 Y N Real 4 Fraction, Families with Income Less Than 515K
Fl1524 Y N Real 4 Fraction, Families with Income between 515K and $24,999
Fl2534 Y N Real 4 Fraction, Families with Income between 525K and $34,999
F13549 Y N Real 4 Fraction, Families with Income between 535K and 549,999
FI5074 Y N Real 4 Fraction, Families with income between 550K and $74,999
FIGT75 Y N Real 4 Fraction, Families with Income more than $75K
FIMED Y N Num 7 Median Family Income
FIAVE V N Num 7 Average Family Income
PCI9O V N Num 7 1990 Per-Capita Income
URBPOPF Y N Real 4 Fraction, Urban Population
RULPOPF Y N Real 4 Fraction, Rural Population
NATBRNF V N Real 4 Fraction, Native Born
FRNBRNF Y N Real 4 Fraction, Foreign Born
EM FLOYD Y N Num 7 Total Employed
UNEMPLF Y N Real 4 Fraction, Unemployed
HISPF V N Real 4 Fraction, Hispanic
WHITF V N Real 4 Fraction, White, Non-Hispanic
MINTF Y N Real 4 Fraction, Minority
Appendix C Data Elements in IDEA Shadow Files C-51
-------
C-52 IDEA User’s Guide October 22, 1996
-------
Appendix D. Error Messages for the 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) 564-2475
Monday-Friday 9:00am to 5:00pm (eastern time)
INPUT/OUTPUT SPECIFICA TIONS.
ERROR: YOU MAY ONLY SPECIFY INPUT CRITERIA ONCE PER
QUERY.
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.”
ERROR: YOU MAY ONLY SPEOIFY OUTPUT CRITERIA ONCE PER
QUERY. -
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
-------
• ERROR; YOU MAY SPECIFY YOUR SECURITY LEVEL ONLY
BEFORE YOUR INPUT.
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.
ERROR YOU MUST ENTER INPUT CRITERIA
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.
ERROR: YOUR HIGH-LEVEL ITETI ;xxx:
IS INVALID.
Call IDEA User Support (see below
SECURITY SPECIFI A TIONS.
ERROR: YOU ARE NOT AUTH ORTZED FOR
THIS SECURITY
LEVEL.
.
Refer to Appendix A, Access and Security Procedures for IDEA, for information on
security and access procedures.
ERROR; YOU HAVE ENTERED AN INVALID SECURITY LEVEL.
Currently, IDEA supports four security levels: 1 through 4. One being the lowest
level of security access and four being the highest.
INPUT SPE IFJ A TIONS:
FRROR: YOU MUST SPECIFY LINKED” BEFORE YOUR
SELECTION EXPRESSIONS.
Refer to Chapter 8 for information on INPUT statements.
D-2 IDEA User’s Guide October 22, 1996
-------
ERROR: YOU MUST SPECIFY ‘ 1 NOr LiNKED” BEF RE YOUR
SE1..ECTION EXPRESSIONS.
Refer to Chapter 8 for information on INPUT statements.
ERROR: YOU MAY ONLY SPECIFY SELECT C 1TERIA ONCE PER
QUERY.
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.”
ERROR: INPUT OPTION ‘ XXX” IS INVALID.
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.
ERROR: YOU t4UST ENTER SEL T CRITERIA.
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.
ERROR: YOUR LIST OF EXPRESSIONS IS INC 1PLETE.
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.)
ERROR: YOUR PARENTHESES ARE IMBALANGED.
Each opening parenthesis must have a corresponding closing parenthesis, and visa-
versa.
Appendix D. Error Messages for the Keyword Interface D-3
-------
ERROR: YOUR UER\ IS TOO LONG. PLEASE CALL THE HELP
INE.
Contact IDEA User Support (see below).
VALUE SPEGIFKA TIONS.
ERROR: THERE IS AN INVALID APOSTROPHE IN YOUR VALUE
_IST.
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: THERE IS AN INVALID CHARACTER IN YOUR VALUE
.JST.
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.
ERROR: YOUR LIST OF VALUES IS INVALID
To correct this error, compare the indicated value list with the list of valid values for
the data element and change the list accordingly.
• ERROR: THERE IS NO VALUE BEFORE THE COMMA.
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.
ERROR: HERE IS NO VALUE BEFORE THE CLOSING
PARENTHESIS.
D-4 IDEA User’s Guide October 22, 1996
-------
Parentheses in IDEA keyword queries cannot stand alone. Refer to to Chapter 8
Chapter 8 for proper syntax.
ERROR: THERE IS 1W VALUE BEFORE THE CONNECTOR.
Refer to Chapter 8 for proper connector syntax.
ERROR: THE VALUE “XXX” MUST BE NO LONGER THAN XXX
CHARACTERS -
To correct this error limit the number of characters or contact IDEA User Support
(see below).
ERROR: THE VALUE ‘XXX” MUST BE BETWEEN U AND 32,757.
Limit the number of characters or contact IDEA User Support (see below).
ERROR: THE VALUE ‘XXX” MUST BE BETWEEN B AND
2,147.483,647.
Limit the number of characters or contact IDEA User Support (see below).
ERROR: THE VALUE “X XX” MUST BE BETWEEN 0 AND ‘XXX”.
Limit the number of characters or call IDEA User Support (see below).
ERROR: THE NUMBER: 1 ’XXX ” CONTAINS INVALID CHARAcTERS.
Refer to Appendix B or contact IDEA User Support (see below).
ERROR: THENUMBER “XXX ” IS TOO LONG.
Limit the number of characters or call IDEA User Support (see below 2 .
Appendix D. Error Messages for the Keyword Interface D-5
-------
ERROR: THE NUMBER “XXXi’ MUST BE GREATER-THAN OR
E UAL -TO 0.
Refer to Appendix B for valid data values or contact IDEA User Support (see
below).
ERROR: THE DATE “XXX’ IS INVALID.
Refer to Appendix B for valid date formats.
ERROR: THERE IS NO COMMA BETWEEN VALUES.
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:
• ERROR: OUTPUT OPTION “XXX” IS INVALID.
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.
ERROR: “XXX’ IS AN INVALID KEYWORD.
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.
ERROR: YOU MUST ENTER A REPORT NAME.
D-6 IDEA User’s Guide October 22, 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, 1B, 2, SUMMARY, and FINDUMP. For information on the syntax of a User
Specified Report, see Chapter 11
ERROR: YOU MAY SPECIFY ONL\ ONE DESTINATIOH PER
REPORT.
Refer to Chapter 8 for proper destination specifications.
DA TA BASE ID:
ERROR: THE DATABASE “XXX DOES NOT EXIST.
This message indicates that an invalid database ID is present. Chapter 8 lists the
current database ID’s.
ERROR: THE DATABASE NAME ‘XXX” IS LONGER THAN B
CHARACTERS.
Contact IDEA User Support (see below).
ERROR: THE DATABASE XXX’ CAt NOT BE ALLOCATED.
Contact IDEA User Support (see below).
DA TABASE.ELEMENT:
ERRO : ‘XXX ” IS INCORRECT. ORM MUST BE
“DATABASE. 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:
ERROR: THE ELEMENT NAME MAY BE ND MORE THAN
7-CHARPcTERS IN LENG1-.
Refer to Chapter 8 for proper data element syntax and Appendix C for data elements
used by IDEA.
ERROR: THE ELEMENT “XXX” IS NOT INDEXED.
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.
ERROR: OERR PROHIBITS ACCESS TO CERCLIS ELEMENT “XXX”.
Contact IDEA User Support (see below
ERROR: ELEMENT ‘XXX” IS NOT AN ITEM OR A FUNCTION.
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.
ERROR; ELEt 1ENT “XXX” DOES N0 EXIST IN DATABASE
“XXX”.
Check the list of elements and match them to the database you have specified, then
make the appropriate correction.
ERROR: ELEMENT “XXX” MAY MDI t E USED TO SEL:Ci
FACILITIES.
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
specffied element from the query to correct this error.
D-8 IDEA User’s Guide October 22, 1996
-------
OPERA TORS (EQ, NE, L T, ETC):
• ERROR: THE OPERAOR ,XXX IS INVALID.
Refer to Chapter 8 for a list of valid Boolean operators and the proper syntax associ-
ated with each.
EXPRESSION CONNECTORS (AND/OR):
ERROR: THE ONNECTOP ‘XXX” IS INVALID.
Refer to Chapter 8 for a list of valid Boolean connectors and the proper syntax asso-
ciated with each.
DES TINA TION KEYWORD:
ERROR: THE DESTIHATION MUST BE NO MORE
•8-CHA ACTERS LONG.
THAN
Refer to Chapter 8 or contact IDEA User
Support
(see
below).
BIN/BOX KEYWORD.
ERROR: THE BIN/BQX MUST BE EXACTLY 4 CHARAcTERS
LONG.
Refer to Chapter 8 for proper syntax or contact IDEA User Support (see below).
JCL OVERRIDE:
ERROR: THE BATASET “XXX ” WAS SPECIFIED AS “NEW” BUT
ALREADY EXISTS.
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.
ERROR: .E THE DATASET W t ’ WAS SPECIFIED AS OI..D OR
SHR> ’ BUT DOES NOT EXIST.
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.
ERROR: EACH DATASET MAY BE SPECIFIED ONLY ONCE PER
QUER ’.
Refer to Chapter 8 for proper syntax.
ERROR: NO JOB CARD WAS FOUND DOWN BELOW.
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:
ERROR: NO MATCHING dci STATEMENT WAS FOLND DOWN
BELOW.
If you write the keyword dd after either PRINT or DATASE1, 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.
ERROR: THE KEYWORD ‘dd” MUST BE FOLLOWED BY A
ddNAME.
If you write the keyword dd after either PRINT or DAIASET, 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-1O IDEA User’s Guide October 22, 1996
-------
ERROR YOU NUST ENTER E:THER A DATASET NAME OR A
ddNANIE.
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) 564-2475
Monday-Friday 9:00am to 5:00pm (eastern time)
Appendix D. Error Messages for the Keyword Interface D-11
-------
D-12 IDEA User’s Guide October 22, 1996
-------
Appendix E. The Structure of the IDEA Shadow Databases
E.1 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 vanes 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
lmes 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 mmor levels can
then occur either many times (a “repeating” record), or only once (a “non-repeating”
record). This is agam shown by havmg 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 mto three categories:
1. The AFS, ERN, FF1, NCD, PCS, SET, and TRI databases are all stru ctured
similarly m 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, accordmg 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
m 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 compnsed of repeating records, the data elements shown in the diagrams,
called the “keyed” elements for the group, will umquely 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 compnse a record. Some elements are not required fields in the
source databases, and hence could be blank m 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 “offsprmg”, and not to stack otherwise.
For example, in the Instrument group m 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 Authonty 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 JEMOD, 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 October 22. 1996
-------
AFS ldenmier
AFSID
I ___
Source Plant Historical
Compliance
HMONTH
11
Air Program
APC1 ASh
Program Histoncall Pollutant Actions
Compliance PI AP DIAl
HDT I ACSEQ
Figure E- 1. AFS Database Skeleton
Block Group
STATE
COUNTY
TRCTBNA
______ I I ____ _____
Demographics Number of Number Of Houslngj Fraction of Fraction of
Households Persons Households Poisons
Figure E-2. CBG Database Skeleton
Appendix E The Structure of the IDEA Shadow Databases E-3
-------
Figure E-3. CRM Database Skeleton
Responsible Office
RSOF
Case Number
CSNO
I r rk __ __ __ __ ___ __
Case Laws Pollutant olaVon Plaintiff Intervenor Defendant Amendment Comment
LAWS POLL Type PLTF INTV DFNM ANUM PGNM
SECT V1OT LNNM
Figure E-4. DCK Database Skeleton
E-4 IDEA User’s Guide
October 22, 1996
-------
State
DUNS Number
DCNO
Company
Figure F-S. DUN Database Skeleton
Material
Spilled
MTRLSEQ
Figure E-6. ERN Database Skeleton
Discharge
DOWNID
Report Date and Time
DTRPT TMRPT OWNID
Appendix E The Structure of the IDEA Shadow Databases
E5
-------
Figure E-7. FF1 Database Skeleton
Stated
EPA Identifier
EPID
Identification Information
SRCE SRID
SRI DSEQ
Figure E-8. FIN Database Skeleton
E-6 IDEA User’s Guide
October 22, 1996
-------
Responsible Office
RSOF
rk
Case Number
CSNO
Cesel Pollutant Law CFR Relief Basis Law Standards Continuing PrerequisIte Proposed CaseStatus Faolhty
POLL LAW CFRT Sought BLAW Which Apply Viøl Page EnforcAction Remedy Comments Information
SECT CFRS RLFS BACT SDWAPG CRVLPG PEFAPG PRRMPG CSCMPG FCINPG
SDWALN CRVLLN PEFALN PRRMLN CSCMLN FCINLN
Figure E-9. LST Database Skeleton
Appendix E The Structure of the IDEA Shadow Databases E-7
-------
NCDB Identifier
NCDBID
__ I
Ref errall Actions Terms Grant
_______ TERMSEQ
Sample Number
SAM PS
Case Multiple
Sample Actions
ACTNID
Related Optional Debt
Activity Info
REUTEM OPT YPE
2. Violation History
HSTDT HSTEVNT
Figure E-l1. OSH Database Skeleton
ICOMMNI Identification lnspectlon/
Information Import
NAMESEQ
r
Figure E- 10. NCD Database Skeleton
Establishment
ESTABST ESTABNR
rt
ISTEMI
Inspection Activit
ACTIVTY I
r
1.
Violations Records
Violations
VIOLKEY
+ rh rh
Accidents I Adrninistra ve Payments I
ACCITEMI IPAYTIPE
ADMTYPE I PAYDT I
ADMDT 1 I
E-8 IDEA User’s Guide
October 22, 1996
-------
Ii NPDES identifier ii
NPDES
__ __ I _____ I __ __
I Pernu t I I Historical I I Preb’ealment I Inspectiens (IN) Records Pervnrt I Compliance I Enforcement I
Faulty ( PF) I Compliance I Performance I i. PCIIAudft ReCOrdS Event ( PE ) Schedule (CS) Actions (EA)
HQRTR Summary ( SP)I Violation I ENAC
________ INSPDTE INSPTYP I
VCSN VDCD I
2. Inspection cvEv cvio I ENDT
INSPCOD CVDT
3. Inspection Schedule
SIDT
Number
DSCHJ
Effluents ( EF) Records
I Pipe Schedule
RPTDSGR PIPESET
2 Pipe Limits
LMTTYPE PARAMTR
MONLOCN SEASON
MODNUM
3 Pipe Measurements
MVDT
Figure E- 12. PCS Database Skeleton
Appendix E The Structure of the IDEA Shadow Databases E-9
-------
di di Hi
Plendlerl Contact Owner SIC Code
cowiri HCOSEQ SICSEO
I Source
SOURCE
RECDATE
2 te
wAS l.grR
cwce Records
3 waste
Code
SOURCE
WASTSTR
WASTCD
Hinder Id Number
ID
5 FacIlity
Process
SOURCE
PROCESS
PROCSEQ
6 Process
Nnoa
PROCAT
7 Process
Unit Group
PROCUID
4 waste
SOURCE
WASTSTR
WASTPRC
rh ______ d i
Evaluabon Records I I I
IlEvaliwbonI2EvaJrat}onj ______________II 8aODI
Are s I ______ 1 ECODE I
I EVALNO f EVAU IO I I2 . 0 n I 3 d iIEAGCY I
Unk I i ESEQ 1
EVALAGN EVALAGN VENFKEY
p EVALDTE 1 EVALSEQ I ervseo
4
lnt erd Raad .
I Itnent
INST LAGCY IEDATE
2 Legal I 3 lnsbumsnt
— I Ares
ISTAT CAREA
Athon Event
I ISIOD IECODE
d i Hi
Vioblion Records PermIt Sequenoe
I VIolatIon Data Records
CEvvIcEY 1 Permit
PSON
2 Event Acbvdy
PECOOF PE V
PESED
3 Process
Unit Groups
UPIIIBEQ UN PtAME
PUSEC
±
Ut
Ento .e.nunt Records
1. Enforcement Kay
Dab Records
EENUM ENFAGN
EDATE
2.6FF! 13 Muldmedle 4 Penalty
MUealOn Action Data
Data MMCODE E.AMTTYP
SEPSEQ
Cornmllrnatd Records
1. Ccou ,iltirMiI
CTYPE ccv
2. AdMty Tracks
and Evsnb
EVCODE OD
3 Activity Track Link
HIDNUM GKEY
Figure E- 13. RCR Database Skeleton
Figure E- 14. SET Database Skeleton
E-1O IDEA User’s GUIde
October 22, 1996
-------
TRIS Facility Identifier
TFID
__ rk
Facility Histoncal Yearly Submission
LatlLorig Facility Data Records
HSEQ SUBYEAR
SUBSEQ
11
Document Number
DCNO
Activity Use Code IChemica Source Release Release Treatment
AUCD Reduction Activity RSEQ TSEQ
SRDRCYC
Figure E- 15. TRI Database Skeleton
ZIP Code
ZIP
I r1i I
ZIP Code Names Demographics
Infom ab j NSEO
Figure E-16. ZI Database Skeleton
Appendix E The Structure of the IDEA Shadow Databases E-11
-------
E.2 How the underlyi,tg 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 facili-
ties with those having FFIS compliance status FFI.CPST== ESDF.
EDIT ---- BWWA O36.QUERY.SPECS(FFITEST) COLUMNS :Ø i 72
COMMAND SCROLL === HALF
***** ************* .************** TOP OF DATA ** ** ***.**
0-39001 QUTPIIT REPORT DL OUNT
000002 DETAIL LINE
009003 FIN.EP ID
000004 FIN.FZIP
009905 FFI.FFID
000006 FFI.ZIPC
00990! FF1 .PRJN
008008 FF1 .PMED
• 098089 FFLcPST
• 098010 INPUT LINKED SELECT
o - 3 9 0ii (FIN.FZIP = 2122C
000012 AND
0-38013 FFLPMED = CA
098014 AND
090915 FFI.CPST = ESDF
******.*k**************************.:BOTTOM OF DATA * ***
Figure E- 17. Select Criteria consulting two databases
Recall in Chapter 11, IDEA User-spec fled Reports, that the data elements in the
IDEA shadow databases can be on one of four levels. (See Table E-J.) 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 FF1, in the same group.
E-12 IDEA User’s Guide October 22, 1996
-------
Table E-l. Levels of Hierarchy in IDEA Shadow Databases
Level
Descnption
1
Major-valued, Non-repeating Group
2
Major-valued, Repeatmg Group
3
Minor-valued, Non-repeating Group
4
Minor-valued, Repeating Group
Because we are consulting more than one database when we AND the first two cn-
tena, IDEA must combine these cntena 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 cntena. When these facilities are then ANDed with the
facilities havmg comphance status FFI.CPST= ESDF, this will also be done at the
facility level.
The User-specified Report (USR) generated by this query is shown m Figure E-18.
Two facilities met our query critena. Notice that the level of each data element is
prmted out in the fourth column in the table at the top of the USR.
Appendix E The Structure of the IDEA Shadow Databases E-13
-------
BROWSE Report .ADHOC--- - Comp Iete- - - MAX 990037 LINE 90009900 O.L 001 080
CO 4AND
Issue coimiand 1NTO to print, or SAVE to save to dataset.
TOP OF DATA
ILS. ENVIRONMENTAL PROTECTION AOEUCY 10/20/94
ENFORCBIENT CONFIDENTIAL FOR EPA INTERNAL USE ONLY
INTEGRATE.D DATA FACI LITY-USER SPECIFIED REPORT ULCOUNT
REPORT FORMAT
# 0010 ELEMENT LEV LEN DIS- INTERNAL SORT TAL/ DESCRIPTION
NAME EL GIN PLACEMENT LEN PUS A/D TOT
3. FIN EPI .. 3 12 1 12 1 EPA- ID
2 FIN FLIP 4 7 14 4 13 ZIP-CODE
3 FF.I FF10 1 12 22 12 17: FFI:D
4 FF1 IIP.C. i 10 35 4 29: ZIP-0 0 0E
5 FF1 PRIM 3 10 46 18 33.: PROiECT -N 4BER
6 FF1 P 3 7 57 2 43 MEDIA
7 FF1 PST” 3 7 65 4 45 cOMPLIANCE-STATUS
U.S. ENVIRONMENTAL PROTECTION AGENCY :10/20/94 Page
ENFO CB4ENT CONFIDENTIAL FOR EPA INTERNAL USE ONLY
INTEGRATED DATA FACILITY-USER SPECIFI€D ::RE PORT OLCOUNT
FIN FIN FF1 FF1 FF1 FF1: FF 1
EPID FZIP FF10 ZIPC PRJN PMED CPST
M 00023501023 .21220 MD-572825901 21220 AF-122A SF SDF
21220
:AF-. 1229 SF OTHR
P3MS-IRP 1 C ESOP
PJM 5091533 NE OTNR
PJMSS5ZOEi1 CW ESDP
PJM 5852041 CA ESRO
PJMS999549 1 C ESDE
M04470900551 21220 MD-470Bt flJLTi . 2122 P93LZZ9348 TS ESDF
21220
MD-470 0 00551 21220 P83ZZZO077 TS OTHR
P93ZZZ 3078 TS ESRO
P03ZZZ 024 CA .ESDP
nd f.
BOTTOM OF DATA
Figure F-IS. User-specified Report--Two facilities
If, however, we change line 11 in Figure E-17 to be FF1.ZIPC= 21220, we are no
longer consulting two databases in our query. See Figure E-19.) FFI.ZIPC is a
level 1 data element in FF1.
E-14 IDEA User’s Guide October 22. 1996
-------
EDIT ---- BW A036.QUERY.SPECS(FFITESD - 0LUMNS 001 072
COM ND ===> SCROLL == HALF
****** **** * **********A**** TOP OF DATA
080001 OUTPUT REPORT DL OUNT
088002 DETAIL LINE
008003 FIN. EPID
008004 FIN.FZIP
088005 FFI.FFID
000006 FFI.ZIPC
080007 FFI.PRJN
088008 FFLPMED
080009 FFLDPST
000010 INPUT LIP4KED SELECT
08801.1 (FFI.ZIPC = 21220
088012 AND
080013 FFLPMED = CA)
008014 AND
000015 FFLCPST = ESDF
****** ****** **********t*** ***** BOTTOM OF DATA *********•*•****** ******* *
Figure E- 19. 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 FFI.ZIPC’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-19 are shown below. Note that the second
facility in Figure E-18 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-15
-------
8ROW SE - Report: ADHOC---- Complete--- MAX 8O O32 LINE 800 0O OL Gal 000
COMMAND 2=2>
Issue coniiiand NUNTO t print,. r SAVE to save to dataset.
TOP OF DATA ******** ***********-**************
U .S. ENVIRONMENTAL PROTECTION AGENCY 1O/20/ 4
ENFORCEMENT CONFIDENTIAL - FOR EPA INTERNAL USE ONLY
INTEGRATED DATA FACILITY-USER SPECIFIED REPORT OLCOUNT
REPORT FORMAT
• # 0010 ELEMENT LEV LEN OhS- INTERNAL SORT TAL/ DESCRIPTION
NAME EL 0TH PLACEMENT LEN P05 AfD TOT
1 FIN EPID 3 12 1 12 1 EPA-ID
2 FIN FZIP 4 7 14 4 13 ZIP-CODE
3 FF1 FF10 1 12 22 12 17 FF10:
4 FF1 ZIPC I 10 35 4 : 29 ZIP-CODE
5 FF1 PRJN : 10 46 10 33 PROJECT-NUMBER
§ FF1 PMED 3 7 57 2 43 MEDIA
7 FF.I GPST 3 7 65 4 45 COMPLIANCE-STATUS
u.S. ENVIRONMENTAL PROTECTION AGENCY 10f20/94 Page 1
ENFORCEMENT CONFIDEN IAL - FOR EPA INTERNAL USE ONLY
INTEGRATED DATA FACI LITY-USER SPECIFIED REPORT OLCOUNT
FIN F IN FF1 EFI FF1 FF1 FF1
EPIC FZIP FF10 .ZIPC PRJN PMED CPST
M0DD83501023 2122D MD-5728259$i 21220 AF-122A SF ESOF
21220
AF-1228 SF OTHR
PJMS—IRP RO ESOP:
PJ4S001533 NE OTMR
PJMSO520 0 I CW ESOP
P3MS052041 CA ESRO
PJNS909549 RC ESDF
nd of report
*********k**** ***** ******** * BOTTO 1 OF DATA **** **
Figure E-20. 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-21.) Note that changing this
order makes a difference even when both logical connectors are AND!
E-16 IDEA User’s Guide October 22. 1996
-------
. EDIT ---- 8WWA036.QUERY.SPECS(FFTEST) -• - COLUMNS O )3 G72
COMMAND ===> SCROLL ===> HALr
****** TOP OF DATA
008001 OUTPUT REPORT DL OUNT
080t302 DETAIL LINE •
. oee o3 FIN..EPID
. 088004 FIN.FZIP
l 889O5 FF1 .FFID
OO8 O6 FFI.ZIPC
. OO&J07 FFI.PRJN
009008 FFI.PMED
. OGOBOQ FFI.CPST
: INPUT LINKED SELECT
OE OO1i FFI..ZIPC = 2!22
•e90012 AND
:OO(-) ji3 (FF.PMED = CA
080B14 AND
: OOt3 13 FFI.CPST = ESOF)
****** *********** ***************± BOTTOM OF DATA ;********************** *** *
Figure E-2 1. 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- 18 , no facilities meet the combination of these two
criteria, so as a result, we get the following message:
QUERY STATUS SCREEN
COMMAND ===>
I1:5 3:42.e7 - U Facilities selected and in FINDS
Counts (percentages), by database, of facilities selected but
excluded because they were not. present in FINDS:
: F)( B’
Press ENTER to continue
Figure E-22. Query Status Screen--No facilties
Appendix E. The Structure ofthe IDEA Shadow Databases E-17
-------
E-18 IDEA User’s Guide October 22, 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.1 Accessing the User’s Guide in Bookmana ’er
To view the IDEA User’s Guide online, first type books at any Command prompt in
IDEA and press .
IDEA Help Menu
COMMAND == books SCROLL == SR
• Welcome To *** *** x** **t**
* *
* 1111111 000DD £EEEEE AAAA *
* I D U :E A A *
I D C EEE.E AAAAAA
I 0 U E A A
* 111:111 000DD EEEEEE A A
*
* Enter one of the following on the CO*1AND line *
* *
* 0 - Database Status H - Helpline Info U - User Documentation
* Or, enter the name of tt e NEWS ALERT you wish to read, or just *
* press ENTER to continue with IDEA. *
Scroll down for more ******************** **** ********************** ***** *****
@ALERTOI 959822.1525 About IDEA News Alerts... PQK
@ISPF 960126.1811 ISPF v.4.1- Effects on IDEAUsers P0K
CENSUS 960221.1331 I0€A t s new Zip Code (ZIP) database PQK
ER3AN96 960221.1322 New CE CLIS Data Elements (added Jan. 96) PQK
ERNS 960126.1814 Accessing ERNS data through IDEA PQK
KERMIT 960126.1138 Downloading IDEA Reports :Using KERMIT P K
Figure F-i. The books command
The EPA SOFTCOPY LIBRARY MAIN PANEL will appear.
Appendix F. Accessing the User’s Guide Online F-I
-------
- T - EPA SOFTCOPV LIBRARY MAIN
PANEL
-
SELECT ION
= = >
1
• ENY - Environmental Bookshelves •
•
2
Af*t .- Administrative Bookshelves
.
sv • Computer System Bookshelves
..
C
CAT
-
Softcopy Catalog
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.
Books View Options Help
Cormiand ===> ________________________________________________ SCROLL ==z> PAGE
Booksheff List
Shelves I to 10 of 10
Shelf Name Description
— AWPD Office Of Water AWPD Documentation.
— EN-EDSS Enforcement Document SoftCopy System.
— EN_IDEAS Enforcement * ** CROSS MEDIA SOFUOPY SHELF
— OECA Integrated Data for Enforcement Analysis Documentation
-—. OECA-PCS Permit Compliance System (PUS ) User Documentation
— OECATEST Enforcement and compliamce documentation in development
-— OS—RCRIS Office Of Solid Waste R RIS Documentation.
— OW-AWPO Office Of Water AWPO Documentation.
—— OW-NPS Office Of Water NonPoint Source.
— OVTEST Office of Water documentation in development
Figure F-3. Environmental Bookshelves
F-2 IDEA User’s Guide October 22, 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 bookshelfwhere the online version ofthe User’s Guide resides,
down to the OECA bookshe1f type an S next to it, and press < Enter > . The
ENFORID bookshelf(where all IDEA bookmanager documents reside) will appear.
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.
Books View Search Group Options Help
Coninand __________ ____________________________________ SLkOLL ===> PAGE
ENFOR:D Bookshelf
Books 1 to 2 of 2
Book Name Book Title Date
— COURSE Introduction to IDEA Systems Fundan ntals 95/ 03/28
— IDEAUG IDEA User’s Guide 95/10/23
Figure F-4. The IDEA Bookshelf
To view the Guide online, down to the IDEA User’s Guide, type an S next
to it. and press . The table of contents of the IDEA User’s Guide will
appear.
Appendix F. Accessing the User’s Guide Online F-3
-------
Books GoTo Search Notes Services Options Help
Cormiand === __________________________________________________ SCROLL ===> CSR
CONTENTS Ta le of Con:erits
Topic lines 1 to 17 of 242
TITLE Title Page
EDITION Edition Notice
CONTENTS Tab le of Oontents
TABLES Tables
FIGURES Figures
1.0 Chapter 1. Introduction
1.1 backg ’ound of the IDEA System
1.2 Purpose of tne Users Guide
Sumary
2.0 Chapter 2. iDEA: What it Does & How t Works
2.1 What is a Query?
2.2 The Data Accessed by IDEA
2.3 How IDEA Processes Queries
2.3.: Initial Fac lity Select on
2.3.2 Integrati n Process
2.3.3 Query Status
2.3.3.1 Linked Queries
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 and
to scroll through the Table of Contents, place your cursor on the section
number, and press . 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 ,
you will “jump” to the section referenced.
When you are fmished viewing the User’s Guide, and wish to return to IDEA, press
PF3. A popup window wifi ask you if you wish to leave a bookmark. Type 3 (so as
not to leave a bookmark) and press . You will return to the ENFORID
bookshelf’: Press again. A popup window wifi ask if you want to close the
bookshelf Press to close the bookshelf. Your will return to the list of
Environmental bookshelves. Press ’, and then , again. Finally,
press to exit bookmanager and return to IDEA.
F-4 IDEA User’s Guide October 22, 1996
-------
F.2 Printinj’ Additional Copies 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 . An ISPF panel, with several
prefomatted documents to choose from, will appear.
Preformatted D&cuments -
COMMAND === SCROLL==> PAGE
Select a file to P - Print or B -View the softcopy version
— 0E A IDEA :Us r ’s Guide
NDPD Gu de to N C Services
ETSD Disaster Recovery Manual (restricted)
* ETSD Revisions to the Disaster Recovery nuai (restricted)
— :0W DFLOW User s Manual
— OW Mapping and Data Display Manager (MDDM) Users Guide
— OW Environmental Display Manager (EDDM) Users Guide
OW GETDLG User 1 s guide
— OW GETSITES User 1 s Guide
OW Documentation for “WQAB IFDP1..OT”
— OW WQAB Data Element List for Environmental Databases
— OW Features of the Facilities Reporting File Database
— .0W Attachment 8-Example infonnation of Cataloging Unit 81888105
— .0W REACH File Management System RFMS) User’s Guide
— OW RF3 Mapping and Data Display Manager (MDDM) User’s Guide
OW Technical Description of the REACH File
— OW REACH Pollutant Assessment User’s Guide
Figure F-6. Documents available for printing
down to the IDEA User’s Guide, type a P next to it, and press .
The EPA PRINT ROUTING SCREEN will appear.
Appendix F. Accessing the User’s Guide Online F-5
-------
- EPA Print Routing *
OPTIOr;
Be sure the information below is correct then press enter to
print DECA IDEA Use ’ ’s Guide
from dataset JAFP.IDEA.
If you don’t want, to print, press PF3.
• Printer == => (R90 = 3825 at RTP,NC)
• or n ======= S (S=Standaru, 3=3 hole)
Name ===== >
Address ===
Bui din ‘ :.. . .
BIN === > .. .i. .. “ ‘:. . ... “
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 UserID).
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 when you are finished. In the upper-right corner, in should say that
the document has been “SENT TO PRINTER.” Press to return to IDEA.
F-6 IDEA User’s Guide October 22, 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-
mathd 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 retneve any facility that ful-
fills the first criterion AND the second cntenon
Bin This four-character code of the form MUID
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
mdicate express mail) ULD 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 cntenon AND the second criterion
OR tells IDEA to retneve 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 withm
a SELECT statement m 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, pnnt, 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 honzontally 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 A group of query criteria There are six
categones (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-
lowmg screens INPUT LIBRARY SELECTION
SCREEN, MEMBER LIST SCREEN, EDIT
SCREEN, NAME SELECTION MENU SCREEN,
QUERY STATUS SCREEN, and BROWSE
SCREEN
Comments In 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 havmg the same ultimate
Glossary X-1
-------
parent number m the Dim & Bradstreet Marketing
Index.
County Code A five-character FIPS 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 m your SELECT
statement. To refer to a database in a SELECT
statement, you must use the 3-character abbrevi-
ation for it:
AFS =
AFS
CEKCLIS =
CER
DOCKET
= DCK
DUNS
= DUN
ERNS = ERN
FF IS =
FF1
FINDS
= FIN
LST = LST
NCDB
= NCD
OS}JA
= OSH
PCS = PCS
RCRJS
= RCR
SETS =
SET
TRIS = TRI
Refer to Appendix B, “Database Descriptions” on
page B-I 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 critena in the pop-up windows for each cate-
gory In the Keyword Interface, they are referred
to by name after the database abbreviation m the
SELECT statement For a list of the data elements
accessed by IDEA, refer to Appendix C, “Data Ele-
ni.ents in IDEA Shadow Files” on page C- /
Data values are the actual values that are stored for
each mstance 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 critenon 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
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
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 pnnter 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
Prmtouts 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 Tnangle Park (RTP), 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 Umversal Nuinbenng System
assigned and maintained by Dun & Bradstreet Mar-
keting Index (Office of Information Resources
Management)
X-2 IDEA User’s Guide
October 22, 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 estabhshments Digits one
through eight are machine-generated and assigned
The ninth digit is a check digit which is instru-
mental in catchmg input errors
Edit Screen An IDEA screen identical to the edit
screen in ISPF, this display allows you to wnte and
edit Keyword Interface quenes
Element. See Data Element.
Enforcement One of six information categones 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 (FINDS) 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 categones for building
quenes 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
(FMFL4) A Presidential report submitted to
Congress in FY 1990 that cited the need to inte-
grate factual comphance 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)
FWRA Federal Insecticide, Fungicide, and
Rodenticide Act
FIMAS Prompt The Facility Impact Momtormg
and Analysis System Identification prompt occurs
on the EPA2 TSO/E LOGON SCREEN and
should be completed with the four-character code,
LESYP.
FINDS Facility Index System (Office of informa-
tion Resources Management) See also Facility
Index System
FMFIA See Federal Managers Financial Integrity
Act
GAO. General Accountmg Ofilce
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 typmg GO MeiiuA 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 retneve 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 Pnonty Violator
Glossary X-3
-------
IDEA. Integrated Data for Enforcement Analysis
(Office of Compliance)
1G. 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
mdustiy 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 mput you want
for the query (Linked and/or Nonlmked) and the
report format (1A, 1B, 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
hbraiy.
Integrated Data for Enforcement Analysis
(IDEA) This system, the subject of this manual,
provides two interfaces that allow the user to
retrieve information from (m most cases) copies of
fourteen EPA data systems in mtegrated 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 quenes in the Keyword
Interface EDIT SCREEN
JA Judicial Action
JCL Job Control Language
Keyword Interface The more complicated and
flexible of the two mterfaces available m the IDEA
system The Keyword Interface allows you access
to the GO Names utthty 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 estabhshing a new library),
SHR (shared -- the default setting winch will allow
other users to access the library), and OLD (which
provides exdusive 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 combmed 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 m 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
October 22, 1996
-------
area - ranging from the size of an EPA region to
the area covered by a ZIP code.
LS1’ Contractor Listmg Docket (Office of Com-
phance)
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 like 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 hbrary. 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-like pop-up
windows These windows allow you to choose en-
tena 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 utility. This screen, accessible through the
Keyword Interface, allows you to perform a search
for facilities by name and/or location. Moreover,
you can specify a Dun & Bradstreet corporate
profile on the facilities your search retneves
National Computer Center (NCC) The
mainframe computer center located in Research
Tnangle Park (RTP), NC that provides EPA with
support for scientific and administrative applica-
tions NCC serves EPA customers and other quali-
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 followmg telephone
numbers
inside NC 919 541-7862
NC Noncompher
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 Compliance Database (Office of
Comphance)
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 library status option for a new library.
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 Cnteria chosen from the
pop-up window for this category will direct IDEA
to search for facilities according to their comphance
record
Noncomplier A facility whose status is not in
compliance with EPA laws and/or regulations
NONLINKED Nonintegrated queries in Non-
linked queries, IDEA does not attempt to integrate
facility data Instead of using FINDS as a cross-
reference mechanism, these quenes search and
retneve data from (for the most part) copies of the
program office databases This keyword should
appear in the INPUT statement.
Nonlinked Data Data retneved as the result of a
nonhnked search See Non/inked
Nonlinked Linked Data See Linked Nonlinked
NCC User Support
from outside NC
1 800 334-241)5
NOT NOT tells IDEA to choose any facility that
does not meet the cntenon this word modifies
Glossary X-5
-------
NOV Notice of Violation
NPDES. (pronounced ‘Nip-dees’) National Pol-
lution Discharge Elimination System
NFL National Priorities List (under CERCLA)
NSPS New Source Performance Standard
OARM Office of Administration and Resources
Management
OC. Office of Comphance.
OECA. Office of Enforcement and Compliance
Assurance.
OERM. Office of Information Resources Manage-
ment
OLD. A library status option that allows the user
exdusive access to the hbraiy 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 cntenon
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 Corn-
pliance).
PDF Productivity Development Facility.
PF Key See Program Function Key
Pointers or Links For each facility in FINDS,
there are pomters 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 categones 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, Noncomphance, Enforcement,
or Facility Status) or a query management option
(such as Run Query, Clear Query, Save Query, or
Retneve 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
PR? 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 m the
Menu Interface that appears after you select
Retrieve Query This screen lists all the queries
that you have saved m 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
October 22, 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
Sohd Waste and Emergency Response).
REPORT A keyword that specifies the query
report format (either a standard report, or user-
specified) Jt must follow the OUTPUT statement
Report Format The format of the data retrieved
by IDEA on facilities selected m accordance with
the query critena There are four standard report
formats currently available in IDEA. IA, 1B, 2,
and SUMMARY
SHR can be designated at the LIBRARY
STATUS prompt on the INPUT LIBRARY
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 defined in the Standard Industrial Classifica-
tion Manual pubhshed by 0MB (Office of Manage-
ment and Budget)
Significant Noncomplier A facility that is noted as
significantly out of compliance with EPA laws
andjor regulations
SIP, State Implementation Plan.
SNA Gateway System Network Architecture -- a
communications access port to the mainframe
Retrieve Query A Menu Interface option that
allows you to recall a previously saved query.
RTI’ Research Tnangle 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
STA TUS 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
SNC (pronounced ‘snick’) Significant
Noncompher
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 Tnchloroethylene
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 link to NCC
Till 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 II) A unique identification number assigned
Control Act. to each NCC user If you are an EPA employee,
you can obtain a user ID from your ADP Coordi-
TSD. Treatment, Storage, and Disposal (m 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-miss’) Time Sharing offered)
Services Management System
X-8 IDEA User’s Guide October 22, 1996
-------
Index
A
Accessmg IDEA 3-2
Access pohcy & procedures A-i, A-2
EPA Contractor Employees A- 10
EPA Office of Enforcement and Compliance
Assurance Employees A-9
EPA Program Office Employees A-8
EPA Regional Employees A-7
Hardware Considerations 3-2
Non-sensitive access A-I
requesting mainframe User-ID A-5
Sensitive access A-i
State Enforcement Agency Employees A-il
Using a Modem 3-4
Using SNA Gateway 3-3
AFS
Data Elements C-2
Description B-i
B
Boolean Operators/Connectors 8-10
AND 8-15
NOT 8-13
OR 4-9, 8-14
C
CERCLIS
Data Elements C- 15
Description B-2
Codes
Chenucal Code 4-12
Pollutant Code 4-il
SIC Code 4-16
State/County Code 4-7
Translating into English 8-16
Waste Code 4-i2
ZIP Code 4-8
Criteria 2-1, 4-i, 4-8, 4-26, 7-1
CRM
Data Elements C-26
D
Data
Data Elements C-I
Database Descriptions B-i
Data (continued)
Integration 2-6
Interpretation considerations A-3
Limitations on Use A-3
Non-sensitive access A-i
Security 5-9
Sensitive Access A-i
STARS reporting A-3
Dataset
Defimtion 5-I
See Library 5-1
DOCKET
Data Elements C-27
Description B-3
Dun & Bradstreet (or DUNS)
Data Elements C-28
Description B-4
E
ERNS
Data Elements C-29
Description B-S
F
FFIS
Data Elements C-32
Descnption B-6
FINDS
Data Elements C-33
Description B-7
Integration 2-8
G
GO MenuA 7-1, 7-4
Editing Queries 7-8, 7-10
Exiting 7-6, 7-i3
Reports 7-12
Running a Query 7-li
GO Names 7-8
Corporate Profile 6-12
Editing GO Names Queries 6-i
Excluding Nonreleasabie Data 6-17
Exiting GO Names 6-20
looking at a go names query 6-13
Managing Queries in the ISPF Mode 6-b
Modifying a GO Names Query 6-15
Index X-9
-------
GO Names (continued) Keyword Interface (continued)
Running a GO Names Query 6-19 INCLUDE 8-21
Searching by Facility Name 6-7 INPUT 8-6
Searching for Facilities by Location 6-8 Interface Selection Screen 8-1
Searching for Facilities by Name and JOB 8-27
Location 6-10 JUSTIFY 11-12
Using ERNS Data 6-5 JUSTIFY HEADINGS 11-9
Using OSHA Data 6-5 OUTPUT 8-19, 11-5
viewing a query report 6-19 PRINT 8-22
RESTRICT 11-25
u ROUTE 8-27
Running a Query 8-29
IDEA 2-1
Saving a Query 8-31
Authonzation Sample Memorandum A-6, A-7, SECURITY 8-20
A-8, A-9, A-b
SELECT 8-8
Background A-2
SORT 11-26
Conclusion A-4
SUMMARY LINE 11-28
Implementation approach A-3
SUPPRESS 11-34
Library Security 5-9
TITLE 11-8
Limitations on use of information A-3
WIDTH 11-10
Non-sensitive access A-i
Keywork Interface
Pohcy & procedures A-i
Selecting an IDEA Library 5-1
Security Overview A-3
see Accessing IDEA A-i
Sensitive access A-I L
User Support 3-14 Library
ISPF Commands 4-3, 9-1 Accepting the default 5-2
Adding Comments 9-8 Allowing others access 5-9
Copy 9-3, 9-10 Defining additional libraries 5-2
Deletmg Lines 9-2 Naming convention 5-2
Exclude 9-11 NEW status 5-3
Excluding Lines 9-6 OLD status 5-3
Find 9-7 Security considerations 5-9
Inserting Lines 9-2 SHR (share) status 5-2
Moving 9-3 What is a library 5-1
Repeating Lines 9-5 Linked
Scrolling Data 9-12 Integration 2-8
Linked Nonlinked
K Integration 2-9
Keys/Keyboard Mapping 3-10 Logic 2-4
Keyword Interface Logoff 3-15
LST
Building a Query in 9-2
Data Elements C-33
Comments in Quenes 8-26
Description B-8
DATASET 8-26
DD 8-27
DECIMALS 11-12 M
DETAIL LINE 11-6 Mainframe
EXCLUDE 8-21 Access 3-i
Exiting 8-31 Logging on 3-5
HEADER OFF 11-9 Obtaining an ID 3-1
HEADING 11-10 User Support 3-i, 3-5
X-1O IDEA User’s Guide October 22, 1996
-------
Mainframe User-ID
EPA employee request A-S
Non-EPA employee request A-5
Member List 5-3
Creating a New Member/Query 5-4
Deletmg 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
Wntmg/Updatmg a Descnption 5-7
Menu Interface
Cleanng 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
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-7, 4-8
Retrieving a Query 4-25
Running a Query 4-26
Saving a Query 4-25
\iiewing Reports 4-30
N
NCDB
Data Elements C-35
Description B-9
Nonhnked
Integration 2-9
0
OSHA
Data Elements C-37
p
PCS
Data Elements C-41
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
Retnevmg 4-25
Running 4-26
Saving 4-25
Query Status Screen 2-7
R
RACF
Allowing others 5-9
Definition 5-9
RCRIS
Data Elements C-44
Description B- 10
S
Security
Allowing others access 5-9
Excluding Nonreleasable Data 6-17, 8-20
Non-sensitive access A-i
Pohcy & procedures A-i, A-2
Sensitive access A-i
SETS
Data Elements C-48
I)escnption B-il
System Overview 2-12
T
TRIS
Data Elements C-49
Description B- 12
U
User Support & Training 3-14
User-Specified Reports 11-1
Construction 11-35
Custom USR Functions 11-14
DEFINE statements 11-7, 11-29
Detail Line 11-6
Expressions 11-7, 11-29
Formatting 11-10
Sorting 11-26
Statistical Functions 11-29
Index X-11
-------
User-Specified Reports (continued)
Summary Lme 11-28
USR Names 11-5
z
ZIP
Data Elements C-SO
Descnption B-13
X-12 IDEA User’s Guide October 22, 1996
-------
Printed in U S A
-------
APS226 1 THE ASSOCIATED DATASET WAS PRINTED ON PRT11, WHICH IS A 3160
APSB5OI A CONDITION OCCURRED IN THE PRINTER OR A FUNCTION WAS SELECTED ON THE
PRINTER CONTROL PANEL WHILE THE PRINTER WAS PROCESSING A DATA SET.
PARTIAL OR DUPLICATE PAGES MAY BE PRINTED
-------
NH NN KK KK NN MN
NNN MN KK KK NMN MN
NNNN MN KK KR NNNN MN
NM NH NM KK KK NH NH MN
NM MN NM KR KK NM MN MN
NH MN NM KKKKKKK MN NM NN
NH NH NN KKKKKKK NM NN MN
MN NM MN KK KK MN NH NH
NH NMNN KK KR NM NNNN
NH NNN KR KR MN NNN
NM NN KR KK NH MN
NM N KK KR NM N
TTTTTTTTTTTT SSSSSSSSSS UU UU 00000000 777777777777 6666666666 555555555555 777777777777
TTTTTTTTTTTT SSSSSSSSSSSS UU UU 0000000000 77777777777 666666666666 555555555555 77777777777
TT SS SS UU UU 00 0000 77 77 66 66 55 77 77
TT SS UU UU 00 00 00 77 66 55 77
TT SSS UU UU 00 00 00 77 66 55 77
rr sssssssss uu UU 00 00 00 77 66666666666 555555555 77
TT SSSSSSSSS UU UU 00 00 00 77 666666666666 5555555555 77
TT SSS 1111 UU 00 00 00 77 66 66 55 77
TT SS UU UU 0000 00 77 66 66 55 77
TT SS SS UU UU 000 00 77 66 66 55 77
TT SSSSSSSSSSSS UUUUUUUUUUUU 0000000000 77 666666666666 555555555555 77
TT SSSSSSSSSS UUUUUUUUUU 00000000 77 6666666666 55555555555 77
MM MM NM MN KK KR NM NM AAAAAAAAAA
MMM MMM NNM MN KK KK NNN NN AAAAAAAAAAAA
MMMM MMMM NNNN MN KK KR NNNN MN AA AA
MM MM MM MM NM NH MN KK KK NM NM NM AA AA
MM MMMM MM NM NM MN KK KK NM MN MN AA AA
MM fIN Nfl NM MN MN RKKKKKK NM NM NM AAAAAAAAAAAA
MM MM MN MN MN KKKKKKK NM MN NN AAAAAAAAAAAA
MM MM MN MN MN KR KR NM MN MN AA AA
MM MM MN NNMN KK KR MM NNNN Ak AA
MM MM MN MMN KK KR NM NNN Ak Ak
N Fl MM MN MN KK KR NM NN Ak AA
MM MM NM N KK KK NM N Ak Ak
* *
* JOBID. TSU07657
* JOB NAME NKM *
* USERID NKN *
* SYSOUT CLASS A *
* OUTPUT GROUP 1 00001 00001 *
* TITLE: *
* *
* DESTINATION R90 *
* NAME. Nancy K Nibling *
* ROOM: MMKN *
* BUILDING: BLDG 53 *
* DEPARTMENT: *
* ADDRESS. US EPA NEIC *
* Box 25227, Denver Federal Center / Denver CO 80225 *
* *
* BIN: MNKN *
* *
* PRINT TIME: 09:14:17 AN *
* PRINT DATE: 10 JAN 2001 *
* PRINTER: PRT11
* SYSTEM ID: EPAZ
* *
* 5** *
------- |