Laserfiche WebLink
of the incident to identify lessons learned; post -incident reporting; and development <br />of initiatives to mitigate the effects of future incidents. <br />Recovery Plan <br />A plan developed by a State, local, or tribal jurisdiction with assistance from <br />responding Federal agencies to restore the affected area. <br />Refuge Area <br />An area identified within the Exclusion zone, if needed, for the assemblage of <br />contaminated individuals in order to reduce the risk of further contamination or <br />injury. The Refuge Area may provide the gross decontamination and triage. <br />Remedial Actions <br />Actions consistent with a permanent remedy which are necessary to prevent or <br />minimize the release of hazardous materials so that they do not spread or cause <br />substantial danger to public health and safety, or to the environment. <br />Reportable Quantity (RQ) <br />The quantity of a hazardous substance that triggers reporting under CERCLA; if a <br />substance is released in a quantity that exceeds its RQ, the release must be <br />reported to the National Response Center (NRC), as well as to the State <br />Emergency Response Commission (SERC) and the community emergency <br />coordinator for areas likely to be affected by the release. <br />Resources <br />Personnel and major items of equipment, supplies, and facilities available or <br />potentially available for assignment to incident operations and for which status is <br />maintained. Resources are described by kind and type and may be used in <br />operational support or supervisory capacities at an incident or at an EOC. <br />Resource Management <br />Efficient incident management requires a system for identifying available resources <br />at all jurisdictional levels to enable timely and unimpeded access to resources <br />needed to prepare for, respond to, or recover from an incident. Resource <br />management under the NIMS includes mutual -aid agreements; the use of special <br />Federal, State, local, and tribal teams; and resource mobilization protocols. <br />xxvii <br />