improving hazardous waste management compliance using relational databases angela cox and larry...

IMPROVING HAZARDOUS WASTE MANAGEMENT COMPLIANCE

USINGRELATIONAL DATABASES

Angela Cox and Larry Reynolds

Presentation Contents Brief Explanation of What a Database Is and Is Not

Ways a Relational Database Can be Used

User Interface Choices

How to Plan a Simple Waste Management Database

Typical Effort and Cost Requirements

Technology Growth

A Database Is Not

A place to store things

A collection of information

A substitute for sound management

A guarantee of success

What A Database Is

An organization of information you will need to retrieve for use later

Means to recover information when you need it arranged, organized and summarized in a useful fashion

A way to structure your work

Database vs. Sequential (and other) Databases

Typical Database –

Rainfall data for each day

Number of units produced each shift

Number of employees absent each day

These are examples of typical sequential databases.

Database vs. Sequential (and other) Databases

In manufacturing, they are related in various fashions – The number of employees absent from key production areas is related to the number of units produced in a day. The number of absences may also be related to such things as rainfall, etc.

Database vs. Sequential (and other) Databases

Other Examples of Relational Databases –

Address Book vs. Contact Information Manager

Contact Manager

Contact Manager

Database vs. Sequential (and other) Databases

Other Examples of Relational Databases –

Address Book vs. Contact Information Manager

Inventory and Distribution Control Systems

Database vs. Sequential (and other) Databases

Most environmental compliance data has many relationships –

Regulatory program

Permit requirements

Data/reporting period

Manufacturing production rate or activity

Physical location

Database vs. Sequential (and other) Databases

Most Environmental Compliance data, particularly waste management data have many inter-relationships with other activities

A Relational Database allows the connection of these activities and programs

Ways a Relational Database Can Be Used in Waste Management

To Organize Your Facility Specific Regulatory Requirements

To Record and Track Compliance Activities

As a Management Tool To monitor and summarize regulatory activities

To report compliance data in the form or frame work you need

Quality Assurance (e.g. much like ISO procedures)

Ways a Relational Database Can Be Used in Waste Management

As a Compliance Tool

Using same/similar reports for regulatory compliance reporting

As a Business Tool

Schedule work based on past history, current inventory, etc.

Sort, Categorize, Track key information

Support Basic Decision Making

How to Plan A Waste Management Database

Questions to Answer – What do you wish to do with it?

What information, reports, etc. do you wish to derive from it?

What information is needed to do these things?

How is that information to be captured?

How secure must your information be?

What user interface do you want?

User Interface

Single vs. Multi-User

Stand Alone Work Station, LAN accessible or Web accessible

Simple Waste Management Database

Want to –

Track hazardous waste generation

Determine Generator Status each month

Single User on Stand Alone Work Station connected to Local Area Network

Data will ultimately be in the public record

Simple Waste Management Database

Information Requirements

Basic Facility Information – address, contact name and phone number, etc.

Generator ID number

Waste Stream Information – from waste stream survey, characterization, profile application, …

Transporter Information

TSDF Information

Simple Waste Management Database

Waste Generation Records – Date of generation, quantity, plant operating records

Waste Shipment Records – Manifests

Reporting Requirements – State reporting requirements

Required Effort

60% + of effort will be in initial setup and ongoing data capture

In-House vs. Outside consultant for application development is a critical decision

User Interface significant cost factor

Cost

Initial Set up -- $50k to ?

Application Development Single User/Stand Alone Work Station -- $10k to $15k

Multi-User via Local Area Network -- $25k

Multi-Facility/Multi-User via Web Interface -- $75k - $125k

Technological Improvements

Point of Service Ports – available computers and network access

Hand Held PCs – IR/Bluetooth data upload capabilities

Bar Code/UPC Scanners

Radio Frequency Identification

USE OF RELATIONAL DATABASES IN WASTE MANAGEMENT

Questions?