NFPA 1600 2007PLAIN ENGLISH DEFINITIONS |
NFPA 1600 is a Disaster
Management, Emergency
Management, and Business Continuity Standard.
| 3.1 Introduction |
NFPA distinguishes between two kinds of
definitions:
Terms that aren’t formally defined here tend to have their ordinary non‑technical meanings. Whenever you’re not sure about the meaning of a word, and it’s not defined here, you may wish to consult a dictionary. |
3.2 NFPA'S Official Definitions |
3.2.1 ApprovedSomething is approved when it has been
accepted or certified. But, what is being approved? While
NFPA doesn’t say so explicitly, But, when can we say that something is approved?
Or, more
|
3.2.2 Authority Having Jurisdiction (AHJ)AHJs include:
AHJs have two responsibilities:
AHJs have the official authority and duty to
enforce compliance |
3.2.3 ShallWhen the word shall is used in a sentence,
it means that a |
3.2.4 ShouldWhen the word should is used in a
sentence, it means that |
3.2.5 StandardA standard is a document that defines a
set of expectations.
Requirements are defined in
Chapter 4 and
Chapter 5, while |
3.3 Other Technical Definitions |
3.3.1 Business ContinuityA business continuity program is a process
that is
In order to be effective, a business
continuity program |
3.3.2 Damage AssessmentA damage assessment is an analytical
process that
|
3.3.3 Disaster or Emergency ManagementDisaster or emergency management is an
This management process tries to cope with:
|
3.3.4 Emergency Management ProgramNFPA 1600 asks you to develop a program that complies with this NFPA standard. Definition 3.3.4 says that this program may be referred to as an emergency management program. More precisely, any organization that establishes a vision and mission that complies with the NFPA 1600 standard and sets up a management framework to achieve the standard’s strategic goals and objectives, could be referred to as an emergency management program. |
3.3.5 EntityAn entity is a group of people responsible
Entities include:
|
3.3.6 Impact Analysis (Business Impact Analysis)An impact analysis is a methodology that
managers use
Such an analysis helps managers:
An impact analysis can also be referred to |
3.3.7 Incident Action PlanAn incident action plan describes how an incident or emergency is being handled. It explains what the risks are, what the basic strategy is, and what kinds of tactics are being used to respond to a particular incident or emergency. The incident action plan is developed by the incident commander and is updated as the emergency evolves. |
3.3.8 Incident Management System (IMS)An incident management system is an organizational structure that is set up to manage emergencies and incidents (hazardous events). An incident management system achieves its goals by managing incident management personnel, procedures, facilities, equipment, and communications. |
3.3.9 MitigationTo mitigate means to reduce the severity of hazardous incidents and emergencies, to control the consequences, and to limit the damage and loss that tends to occur when prevention fails. |
3.3.10 Mutual Aid AgreementA mutual aid agreement is a mutual
understanding or promise |
3.3.11 PreparednessPreparedness means being ready to handle
future emergencies. Your jurisdiction, organization, or company
has achieved a state of preparedness
if you're ready to manage future emergencies.
You're ready if you've established all the
systems, programs, and procedures that are needed and if you've defined
all the tasks and activities that should be performed. You’ve
achieved a state of
|
3.3.12 PreventionPrevention means to avoid an incident or
emergency.
|
3.3.13 RecoveryRecovery means to restore or rebuild services, operations, facilities, programs, and institutions after an incident or emergency. Recovery means to restore conditions back to a level that is acceptable to the company, organization, or jurisdiction that experienced the incident or emergency. |
3.3.14 Resource ManagementResource management is a system that is used to identify and deploy resources that are needed to manage incidents. Resource management systems use a variety of methods to manage and control both internal and external resources (both purchased and donated). Resources include personnel, services, supplies, materials, equipment, facilities, energy, information, and systems. These resources are used to:
|
3.3.15 ResponseA response is an activity or task that is carried out or a program or system that is used to manage incidents that threaten people, property, operations, or the environment. Responses are both immediate and ongoing and should address both the incident and its effects. |
3.3.16 Situation AnalysisA situation analysis evaluates incidents and
events and prepares
|
3.3.17 StakeholderStakeholders include individual, groups,
and organizations.
|
![]()
| CONTACT INFORMATION |
| Praxiom Research Group Limited 9619 - 100A Street, Edmonton, Alberta, T5K 0V7, Canada Phone: (780)461-4514 Fax: (780)463-6034 info@praxiom.org |
![]()
Legal
Restrictions on the Use of this Page
Thank
you for visiting this page. You are, of course, welcome to view our
material as often as you wish, free of charge. And as long as you
keep intact
all copyright notices, you are also welcome to print or make one
copy of this
page for your own personal, noncommercial, home use.
But, you are not
legally authorized to print or produce additional copies, or to
copy and paste
any of our material onto another web site. If you would like
to purchase our
material, please contact our Sales Desk. Our staff would be very
pleased to
take your order or to answer any questions you might have.
Disclaimer and Limitation of Liability
The
publisher and authors have used their best efforts in designing and
developing this electronic publication. We make no representation or
warranties
with respect to accuracy or completeness of the contents of
this publication and
specifically disclaim any implied warranties or
merchantability or fitness for any
particular purpose and shall in no
event be liable for any loss of profit or any
other commercial damage,
including but not limited to special, incidental,
consequential, or
other damages.
Copyright © 2005 - 2007 by Praxiom Research Group Limited. All Rights Reserved.

| How to Order | Our Products | Our Prices | Our Guarantee |
| Home Page | Table of Contents | Our Customers | Our Supporters |
| OTHER NFPA 1600 WEB PAGES |
| Introduction to NFPA |
| Introduction to NFPA 1600 |
| Overview of NFPA 1600 2007 |
| NFPA 1600 2007 in Plain English |
| NFPA 1600 2007 Audit Process |
| How to Develop an NFPA 1600 Mitigation Strategy |
| How to Conduct NFPA 1600 Business Continuity Planning |
| How to Develop an NFPA 1600 Corrective Action Procedure |
| Business Continuity Management using the NFPA 1600 Standard |
| Emergency Management using the NFPA 1600 Standard |
| Disaster Management using the NFPA 1600 Standard |
|
NFPA 1600 2007 is an Emergency Management, |
Updated on September 10, 2007. On the web since May 25, 2007.
Also see ISO 27002 (17799) Information Security Audit Tool.
![]()