oEFA

United States	Office of Resource

Environmental Protection Conservation and Recovery

Agency	Washington, D.C. 20460	February 2015

RCRAInfo File

Specification Guide:

2015 Hazardous Waste
Report Submissions


-------
TABLE OF CONTENTS

INTRODUCTION	1

Overview of Document	1

Intended Audience	2

Hazardous Waste Report Forms	2

Data Files	3

Questions/Comments	3

CHANGES FROM PREVIOUS CYCLES	4

DATA SUBMISSION OVERVIEW	5

Data Requirements	5

Data Submission	6

User Access and Permissions	6

Flat File Submissions	7

Amount of Data in a Single Submission	7

States/Regions not using the 2015 Hazardous Waste Report, Instructions and Forms	8

Identify Sites	8

Access Equivalent Data	8

Data Quality/Equivalency	10

Write Translated Data to Flat Files	10

TECHNICAL SPECIFICATIONS	12

Include in National Report Flags	12

State Generator Status	12

Rules and Format Conventions Required for Data Flat Files	12

Alphanumeric Fields	13

February 2015

File Specification Guide


-------
Integer Fields	13

Fixed Decimal Fields	14

Sequence Number Fields	14

Negative Numbers	14

Record Termination	15

Empty Fields	15

Confidential Business Information (CBI)	15

SUBMISSION AND STATUS REPORT INSTRUCTIONS	16

Step-by-Step Instructions for BR Submissions	16

Status Report	19

Files Submitted	20

Errors Detected	21

Loading Data	22

APPENDIX A - FLAT FILE SPECIFICATIONS AND DATA EDITS	A-1

Key For Flat File Tables	A-1

Flat File Naming Convention	A-1

FLAT FILE ID# - Sll (HHANDLER5)	A-2

SIlFlat File Edit Specifications	A-7

FLAT FILE ID# - SI2 (HOWNER_OPERATOR5)	A-12

512	Flat File Edit Specifications	A-14

FLAT FILE ID# - SI3 (HNAICS5)	A-15

513	Flat File Edit Specifications	A-16

FLAT FILE ID# - SI4 (HWASTE_CODE5)	A-17

514	Flat File Edit Specifications	A-18

FLAT FILE ID# - SI5 (HWASTE_CODE5)	A-19

February 2015

File Specification Guide


-------
515	Flat File Edit Specifications	A-20

FLAT FILE ID# - SI6 (HUNIVERSAL_WASTE5)	A-21

516	Flat File Edit Specifications	A-22

FLAT FILE ID# - SI7 (HCERTIFICATION5)	A-23

517	Flat File Edit Specifications	A-24

FLAT FILE ID# - SI8 (HSTATE_ACTIVITY5)	A-25

518	Flat File Edit Specifications	A-26

FLAT FILE ID# - SI9 (HHSM_BASIC5)	A-27

519	Flat File Edit Specifications	A-28

FLAT FILE ID# - SIA (HHSM_ACTIVITY5)	A-29

SIA Flat File Edit Specifications	A-30

FLAT FILE ID# - SIB (HHSM_WASTE_CODE5)	A-31

SIB Flat File Edit Specifications	A-32

FLAT FILE ID# - GM1 (BGM_BASIC)	A-33

GM1 Flat File Edit Specifications	A-35

FLAT FILE ID# - GM2 (BGM_WASTE_CODE)	A-37

GM2 Flat File Edit Specifications	A-38

FLAT FILE ID# - GM3 (BGM_WASTE_CODE)	A-39

GM3 Flat File Edit Specifications	A-40

FLAT FILE ID# - GM4 (BGM_OFFSITE_SHIPMENT)	A-41

GM4 Flat File Edit Specifications	A-42

FLAT FILE ID# - GM5 (BGM_ONSITE_TREATMENT)	A-43

GM5 Flat File Edit Specifications	A-44

FLAT FILE ID# - WR1 (BWR_BASIC)	A-45

WR1 Flat File Edit Specifications	A-47

February 2015

File Specification Guide


-------
FLAT FILE ID# - WR2 (BWR_WASTE_CODE)	A-48

WR2 Flat File Edit Specifications	A-49

FLAT FILE ID# - WR3 (BWR_WASTE_CODE)	A-50

WR3 Flat File Edit Specifications	A-51

FLAT FILE ID#-Oil	A-52

APPENDIX B - HAZARDOUS WASTE REPORT ANNOTATED FORMS	B-1

February 2015	iv	File Specification Guide


-------
INTRODUCTION

This document describes the file specifications for reporting data for the 2015 Hazardous Waste Report
(also called the Biennial Report). The material in this guide covers submissions by States and Regions to
EPA Headquarters (HQ). The file specifications in this guide are not intended to be used to cover
submissions by individual reporting sites. Also, this guide is only intended to specify the file and data
formats for the submission and is not intended to cover any procedural or EPA programmatic issues.

This document is designed to be used in conjunction with the 2015 Hazardous Waste Report,
Instructions and Forms, EPA Form 8700-13A/B that is referenced throughout this document. You should
have a complete copy of the 2015 Hazardous Waste Report, Instructions and Forms in your possession
while using this guide. Copies of the 2015 Hazardous Waste Report, Instructions and Forms are available
at http://www.epa.gov/epaoswer/hazwaste/data/biennialreport/.

OVERVIEW OF DOCUMENT

The File Specification Guide for 2015 Hazardous Waste Report Submissions is divided into five sections:

Section 1 (Introduction) defines the intended audience for this guide, offers a brief description of the
forms contained in the 2015 Hazardous Waste Report, Instructions and Forms, and describes the general
purpose and outline of this document.

Section 2 (Changes from Previous Cycles) outlines the major changes to the file specifications from
previous Biennial Report cycles.

Section 3 (Data Submission Overview) describes the overall characteristics for a data submission.

Section 4 (Technical Specifications) discusses the technical details of the data files and programs
necessary for data submission.

Section 5 (Submission and Status Report Instructions) will provide detailed instructions on how to
submit Biennial Report flat files to RCRAInfo via the RCRAInfo production application. This section will
be provided once the RCRAInfo interface has been created.

Several appendices are included with this document. These appendices provide background material as
well as detailed technical information necessary to properly prepare file submissions.

February 2015

1

File Specification Guide


-------
INTENDED AUDIENCE

The intended audience for this guide is any State or EPA Region that is using its own software and
procedures to extract hazardous waste data from a State or Regional system for submission to EPA HQ
for inclusion in the RCRAInfo database for the 2015 Hazardous Waste Report; or any commercial
software vendor who is preparing software for use/purchase by States and Regions for preparation of
State or Regional submission of data for the 2015 Hazardous Waste Report.

(Note: States or Regions who use a data collection instrument different than the Hazardous Waste
ReportInstructions and Forms developed by EPA HQ are called translators. This guide will serve as
guidance for both translators and commercial software vendors.)

This document was written assuming the reader 1) is familiar with the 2015 Hazardous Waste Report,
Instructions and Forms and 2) understands basic computer concepts and terminology.

HAZARDOUS WASTE REPORT FORMS

The 2015 Hazardous Waste Report, Instructions and Forms document captures information on the
following forms:

RCRA SUBTITLE C SITE IDENTIFICATION FORM

The Site Identification Form collects information on the site completing the Biennial Report
forms package. The form is divided into fourteen items and an addendum. States and Regions
submit Site ID form information via the SI 1, SI2, SI3, SI4, SI5, SI6, SI7, SI9, SIA, and SIB flat files.

Note: The SI8 flat file allows implementers to include State-specific activities in their Biennial
Report submission. This information is not found on the RCRA Subtitle C Site Identification
Form, but rather is implementer-defined to meet the State's regulatory requirements.

GM FORM

The Waste Generation and Management Form (GM Form) is used for reporting on-site
hazardous waste generation, management, and off-site shipment. The GM Form is divided into
three sections that document 1) the source, characteristics, and quantity of hazardous waste
generated; 2) the quantity of hazardous waste managed on-site along with the management
method used; and 3) the quantity of hazardous waste shipped off-site for treatment, disposal, or
recycling along with the off-site management method used. States and Regions submit GM
form information via the GM1, GM2, GM3, GM4, and GM5 flat files.

February 2015

2

File Specification Guide


-------
WR FORM

The Waste Received from Off-site Form (WR Form) identifies hazardous wastes that were
received from other hazardous waste sites and the method(s) used to manage them. The WR
Form is divided into three identical parts (i.e., waste blocks), labeled Waste 1, Waste 2, and
Waste 3, that collect information on the quantities and characteristics of each hazardous waste
received from an off-site source during 2015 and managed on-site. States and Regions submit
WR form information via the WR1, WR2, and WR3 flat files.

01 FORM

The Off-site Identification Form (01 Form) captures the names and addresses of off-site
installations and transporters. 01 information is not loaded into the RCRAInfo database, but a
file specification has been included to facilitate data sharing.

DATA FILES

Information gathered from the Hazardous Waste Report is submitted to EPA HQ via a series of flat files.
Each form contains information that relates to the form in a one-to-one (1:1) relationship (e.g., GM
Form, Section 1, Block D, source code). These data elements are captured in the primary flat file for that
form (e.g., SI 1, GM1, and WR1). Information that relates to the form in a many-to-one (n: 1) relationship
(e.g., GM Form, Section 1, Block B, EPA hazardous waste codes) is captured in secondary flat files (e.g.,
GM2, GM3, GM4, GM5, WR2, WR3).

The remainder of this document describes in detail the steps necessary to ensure a successful data
submission including identifying which sites should be reported, the types of files that must be included
with each submission, and technical aspects of the file creation process.

QUESTIONS/COMMENTS

Questions about this document should be directed to the RCRAInfo team via the User Support Issue
Tracking System (USITS) utility in RCRAInfo. Questions submitted must only concern the file
specification for submission of data from the States or EPA Regions to the RCRAInfo database.
Questions on submissions of data by individual sites should be directed to the appropriate State or EPA
Regional personnel. For a list of the appropriate contacts see:
http://www.epa.gov/osw/inforesources/data/form8700/contact.pdf.

February 2015

3

File Specification Guide


-------
CHANGES FROM PREVIOUS CYCLES

Other than the valid dates associated with the Receive Date and Certification Date, there are no changes
in the business rules for the 2015 Hazardous Waste Report.

February 2015

4

File Specification Guide


-------
DATA SUBMISSION OVERVIEW

DATA REQUIREMENTS

Data collected via the 2015 Hazardous Waste Report, Instructions and Forms may or may not be
required to be included in the Hazardous Waste Report submission. For the purposes of this document,
"required" refers to data elements that must be provided and cannot have a value of blank.

States and Regions are encouraged to provide as much data (required or not required) as possible. This
information enhances the analytical usefulness of the Hazardous Waste Report data within RCRAInfo.

State, Regional, and commercial software packages must provide data for required data elements. Flat
files containing required data elements include:

•	Site ID Form data (RCRA Subtitle C Site Identification Form):

Flat Files Sll, SI2, SI3, SI4, SI6, SI7

•	GM Form data (Waste Generation and Management):

Flat Files GM1, GM2, GM4, and GM5

•	WR Form data (Waste Received from Off-site):

Flat Files WR1 and WR2

Additionally, States who allow facilities to manage hazardous secondary material under 40 CFR
261.2(a)(2)(ii), 40 CFR 261.4(a)(23), (24), or (25) may submit their required re-notification of hazardous
secondary material activity using the following flat files:

• Site ID Form Addendum data (Hazardous Secondary Material):

Flat Files SI9, SIA, and SIB

All data elements must be properly formatted and meet required data quality standards to be loaded
into RCRAInfo. The data quality standards for these elements are presented in Appendix A.

February 2015

5

File Specification Guide


-------
To successfully load data into RCRAInfo, all data elements for every submitted flat file must meet
formatting and data quality standards. See Appendix A for specifications on standards and formats for
all flat files.

DATA SUBMISSION

It is the responsibility of the State, Regional, or commercial software package to produce a complete set
of correctly formatted files for a given State for inclusion in the RCRAInfo database. The RCRAInfo
application can only accommodate submissions containing all data for a given State, that is, data for a
single site cannot be loaded into RCRAInfo.

Flat files are submitted to RCRAInfo in accordance with the Memorandum of Understanding between
the Region and the State. The data is transferred to RCRAInfo in the form of Windows-compatible ZIP
files. The RCRAInfo File Transfer Process extracts the files from these zip files and stores the data in
Oracle database "staging" tables for further processing.

USER ACCESS AND PERMISSIONS

The user must have the following access and permissions to successfully submit flat files to RCRAInfo:

•	User ID and password for the RCRAInfo production application;

•	Granted the translation "role" within the database;

•	Have Level 4 (read, add, update, and delete) permissions for the Biennial Report module;

•	Be the implementer of record for the information being submitted.

Please contact your State or Regional system administrator to obtain a RCRAInfo ID and password, to
receive the required permissions, and/or to set implementer of record settings. To obtain the
translation "role", please contact Idali Gotay (gotay.idali@epa.gov).

February 2015

6

File Specification Guide


-------
FLAT FILE SUBMISSIONS

The RCRAInfo application provides an interface for submitters to upload a ZIP file from their local file
location to the RCRAInfo staging tables. The uploaded file must be in the form of a ZIP file. These files
must be:

-	flat files;

-	column delimited;

-	formatted such that each record in the file is followed by a carriage return/line feed;

-	formatted per the flat file specification's documented in this booklet.

A submitter is limited to filing data for one State per ZIP file.

Before the file is uploaded, the RCRAInfo interface will validate the zip file name by the following
criteria:

-	the first three (3) characters are the program abbreviation: RCR

-	the next four (4) characters are program-specific: 2-letter State abbreviation followed by the
submission number (e.g., KS01)

-	the last three (3) characters are the TSSMS ID of the user submitting the files.

An example file name would be RCRKS01SIX.ZIP. Note: The activity location (state code) embedded in
the file name must match the state code associated with the RCRAInfo agency of the submitter that is
filing the information.

If the file name does not pass validation, the RCRAInfo interface will provide the submitter with a
message describing the error and prompt the submitter to correct the error in order to complete the file
upload process.

AMOUNT OF DATA IN A SINGLE SUBMISSION

Each data submission must contain ALL data for the State being submitted. Each data submission will
overwrite ALL existing 2015 Hazardous Waste Report data for the State in the RCRAInfo database. Note:
If you provide data for a handler with an incorrect Handler ID, you cannot delete this Handler ID from
RCRAInfo simply by excluding the Handler ID from your next submission. Rather, you will need to
submit a USITS issue through RCRAInfo, requesting EPA Headquarters to delete the Handler ID.

February 2015

7

File Specification Guide


-------
STATES/REGIONS NOT USING THE 2015 HAZARDOUS WASTE REPORT, INSTRUCTIONS AND
FORMS

The information contained in this guide is equally applicable to States and Regions who use a different
data collection package than the 2015 Hazardous Waste Report, Instructions and Forms. Translators are
required to provide data equivalent to that collected by the 2015 Hazardous Waste Report, Instructions
and Forms (required data elements). The following information is provided to help translators become
familiar with the steps necessary to ensure a successful data submission:

•	Identify all sites for which information is to be translated.

•	Access information that is equivalent to the 2015 Hazardous Waste Report data.

•	Validate that the equivalent data conforms to the appropriate data quality standards.

•	Write translated data to appropriate flat files.

IDENTIFY SITES

The State/Region must submit information for sites required to file the 2015 Hazardous Waste Report,
Instructions and Forms. The criterion that defines these sites is presented in the 2015 Hazardous Waste
ReportInstructions and Forms under "Sites Required to File the Hazardous Waste Report." States and
Regions are not precluded from submitting information for sites not required to file the 2015 Hazardous
Waste Report, Instructions and Forms.

ACCESS EQUIVALENT DATA

The required data elements for the sites being reported must be provided. The translator State/Region
must identify, in their system, the data elements and relationships equivalent to the data
elements/relationships represented by the flat file specifications provided in Appendix A.

The GM Form, WR Form, and 01 Form allow for multiple form submissions by a handler. Translator
States/Regions must also accommodate multiple "forms" by a handler as follows:

February 2015

8

File Specification Guide


-------
GM FORM

The GM Form collects data associated with a single reported waste. Translators must provide
records in the GM1 - GM5 files for each waste generated or managed during the reporting
cycle. Thus, each page number for the GM flat file records represents a single reported waste.
All GM flat file records containing data associated with the same waste reported for the same
EPA ID will have the same page number. Page number takes the value of "00001" for the first
reported waste on the GM Form and is incremented by one (1) with each following reported
waste. (Note: The instructions on assignment of page number for translators are different than
for those States/Regions/commercial software vendors supporting the 2015 Hazardous Waste
ReportInstructions and Forms. For vendors supporting the 2015 Hazardous Waste Report,
Instructions and Forms, page number should be the same as the number assigned by the
respondent to the actual form.)

WR FORM

The WR Form collects data associated with each reported waste received from off-site.
Translators must provide records in the WR1 - WR3 files for each waste received from off-site.
All WR flat file records containing data associated with the same received waste reported for the
same handler will have the same page number. Page number takes the value of "00001" for the
first received waste on the WR Form and is incremented by one (1) with each separate received
waste reported. The sub-page number for the WR Form data must always be assigned the value
of "1". (Note: The instructions on assignment of page number and sub-page number for
translators are different than for those States/Regions/commercial software vendors supporting
the 2015 Hazardous Waste Report, Instructions and Forms. For vendors supporting the 2015
Hazardous Waste Report, Instructions and Forms, page number and sub-page number should be
the same as the number assigned by the respondent to the actual form. Sub-page number is '1'
for the waste reported in the "Waste 1" block of the WR form, '2' for the waste reported in the
"Waste 2" block of the WR form, and '3' for the waste reported in the "Waste 3" block of the
WR form.)

February 2015

9

File Specification Guide


-------
01 FORM

The 01 Form collects data identifying 1) handlers from whom waste was received and to whom
waste was shipped and 2) all transporters used to ship waste during the reporting cycle. These
source, destination, and transporting entities are identified by their EPA ID, name, and address.
The page number for the 01 flat file records represents a single handler record. Page number
takes the value of "00001" for the first handler record and is incremented by one (1) with each
separate handler record reported.

DATA QUALITY/EQUIVALENCY

The State/Region's translator data must provide an accurate representation of hazardous waste activity
for that State. In addition, the translator's data must pass a minimum set of data edits (see Appendix A)
in order to provide information comparable to data gathered with the 2015 Hazardous Waste Report,
Instructions and Forms and to be properly loaded into the RCRAInfo database. Any data failing to
conform to the appropriate data quality edits will result in the entire data submission to RCRAInfo being
rejected.

Appendix B contains an annotated copy of the 2015 Hazardous Waste Report forms showing in which
flat file each data element is located. In addition, all codes used in the submission must conform to
acceptable data values as specified in Appendix A.

WRITE TRANSLATED DATA TO FLAT FILES

Translator States/Regions must extract data from their State/Regional system and re-produce the data
in the flat file formats outlined in Appendix A. A complete translation may not necessarily include all flat
files. For example, a translator submitting SI Form data is not required to include the "SI8" flat file (state
activity) since it is non-required data. However, the State/Region is encouraged to include in the
Hazardous Waste Report data submission all data (required and non-required) that the State/Region
currently collects.

The flat file specifications for the Hazardous Waste Report data are based on a series of parent-child
relationships. A parent file (i.e., SI 1, GM1, WR1) may have one or more child relationships with other
flat files (i.e., SI2-SIB, GM2-GM5, WR2-WR3). Child records may not exist without the existence of the
parent record (e.g., a record for site XYZ cannot exist in the GM2 file if a corresponding record does not
exist in the GM1 file).

February 2015

10

File Specification Guide


-------
Data for a site should only be included in the Hazardous Waste Report data submission after all records
for that site pass all appropriate edit checks. If a site's data is incomplete, then the site's information
must not be included in the State's Hazardous Waste Report data submission. It is not sufficient to
eliminate the data element in error and submit the remainder of the site's data.

February 2015

11

File Specification Guide


-------
TECHNICAL SPECIFICATIONS

This section contains the standards that must be met when producing flat files for the Hazardous Waste
Report data submission. Failure to meet these specifications will result in the rejection of the flat files
and failure to load the data into the RCRAInfo database.

INCLUDE IN NATIONAL REPORT FLAGS

Sll, GM1, and WR1 file specifications include a field labeled INCLUDE_IN_NATIONAL_ REPORT. The
purpose of this field is to allow implementers to submit additional Hazardous Waste Report data (for
purposes of data sharing) but keep that data from being included in the National Biennial Hazardous
Waste Report. The field is defined as follows: If the INCLUDE_IN_NATIONAL_REPORT flag in the Sll file
is 'N' (No), then all the INCLUDE_IN_NATIONAL_REPORT flags for the site must also equal 'N' (No) else
the submission will be in error. If the INCLUDE_IN_NATIONAL_REPORT flag in the Sll file is 'Y' (Yes),
implementers may set the flag in the GM1 and WR1 file as either 'Y' (Yes) or'N' (No) to indicate whether
that particular waste should be included in the National Biennial Hazardous Waste Report. It is
anticipated that many implementers will default the value for these flags to 'Y' (Yes) in all cases,
however the specific implementation of how these flags are populated is determined by the
implementer.

STATE GENERATOR STATUS

Implementers are required to furnish both the State-specific generator status and the Federal generator
status for each site in their submission. Appropriate fields are included in the Sll file specification for
this purpose. It is anticipated that many States whose regulations closely match the federal regulations,
either by reference or by inclusion, will choose for the values of these fields to be the same. The
method to populate these fields is determined by the implementer, however both fields must be
provided or the submission will be rejected.

RULES AND FORMAT CONVENTIONS REQUIRED FOR DATA FLAT FILES

The following sub-sections detail the correct field formats for the data in the flat files.

February 2015

12

File Specification Guide


-------
ALPHANUMERIC FIELDS

Alphanumeric fields are identified in Appendix A as Data Type "A" fields. Data Type "A" fields must be
left-justified with all trailing spaces filled with the space character (i.e., ASCII HEX 0x20 or ASCII Decimal
32).

Valid characters for alphanumeric fields are limited to:

()_-+={}[] |\:;"',.?/1234567890ABCDEFGHIJKLMNOPQRSTUVWXYZ

Invalid characters for alphanumeric fields include:

<>

If the "<" or ">" symbols are used to indicate less than or greater than, it is recommended that these
symbols be replaced with "LT" or "GT".

As part of the RCRAInfo load routines, all lowercase letters (a-z) will be converted to uppercase
characters (A-Z). Lowercase letters will not cause a submission to be rejected, however the lowercase
letters will be converted to uppercase characters.

INTEGER FIELDS

Integer fields are identified in Appendix A as Data Type "I" fields.

Allowed values for integer fields are numbers 0-9 and the space character (ASCII Hex 0x20 or ASCII
Decimal 32).

Examples of incorrect and correct entries for an integer field defined with a length of five (5) are
presented in Exhibit 2 below.

INCORRECT

CORRECT

1A

1

10,000

10000

750.25

750

Exhibit 2. Incorrect and Correct Integer Entries

February 2015

13

File Specification Guide


-------
FIXED DECIMAL FIELDS

Fixed place decimal fields are identified in Appendix A as Data Type "D" fields.

For all "D" field entries, the flat file specifications indicate the number of digits that the data element is
allowed before the decimal and after the decimal. For example, D11.6 indicates that the number may
have up to 11 digits before the decimal and 6 digits after the decimal (99999999999.999999). The field
length includes the decimal character.

Allowed values for fixed decimal fields are numbers 0-9, the decimal character and the space
character (ASCII Hex 0x20 or ASCII Decimal 32).

Although some data blocks on the 2015 Hazardous Waste Report, Instructions and Forms provide for
only one decimal place, the translator flat files may allow additional decimal places to be represented in
"D" fields. Exhibit 3 shows incorrect and correct entries in a type "D5.2" field.

INCORRECT

CORRECT

10,032.1

10032.10

10,032A

10032

Exhibit 3. Incorrect and Correct Fixed Decimal Entries

SEQUENCE NUMBER FIELDS

Some of the files in Appendix A require a sequence number to be provided for each record. The SI3 file,
for example, requires a sequence number (NAICS_SEQ) for the NAICS codes. The sequence number is
needed for data elements, such as the NAICS code, which may have more than one value. The sequence
number should be assigned the value "0001" for the first occurrence of the sequenced data element for
the EPA ID and should then be incremented by one with each successive occurrence of that same EPA
ID.

NEGATIVE NUMBERS

Negative numbers are not allowed in the data submission.

February 2015

14

File Specification Guide


-------
RECORD TERMINATION

Each flat file record must be terminated by a line feed character (ASCII Hex OxOA or ASCII Decimal 010),
or a carriage return character (ASCII Hex OxOD or ASCII Decimal 013) followed by a line feed character.

EMPTY FIELDS

For fields that require no response, the field should be filled with the space character (i.e., blanks).

CONFIDENTIAL BUSINESS INFORMATION (CBI)

Under existing RCRA statutes, sites may claim that certain items of information submitted as part of
their Hazardous Waste Report contain Confidential Business Information (CBI). The procedures for
handling CBI can be found in Procedures for Handling RCRA Confidential Business Information (available
from the EPA HQ RCRA Document Control Officer). A subset of these procedures is documented in
Procedures for Handling RCRA Confidential Business Information Submitted for the Biennial Report.
(Copies of these documents can be requested using the USITS utility in RCRAInfo). In brief, it is not
allowable to mingle CBI data with non-CBI data. In addition, CBI data must be handled on a secure
computer (either a computer that is kept in a secure environment or a computer that uses removable
media where the media is kept in a secure environment). CBI data must be submitted separately from
non-CBI data using data handling methods outlined in the Procedures for Handling RCRA Confidential
Business Information documentation.

In previous Biennial Report cycles, some States/Regions that have received CBI have masked the CBI
data (in other words, changed the CBI data so it no longer is CBI). This practice is not a requirement of
EPA HQ, but as long as the masking is acceptable to the site and the implementer, and the data meets
the minimum edit standards as detailed in the appendices, this solution is acceptable.

February 2015

15

File Specification Guide


-------
SUBMISSION AND STATUS REPORT INSTRUCTIONS

STEP-BY-STEP INSTRUCTIONS FOR BR SUBMISSIONS

The following step-by-step submission instructions assume that you have obtained the necessary user ID
/ passwords and access for the RCRAInfo application. The steps provided below illustrate how to submit
a BR flat file into the RCRAInfo production environment.

Step 1 - Open Internet Explorer and go to the RCRAInfo URL - https://rcrainfo.epa.gov (Production
RCRAInfo website) or https://rcrainfopreprod.epa.gov (Pre-production RCRAInfo website)

Step 2 - On the Warning Notice page click "here" to agree to the terms and continue

Step 3 - On the RCRAInfo page, provide your RCRAInfo user ID and password and click "Log on"

Step 4 - From the RCRAInfo Main Menu, click "Translate Data"

Select a Handler for Data Maintenance

National and Implementer Reports



Handler, Permitting, Corrective Action, CM&E, Financial

My RCRA ID Submissions

Assurance, GIS

Multi-site Consent Anreement/Final Orders

BARRT

(CAFOs)





Utilities

Co m m itm e nt M a i nte nance

Change Password, User Preferences, Groups of IDs, Status



Reports

News Alerts and General Information



Contact Lists, System Documentation, Security

System Administration



System Administrators, User Maintenance, Lookup

PCB Data System

Maintenance

Translate Data

USITS



Change Management



Lotioff

Step 5 - From the Load Translation Files screen, select a Module Type of "Biennial Report", an Upload
Type of "Full Replace", and a Report Cycle of "BR 2015".

February 2015

16

File Specification Guide


-------
Module Type

Upload Type

Report Cycle

® Biennial Report

O Transactional

Report Cycle: IdaiMH v

O Compliance, Monitoring & Enforcement

O Partial



O Corrective Action

® Full Replace



O Financial Assurance

O Delete



O GIS





O Handler





O Permitting





Step 6 - Provide the name of the zip file containing the BR data (i.e., c:\flatfiles\rcrfl01six.zip) by typing
it in the "File Name:" or using the "Browse" button

Upload Data [Please use the Browse button to select the file to upload.)

File Name: |c:\flatfiIes\rcrfl01six.zip	| Browse..

Step 7 - Click the "Load Data" button

Step 8 - You will receive the message "File Upload is Valid" and the name of the flat files found in the
zip file will be displayed

File Upload is Valid

File Names Found: flwr2001.fi! flgrn1001.fl flgm2001.fll flgm4001.fil flgm5001.fil flsi1001.fll flsi2001.fi! flsi3001.fi! flsi4001.fil flsi6001.fi! flsi7001.fi! flwr1001.fil

Step 9 - Click "Initialize and Load Staging Tables"

Step 10 - A message will appear indicating that the staging tables are being loaded

February 2015

17

File Specification Guide


-------
Loading Tables. Please ivait...

Thu Feb 11 10:39:01 EST 2010

Step 11 - The "Confirmation of Biennial Report Upload" screen will be displayed showing each file in the
submission and the number of records received for each file. It will also indicate if any load
errors were encountered by adding "with errors" after the record count. Click the "with
errors" link to determine what load errors were encountered.

Total Number of Records Received
83181 WR2 (BWR_WASTE_CODE [EPA]) record(s) received.
5599 GM1 (BGM_BASIC) record(s) received.

15830 GM2 (BGM_WASTE_CODE [EPA]) record(s) received.
6056 GM4 (BGM_OFFSITE_SHIRMENT) record(s) received.
45 GM5 (BGM_ONSITE_TREATMENT) record(s) received.

364 SI1 (HHANDLER5) record(s) received.

745 SI2 (HOWNER_OPERATOR5) record(s) received.

411 SI3 (HNAICS5) record(s) received.

5577 SI4 (HWASTE_CODE5 [EPA]) record(s) received.
36 SI6 (HUNIVERSAL_WASTE5) record(s) received.

372 SI7 (HCERTIFICATION5) record(s) received.

24893 WR1 (BWR_BASIC) record(s) received.

12 Control Records Were Built

Step 12 - Click "Continue"

February 2015	18	File Specification Guide


-------
Step 13 - The Status Report screen will be displayed (depending on the size of the load, it may take
several minutes for the Status Report screen to be displayed)

Step 14 - Click the "Biennial Report Load" radio button and use the drop-down list to specify you state.
Click "Run Report".

® Biennial Report Load
O Translator Load
O Universe Calculations

0	GPRA Update

For BR or Translator Status Reports, please select a State to view:
^ si I	v

For Translator Status Reports, please select a Module:

1	Select a Module

Step 15 - At the bottom of the Status Report you should seethe message "Translation has finished

successfully" or "Translation has FAILED - Please review your error messages". If you get the
"Translation has finished successfully" message, you submission was successful and your data
was loaded into RCRAInfo. If you get the "Translation has FAILED..." message, your submission
was not successful and you need to proceed to Step 16.

Step 16 - Review the Status Report to see the errors that were detected. You must correct the errors in
the flat files and go back to Step 1.

STATUS REPORT

The Status Report provides the user with information regarding the processing of the BR load. See Step
14 above to access the Status Report in RCRAInfo.

The Status Report contains information on the files submitted, the errors detected, and the status of
loading data into RCRAInfo.

February 2015

19

File Specification Guide


-------
FILES SUBMITTED

The top portion of the Status Report shows the flat files submitted and the number of records received.
You should see one record for each file submitted. The record counts are provided so that you know
how much data was received by RCRAInfo. If these record counts are not correct, you will need to
resubmit all of your files.

11/28/2011 01:06:24

Translating BR 2011 data for FL

11/28/2011 01:06:24

File: SI1. Records: 364 received.

11/28/2011 01:06:24

File: SI2. Records: 745 received.

11/28/2011 01:06:24

File: SI3. Records: 411 received.

11/28/2011 01:06:24

File: SI4. Records: 5577 received.

11/28/2011 01:06:24

File: SI6. Records: 36 received.

11/28/2011 01:06:24

File: SI7. Records: 372 received.

11/28/2011 01:06:24

File: GM1. Records: 5599 received.

11/28/2011 01:06:24

File: GM2. Records: 15830 received.

11/28/2011 01:06:24

File: GM4. Records: 6056 received.

11/28/2011 01:06:24

File: GM5. Records: 45 received.

11/28/2011 01:06:24

File: WR1. Records: 24893 received.

11/28/2011 01:06:24

File: WR2. Records: 83181 received.

The status report will then show every file within the module (including files that were not submitted)
indicating the number of records in each file, the number of records which do not have any edit errors,
and the number of records that do have edit errors. If any of the files contain data edit errors, then NO
data from the submission will be loaded into RCRAInfo. If the data does contain errors, you will have to
correct the errors in the flat files and resubmit the entire load.

February 2015

20

File Specification Guide


-------
11/28/2011 01:25:42

Completed edit checks for SI1. 0 records have errors.

11/28/2011 01:25:42

Processing edit checks for file SI2.

11/28/2011 01:25:42

Completed edit checks for SI2. 0 records have errors.

11/28/2011 01:25:42

Processing edit checks for file SI3.

11/28/2011 01:25:42

Completed edit checks for SI3. 0 records have errors.

11/28/2011 01:25:42

Processing edit checks for file SI4.

11/28/2011 01:25:42

Completed edit checks for SI4. 0 records have errors.

11/28/2011 01:25:42

FL has no records in file SI5.

11/28/2011 01:25:42

Processing edit checks for file SI6.

11/28/2011 01:25:42

Completed edit checks for SI6. 0 records have errors.

11/28/2011 01:25:42

Processing edit checks for file SI7.

11/28/2011 01:25:42

Completed edit checks for SI7. 0 records have errors.

11/28/2011 01:25:42

FL has no records in file SI8.

11/28/2011 01:25:42

FL has no records in file SI9.

11/28/2011 01:25:42

FL has no records in file SIA.

11/28/2011 01:25:42

FL has no records in file SIB.

11/28/2011 01:25:42

Processing edit checks for file GM1.

11/28/2011 01:25:59

Completed edit checks for GM1. 0 records have errors.

11/28/2011 01:25:59

Processing edit checks forfile GM2.

11/28/2011 01:25:59

Completed edit checks for GM2. 0 records have errors.

11/28/2011 01:25:59

FL has no records in file GM3.

11/28/2011 01:25:59

Processing edit checks for file GM4.

11/28/2011 01:25:59

Completed edit checks for GM4. 0 records have errors.

11/28/2011 01:25:59

Processing edit checks forfile GM5.

11/28/2011 01:26:00

Completed edit checks for GM5. 0 records have errors.

11/28/2011 01:26:00

Processing edit checks for file WR1.

11/28/2011 01:26:01

Completed edit checks for WR1. 0 records have errors.

11/28/2011 01:26:01

Processing edit checks for file WR2.

11/28/2011 01:26:03

Completed edit checks for WR2. 0 records have errors.

11/28/2011 01:26:03

FL has no records in file WR3.

ERRORS DETECTED

The status report will show all of the errors detected within the BR load, reporting the flat file in error,
the record number in error, and the key fields for the record. Additionally, information regarding the
error will be given, often making references to the error numbers in the BR Flat File Specification. All
errors must be corrected and the flat files resubmitted before any data will be moved to the RCRAInfo
tables.

February 2015

21

File Specification Guide


-------
The BR load process attempts to detect all errors so that the user can correct as many errors as possible
before reloading the data. However, to make the report manageable to the user, only the first 200
errors are reported. Additionally, correcting an error may create another error, so it is very important to
always verify that your load is error-free in the status report.

11/28/2011 File:SI1 Rec:207 Key: FLD982083115, Receive Date: 01-11-2012. RECEIVE DATE must be >= 1/1/2011 and <= Today. See SI1-016.

02:38:32

11/28/2011 File:SI1 Rec:211 Key: FLD060249547. The HANDLER NAHE must be provided. See SI1-020.

02:38:32

11/28/2011 File:SIl Rec:217 Key: FLD064675978, Location State:XX. LOCATION STATE does not equal the first two characters of the HANDLER ID. See SI1-050.

02:38:32

11/28/2011 File:SI1 Rec:247 Key: FLD004059861. The LOCATION CITY must be provided. See SI1-040.

02:38:32

LOADING DATA

Once the load is error free, the data in the SI files will be moved to the RCRAInfo production tables and a
BR staging environment. The GM and WR files will be moved to the BR staging environment but will
NOT be moved to the RCRAInfo production tables until the BR Cycle is final. The status report wiil show
if the data has been successfully moved to the RCRAInfo production and BR staging tables.

11/28/2011 01:28:59

Loading 2011 BR data into RCRAINF0 tables

11/28/2011 01:29:01

Completed translation load into HBASIC from SI1

11/28/2011 01:29:01

Loading data from SI1 into HHANDLERS.

11/28/2011 01:29:02

Completed loading data from SI1 into HHANDLERS,

11/28/2011 01:29:02

Loading data from SI2 into HOWNER_OPERATOR5.

11/28/2011 01:29:03

Completed loading data from SI2 into HOWNER_OPERATOR5.

11/28/2011 01:29:03

Loading data from SI3 into HNAICS5.

11/28/2011 01:29:03

Completed loading data from SI3 into HNAICS5.

February 2015

22

File Specification Guide


-------
Upon completion of the BR load process (either successful or unsuccessful), the status report will
indicate that process has been completed.

11/28/2011 01:31:23

Translation has finished successfully.

or

1 1/28/201 1
02:38:58

Translation has FAILED-- Please review your error messages.

February 2015

23

File Specification Guide


-------
APPENDIX A

Flat File Specifications and Data Edits


-------
KEY FOR FLAT FILE TABLES

Data Type

A	Alphanumeric

I	Integer

D	Fixed Decimal

FLAT FILE NAMING CONVENTION

Flat files names are constructed in the following manner:

SSFFFNNN.FIL

Where:

SS	= State Postal Code

FFF	= Flat file identifier (for example, GM1 or GM2)

NNN	= Julian Date when file was created

Files must be named using all uppercase characters.

Note: The three-character file ID distinguishes each flat file produced during the translation. For
example, the correct name for the SI3 file, containing KS data, produced on January 4th, is KSSI3004.FIL.

February 2015

A-1

File Specification Guide


-------
FLAT FILE SPECIFICATIONS AND DATA EDITS

FLAT FILE ID#-SI 1

Source Form: Site ID Description: Handler Identification, Address, and Hazardous Waste Activities Information



This file must contain one and only one record for each Handler ID reporting. Also, any Handler ID appearing as the key in ANY of the "GM" or
"WR" files must also be present in this file.

Key Fields: Handler ID (HANDLERJD). Each record in the Sll file must contain a unique Handler ID.







Note: The Sll file is REQUIRED. One record must be provided for each handler.







Field Name

Starting
Column

Field
Length

Data
Type

Description

Location
on Form

Required /

Cond.
Required

Edit
Number(s)

HANDLERJD

1

12

A

EPA Identification Number

SI-2

Required

Sll-010,
Sll-015,
SI 1-490,
SI 1-500,
SI 1-510,
SI 1-5 20

RECEIVE_DATE

13

8

Date

Received Date



Required

Sll-016

HANDLER_NAME

21

80

A

Handler Name

SI-3

Required

Sll-020

LOCATION_STREET_NO

101

12

A

Location Street Number

SI-4





LOCATION_STREETl

113

30

A

Location Street 1

SI-4

Required

Sll-030

LOCATION_STREET2

143

30

A

Location Street 2

SI-4





LOCATION_CITY

173

25

A

Location City

SI-4

Required

SI 1-040

LOCATION_STATE

198

2

A

Location State

SI-4

Cond.
Required

SI 1-050,
SI 1-060

February 2015

A-2

File Specification Guide


-------












Required /





Starting

Field

Data



Location

Cond.

Edit

Field Name

Column

Length

Type

Description

on Form

Required

Number(s)

LOCATION ZIP

200

14

A

Location Zip

SI-4

Required

SI 1-070













Cond.

SI 1-080,

COUNTY CODE

214

5

A

Location County Code

SI-4

Required

SI 1-085















Sll-050,















SI 1-060,















SI 1-080,















SI 1-085,















SI 1-090,















Sll-530,

LOCATION COUNTRY

219

2

A

Location Country Code

SI-4



SI 1-540

STATE DISTRICT

221

10

A

State District





SI 1-095

MAIL STREET NO

231

12

A

Mailing Street Number

SI-7





MAIL STREET1

243

30

A

Mailing Street 1

SI-7

Required

Sll-100

MAIL STREET2

273

30

A

Mailing Street 2

SI-7





MAIL CITY

303

25

A

Mailing City

SI-7

Required

Sll-110













Cond.

Sll-120,

MAIL STATE

328

2

A

Mailing State

SI-7

Required

SI 1-130

MAIL ZIP

330

14

A

Mailing Zip

SI-7

Required

SI 1-140















Sll-120,















Sll-130,

MAIL COUNTRY

344

2

A

Mailing Country Code

SI-7



SI 1-150

LAND TYPE

346

1

A

Site Land Type

SI-5

Required

Sll-160

CONTACT FIRST NAME

347

15

A

Contact First Name

SI-8

Required

Sll-170

CONTACT MIDDLE INITIAL

362

1

A

Contact Middle Initial

SI-8





CONTACT LAST NAME

363

15

A

Contact Last Name

SI-8

Required

Sll-180

CONTACT STREET NO

378

12

A

Contact Street Number

SI-8





CONTACT STREET1

390

30

A

Contact Street 1

SI-8





CONTACT STREET2

420

30

A

Contact Street 2

SI-8





CONTACT_CITY

450

25

A

Contact City

SI-8





February 2015

A-3

File Specification Guide


-------












Required /





Starting

Field

Data



Location

Cond.

Edit

Field Name

Column

Length

Type

Description

on Form

Required

Number(s)















Sll-190,

CONTACT STATE

475

2

A

Contact State

SI-8



Sll-200

CONTACT ZIP

477

14

A

Contact Zip

SI-8



















Sll-190,















Sll-200,

CONTACT COUNTRY

491

2

A

Contact Country

SI-8



SI 1-210

CONTACT PHONE

493

15

A

Contact Phone Number

SI-8

Required

SI 1-220

CONTACT PHONE EXT

508

6

A

Contact Phone Number Extension

SI-8





CONTACT FAX

514

15

A

Contact Fax Number

SI-8





CONTACT TITLE

529

45

A

Contact Title

SI-8





CONTACT EMAIL

574

80

A

Contact E-mail Address

SI-8



















SI 1-240,















Sll-275,















Sll-295,

FED WASTE GENERATOR

654

1

A

Federal Generator Status

SI-10-A-1

Required

SI 1-540

STATE WASTE GENERATOR

655

1

A

State Generator Status



Required

Sll-260















Sll-270,















Sll-275,









Short Term or Temporary





SI 1-277,

SHORT TERM GENERATOR

656

1

A

Generator

SI-10-A-1

Required

Sil-540









U.S. Importer of Hazardous





SI 1-280,

IMPORTER ACTIVITY

657

1

A

Waste

SI-10-A-1

Required

SI 1-540















Sll-290,









Mixed Waste (hazardous and





Sll-295,

MIXED WASTE GENERATOR

658

1

A

radioactive) Generator

SI-10-A-1

Required

Sil-540

TRANSPORTER

659

1

A

Transporter of Hazardous Waste

SI-10-A-2

Required

Sll-300









Transfer Facility of Hazardous





SI 1-310,

TRANSFER_FACILITY

660

1

A

Waste

SI-10-A-2

Required

SI 1-540

February 2015

A-4

File Specification Guide


-------












Required /





Starting

Field

Data



Location

Cond.

Edit

Field Name

Column

Length

Type

Description

on Form

Required

Number(s)









Treater, Storer, or Disposer of















Hazardous Waste in a Permitted





Sll-320,

TSD ACTIVITY

661

1

A

Unit

SI-10-A-3

Required

SI 1-540















Sll-330,

RECYCLER ACTIVITY

662

1

A

Recycler of Hazardous Waste

SI-10-A-4

Required

SI 1-540









Small Quantity On-Site Burner





SI 1-340,

ONSITE BURNER EXEMPTION

663

1

A

Exemption

SI-10-A-5

Required

SI 1-540









Smelting, Melting, and Refining





Sll-350,

FURNACE EXEMPTION

664

1

A

Furnace Exemption

SI-10-A-5

Required

SI 1-540















Sll-360,

UNDERGROUND INJECTION ACTIVITY

665

1

A

Underground Injection Control

SI-10-A-6

Required

SI 1-540









Received Hazardous Waste from







OFF SITE RECEIPT

666

1

A

Off-site

SI-10-A-7

Required

SI 1-362









Destination Facility for Universal





Sll-365,

UNIVERSAL WASTE DEST FACILITY

667

1

A

Waste

SI-10-B-2

Required

SI 1-540

USED OIL TRANSPORTER

668

1

A

Used Oil Transporter

SI-10-C-1

Required

Sll-370















SI 1-380,

USED OIL TRANSFER FACILITY

669

1

A

Used Oil Transfer Facility

SI-10-C-1

Required

SI 1-540















Sll-390,

USED OIL PROCESSOR

670

1

A

Used Oil Processor

SI-10-C-2

Required

SI 1-540















SI 1-400,

USED OIL REFINER

671

1

A

Used Oil Re-refiner

SI-10-C-2

Required

SI 1-540















SI 1-410,

USED OIL BURNER

672

1

A

Off-Specification Used Oil Burner

SI-10-C-3

Required

SI 1-540









Marketer Who Directs Shipment















of Off-Specification Used Oil to





SI 1-420,

USED OIL MARKET BURNER

673

1

A

Off-Specification Used Oil Burner

SI-10-C-4

Required

SI 1-540









Marketer Who First Claims the





SI 1-430,

USED_OIL_SPEC_MARKETER

674

1

A

Used Oil Meets the Specifications

SI-10-C-4

Required

SI 1-540

February 2015

A-5

File Specification Guide


-------
















Required /









Starting

Field

Data



Location

Cond.

Edit





Field Name

Column

Length

Type

Description

on Form

Required

Number(s)













Opting into or Currently





SI 1-440,













Operating under 40 CFR Part 262





SI 1-475,













Subpart K as a College or





SI 1-476,

SUBPART

K

COLLEGE

675

1

A

University

SI-10-D

Required

SI 1-540,



















SI 1-450,













Opting into or Currently





SI 1-475,













Operating under 40 CFR Part 262





SI 1-476,

SUBPART

K

HOSPITAL

676

1

A

Subpart K as a Teaching Hospital

SI-10-D

Required

SI 1-540













Opting into or Currently





SI 1-460,













Operating under 40 CFR Part 262





SI 1-475,













Subpart K as a Non-profit





SI 1-476,

SUBPART

K

NONPROFIT

677

1

A

Research Institute

SI-10-D

Required

SI 1-540



















SI 1-470,



















SI 1-475,













Withdrawing from 40 CFR Part





SI 1-476,

SUBPART

K

WITHDRAWAL

678

1

A

262 Subpart K

SI-10-D

Required

SI 1-540













Include this Information in the



















National Hazardous Waste







INCLUDE

IN

NATIONAL REPORT

679

1

A

Report



Required

SI 1-480

NOTES

680

1000

A

Comments / Notes

SI-13



SI 1-277

Total Record Length:

1679



February 2015

A-6

File Specification Guide


-------
Sll Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

Sll-010

The first two characters of the EPA ID must match the
state code for which data is being submitted.

SUBSTR(HANDLER_ID,1,2) = state postal code of submission

Sll-015

Handler ID must be at least four characters and no more
than twelve characters.

LENGTH(HANDLERJD) >= 4 and LENGTH(HANDLER_ID <= 12

Sll-016

Receive Date must be greater than January 1, 2015 and no
later than today.

RECEIVE_DATE >= '20150101' and RECEIVE_DATE <= today

Sll-020

Handler Name must be provided.

HANDLER NAME <> "

Sll-030

Location Streetl must be provided.

LOCATION STREETlo"

Sll-040

Location City must be provided.

LOCATION CITY <> ''



If Location Country equals 'US' or blank and Handler ID
does not begin with 'NN' then Location State must equal
the first two characters of the Handler ID.

If LOCATION_COUNTRY = 'US' or'' and SUBSTR(HANDLER_ID,1,2)
<> 'NN' Then LOCATION_STATE = SUBSTR(HANDLER_ID,1,2)

Sll-050

If Location Country equals 'US' or blank and Handler ID
begins with 'NN' then Location State must equal a state
postal code in LU_STATE.

If LOCATION_COUNTRY = 'US' or'' and SUBSTR(HANDLER_ID, 1,2)
= 'NN' Then LOCATION_STATE = state postal code in LU_STATE

Sll-060

If Location Country does not equal 'US' or blank, then
Location State must equal a foreign state in
LU FOREIGN STATE or blank.

If LOCATION_COUNTRY <> 'US' or'' Then LOCATION_STATE =
foreign state in LU_FOREIGN_STATE or''

Sll-070

Location Zip must be provided.

LOCATION ZIP <> "

Sll-080

If Location Country equals 'US' or blank, then Location
County must equal a county code in LU_COUNTY.

If LOCATION_COUNTRY = 'US' or'' Then COUNTY_CODE = county
code in LU COUNTY

Sll-085

If Location Country does not equal 'US' or blank, then
Location County must be blank.

If LOCATION_COUNTRY <> 'US' or'' Then LOCATION_COUNTY = ''

Sll-090

Location Country must equal a country code in
LU_COUNTRY or blank. If Location Country is blank, a
value of 'US' will be assumed.

LOCATION_COUNTRY = country code in LU_COUNTRY or''

February 2015

A-7

File Specification Guide


-------
Sll Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

Sll-095

State District must equal an implementer-defined value in
LU STATE DISTRICT or blank.

STATE_DISTRICT = implementer-defined value in
LU STATE DISTRICT or STATE DISTRICT =".

Sll-100

Mail Streetl must be provided.

MAIL STREETlo"

Sll-110

Mail City must be provided.

MAIL CITY <> ''

SI 1-120

If Mail Country equals 'US' or blank, then Mail State must
equal a state postal code in LU_STATE.

If MAIL_COUNTRY = 'US' or'' Then MAIL_STATE = state postal
code in LU STATE

SI 1-130

If Mail Country does not equal 'US' or blank, then Mail
State must equal a foreign state in LU_FOREIGN_STATE or
blank.

If MAIL_COUNTRY <> 'US' or'' Then MAIL_STATE = foreign state in
LU FOREIGN STATE or "

Sll-140

Mail Zip must be provided.

MAIL ZIP <> ''

SI 1-150

Mail Country must equal a country code in LU_COUNTRY
or blank. If Mail Country is blank, a value of 'US' will be
assumed.

MAIL_COUNTRY = country code in LU_COUNTRY or''

Sll-160

Land Type must equal 'P', 'C', 'D', 'F', 'I', 'M', 'S', or 'O'.

LAND TYPE = 'P' or 'C' or 'D' or 'F' or 'I' or 'M' or'S' or 'O'

Sll-170

Contact First Name must be provided.

CONTACT FIRST NAME <> "

Sll-180

Contact Last Name must be provided.

CONTACT LAST NAME <> "

Sll-190

If Contact Country equals 'US' or blank, then Contact State
must equal a state post code in LU_STATE or blank.

If CONTACT_COUNTRY = 'US' or'' Then CONTACT_STATE = state
postal code in LU_STATE or''

Sll-200

If Contact Country does not equal 'US' or blank, then
Contact State must equal a foreign state in
LU FOREIGN STATE or blank.

If CONTACT_COUNTRY <> 'US' or'' Then CONTACT_STATE =
foreign state in LU_FOREIGN_STATE or''

Sll-210

Contact Country must equal a country code in
LU_COUNTRY or blank. If Contact Country is blank, a value
of 'US' will be assumed.

CONTACT_COUNTRY = country code in LU_COUNTRY or''

SI 1-220

Contact Phone must be provided.

CONTACT_PHONE <> ''

Sll-240

Federal Waste Generator Status must equal a
headquarter-defined generator status in
LU_G E N E RATO R_STATUS.

FED_WASTE_GENERATOR = headquarter-defined generator status
in LU_GENERATOR_STATUS

February 2015

A-8

File Specification Guide


-------
Sll Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

Sll-260

State Waste Generator Status must equal a implementer-
defined generator status in LU_GENERATOR_STATUS.

STATE_WASTE_GENERATOR = implementer-defined generator
status in LU GENERATOR STATUS

Sll-270

Short Term Generator must equal 'Y' or 'N'.

SHORT TERM GENERATOR = 'Y' or 'N'

SI 1-275

If Short Term Generator equals Y, then Federal Waste
Generator Status cannot equal 'N'.

If SHORT_TERM_GENERATOR = Y Then FED_WASTE_GENERATOR

<> 'N'

SI 1-277

If Short Term Generator equals 'Y', then Notes must be
provided.

If SHORT TERM GENERATOR = Y Then NOTES <> ''

Sll-280

Importer Activity must equal 'Y' or 'N'.

IMPORTER ACTIVITY = Y or 'N'

Sll-290

Mixed Waste Generator must equal 'Y' or 'N'

MIXED WASTE GENERATOR = T or 'N'

SI 1-295

If Mixed Waste Generator equal 'Y' Then Federal Waste
Generator Status cannot equal 'N'.

If MIXED_WASTE_GENERATOR = Y Then
FED WASTE GENERATOR <> 'N'

Sll-300

Transporter Activity must equal 'Y' or 'N'

TRANSPORTER ACTIVITY = Y or 'N'

SI 1-310

Transfer Facility must equal 'Y' or 'N'

TRANSFER FACILITY = 'Y' or 'N'

SI 1-320

TSD Activity must equal 'Y' or 'N'

TSD ACTIVITY = 'Y' or 'N'

SI 1-330

Recycler Activity must equal 'Y' or 'N'

RECYCLER ACTIVITY = Y or 'N'

Sll-340

Small Quantity On-Site Burner Exemption must equal 'Y' or

'N'

ONSITE BURNER EXEMPTION = T or 'N'

SI 1-350

Smelting, Melting, and Refining Furnace Exemption must
equal Y or 'N'

FURNACE EXEMPTION = 'Y' or 'N'

Sll-360

Underground Injection Control must equal Y or 'N'

UNDERGROUND INJECTION ACTIVITY = T or 'N'

SI 1-362

Received Hazardous Waste from Off-site must equal Y or

'N'

OFF SITE RECEIPT = T or 'N'

SI 1-365

Destination Facility for Universal Waste must equal 'Y' or

'N'

UNIVERSAL_WASTE_DEST_FACILITY = Y or 'N'

Sll-370

Used Oil Transporter must equal Y or 'N'

USED_OIL_TRANSPORTER = Y or 'N'

Sll-380

Used Oil Transfer Facility must equal 'Y' or 'N'

USED_OIL_TRANSFER_FACILITY = Y or 'N'

Sll-390

Used Oil Processor must equal 'Y' or 'N'

USED_OIL_PROCESSOR = Y or 'N'

Sll-400

Used Oil Re-refiner must equal Y or 'N'

USED_OIL_REFINER = Y or 'N'

February 2015

A-9

File Specification Guide


-------
Sll Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

Sll-410

Off-Specification Used Oil Burner must equal 'Y' or 'N'

USED OIL BURNER = Y or'N'



Marketer Who Directs Shipment of Off-Specification Used





Oil to Off-Specification Used Oil Burner must equal 'Y' or



Sll-420

'N'

USED OIL MARKET BURNER = Y or'N'



Marketer Who First Claims the Used Oil Meets the



Sll-430

Specifications must equal 'Y' or 'N'

USED OIL SPEC MARKETER = Y or'N'



Opting into or currently operating under 40 CFR Part 262



SI 1-440

Subpart K as a College or University must equal 'Y' or 'N'

SUBPART K COLLEGE = Y or 'N'



Opting into or currently operating under 40 CFR Part 262



Sll-450

Subpart K as a Teaching Hospital must equal 'Y' or 'N'

SUBPART K HOSPITAL ='Y'or'N'



Opting into or currently operating under 40 CFR Part 262





Subpart K as a Non-profit Research Institute must equal 'Y'



Sll-460

or'N'

SUBPART K NONPROFIT = 'Y'or'N'



Withdrawing from 40 CFR Part 262 Subpart K must equal



Sll-470

Y or 'N'

SUBPART K WITHDRAWAL ='Y'or'N'



If Withdrawing from 40 CFR Part 262 Subpart K equals 'Y'





then Opting into or currently operating under 40 CFR Part





262 Subpart K as a College or University must equal 'N'





and Opting into or currently operating under 40 CFR Part

If SUBPART_K_WITHDRAWAL = 'Y' Then



262 Subpart K as a Teaching Hospital must equal 'N' and

SUBPART_K_COLLEGE = 'N' and



Opting into or currently operating under 40 CFR Part 262

SUBPART_K_HOSPITAL = 'N' and

Sll-475

Subpart K as a Non-profit Research Institute must equal 'N'

SUBPART_K_NON PROFIT = 'N'



Include this Information in the National Hazardous Waste



Sll-480

Report must equal 'Y' or 'N'

INCLUDE_IN_NATIONAL_REPORT = 'Y' or 'N'



For each handler in Sll, one NAICS record must exist in SI3

For each HANDLERJD in Sll there must be a record in SI3 where

Sll-490

where the NAICS Sequence equals 1.

NAICS_SEQ = 1.



For each handler in Sll, one certification record must exist

For each HANDLERJD in Sll there must be a record in SI7 where

Sll-500

in SI7 where the Certification Sequence equals 1.

CERT_SEQ = 1.

February 2015

A-10

File Specification Guide


-------
Sll Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

SI 1-510

For each handler in Sll, at least one owner record must
exist in SI2 where the Owner / Operator Indicator equals
'CO' and at least one operator record must exist in SI2
where the Owner / Operator Indicator equals 'CP'.

For each HANDLERJD in Sll there must be a record in SI2 where
OWNER_OPERATOR_INDICATOR = 'CO' and a record in SI2 where
OWNER OPERATOR INDICATOR ='CP'

SI 1-520

If Federal Generator Status equals '1', '2', or '3', or TSD
Activity equals 'Y' or Recycler Activity equals 'Y' or Small
Quantity On-Site Burner Exemption equals 'Y' or Smelting,
Melting, and Refining Furnace Exemption equals 'Y', then
one waste code record must exist in SI4 or SI5.

If FED_WASTE_GENERAT0R = '1' or '2' or '3'
or TSD_ACTIVITY = 'Y'
or RECYCLER_ACTIVITY = 'Y'
or ONSITE_BURNER_EXEMPTION = 'Y'

or FURNACE_EXEMPTION = 'Y' Then there must be a record in SI4
or SI5 where HANDLER ID in SI4 or SI5 = HANDLER ID in Sll.

SI 1-530

If Location Country does not equal 'US' or blank Then HSM
data cannot be provided.

If LOCATION_COUNTRY <> 'US' or'' Then there cannot be a record
in SI9 where HANDLER ID in Sll = HANDLER ID in SI9.

Sll-540

If Location Country does not equal 'US' or blank then the
following activities must equal 'N': Federal Generator
Status, Importer Activity, Short-Term Generator, Mixed
Waste Generator, Transfer Facility, TSD Activity, Recycler
Activity, On-site Burner Exemption, Furnace Exemption,
Underground Injection Activity, Universal Waste
Destination Facility, Used Oil Burner, Used Oil Transfer
Facility, Used Oil Processor, Used Oil Refiner, Used Oil
Specification Marketer, Used Oil Fuel Marketer, Subpart K-
College, Subpart K-Hospital, Subpart K-Non-profit, and
Subpart K-Withdrawal.

If LOCATION_COUNTRY <> 'US' or'' Then
FED_WASTE_GENERAT0R = 'N' AND 1MPORTER_ACTIVITY = 'N'
AND SHORT_TERM_GENERATOR = 'N" AND
MIXED_WASTE_GENERAT0R = 'N' AND TRANSFER_FACILITY = 'N'
AND TSD_ACTIVITY = 'N' AND RECYCLER_ACTIVITY = 'N' AND
ONSITE_BURNER_EXEMPTION = 'N' AND FURNACE_EXEMPTION =
'N' AND UNDERGROUND J NJECTION_ACTIVITY = 'N' AND
UNIVERSAL_WASTE_DEST_FACILITY = 'N' AND USED_OIL_BURNER
= 'N' AND USED_OIL_TRANSFER_FACILITY = 'N' AND
USED_OIL_PROCESSOR = 'N' AND USED_OIL_REFINER = 'N' AND
USED_OIL_SPEC_MARKETER = 'N' AND SUBPART_K_COLLEGE = 'N'
AND SUBPART_K_HOSPITAL = 'N' AND SUBPART_K_NONPROFIT =
'N' AND SUBPART_K_WITHDRAWAL = 'N'

February 2015

A-11

File Specification Guide


-------
FLAT FILE ID#-SI 2

Source Form: Site ID Description: Owner/Operator Name and Address







This file reports the owner and operator name and address for each site. The relationship of these data records to the reported site is n: 1, that
is, there can be multiple owner and operator names and addresses for each site.

Key Fields: Handler ID (HANDLERJD); Owner/Operator Sequence Number (OWNER_OPERATOR_SEQ). Each record in the SI2 file must contain a
unique combination of the Handler ID and Owner/Operator Sequence Number.

Note: The SI2file is REQUIRED. At least two records must be provided for each handler - one record for the current owner and one record for the
current operator.

Field Name

Starting
Column

Field
Length

Data
Type

Description

Location
on Form

Required /

Cond.
Required

Edit
Number(s)

HANDLER ID

1

12

A

EPA Identification Number

SI-2

Required

SI2-010

OWNER OPERATOR SEQ

13

6

1

Owner/Operator Sequence
Number



Required

SI2-020

OWNER OPERATOR INDICATOR

19

2

A

Owner/Operator Indicator



Required

SI2-030

OWNER OPERATOR NAME

21

40

A

Owner/Operator Name

SI-9

Required

SI2-040

DATE BECAME CURRENT

61

8

Date

Date the Owner/Operator
Became Current

SI-9



SI2-050

0 W N E R_0 P E R ATO R_TYPE

69

1

A

Owner/Operator Type

SI-9

Required

SI2-060

STREET_NO

70

12

A

Owner/Operator Street Number

SI-9





STREET1

82

30

A

Owner/Operator Street 1

SI-9





STREET2

112

30

A

Owner/Operator Street 2

SI-9





CITY

142

25

A

Owner/Operator City

SI-9





STATE

167

2

A

Owner/Operator State

SI-9



SI2-070,
SI2-080

ZIP

169

14

A

Owner/Operator Zip

SI-9





February 2015

A-12

File Specification Guide


-------












Required /





Starting

Field

Data



Location

Cond.

Edit

Field Name

Column

Length

Type

Description

on Form

Required

Number(s)















SI2-070,















SI2-080,

COUNTRY

183

2

A

Owner/Operator Country

SI-9



SI2-090

PHONE

185

15

A

Owner/Operator Phone Number

SI-9





NOTES

200

240

A

Comments / Notes







Total Record Length:

439



February 2015

A-13

File Specification Guide


-------
SI2 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

SI2-010

Handler ID must exist in Sll

HANDLER ID must exist in Sll

SI2-020

Owner / Operator Sequence must be greater than zero.

OWNER OPERATOR SEQ>0

SI2-030

Owner / Operator Indicator must equal 'CO' or 'CP'.

OWNER OPERATOR INDICATOR ='CO'or'CP'

SI2-040

Owner / Operator Name must be provided.

OWNER OPERATOR NAME <> "

SI2-050

Date the Owner /Operator Became Current must be a
valid date greater than or equal to January 1, 1600 or
blank.

DATE BECAME CURRENT >='16000101'or "

SI2-060

Owner / Operator Type must equal 'C', 'D', 'F', T, 'M',
'S', or '0'.

OWNER_0PERATOR_TYPE = 'P' or 'C' or 'D' or 'F' or '1' or 'M' or'S'
or 'O'

SI2-070

If Owner / Operator Country equals 'US' or blank, then
Owner / Operator State must equal a state postal code in
LU_STATE or blank.

If COUNTRY = 'US' or'' Then STATE = state postal code in
LU_STATE or''

SI2-080

If Owner / Operator Country does not equal 'US' or blank,
then Owner / Operator State must equal a foreign state in
LU_FOREIGN_STATE or blank.

If COUNTRY <> 'US' or'' Then STATE = foreign state in
LU_FOREIGN_STATE or''

SI2-090

Owner / Operator Country must equal a country code in
LU_COUNTRY or blank. If Owner / Operator Country is
blank, a value of 'US' will be assumed.

COUNTRY = country code in LU_COUNTRY or''

February 2015

A-14

File Specification Guide


-------
FLAT FILE ID#-SI 3

Source Form: Site ID Description: North American Industry Classification System Codes for the Site





This file captures the information contained in Item 6 of the Site ID form. The relationship of these data records to the reported site is n: 1, that

is, there can be multiple NAICS for each site.













Key Fields: Handler ID (HANDLERJD); NAICS Sequence Number (NAICS_SEQ). Each record in the SI3 file must contain a unique combination of

the Handler ID and NAICS Sequence Number.













Note: The SI3file is REQUIRED. At least one record with a sequence number of 1 (indicating the primary NAICS) must be provided for each

handler.



























Required /





Starting

Field

Data



Location

Cond.

Edit

Field Name

Column

Length

Type

Description

on Form

Required

Number(s)

HANDLERJD

1

12

A

EPA Identification Number

SI-2

Required

SI3-010

NAICS_SEQ

13

4

1

NAICS Sequence Number



Required

SI3-020

NAICS_CODE

17

6

A

NAICS Code

SI-6

Required

SI3-030

Total Record Length:

22



February 2015

A-15

File Specification Guide


-------
SI3 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

S13-010

Handler ID must exist in SI1.

HANDLER ID must exist in SI1

SI3-020

NAICS Sequence must be greater than zero.

NAICS SEQ > 0

SI3-030

NAICS Code must equal a headquarters-defined NAICS code in
LU NAICS.

NAICS CODE = headquarters-defined NAICS code in LU NAICS.

February 2015

A-16

File Specification Guide


-------
FLAT FILE ID#-SI4

Source Form: Site ID Description: EPA Hazardous Waste Codes







This file captures the information contained in Item 11-A of the Site ID form. The relationship of these data records to the reported site is n: 1,

that is, there can be multiple waste codes for each site.











Key Fields: Handler ID (HANDLERJD); EPA Waste Code (EPA_WASTE_CODE). Each record in the SI4 file must contain a unique combination of

the Handler ID and EPA Waste Code.















Note: The SI4file is REQUIRED for handlers that have generation (LQG, SQG, or CESQG), TSD, Recycler, or Exempt Boiler and/or Industrial Furnace

activities.



























Required /





Starting

Field

Data



Location

Cond.

Edit

Field Name

Column

Length

Type

Description

on Form

Required

Number(s)

HANDLERJD

1

12

A

EPA Identification Number

SI-2

Required

SI4-010









Waste Code for Federally-







EPA_WASTE_CODE

13

4

A

Regulated Hazardous Wastes

SI-ll-A

Required

SI4-020

Total Record Length:

16



February 2015

A-17

File Specification Guide


-------
SI4 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

S14-010

Handler ID must exist in SI1.

HANDLER ID must exist in SI1

SI4-020

EPA Waste Code must equal a headquarters-defined waste code in
LU WASTE CODE.

EPA WASTE CODE = headquarters-defined waste code in
LU WASTE CODE.

February 2015

A-18

File Specification Guide


-------
FLAT FILE ID#-SI 5

Source Form: Site ID Description: State Hazardous Waste Codes







This file captures the information contained in Item 11-B of the Site ID form. The relationship of these data records to the reported site is n:l,
that is, there can be multiple waste codes for each site.

Key Fields: Handler ID (HANDLERJD); State Waste Code (STATE_WASTE_CODE). Each record in the SI5 file must contain a unique combination
of the Handler ID and State Waste Code.

Note: The SI5file is NOT REQUIRED. The edits for this file apply only if you provide data for this file.







Field Name

Starting
Column

Field
Length

Data
Type

Description

Location
on Form

Required /

Cond.
Required

Edit
Number(s)

HANDLERJD

1

12

A

EPA Identification Number

SI-2

Required

SI5-010

STATE_WASTE_CODE

13

6

A

Waste Code for State-Regulated
Hazardous Waste

SI-ll-B

Required

SI5-020

Total Record Length:

18



February 2015

A-19

File Specification Guide


-------
SI5 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

SI5-010

Handler ID must exist in SI 1.

HANDLERJD must exist in Sll

SI5-020

State Waste Code must equal an implementer-defined
waste code in LU_WASTE_CODE.

STATE_WASTE_CODE = implementer-defined waste code in
LU_WASTE_CODE.

February 2015

A-20

File Specification Guide


-------
FLAT FILE ID#-SI 6

Source Form: Site ID Description: Universal Waste Activities







This file captures the information contained in Item 10-B-l of the Site ID form. The relationship of these data records to the reported site is n: 1,
that is, there can be multiple universal wastes for each site.

Key Fields: Handler ID (HANDLERJD); Universal Waste Owner (UN1VERSAL_WASTE_0WNER); Universal Waste (UNIVERSAL_WASTE).
Each record in the SI6 file must contain a unique combination of the Handler ID, Universal Waste Owner, and Universal Waste.



If the Universal Waste is a headquarters-defined universal waste (i.e., lamps, batteries, pesticides, or mercury containing equipment), the
Universal Waste Owner will be equal to 'HQ'.

If the Universal Waste is an implementer-defined universal waste, the Universal Waste Owner will be equal to the State of submission.

Note: The SI6file is REQUIRED for handlers that accumulated/ managed lamps, batteries, pesticides, or mercury containing equipment.

Field Name

Starting
Column

Field
Length

Data
Type

Description

Location
on Form

Required /

Cond.
Required

Edit
Number(s)

HANDLER ID

1

12

A

EPA Identification Number

SI-2

Required

SI6-010

UNIVERSAL_WASTE_OWNER

13

2

A

Universal Waste Owner



Required

SI6-020,
SI6-040,
SI6-050,
SI6-060,
SI6-070

UNIVERSAL_WASTE

15

1

A

Universal Waste

SI-10-B-1

Required

SI6-030

GENERATED

16

1

A

Generated





SI6-060

ACCUMULATED

17

1

A

Accumulated / Managed

SI-10-B-1

Required

SI6-040,
SI6-050,
SI6-070

Total Record Length:

17



February 2015

A-21

File Specification Guide


-------
SI6 Flat File Edit Specifications

Edit

Number

Edit Description

Select Logic

SI6-010

Handler ID must exist in SI 1.

HANDLER ID must exist in Sll

SI6-020

Universal Waste Owner must equal 'HQ' or the State of
submission.

UNIVERSAL WASTE OWNER ='HQ'or State of submission

SI6-030

Universal Waste Type must equal a headquarters or
implementer-defined universal waste type in
LU UNIVERSAL WASTE.

UNIVERSAL_WASTE_TYPE = headquarter or implementer-defined
universal waste type in LU_UNIVERSAL_WASTE

SI6-040

If Universal Waste Owner equals 'HQ' then Accumulated /
Managed must equal 'Y'

If UNIVERSAL_WASTE_OWNER = 'HQ' Then ACCUMULATED = Y

SI6-050

If Universal Waste Owner equals State of submission then
Accumulated / Managed must equal 'Y' or 'N'

If UNIVERSAL_WASTE_OWNER = State of submission Then
ACCUMULATED ='Y' or 'N'

SI6-060

If Universal Waste Owner equals state of submission then
Generated must equal 'Y' or 'N'

If UNIVERSAL_WASTE_OWNER = State of submission Then
GENERATED = 'Y' or 'N'

SI6-070

If Universal Waste Owner equals State of submission then
Accumulated / Managed must equal 'Y' or Generated must
equal Y

If UNIVERSAL_WASTE_OWNER = state of submission Then
ACCUMULATED = 'Y' or GENERATED = 'Y'

Note: If the Universal Waste Type is headquarters-defined, then the Generated field will be set to null, regardless of the value provided by the
submitter.

February 2015

A-22

File Specification Guide


-------
FLAT FILE ID#-SI 7

Source Form: Site ID Description: Site Identification Form Certification







This file captures the information contained in Iteml4 of the Site ID form. The relationship of these data records to the reported site is n: 1, that
is, there can be multiple certifications for each site.

Key Fields: Handler ID (HANDLERJD); Certification Sequence Number (CERT_SEQ). Each record in the SI7 file must contain a unique
combination of the Handler ID and Certification Sequence Number.



Note: The SI7file is REQUIRED. At least one record must be provided for each handler.







Field Name

Starting
Column

Field
Length

Data
Type

Description

Location
on Form

Required /

Cond.
Required

Edit
Number(s)

HANDLERJD

1

12

A

EPA Identification Number

SI-2

Required

SI7-010

CERT_SEQ

13

6

1

Certification Sequence Number



Required

SI7-020

CERT_FIRST_NAME

19

15

A

Certification First Name

SI-14

Required

SI7-030

CERT_MIDDLE_INITIAL

34

1

A

Certification Middle Initial

SI-14





CERT_LAST_NAME

35

15

A

Certification Last Name

SI-14

Required

SI7-040

CERTJITLE

50

45

A

Certification Title

SI-14

Required

SI7-050

CERT_SIGNED_DATE

95

8

Date

Date Certification was Signed

SI-14

Required

SI7-060

Total Record Length:

102



February 2015

A-23

File Specification Guide


-------
SI7 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

SI7-010

Handler ID must exist in SI 1.

HANDLERJD must exist in Sll

SI7-020

Certification Sequence must be greater than zero.

CERT_SEQ > 0

SI7-030

Certification First Name must be provided.

CERT_FIRST_NAME <> "

SI7-040

Certification Last Name must be provided.

CERT_LAST_NAME <> ''

SI7-050

Certification Title must be provided.

CERT_TITLE <> ''

SI7-060

Date Certification was Signed must be a valid date greater
than or equal to January 1, 2015 and less than today.

CERT_SIGNED_DATE >= '20150101' and CERT_SIGNED_DATE <=
Today

February 2015

A-24

File Specification Guide


-------
FLAT FILE ID#-SI8

Source Form: Site ID Description: State-Specific Activities







This file reports the state-specific activities for each site. Although not on the EPA Form 8700-13A/B, this file available for States who wish to report this

information. The relationship of these data records to the reported site is n: 1, that is, there can be state activities for each site.





Key Fields: Handler ID (HANDLERJD); State Activity (STATE_ACTIVITY). Each record in the SI8 file must contain a unique combination of the Handler ID and

State Activity.















Note: The SI8file is NOT REQUIRED. The edits for this file apply only if you provide data for this file.



















Required /





Starting

Field

Data



Location

Cond.

Edit

Field Name

Column

Length

Type

Description

on Form

Required

Number(s)

HANDLERJD

1

12

A

EPA Identification Number

SI-2

Required

SI8-010

STATE_ACTIVITY

13

5

A

State Activity



Required

SI8-020

Total Record Length:

17



February 2015

A-25

File Specification Guide


-------
SI8 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

SI8-010

Handler ID must exist in SI 1.

HANDLERJD must exist in Sll

SI8-020

State Activity must equal an implementer-defined state
activity in LU_STATE_ACTIVITY.

STATE_ACTIVITY = implementer-defined state activity in
LU_STATE_ACTIVITY.

February 2015

A-26

File Specification Guide


-------
FLAT FILE ID#-SI 9

Source Form: Site ID Description: Hazardous Secondary Material Basic Information







This file captures the information contained in Items 1 and 3 of the Addendum to the Site ID form. The relationship of these data records to the
reported site is 1:1, that is, there can only be one record for each site.

Key Fields: Handler ID (HANDLERJD. Each record in the SI9 file must contain a unique Handler ID.







Note: The SI9file is REQUIRED for handlers that will manage, are managing, or have stopped managing hazardous secondary material under 40
CFR 261.2(a)(2)(H), 261.4(a)(23), (24), or (25).

Field Name

Starting
Column

Field
Length

Data
Type

Description

Location
on Form

Required /

Cond.
Required

Edit
Number(s)

HANDLERJD

1

12

A

EPA Identification Number

SI-2

Required

SI9-010,
SI9-050

REASON_FOR_NOTIFICATION

13

1

A

Reason for Notification

ADD-1

Required

SI9-020,
SI9-030

HSM_EFFECTIVE_DATE

14

8

Date

Hazardous Secondary Material
Effective Date

ADD-1

Cond.
Required

SI9-030

HSM_FA

22

1

A

Hazardous Secondary Material
Financial Assurance

ADD-3

Required

SI9-040

Total Record Length:

22



February 2015

A-27

File Specification Guide


-------
SI9 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

SI9-010

Handler ID must exist in SI 1.

HANDLER ID must exist in Sll

SI9-020

Reason for Notification must equal T, 'R', or'S'

REASON FOR NOTIFICATION ='1'or'R'or'S'



If Reason for Notification equals T or'S' then Hazardous
Secondary Material Effective Date must be greater than
December 29, 2008

If REASON_FOR_NOTIFICATION = '1' or'S' Then
HSM_EFFECTIVE_DATE >= '20081229'

SI9-030

If Reason for Notification equals 'R' then Hazardous
Secondary Material Effective Date must be blank

If REASON_FOR_NOTIFICATION = 'R' Then
HSM EFFECTIVE DATE = blank



If Facility Code in SIA equals '07', '08', or '11' then
Hazardous Secondary Material Financial Assurance must
equal 'Y' or 'N'

If FACILITY_CODE in SIA = '07' or '08' or '11' Then
HSM_FA = T or 'N'

SI9-040

If Facility Code in SIA does not equal '07', '08', or '11' then
Hazardous Secondary Material Financial Assurance must
equal 'N'

If FACILITY_CODE in SIA <> '07' or '08' or '11' Then
HSM_FA = 'N'

SI9-050

For each handler in SI9, one HSM activity record must exist
in SIA.

For each HANDLERJD in SI9 there must be a record in SIA.

SI9-060

If Reason for Notification equals 'R' or'S' then there must
be a record in HHSM_BASIC5 where Reason for
Notification equals '1'.

If REASON_FOR_NOTIFICATION = 'R' or'S' Then there must be a
record in HHSM_BASIC5 where REASON_FOR_NOTIFICATION = '1'
for this facility.

February 2015

A-28

File Specification Guide


-------
FLAT FILE ID#-SI A

Source Form: Site ID Description: Hazardous Secondary Material Activity







This file captures the information contained in Item 2 of the Addendum to the Site ID form. The relationship of these data records to the
reported site is n: 1, that is, there can be multiple HSM activities for each site.

Key Fields: Handler ID (HANDLERJD); HSM Sequence Number (HSM_SEQ_NUMBER). Each record in the SIA file must contain a unique
combination of the Handler ID and HSM Sequence Number.

Note: The SIA file is REQUIRED for handlers that will manage, are managing, or have stopped managing hazardous secondary material under 40
CFR 261.2(a)(2)(H), 261.4(a)(23), (24), or (25).

Field Name

Starting
Column

Field
Length

Data
Type

Description

Location
on Form

Required /

Cond.
Required

Edit
Number(s)

HANDLER ID

1

12

A

EPA Identification Number

SI-2

Required

SIA-010,
SIA-100

HSM SEQ NUMBER

13

2

1

Hazardous Secondary Material
Sequence Number



Required

SIA-020,
SIA-100

FACILITY_CODE

15

2

A

Facility Code

ADD-2-A

Required

SIA-030

ESTIMATE_SHORT_TONS

17

10

1

Estimated Tons of HSM Managed
Annually

ADD-2-C

Required

SIA-040,
SIA-050

ACTUAL_SHORT_TONS

27

10

1

Actual Tons of HSM Managed
Annually

ADD-2-D

Required

SIA-060,
SIA-070,
SIA-080

LAND_BASED_UNIT

37

2

A

Land-based Unit Code

ADD-2-E

Required

SIA-090

Total Record Length:

38



February 2015

A-29

File Specification Guide


-------
SIA Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

SIA-010

Handler ID must exist in SI9.

HANDLER ID must exist in SI9

SIA-020

HSM Sequence Number must be greater than zero.

HSM SEQUENCE NUMBER >0



Facility Code must equal a headquarters-defined facility

FACILITY_CODE = headquarters-defined facility code in

SIA-030

code in LU HSM FACILITY CODE.

LU HSM FACILITY CODE.



If Reason For Notification equals T or 'R' then Estimated





Tons of HSM Managed Annually must be greater than

If REASON_FOR_NOTIFICATION = 'N' or 'R' Then

SIA-040

zero.

ESTIMATE SHORT TONS > 0



If Reason for Notification equals 'S' then Estimated Tons of

If REASON FOR NOTIFICATION ='S'Then ESTIMATE SHORT TONS

SIA-050

HSM Managed Annually must equal zero.

= 0



If Reason for Notification equals 'R' then Actual Tons of





HSM Managed Annually must be greater than or equal to

If REASON_FOR_NOTIFICATION = 'R' Then ACTUAL_SHORT_TONS

SIA-060

zero.

>=0



If Reason for Notification equals T then Actual Tons of

If REASON_FOR_NOTIFICATION = '1' Then ACTUAL_SHORT_TONS =

SIA-070

HSM Managed Annually must equal zero.

0



If Reason for Notification equals 'S' then Actual Tons of





HSM Managed Annually must be greater than or equal to

If REASON_FOR_NOTIFICATION = 'S' Then ACTUAL_SHORT_TONS

SIA-080

zero.

>=0

SIA-090

Land-based Unit Code must equal 'NA', 'SI', 'PL', or 'OT'

LAND_BASED_UNIT = 'NA' or 'SI' or 'PL' or 'OT'



For each handler/HSM sequence number in SIA, one HSM

For each HANDLERJD and HSM_SEQ_NUMBER in SIA there must

SIA-100

waste code record must exist in SIB.

be a record in SIB.

February 2015

A-30

File Specification Guide


-------
FLAT FILE ID#-SIB

Source Form: Site ID Description: Hazardous Secondary Material Waste Codes







This file captures the information contained in Item 2.C of the Addendum to the Site ID form. The relationship of these data records to the

reported site is n: 1, that is, there can be multiple waste codes for each site / HSM sequence number.







Key Fields: Handler ID (HANDLERJD); HSM Sequence Number (HSM_SEQUENCE_N UMBER), Waste Code (WASTE_CODE). Each record in the SIB

file must contain a unique combination of the Handler ID, HSM Sequence Number, and Waste Code.







Note: The SIB file is REQUIRED for handlers that will manage, are managing, or have stopped managing hazardous secondary material under 40

CFR 261.2(a)(2)(H), 261.4(a)(23), (24), or (25).

























Required /





Starting

Field

Data



Location

Cond.

Edit

Field Name

Column

Length

Type

Description

on Form

Required

Number(s)

HANDLERJD

1

12

A

EPA Identification Number

SI-2

Required

SIB-010









Hazardous Secondary Material







HSM_SEQ_N UMBER

13

2

1

Sequence Number



Required

SIB-010

WASTE_CODE

15

4

A

EPA Hazardous Waste Code

ADD-2-C

Required

SIB-020

Total Record Length:

18



February 2015

A-31

File Specification Guide


-------
SIB Flat File Edit Specifications

Edit

Number

Edit Description

Select Logic

SIB-010

Handler ID and HSM Sequence Number must exist in SIA.

HANDLERJD and HSM_SEQ_NUMBER must exist in SIA

SIB-020

Waste Code must equal a headquarters-defined waste code
in LU_WASTE_CODE.

WASTE_CODE = headquarters-defined waste code in
LU_WASTE_CODE.

February 2015

A-32

File Specification Guide


-------
FLAT FILE ID#-GM1

Source Form: GM Description: Waste Generation and Management Information







This file captures data elements that have 1:1 relationship to the reported waste. These data elements are as follows
through l.G.

: GM Items l.A

, and l.D

Key Fields: Handler ID (HANDLERJD); Page Number (HZ_PG). Each record in the GM1 file must contain a unique combination of the Handler ID
and Page Number.

Note: The GM1 file is REQUIRED for handlers that generated RCRA hazardous waste that, in 2015, was accumulated on-site; managed on-site in
a treatment, storage, or disposal unit; and/or shipped off-site for management

Field Name

Starting
Column

Field
Length

Data
Type

Description

Location
on Form

Required /

Cond.
Required

Edit
Number(s)

HANDLER ID

1

12

A

EPA Identification Number



Required

GM1-010,
GM1-190

HZ PG

13

5

1

Page Number



Required

GM1-020,
GM1-190

FORM CODE

18

4

A

Waste Form Code

GM-l-E

Required

GM1-060

UNIT_OF_MEASURE

22

1

A

Unit of Measure

GM-l-F

Required

GM1-080,
GM1-090,
GM1-100

WST_DENSITY

23

6

D3.2

Density

GM-l-F

Cond.
Required

GM1-090

DENSITY_UNIT_OF_MEASURE

29

1

A

Density Unit of Measure

(1 = lbs/gal; 2 = specific gravity)

GM-l-F

Cond.
Required

GM1-100

MANAGEMENT_METHOD

30

4

A

Management Method (for source
code 'G25" only)

GM-l-D

Cond.
Required

GM1-050

WASTE_MIN_CODE

34

1

A

Waste Minimization Indicator

GM-l-G

Required

GM1-110

February 2015

A-33

File Specification Guide


-------












Required /





Starting

Field

Data



Location

Cond.

Edit

Field Name

Column

Length

Type

Description

on Form

Required

Number(s)















GM1-040,















GM1-050,















GM1-055,

SOURCE CODE

35

3

A

Source Code

GM-l-D

Required

GM1-056









Quantity Generated in Reporting





GM1-055,

GEN QTY

38

18

D11.6

Year

GM-l-F

Required

GM1-070









Include Information in the







INCLUDE IN NATIONAL REPORT

56

1

A

National Hazardous Waste Report



Required

GM1-180

DESCRIPTION

57

240

A

Waste Stream Description

GM-l-A

Required

GM1-030











Bottom





NOTES

297

240

A

Comments/Notes

of form



















GM1-120,









Was this Waste Stream Managed





GM1-130,

ON SITE MANAGEMENT

537

1

A

On-Site

GM-2

Required

GM1-140















GM1-150,









Was this Waste Stream Shipped





GM1-160,

OFF SITE SHIPMENT

538

1

A

Off-Site

GM-3-A

Required

GM1-170

Total Record Length:

538



February 2015

A-34

File Specification Guide


-------
GM1 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

GM1-010

Handler ID must exist in SI 1.

HANDLER ID must exist in Sll

GM1-020

Page Number must be greater than zero.

HZ PG > 0

GM1-030

Waste Stream Description must be provided.

DESCRIPTION <> "

GM1-040

Source Code must equal a headquarter-defined source
code in LU SOURCE CODE.

SOURCE_CODE = headquarter-defined source code in
LU SOURCE CODE

GM1-050

If Source Code equals 'G25' then Management Method
must equal a headquarter-defined management method
in LU_MANAGEMENT_METHOD else Management
Method must equal ''

If SOURCE_CODE = 'G25' Then MANAGEMENT_METHOD =
headquarter-defined management method in
LU _M AN AG E M E NT_M ETH 0 D
Else MANAGEMENT METHOD = "

GM1-055

If Source Code equals 'G17' then Quantity Generated must
equal zero.

If SOURCE CODE = 'G17'Then GEN QTY = 0.

GM1-056

If Source Code equals 'G17' then handler must have opted
into the Subpart K rule.

If SOURCE_CODE = 'G17' Then SUBPART_K_COLLEGE in Sll = Y or
SUBPART_K_HOSPITAL in Sll = Y or SUBPART_K_NONPROFIT in
Sll = Y or SUBPART K WITHDRAWAL in Sll = Y.

GM1-060

Form Code must equal a headquarter-defined form code
in LU FORM CODE.

FORM_CODE = headquarter-defined form code in LU_FORM_CODE

GM1-070

Quantity Generated must be greater than or equal to zero.

GEN QTY >= 0

GM1-080

Unit of Measure must equal a headquarter-defined unit of
measure in LU BR UOM.

UNIT_OF_MEASURE = headquarter-defined unit of measure in
LU BR UOM

GM1-090

If Unit of Measure equals '5', '6', or '1', then Density must
be greater than zero else Density must equal 0.

If UNIT_OF_MEASURE = '5' or '6' or'T Then WST_DENSITY > 0
Else WST DENSITY = 0

GM1-100

If Unit of Measure equals '5', '6', or '1', then Density Unit
of Measure must equal a headquarter-defined unit of
measure in LU_DENSITY_UOM else Density Unit of
Measure must equal blank.

If UNIT_OF_MEASURE = '5' or '6' or'T Then
DENSITY_UNIT_OF_MEASURE = headquarter-defined density unit
of measure in LU_DENSITY_UOM
Else DENSITYJJNIT_OF_MEASURE = ''

GM1-110

Waste Minimization must equal a headquarter-defined
waste minimization code in LU_WASTE_MINIMIZATION.

WASTE_MIN_CODE = headquarter-defined waste minimization
code in LU_WASTE_MINIMIZATION

GM1-120

On-Site Management Indicator must equal 'Y' or 'N'

ON_SITE_MANAGEMENT = Y or 'N'

February 2015

A-35

File Specification Guide


-------
GM1 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

GM1-130

If On-Site Management Indicator equals 'Y' then at least
one corresponding record must exist in GM5.

If ON_SITE_MANAGEMENT = Y Then HANDLERJD and HZ_PG in
GM1 must exist in GM5

GM1-140

If On-Site Management Indicator equals 'N' then no
corresponding record may exist in GM5.

If ON_SITE_MANAGEMENT = 'N' Then HANDLERJD and HZPG in
GM1 cannot exist in GM5

GM1-150

Off-Site Management Indicator must equal 'Y' or 'N'

OFF SITE MANAGEMENT = Y or 'N'

GM1-160

If Off-Site Management Indicator equals 'Y' then at least
one corresponding record must exist in GM4.

If OFF_SITE_MANAGEMENT = Y Then HANDLERJD and HZ_PG in
GM1 must exist in GM4

GM1-170

If Off-Site Management Indicator equals 'N' then no
corresponding record may exist in GM4.

If OFF_SITE_MANAGEMENT = 'N' Then HANDLERJD and HZ_PG in
GM1 must exist in GM4

GM1-180

If Include in National Report in the Sll file equals 'N' then
Include in National Report must equal 'N' else Include in
National Report must equal 'N' or 'Y'.

If INCLUDE_IN_NATIONAL_REPORT in Sll= 'N' Then

INCLUDE_IN_NATIONAL_REPORT = 'N'

Else INCLUDE_IN_NATIONAL_REPORT = 'N' or Y

GM1-190

For each handler and page number in GM1, one record
must exist in GM2 or GM3

For each HANDLERJD and HZ_PG in GM1 there must be a record
in GM2 or GM3.

February 2015

A-36

File Specification Guide


-------
FLAT FILE ID#-GM2

Source Form: GM Description: EPA Hazardous Waste Codes







This file captures the information contained in Item l.B of the GM form. The relationship of these data records to the reported waste is n: 1, that

is, there can be multiple waste codes for each reported waste.









Key Fields: Handler ID (HANDLERJD); Page Number (HZ_PG); EPA Waste Code (EPA_WASTE_CODE). Each record in the GM2 file must contain a

unique combination of the Handler ID, Page Number, and EPA Waste Code.







Note: For each waste stream, either EPA Hazardous Waste Code information (GM2) is REQUIRED or State Hazardous Waste Code information

(GM3) is REQUIRED.



























Required /





Starting

Field

Data



Location

Cond.

Edit

Field Name

Column

Length

Type

Description

on Form

Required

Number(s)

HANDLERJD

1

12

A

EPA Identification Number



Required

GM2-010

HZ_PG

13

5

1

Page Number



Required

GM2-010

EPA_WASTE_CODE

18

4

A

EPA Hazardous Waste Code

GM-l-B

Required

GM2-020

Total Record Length:

21



February 2015

A-37

File Specification Guide


-------
GM2 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

GM2-010

Handler ID and Page Number must exist in GM1.

HANDLERJD and HZ_PG must exist in GM1

GM2-020

EPA Waste Code must equal a headquarters-defined waste
code in LU_WASTE_CODE.

EPA_WASTE_CODE = headquarters-defined waste code in
LU_WASTE_CODE.

February 2015

A-38

File Specification Guide


-------
FLAT FILE ID#-GM3

Source Form: GM Description: State Hazardous Waste Codes







This file captures the information contained in Item l.C of the GM form. The relationship of these data records to the reported waste is n:l, that
is, there can be multiple waste codes for each reported waste.

Key Fields: Handler ID (HANDLERJD); Page Number (HZ_PG); State Waste Code (STATE_WASTE_CODE).
contain a unique combination of the Handler ID, Page Number, and State Waste Code.

Each record in the GM3 file must

Note: For each waste stream, either EPA Hazardous Waste Code information (GM2) is REQUIRED or State Hazardous Waste Code information
(GM3) is REQUIRED.

Field Name

Starting
Column

Field
Length

Data
Type

Description

Location
on Form

Required /

Cond.
Required

Edit
Number(s)

HANDLERJD

1

12

A

EPA Identification Number



Required

GM3-010

HZ_PG

13

5

1

Page Number



Required

GM3-010

STATE_WASTE_CODE

18

6

A

State Hazardous Waste Code

GM-l-C

Required

GM3-020

Total Record Length:

23



February 2015

A-39

File Specification Guide


-------
GM3 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

GM3-010

Handler ID and Page Number must exist in GM1.

HANDLERJD and HZ_PG must exist in GM1

GM3-020

State Waste Code must equal an implementer-defined
waste code in LU_WASTE_CODE.

STATE_WASTE_CODE = implementer-defined waste code in
LU_WASTE_CODE.

February 2015

A-40

File Specification Guide


-------
FLAT FILE ID#-GM4

Source Form: GM Description: Off-Site Management Information for the Reported Waste





This file captures off-site treatment information for the reported waste as represented in GM Items 3.B through 3.D.
data records to the reported waste is n: 1, that is, there can be multiple off-site information for each reported waste.

The relationship of these

Key Fields: Handler ID (HANDLERJD); Page Number (HZ_PG); Off-Site Sequence Number (IO_PG_NUM_SEQ). Each record in the GM4 file must
contain a unique combination of the Handler ID, Page Number, and Off-Site Sequence Number.

Note: The GM4file is REQUIRED for handlers that generated RCRA hazardous waste that, in 2015, was shipped off-site for management.

Field Name

Starting
Column

Field
Length

Data
Type

Description

Location
on Form

Required /

Cond.
Required

Edit
Number(s)

HANDLER ID

1

12

A

EPA Identification Number



Required

GM4-010

HZ_PG

13

5

1

Page Number



Required

GM4-010

IO_PG_NUM_SEQ

18

5

1

Off-Site Sequence Number



Required

GM4-020

MANAGEMENT_METHOD

23

4

A

Management Method

GM-3-C

Required

GM4-040

IO_TDR_ID

27

12

A

EPA ID Number of the Facility to
which Waste was Shipped

GM-3-B

Required

GM4-030

IO_TDR_QTY

39

18

D11.6

Total Quantity Shipped to EPA ID
in Current Reporting Year

GM-3-D

Required

GM4-050

Total Record Length:

56



February 2015

A-41

File Specification Guide


-------
GM4 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

GM4-010

Handler ID and Page Number must exist in GM1.

HANDLER ID and HZ PG must exist in GM1

GM4-020

Off-Site Sequence must be greater than zero.

IO_PG_NUM_SEQ > 0

GM4-030

EPA ID Number of the Facility to which Waste was Shipped
must begin with a state postal code in LU_STATE.

SUBSTR(IO_TDR_ID,l,2) = state postal code in LU_STATE

GM4-040

Management Method must equal a headquarter-defined
management method in LU_MANAGEMENT_METHOD.

MANAGEMENT_METHOD = headquarter-defined management
method in LU_MANAGEMENT_METHOD

GM4-050

Total Quantity Shipped to EPA ID in Current Reporting Year
must be greater than zero and less than
99,999,999,999.999999.

IO_TDR_QTY > 0 and <= 99999999999.999999

February 2015

A-42

File Specification Guide


-------
FLAT FILE ID#-GM5

Source Form: GM Description: On-Site Management Information for the Reported Waste





This file captures on-site treatment information for the reported waste as represented in GM Item 2. The relationship of these data records to

the reported waste is n: 1, that is, there can be multiple off-site information for each reported waste.







Key Fields: Handler ID (HANDLERJD); Page Number (HZ_PG); On-Site Sequence Number (SYS_PG_NUM_SEQ). Each record in the GM5 file must

contain a unique combination of the Handler ID, Page Number, and On-Site Sequence Number.







Note: The GM5file is REQUIRED for handlers that generated RCRA hazardous waste that, in 2015, was accumulated on-site or managed on-site

in a treatment, storage, or disposal unit

























Required /





Starting

Field

Data



Location

Cond.

Edit

Field Name

Column

Length

Type

Description

on Form

Required

Number(s)

HANDLERJD

1

12

A

EPA Identification Number



Required

GM5-010

HZ_PG

13

5

1

Page Number



Required

GM5-010

SYS_PG_NUM_SEQ

18

5

1

On-Site Sequence Number



Required

GM5-020

MANAGEMENT_METHOD

23

4

A

Management Method

GM-2

Required

GM5-030









Total Quantity Treated, Disposed,















or Recycled On-Site in Current







SYS_TDR_QTY

27

18

D11.6

Reporting Year

GM-2

Required

GM5-040

Total Record Length:

44



February 2015

A-43

File Specification Guide


-------
GM5 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

GM5-010

Handler ID and Page Number must exist in GM1.

HANDLERJD and HZ_PG must exist in GM1

GM5-020

On-Site Sequence must be greater than zero.

SYS_PG_NUM_SEQ > 0

GM5-030

Management Method must equal a headquarter-defined
management method in LU_MANAGEMENT_METHOD.

MANAGEMENT_METHOD = headquarter-defined management
method in LU_MANAGEMENT_METHOD

GM5-040

Total Quantity Treated, Disposed, or Recycled On-Site in
Current Reporting Year must be greater than zero and less
than 99,999,999,999.999999.

SYS_TDR_QTY > 0 and <= 99999999999.999999

February 2015

A-44

File Specification Guide


-------
FLAT FILE ID# - WR1

Source Form: WR Description: Waste Received From Off-Site







This file captures the information contained in Item A and Items D through H of the WR form. The relationship of these data records to the
reported site is n: 1, that is, there can be multiple received waste for each site.

Key Fields: Handler ID (HANDLERJD); Page Number (HZ_PG); Waste Number (SUB_PG_NUM). Each record in the WR1 file must contain a
unique combination of the Handler ID, Page Number and Waste Number.

Note: The WR1 file is REQUIRED for handlers who, during 2015, received RCRA hazardous waste from off-site.





Field Name

Starting
Column

Field
Length

Data
Type

Description

Location
on Form

Required /

Cond.
Required

Edit
Number(s)

HANDLER ID

1

12

A

EPA Identification Number



Required

WR1-010,
WR1-130

HZ PG

13

5

1

Page Number



Required

WR1-020,
WR1-130

SUB PG NUM

18

1

1

Waste Number



Required

WR1-030,
WR1-130

FORM CODE

19

4

A

Form Code

WR-G

Required

WR1-100

UNIT OF MEASURE

23

1

A

Unit of Measure

WR-F

Required

WR1-070,
WR1-080,
WR1-090

WST_DENSITY

24

6

D3.2

Density

WR-F

Cond.
Required

WR1-080

DENSITY_UN IT_OF_MEASURE

30

1

A

Density Unit of Measure

(1 = lbs/gal; 2 = specific gravity)

WR-F

Cond.
Required

WR1-090

INCLUDE_IN_NATIONAL_REPORT

31

1

A

Include Information in the
National Hazardous Waste Report



Required

WR1-120

MANAGEMENT_METHOD

32

4

A

Management Method

WR-H

Required

WR1-110

IO_TDR_ID

36

12

A

Off-Site Source EPA ID Number

WR-D

Required

WR1-050

February 2015

A-45

File Specification Guide


-------












Required /





Starting

Field

Data



Location

Cond.

Edit

Field Name

Column

Length

Type

Description

on Form

Required

Number(s)









Quantity Received in Current







IO TDR QTY

48

18

D11.6

Reporting Year

WR-E

Required

WR1-060

DESCRIPTION

66

240

A

Waste Stream Description

WR-A

Required

WR1-040











Bottom





NOTES

306

240

A

Comments / Notes

of Form





Total Record Length:

545



February 2015

A-46

File Specification Guide


-------
WR1 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

WR1-010

Handler ID must exist in SI 1.

HANDLER ID must exist in Sll

WR1-020

Page Number must be greater than zero.

HZ PG > 0

WR1-030

Waste Number must equal T, '2', or '3'

SUB PG NUM = T or'T or '3'

WR1-040

Waste Stream Description must be provided.

DESCRIPTION <> "



The first two characters of the Off-Site Handler EPA ID





Number must be a state postal code in LU_STATE or 'FC'



WR1-050

(foreign country)

SUBSTR(IO_TDR_ID,l,2) = state postal code in LU_STATE or 'FC'



Total Quantity Received in Current Reporting Year must be



WR1-060

greater than zero and less than 99,999,999,999.999999.

10 TDR QTY > 0 and <= 99999999999.999999



Unit of Measure must equal a headquarter-defined unit of

UNIT_OF_MEASURE = headquarter-defined unit of measure in

WR1-070

measure in LU BR UOM.

LU BR UOM



If Unit of Measure equals '5', '6', or '7', then Density must

If UNIT_OF_MEASURE = '5' or '6' or'T Then WST_DENSITY > 0

WR1-080

be greater than zero else Density must equal 0.

Else WST DENSITY = 0



If Unit of Measure equals '5', '6', or '7', then Density Unit

If UNIT OF MEASURE = '5'or'6'or'7'Then



of Measure must equal a headquarter-defined unit of

DENSITY_UNIT_OF_MEASURE = headquarter-defined density unit



measure in LU_DENSITY_UOM else Density Unit of

of measure in LU_DENSITY_UOM

WR1-090

Measure must equal blank.

Else DENSITY UNIT OF MEASURE = "



Form Code must equal a headquarter-defined form code



WR1-100

in LU_FORM_CODE.

FORM_CODE = headquarter-defined form code in LU_FORM_CODE



Management Method must equal a headquarter-defined

MANAGEMENT_METHOD = headquarter-defined management

WR1-110

management method in LU_MANAGEMENT_METHOD.

method in LU_MANAGEMENT_METHOD



If Include in National Report in the Sll file equals 'N' then

If INCLUDE_IN_NATIONAL_REPORT in Sll = 'N' Then



Include in National Report must equal 'N' else Include in

INCLUDE_IN_NATIONAL_REPORT = 'N'

WR1-120

National Report must equal 'N' or 'Y'.

Else INCLUDE_IN_NATIONAL_REPORT = 'N' or Y



For each handler, page number, and waste number in

For each HANDLERJD, HZ_PG, and SUB_PG_NUM in WR1 there

WR1-130

WR1, one record must exist in WR2 or WR3.

must be a record in WR2 or WR3.

February 2015

A-47

File Specification Guide


-------
FLAT FILE ID#-WR2

Source Form: WR Description: EPA Hazardous Waste Codes







This file captures the information contained in Item B of the WR form. The relationship of these data records to the reported waste is n: 1, that
is, there can be multiple waste codes for each reported waste.

Key Fields: Handler ID (HANDLERJD); Page Number (HZ_PG); Waste Number (SUB_PG_NUM); EPA Waste Code (EPA_WASTE_CODE)
record in the WR2 file must contain a unique combination of the Handler ID, Page Number, Waste Number, and EPA Waste Code.

. Each

Note: For each waste stream, either EPA Hazardous Waste Code information (WR2) is REQUIRED or State Hazardous Waste Code information
(WR3) is REQUIRED.

Field Name

Starting
Column

Field
Length

Data
Type

Description

Location
on Form

Required /

Cond.
Required

Edit
Number(s)

HANDLERJD

1

12

A

EPA Identification Number



Required

WR2-010

HZ_PG

13

5

1

Page Number



Required

WR2-010

SUB_PG_NUM

18

1

1

Waste Number



Required

WR2-010

EPA_WASTE_CODE

19

4

A

EPA Hazardous Waste Code

WR-B

Required

WR2-020

Total Record Length:

22



February 2015

A-48

File Specification Guide


-------
WR2 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

WR2-010

Handler ID, Page Number and Waste Number must exist in
WR1.

HANDLERJD, HZ_PG, and SUB_PG_NUM must exist in WR1

WR2-020

EPA Waste Code must equal a headquarters-defined waste
code in LU_WASTE_CODE.

EPA_WASTE_CODE = headquarters-defined waste code in
LU_WASTE_CODE.

February 2015

A-49

File Specification Guide


-------
FLAT FILE ID#-WR3

Source Form: WR Description: State Hazardous Waste Codes







This file captures the information contained in Item C of the WR form. The relationship of these data records to the reported waste is n:1, that is,

there can be multiple waste codes for each reported waste.











Key Fields: Handler ID (HANDLERJD); Page Number (HZ_PG); Waste Number (SUB_PG_NUM); State Waste Code (STATE_WASTE_CODE).

Each record in the WR3 file must contain a unique combination of the Handler ID, Page Number, Waste Number, and State Waste Code.

Note: For each waste stream, either EPA Hazardous Waste Code information (WR2) is REQUIRED or State Hazardous Waste Code information

(WR3) is REQUIRED.



























Required /





Starting

Field

Data



Location

Cond.

Edit

Field Name

Column

Length

Type

Description

on Form

Required

Number(s)

HANDLERJD

1

12

A

EPA Identification Number



Required

WR3-010

HZ_PG

13

5

1

Page Number



Required

WR3-010

SUB_PG_NUM

18

1

1

Waste Number



Required

WR3-010

STATE_WASTE_CODE

19

6

A

State Hazardous Waste Code

WR-C

Required

WR3-020

Total Record Length:

24



February 2015

A-50

File Specification Guide


-------
WR3 Flat File Edit Specifications

Edit Number

Edit Description

Select Logic

WR3-010

Handler ID, Page Number and Waste Number must exist in
WR1.

HANDLERJD, HZ_PG, and SUB_PG_NUM must exist in WR1

WR3-020

State Waste Code must equal an implementer-defined
waste code in LU_WASTE_CODE.

STATE_WASTE_CODE = implementer-defined waste code in
LU_WASTE_CODE.

February 2015

A-51

File Specification Guide


-------
FLAT FILE ID#-Oil

Source Form: Ol Description:

Identification of All Handlers to Whom or From Whom Waste was Shipped, and Transporters



This file captures information from the Ol form. This flat file should never be included in submissions to RCRAInfo.





Key Fields: Handler ID (HANDLERJD); Page Number (OSITE_PGNUM). Each record in the Oil file must contain a unique combination of the
Handler ID and Page Number.

Field Name

Starting
Column

Field
Length

Data
Type

Description

Location
on Form

Required /

Cond.
Required

Edit
Number(s)

HANDLER ID

1

12

A

EPA Identification Number







OSITE PGNUM

13

5

1

Page Number







OFF ID

18

12

A

Off-Site Installation or Transporter
EPA ID Number

Ol-A





WST GEN FLG

30

1

A

Handler Type = Generator
(Checked = 'Y, Unchecked and
not implementer-required = 'U',
Unchecked and implementer-
required = 'N')

Ol-C





WST_TRNS_FLG

31

1

A

Handler Type = Transporter
(Checked = 'Y, Unchecked and
not implementer-required = 'U',
Unchecked and implementer-
required = 'N')

Ol-C





WST_TSDR_FLG

32

1

A

Handler Type = Receiving Facility
(Checked = 'Y, Unchecked and
not implementer-required = 'U',
Unchecked and implementer-
required = 'N')

Ol-C





ONAME

33

40

A

Name of Off-Site Installation or
Transporter

Ol-B





February 2015

A-52

File Specification Guide


-------
Field Name

Starting
Column

Field
Length

Data
Type

Description

Location
on Form

Required /

Cond.
Required

Edit
Number(s)

01STREET

73

30

A

Installation or Transporter Street
Addressl

Ol-D





02STREET

103

30

A

Installation or Transporter Street
Address2

Ol-D





OCITY

133

25

A

City

Ol-D





OSTATE

158

2

A

State

Ol-D





OZIP

160

9

A

Zip Code

Ol-D





NOTES

169

240

A

Comments / Notes

Bottom
of 01
Form





Total Record Length:

408



February 2015

A-53

File Specification Guide


-------
APPENDIX B

Hazardous Waste Report Annotated Forms


-------
OMB#: 2050-0024; Expiration Date 12/31/2014

SEND

COMPLETED
FORM TO:

The Appropriate
State or Regional
Office.

United States Environmental Protection Agency
RCRA SUBTITLE C SITE IDENTIFICATION FORM

/ o X
ISEzJ

1. Reason for
Submittal

MARK ALL
BOX(ES) THAT
APPLY

Reason for Submittal:

~	To provide an Initial Notification (first time submitting site identification information / to obtain an EPA ID number for this
location)

~	To provide a Subsequent Notification (to update site identification information for this location)

~	As a component of a First RCRA Hazardous Waste Part A Permit Application

~	As a component of a Revised RCRA Hazardous Waste Part A Permit ADDlication (Amendment # )

~	As a component of the Hazardous Waste Report (If marked, see sub-bullet below)

~ Site was a TSD facility and/or generator of >1,000 kg of hazardous waste, >1 kg of acute hazardous waste, or
>100 kq of acute hazardous waste spill cleanup in one or more months of the report vear (or State equivalent LQG
regulations)

2. Site EPA ID
Number

EPA ID Numbe

r I I I II I I I

I I II I I I M

ANDLERJD





3. Site Name

SI1 File

Name: HANDLER_NAME

4. Site Location
Information

SI1 File

Street Address:

LOCATION STREET NO, LOCATION STREET1, LOCATION STREET2

City, Town, or Village: LOCATION CITY

County: COUNTY CODE

state: LOCATION STATE

Country: LOCATION COUNTRY

Zip Code: LOCATION ZIP

5. Site Land Type

SI1 File

EH Private EH County EH District EHFederal EH Tribal EH Municipal

EH State EH Other LAND TYPE

6. NAICS Code(s)
for the Site
(at least 5-digit
codes) SI3 File

A.

I I I I I

J NAICS CODE

C.

I I I I I









B.

I I I I I

j

D.

I I I I I









7. Site Mailing
Address

SI1 File

street or P.O. Box: MAIL STREET NO, MAIL STREET1, MAIL STREET2

City, Town, or Village: MAIL CITY

state: MAIL STATE

Country: MAIL COUNTRY

Zip Code: MAIL ZIP

8. Site Contact
Person

SI1 File

First Name: CONTACT FIRST NAME

Ml

: Last: CONTACT LAST NAME

Title: CONTACT

TITLE CONTACT MIDDLE INITIAL



street or P.O. Box: CONTACT STREET NO, CONTACT STREET1, CONTACT STREET2

City, Town or Village: CONTACT CITY

State: CONTACT

STATE

Country: CONTACT COUNTRY

Zip Code: CONTACT ZIP

Email: CONTACT EMAIL ADDRESS

Phone: CONTACT PHONE

Ext.: CONTACT PHONE EXT



Fax: CONTACT FAX

9. Legal Owner
and Operator
of the Site

SI2 File

A. Name of Site's Legal Owner: OWNER_OPERATOR_NAME

Date Became

Owner: DATE BECAME CURRENT

Owner Type: EH Private EH County EH District EH Federal EH Tribal

EH Municipal EH State EH Other

street or P.O. Box: STREET NO, STREET1, STREET2 OWNER OPERATOR TYPE

City, Town, or Village: CITY

Phone: PHONE

State: STATE

Country: COUNTRY

Zip Code: ZIP

B. Name of Site's Operator: OWNER_0PERATOR_NAME OWNER_OPERATOR_TYPE

Date Became

Operator: DATE BECAME CURRENT

^Typ^°r ^ Private EH County EH District EH Federal I I Tribal

EH Municipal I I State I I Other

EPA Form 8700-12, 8700-13 A/B, 8700-23

Pagel of


-------
OMB#: 2050-0024; Expiration Date 12/31/2014

10. Type of Regulated Waste Activity (at your site)

Mark "Yes" or "No" for all current activities (as of the date submitting the form); complete any additional boxes as instructed.

A. Hazardous Waste Activities; Complete all parts 1-10. SI1 File

~

y|HI nQ] 1. Generator of Hazardous Waste FED_WASTE_GENERATOR
If "Yes", mark only one of the following - a, b, or c.

a. LQG: Generates, in any calendar month, 1,000 kg/mo
(2,200 lbs./mo.) or more of hazardous waste; or
Generates, in any calendar month, or
accumulates at anytime, more than 1 kg/mo (2.2
lbs./mo) of acute hazardous waste; or
Generates, in any calendar month, or
accumulates at anytime, more than 100 kg/mo
(220 lbs./mo) of acute hazardous spill cleanup
material.

Q b. SQG: 100 to 1,000 kg/mo (220-2,200 Ibs./mo) of non-
acute hazardous waste.

I | c. CESQG: Less than 100 kg/mo (220 Ibs./mo) of non-acute
hazardous waste.

If "Yes" above, indicate other generator activities in 2-4.

YD N | | 2. Short-Term Generator (generate from a short-term or one-time
event and not from on-going processes). If "Yes", provide an
explanation in the Comments section.

S H O RT_TE RM_G E N E RATO R

Y| | [\|| | 3. United States Importer of Hazardous Waste

IMPORTER ACTIVITY

yDnD 5. Transporter of Hazardous Waste
If "Yes", mark all that apply.

| |l Transporter TRANSPORTER

i—V Transfer Facility (at your site)

'—1	TRANSFER_FACILITY

yDnD 6. Treater, Storer, or Disposer of

Hazardous Waste Note: A hazardous
waste Part B permit is required for these
activities. TSD_ACTIVITY

~ i—| 7. Recycler of Hazardous Waste

N	

1—1 RECYCLER ACTIVITY

yDnD 8. Exempt Boiler and/or Industrial Furnace
If "Yes", mark all that apply.

~
~

Small Quantity On-site Burner
Exemption

ONSITE_BURNER_EXEMPTION

Smelting, Melting, and Refining
Furnace Exemption
FURNACE EXEMPTION

yD nD

4. Mixed Waste (hazardous and radioactive) Generator

MIXED WASTE GENERATOR

Y| | N| I 9- Underground Injection Control

UNDERGROUND_INJECTION_ACTIVITY

Y| I N| I 10. Receives Hazardous Waste from Off-
— — site OFF SITE RECEIPT

B. Universal Waste Activities; Complete all parts 1-2. SI6 File

Y Q N Q 1. Large Quantity Handler of Universal Waste (you
accumulate 5,000 kg or more) [refer to your State
regulations to determine what is regulated]. Indicate
types of universal waste managed at your site. If "Yes",
mark all that apply.

UNIVERSAL WASTE	ACCUMULATE

f.

Batteries
Pesticides

Mercury containing equipment
Lamps

Other (specify)	

Other (specify)	

~
~
~
~
~
~

Y Q N Q 2. Destination Facility for Universal Was|~|

Note: A hazardous waste permit may be required for this
activity. UNIVERSAL_WASTE_DEST_FACILITY

C. Used Oil Activities; Complete all parts 1-4.

Y| I n| I 1- Used Oil Transporter

If "Yes", mark all that apply.

|—| a. Transporter USED_OIL_TRANSPORTER
~

b. Transfer Facility (at your site)
USED OIL TRANSFER FACILITY

Y| I n| I 2. Used Oil Processor and/or Re-refiner
If "Yes", mark all that apply.

~
~

a.	Processor USED_OIL_PROCESSOR

b.	Re-refiner USED OIL REFINER

Y	EUn EH 3. Off-Specification Used Oil Burner

USED_OIL_BURNER

Y	Qn Q 4. Used Oil Fuel Marketer

If "Yes", mark all that apply.

| | a. Marketer Who Directs Shipment of
Off-Specification Used Oil to Off-
Specification Used Oil Burner
USED_OIL_MARKET_BURNER
~ b. Marketer Who First Claims the Used
Oil Meets the Specifications
USED OIL SPEC MARKETER


-------
OMB#: 2050-0024; Expiration Date 12/31/2014

D. Eligible Academic Entities with Laboratories—Notification for opting into or withdrawing from managing laboratory hazardous
wastes pursuant to 40 CFR Part 262 Subpart K SI1 File

~ You can ONLY Opt into Subpart K if:

•	you are at least one of the following: a college or university; a teaching hospital that is owned by or has a formal affiliation
agreement with a college or university; or a non-profit research institute that is owned by or has a formal affiliation agreement with
a college or university; AND

•	you have checked with your State to determine if 40 CFR Part 262 Subpart K is effective in your state

yd nQ 1. Opting into or currently operating under 40 CFR Part 262 Subpart K for the management of hazardous wastes in laboratories
See the item-by-item instructions for definitions of types of eligible academic entities. Mark all that apply:

| |a. College or University
SUBPART_K_COLLEGE

| |b. Teaching Hospital that is owned by or has a formal written affiliation agreement with a college or university
SUBPART_K_HOSPITAL

~ C Non-profit Institute that is owned by or has a formal written affiliation agreement with a college or university
SUBPART_K_NONPROFIT

Y| I n| I 2. Withdrawing from 40 CFR Part 262 Subpart K for the management of hazardous wastes in laboratories
'—' '—' SUBPART K WITHDRAWAL

11. Description of Hazardous Waste

A. Waste Codes for Federally Regulated Hazardous Wastes. Please list the waste codes of the Federal hazardous wastes handled at
your site. List them in the order they are presented in the regulations (e.g., D001, D003, F007, U112). Use an additional page if more
spaces are needed SI4 File

EPA WASTE CODE

B. Waste Codes for State-Regulated (i.e., non-Federal) Hazardous Wastes. Please list the waste codes of the State-Regulated
hazardous wastes handled at your site. List them in the order they are presented in the regulations. Use an additional page if more
spaces are needed SI5 File

STATE WASTE CODE

EPA Form 8700-12, 8700-13 A/B, 8700-23

Page 3 of	


-------
OMB#: 2050-0024; Expiration Date 12/31/2014

12. Notification of Hazardous Secondary Material (HSM) Activity

yD nD Are you notifying under 40 CFR 260.42 that you will begin managing, are managing, or will stop managing hazardous
secondary material under 40 CFR 261,2(a)(2)(ii), 40 CFR 261.4(a)(23), (24), or (25)?

If "Yes", you must fill out the Addendum to the Site Identification Form: Notification for Managing Hazardous Secondary
Material.

13. Comments SI1 File

NOTES

14. Certification. I certify under penalty of law that this document and all attachments were prepared under my direction or supervision in
accordance with a system designed to assure that qualified personnel properly gather and evaluate the information submitted. Based
on my inquiry of the person or persons who manage the system, or those persons directly responsible for gathering the information, the
information submitted is, to the best of my knowledge and belief, true, accurate, and complete. I am aware that there are significant
penalties for submitting false information, including the possibility of fines and imprisonment for knowing violations. For the RCRA
Hazardous Waste Part A Permit Application, all owner(s) and operator(s) must sign (see 40 CFR 270.10(b) and 270.11). SI7 File

Signature of legal owner, operator, or an
authorized representative

Name and Official Title (type or print)

Date Signed
(mm/dd/yyyy)

CERT_FIRST_NAME, CERT_MIDDLE_INITIAL,
CERT LAST NAME, CERT TITLE

CERT SIGNED DATE

EPA Form 8700-12, 8700-13 A/B, 8700-23

Page 4 of	


-------
OMB#: 2050-0024; Expiration Date 12/31/2014

ADDENDUM TO THE SITE IDENTIFICATION FORM:
NOTIFICATION OF HAZARDOUS SECONDARY MATERIAL ACTIVITY



s&Si

ONLY fill out this form if:

~	You are located in a State that allows you to manage excluded hazardous secondary material (HSM) under 40 CFR 261.2(a)(2)(H),
261,4(a)(23), (24), or (25) (or state equivalent). See http://www.epa.aov/epawaste/hazard/dsw/statespf.htm for a list of eligible
states; AND

~	You are or will be managing excluded HSM in compliance with 40 CFR 261,2(a)(2)(ii), 261,4(a)(23), (24), or (25) (or state
equivalent) or you have stopped managing excluded HSM in compliance with the exclusion(s) and do not expect to manage any
amount of excluded HSM under the exclusion(s) for at least one year. Do not include any information regarding your hazardous
waste activities in this section.

1.	Indicate reason for notification. Include dates where requested. SI9 File

REASON_FOR_NOTIFICATION

~	Facility will begin managing excluded HSM as of	(mm/dd/yyyy). HSM_EFFECTIVE_DATE

~	Facility is still managing excluded HSM/re-notifying as required by March 1 of each even-numbered year.

~	Facility has stopped managing excluded HSM as of	(mm/dd/yyyy) and is notifying as required.

2.	Description of excluded HSM activity. Please list the appropriate codes and quantities in short tons to describe your excluded HSM

activity ONLY (do not include any information regarding your hazardous wastes). Use additional pages if more space is needed.

a. Facility code

(answer using
codes listed in the
Code List section of
the instructions)
SIA File

b. Waste code(s) for HSM

SIB File

Estimated short tons of
excluded HSM to be
managed annually

SIA File

d. Actual short tons of
excluded HSM that was
managed during the
most recent odd-
numbered year
SIA File

e. Land-based unit
code (answer using
codes listed in the
Code List section of
the instructions)
SIA File

FACILITY CODE

WASTE CODE

ESTIMATE SHORT TONS

ACTUAL SHORT TONS

LAND BASED UNITS

3. Facility has financial assurance pursuant to 40 CFR 261.4(a)(24)(vi). (Financial assurance is required for reclaimers and
intermediate facilities managing excluded HSM under 40 CFR 261.4(a)(24) and (25)) SI9 File

y|HI nEH Does this facility have financial assurance pursuant to 40 CFR 261.4(a)(24)(vi)? HSM_FA


-------
OMB# 2050-0024; Expiration Date 12/31/2014

BEFORE COPYING FORM, ATTACH SITE IDENTIFICATION LABEL
OR ENTER:

SITE NAME:	

EPA ID Number

U.S. ENVIRONMENTAL
PROTECTION AGENCY

2013 Hazardous Waste Report

WASTE GENERATION
AND MANAGEMENT

Sec. 1

A. Waste description: GM1 File DESCRIPTION

B. EPA hazardous waste code(s) GM2 File EPA_WASTE_CODE C. State hazardous waste code(s) GM3 File STATE_WASTE_CODE

D. Source code

IGI I I

GM1 File
SOURCE CODE

Vlanagement Method code for Source code G25

MANAGEMENT METHOD

E. Form code

|w| | | |

GM1 File
FORM CODE

F. Quantity generated in 2013 GM1 File

GEN_QTY

UOM |	|

UNIT_OF_MEASURE
Density I	I	|.|	

~ lbs/gal ~ sg

WST DENSITY DENSITY UNIT OF MEASURE

G. Waste

minimization code

u

GM1 File
WASTE MIN CODE

Sec. 2

Was any of this waste that was generated at this facility treated, disposed, and/or recycled on site? GM1 File

~	Yes (CONTINUE TO ON-SITE PROCESS SYSTEM 1) ON_SITE_MANAGEMENT

~	No (SKIP TO SEC. 3)

ON-SITE PROCESS SYSTEM 1 GM5 File

ON-SITE PROCESS SYSTEM 2

On-site Management
Method code

MANAGEMENT METHOD^"

Quantity treated, disposed, or
recycled on site in 2013

SYS TDR QTY

On-site Management
Method code

Quantity treated, disposed, or
recycled on site in 2013

Sec. 3

A. Was any of this waste shipped off site in 2011 for treatment, disposal, or recycling? GM1 File

~	Yes (CONTINUE TO ITEM B) OFF_SITE_SHIPMENT

~	No (FORM IS COMPLETE)

Site 1
GM4 File

B. EPA ID No. of facility to which waste was shipped

IO TDR ID

C. Off-site Management
Method code shipped to

MANAGEMENT METHOD

D. Total quantity shipped in 2013

IO TDR QTY

Site 2

B. EPA ID No. of facility to which waste was shipped

C. Off-site Management
Method code shipped to

D. Total quantity shipped in 2013

Site 3

B. EPA ID No. of facility to which waste was shipped

C. Off-site Management
Method code shipped to

D. Total quantity shipped in 2013

Comments: GM1 File
NOTES

Page	of


-------
Page	of _


-------
OMB# 2050-0024; Expiration Date 12/31/2014

BEFORE COPYING FORM, ATTACH SITE IDENTIFICATION LABEL
OR ENTER:

SITE NAME:

EPA ID NO:

Ol
FORM

U.S. ENVIRONMENTAL
PROTECTION AGENCY

2013 Hazardous Waste Report

OFF-SITE
IDENTIFICATION

Site 1

011 File

A. EPA ID number of off-site installation or transporter

OFF ID

B. Name of off-site installation or transporter
ONAME

C. Handler type (MARK ALL THAT APPLY)

~	Generator	WST_GEN_FLG

~	Transporter	WST_TRANS_FLG

~	Receiving facility WST_TSDR_FLG

D. Address of off-site installation

street 01 STREET, 02STREET
City OCITY

State |_
OSTATE

Zip

OZIP

Site 2 A. EPA ID number of off-site installation or transporter

B. Name of off-site installation or transporter

C. Handler type (MARK ALL THAT APPLY)

~	Generator

~	Transporter

~	Receiving facility

D. Address of off-site installation
Street
City

State I I

Zip

Site 3 A. EPA ID number of off-site installation or transporter

B. Name of off-site installation or transporter

C. Handler type (MARK ALL THAT APPLY)

~	Generator

~	Transporter

~	Receiving facility

D. Address of off-site installation
Street
City

State I I

Zip

Site 4 A. EPA ID number of off-site installation or transporter

B. Name of off-site installation or transporter

C. Handler type (MARK ALL THAT APPLY)

~	Generator

~	Transporter

~	Receiving facility

Comments:
NOTES

D. Address of off-site installation

Street
City

State | | | Zip I	I

Page	of


-------
End of document.


-------