# tlkpRS_FieldDesc

Table: tblAudit
Field: EPAFacilityID
ShortDesc: Unique identifier for all RMPs submitted by a specific facility
DataType: Text
Description:
Unique identifier for all RMPs submitted by a specific facility (assigned by Reporting Center for first-time submission). * After this number is assigned to the first submission for a facility, subsequent submissions for the same facility must include this identifier.


Table: tblRMPTrack
Field: FacilityZip4
ShortDesc: Facility Zip4
DataType: Text
Description:
The code which represents the Zoning Improve Plan (ZIP) Geographic Segment of the facility mailing address.


Table: tblS1Facilities
Field: AttachmentsIndicator
ShortDesc: Attachments Indicator
DataType: Yes/No
Description:
An indication of whether one or more attachments other than graphics were submitted with the RMP. ‘Y’es or ‘N’o


Table: tblS1Facilities
Field: CAA_TitleV
ShortDesc: 1.12.c CAA Title V
DataType: Yes/No
Description:
Indicate if your facility has a CAA Title V Operating Permit with “Y.”  CAA Title V Air Operating Permit ID Title V (Part 70) of the Clean Air Act (40CFR70) requires major sources of air pollution to obtain permits.


Table: tblS1Facilities
Field: CBIFlag
ShortDesc: CBI Flag: RMP
DataType: Yes/No
Description:
An indication that Confidential Business Information (CBI) was claimed for certain data elements in the record.  ‘Y’es or ‘N’o


Table: tblS1Facilities
Field: CertificationReceivedFlag
ShortDesc: Certification Received Flag
DataType: Yes/No
Description:
A flag to indicate whether the certification letter accompanied the RMP submission.  The default for this field is “N.” ‘Y’es or ‘N’o


Table: tblS1Facilities
Field: Company2DUNS
ShortDesc: 1.4.c Parent Company #2 DUNS
DataType: Text
Description:
If your facility is owned by a joint venture, this is the DUNS Number assigned by Dun & Bradstreet to the second parent company.


Table: tblS1Facilities
Field: DeRegistrationDate
ShortDesc: De-registration Date
DataType: Date/Time
Description:
Date that the request to de-register the facility was entered into the system at the reporting center.


Table: tblS1Facilities
Field: ElectronicWaiverReceivedFlag
ShortDesc: Electronic Waiver Received Flag
DataType: Yes/No
Description:
An indication of whether an electronic waiver accompanied the submission, if the submission came in paper.  The default for this field is “N”. ‘Y’es or ‘N’o


Table: tblS1Facilities
Field: EPCRA_302
ShortDesc: 1.12.b Covered by: EPCRA 302
DataType: Yes/No
Description:
EPCRA Section 302 pertains to the Extremely Hazardous Substances list.  Any facility with a toxic regulated substance above the threshold quantity in a process is subject to EPCRA 302.  If the facility is covered for only flammable regulated substances, the facility is not subject to 40 CFR 355
for those substances, although the facility may be for toxic substances not affected by this Rule.


Table: tblS1Facilities
Field: ErrorReportDate
ShortDesc: Error Report Date
DataType: Date/Time
Description:
System generated data element that indicates the date that the error report was created by the system.


Table: tblS1Facilities
Field: Facility4DigitZipExt
ShortDesc: 1.5.e Facility ZIP Extention
DataType: Text
Description:
The four-digit extension code that represents the geographic segment that is a sub-unit of the ZIP Code and further refines the exact location of the facility.


Table: tblS1Facilities
Field: FacilityCountyFIPS
ShortDesc: 1.5.f Facility County
DataType: Text
Description:
Federal Information Processing Standard (FIPS) code for the county in which the facility is located.


Table: tblS1Facilities
Field: FacilityStr1
ShortDesc: 1.5.a Facility Street - Line 1
DataType: Text
Description:
Facility Street - Line 1 using local street and road designations.  No post office box numbers or rural route numbers.  This is not the mailing address.


Table: tblS1Facilities
Field: FacilityZipCode
ShortDesc: 1.5.e Facility ZIP Code
DataType: Text
Description:
The Zoning Improvement Plan (ZIP) Code assigned to the facility by the U.S. Postal Service which represents a geographic area that facilitates mail
delivery.


Table: tblS1Facilities
Field: ForeignCountry
ShortDesc: 1.6.g Foreign Country
DataType: Text
Description:
If the Owner or Operator (reported in 1.6.a) has an address outside the USA as his or her primary mailing address, enter the foreign country’s code representing the name of the foreign country.  If the primary address is in the USA, leave this field blank.


Table: tblS1Facilities
Field: ForeignStateProv
ShortDesc: 1.6.f Foreign State or Province
DataType: Text
Description:
If the Owner or Operator (reported in 1.6.a) has an address outside the USA as his or her primary mailing address, enter the name of the foreign state
or province.  If the primary address is in the USA, or if there is no state or province in the foreign mailing address, leave this field blank.


Table: tblS1Facilities
Field: ForeignZipCode
ShortDesc: 1.6.h Foreign ZIP Code
DataType: Text
Description:
If the Owner or Operator (reported in 1.6.a) has an address outside the USA as his or her primary mailing address, enter the International Postal Code
that represents the address’s postal zone.  If the primary address is in the USA, or if there is no state or province in the foreign mailing address, leave this field blank.


Table: tblS1Facilities
Field: LatLongDescription
ShortDesc: 1.5.j Lat/Long Description
DataType: Text
Description:
Code for the physical place corresponding to the coordinate.  Codes can be obtained from MAD Version 6.1 Standard as implemented in Envirofacts Locational Reference Tables (EF LRT).  http://www.epa.gov/enviro/html/lrt/lrt_over.html


Table: tblS1Facilities
Field: LatLongMethod
ShortDesc: 1.5.i Lat/Long Method
DataType: Text
Description:
Code representing method used to obtain latitude or longitude data.  Codes can be obtained from Method Accuracy Description (MAD) Version 6.1
Information Coding Standards as implemented in Envirofacts Locational Reference Tables (EF LRT).  http://www.epa.gov/enviro/html/lrt/lrt_over.html


Table: tblS1Facilities
Field: LEPC
ShortDesc: 1.10 LEPC
DataType: Text
Description:
Local Emergency Planning Committee (LEPC) associated with the facility county.  For LEPC information refer to the LEPC/SERC Net Web site
at http://www.RTK.NET:80/lepc.  Must cover all or part of the Facility County.


Table: tblS1Facilities
Field: OperatorZipCodeExt
ShortDesc: 1.6.g Owner/Operator ZIP four-digit extention code
DataType: Text
Description:
The four-digit extension code that represents the geographic segment that is a subunit of the ZIP Code and further refines the business mailing address of the Owner or Operator.


Table: tblS1Facilities
Field: OSHA_PSM
ShortDesc: 1.12.a Covered by: OSHA PSM
DataType: Yes/No
Description:
Occupational Safety and Health Act (OSHA) Process Safety Management (PSM) Standard. Question covers all processes at the facility; if any process at the facility is subject to OSHA PSM, must answer “Y” even if the PSM process is not covered by this Rule.


Table: tblS1Facilities
Field: OSHARanking
ShortDesc: 1.13 OSH Star or Merit Ranking
DataType: Yes/No
Description:
A stationary source with a Star or Merit ranking under OSHA's voluntary protection program shall be exempt from audits under paragraph (b)(2) and
(b)(7) of [Section 68.220 - audits].


Table: tblS1Facilities
Field: OtherEPAFacilityID
ShortDesc: 1.3 Other EPA Systems Program Facility Identifier
DataType: Text
Description:
The unique identification number assigned to a facility by the Facility Index System (FINDS) (or if not known, the Resource Conservation and Recovery Act (RCRA), Emergency Planning and Community Right-to-Know Act (EPCRA), TRI, or other EPA facility identifier).


Table: tblS1Facilities
Field: RMPCompleteFlag
ShortDesc: RMP Complete Flag
DataType: Yes/No
Description:
Flag to indicate whether the RMP passed RMP*Process validation and is considered complete, or failed and is considered incomplete.


Table: tblS1Facilities
Field: RMPDescription
ShortDesc: RMP Description
DataType: Text
Description:
RMP Description is an optional description for the whole RMP.  RMP Description is not accessible to  RMP*Info on the Web.


Table: tblS1Facilities
Field: SafetyInspectionBy
ShortDesc: 1.15 Last Safety Inspection Performed by:
DataType: Text
Description:
A designation representing the external agency that performed the last safety inspection. One or more of the following is expected: 
   OSHA
   State OSHA
   EPA
   State EPA
   Fire Department
   Never had a safety inspection
   Other


Table: tblS1Facilities
Field: SubmissionMethod
ShortDesc: Submission Method
DataType: Text
Description:
The method in which the RMP was submitted, either by RMP*Submit, paper, a commercial software vendor, or other submission method.


Table: tblS1Facilities
Field: VersionNumber
ShortDesc: Version Number
DataType: Text
Description:
Indicates which version of RMP software was used to submit the plan.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS1FlammableMixtureChemicals
Field: FlamMixChemID
ShortDesc: Flam Mix Chem ID
DataType: Long Integer
Description:
Unique identifier for the Section 1 Flammable Mixture Chemicals record destination table. Generated by RMP*Submit and 3rd-party programs.


Table: tblS1FlammableMixtureChemicals
Field: ProcessChemicalID
ShortDesc: Process Chemical ID
DataType: Long Integer
Description:
Unique number used to identify each chemical within a single RMP. Generated by RMP*Submit and 3rd-party programs.


Table: tblS1Process_NAICS
Field: Process_NAICS_ID
ShortDesc: Process NAICS ID
DataType: Long Integer
Description:
Unique number used to identify each NAICS code within a covered process in an RMP.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS1Process_NAICS
Field: ProcessID
ShortDesc: Process ID
DataType: Long Integer
Description:
Unique number used to identify each covered process in an RMP reported in Section 1. Generated by RMP*Submit and 3rd-party programs.


Table: tblS1ProcessChemicals
Field: ProcessChemicalID
ShortDesc: Process Chemical ID
DataType: Long Integer
Description:
Unique number used to identify each chemical within a single RMP.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS1ProcessChemicals
Field: ProcessID
ShortDesc: Process ID
DataType: Long Integer
Description:
Unique number used to identify each covered process within an RMP from Section 1 Program Level for the Covered Process.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS1Processes
Field: ProcessID
ShortDesc: Process ID
DataType: Long Integer
Description:
Unique number used to identify each process within the RMP.  The same number will not necessarily be assigned to the same process for an RMP in a resubmission.


Table: tblS1Processes
Field: ProgramLevel
ShortDesc: 1.17.a Program Level
DataType: Integer
Description:
Program category, (e.g., Program Level 1, 2, or 3), to identify with which program level the process complies.


Table: tblS2ToxicsWorstCase
Field: AnalyticalBasis
ShortDesc: 2.3 Model Used
DataType: Text
Description:
The analytical basis for choosing the Toxics Worst Case Scenario.   One of the following is expected:
EPA’s OCA Guidance Reference Tables or Equations; 
EPA’s RMP Guidance for Ammonia Refrigeration
Reference Tables or Equations;
EPA’s RMP Guidance for Wastewater Treatment Plants Reference Tables or Equations;
EPA’s RMP Guidance for Warehouses Reference Tables or Equations;
EPA’s RMP Guidance for Chemical Distributors Reference Tables or Equations;
EPA’s RMP*Comp (TM);
Areal Locations of Hazardous Atmosphere
[Aloha (R)];
Other Model Name.


Table: tblS2ToxicsWorstCase
Field: CBI_Flag
ShortDesc: CBI Flag
DataType: Yes/No
Description:
An indication that Confidential Business Information (CBI) was claimed for certain data elements in the record.


Table: tblS2ToxicsWorstCase
Field: Distance2Endpoint
ShortDesc: 2.11 Distance to endpoint (miles)
DataType: Single
Description:
The distance to the endpoint in miles for the chemical, using the endpoint specified for the chemical in Appendix A of the risk management program Rule.


Table: tblS2ToxicsWorstCase
Field: ER_FedWilderness
DataType: Yes/No
Description:
An indication that federal wilderness areas are within a circle whose center is the point of the release and radius is determined by the distance to the endpoint.


Table: tblS2ToxicsWorstCase
Field: ER_NatlStateParks
DataType: Yes/No
Description:
An indication that national or state parks, forests, or monuments are within a circle whose center is the point of the release and radius is determined by
the distance to the endpoint.


Table: tblS2ToxicsWorstCase
Field: ER_OtherType
DataType: Text
Description:
The type of environmental receptor if the environmental receptor is other than those listed in 2.14.a. through 2.14.c.


Table: tblS2ToxicsWorstCase
Field: ER_WildlifeSactuary
DataType: Yes/No
Description:
An indication that officially designated wildlife sanctuaries, preserves, or refuges are within a circle whose center is the point of the release and
radius is determined by the distance to the endpoint.


Table: tblS2ToxicsWorstCase
Field: PM_Berms
DataType: Yes/No
Description:
An indication that a mound or wall of earth at the top or bottom of a slope that prevents a spill from spreading is in place.


Table: tblS2ToxicsWorstCase
Field: PM_Enclosures
DataType: Yes/No
Description:
An indication that a physical containment of the release within a structure (e.g., a building) is in place.


Table: tblS2ToxicsWorstCase
Field: PR_Comm_Ind
DataType: Yes/No
Description:
Indication that a major commercial, office, or industrial area is within the distance to the endpoint specified in the worst case scenario. These include
industrial parks, office buildings, shopping malls, commercial areas.


Table: tblS2ToxicsWorstCase
Field: PR_Hospitals
DataType: Yes/No
Description:
Indication that a hospital is within the distance to the endpoint specified in the worst case scenario.


Table: tblS2ToxicsWorstCase
Field: PR_OtherType
DataType: Text
Description:
The type of public receptor if the public receptor is other than those listed in 2.13.a. through 2.13.f.


Table: tblS2ToxicsWorstCase
Field: PR_Prisons
DataType: Yes/No
Description:
Indication that a prison or correction facility is within the distance to the endpoint specified in the worst case scenario.


Table: tblS2ToxicsWorstCase
Field: PR_PublicRecreation
DataType: Yes/No
Description:
Indication that a recreational area or arena is within the distance to the endpoint specified in the worst case scenario.  These include stadiums, parks, and public pools.


Table: tblS2ToxicsWorstCase
Field: PR_Residences
DataType: Yes/No
Description:
Indication that residences are within the distance to the endpoint specified in the worst case scenario.


Table: tblS2ToxicsWorstCase
Field: PR_Schools
DataType: Yes/No
Description:
Indication that a school is within the distance to the endpoint specified in the worst case scenario. Schools include: public and private elementary,
secondary, and higher education schools.


Table: tblS2ToxicsWorstCase
Field: ProcessChemicalID
DataType: Long Integer
Description:
Unique number used to identify each chemical in a process.  From Section 1 Chemicals in Covered Process.


Table: tblS2ToxicsWorstCase
Field: ptrGraphic
DataType: Text
Description:
The DOS file name for the toxics worst case graphic accompanying the scenario.  Should be “.JPG,” or “.GIF” with up to an 8-character prefix.


Table: tblS2ToxicsWorstCase
Field: ReleaseDuration
ShortDesc: 2.7 Release duration (min)
DataType: Single
Description:
Indicate the length of time in minutes for the vessel, pipeline, or other location of the regulated substance to release all of its contents.  For gasses, the duration is 10 minutes.


Table: tblS2ToxicsWorstCase
Field: ResidentialPopulation
ShortDesc: 2.12 Residential population within distance to endpoint
DataType: Long Integer
Description:
Population within the distance to endpoint of the area encompassed by the endpoint.  Need only include residential populations and may be rounded to two significant digits.


Table: tblS2ToxicsWorstCase
Field: ToxicID
DataType: Long Integer
Description:
Unique identifier for Section 2 Toxics Worst Case record destination table.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS2ToxicsWorstCase
Field: WindSpeed
DataType: Single
Description:
The wind speed in meters per second. This is 1.5 meters per second unless local meteorological data applicable to the source is used to show a higher
minimum wind speed at all times during the last 3 years.


Table: tblS3ToxicsAltReleases
Field: AM_Scrubbers
DataType: Yes/No
Description:
A pre-release protection measure that uses water or aqueous mixtures containing scrubbing reagents to remove discharging liquids and possibly also treating the discharging chemical.


Table: tblS3ToxicsAltReleases
Field: AM_SprinklerSystems
DataType: Yes/No
Description:
A system for protecting a building against fire by means of overhead pipes which convey an extinguishing fluid through heat activated outlets.


Table: tblS3ToxicsAltReleases
Field: AM_WaterCurtain
DataType: Yes/No
Description:
A spray of water from a horizontal pipe through nozzles, the curtain may be activated manually or automatically.


Table: tblS3ToxicsAltReleases
Field: AnalyticalBasis
DataType: Text
Description:
The analytical basis for choosing the Toxics Alternative Release Scenario.  Users may add their own data source if it is not on the list.  One of the
following is expected:
EPA’s OCA Guidance Reference Tables or Equations; 
EPA’s RMP Guidance for Ammonia Refrigeration
Reference Tables or Equations;
EPA’s RMP Guidance for Wastewater Treatment
Plants Reference Tables or Equations;
EPA’s RMP Guidance for Warehouses Reference
Tables or Equations;
EPA’s RMP Guidance for Chemical Distributors
Reference Tables or Equations;
EPA’s RMP*Comp (TM);
Areal Locations of Hazardous Atmosphere
[Aloha(R)];
Other Model Name.


Table: tblS3ToxicsAltReleases
Field: Distance2Endpoint
ShortDesc: 3.11 Distance to endpoint (miles)
DataType: Single
Description:
The distance to the endpoint of the toxics alternative release scenario in miles using the endpoint specified for the chemical in Appendix A of the Risk Management Program Rule.


Table: tblS3ToxicsAltReleases
Field: ER_FedWilderness
DataType: Yes/No
Description:
An indication that federal wilderness areas are within a circle whose center is the point of the release and radius is determined by the distance to the endpoint for the alternative release scenario.


Table: tblS3ToxicsAltReleases
Field: ER_NatlStateParks
DataType: Yes/No
Description:
An indication that national or state parks, forests, or monuments are within a circle whose center is the point of the release and radius is determined by
the distance to the endpoint for the alternative release scenario.


Table: tblS3ToxicsAltReleases
Field: ER_OtherType
DataType: Text
Description:
The type of environmental receptor if the environmental receptor is other than those listed in 3.14.a. through 3.14.c.


Table: tblS3ToxicsAltReleases
Field: PM_OtherType
DataType: Text
Description:
The type of Passive Mitigation in place if the passive mitigation is other than those listed in 3.15.a. through 3.15.e.


Table: tblS3ToxicsAltReleases
Field: PR_Comm_Ind
DataType: Yes/No
Description:
An indication that a major commercial, office, or industrial area is within the distance to the endpoint specified in the alternative release scenario. These
include industrial parks, office buildings, shopping malls, commercial areas.


Table: tblS3ToxicsAltReleases
Field: PR_Hospitals
DataType: Yes/No
Description:
An indication that a hospital is within the distance to the endpoint specified in the alternative release scenario.


Table: tblS3ToxicsAltReleases
Field: PR_OtherType
DataType: Text
Description:
The type of public receptor if the public receptor is other than those listed in 3.13.a. through 3.13.f.


Table: tblS3ToxicsAltReleases
Field: PR_Prisons
DataType: Yes/No
Description:
An indication that a prison or correction facility is within the distance to the endpoint specified in the alternative release scenario.


Table: tblS3ToxicsAltReleases
Field: PR_PublicRecreation
DataType: Yes/No
Description:
An indication that a recreational area or arena is within the distance to the endpoint specified in the alternative release scenario. These include stadiums, parks, and public pools.


Table: tblS3ToxicsAltReleases
Field: PR_Residences
DataType: Yes/No
Description:
An indication that residences are within the distance to the endpoint specified in the alternative release scenario.


Table: tblS3ToxicsAltReleases
Field: PR_Schools
DataType: Yes/No
Description:
An indication that a school is within the distance to the endpoint specified in the alternative release scenario. Schools include public and private elementary, secondary, or higher education schools.


Table: tblS3ToxicsAltReleases
Field: ProcessChemicalID
DataType: Long Integer
Description:
Unique number used to identify each chemical in a process from Section 1 Chemicals in Covered Process.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS3ToxicsAltReleases
Field: ReleaseDuration
ShortDesc: 3.7 Release duration (min)
DataType: Single
Description:
The a length of time in minutes for the vessel, pipeline, or other location of the regulated substance to release the quantity.


Table: tblS3ToxicsAltReleases
Field: ResidentialPopulation
ShortDesc: 3.12 Residential population within distance to endpoint
DataType: Long Integer
Description:
The residential population within the distance to endpoint potentially impacted by the toxics alternative release scenario.


Table: tblS3ToxicsAltReleases
Field: Scenario
DataType: Text
Description:
A description of the toxics alternative release scenario as follows: (a) Transfer hose failure is the failure of the connection between two or more
vessels; (b) Pipe leak is the release through a rupture in a pipe; (c) Vessel leak is a release through a rupture in a vessel; (d) Overfilling is release due to filling a pipe, vessel, or other container past its capacity; (e) Ruptured disk/relief valve is a release due to failure of a rupture disk/relief valve to function properly.  A rupture disk/relief valve is a valve that relieves pressure
beyond a specified limit; a relief valve re-closes upon return to normal operating conditions; (f) Excess flow device failure is a release caused by
the failure of excess flow device to function properly and prevent surges from reaching downstream equipment; and (g) any other scenario not in list. One of the following should be specified:
Transfer hose failure;
Pipe leak;
Vessel leak;
Overfilling;
Rupture disk/relief; Valve failure;
Excess flow device failure;
Other (specify).


Table: tblS3ToxicsAltReleases
Field: StabilityClass
DataType: Text
Description:
A code (A through F) representing the average daily stability based on annual data collected at the site or local meteorological station.  List "D," if
OCA guidance is used.  If scenario is modeled, use the average daily stability based on annual data collected at local meteorological station.


Table: tblS3ToxicsAltReleases
Field: Topography
DataType: Text
Description:
A code representing the topography of the area potentially impacted by the alternative release scenario.


Table: tblS3ToxicsAltReleases
Field: ToxicID
DataType: Long Integer
Description:
Unique identifier for the Section 3 Toxics Alternative Release record destination table.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS3ToxicsAltReleases
Field: WindSpeed
DataType: Single
Description:
The wind speed in meters per second.  List 3 m/s if RMP Offsite Consequence Analysis (OCA) guidance is used.  If scenario is modeled, indicate the average daily wind speed based on annual data collected at the local meteorological station.


Table: tblS4FlammablesWorstCase
Field: AnalyticalBasis
DataType: Text
Description:
The analytical basis for choosing the Flammables Worst Case Scenario.  
One of the following should be specified:
EPA’s OCA Guidance Reference Tables or Equations; 
EPA’s RMP Guidance for Propane Storage
Reference Tables or Equations;
EPA’s RMP Guidance for Wastewater Treatment Plants Reference Tables or Equations;
EPA’s RMP Guidance for Warehouses Reference Tables or Equations;
EPA’s RMP Guidance for Chemical Distributors Reference Tables or Equations;
EPA’s RMP*Comp (TM);
Other Model Name.


Table: tblS4FlammablesWorstCase
Field: ER_OtherType
DataType: Text
Description:
The type of environmental receptor if the environmental receptor is other than those listed in 4.9.a. through 4.9.c.


Table: tblS4FlammablesWorstCase
Field: FlammableID
DataType: Long Integer
Description:
Unique identifier for the flammables worst case record destination table.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS4FlammablesWorstCase
Field: PM_BlastWalls
DataType: Yes/No
Description:
An indication that a heavy wall used to isolate buildings or areas that contain highly combustible or explosive materials is in place.


Table: tblS4FlammablesWorstCase
Field: PR_Comm_Ind
DataType: Yes/No
Description:
An indication that a major commercial, office, or industrial area is within the distance to the endpoint specified in the worst case scenario. These include
industrial parks, office buildings, shopping malls, commercial areas.


Table: tblS4FlammablesWorstCase
Field: PR_Hospitals
DataType: Yes/No
Description:
An indication that a hospital is within the distance to the endpoint specified in the worst case scenario.


Table: tblS4FlammablesWorstCase
Field: PR_OtherType
DataType: Text
Description:
The type of public receptor if the public receptor is other than those listed in 4.8.a through 4.8.f.


Table: tblS4FlammablesWorstCase
Field: PR_Prisons
DataType: Yes/No
Description:
An indication that a prison or correction facility is within the distance to the endpoint specified in the worst case scenario.


Table: tblS4FlammablesWorstCase
Field: PR_PublicRecreation
DataType: Yes/No
Description:
An indication that a recreational area or arena is within the distance to the endpoint specified in the worst case scenario. These include stadiums, parks, and public pools.


Table: tblS4FlammablesWorstCase
Field: PR_Residences
DataType: Yes/No
Description:
An indication that residences are within the distance to the endpoint specified in the worst case scenario.


Table: tblS4FlammablesWorstCase
Field: PR_Schools
DataType: Yes/No
Description:
An indication that a school is within the distance to the endpoint specified in the worst case scenario.  Schools include: public and private elementary,
secondary, or higher education schools.


Table: tblS4FlammablesWorstCase
Field: ProcessChemicalID
DataType: Long Integer
Description:
Unique number used to identify each chemical in a process.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS4FlammablesWorstCase
Field: ptrGraphic
DataType: Text
Description:
The DOS file name of the graphic file for the flammables worst case scenario.  Should be “.JPG” or “.GIF” with up to an 8-character prefix.


Table: tblS5FlammablesAltReleases
Field: AM_DelugeSystems
DataType: Yes/No
Description:
An indication that a system to overflow an area of a release with water or other extinguishing fluid was considered.


Table: tblS5FlammablesAltReleases
Field: AM_SprinklerSystems
DataType: Yes/No
Description:
An indication that a system for protecting against fire by means of overhead pipes which convey an extinguishing fluid through heat activated outlets was considered.


Table: tblS5FlammablesAltReleases
Field: AM_WaterCurtain
DataType: Yes/No
Description:
An indication that a spray of water from a horizontal pipe through nozzles was considered.  The curtain may be activated manually or automatically.


Table: tblS5FlammablesAltReleases
Field: EndpointUsed
DataType: Text
Description:
The endpoint of the flammable reaction - “1 PSI” or “5 kw/m2 for 40 seconds” or “Lower flammability limit.”


Table: tblS5FlammablesAltReleases
Field: ER_NatlStateParks
DataType: Yes/No
Description:
An indication that national or state parks, forests, or monuments are within a circle whose center is the point of the release and radius is determined by the distance to the endpoint.


Table: tblS5FlammablesAltReleases
Field: ER_OtherType
DataType: Text
Description:
The type of environmental receptor if the environmental receptor is other than those listed in 5.9.a. through 5.9.c.


Table: tblS5FlammablesAltReleases
Field: ER_WildlifeSactuary
DataType: Yes/No
Description:
An indication that officially designated wildlife sanctuaries, preserves, or refuges are within a circle whose center is the point of the release and radius is determined by the distance to the endpoint.


Table: tblS5FlammablesAltReleases
Field: FlammableID
DataType: Long Integer
Description:
Unique identifier for the Flammables Alternative Release record.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS5FlammablesAltReleases
Field: PM_Enclosures
DataType: Yes/No
Description:
An indication that a type of physical containment of the release within a structure (e.g., a building) is in place.


Table: tblS5FlammablesAltReleases
Field: PR_Comm_Ind
DataType: Yes/No
Description:
An indication that a major commercial, office, or industrial area is within the distance to the endpoint specified in the alternative release scenario. These
include industrial parks, office buildings, shopping malls, and commercial areas.


Table: tblS5FlammablesAltReleases
Field: PR_OtherType
DataType: Text
Description:
The type of public receptor if the public receptor is other than those listed in 5.8.a. through 5.8.f.


Table: tblS5FlammablesAltReleases
Field: PR_Schools
DataType: Yes/No
Description:
An indication that a school is within the distance to the endpoint specified in the alternative release scenario.  Schools include: public and private elementary, secondary, and  higher education schools.


Table: tblS5FlammablesAltReleases
Field: ProcessChemicalID
DataType: Long Integer
Description:
From Section 1 Chemicals in Covered Process, the Process Chemical Identifier is a number unique to the chemical that is being reported and is used to identify each chemical within a process.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS5FlammablesAltReleases
Field: ptrGraphic
DataType: Text
Description:
The file name of the graphics file for the flammable alternative release scenario.  Should be “.JPG,” or “.GIF” with up to an 8-character prefix.


Table: tblS5FlammablesAltReleases
Field: Scenario
DataType: Text
Description:
The type of flammable release scenario.   One of the following should be specified:
Vapor cloud explosion;
Fireball;
BLEVE;
Pool fire;
Jet fire;
Vapor cloud fire;
Other (specify).


Table: tblS6AccidentChemicals
Field: AccidentChemicalID
DataType: Long Integer
Description:
Unique identifier for the Five-year Accident History record.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS6AccidentHistory
Field: CF_BypassCondition
DataType: Yes/No
Description:
A pipe or channel that provides an alternative pathway that detours the main pathway fails releasing a substance.


Table: tblS6AccidentHistory
Field: CF_EquipmentFailure
DataType: Yes/No
Description:
A device or piece of equipment did not function as designed thereby allowing a substance to be released.


Table: tblS6AccidentHistory
Field: CF_ImproperProcedure
DataType: Yes/No
Description:
The procedure did not reflect the current method of operation, the procedure omitted steps that affected the accident, or the procedure was written in a
manner that allowed for misinterpretation of the instructions.


Table: tblS6AccidentHistory
Field: CF_ManagementError
DataType: Yes/No
Description:
This may be used to describe failures that occur because management did not exercise its managerial control to prevent the situation from
occurring.  This is usually used to describe faulty procedures, inadequate training, or failure to follow existing administrative procedures.


Table: tblS6AccidentHistory
Field: CF_Other
DataType: Text
Description:
A description of the factor that contributed to the accident occurring if other than those listed in 6.12.a. through 6.12.k.


Table: tblS6AccidentHistory
Field: CF_UnusualWeather
DataType: Yes/No
Description:
Weather conditions, such as lightning, hail, ice storms, tornados, hurricanes, floods, or high winds caused the accident.


Table: tblS6AccidentHistory
Field: CI_NewProcessControls
DataType: Yes/No
Description:
New process designs and controls were installed to correct problems and prevent recurrence of an accidental release.


Table: tblS6AccidentHistory
Field: CI_None
DataType: Yes/No
Description:
An indication that none of the measures were taken at the facility to prevent recurrence of the accident.


Table: tblS6AccidentHistory
Field: CI_RevisedMaintenance
DataType: Yes/No
Description:
Maintenance processes were clarified or changed to ensure employees and contract employees are aware of and are practicing correct safety, process,
and administrative procedures.


Table: tblS6AccidentHistory
Field: CI_RevisedOpProcedures
DataType: Yes/No
Description:
Operating procedures were clarified or changed to ensure that employees and contract employees are trained on process operating procedures.


Table: tblS6AccidentHistory
Field: CI_RevisedTraining
DataType: Yes/No
Description:
Training programs were clarified or changed to ensure that employees and contract employees are aware of and are practicing correct safety, process,
and administrative procedures.


Table: tblS6AccidentHistory
Field: DeathsPublicResponders
ShortDesc: 6.9.a.ii On-site impacts: Deaths: Public responders
DataType: Long Integer
Description:
The number of public responders killed onsite during the accident or performing any mitigation activities.


Table: tblS6AccidentHistory
Field: DeathsWorkers
ShortDesc: 6.9.a.i On-site impacts: Deaths: Employees or contractors
DataType: Long Integer
Description:
The number of workers or contractors killed onsite during the accident or performing any mitigation activities.


Table: tblS6AccidentHistory
Field: ED_MinorDefoliation
DataType: Yes/No
Description:
An indication that the type of environmental damage that occurred involved tree, lawn, shrub, or crop damage.


Table: tblS6AccidentHistory
Field: ED_Other
DataType: Text
Description:
The name of the other type of environmental damage that occurred if other than those listed in 6.10.g.1 through 6.10.g.4.


Table: tblS6AccidentHistory
Field: Hospitalization
ShortDesc: 6.10.b Known off-site impacts: Hospitalizations
DataType: Double
Description:
The total number of injuries to the community attributable to the accident that required hospitalization.


Table: tblS6AccidentHistory
Field: InjuriesPublicResponders
ShortDesc: 6.9.b.ii On-site impacts: Injuries: Public responders
DataType: Long Integer
Description:
The number of public responders injured onsite during the accident or performing any mitigation activities.


Table: tblS6AccidentHistory
Field: InjuriesWorkers
ShortDesc: 6.9.b.i On-site impacts: Injuries: Employees or contractors
DataType: Long Integer
Description:
The number of workers or contractors injured onsite during the accident or performing any mitigation activities.


Table: tblS6AccidentHistory
Field: OffsitePropertyDamage
ShortDesc: 6.10.f Known off-site impacts: Property damage ($)
DataType: Double
Description:
Estimated value of the off-site property damage, in whole American dollars, caused by the accident, including damage to response equipment.


Table: tblS6AccidentHistory
Field: OffsiteRespondersNotify
DataType: Text
Description:
Indication of whether agencies were contacted:
	Notified only
	Notified Responded
	No, not notified
	Unknown
Users may add their own data if it is not on the list.


Table: tblS6AccidentHistory
Field: OnsitePropertyDamage
ShortDesc: 6.9.c On-site impacts: Injuries: Property damage
DataType: Double
Description:
Value of the equipment or business structures that were damaged by the accident or mitigation activities at the facility, in whole U.S. dollars.


Table: tblS6AccidentHistory
Field: RS_ProcessVessel
DataType: Yes/No
Description:
Container in which regulated substances are blended to form a mixture or reacted to convert them into some other final product or form.


Table: tblS6AccidentHistory
Field: RS_Pump
DataType: Yes/No
Description:
Device that raises, transfers, or compresses fluids or that attenuates gases by suction or pressure or both.


Table: tblS6AccidentHistory
Field: ShelteredInPlace
ShortDesc: 6.10.e Known off-site impacts: Sheltered-in-place
DataType: Double
Description:
Number of community members sheltered-in-place (ordered by the incident commander to remain inside their residence or place of work until the emergency is over).


Table: tblS6AccidentHistory
Field: StabilityClass
DataType: Text
Description:
A general indication of the degree of mixing present in the atmosphere accounting for wind speed and sunlight, where "A" represents extremely unstable conditions and "F" represents calm conditions.


Table: tblS6FlammableMixtureChemicals
Field: AccidentChemicalID
DataType: Long Integer
Description:
Unique identifier for each Accident History flammable mixture chemical.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS6FlammableMixtureChemicals
Field: FlamMixChemID
DataType: Long Integer
Description:
Unique identifier for the Accident Flammable Mixture Chemical record.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS7_Prevention_Program_Chemicals
Field: PreventionProgram3ID
DataType: Long Integer
Description:
A unique number used to identify each prevention program within a NAICS code within a process.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS7_Prevention_Program_Chemicals
Field: PrimaryKey
DataType: Long Integer
Description:
Unique identifier for the Prevention Program 3 chemicals record destination table.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS7_Prevention_Program_Chemicals
Field: ProcessChemicalID
DataType: Long Integer
Description:
A number used to identify each chemical within a single RMP from Section 1 Chemicals in Covered Process.  Generated by RMP*Submit and 3rd-party
programs.


Table: tblS7PreventionProgram3
Field: CH_InstallPerimeterMonitoring
DataType: Yes/No
Description:
Additional perimeter monitoring systems have been installed to detect a release of a regulated substance from the process.


Table: tblS7PreventionProgram3
Field: CH_InstallProcessDetection
DataType: Yes/No
Description:
Additional detection systems have been installed to detect a release of a regulated substance from the process.


Table: tblS7PreventionProgram3
Field: MD_PerimeterMonitors
DataType: Yes/No
Description:
Integrated detection networks at the source boundary.  Detection systems can include fluorescent SO2 analyzers, photoelectric tape sensors, or electrolytic chlorine detectors.


Table: tblS7PreventionProgram3
Field: MD_ProcessAreaDetectors
DataType: Yes/No
Description:
Detection systems located on or close to process equipment.  Detection systems include indicator tubes, and chromatographic, spectrometric, electrochemical, and colorimetric gas analysis.


Table: tblS7PreventionProgram3
Field: MH_Contamination
DataType: Yes/No
Description:
A release could occur if inappropriate substances are introduced into storage or process vessels.  Contamination may be a major hazard when
controlling inappropriate substances (e.g., H2O) is difficult.


Table: tblS7PreventionProgram3
Field: MH_CoolingLoss
DataType: Yes/No
Description:
These losses could be major hazards if they could lead to releases.  For example, loss of cooling could lead to an increase in pressure and failure of
a vessel or pipe, and a loss of heating or power could lead to unstable processes.


Table: tblS7PreventionProgram3
Field: MH_Corrosion
DataType: Yes/No
Description:
The presence of the regulated substance could lead to destruction of equipment and a release.  Corrosion may be a major hazard for substances
identified as corrosives on Material Safety Data Sheets unless the equipment used limits the hazard.


Table: tblS7PreventionProgram3
Field: MH_Earthquake
DataType: Yes/No
Description:
Report earthquakes as a major hazard only if they occur or are likely to occur at your site such that you design and plan for them.


Table: tblS7PreventionProgram3
Field: MH_EquipmentFailure
DataType: Yes/No
Description:
Equipment failure will be a major hazard for most processes because such failure could lead to a release.  Equipment failure includes cracks, weld
failures, disk failures, ruptures, pump/gauge/control system failures, etc.


Table: tblS7PreventionProgram3
Field: MH_Floods
DataType: Yes/No
Description:
Report floods as a major hazard only if they occur or are likely to occur at your site such that you design and plan for them.


Table: tblS7PreventionProgram3
Field: MH_Hurricanes
DataType: Yes/No
Description:
Report hurricanes as a major hazard only if they occur or are likely to occur at your site such that you design and plan for them.


Table: tblS7PreventionProgram3
Field: MH_Tornado
DataType: Yes/No
Description:
Report tornados as a major hazard only if they occur or are likely to occur at your site such that you design and plan for them.


Table: tblS7PreventionProgram3
Field: MS_BlastWalls
DataType: Yes/No
Description:
A heavy wall used to isolate buildings or areas that contain highly combustible or explosive materials.


Table: tblS7PreventionProgram3
Field: MS_SprinklerSystem
DataType: Yes/No
Description:
A system for protecting a building against fire by means of overhead pipes that release an extinguishing fluid through heat activated outlets.


Table: tblS7PreventionProgram3
Field: MS_WaterCurtain
DataType: Yes/No
Description:
A spray of water from a horizontal pipe through nozzles.  The curtain may be activated manually or automatically.


Table: tblS7PreventionProgram3
Field: PC_Alarms
DataType: Yes/No
Description:
Systems that operate a warning device after the occurrence of a Hazardous condition and procedures to activate the alarm system.


Table: tblS7PreventionProgram3
Field: PC_AutomaticShutoffs
DataType: Yes/No
Description:
Controls the shutoff flow to a pipe or vessel and are triggered automatically when process conditions are exceeded.


Table: tblS7PreventionProgram3
Field: PC_Flares
DataType: Yes/No
Description:
A pre-release protection measure used for flammable gases and vapors to remove and possibly treat discharged liquids.


Table: tblS7PreventionProgram3
Field: PC_InhibitorAddition
DataType: Yes/No
Description:
A substance that is added to a reaction that is capable of stopping or retarding a chemical reaction.


Table: tblS7PreventionProgram3
Field: PC_Interlocks
DataType: Yes/No
Description:
A switch or other device that prevents activation of a piece of equipment when a protective door is open or some other hazard exists.


Table: tblS7PreventionProgram3
Field: PC_PurgeSystem
DataType: Yes/No
Description:
A system that replaces the atmosphere in a container with an inert substance to prevent the formation of an explosive mixture.


Table: tblS7PreventionProgram3
Field: PC_ReliefValves
DataType: Yes/No
Description:
A valve that relieves pressure beyond a specified limit and re-closes upon return to normal operating procedures.


Table: tblS7PreventionProgram3
Field: PC_Scrubbers
DataType: Yes/No
Description:
A pre-release protection measure that uses water or aqueous mixtures containing scrubbing reagents to remove discharging liquids and may treat the discharging chemical.


Table: tblS7PreventionProgram3
Field: PC_Vents
DataType: Yes/No
Description:
An opening provided for the discharge of pressure or release of pressure from tanks, vessels, processing equipment, etc.


Table: tblS7PreventionProgram3
Field: PHA_Checklist
DataType: Yes/No
Description:
This technique involves developing a checklist of failure areas and reviewing each area to determine the possible effects of failure.


Table: tblS7PreventionProgram3
Field: PHA_FMEA
DataType: Yes/No
Description:
This is a methodology of tabulating the source's equipment, failure modes (how equipment fails), each failure mode's effect on the source, and a
ranking of each failure mode.


Table: tblS7PreventionProgram3
Field: PHA_FTA
DataType: Yes/No
Description:
This is a deductive technique that focuses on one particular accident event and provides a method for determining causes of the event. The fault tree is a
graphic model that displays the various combinations of equipment faults and failures that can result in a release.


Table: tblS7PreventionProgram3
Field: PHA_HAZOP
DataType: Yes/No
Description:
Hazard and Operability Studies (HAZOPs) are conducted by teams that brainstorm to systematically identify hazards or operability problems through the use of certain guidewords.


Table: tblS7PreventionProgram3
Field: PHA_WhatIf
DataType: Yes/No
Description:
A What If analysis considers the consequences associated with events that occurred as a result of failures involving equipment, design, or procedures.


Table: tblS7PreventionProgram3
Field: PHA_WhatIfChecklist
DataType: Yes/No
Description:
This technique combines the What If and checklist analysis techniques to identify and evaluate process hazards.


Table: tblS7PreventionProgram3
Field: PreventionProgram3ID
DataType: Long Integer
Description:
A unique number used to identify each prevention program within a NAICS code within a process. Generated by RMP*Submit and 3rd-party programs.


Table: tblS8_Prevention_Program_Chemicals
Field: PreventionProgram2ID
DataType: Long Integer
Description:
A unique number used to identify each prevention program within a NAICS code.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS8_Prevention_Program_Chemicals
Field: PrimaryKey
DataType: Long Integer
Description:
Unique identifier for the Prevention Program 2 Chemicals record destination table.  Generated by RMP*Submit and 3rd-party programs.


Table: tblS8_Prevention_Program_Chemicals
Field: ProcessChemicalID
DataType: Long Integer
Description:
A number used to identify each chemical within a single RMP.  Generated by RMP*Submit and 3rd- party programs.


Table: tblS8PreventionProgram2
Field: CH_InstallPerimeterMonitoring
DataType: Yes/No
Description:
Additional perimeter monitoring systems have been installed to detect a release of a regulated substance from a process.


Table: tblS8PreventionProgram2
Field: CH_OtherChanges
DataType: Text
Description:
The name of the change since the last PHA update if other than those listed in 8.4.g.1. Through 8.4.g.9.


Table: tblS8PreventionProgram2
Field: CT_OtherType
DataType: Text
Description:
A description of the type of competency test used if other than those listed in 8.6.c.1. through 8.6.c.4.


Table: tblS8PreventionProgram2
Field: FR_ANSI
DataType: Yes/No
Description:
An indication of safety compliance with the American National Standards Institute (ANSI) standards.  Nationally coordinates voluntary standards.  Gives status to standards in such areas as definitions, terminology, symbols, and abbreviations; materials, performance characteristics, procedure, and methods of rating; methods of testing and analysis; size, weight, and volume; safety, health, and building construction.


Table: tblS8PreventionProgram2
Field: FR_ASME
DataType: Yes/No
Description:
An indication of safety compliance with the American Society of Mechanical Engineers standards.  Conducts research and develops boiler, pressure vessel, and power test codes.  Also develops safety codes and standards for equipment.


Table: tblS8PreventionProgram2
Field: FR_ASTM
DataType: Yes/No
Description:
An indication of safety compliance with the American Society of Testing Materials (ASTM) standards.  Establishes standards for materials, products, systems, services, test methods, specifications, classifications, definitions, and recommended practices.


Table: tblS8PreventionProgram2
Field: FR_Comments
DataType: Text
Description:
A comment field to explain how Federal, State, or industry-specific design codes and standards are being used to demonstrate compliance with the
safety information requirement.


Table: tblS8PreventionProgram2
Field: FR_NFPA58
DataType: Yes/No
Description:
An indication of safety compliance with the National Fire Protection Association (NFPA) propane handling laws.  Propane laws are based on
NFPA 59 except in the states of California and Texas.


Table: tblS8PreventionProgram2
Field: FR_None
DataType: Yes/No
Description:
An indication that no Federal or state regulations or industry-specific design codes or standards were used to demonstrate compliance with the safety information requirement.


Table: tblS8PreventionProgram2
Field: FR_OSHA
DataType: Yes/No
Description:
An indication of safety compliance with the Occupational Safety and Health Administration  (OSHA) rule for handling anhydrous ammonia.


Table: tblS8PreventionProgram2
Field: FR_OtherType
DataType: Text
Description:
The name of the industry-specific design code or standard used to demonstrate compliance with the safety information requirement if other than one of the choices above.


Table: tblS8PreventionProgram2
Field: MaintenanceReviewDate
DataType: Date/Time
Description:
Date of most recent change that triggered review or revision of safety information, hazard review, operating or maintenance procedures or training.


Table: tblS8PreventionProgram2
Field: MD_OtherType
DataType: Text
Description:
A description of the monitoring or detection mechanism in place if other than those specified in 8.4.f.1. and 8.4.f.3.


Table: tblS8PreventionProgram2
Field: MH_Contamination
DataType: Yes/No
Description:
A release could occur if inappropriate substances are introduced into storage or process vessels.  Contamination may be a major hazard when 
controlling inappropriate substances (e.g., H2O) is difficult.


Table: tblS8PreventionProgram2
Field: MH_CoolingLoss
DataType: Yes/No
Description:
These losses could be major hazards if they could lead to releases. For example, loss of cooling could lead to an increase in pressure and failure of a vessel or pipe, and a loss of heating or power could lead to unstable processes.


Table: tblS8PreventionProgram2
Field: MH_Corrosion
DataType: Yes/No
Description:
The presence of the regulated substance could lead to destruction of equipment and a release. Corrosion may be a major hazard for substances
identified as corrosives on MSDSs unless the equipment used limits the hazard.


Table: tblS8PreventionProgram2
Field: MS_BlastWalls
DataType: Yes/No
Description:
A mitigation system which uses a heavy wall used to isolate buildings or areas that contain highly combustible or explosive materials.


Table: tblS8PreventionProgram2
Field: MS_Enclosure
DataType: Yes/No
Description:
A mitigation system which uses physical containment of the release within a structure (e.g., a building).


Table: tblS8PreventionProgram2
Field: MS_OtherType
DataType: Text
Description:
The name of the mitigation system if other than those listed in 8.4.e.1. through 8.4.e.9. are blank.


Table: tblS8PreventionProgram2
Field: MS_SprinklerSystem
DataType: Yes/No
Description:
A mitigation system for protecting a building against fire by means of overhead pipes which convey an extinguishing fluid through heat activated outlets.


Table: tblS8PreventionProgram2
Field: MS_WaterCurtain
DataType: Yes/No
Description:
A mitigation system which uses a spray of water from a horizontal pipe through nozzles, the curtain may be activated manually or automatically.


Table: tblS8PreventionProgram2
Field: PC_AutomaticShutoffs
DataType: Yes/No
Description:
Controls of the shutoff flow to a pipe or vessel and are triggered automatically when process conditions are exceeded.


Table: tblS8PreventionProgram2
Field: TR_OtherType
DataType: Text
Description:
A description of the type of training type provided if other than those  listed in 8.6.b.1 through 8.6.b.2.


Table: tblS9EmergencyResponses
Field: ER_CommunityPlan
DataType: Yes/No
Description:
Flag indicating that the facility is included in the written Community Emergency Response Plan (ERP).


Table: tblS9EmergencyResponses
Field: ER_PublicInfoProcedures
DataType: Yes/No
Description:
Flag indicating that plan includes procedures for informing public and local agencies responding to the accidental releases.


Table: tblS9EmergencyResponses
Field: ER_ResponseActions
DataType: Yes/No
Description:
Flag indicating that the plan includes specific actions that should be taken in response to an accidental release of a regulated substance.


Table: tblS9EmergencyResponses
Field: FR_EPCRA
DataType: Yes/No
Description:
These are the state Emergency Planning and Community Right-to-Know Act (EPCRA) laws.  Federal EPCRA does not require facility response plans, but some state laws may.


Table: tblS9EmergencyResponses
Field: FR_OPA90
DataType: Yes/No
Description:
An indication that the site is subject to EPA, U.S. Coast Guard, Department of Transportation, and Department of the Interior facility response plan requirements.  Currently these apply only to oil.


Table: tblS9EmergencyResponses
Field: FR_OSHA1910_120
DataType: Yes/No
Description:
An indication that the site is subject to OSHA's Hazardous Waste Operations and Emergency Response (HAZWOPER) plan.


Table: tblS9EmergencyResponses
Field: FR_OSHA1910_38
DataType: Yes/No
Description:
An indication that the site is subject to OSHA's Emergency Action Plan.  All sources are subject to this Rule except State and local governments in states without delegated OSHA programs.


Table: tblS9EmergencyResponses
Field: FR_OtherRegulation
DataType: Text
Description:
The name of the other regulation which applies to the Emergency Response Plan if other than those listed in 9.8.a. through 9.8.f.


Table: tblS9EmergencyResponses
Field: FR_RCRA
DataType: Yes/No
Description:
An indication that the site is subject to EPA's Resource Conservation and Recovery Act (RCRA) permitting requirements for solid waste.


Table: tblS9EmergencyResponses
Field: FR_SPCC
DataType: Yes/No
Description:
An indication that the site is subject to EPA's Oil Spill Prevention Control and Countermeasures Plan requirements.


Table: tlkpChemicals
Field: flgCBI
DataType: Yes/No
Description:
An indication that the Chemical is determined to be Confidential Business Information (CBI). ‘Y’es or ‘N’o.


Table: tlkpLatLongMethods
Field: Method_Code
DataType: Text
Description:
Code representing method used to obtain latitude or longitude data.  Codes can be obtained from Method Accuracy Description (MAD) Version 6.1 Information Coding Standards as implemented in Envirofacts Locational Reference Tables (EF LRT).


