1AIHCE--"Prevention. . ." (May, 2000)

Prevention Applications in Hazards Management

Hazards Database for LEPC Operations

Copyright 2000 by Elizabeth Aton

2AIHCE--"Prevention. . ." (May, 2000)

AIHCE 2000 “Prevention. . .” Abstract

• 08:00• Vacation paradise

location• “Computer Apps”• Widely divergent

knowledge levels

3AIHCE--"Prevention. . ." (May, 2000)

Prevention Applications in Hazards Management

(Elizabeth Aton (Washington University School of Medicine)

George Bleazard (Sigma Chemical)

4AIHCE--"Prevention. . ." (May, 2000)

LEPC

• L ocal

• E mergency

• P lanning

• C ommittee

AIHCE--"Prevention. . ." (May, 2000)

5

6AIHCE--"Prevention. . ." (May, 2000)

LEPC Roles

• Form a committee with varied representation

• Prepare emergency plans

• Receive Section 304 release notifications

• Receive Section 311 notices and Section 312 inventories

• Update emergency plans

• Broker information to the public

7AIHCE--"Prevention. . ." (May, 2000)

Saint Louis City

• Stand-alone County

• Founded in 1764• Transportation

Hub• Chemical Industry• Emerging Biotech

8AIHCE--"Prevention. . ." (May, 2000)

Saint Louis City LEPCMembership

• Emergency Response

• Law Enforcement• Government• Industry and

Academia• Media• Citizens

9AIHCE--"Prevention. . ." (May, 2000)

STL LEPC Review 1998

• Need for information management improvements

• Greater IH presence in LEPC membership

10AIHCE--"Prevention. . ." (May, 2000)

Target: Improve HazMat Info Process

• Paper Data Sets• Little Standardization• Difficult Retrieval• Pre-Planning Guides and Feedback

Limited• Limited Use in Emergency

Response

11AIHCE--"Prevention. . ." (May, 2000)

Hazard Analysis Subcommittee

Recommissioned• Strong IH

presence• Interagency

cooperation manifest

• No secondary agendas

12AIHCE--"Prevention. . ." (May, 2000)

Hazard Analysis Goals and Methodology

• Prepare a system for hazmat ID

• Prepare hazmat profiles

• Prepare a methodology for response for hazmat incidents

• RECOGNITION

• EVALUATION

• CONTROL

13AIHCE--"Prevention. . ." (May, 2000)

Create a Custom Database

14AIHCE--"Prevention. . ." (May, 2000)

The Database Is

• To be a usable tool by multiple levels of professionals

• To enhance and exploit experience information

• To plug information gaps associated with regulatory data alone

15AIHCE--"Prevention. . ." (May, 2000)

The Database Is NOT

• A substitute for extant database software (e.g., Cameo, etc.)

• A sole source of hazard information

• A dose assessment methodology

16AIHCE--"Prevention. . ." (May, 2000)

Database Details

• Access 97 • All data are linked

by site name and address

• Users defining reports

• Flags regulatory data as available

17AIHCE--"Prevention. . ." (May, 2000)

Next Actions

• Funding • Database name• Initial field roll-out• Fields and tables

18AIHCE--"Prevention. . ." (May, 2000)

Conclusions• Creation of a database can bring

together disparate information critical to hazard management

• The IH process (Recognition=>Evaluation=>Control) is a usable framework in a community hazard prevention role

19AIHCE--"Prevention. . ." (May, 2000)

Questions?