Record Display for the EPA National Library Catalog

RECORD NUMBER: 33 OF 41

Main Title RPM (Remedial Project Manager) Primer: An Introductory Guide to the Role and Responsibilities of the Superfund Remedial Project Manager.
Author Roe, C. H. ;
CORP Author Booz-Allen and Hamilton, Inc., Bethesda, MD.;Environmental Protection Agency, Washington, DC. Office of Emergency and Remedial Response.
Year Published 1987
Report Number REPT-9355.1-02; EPA-68-01-7376; EPA/540/G-87/005;
Stock Number PB88-176128
Additional Subjects Hazardous wastes ; Guidelines ; Superfund remedial fund ; CERCLA ; SARA ; Remedial ; Remedial project managers
Internet Access
Description Access URL
https://nepis.epa.gov/Exe/ZyPDF.cgi?Dockey=10001V9W.PDF
Holdings
Library Call Number Additional Info Location Last
Modified
Checkout
Status
NTIS  PB88-176128 Some EPA libraries have a fiche copy filed under the call number shown. 07/26/2022
Collation 46p
Abstract
The purpose of the document is to familiarize new Remedial Project Managers (RPMs) with their roles and responsibilities in the Superfund remedial program. It also can serve as an orientation to the Superfund remedial program for EPA program staff, and the public. It is not intended to be a training document. EPA has developed other materials and conducts courses specifically for training purposes. The Acme Waste Disposal Co. site, the people, and the events described in the document are hypothetical and were created to depict the cleanup of an abandoned hazardous waste site. The example illustrates typical Superfund remedial response activities and was written to demonstrate specifically the important role of the RP in managing site cleanup and in coordinating the various participants. Key terminology and concepts appear in bold face. For simplicity, the example depicted in the Primer is a Fund-financed, Federal-lead project from start to finish. In reality, a project may switch from Fund- to Enforcement-lead, and from Federal- to State-lead during the remedial process, thereby altering roles of the participants. In addition, the example portrays the RPMs involvement with only one site, when an RPM actually may be involved with several concurrent projects.