FIESTA_CHASZ Manual



CHAZ User’s Manual v4

procedure style

|Date |Description |Version |

|01/30/2005 |Online Help authoring online conversions style sheet template used to |4.0 |

| |prepare Word documents styled under the Numbered Paragraph style guide | |

| |by changing fonts, font sizes, and making other style adjustments | |

| |necessary for online presentation | |

TABLE OF CONTENTS

1. OVERVIEW ………………………………………………………………… 1

1.1 WHAT IS COMHAZ ? …………………………………………… 1

1.2 BACKGROUND …………………………………………………… 1

1.3 COMET FOR HAZARDOUS WASTE (COMHAZ) …………… 2

1.4 USERS AND ROLES ……………………………………………… 3

1.5 DEVELOPMENT PLATFORM ………………………………… 4

2. ACCESSING COMHAZ …………………………………………………… 6

3. NAVIGATING IN COMHAZ ……………………………………………… 11

4. Managed Entity …………………………………………………………… 15

4.1 NEW ……………………………………………………………… 15

4.2 OPEN ……………………………………………………………… 18

4.3 ALTERNATE ID …………………………………………………… 20

5. PREHANDLER …………………………………………………………… 22

5.1 NEW ………………………………………………………………… 24

5.2 OPEN ……………………………………………………………… 36

5.3 PROMOTE ………………………………………………………… 37

6. HANDLER …………………………………………………………………… 40

6.1 OPEN ……………………………………………………………… 40

6.2 CONTACTS ……………………………………………………… 46

6.3 OWNER/OPERATOR …………………………………………… 48

6.4 SOURCE - STATUS ……………………………………………… 50

6.5 SIC ………………………………………………………………… 58

6.6 SOURCE - WASTE CODES ……………………………………… 59

6.7 TRANSPORTER ………………………………………………… 60

6.8 UNIVERSAL WASTE - MERCURY …………………………… 64

6.9 - PCW …………………………………… 68

6.10 - PESTICIDES ………………………… 68

6.11 - BATTERIES ………………………… 68

6.12 USED OIL ………………………………………………………… 69

6.13 EMERGENCY ID ……………………………………………… 74

6.14 LETTERS ………………………………………………………… 78

6.15 VIOLATIONS …………………………………………………… 80

7. PROJECT …………………………………………………………………… 82

7.1 NEW - COMPLIANCE ……………………………………… 82

7.2 - ENFORCEMENT …………………………………… 85

7.3 - CRIMINAL ………………………………………… 85 7.4 - COMPLAINT ………………………………………… 86

7.5 OPEN ……………………………………………………………… 91

7.6 RELATED PARTY ……………………………………………… 96

7.7 LCT LINK ………………………………………………………… 100

7.8 COMPLAINT …………………………………………………… 102

8. ACTIVITY ………………………………………………………………… 103

8.1 NEW ……………………………………………………………… 103

8.2 OPEN ……………………………………………………………… 106

8.3 STAFF ASSIGNED ……………………………………………… 108

8.4 VIOLATION - ADD/UPDATE ………………………… 110

8.5 - BROWSE ……………………………… 113

8.6 - LINK/UNLINK ………………………… 114

8.7 $ETTLEMENT - ASSESSED ……………………………… 116

8.8 - COLLECTED …………………………… 119

8.9 SEPS ……………………………………………………………… 121

9. REPORT …………………………………………………………………… 123

9.1 RUNNING REPORTS …………………………………………… 123

9.2 COMPLIANCE - MOST RECENT ACT ……………………… 125

9.3 - TICKLER BY STAFF ……………………… 127 9.4 - PROJECT SUMMARY …………………… 129

9.5 - PROJECT BRIEF …………………………… 131

9.6 - PROJECT LIST …………………………… 133

9.7 - EXMIS ……………………………………… 135

9.8 - PERSON CHRON ………………………… 137

9.9 - VIOLATION/ENF ………………………… 139

9.10 - CM&E ACTIVITIES ……………………… 141

9.11 COMPLAINT - DETAIL …………………………………… 144

9.12 - SUMMARY ………………………………… 146

9.13 SITE - SUMMARY ………………………………… 148

9.14 - LISTING …………………………………… 150

Appendix 1

Appendix 2

9.15 HANDLER - LOCATION ………………………………… 152

9.16 - FOIA ………………………………………… 154

9.17 - HW TRANSPORTER ……………………… 156

9.18 - MERCURY HANDLER …………………… 158

9.19 - PREHANDLERS ………………………… 161

9.20 - HANDLER_LATLONG …………………… 163

9.21 DATA ASSESSMENT - INCOMPLETE VIOL ……………… 165

9.22 - DUPLICATE ACTIVITY ………… 167

9.23 - UNLINKED ENFORCEMENT …… 169

9.24 CODES - ACTIVITY CODES ………………………………… 171

9.25 - PROCESS CODES ………………………………… 173

9.26 - VIOLATION CODES ……………………………… 175

9.27 - WASTE CODES …………………………………… 177

10. MAINT …………………………………………………………………… 179

11. HELP ……………………………………………………………………… 180

12. APPENDIX A …………………………………………………………… 182

12.1 FUNCTION KEYS …………………………………………… 182

12.2 HOT KEYS …………………………………………………… 184

12.3 HOW TO RETRIEVE DATA ..………………………………… 185

12.4 DATE FORMAT .……………………………………………… 187

12.5 HOW TO RUN REPORTS …..………………………………… 188

12.6 ACCESSING COMHAZ VIA INTRANET .…………………… 189

13. APPENDIX B …………………………………………………………… 190

13.1 Data Entry Guidelines

14. APPENDIX C …………………………………………………………… 208

14.1 Activity Code List

15. APPENDIX D …………………………………………………………… 216

15.1 Draft Data Element Dictionary and SOP

16. APPENDIX E ……………………………………………………………

16.1 Installation and Logon Instructions

1 OVERVIEW

1.1. WHAT IS COMHAZ

COMHAZ is the Compliance and Enforcement Tracking System for the Hazardous Waste Program and is also called CHAZ. It is a relational database management system exclusively developed for hazardous waste program staff and it is primarily used for tracking hazardous waste facility information and compliance and enforcement activities. It is also used to track used oil, mercury, transporter registration, and emergency EPA Identification Numbers (EPA ID). The development of COMHAZ was initiated in January 1995 and completed by October 1996.

1.2. BACKGROUND

Before COMHAZ was developed, relevant program information was tracked in various database systems. Compliance and enforcement data was tracked in the department’s COMET database and the same data was sent to Tallahassee on paper logs to fulfill EPA’s data reporting requirements. Data entry staff in Tallahassee used the GMS system to track facility information and this data was electronically transferred to the EPA mainframe. Compliance data from paper logs was directly entered into the EPA’s Resource Conservation and Recovery Information System (RCRIS). In addition, emergency EPA IDs were tracked on the MAPPER system and used oil and transporter registration information was tracked separately. A move to consolidate all these applications into one single application and avoid duplicate data entry resulted in COMHAZ development. With COMHAZ, program staffs were able to discontinue data entry into RCRIS, GMS, COMET, MAPPER, and paper logs. Data from COMHAZ to RCRIS is electronically transferred saving time and resources.

1.3. COMET for Hazardous Waste Program (COMHAZ)

Department staffs use COMET to track facility, compliance and enforcement information. Hazardous waste program staffs are required to track more data than COMET is capable of tracking to fulfill EPA data reporting requirements. Additional data modules were added to COMET and the new system is called COMHAZ. One can visualize COMHAZ as COMET with additional data tracking capabilities for the Hazardous Waste program. See Figure 1.1 below.

1.4. USERS AND ROLES

COMHAZ users are located in Tallahassee as well as in district offices. They are divided into 6 groups based on their data entry requirements.

1) CHAZ DISTRICT ANALYST

District programmer analysts are allocated to this role. They are responsible for helping the district users in maintaining the data.

2) CHAZ CO-ORDINATOR

This role is granted to any person responsible for maintaining the database, and this role is restricted to very few people. Users having this role are responsible for updating code tables, granting access to users, and maintaining the database.

3) CHAZ HW MANAGEMENT

This role is exclusively granted to the users in the Hazardous Waste Management Section. Users having this role can update the used oil, transporter, and mercury registration data. They will have view-only privileges on other data.

4) CHAZ INSPECTOR

This role is granted to the district staff who are responsible for entering the inspection data into the system.

5) CHAZ USER

This role is granted to users who are responsible for issuing EPA IDs. They cannot update the inspection data, but can view it.

6) CHAZ VIEWER

This role is granted to any user who requests access to COMHAZ but does not fall into any of the above categories. Users having this role will have read-only privileges for all data.

1.5. DEVELOPMENT PLATFORM

Oracle Relational Database Management System (RDBMS) was chosen as the platform for COMHAZ development. The reason behind choosing Oracle is that it is Department’s standard development platform and COMET was already developed in Oracle. The database management system mainly consists of:

1) Oracle tables to store the data.

2) Oracle forms to retrieve, add, update the data

3) Oracle menus to navigate between various forms and

4) Oracle reports to generate data outputs

[pic]

Figure 1.1 : Oracle Form

Oracle forms play a major role in the application as they help to integrate tables, menus, and reports. Forms are used to add, update, delete and view the data. Based on the design, a form can display one to many records and programmatically restrict users from updating any field. Oracle tables are used to store the data and can be updated through forms. Oracle is powerful table indexing system which enables faster data retrieval. Data can be validated with the help of database triggers before it is saved in the table. Oracle menus are used to enter into the application and navigate between various forms. Oracle reports are used to generate custom data outputs. Refer to the Appendix for more details on forms, menus and reports.

2 ACCESSING COMHAZ

COMHAZ has been developed using the Oracle RDBMS system, and it is stored on the Department’s Digital Equipment Corporation (DEC) computer system also known as the VAX. To access the COMHAZ database system, 3 system accounts must be established for any user.

Hint: Users who already have a COMHAZ account can skip this page.

1) Oracle account

2) User COMHAZ role in WEB Access Control Application(WACA)

The immediate supervisor is usually responsible for establishing these accounts for any user. To establish the Oracle account, the immediate supervisor should complete the Information Systems Request Form, available from Information Systems Support Center (ISSC) and submit it to section/bureau/division computer support representative. The computer representative will review the application and submit it to ISSC for processing.

Once an Oracle account is established, the immediate supervisor can request a COMHAZ user’s role by e-mailing the user details to the COMHAZ database administrator. Required user details to establish the COMHAZ WACA role are:

1) Username

2) Office (usually name of the district office)

3) User initials (must be at least 3 letters), and

4) User role (please refer to Chapter 2 for details)

Once the COMHAZ role is established, the COMHAZ database administrator will notify the supervisor and the user about the new account status.

Any user with a valid COMHAZ account can log into the system by following the simple steps explained below.

2.1 Log into Oracle Web Database

- From HWRS Data Home : under HW Handler menu, Select COMHAZ Online.

[pic]

Figure 2.1 : HWRS Data Home

- URL .

A user can logged on at the URL . A popup menu will prompt the username, password and database to log into the system. Once a username, password and database are supplied, the system will take a user to the DEP Oracle enterprise menu which looks similar to Figure 2.3.

2.2 Password setting option.

[pic]

Figure 2.2 : Oracle Developer – Logon Screen.

The password setup will be required for the user fist time logon to the Comhaz’s application. Type the new password in the New Password and Verify Password field and press the [Set Password] key. Selecting the Set Password option for Oracle Applications will bring up the Applications Menu screen shown in Figure 2.4.

[pic]

Figure 2.3 : Enterprise Applications.

Select the Fiesta Data Maintenance on to access the FDM main application menu which is shown in Figure 2.2. The DEP Oracle applications Main Menu will list all the applications that a user has allowable access on the top left corner of the screen. Click or chose the “Fiesta Data Maintenance” to start Florida Integrated Environmental System TodAy.

[pic]

Figure 2.4 : WELCOME to FIESTA

2.3 From Oracle Applications Menu select FDM

In the Application Menu (Figure 2.3) select FIESTA DATA MAINTENANCE option and press the [ENTER] key to enter into FIEASTA. This action will navigate the user to the FIESTA’s main menu.

[pic]

Figure 2.5: Managed Entity Search

[pic]

Figure2.6 : COMHAZ Main Application

The COMHAZ main menu screen shown above (Figure 2.6) is also called the startup screen. The phrase “log into COMHAZ” also refers to accessing the main menu screen.

The number of menu items present in the above menu depends on the user’s access privileges.

For example, some users may not see the “Maint” menu item on the screen because this menu item provides access to data maintenance and this privilege is not granted to all users.

3 NAVIGATING IN COMHAZ

This chapter guides the user in navigating through COMHAZ including viewing, adding or updating COMHAZ data. By using the flowcharts provided in this chapter, the user will be able to easily determine the steps required to perform any data processing operation. It is recommended that every user read and familiarize themselves with this chapter and the flow charts following this section irrespective of their expertise with COMHAZ.

One major advantage of COMHAZ is the ability to track both Hazardous Waste Management related data and Hazardous Waste Compliance and Enforcement related data in one system. Such design provides the ability to crosscheck information automatically. For example, whenever a user tries to enter Used Oil registration data for a handler located in Florida, COMHAZ automatically checks the validity of the handler identification number and also the notified status to make sure that facility notified properly before registering.

To simplify data processing, all COMHAZ data is divided into 2 groups, namely, Hazardous Waste Management related data and Hazardous Waste Compliance and Enforcement related data. Hazardous Waste Management related data includes registration data pertaining to Used Oil, Hazardous Waste Transporter, and Mercury Handler. In addition, the emergency EPA ID issuing and tracking system also falls into the Management category. Hazardous Waste Compliance and Enforcement related data includes data pertaining to Handler Notification, Projects, Activities, Violations, Penalties, etc. To simplify data processing, a flowchart has been developed for each group which describes the steps required to perform data updates. Before beginning any data updates in COMHAZ, first determine the group which the data belongs to and use the corresponding flowchart (Figure 3.1 or Figure 3.2) to add, update or view the data.

Group I: Hazardous Waste Compliance and Enforcement data

a) Handler Notification data

b) FIESTA

1) Alternate IDs

c Projects

1) Related Parties

2) Legal Case Tracking (LCT)

d) Activities

1) Violations

2) Penalties

Group II: Hazardous Waste Management Related data

a) Emergency EPA ID (Temporary ID) data

b) Used Oil Registration data

c) Transporter Registration data

d) Mercury Registration data

In the following flowcharts, each step refers to a chapter. A page number for each chapter, in black, is included in each box. Using the page number, locate the corresponding chapter and follow the directions listed in the chapter.

[pic]

Figure 3.1: Hazardous Waste Compliance and Enforcement Data Flowchart

[pic]

Figure 3.2: Hazardous Waste Management Data Flowchart

Figure 3.2: Emergency Hazardous Waste ID management Flowchart

4 MANAGED ENTITY FIESTA

See FIESTA BUSINESS DATA MAINTENANCE HELP.



An ME form (screen) contains the basic details of the physical location of a facility. The details tracked in the site form include site name, county, address and coordinates. Information recorded in the site form is shared by every program.

4.1 MANAGED ENTITY

5. PRE-HANDLER (non-notifier)

A pre-handler form is used as a temporary holding area to hold and process the information required to obtain an EPA ID. Once the ID is issued, pre-handler record will be deleted from the system. District users must use this form to obtain EPA ID number for facilities that were inspected and require data entry but have no EPA ID. Tallahassee staff must use this form to process the notification form (EPA Form 8700-12FL) data that they receive from the public. Several data validation scripts are incorporated into the form to validate the data thoroughly and check for completeness before issuing the EPA ID. Before beginning the pre-handler data entry, follow the appropriate guidelines because they are different for each user. Guidelines for entering and promoting pre-handler data are divided into 3 groups as follows.

1) Guidelines for entering inspection data for the purpose of obtaining an EPA ID number. (Applicable to district staff only).

The pre-handler form has 2 pages. Every field on each page must be entered in order to obtain the EPA ID. In cases where data is not available or unknown, default data is supplied by the system or the operator responsible for issuing the EPA ID. For example, if the SIC code data on page 4 is unknown, default value 0011 (Unknown) will be supplied by the system. User must at least supply the following values to create a pre-handler record. User will not be able to save the pre-handler record unless the following values are supplied.

ME Name *

ME Number *(Sometimes also referred to as COMET site number)

Source *(Inspection or Notification)

County *, District *

Affiliation data : Facility, Mailing, Contact address, Legal owner*

Date Site Inspected or Notification Form Received *

Facility Waste Activity or Facility Status * (LQG, SQG, CESQG, etc.)

NAICs code

Waste code

Any additional data beyond the above details are highly recommended, but are not mandatory to obtain an EPA ID. District staffs are responsible only for entering the pre-handler record. Within 2 to 3 days after the pre-handler is entered, Tallahassee staff will issue an EPA ID for the pre-handler and will provide that number to the district staff user via email.

2) Guidelines for entering notification data for the purpose of obtaining an EPA ID.

(Applicable only to Tallahassee staff who are responsible for processing notification

forms).

The pre-handler form is designed to closely match the format of a notification form (EPA Form 8700-12FL) because 70% to 80% of the data records for a pre-handler form are derived from a notification form. Every data item on the notification form is present on the pre-handler form and in the same order.

Before entering data in a pre-handler form, a user must determine the managed entity / environmental interest and affiliation data for the address location indicated on the notification form. A ME number can be found on the ME screen by querying the address and/or site name. If the user is unable to locate a ME, then a ME record must be created. Before creating the managed entity, user must determine the coordinates for the site location to enter on the site form.

Once the site number is determined for the facility address on the notification form, a user can create a pre-handler record by transferring the data from a notification form to a pre-handler form.

3) Guidelines for promoting pre-handler data for the purpose of obtaining an EPA ID.

(Applicable only to Tallahassee staff who are responsible for generating EPA ID

numbers).

Issuing an EPA ID for a pre-handler is sometimes also referred to as promoting a pre-handler or generating an EPA ID. Once the pre-handler is promoted, an EPA ID will be generated for the address location noted in the pre-handler and the facility will be called a handler.

Before promoting a pre-handler, a user must check the data for completeness. Unless all the fields on page 1, coordinates on page 2, and at least one status on page 3 are filled in, COMHAZ will not allow the pre-handler to be promoted. If a required data element is not present on page 1 then enter a default value. For example, if the contact person’s phone number is not present on page 1, then supply (999)999-9999 as a default. For a list of default values, refer to the Pre-handler New section following these guidelines.

Once promoted, data from pre-handler table will be transferred to a handler table and the pre-handler record will be permanently deleted from the system. For an inspection source pre-handler record (originally created by district staff), COMHAZ will generate an e-mail notifying the EPA ID. The user must then forward the e-mail to the respective district staff person.

5.1 PRE-HANDLER or NON-NOTIFIER - NEW

To create a new pre-handler record in COMHAZ, select to create new ME/ EI / Affiliation record in FIESTA. Select EI Supporting Info menu to open CHAZ record. Then click Pre-Handler menu.

[pic]

Figure 5.1:Pre-handler record

The pre-handler form has 4 tabs as shown in figures 5.2 To create the pre-handler record enter the required information and press the [CTRL] [F6](COMMIT) key or [pic]. System will display an error message if any required information is missing and also indicates the type of missing information.

[pic]

Figure 5.2: Creating a Pre-handler Record.

Description for each field in the pre-handler screen is as follows:

Name: Name of the facility.

When a site ID is entered, the name is automatically populated.

ME ID: Unique site ID assigned for this facility in the FIESTA screen.

After click on EI supporting Info, all prehandler information will show up.

Source: Code indicating the data source for the current pre-handler record.

Even though several values are available in the list of values, COMHAZ is currently designed to accommodate only 2 sources which are ‘S’ (Inspection) an and ‘N’ (Notification). District staff must always choose ‘S’ and Tallahassee staff must always choose ‘N’.

Address: Facility location address.

Addresses having Post Office Box numbers are not allowed.

District: DEP district office jurisdiction in which this facility is located.

City: Name of the city where the facility is located.

State: Name of the state where the facility is located.

‘FL’, for Florida, is the only value allowed because EPA ID numbers are not assigned for out-of-state facilities at this time.

Zip: Zip code of the location.

Date: Date on which facility is first inspected by the inspector or notification form is received.

Mailing Address:

Facility mailing address (or the post office box number).

Mailing City: City where facility mailing address is located.

Mailing State: State where mailing address is located.

Mailing Zip: Zip code where mailing address is located.

Contact Name L:

Last name of the person who is familiar with the handler’s operation and the information provided to the agency (DEP).

Enter ‘NOTIFIER’ as the last name if it is unknown and the source is inspection.

Contact Name F:

First name of the person who is familiar with the handler’s operation and the information provided to the agency (DEP).

Enter ‘NON’ as the first name if it is unknown and the source is inspection.

Contact Title: Title of the contact person.

Contact Phone:Telephone number associated with the contact.

Enter (999)999-9999 if the telephone number is unknown.

Contact Address:

Street address of the contact person.

Contact City: City where the contact person’s address is located.

Contact State: State where the contact person’s address is located.

Contact Zip: Zip code of the contact person’s address.

Owner Name:The legal name of the person, firm, public organization, or other entity that owns or operates the facility.

Enter ‘NON NOTIFIER’ as the name if it is unknown and the source is inspection.

Owner Type: Code indicating the owner/operator type.

Land Type: Code indicating the owner/operator land type.

Legal Owner Address: Street address of the owner.

Legal Owner City: City where the owner address is located.

Legal Owner State: State where the owner address is located.

Legal Owner Zip: Zip code of the owner address.

Legal Owner Phone:

Telephone number associated with the owner.

Enter (999)999-9999 if the telephone number is unknown.

Method: Method used for determining the coordinates.

Coordinates: Latitude and longitude coordinates in degrees, minutes, and seconds.

The system will generate an error message if the latitude or longitude coordinate values don’t fall within the geographical boundary of the county specified on page 1.

Directions: Directions to the facility.

Comments: Comments.

[pic]

Figure 5.3: Creating a Pre-handler Record.

[pic]

Figure 5.4: Creating a Pre-handler Record.

[pic]

[pic]

[pic]

[pic]

[pic]

[pic]

[pic]

[pic]

Figure 5.5: Creating a Pre-handler Record.

Generator: Field indicating that the handler is engaged in the generation of hazardous waste. Indicate the appropriate generator type by entering ‘X’ in either LQG (large quantity generator) field, SQG (small quantity generator) field, CES (conditionally exempt small quantity generator) field or NHR (non-handler) field.

At least one status indicator (Generator Indicator, TSD Indicator, Transporter Indicator, Used Oil Recycler Indicator, Burner/Blender Indicator, Underground Injection Control Indicator or Recycler) is required for every pre-handler.

[pic]

Figure 5.3.1: Waste Activity Status Screen Displaying the Transporter Details.

Transporter tab: Flag indicating that the handler is engaged in the transportation of hazardous waste.

At least one status indicator (Generator Indicator, TSD Indicator, Transporter Indicator, Used Oil Recycler Indicator, Burner/Blender Indicator, Underground Injection Control Indicator or Recycler) is required for every pre-handler.

Transporter Status:

Transporter status indicator.

Enter ‘(’ to indicate the transporter status. A user must also indicate the appropriate transportation mode if either the Own Waste and/or Commercial Waste boxes are checked.

TSD: Hazardous waste treatment, storage and/or disposal indicator.

Enter ‘(’ to indicate the treatment, storage and/or disposal status.

At least one status indicator (Generator Indicator, TSD Indicator, Transporter Indicator, Used Oil Recycler Indicator, Burner/Blender Indicator, Underground Injection Control Indicator or Recycler) is required for every pre-handler.

Used Oil tab:Flag indicating that the handler is engaged in used oil related activities.

At least one status indicator (Generator Indicator, TSD Indicator, Transporter Indicator, Used Oil Recycler Indicator, Burner/Blender Indicator, Underground Injection Control Indicator or Recycler) is required for every pre-handler.

[pic]

Figure 5.3.2: Waste Activity Status Screen Displaying the Used Oil Details.

Used Oil Status - Marketer:

Flag indicating that the handler directs shipments of used oil to burners.

Enter ‘X’ in the Off-Spec Burner field if the handler is engaged in marketing of off-spec. Used oil fuel other than generator marketing to burner (e.g., marketing to used oil refinery). Enter ‘X’ in the First Claimant field if the handler is a marketer who first claims the used oil meets the specifications.

Used Oil Status - Burner:

Flag indicating that the handler is engaged in the burning of used oil fuel.

Indicate the appropriate burning device by entering ‘X’.

Used Oil Status - Transporter:

Flag indicating that the handler is engaged in used oil transportation and/or transfer facility activities.

Used Oil Status - Processor:

Flag indicating that the handler is engaged in processing and/or re-refining used oil activities.

Used Oil Status - Generator:

Flag indicating that the handler is engaged in generating used oil.

Recycler: Flag indicating that the handler is engaged in recycling hazardous waste.

At least one status indicator (Generator Indicator, TSD Indicator, Transporter Indicator, Used Oil Recycler Indicator, Burner/Blender Indicator, Underground Injection Control Indicator or Recycler) is required for every pre-handler.

HW Fuel tab:Field indicating that the handler is engaged in the burning and/or blending of hazardous waste.

At least one status indicator (Generator Indicator, TSD Indicator, Transporter Indicator, Used Oil Recycler Indicator, Burner/Blender Indicator, Underground Injection Control Indicator or Recycler) is required for every pre-handler.

[pic]

Figure 5.3.3: Waste Activity Status Screen Displaying the Burner/Blender Details.

HW Fuel Status:

Hazardous waste fuel burner, blender or marketer indicator.

User must also specify the appropriate combustion device if the handler is engaged in any burning/blending activity (BIF/Industrial Furnace, Smelter Deferral, Small Quantity Exemption).

UIC: Flag indicating that the handler generates and or treats, stores, or disposes of hazardous waste and has an injection well located at the installation.

At least one status indicator (Generator Indicator, TSD Indicator, Transporter Indicator, Used Oil Recycler Indicator, Burner/Blender Indicator, Underground Injection Control Indicator or Recycler) is required for every pre-handler.

OTHER: Flag indicating other state regulated programs.

[pic]

Figure 5.3.4: Waste Activity Status Screen Displaying the State Regulated Programs.

PCW: Flag indicating that the handler is engaged in transporting petroleum contact water.

Mercury: Flag indicating that the handler is engaged in managing (transporter, transfer facility, storer etc,) mercury-containing devices.

Batteries: (Reserved for future use)

Pesticides: (Reserved for future use)

Oil Filters: Flag indicating that the handler is engaged in transporting used oil filters.

[pic]

Figure 5.4: Creating a Pre-handler Record.

NAIC - Primary: Standard Industrial Classification code indicating the primary activity of the facility.

Press [Ctrl] [l] or right mouse click, select Edit, Display List or right mouse click, select Calender/LOV or [pic] list of values for a list of valid codes.

SIC - Secondary:

SIC code indicating the secondary activity of the facility.

[pic]

Figure 5.5: Creating a Pre-handler Record.

Waste Code: Waste Code(s) used to identify a hazardous waste or properties of a hazardous waste associated with the handler.

5.2 PRE-HANDLER - OPEN

To open an existing pre-handler record in COMHAZ, select the OPEN ME data in FIESTA and press the [ENTER] key.to open ME record. Then select EI supporting Info menu. Click back button and click Pre-Handler. To navigate to the record use [Move next] [Move to last page] icon on the menu bar.

[pic]

Figure 5.6: Opening a Pre-handler Record.

ME Status is flagged to “Reviewed’ or “REVW” till the data clearing house has approved it. It will change from “REVW” to “APPR”. New prehandler records are subject to be check by Dataclearing house staff.

[pic]

Figure 5.7: Opening a Pre-handler Record : Approved Status

5.3 PRE-HANDLER - PROMOTE

Promoting will assign an EPA ID number for the pre-handler location. This EPA ID will be

generated by COMHAZ. Once promoted, pre-handler data will be moved to the handler related tables and the pre-handler record will be deleted permanently. Before promoting, a user must check the pre-handler record for completeness. To promote a pre-handler, open the pre-handler record and from the PRE-HANDLER command select the Promote sub-menu as shown in Figure 5.7. Upon pressing the [ENTER] key, COMHAZ will run several validation scripts against the data and show a confirmation screen (Figure 5.8).

[pic]

Figure 5.8: Pre-handler Screen Displaying the EPA ID.

Note the EPA ID number and press any key to accept and exit from the screen. A message will be displayed at the bottom of the screen confirming the promotion and deletion of the pre-handler. COMHAZ will also generate and send an e-mail containing EPA ID details to the user who promoted the pre-handler. This e-mail must be forwarded to the original user who created the pre-handler.

6. HANDLER

A handler form contains the facility information in detail. Every facility record that exists in the handler table has a 12 character unique ID referred as EPA ID or handler ID. This ID always starts with letters “FL’. A handler ID is assigned for a location but not for company name. The handler form has 6 pages, and each page contains information specific to the ID displayed on page 1.

The handler menu has several sub-menu items as shown in Figure 6.4. Some of the sub-menu items will be enabled only when a user selects an EPA ID.

6.1 HANDLER - OPEN

To open, view handler information. Select query ME information and EI data then click EI Supporting Info submenu on the task bar.

To open, view and/or update handler information select the [Open] sub-menu from the [Handler] menu as shown in Figure 6.1 and press the [ENTER] key. Page 1 of the handler form will be displayed (Figure 6.4) in enter-query mode.

[pic]

Figure 6.1: Menu Option to Open a Handler Record.

[pic]

Figure 6.2: Handler Form in Enter-Query Mode.

Enter the search criteria, and press the [F12] (EXECUTE QUERY) key or [pic] to retrieve the handler records. Whichever fields the cursor is able to navigate in enter-query mode are the only fields in which search criteria can be specified. Once the [F12] (EXECUTE QUERY) key or [pic] is pressed, a new browse screen will be displayed with search results matching the query criteria (Figure 6.3).

[pic]

Figure 6.3: Handler Browse Screen Displaying the Search Results.

This screen is also referred to as the handler browse screen. Press the [PAGE DOWN] key / double click to display details (Figure 6.4).

[pic]

Figure 6.4: Handler Details : Contacts information..

Accessing the above handler details page is sometimes referred to as selecting a handler or opening a handler. The handler form has only one page and each ten tabs display the following details:

Page 1 - Facility ID, name, location address, mailing address and coordinates.

Tab 1 - Facility contact information.

Tab 2 - Facility owner/operator information.

Tab 3 - Facility location

Tab 4 - Facility waste activities (LQG, SQG etc.).

Tab 5 - Facility NAIC code information.

Tab 6 - Facility waste code.

Tab 7 - Facility projects.

Tab 8 - Facility violations.

Tab 9 - Facility letters.

Tab 10 – Facility permit status.

NAIC - Primary: Standard Industrial Classification code indicating the primary activity of the facility.

Press [Ctrl] [l] or right mouse click, select Edit, Display List or right mouse click, select Calender/LOV or [pic] list of values for a list of valid codes.

SIC - Secondary:

SIC code indicating the secondary activity of the facility.

Information in page 1 of the handler form and information in tabs requires a change of status form for updates in FIESTA except for the waste activities, waste code, projects, violations and permit status. Updates are also restricted to users who have a CHAZ USER role.

Description for each field on page 1 of handler screen is as follows,

EPA ID: Unique EPA ID assigned for the handler location.

Updating this field is not allowed.

ME ID: Unique ID assigned on Managed Entity screen for the handler location.

ME ID acts as a link between FIESTA and COMHAZ. Every EPA ID is associated with a ME ID. Updating this field is not allowed.

Previous EPA ID:

Handler EPA ID associated with its previous location.

Handler Name Submitted Name:

Handler name.

Change of status form is required to change the name. When name is changed, previous name will be saved in the database along with its EPA ID.

District: DEP district office jurisdiction in which this facility is located.

ME Name: Name of the Managed Entity as it appears on the ME screen.

This name could be different from the handler name because there are no built-in constraints in the ME form, unlike the handler form, to prevent updates. It must be remembered that the ME record is shared by the entire Department staff. Additionally, when a change of status form is received requesting a name change, only the handler name or submitted name is changed. The ME name is left unchanged.

Address: Street address of the handler location.

City: City or town of the handler location address.

State: State of the handler location address.

Zip: Zip code of the handler location address.

County: County in which handler is located.

Mail Address: Street address for mailings.

Mail City: City or town in the mailing address.

Mail State: State in the mailing address.

Mail Zip: Zip code in the mailing address.

Land Type: Code indicating the facility land type.

Pre-handler: Non-notifier Indicator.

This Flag indicates that the handler has been identified through a source other than Notification.

Access: Handler Accessibility Indicator.

Code indicating the reason why the handler is not accessible for normal RCRA tracking and processing. Press [Ctrl][l] or LOV key for valid codes.

Access Date: Date from which Accessibility Indicator is effective.

Notification Date:

Date on which handler was originally identified.

Location tab:

Feature: Short description of the handler's distinguishing landmark(s).

Method: Method used for determining the latitude and longitude.

Datum: Geographic computation datum value.

Datum (Horizontal Datum) is the basis on which the coordinate system is developed. Currently only two values are available in the system which are 27 and 83 (1927 and 1983). The third and the current datum (83-89) on which GPS locators determine the coordinates will be available soon.

Date: Date on which the coordinates are determined/updated.

Latitude: Site latitude in degrees, minutes and seconds.

System has a built in procedure to check if latitude is within the geographic location of the county mentioned above.

Longitude: Site longitude in degrees, minutes and seconds.

System has a built in procedure to check if longitude is within the geographic location of the county mentioned above.

UTM: UTM coordinates.

Latitude and Longitude coordinates are preferred over UTM coordinates.

6.2 HANDLER - CONTACTS

Select the first tab or CoNtacts tab to view contact information of handler

.

[pic]

Figure 6.5: First tab of the Handler Form Showing the Contact Information.

In order to view any record of contact information. Move the cursor to

specific record. Then double click your left mouse to retrieve contact information. The affiliation maintenance form will popup (Figure 6.6). Update and add new record is done in FIESTA module.

[pic]

Figure 6.6: Affiliation Maintenance screen.

One contact record at a time is shown in the contact screen. This screen is also capable of tracking contact information for eight contact types, emergency contact, facility contact, notifier, operator, onsite-contact, owner, requestor and underwriter. Only one record is allowed for any given contact type. Contact information is updateable, except for the value in the type field. To record a new contact, press the [INSERT] (CREATE RECORD) key in FIESTA module or [pic] and enter the values.

Description for each field in page 2 of handler screen (contact screen) is as follows,

Name L: Last name of the contact person.

Name F: First name of the contact person.

Title: Title of the contact person.

Address: Street address for the contact type.

City: City or town in the contact address.

State: State in the contact address.

Zip: Zip code in the contact address.

6.3 HANDLER - OWNER/OPERATOR

In order to add, update owner/operator information you have to go to FIESTA page.

CHAZ – Handler only let you view owner/operator information. Double click on the record to see owner information in Affiliation Maintenance screen.

[pic]

Figure 6.7: Owner/Operator brows Information.

[pic]

Figure 6.8: Owner/Operator Information.

Description for each field on the handler screen (owner/operator screen) is as follows,

Indicator: Code indicating whether the data is associated with a owner or operator.

Current and previous owner or operator is not used for CHAZ-IMS. If the end date has entered, the owner or operator is no longer active for that facility.

OPR is the code for Operator and OWN is the code for Owner

Org or Individual Name: Name of the current or previous owner/operator.

Address: Street name of the current or previous owner/operator.

City: City or town in the address of the current or previous owner/operator.

State: State in the address of the current or previous owner/operator.

Zip: Zip in the address of the current or previous owner/operator.

Phone: Phone number of the current or previous owner/operator.

Type: Code indicating the owner/operator type.

Date: Date indicating when the owner/operator changed.

6.4 HANDLER - SOURCE - STATUS

The status screen (also called hazardous waste activities screen) displays handler status (LQG, TRA, TSD etc.). Status information is determined from 2 sources (Notification and/or Inspection). In some cases where a facility is a TSD, status may also be determined from a third source (Part A data). This third source is applicable only to historical data. Status of only one source is displayed at a time. A user must use the [UP] or [DOWN] arrow keys to toggle between different sources. COMHAZ will not allow the creation of status information for more than 2 sources. Add/update privileges for inspection source status records are restricted to district staff who have INSPECTOR role. Similarly, add/update privileges for notification source status records are restricted to Tallahassee staff who have USER roles.

To add the handler status information, Double click the empty record. Activities information will show up to let user enter data.

To update and/or view the handler status information, Double click the record you want to modified.

[pic]

Figure 6.9: Handler Activities tab Showing Handler Status Information.

[pic]

Figure 6.10: Handler Activities tab Showing Handler Status Information of Inspection source.

The following section in bold is applicable only to district staff:

To add/update the inspection status record, access the status screen, and using the

[UP] or [DOWN] arrow keys, locate the status record of the inspection source (Source is displayed at the bottom of the screen). If a status record of the inspection source already exists then update the appropriate fields and save the information. If a status record of inspection source does not exist in COMHAZ then press the [INSERT] (CREATE RECORD) key. COMHAZ will automatically create an empty inspection source record. Update the fields and press the [CTRL] [F6] (COMMIT) key to save the record.

The following section in bold is applicable only to Tallahassee staff:

To add/update the notification status record, access the status screen and, using the

[UP] or [DOWN] arrow keys, locate the status record of notification source (source is displayed at the bottom of the screen). If a status record of the notification source already exists then update the appropriate fields and save the information. If a status record of the notification source does not exist in the system, then press the [INSERT] (CREATE RECORD) key. COMHAZ will automatically create an empty notification source record. Update the fields and press the [CTRL] [F6] (COMMIT) key to save the record.

Description for each field on waste activities of handler screen (status screen) is as follows:

Generator: Field indicating that the handler is engaged in the generation of hazardous waste.

Indicate the appropriate generator type by entering ‘(’ in either LQG (large

quantity generator) field, SQG (small quantity generator) field, CES (conditionally exempt small quantity generator) field, NHR (non-handler) field or Closed field.

At least one status indicator (Generator Indicator, TSD Indicator, Transporter Indicator, Used Oil Recycler Indicator, Burner/Blender Indicator, Underground Injection Control Indicator or Recycler) is required for a handler.

If the Closed field is checked then the remaining indicators will automatically be updated to reflect a null value. A user will not be able to access any other field except date and comments.

[pic]

Figure 6.11.1: Waste Activities of Handler Form Displaying the Status Including Transporter Details.

*Transporter: Flag indicating that the handler is engaged in the transportation of hazardous waste

At least one status indicator (Generator Indicator, TSD Indicator, Transporter Indicator, Used Oil Recycler Indicator, Burner/Blender Indicator, Underground Injection Control Indicator, or Recycler) is required for every handler.

Transporter Status:

Transporter status indicator.

Enter ‘(’ to indicate the transporter status. A user must also indicate the appropriate transportation mode if either the Own Waste and/or Commercial Waste boxes are checked.

TSD: Hazardous waste treatment, storage and/or disposal indicator.

Enter ‘(’ to indicate the treatment, storage and/or disposal status. At least one status indicator (Generator Indicator, TSD Indicator, Transporter Indicator, Used Oil Recycler Indicator, Burner/Blender Indicator, Underground Injection Control Indicator, or Recycler) is required for every handler.

[pic]

Figure 6.11.2: Waste Activity of Handler Form Displaying the Status Including Used Oil Details

Used Oil tab: Flag indicating that the handler is engaged in used oil related activities.

At least one status indicator (Generator Indicator, TSD Indicator, Transporter Indicator, Used Oil Recycler Indicator, Burner/Blender Indicator, Underground Injection Control Indicator, or Recycler) is required for every handler.

Used Oil Status - Marketer:

Flag indicating that the handler directs shipments of used oil to burners.

Enter ‘X’ in the Off-Spec Burner field if the handler is engaged in marketing of

off-spec. used oil fuel other than generator marketing to burner (e.g. marketing to used oil refinery).

Enter ‘(’ or click in the First Claimant field if the handler is a marketer who first claims the used oil meets the specifications.

Used Oil Status - Burner:

Flag indicating that the handler is engaged in the burning of used oil fuel.

Indicate the appropriate burning device by entering ‘(’.

Used Oil Status - Transporter:

Flag indicating that the handler is engaged in used oil transportation and/or transfer facility activities.

Used Oil Status - Processor:

Flag indicating that the handler is engaged in processing and/or re-refining used oil activities.

Used Oil Status - Generator:

Flag indicating that the handler is engaged in generating used oil.

Recycler: Flag indicating that the handler is engaged in recycling hazardous waste.

At least one status indicator (Generator Indicator, TSD Indicator, Transporter Indicator, Used Oil Recycler Indicator, Burner/Blender Indicator, Underground Injection Control Indicator, or Recycler) is required for every handler.

`

[pic]

Figure 6.8.3: Waste Activity of Handler Screen Displaying the Status Including HW Fuel Details

HW Fuel tab: Flag indicating that the handler is engaged in the burning and/or blending of hazardous waste.

At least one status indicator (Generator Indicator, TSD Indicator, Transporter Indicator, Used Oil Recycler Indicator, Burner/Blender Indicator, Underground Injection Control Indicator, or Recycler) is required for every handler.

FUEL ACTIVITIES:

Hazardous waste fuel burner, blender or marketer indicator.

User must also specify the appropriate combustion device if the handler is engaged in any burning/blending activity (BIF/Industrial Furnace, Smelter Deferral, Small Quantity Exemption).

[pic]

Figure 6.11.4: Waste activities of Handler Displaying the Status Including UIC.

UIC: Flag indicating that the handler generates and or treats, stores, or disposes hazardous waste and has an injection well located at the installation.

At least one status indicator (Generator Indicator, TSD Indicator, Transporter Indicator, Used Oil Recycler Indicator, Burner/Blender Indicator, Underground Injection Control Indicator, or Recycler) is required for every handler.

[pic]

Figure 6.11.5: Waste activities of Handler Displaying the Status Including Other State Regulated Activities.

*OTHER: Flag indicating other state regulated programs.

PCW: Flag indicating that the handler is engaged in transporting petroleum contact water.

Mercury: Flag indicating that the handler is engaged in managing (transporter, transfer facility, storer, etc.) mercury containing devices.

Batteries: (Reserved for future use)

Pesticides: (Reserved for future use)

Oil Filters: Flag indicating that the handler is engaged in transporting used oil filters.

[pic]

Figure 6.8.5: Page 4 of Handler Displaying the Status Including Correspondence Details.

*CORR: Flag indicating the presence of correspondence details

Do not enter any data in this field. This field is used only as an indicator. Actual details are recorded in a secondary screen. To access the secondary screen, press [Ctrl][E] key or [pic] or click the right mouse button then select Edit or LOV. A pop-up secondary screen will display the actual data fields (Figure 6.8.5).

CORRESPONDENCE DETAILS:

Correspondence letters generated and mailed since October 1996.

EPA ID: Handler identification as it appears in page 1 of handler form.

Update is not allowed on this field.

Source: Source for the current handler status.

This field is automatically updated by the system.

Date: Date from which the current status is effective.

This field must be updated when status is added or updated.

Comments: Comments.

6.5 HANDLER - SIC

Tab 5 of the handler form displays NAIC / SIC code details. To add, update SIC code information, open the FIESTA. Screen viewing is the only option available in CHAZ.

[pic]

Figure 6.12: Waste Activities of the Handler Form Showing the NAIC / SIC Code Information.

Description for each field in tab 5 of handler screen (NAIC / SIC code screen) is as follows:

NAIC - Primary: Standard Industrial Classification code indicating the primary activity of the facility.

Press the [Ctrl][L] or LOV or [pic] key for a list of valid codes.

Primary field is “Y”.

NAIC - Secondary:

NAIC code indicating the secondary activity of the facility.

Primary field is “N”.

6.6 HANDLER - WASTE

Tab 6 of the handler form displays waste code details. To add, update and/or view waste code information, open the Handler screen and while the cursor is on tab 6 press double click on the record. In addition, waste code information can also be retrieved by selecting the SOURCE-WASTE CODES sub-menu from the Handler menu while the cursor is on tab 6 of the handler screen. To add a waste code simply press the [Ctrl][I] (CREATE RECORD) key or [pic] and enter the value. To update a waste code, select the code to be updated and type a new value.

[pic]

Figure 6.13: Tab 6 of the Handler Form Showing the Waste Code Information.

Description for each field in tab 6 of handler screen (waste code screen) is as follows:

SOURCE: Source for the current waste code.

Allowed values are ‘N’ for notification and ‘S’ for inspection. The selected source must also have a status record in tab 4 of handler form.

CODE: Waste Code(s) used to identify a hazardous waste or properties of a hazardous waste associated with the handler.

Press [Ctrl][L] or LOV or [pic] for a list of valid codes.

6.7 HANDLER - TRANSPORTER

The transporter form is used for tracking registration information pertaining to transporters who transport hazardous waste in Florida. By law these transporters are required to register with the department. The transporter form tracks both in and out-of-state transporters. Every transporter must have an EPA ID number and in-state transporters (EPA ID starts with letters ‘FL’) must also submit a notification form. Add/update privileges for transporter registration are limited to users having HW MANAGEMENT privilege. To add, update and/or view the transporter registration data, log into COMHAZ and select Transporter button from

the Handler menu as shown in Figure 6.14.

[pic]

Figure 6.14: Menu Option to Access the Hazardous Waste Transporter Registration Data.

Upon selecting a TRANSPORTER, COMHAZ will display the transporter form as shown in

Figure 6.15.

[pic]

Figure 6.15: Hazardous Waste Transporter Registration Data Tracking Form.

Initially, the transporter form will be displayed in data entry mode. To create a transporter record, simply type the data starting with EPA ID of the transporter. If the ID starts with the letters ‘FL’ then COMHAZ performs the necessary validation before accepting it. Once the data entry is completed, press [CTRL] [F6] (COMMIT] or [pic] to save the record.

To update or view an existing transporter record, first retrieve the record by following 3 simple steps:

1) Press the [F11] (ENTER QUERY) or [pic] key.

2) Specify the query criteria.

3) Press the [F12] (EXECUTE QUERY) or [pic] key.

Based on the query criteria, COMHAZ may retrieve multiple records. Using the [UP] and [DOWN] arrow keys a user can browse through the records to locate any particular record. Once the desired record is located, update the information and press [CTRL] [F6] (COMMIT) or [pic] to save the changes.

Description for fields in transporter form is as follows.

EPA ID: Unique federal EPA ID assigned for the transporter.

Name: The name of the transporter as it appears on the notification form.

Last Update: Date on which this record was last updated.

Site Address: Street address of the transporter location.

This address must match with the location address on page 1 of the handler form.

City: The city or town of the location address.

St: State in which the transporter is located.

Zip: Zip code of the location address.

District: DEP district office in which the transporter is located.

Mailing Address:

Mailing address for the transporter.

Mailing City: City of the mailing address.

Mailing St: State in which the mailing address is located.

Mailing Zip: Zip code of the mailing address.

Contact Name:Name of the contact person.

Phone: Telephone number of the contact person.

Insurance Co: Name or abbreviation of the insurance company that provided insurance to the transporter.

Effective Date:Date from which the insurance is effective.

Policy No: Insurance policy number.

Expiry date: Date on which insurance policy expires.

TF: Flag (‘Y’ or blank) indicating whether the transporter is a transfer facility.

Storage Capacity:

Storage capacity of the transfer facility.

Commercial: Flag (‘Y’ or blank) indicating whether the facility is a commercial transporter.

Transporter Status:

Code indicating the current registration status.

Every code that starts with letter ‘C’ indicates that the registration is current.

Comments: Comments.

6.8 HANDLER -UNIVERSAL WASTE -MERCURY

The Mercury form is used for tracking registration and permitting information pertaining to facilities handling lamps and devices containing mercury waste. Currently this form tracks only in-state (handlers having EPA ID that starts with letters ‘FL’) facilities. In the future, this form will be modified to track out-of-state mercury handlers who have registered with the department. Add/update privileges for mercury registration data are limited to users having HW MANAGEMENT privilege. Add/update privileges for permitting data are limited to users having INSPECTOR and MANAGEMENT roles. To add, update and/or view the mercury registration data, log into COMHAZ and select the [UNIVERSAL WASTE] Mercury sub-menu from the Handler menu as shown in Figure 6.16.

[pic]

Figure 6.16: Menu Option to Access the Mercury Handler Registration Data.

Once the Mercury sub-menu is selected, COMHAZ will display the mercury form as shown in Figure 6.17.

[pic]

Figure 6.17: Mercury Handler Registration Tracking Form.

Initially, the mercury screen will be displayed in data entry mode. To create a record, simply type the data starting with the EPA ID of the transporter. If the ID starts with letters ‘FL’ then COMHAZ performs the necessary validation before accepting it. Once the data entry is completed, press [CTRL] [F6] (COMMIT) or [pic] to save the record.

To update or view an existing mercury handler record, first retrieve the record by following 3 simple steps:

1) Press the [F11] (ENTER QUERY) or [pic] key.

2) Specify the query criteria.

3) Press the [F12] (EXECUTE QUERY) or [pic] key.

Based on the query criteria, system may retrieve multiple records. Using [UP] and [DOWN] arrow keys to browse through the records and locate the record. Once the desired record is located, update the information and press [CTRL] [F6] (COMMIT) or [pic] key to save the changes.

Description for fields in mercury screen is as follows.

EPA ID: Unique federal EPA ID assigned for the mercury handler.

Name: The name of the handler as it appears on the notification form.

REGISTERED - Transporter - Lamps:

Flag indicating that handler is engaged in transporting mercury containing lamps.

REGISTERED - Transporter - Devices:

Flag indicating that handler is engaged in transporting mercury containing devices.

REGISTERED - Storage Facility - Lamps:

Flag indicating that handler is a storage facility for mercury lamps.

REGISTERED - Storage Facility - Devices:

Flag indicating that handler is a storage facility for mercury devices.

REGISTERED - Reverse Dist Program - Lamps:

Flag indicating that handler operates a reverse distribution program for mercury lamps or devices.

REGISTERED - Reverse Dist Program - Devices:

Flag indicating that handler operates a reverse distribution program for mercury devices.

REGISTERED - Valid Until:

Registration Expiration date.

PERMITTED - Storage - Lamps:

Flag indicating that handler is a permitted storage facility for mercury lamps.

PERMITTED - Storage - Devices:

Flag indicating that handler is a permitted storage facility for mercury devices.

PERMITTED - Volume Reduction - Lamps:

Flag indicating that handler is a permitted volume reduction facility for mercury lamps.

PERMITTED - Volume Reduction - Devices:

Flag indicating that handler is a permitted volume reduction facility for mercury devices.

PERMITTED - Mercury Recovery - Lamps:

Flag indicating that handler is a permitted mercury recovery facility for mercury lamps.

PERMITTED - Mercury Recovery - Devices:

Flag indicating that handler is a permitted mercury recovery facility for mercury devices.

PERMITTED - Mercury Reclamation - Lamps:

Flag indicating that handler is a permitted mercury reclamation facility for mercury lamps.

PERMITTED - Mercury Reclamation - Devices:

Flag indicating that handler is a permitted mercury reclamation facility for mercury devices.

PERMITTED - Other Mercury Wastes:

Flag indicating that handler is permitted for handling mercury waste other than lamps or devices.

PERMITTED - Commodity Grade Mercury - Lamps:

Flag indicating that handler is permitted for handling commodity grade mercury.

PERMITTED - Valid Until:

Permit Expiration date.

Comments: Comments.

6.9 HANDLER -UNIVERSAL WASTE -PCW

(Reserved for future use)

6.10 HANDLER -UNIVERSAL WASTE -PESTICIDES

(Reserved for future use)

6.11 HANDLER -UNIVERSAL WASTE -BATTERIES

(Reserved for future use)

6.12 HANDLER - USED OIL

Used oil form is used for tracking registration information pertaining to handlers who manage used oil and used oil filters in Florida. Managing used oil and used oil filters includes transporting, processing, marketing, and burning, etc. By law these handlers are required to register with the department. Used oil form tracks both in and out-of-state used oil handlers. Every handler must have EPA ID number and in-state handlers (Having EPA ID that starts with letters ‘FL’) must also submit a notification form. Add/update privileges for used oil registration data are limited to users having HW MANAGEMENT privilege. To add, update and/or view the used oil registration data, log into COMHAZ and select Used oil sub-menu from Handler menu as shown in Figure 6.18.

[pic]

Figure 6.18: Menu Option to Access the Used Oil Registration Data.

Once the USED OIL sub-menu is selected, system will display the used oil form as shown in Figure 6.19.

[pic]

Figure 6.19: Used Oil Registration Data Tracking Form.

Initially the used oil form will be displayed in data entry mode. To create a new record, user has to start in FIESTA. Create ME with Registered Used Oil Handler Managed Entity Type (RUOH) and has Used Oil Program (UOP) for Environmental Interest type.

To modify Use oil handler data simply type the data starting with ME ID or EPA ID. If the ID starts with letters ‘FL’ then system performs necessary validation before accepting it. Once the data entry is completed, press [CTRL] [F6] (COMMIT) key or [pic] to save the record.

To update or view an existing used oil record, first retrieve the record by following 3 simple steps:

1) Press the [F11] (ENTER QUERY) or [pic] key.

2) Specify the query criteria.

3) Press the [F12] (EXECUTE QUERY) or [pic] key.

Based on the query criteria, system may retrieve multiple records. Using [UP] and [DOWN] arrow keys browse through the records and locate the record. Once the desired record is located, update the information and press [CTRL] [F6] (COMMIT) key or [pic] to save the changes.

Description for fields in the used oil form is as follows.

EPA ID: Unique federal EPA ID assigned for the used oil handler.

Fed ID: Federal employer ID.

Phone: Phone number

Toll Phone: Toll free phone number for the facility.

Business Name: Legal business name.

Name: Alias name of the facility if any.

County: County in which the facility address is located.

District: District office in which the facility address is located.

Fac Address: Facility address as indicated on the registration form.

For in-state handlers this address must be same as location address on page 1 of handler form.

Fac City: City or town where the facility address is located.

Fac State: State where the facility address is located.

Fac Zip: Zip code for the facility address.

Mail Address: Mailing address for the facility.

Mail City: City or town where the mailing address is located.

Mail State: State where the mailing address is located.

Mail Zip: Zip code for the mailing address.

Transporter - Oil:Flag indicating that handler is engaged in transporting used oil.

Transporter - Filter:

Flag indicating that handler is engaged in transporting used oil filters.

Transfer Facility - Oil:

Flag indicating that handler is a transfer facility for used oil.

Transfer Facility - Filter:

Flag indicating that handler is a transfer facility for used oil filters.

Processor - Oil: Flag indicating that handler is engaged in processing used oil.

Processor - Filter:Flag indicating that handler is engaged in processing used oil filters.

Marketer - Oil: Flag indicating that handler is engaged in marketing used oil.

Burner - Oil: Flag indicating that handler is engaged in burning used oil.

End User - Filter: Flag indicating that handler is a end user of used oil filters.

Contact Name: Name of the contact person.

Contact Phone: Phone number for the contact person.

Owner name: Name of the legal owner.

Owner Phone: Phone number for the owner.

Address: Address for the contact person/owner.

City, ST, Zip: City, State and Zip code in the contact person/owner address.

C Y REG: Current year registered.

F Y REG: First year registered.

Fees Rec Date: Date registration fee is received.

Fees Paid: Amount of registration fee paid.

Permit Num: Registration permit number.

Permit Exp: Permit Expiration date.

Training Required:

Code indicating whether training is required pertaining to handling used oil.

Insur Company: Name of the company that provided the insurance.

Insur Exp: Insurance Expiration date.

Comments: Comments.

6.13 HANDLER – TEMPORARY EPA ID / EMERGENCY ID

Emergency ID form is used for issuing and tracking emergency ID numbers. Emergency ID numbers are issued for facilities that generate hazardous waste on a one-time basis (Ex: spills) and do not have an EPA ID number. Facilities that generate the hazardous waste regularly are required to obtain an EPA ID number. To access the emergency id tracking form, select the Emergency ID sub-menu from Handler menu as shown in Figure 6.17. Selecting the Emergency ID sub-menu will display the emergency ID form as shown in Figure 6.21.

[pic]

Figure 6.20: Menu Option to Access Emergency ID Tracking Form.

[pic]

Figure 6.21: Emergency ID Tracking Form.

Initially the emergency ID form will be displayed in data entry mode. To create a new record, user has to go to FIESTA create ME and EI. Once the data entry is completed, press the [CTRL] [F6] (COMMIT) key or [pic] to save the record and generate a number. The generated number will be displayed in the Emergency EPA ID field.

To update or view an existing emergency ID record, first retrieve the record by following 3 simple steps:

1) Press the [F11] (ENTER QUERY) or [pic] key.

2) Specify the query criteria.

3) Press the [F12] (EXECUTE QUERY) or [pic] key.

Based on the query criteria, the system may retrieve multiple records. Using [UP] and [DOWN] arrows browse through the records and locate the desired record. Once the desired record is located, update the information and press [CTRL] [F6] (COMMIT) or [pic] to save changes.

Following is the description for the data fields in emergency ID form.

Emergency EPA ID:

Emergency ID assigned for the facility.

This value is generated by the system and it is not updatable.

Date: Date on which the ID is requested and generated.

District: DEP district office which processed the request.

Issued By: Name of the user who processed the request.

Requestor Name:

Name of the person who requested the ID.

Phone Number:

Phone number of the requestor.

Generator Name:

Name of the company which generated the waste.

Facility Address:

Location address of the facility.

Facility City: City where the facility is located.

Facility State: State where the facility is located.

Facility Zip: Zip code of the facility location address.

Mailing Name:Name of the facility for mailing purpose.

Mailing Address:

Mailing address of the facility.

Mailing City: City where the mailing address is located.

Mailing State: State where the mailing address is located.

Mailing Zip: Zip code for the mailing address.

Transporter EPA ID:

EPA ID of the transporter who is responsible for transporting the waste.

Transporter EPA ID will be validated to make sure that the transporter registration is current. Press the [Ctrl][L] or LOV or [pic] key for a list of currently registered transporters.

TSDF EPA ID:

Treatment, storage and/or disposal facility EPA ID where this waste is disposed.

Waste Quantity:

Total quantity of waste shipped.

Default unit for waste quantity is GAL (gallons). Press the [Ctrl][L] or LOV or [pic] key for a list of valid units.

Waste Description:

Description of the waste.

Comments: Comments.

W Codes: Waste code(s). A user may enter unlimited number of waste codes in this field.

For a list of valid waste codes press the [Ctrl][L] or LOV or [pic] key.

6.14 HANDLER - LETTERS

Every time a handler record is created or updated as a result of processing a notification form or change of status form, a letter must be generated and mailed to the handler notifying them of the updated status. These letters are generated by the system after the user who is responsible for generating these letters enters the required information. The user must first follow 2 steps explained below:

1) Specify the type of letter to be generated.

2) Run (Print) the generated letter.

This chapter explains how to specify a letter type and chapter 9 sub-chapter Print Letters explains how to print the letters. To specify the type of letter to be generated open the Handler which requires the letter and select NOTIF - LETTERS sub-menu from the Handler menu as shown in Figure 6.19.

[pic]

Figure 6.22: Menu Option to Specify a Letter Type

The Notif letters sub-menu further displays 6 sub-menu items, each representing a different letter type. Select the desired letter type to be generated (processed) and press [ENTER]. A message will be displayed at the bottom of the screen confirming the process. Follow the instructions in chapter 9 sub-chapter Print letters to print the letter(s) that are already processed.

Each sub-menu choice in the Notif letters sub-menu represents a letter type. Use the following criteria to select the appropriate choice.

Sub-Menu choice When to select

New Notifier EPA ID is issued through a notification form.

Status change Status was changed through a change of status form.

Facility name Facility name was changed through change of status form.

Other info chng Other information such as contact, owner/operator details are updated.

Closed/moved Business was relocated or closed.

pre-handler EPA ID is issued through a source other than notification form.

6.15 HANDLER - VIOLATIONS

>>>>>02/17/2006

The handler violation form is used for browsing the violations of any handler. In the handler-violation form updating of violations is restricted. To browse the violations, open the handler and select Violations sub-menu from Handler menu as shown in Figure 6.20.

[pic]

[pic]

[pic]

[pic]

Figure 6.23: Menu Option to Browse the Violations of a Handler.

Selecting the Violations sub-menu will display the violations recorded for the handler as shown in Figure 6.21.

[pic]

Figure 6.21: Violations Browse Screen.

Refer to page 108 for the description of fields in the violation browse screen.

7. PROJECT

A project is used as a folder to contain and track a group of events (activities) for a facility. User may create multiple projects for a fvacility. Every project must be associated with a handler and a program area. . Projects of type complaint are the only exception to the above statement. In COMHAZ when a new project is created, it is automatically associated with a handler and HW program area.

7.1 PROJECT - NEW - COMPLIANCE

To create a new compliance project open the handler and select the NEW sub-menu from Project menu as shown in Figure 7.1. There are 4 menu options available under New sub-menu. Each option represents the reason that will be assigned for the new project. Select the COMPLIANCE option and press the [ENTER] key to navigate to the project screen to create a new compliance project.

Note: User must open a handler to create a project with reason Compliance, Enforcement or Criminal (refer to Figure 7.1). Complaint is the only project reason that a user can select without a handler being active. But if a project is created without specifying the handler then user will not be able to add activities to that project. Selecting Compliance option as the project reason will navigate the cursor to the project screen as shown in Figure 7.2.

Figure 7.1: Menu Option to Create a New Project

[pic]

Figure 7.2: Project Screen

The project screen will be displayed in data entry mode. Most of the required data values are populated by the system. Supply the additional required values (name, coordinator, county) and press [CTRL] [F6] (COMMIT) key or [pic] to generate a project number and save the record.

Description for each field on project screen is as follows.

Project ID: Unique ID issued to this project.

This number is assigned by system and update is not allowed.

Open Date: Date on which this project was opened.

Priority: Code indicating the project priority status.

Allowed values are ‘Y’ for yes and ‘N’ for no.

Status: Code indicating the project status.

Code ‘OPEN’ is used when a project is being created or updated. ‘CLOSED’ is used when adding or updating of activities in the project is no longer required.

System will not allow adding activities to closed projects.

Reason: Project reason.

Defaults to the selection that user made to access the project screen.

DEP Office: District office to which the user belongs.

County: County in which the district office is located.

Description: Comments describing the project.

Coordinator: User responsible for tracking the project.

Accessibility: Code indicating the reason why the handler is not accessible for normal RCRA tracking.

Updating of accessibility code is done in page 1 of handler form.

Prog Area: Program area.

This value is automatically populated by the system.

EPA Id: EPA ID of the facility.

This value is automatically populated by the system.

Site: Site number of the facility.

This value is automatically populated by the system.

Site Name: Site name as it appears in the page 1 of handler form.

This value is automatically populated by the system.

7.2 PROJECT - NEW - ENFORCEMENT

Follow the instructions described in Chapter 7.1.

7.3 PROJECT - NEW - CRIMINAL

Follow the instructions described in Chapter 7.1.

7.4 PROJECT - NEW - COMPLAINT

A compliant project can be created with or without opening a handler. Sometimes complaint projects are created without knowing or having the EPA ID for the facility against whom the complaint is filed. If a compliant project is created without opening a handler, then it will not be linked to a handler automatically and system will not allow activities to be added to that project. To add activities to a project that is not linked to EPA ID, user must first establish an EPA ID for the facility and e-mail or call the COMHAZ database administrator and request to link the complaint project to the handler.

To create a new complaint project, select the NEW sub-menu from PROJECT menu as shown in Figure 7.1. There are 4 menu options available under New sub-menu. Select the COMPLAINT option and press the [ENTER] key to navigate to the complaint project screen (Figure 7.3) to create a new complaint project.

Figure 7.3: Complaint Form (Page 1 of 3)

To log or create a complaint project, fill the values in the complaint screen and press the [CTRL] [F6] (COMMIT) key or [pic]. Upon entering the data and pressing [CTRL] [F6] (COMMIT) or [pic], a new project will be created having ‘COMPLAINT’ as the reason. In addition, 2 activities (CPR, CPIS) will be created in the system. Once again please note that user will not be able to update these activities until this project is associated with a handler.

Description for fields on complaint form is as follows.

Complaint #: A unique number assigned for the complaint record.

This number is assigned by the system and is not updateable. This number is same as the project number.

Program Area: Program area of the user who is recording this complaint or program area which will investigate this complaint. This value must be ‘HW’ if the user would like to track hazardous waste activities in this project.

Office: District office which received the complaint.

County: County where the district office is located.

Open Date: The date that the complaint was received.

Status: The status of the complaint, whether 'Open' or 'Closed'.

Priority: Indicates whether the complaint is a DEP-defined, priority project.

Reviewer: Staff person assigned to the complaint.

Company: Name of the company reporting the complaint.

Job Title: Position of the person reporting.

Name: Last, first and middle name of the person reporting.

Address: Address of the person reporting.

Type: Type of company reporting.

Phone: Phone number of the person reporting.

City/State/Zip: City, state and zip code of the person reporting.

Country: Country of the company or person reporting.

Company: Name of the company being reported.

Job Title: Position of the person being reported.

Name: Last, first and middle name of the person being reported.

Address: Address of the person being reported.

Type: Type of company being reported.

Phone: Phone number of the person being reported.

City/State/Zip: City, state and zip code of the person being reported.

Country: Country of the company or person being reported.

[pic]

Figure 7.4: Complaint Form (Page 2 of 3)

Description: Description of the complaint.

Directions: Directions to the location of the reported complaint.

Received by: Person receiving the complaint.

Mode: Code indicating the mode of the complaint.

Recontact Requested:

Code indicating whether the person reporting the complaint wishes to be recontacted.

Time Existed: Number of days has this condition has existed.

Initial Disposition:

Comments regarding the complaint prior to referral.

Investigation Begin Date:

Date the investigation began.

Investigation End Date:

Date the investigation ended.

Investigation Procedure:

Comments explaining the procedure used in complaint investigation.

Facts Discovered:

Details related to the facts revealed during the investigation.

Resolution: Narrative outlining the resolution of the complaint.

[pic]

Figure 7.5: Complaint Form (Page 3 of 3)

Follow Up: Details related to the complaint's follow-up investigation.

Final Deposition:

Final comments related to the complaint.

Date: When the final disposition was completed.

Corrective actions:

Comments about corrective actions taken regarding the complaint.

Field Hours Spent:

Time spent in the field responding to the complaint.

Office Hours Spent:

Time spent in the office responding to the complaint.

Referral Agency:

Code of the agency(ies) to which the complaint was referred.

Agency Name:Name of the agency(ies) to which the complaint was referred.

7.5 PROJECT - OPEN

To open and/or update an existing project select the OPEN sub-menu from the PROJECT menu as shown in Figure 7.6.

[pic]

Figure 7.6: Menu Option to Open an Existing Project.

Upon selecting the Open sub-menu, cursor will be navigated to project query screen as shown in Figure 7.7.

[pic]

Figure 7.7: Project Query Screen.

Specify the query criteria to retrieve the project(s) and press the [F12] (EXECUTE QUERY) key or [pic].

Please note that if the above screen is accessed while a handler record is active then system automatically populates the EPA ID, Site ID and the Name fields. Upon specifying the query criteria and pressing the [F12] (EXECUTE QUERY) key or [pic], system will retrieve the projects and display them in project browse screen as shown in figure 7.8. If no query criteria is specified then system will retrieve all the projects that are associated with HW (Hazardous Waste) program area and display them in project browse screen.

Description for fields in project query screen is as follows.

EPA ID: Unique EPA ID assigned for the facility.

Site ID Unique site ID assigned for the facility.

Name: Facility name as it appears in the page 1 of handler form.

This name is automatically populated when user enters EPA ID or site ID.

Related Party: Full or partial name of the related party.

Staff Assigned: User assigned to perform the activities.

Specified staff assigned will retrieve all the projects that have activities assigned to the specified user.

Project Id: Project number.

Priority: Priority indicator that retrieved project(s) must contain.

Status: Status indicator that retrieved project(s) must contain.

Name: Name that retrieved projects must contain.

Reason: Reason that retrieved project(s) must contain.

Office: Office where the retrieved project(s) are located.

County: County for the project(s).

Project Coordinator:

User who is responsible for tracking the project(s).

[pic]

Figure 7.8: Project Browse Screen with Query Results.

Project browse screen (Figure 7.7) displays the project query results. For every project record, browse screen only displays the project number, project name, project open date, project status, project reason, and OGC case number. Select the desired project from the browse list and press the [PAGE DOWN] key for more details (Figure 7.9).

[pic]

Figure 7.9: Project Form with Project Details.

Accessing the above project form with a project is also referred as opening a project. To update the project, update the data and press the [CTRL] [F6] (COMMIT) key or [pic] to save the changes. For brief descriptions of the fields in the project form refer to Chapter 7.1.

7.6 PROJECT - RELATED PARTY

Related party form tracks the contact information pertaining to parties involved in the case development (Ex: Attorneys, Consultants, Contractors, etc.). To add, update, and/or view the related party information, open the project and select the RELATED PARTY sub-menu from the PROJECT menu as shown in Figure 7.10. Upon selecting the RELATED PARTY menu, cursor will navigate to a browse screen (Figure 7.11) displaying the existing related parties for the selected project.

[pic]

Figure 7.10: Menu Option to Access the Related Party Information.

[pic]

Figure 7.11: Related Party Browse Screen.

Related party browse screen displays the name and role of the already existing parties. To view and/or update the existing party information select the desired party record and press the [PAGE DOWN] key. To create a new related party record, press the [Ctrl][I] key or [pic] (Create Record). In either case cursor will navigate to the related party screen as shown in Figure 7.12.

[pic]

Figure 7.12: Related Party Form.

To add a new related party enter the values and press the [CTRL] [F6] (COMMIT) key or [pic]. Similarly to update a related party record update the existing data and press the [CTRL] [F6] (COMMIT) key or [pic].

Description for data fields in related party form is as follows.

Company: Company name of the related party.

Contact: Name (Last, First, Middle, Suffix) of the contact person.

Title: Title for the contact person.

Phone: Phone number for the contact person.

Noncompliance History:

Code indicating the past compliance history of the related party.

Allowed values are ‘Y’ or ‘N’.

Relationship Ind:

Code indicating whether the related party is a company or individual.

Enter ‘C’ to indicate that party is a company or ‘I’ to indicate individual.

Discontinued Date:

Date on which the related party is discontinued.

E-Mail Address:

E-mail address for the contact person.

Address: Address for the related party.

Multiple addresses can be entered in this block. To add more than one address save the data and navigate to address block and press the [Ctrl][I] key or [pic] (Create Record) to create a new address record.

City: City or town where the address is located.

State: State where the address is located.

Zip: Zip code of the address.

Type: Code indicating the related party address type.

Mailing Address:

Code indicating whether the current record is the mailing address.

7.7 PROJECT - LCT

LCT (Legal Case Tracking system) is an Oracle application similar to COMHAZ. Legal case history for cases that lead to formal enforcement action is tracked in the LCT system. Every case in LCT will be assigned a unique ID number called OGC (Office of General Council) case number. This case number must be linked to a project number which is tracking the case activities in COMHAZ. To link a project to the OGC case in the LCT system, a user must have proper privilege. To view and/or link a project to the OGC case, open the project and select the LCT link sub-menu from the PROJECT menu as shown in figure 7.13. Upon selecting the LCT menu, the cursor will navigate to a browse screen (Figure 7.14) displaying the existing LCT case(s) linked to the current project.

[pic]

Figure 7.13: Menu Option to Link a Project to LCT System Using OGC Number.

[pic][pic]

Figure 7.14: Form Displaying the Currently Linked OGC Cases to the Project.

To link the project to a new OGC case follow the steps explained below.

1) Press the [ENTER] key while the cursor is in the browse screen. Upon pressing [ENTER] key,

cursor will navigate to the LCT case record part 1 screen.

2) Retrieve the OGC case record by querying for OGC case number.

3) When the desired OGC case record is active, press [NUM LOCK] [F12] on the PC keyboard

or [NUMLOCK] [DO] on the DEC keyboard. This action will display a pop-up

link screen.

4) In the link screen enter the project number and press [ENTER] key to populate the project

details.

5) If the correct project name appears then press the [F12] or [DO] key to link the project to the

OGC case number.

7.8 PROJECT - COMPLAINT

To create a complaint project follow the instructions outlined in chapter 7.4. To update the details of a complaint project follow the instructions outlined in chapter 7.4 to access page 1 of the complaint form. While the cursor is on page 1 press the [F11] (ENTER QUERY) key or [pic] and specify the query criteria. Press the [F12] (EXECUTE QUERY) or [pic] key to retrieve the complaint records. Locate the desired record, update and press the [CTRL] [F6] (COMMIT) or [pic] key to save the record.

8. ACTIVITY

Activities are events resulting from compliance and/or enforcement actions performed for any facility. A group of activities are tracked inside a project. In COMHAZ every project that is

being used for tracking activities must be associated with HW program area and a EPA ID. In COMHAZ, activities are divided into 3 groups: compliance, enforcement and other.

8.1 ACTIVITY - NEW

To create a new activity, select the NEW sub-menu from the ACTIVITY menu while a project is active (Figure 8.1). Please note that the ACTIVITY menu is not enabled until a project is active. In addition, creating a new activity is not allowed until the active project has a project number which is also referred to as project ID. Upon selecting the NEW sub-menu, cursor will navigate to the activity form (Figure 8.2).

Figure 8.1: Menu Option to Create a New Activity.

[pic]

Figure 8.2: Activity Form

To add a new activity record enter the data and press the [CTRL] [F6] (COMMIT) key or [pic] to save. If the activity is a compliance activity and Date Done field is filled then after saving the activity, system will display a pop-up screen with a message to confirm whether the user want to add violations. At this time user can press the [ENTER] key to add violations to the new activity or type ‘N’ in the message screen and press the [ENTER] key to skip entering the violations. Choosing to add the violations will navigate the cursor to the violation screen. Refer to Chapter 8.4 for details on adding the violations.

If the activity is an enforcement activity and the Date Done field is filled then after saving the activity, system will automatically navigate to the violation link screen prompting the user to link the enforcement activity to the existing violations. Please note that every enforcement activity must be linked to at least one violation. Refer to Chapter 8.6 for details on linking the violations.

Description for fields in the activity screen is as follows.

Activity: Code indicating the activity.

Press the List of Value key [pic] for a list of valid hazardous waste activity codes.

GCI: Flag indicating whether the current inspection is conducted under the Gulf Coast Initiative program. Cursor will navigate to this field only when user enters a

CEI (Compliance Evaluation Inspection) activity code.

Date Done: (Please refer to the activity code guidance manual for details).

Response/Action Due:

Due date.

(Please refer to the activity code guidance manual for details).

Completed: Completed date.

(Please refer to the activity code guidance manual for details).

Inspection: Flag indicating whether the current activity is an inspection.

(Automatically populated by system based on the activity code.)

Eval Results: Results of the evaluation.

Cursor will navigate to this field only when the Inspection field is marked with ‘Y’.

Prep Notes: Instructions to be used in the preparation for an evaluation.

Comp Notes: Detailed information outlining the activity's completion.

Permit #: Permit number related to the condition number.

OGC #: OGC number related to the activity.

Condition #: Condition number related to the activity.

8.2 ACTIVITY - OPEN

To open, view and/or update an activity select the OPEN sub-menu from the ACTIVITY menu as shown in Figure 8.3. A project must be active to select the OPEN sub-menu. Upon selecting the OPEN sub-menu, system will navigate to the activity browse screen (Figure 8.4) displaying the hazardous waste activities for the selected project.

Figure 8.3: Menu Option to Open the Existing Activities.

[pic]

Figure 8.4: Activity Browse Form Displaying the Current Activity History for the Project.

Activity browse form displays only HW (Hazardous Waste) program activity codes. To create a new activity record press the [INSERT] (CREATE RECORD) key. To delete an activity, select the activity and press the [DELETE] key. Please note that system will not allow the deletion of activities if the activity is associated with violations or penalties.

To view or update an activity, select the activity using [UP ARROW] or [DOWN ARROW] keys and press the [PAGE DOWN] key to navigate to the activity detail form, which looks like

Figure 8.2 with activity details. Update the field values and press the [CTRL] [F6] (COMMIT) key to save the changes.

Please note that system doesn’t allow the updating of Activity Code or Date Done fields if the activity is associated with violations or penalties. To update an activity that is associated with violations and/or penalties follow the steps explained below.

1) Delete the penalty data.

2) Delete the violations if it is a compliance activity or unlink the violations if it is an enforcement activity.

3) Update the Activity Code and/or Date Done.

4) Add the violations if it is a compliance activity or link the violations if it is an enforcement activity.

5) Add the penalty data.

8.3 ACTIVITY - STAFF ASSIGNED

Staff assigned form tracks the details pertaining to user(s) who have been assigned for the activities. In COMHAZ when a new activity is created, project coordinator is defaulted as the staff assigned. To view and/or update the staff assigned details, select the activity from the activity browse form and select the STAFF ASSIGNED sub-menu from ACTIVITY menu as shown in Figure 8.5. Upon selecting the STAFF ASSIGNED sub-menu, cursor will navigate to the staff assigned form (Figure 8.6) displaying a list of user(s) and their location details.

Figure 8.5: Menu Option to Access the Staff Assigned Details

[pic]

Figure 8.6: Staff Assigned Form.

To update an existing staff assigned record simply type the new name and press the [CTRL] [F6] (COMMIT) key to save the changes. To delete an existing staff assigned record, select the desired record and press the [DELETE] key. To add a staff assigned record, press the [INSERT] (CREATE RECORD) key to get a blank record, enter the name and press the [CTRL] [F6] (COMMIT) key to save the new record.

Description for each field in the staff assigned form is as follows.

Staff: Name of the user performing or assigned for the activity.

Press the [HOME] (LIST) key for a list of valid users.

Date: Date activity was performed.

Description: Description of what was done during this time.

8.4 ACTIVITY -VIOLATION - ADD/UPDATE

Violation(s) must be added only to the compliance activities. To add and/or update the violations, open the compliance activity that led to the discovery of violations and while the cursor is on the activity record select the ADD/UPDATE option from the VIOLATION sub-menu as shown in Figure 8.7. Upon selecting the ADD/UPDATE option, cursor will navigate to the violation add/update form as shown in Figure 8.8.

Figure 8.7: Menu Option to Access the Violation Add/Update Form.

[pic]

Figure 8.8: Violation(s) Add/Update Form.

To update a violation record, select the violation, enter the new values and press the [CTRL] [F6] (COMMIT) key to save the changes. To delete a violation record, select the violation and press the [DELETE] key to delete the record and then press the [CTRL] [F6] (COMMIT) key to save the changes.

Enter the violation data and press the [CTRL] [F6] (COMMIT) key to add a new violation record when there are no existing violations. To create a new violation record when there are existing violations press the [INSERT] (CREATE RECORD) key. System will create a blank violation record at the bottom of the existing violations and populate it with the data from the previous record to save data-entry time. Update this new violation and press the [CTRL] [F6] (COMMIT) key to save the changes.

Description for fields in violation add/update screen is as follows:

CITATION: Citation from Federal or State regulations or statutes that specifies a violation in sufficient detail to distinguish it from other violations.

TY: Code indicating the area of violation.

Press the [HOME] (LIST) key for a list of valid violation area codes.

C: Code indicating the class of violation. Violation class the code for violations indicating the relative severity of the violation discovered as a result of an evaluation. Allowed values are ‘1’ for class 1, ‘2’ for class 2 and ‘P’ for pending.

Class 1: This code is only valid on violations entered prior to 10/01/1996. Deviations from regulations, or provisions of compliance orders, consent agreements, consent decrees or permit conditions which could result in failure to:

a) Assure that hazardous waste is destined for and delivered to authorized treatment, storage or disposal facilities.

b) Prevent releases of hazardous wastes or constituents both during the active and any applicable post-closure periods of the facility operation where appropriate; or

c) Assure early detection of such releases; or

d) Perform emergency cleanup operation or other corrective action for releases.

Class 2: This code is only valid on violations entered prior to 10/01/1996.

Any violation of a RCRA requirement that does not meet the criteria for class 1 violations.

Class P: Pending or potential violation subject to determination when lab sample results or legal determination becomes available.

P: Priority indicator. This code is only valid on violations entered prior to

10/01/1996. Code indicating the relative priority assigned to a violation or pending violation.‘9’ indicates high priority violator status.

RT: Regulation type.

Code indicating the origin of the citation listed in regulation violated.

DATE DET: Date violation determined.

DATE SCH: Scheduled response date.

Date by which the handler is to submit to the agency its documentation that the violation has been bought into compliance.

DATE COMP:Violation resolved date or return to compliance date.

The date the agency determines that the handler demonstrated physical compliance. The handler will be considered to be out-of-compliance until the actual resolved date has been determined and entered in the system.

COMMENTS: Comments.

8.5 ACTIVITY - VIOLATION - BROWSE

This Browse sub-menu option is available only from a project screen. This option is used for browsing the violations pertaining to the active project. To browse the violations of a project, open the project and select the VIOLATION sub-menu from ACTIVITY menu and choose the BROWSE option (Figure 8.9). Upon selecting the BROWSE option, cursor will navigate to the violation browse screen displaying the violations for the selected project. Please note that this menu option displays the violations pertaining to the selected project where as VIOLATION sub-menu option in HANDLER menu will display all the violations pertaining to the handler.

Figure 8.9: Menu Option to Browse the Violations for a Project.

8.6 ACTIVITY -VIOLATION - LINK/UNLINK

Every enforcement activity must be linked to at least one violation. To link/unlink the enforcement action to violation(s), open the enforcement activity and while the cursor is on the enforcement activity record select the LINK/UNLINK option from the VIOLATION sub-menu as shown in figure 8.10. Upon selecting the LINK/UNLINK option, cursor will navigate to the violation link/unlink form as shown in figure 8.11.

Figure 8.10: Menu Option to Link/Unlink the Enforcement Action to Violations.

[pic]

Figure 8.11: Violation Link/Unlink Form.

Violation link screen displays all the existing violations for the EPA ID. Violation with letter ‘L’ at the beginning of the record indicates that the violation is already linked to the enforcement activity. Linking an enforcement activity to a violation indicates that the enforcement activity is addressing that violation. To link enter ‘L’ before the violation record. To unlink a violation from an enforcement activity erase the letter ‘L’ from the violation. Press the [CTRL] [F6] (COMMIT) key to save the changes.

8.7 ACTIVITY - $ETTLEMENT - ASSESSED

Penalties assessed and collected as a result of enforcement action(s) are tracked in department’s Cash Receiving application which is another Oracle based system. In addition, penalties specific to the hazardous program are also tracked in COMHAZ for reporting to EPA purposes. Please note that these penalties are unofficial and shall not be used for accounting purposes.

Recording penalties in COMHAZ is a 3-step process.

1) Record the assessed penalty amount.

This step is recommended but not required.

2) Record the settled penalty amount.

This step is required for tracking collected amounts.

3) Record the collected penalty amount.

To record the assessed and/or settled penalty select the enforcement activity that determined the penalty and while cursor is on the enforcement activity select $ETTLEMENT sub-menu from ACTIVITY menu and choose ASSESSED option as shown in figure 8.12. Upon selecting the ASSESSED option, cursor will navigate to the penalty assessed/settled form as shown in figure 8.13.

Figure 8.12: Menu Option to Access the Penalty Form to Record the Assessed/Settled Penalty.

[pic]

Figure 8.13: Penalties Assessed/Settled Form.

To record the assessed and/or settled penalty data enter the penalty type and the amount

and press the [CTRL] [F6] (COMMIT) key to save the record.

Description for each field in the penalty assessed/settled form is as follows.

Activity: Enforcement activity that determined the penalty.

This value is automatically populated.

Date Done: Date on which the enforcement activity is issued.

This value is automatically populated.

Pen Type: Penalty type.

There are 4 penalty type codes and the description for each code is as follows:

PA: Proposed Monetary Penalty (Assessed amount).

The amount of the total penalty in dollars proposed in an initial enforcement action.

FA: Final Monetary Penalty (Settled amount).

The amount of the total penalty in dollars a handler named in the enforcement action must pay directly to the responsible agency. A formal enforcement action is 0necessary to record this penalty amount.

FC: Final SEP Cost.

The final amount cited in an enforcement action as the cost in dollars to the handler of a supplemental environmental project. A formal enforcement action is necessary to record this penalty amount.

CR: Final SEP Credit.

The credit in dollars allowed by the agency for the completed SEP and applied towards the total final settlement amount. A formal enforcement action is necessary to record this penalty amount.

Amount: Amount in dollars.

8.8 ACTIVITY - $ETTLEMENT - COLLECTED

Collected penalty amount(s) are tracked in penalties collected form (Figure 8.14). Please note that these penalties are unofficial and shall not be used for accounting purposes. To record the collected penalty amount select the enforcement activity that determined the settled amount (Please refer to the previous chapter for details on recording assessed/settled amount) and while the cursor is on the enforcement activity select $ETTLEMENT sub-menu from ACTIVITY menu and choose the COLLECTED option as shown in Figure 8.14. Upon selecting the COLLECTED option, cursor will navigate to the penalty collected form as shown in Figure 8.15.

Figure 8.14: Menu Option to Access the Penalty Form to Record the Collected Penalty.

[pic]

Figure 8.15: Penalties Collected Form.

Description for each field in the penalty collected form is as follows:

S.NO: Unique sequence number assigned for each payment.

This value is automatically populated.

Sch Amount: Scheduled amount.

Sch Date: Date on which the scheduled amount is expected.

Coll Amount: Actual collected amount.

Coll Date: Date on which the collected amount is received.

8.9 ACTIVITY -SEPS

SEP form tracks the data pertaining to Supplemental Environmental Project(s). To record the SEP data select the enforcement activity that determined the final SEP credit amount (CR) and while the cursor is on the enforcement activity select SEPS sub-menu from the ACTIVITY menu as shown in figure 8.16. Upon selecting the SEPS sub-menu, cursor will navigate to the SEP form as shown in figure 8.17.

Please note that the enforcement activity that is being selected for recording the SEP data must be the same activity that determined the final SEP credit as explained in the

ACTIVITY - PENALTY - ASSESSED chapter.

Figure 8.16: Menu Option to Access the SEP Form.

[pic]

Figure 8.17: SEP Form.

Description for each field in the SEP form is as follows:

CODE: Code indicating the type of supplemental environmental project.

Press the (LIST) button or right-click for a list of valid SEP codes.

SCH DATE: Date set by an enforcement action for the full or partial expenditure of funds for a SEP project.

ACT DATE: The actual date of a SEP or an enforcement milestone expenditure.

AMOUNT: The actual amount of the SEP.

USER: Initials of the user who is responsible for tracking the SEP.

COMMENTS: Comments.

9. REPORTS

This chapter explains how to the run reports from COMHAZ and also includes a sample copy of all the available reports and the corresponding selection criteria.

9.1 RUNNING REPORTS

To run a report from COMHAZ log into COMHAZ (Refer to Chapter 2) and select the REPORT menu from COMHAZ main menu as shown in Figure 9.1.

[pic]

Figure 9.1: Menu Option to Run the Reports from COMHAZ.

In the REPORT menu there are two sub-menus linking you to two DEPNET sites: 1) the COMHAZ reports page at and 2) the HWRS Data Home at . The COMHAZ reports web site at tlhora6 will require your Floridadep logon.

[pic]

[pic]

Figure 9.2: COMHAZ Reports pages.

Use the gray menu bar to pull down menu options from each report category (requires MS Internet Explorer).

Following sections will include a copy of each report and the selection criteria for that report.

9.2 COMPLIANCE - MOST RECENT ACT

Run this report to retrieve the list of activities that were conducted since a specified date.

A sample report will be included once the report is working.

[pic]

Figure 9.3: Parameter Form for Compliance - Most Recent Act Report.

9.3 COMPLIANCE - TICKLER - BY STAFF

Run this report to retrieve a list of activities assigned to a user that are pending action and/or response. A sample report is included.

[pic]

Figure 9.4: Parameter Form for Compliance - Tickler - By Staff Report.

[pic]

9.4 COMPLIANCE - PROJECT SUMMARY

Run this report to retrieve the summary of a project. A sample report is included following this page.

[pic]

Figure 9.5: Parameter Form for Compliance - Project Summary Report.

Florida Department of Environmental Protection

Hazardous Waste Compliance and Enforcement Tracking System

Project Summary Report

   January 7 , 2002

Selection Used: Project Number= 100878;   

|Project Id: 100878   |

|Name: JONES, CHARLES (COMPL.#96-236) (OT)   |

|Reason: COMPLAINT   |

|Status: OPEN  Open Date: 14-NOV-1996  Priority: N   |

|Coordinator: BIEMILLER_S   |

|Description: buried solid waste in wetland in backyard; clearing wetland trees to create a road.   |

|Office: NORTHEAST DISTRICT-NED   |

|County: DUVAL-16   |

|Role |Related |Effective |

| |Party # |Date |

|!= |not equal to |!= 'CLOSED' |

|> |greater than |> '01-JAN-93' |

|>= |greater than or equal to |>='30-DEC-92' |

|< |less than | ................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download