NFPA

951
Guide to Building and Utilizing
Digital Information

2016

ORDER VISIT
To order or for more details on other NFPA our online
products or seminars, call 1-800-344-3555. catalog at
For orders outside the U.S., call 617-770-3000. catalog.nfpa.org.
 ®
IMPORTANT NOTICES AND DISCLAIMERS CONCERNING NFPA DOCUMENTS

NOTICE AND DISCLAIMER OF LIABILITY CONCERNING THE USE OF NFPA DOCUMENTS

®
NFPA codes, standards, recommended practices, and guides (“NFPA Standards”), of which the document
contained herein is one, are developed through a consensus standards development process approved by the
American National Standards Institute. This process brings together volunteers representing varied viewpoints
and interests to achieve consensus on fire and other safety issues. While the NFPA administers the process and
establishes rules to promote fairness in the development of consensus, it does not independently test, evaluate, or
verify the accuracy of any information or the soundness of any judgments contained in NFPA Standards.
The NFPA disclaims liability for any personal injury, property or other damages of any nature whatsoever,
whether special, indirect, consequential or compensatory, directly or indirectly resulting from the publication, use
of, or reliance on NFPA Standards. The NFPA also makes no guaranty or warranty as to the accuracy or
completeness of any information published herein.
In issuing and making NFPA Standards available, the NFPA is not undertaking to render professional or other
services for or on behalf of any person or entity. Nor is the NFPA undertaking to perform any duty owed by any
person or entity to someone else. Anyone using this document should rely on his or her own independent
judgment or, as appropriate, seek the advice of a competent professional in determining the exercise of
reasonable care in any given circumstances.
The NFPA has no power, nor does it undertake, to police or enforce compliance with the contents of NFPA
Standards. Nor does the NFPA list, certify, test, or inspect products, designs, or installations for compliance with
this document. Any certification or other statement of compliance with the requirements of this document shall
not be attributable to the NFPA and is solely the responsibility of the certifier or maker of the statement.

REMINDER: UPDATING OF NFPA STANDARDS

Users of NFPA codes, standards, recommended practices, and guides (“NFPA Standards”) should be
aware that NFPA Standards may be amended from time to time through the issuance of Tentative
Interim Amendments or corrected by Errata. An official NFPA Standard at any point in time consists of
the current edition of the document together with any Tentative Interim Amendment and any Errata
then in effect.
In order to determine whether an NFPA Standard has been amended through the issuance of
Tentative Interim Amendments or corrected by Errata, visit the Document Information Pages on
NFPA’s website. The Document Information Pages provide up-to-date, document specific information
including any issued Tentative Interim Amendments and Errata.
To access the Document Information Page for a specific NFPA Standard, go to http://
www.nfpa.org/docinfo to choose from the list of NFPA Standards or use the search feature on the right
to select the NFPA Standard number (e.g., NFPA 101). The Document Information page includes
postings of all existing Tentative Interim Amendments and Errata. It also includes the option to
register for an “Alert” feature to receive an automatic email notification when new updates and other
information are posted regarding the document.

ISBN: 978-145591309-1 (Print)

ISBN: 978-145591338-1 (PDF)
 ®
IMPORTANT NOTICES AND DISCLAIMERS CONCERNING NFPA STANDARDS

ADDITIONAL NOTICES AND DISCLAIMERS

Updating of NFPA Standards

Users of NFPA codes, standards, recommended practices, and guides (“NFPA Standards”) should be aware that these
documents may be superseded at any time by the issuance of new editions or may be amended from time to time through the
issuance of Tentative Interim Amendments or corrected by Errata. An official NFPA Standard at any point in time consists of
the current edition of the document together with any Tentative Interim Amendments and any Errata then in effect. In order
to determine whether a given document is the current edition and whether it has been amended through the issuance of
Tentative Interim Amendments or corrected through the issuance of Errata, consult appropriate NFPA publications such as the
National Fire Codes® Subscription Service, visit the NFPA website at www.nfpa.org, or contact the NFPA at the address listed
below.
Interpretations of NFPA Standards
A statement, written or oral, that is not processed in accordance with Section 6 of the Regulations Governing the
Development of NFPA Standards shall not be considered the official position of NFPA or any of its Committees and shall not
be considered to be, nor be relied upon as, a Formal Interpretation.
Patents
The NFPA does not take any position with respect to the validity of any patent rights referenced in, related to, or asserted in
connection with an NFPA Standard. The users of NFPA Standards bear the sole responsibility for determining the validity of
any such patent rights, as well as the risk of infringement of such rights, and the NFPA disclaims liability for the infringement
of any patent resulting from the use of or reliance on NFPA Standards.
NFPA adheres to the policy of the American National Standards Institute (ANSI) regarding the inclusion of patents in
American National Standards (“the ANSI Patent Policy”), and hereby gives the following notice pursuant to that policy:
NOTICE: The user’s attention is called to the possibility that compliance with an NFPA Standard may require use of an
invention covered by patent rights. NFPA takes no position as to the validity of any such patent rights or as to whether such
patent rights constitute or include essential patent claims under the ANSI Patent Policy. If, in connection with the ANSI Patent
Policy, a patent holder has filed a statement of willingness to grant licenses under these rights on reasonable and
nondiscriminatory terms and conditions to applicants desiring to obtain such a license, copies of such filed statements can be
obtained, on request, from NFPA. For further information, contact the NFPA at the address listed below.
Law and Regulations
Users of NFPA Standards should consult applicable federal, state, and local laws and regulations. NFPA does not, by the
publication of its codes, standards, recommended practices, and guides, intend to urge action that is not in compliance with
applicable laws, and these documents may not be construed as doing so.
Copyrights
NFPA Standards are copyrighted. They are made available for a wide variety of both public and private uses. These include
both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of safe
practices and methods. By making these documents available for use and adoption by public authorities and private users, the
NFPA does not waive any rights in copyright to these documents.
Use of NFPA Standards for regulatory purposes should be accomplished through adoption by reference. The term
“adoption by reference” means the citing of title, edition, and publishing information only. Any deletions, additions, and
changes desired by the adopting authority should be noted separately in the adopting instrument. In order to assist NFPA in
following the uses made of its documents, adopting authorities are requested to notify the NFPA (Attention: Secretary,
Standards Council) in writing of such use. For technical assistance and questions concerning adoption of NFPA Standards,
contact NFPA at the address below.
For Further Information
All questions or other communications relating to NFPA Standards and all requests for information on NFPA procedures
governing its codes and standards development process, including information on the procedures for requesting Formal
Interpretations, for proposing Tentative Interim Amendments, and for proposing revisions to NFPA standards during regular
revision cycles, should be sent to NFPA headquarters, addressed to the attention of the Secretary, Standards Council, NFPA, 1
Batterymarch Park, P.O. Box 9101, Quincy, MA 02269-9101; email: [email protected]
For more information about NFPA, visit the NFPA website at www.nfpa.org. All NFPA codes and standards can be viewed at
no cost at www.nfpa.org/freeaccess.
 951-1

Copyright © 2015 National Fire Protection Association®. All Rights Reserved.

NFPA®951

Guide to

Building and Utilizing Digital Information

2016 Edition

This edition of NFPA 951, Guide to Building and Utilizing Digital Information, was prepared by the
Technical Committee on Data Exchange for the Fire Service. It was issued by the Standards Council
on November 14, 2015, with an effective date of December 4, 2015, and supersedes all previous
editions.
This edition of NFPA 951 was approved as an American National Standard on December 4, 2015.

Origin and Development of NFPA 950

In 2007, at the recommendation of the late Bill McCammon, NFPA Treasurer, a letter was
advanced by the Metro Fire Chiefs Association (a joint section of the NFPA and the IAFC) and
signed by six of the major international fire service organizations, requesting that the NFPA
Standards Council embark on an effort to develop a standard on “data exchange” for fire
departments.
As described in the letter, the purpose of the new standard would be to enable a higher level of
technology penetration in the fire service to enhance data sharing and analytic capability. The issue
was framed to support effective communication and information management on a routine basis and
to enhance situational awareness before, during, and after disasters.
This information exchange need was identified as particularly critical with respect to the
following:
(1) The ability to exchange geographic information between local systems and evolving regional
and national systems to support such functions as vulnerability/risk assessment and
coordinated incident management
(2) The requirements of evolving mutual aid and resource exchange programs
(3) The requirements for participation in systems designed to monitor local, regional, and
national preparedness levels during times of high risk
(4) Fire and emergency service access to and utilization of critical infrastructure data collected
and distributed through national systems
The effort was initiated to enhance the analysis of organizations, promote exchange of concepts
and data development, focus on GIS systems efforts with an industry-wide perspective rather than a
“one-off,” per-organization approach, and streamline and maintain comprehensive inducements to
invest in data systems for the digital age. Solicitation of members was approved by the Standards
Council, and subsequent industrywide response created the membership necessary to draft code-type
and scope documents. Efforts by that group at the initial meeting, held at the IAFC headquarters in
Fairfax, Virginia, resulted in the Standards Council creating a committee and approving efforts to
create a standard on Fire Service Data Exchange (NFPA 950) in 2008.
The new Technical Committee, Data Exchange for the Fire Service, met several times between
November 2008 and February 2011 and produced a draft, approved by the Standards Council, to go
out for public input in the Fall 2014 cycle. The 2015 edition of NFPA 950, Standard for Data
Development and Exchange for the Fire Service, was its inaugural edition.
NFPA 951, Guide to Building and Utilizing Digital Information, was developed as a companion piece
to NFPA 950. NFPA 951 offers guidance to organizations in building NFPA 950–compliant systems.
This effort was undertaken in tandem with NFPA 950 and developed concurrently, thus maintaining
consistency throughout the documents. This first edition of NFPA 951 is intended to be a building
block for data integration in the fire service.

NFPA and National Fire Protection Association are registered trademarks of the National Fire Protection Association, Quincy, Massachusetts 02169.
951-2 BUILDING AND UTILIZING DIGITAL INFORMATION

Technical Committee on Data Exchange for the Fire Service

Edward P. Plaugher, Chair
International Association of Fire Chiefs, SC [E]
Rep. International Association of Fire Chiefs

Andrew D. Bailey, U.S. Department of Interior, ID [E] Paul Morgan, Alameda County Regional Emergency
Talbot J. Brooks, Delta State University, MS [SE] Communication Center, CA [E]
Leandro E. Cieri, City of Hartford Fire Department, CT [U] Kenneth A. Pravetz, City of Virginia Beach Fire Department, VA
[E]
Ron G. Corona, Los Angeles City Fire Department, CA [U]
Michael J. Price, Entrada/San Juan, Inc., WA [SE]
Jeffrey P. Hartberger, Hilton Head Island Fire Rescue, SC [U]
Jennifer Schottke, ESRI, VA [M]
Vickie Hodges, State Farm Insurance Companies, IL [I]
Paul Siebert, Frisco Fire Department, TX [E]
Sarah Ierley, Montgomery County Fire & Rescue Service, MD [E]
James C. Smalley, Scituate, MA [SE]
Kevin P. Kuntz, Insurance Services Office, Inc., NJ [I]
Rep. National Alliance for Public Safety GIS Foundation
Louis A. LaVecchia, Milford, CT [SE]
Christine Klingman Thies, City of Austin Fire Department, TX [U]
Crystal McDuffie, APCO International, FL [SE]
Chris Tubbs, Southern Marin Fire District, CA [U]
Rep. Association of Public-Safety Communications Officials
International Inc. Michael F. Weins, Gartner, VA [SE]
Nathaniel J. Melby, Town of Campbell Fire Department, WI [U] Ty Wooten, National Emergency Number Association, VA [U]
Rep. Volunteer & Combination Officers Section
Jonathan W. Moore, Canterbury, NH [L]
Rep. International Association of Fire Fighters

Alternates
Thomas Dewey, Advanced Justice Systems, CA [SE] Kimber Rosehlle Pederson, U.S. Department of the Interior, ID
Jay English, APCO International, FL [SE] [E]
(Alt. to Crystal McDuffie) (Alt. to Andrew D. Bailey)
Russell G. Johnson, ESRI, CA [M] Jamilatu Zakari, Austin Fire Department, TX [U]
(Alt. to Jennifer Schottke) (Alt. to Christine Klingman Thies)
Thomas R. Mueller, California University of Pennsylvania, PA [SE]
(Alt. to Talbot J. Brooks)
Thomas M. O'Toole, International Association of Fire Fighters,
DC [L]
(Alt. to Jonathan W. Moore)

Nonvoting
Marie E. Martinez, U.S. Department of Homeland Security, MD
[C]

Chris Farrell, NFPA Staff Liaison

This list represents the membership at the time the Committee was balloted on the final text of this edition.
Since that time, changes in the membership may have occurred. A key to classifications is found at the
back of the document.

NOTE: Membership on a committee shall not in and of itself constitute an endorsement of

the Association or any document developed by the committee on which the member serves.

Committee Scope: This Committee shall have primary responsibility for documents that
establish frameworks to 1) provide for the identification, development, management, and
exchange of essential data; and 2) enhance an inter-operable geospatial data environment
for fire and emergency services. This includes documents that establish criteria for and
promote the exchange and use of data in common formats critical to the support for
decision making in all phases of administration, planning, prevention, preparedness,
mitigation, response, and recovery.

2016 Edition
 CONTENTS 951-3

Contents

Chapter 1 Administration ............................................ 951– 4 Technical Standards for Fire and Emergency
1.1 Scope. ................................................................... 951– 4 Service Organizations. .........................................
1.2 Purpose. ............................................................... 951– 4 4.8 Technology Planning. .......................................... 951– 10
1.3 Application. .......................................................... 951– 4
Chapter 5 Data Administration .................................... 951– 11
Chapter 2 Referenced Publications ............................ 951– 5 5.1 General. ................................................................ 951– 11
2.1 General. ................................................................ 951– 5 5.2 Data. ..................................................................... 951– 11
2.2 NFPA Publications. .............................................. 951– 5 5.3 Management/Organization. ............................... 951– 11
2.3 Other Publications. ............................................. 951– 5 5.4 Data Models and Schemas. ................................. 951– 11
2.4 References for Extracts in Advisory Sections. ... 951– 5 5.5 Data Sources and Acquisition. ............................ 951– 11
5.6 Security. ................................................................ 951– 12
Chapter 3 Definitions ................................................... 951– 5 5.7 Maintenance. ....................................................... 951– 12
3.1 General. ................................................................ 951– 5 5.8 Data Exchange. .................................................... 951– 13
3.2 NFPA Official Definitions. .................................. 951– 5
3.3 General Definitions. ............................................ 951– 6 Chapter 6 Data Sharing and Exchange ....................... 951– 14
6.1 Introduction. ........................................................ 951– 14
Chapter 4 Process ......................................................... 951– 6 6.2 Addresses. ............................................................. 951– 14
4.1 General. ................................................................ 951– 6 6.3 Date and Time. .................................................... 951– 14
4.2 Technology Strategic Visioning. ......................... 951– 6 6.4 Incident Typing Information. ............................. 951– 14
4.3 Technology Strategic Planning. .......................... 951– 6 6.5 Text. ...................................................................... 951– 14
4.4 Mission Requirements and User Needs. ............ 951– 6 6.6 CAD, RMS, CAD/CAD, CAD/RMS, and
4.5 Governance and Policy. ....................................... 951– 8 RMS/RMS Exchange. .......................................... 951– 14
4.6 Interoperability and Scalability. .......................... 951– 9
4.7 Planning and Implementation of NFPA 950: Annex A Explanatory Material .................................. 951– 15
An Overview of Implementing Technology and 951– 9
Annex B Informational References .......................... 951– 18

Index ..................................................................... 951– 19

2016 Edition
951-4 BUILDING AND UTILIZING DIGITAL INFORMATION

NFPA 951 1.1.3 The intent of this guide is to provide a framework and
environment consistent with NFPA 950 that results in an infor‐
Guide to mation system for computer aided dispatch (CAD), record
management systems (RMS), geographic information systems
Building and Utilizing Digital Information (GIS), and other associated data systems in common use by fire
and emergency service organizations.
2016 Edition 1.2 Purpose. The purpose of this guide is to help public safety
users envision, plan, build, and maintain an operable, and scal‐
IMPORTANT NOTE: This NFPA document is made available for able information system.
use subject to important notices and legal disclaimers. These notices
1.2.1 A standard approach is essential to manage, use, main‐
and disclaimers appear in all publications containing this document
tain, and exchange data. This guide assists fire and emergency
and may be found under the heading “Important Notices and
service organizations in establishing a vision for information
Disclaimers Concerning NFPA Documents.” They can also be
management within their organization.
obtained on request from NFPA or viewed at www.nfpa.org/disclaim‐
ers. 1.2.2 Technology planning is an essential step in creating an
UPDATES, ALERTS, AND FUTURE EDITIONS: New editions of integrated information management environment. NFPA 950
NFPA codes, standards, recommended practices, and guides (i.e., mandates a methodology for a step-by-step process for technol‐
NFPA Standards) are released on scheduled revision cycles. This ogy planning. This guide recommends a framework for the
edition may be superseded by a later one, or it may be amended governance and oversight needed to establish an effective plan‐
outside of its scheduled revision cycle through the issuance of Tenta‐ ning process based on NFPA 950.
tive Interim Amendments (TIAs). An official NFPA Standard at any
point in time consists of the current edition of the document, together 1.2.3 To create an information system, the authority having
with any TIAs and Errata in effect. To verify that this document is jurisdiction (AHJ) must understand the specific requirements
the current edition or to determine if it has been amended by any for the interoperable use of the data. NFPA 950 sets forth the
TIAs or Errata, please consult the National Fire Codes® Subscription overarching technical standards these requirements must
Service or visit the Document Information (DocInfo) pages on the satisfy. The information in this guide assists the agency in creat‐
NFPA website at www.nfpa.org/docinfo. In addition to TIAs and ing a flexible and scalable system that supports data sharing.
Errata, the DocInfo pages also include the option to sign up for Alerts 1.2.4 This guide provides references and resources for fire and
for each document and to be involved in the development of the next emergency service organization personnel to help identify
edition. applications of and uses for data to improve the organization’s
NOTICE: An asterisk (*) following the number or letter ability to perform fire prevention, damage mitigation, emer‐
designating a paragraph indicates that explanatory material on gency response, and recovery from emergency incidents.
the paragraph can be found in Annex A.
A reference in brackets [ ] following a section or paragraph 1.2.5 This guide is a reference tool and job aid that provides
indicates material that has been extracted from another NFPA practical guidance.
document. As an aid to the user, the complete title and edition 1.3 Application.
of the source documents for extracts in mandatory sections of
the document are given in Chapter 2 and those for extracts in 1.3.1 This guide was designed to be used by fire and emer‐
informational sections are given in Annex B. Extracted text gency service organizations to develop an information struc‐
may be edited for consistency and style and may include the ture and associated requirements and workflows common to
revision of internal paragraph references and other references fire protection delivery and management for emergency
as appropriate. Requests for interpretations or revisions of response and administrative use.
extracted text shall be sent to the technical committee respon‐
sible for the source document. 1.3.2 When implemented, this guide also creates an environ‐
Information on referenced publications can be found in ment whereby fire and emergency service organizations will be
Chapter 2 and Annex B. able to identify best practices, internal and external to the
agency, to ensure data operability in mutual and automatic aid
environments.
Chapter 1 Administration
1.3.3 The purpose of this guide is to describe for all levels of
1.1 Scope. the organization the mechanisms for establishing a standards-
based information management environment, which is an
1.1.1* The intent of this guide is to provide guidance in the essential element for optimal functioning of fire and emer‐
development and integration of information systems to facili‐ gency service organizations. Effective information management
tate information sharing and use. The resulting information is a key to be utilized in keeping fire fighters safe, improving
systems should be designed to support a communications path‐ outcomes, and satisfying performance metrics. An integrated
way for all relevant components of the national preparedness information technology strategy that adheres to the specifica‐
and response framework. tions of NFPA 950 will accomplish these goals by achieving the
following objectives:
1.1.2* This guide provides information for the development of
consistent methods, processes, and tools to capture, utilize, and (1) Establish and maintain accurate and up-to-date under‐
share data within scalable information systems. This framework standing of operations and the events that affect them
supports and sets the stage for effective data exchange at all (2) Collect, organize, exchange, and discover through
operational levels and components. research relevant and authoritative information

2016 Edition
 DEFINITIONS 951-5

(3) Proactively support community fire planning needs and

activities Common
(4) Exchange information to establish data streams into and Incident Public
management operating information
out of the field picture

Inspections
production
(5) Integrate data from multiple internal and external sour‐

Map
ces Situational
(6) Enable a higher level of collaborative decision making awareness
with other stakeholder partners
(7) Maximize value from technology investments

Personnel
resource
Logistics

records
1.3.4 To achieve an NFPA 950–compliant data environment,

management
operations
senior executive leadership must support the decision to imple‐ System

Field

Data
ment the framework principles described in this guide. For Integration
many in the fire and emergency services, managing informa‐

awareness

Pre-plans
updates
Field
tion technology is a new endeavor. Therefore, this guide is writ‐

and
ten to enhance knowledge of fundamental information
management principles in the context of the work that is done
in the fire and emergency services. It is intended to enhance

Records
collection

incident
reports
the knowledge of all members of the organization, as well as Planning

Data
related entities, which is essential for successful implementa‐ and analysis
tion. This allows leadership the framework for implementing
the department’s technology plan in the context of a shared Pre- Standards Risk
Mitigation
incident of and hazard
vision. planning
planning
cover assessment
1.3.5* NFPA 950 is a standard that identifies the critical build‐
ing blocks of a fire and emergency service organization’s infor‐
mation management system. The standard provides a common FIGURE 1.3.5.1 Information Systems Framework for Fire
framework for all departments regardless of size, shape, and and Emergency Service Organizations.
technological resource availability. Embracing this framework
will provide the foundation as an organization begins to assess
its particular landscape, analyze its specific technology require‐ 2.2 NFPA Publications. National Fire Protection Association, 1
ments, and develop a plan that fits its unique environment. Batterymarch Park, Quincy, MA 02169-7471.

1.3.5.1 Figure 1.3.5.1 provides a framework for how an NFPA 950, Standard for Data Development and Exchange for the
organization-wide strategy for information management can Fire Service, 2015 edition.
support the entire organization. A wide range of players within 2.3 Other Publications.
an organization contribute data, perform analysis, and
exchange important field intelligence. Utilization of these key Merriam-Webster’s Collegiate Dictionary, 11th edition, Merriam-
elements provides the framework for organizations and their Webster, Inc., Springfield, MA, 2003.
members to perform their mission effectively and will enhance 2.4 References for Extracts in Advisory Sections.
the overall safety environment. These different functions
within a fire and emergency service organization also have NFPA 450, Guide for Emergency Medical Services and Systems,
different requirements for data and applications. The integra‐ 2017 edition.
ted information management platform illustrated in Figure
1.3.5.1 will support all of these key elements and the ability to NFPA 950, Standard for Data Development and Exchange for the
leverage their respective expertise, perspectives, and skills Fire Service, 2015 edition.
within this data environment.
1.3.5.2 Figure 1.3.5.1 illustrates the concept behind this guide Chapter 3 Definitions
and NFPA 950. It addresses the four fundamental ways informa‐
tion is used to support the goals of a public safety agency. 3.1 General. The definitions contained in this chapter apply
These four categories are as follows (additional information for to the terms used in this guide. Where terms are not defined in
each category is detailed in Chapter 4 and in A.1.3.5). this chapter or within another chapter, they should be defined
using their ordinarily accepted meanings within the context in
(1) Planning and analysis which they are used. Merriam-Webster’s Collegiate Dictionary, 11th
(2) Data management edition, is the source for the ordinarily accepted meaning.
(3) Field operations
(4) Situational awareness 3.2 NFPA Official Definitions.
3.2.1 Approved. Acceptable to the authority having jurisdic‐
Chapter 2 Referenced Publications tion.
3.2.2 Authority Having Jurisdiction (AHJ). An organization,
2.1 General. The documents or portions thereof listed in this office, or individual responsible for enforcing the requirements
chapter are referenced within this guide and should be consid‐ of a code or standard, or for approving equipment, materials,
ered part of the recommendations of this document. an installation, or a procedure.

2016 Edition
951-6 BUILDING AND UTILIZING DIGITAL INFORMATION

3.2.3 Guide. A document that is advisory or informative in 4.2 Technology Strategic Visioning. A strategic visioning proc‐
nature and that contains only nonmandatory provisions. A ess helps to clarify where the organization, its employees, the
guide may contain mandatory statements such as when a guide political leadership, and other stakeholders see the organiza‐
can be used, but the document as a whole is not suitable for tion in the future in terms of its fundamental objective and/or
adoption into law. strategic direction. To be meaningful and relevant, a vision
must be realistic and attainable. A strategic vision must inspire
3.2.4 Listed. Equipment, materials, or services included in a and motivate. Once a vision has been established, the next step
list published by an organization that is acceptable to the is to translate the vision into action.
authority having jurisdiction and concerned with evaluation of
products or services, that maintains periodic inspection of 4.3* Technology Strategic Planning. Establishment of a strate‐
production of listed equipment or materials or periodic evalua‐ gic visioning construct is an underpinning to drive the technol‐
tion of services, and whose listing states that either the equip‐ ogy strategy. Technology strategic planning is a tool that should
ment, material, or service meets appropriate designated end with objectives and a roadmap of ways to achieve the
standards or has been tested and found suitable for a specified organization’s vision. This section covers the fundamental steps
purpose. in the strategic planning process.
3.2.5 Standard. An NFPA Standard, the main text of which 4.3.1 A properly written strategic plan will provide the organi‐
contains only mandatory provisions using the word “shall” to zation with the necessary guidance to develop resources
indicate requirements and that is in a form generally suitable needed to satisfy the vision. An effective strategic plan should
for mandatory reference by another standard or code or for be all-encompassing and constructed only after a deliberative
adoption into law. Nonmandatory provisions are not to be process such as that suggested in A.4.3.
considered a part of the requirements of a standard and shall
be located in an appendix, annex, footnote, informational 4.3.2 Critical to the strategic planning process will be learning
note, or other means as permitted in the NFPA Manuals of how to incorporate technology, particularly geospatial technol‐
Style. When used in a generic sense, such as in the phrase ogy, into the fabric of the organization’s culture and mission.
“standards development process” or “standards development Fundamental to this process is the notion that technology plan‐
activities,” the term “standards” includes all NFPA Standards, ning is integral in supporting the overall strategic plan and
including Codes, Standards, Recommended Practices, and vision. Technology planning must be developed in collabora‐
Guides. tion with technology professionals and a clear understanding
of workflows. It is critical that an agency’s relevant functions be
3.3 General Definitions. incorporated into the technology planning process.
3.3.1 Information System/Geographic Information System 4.3.3 NFPA 950 is a standard for data framework that supports
(GIS). Integrated sets of hardware and software that people the workflows discussed in NFPA 951.
and organizations use to collect, store, process, and communi‐
cate data; a GIS is used to analyze relationships, model 4.4 Mission Requirements and User Needs. A needs assess‐
processes, and display data spatially. ment is an integral part of planning. Conducted properly, it is a
multitiered structured inventory process that provides the
3.3.2 Interoperability. The capability of components or awareness needed to assist an organization through the process
systems to exchange data or information with other compo‐ of planning for an information management system. Adher‐
nents or systems, or to perform in multiple environments. ence to this process will help to avoid single-point solutions
that operate as silos and fail. Each agency will have its own
3.3.3 Response. The deployment of an emergency service vision of how to fulfill its mission, which should be articulated
resource to an incident. [450, 2013] in the strategic plan as described in Section 4.3. Once this
3.3.4 Scalability. The designed characteristic of a system that mission is clearly understood and articulated in the organiza‐
allows it to transition in size without showing negative effects. tion’s policy and planning documents, the technology planning
committee will identify the workflows and associated applica‐
3.3.5 Scalable. The ability to transition in size or complexity tions that technology can support. The next step is to prioritize
without showing negative effects. which of these will be included in the technology plan, based
3.3.6 Text Data. Data limited to display as ASCII characters. on mission priorities, cost-benefit timelines, and funding availa‐
[950, 2015] bility. It is the mission requirement that must drive the technol‐
ogy — not the other way around.
3.3.7 Workflow. A set of processes defined by procedural rules
or a progression of steps, which can include automation, 4.4.1 List of Workflows. Descriptions of some workflows that
between activities in a project or function. can be effectively supported by technology are given in 4.4.1.1
through 4.4.1.4.6. All of these should be considered to the
extent they help the organization accomplish its vision. Table
Chapter 4 Process 4.4.1 provides some common examples of functions supported
by a fire and emergency service organization information
4.1 General. The purpose of this chapter is to describe the system or geographic information system (GIS), or both.
process of developing an information system to acquire,
manage, use, and share information as it pertains to fire and 4.4.1.1 Planning. Planning is a multifaceted process that
emergency service functionsto successfully implement ranges from risk prevention to budgeting across all programs
NFPA 950. The following are the main elements in this process: in fire and emergency service organizations. The proper appli‐
cation of technology provides a set of tools that can enhance
(1) Visioning the planning process. Effective data management leads to
(2) Technology strategic planning meaningful information for enhanced decision making. In
(3) Ongoing needs assessment

2016 Edition
 PROCESS 951-7

Table 4.4.1 Examples of Functions Supported by a Fire and Emergency Service Organization Information System or Geographic
Information System (GIS), or Both

Planning Preparedness Response Recovery

Capability assessment Pre-incident planning CAD, AVL, and routing Damage assessment
Vulnerability/ Resource deployment In-vehicle applications Debris removal
risk assessment
Inspections Targeted mitigation Mobile/field intelligence Infrastructure restoration
Training and exercises Search and rescue Economic and community
recovery
Evacuation, shelter, and mass Environmental stabilization
care
Public warning and Public information
notification
Command and control Analysis and management of
recovery efforts
Incident resource
management
Multidisciplinary coordination
Operations dashboard

particular, it is critical for decision making before, during, and through the building. Technology can help streamline the
after emergency response. acquisition, management, and accessibility of this data.
4.4.1.1.1 Capability Assessment. Capability assessment is a 4.4.1.2.2 Resource Deployment. Resource planning and
method for evaluating the stakeholder’s ability to react to deployment is a dynamic process. Proper resource manage‐
potential all-hazards incidents. A realistic and accurate assess‐ ment requires ongoing analysis. Technology can help agencies
ment identifies potential risks, strengths, weaknesses, and the provide appropriate resources at appropriate levels.
ability to respond. The data and analysis required to assess
capability can be efficiently managed using various technology 4.4.1.2.3 Program Management. Program management, targe‐
components. ted mitigation, and special projects include specific programs
and projects identified during the planning analysis process.
4.4.1.1.2 Vulnerability and Risk Assessment. A vulnerability This can include special projects such as accreditation, the
and risk assessment is one method for evaluating the stakehold‐ identification of equipment failure trends, or incident patterns.
er’s liability. This assessment identifies potential loss and subse‐ Technology can aid in the execution, implementation, and
quent impacts to all stakeholders. Technology provides an management of various programs and targeted projects.
increased capacity to assess vulnerability and risk and how they
can be efficiently managed. 4.4.1.2.4 Training and Exercises. Training develops skill sets
needed to perform a function. Exercises are a practical applica‐
4.4.1.1.3 Inspections. Inspection efforts have the potential to tion of skill development. Training and exercises help ensure
produce substantial amounts of data. Technology can be used that staff have the skills to access the appropriate information
to more efficiently collect, update, and manage this data. Tech‐ from the appropriate technology when it is needed. Addition‐
nology can also be leveraged to distribute this important infor‐ ally, as technological tools are implemented in the agency,
mation to multiple stakeholders, thus increasing the efficiency much of the success of these tools will depend on proper train‐
of process and systems. Properly implemented, technology can ing.
increase safety and focus limited resources to fill the greatest
needs. 4.4.1.3 Response. Response is a multifaceted process that
ranges from single-resource to multijurisdictional incidents.
4.4.1.2 Preparedness. Preparedness is a continuous cycle of The proper application of technology provides a set of tools
planning, managing, training, equipping, exercising, evaluat‐ that can enhance incident response and responder safety.
ing, and improving activities. Preparedness ensures effective Effective data management leads to meaningful information
coordination and the enhancement of capabilities of for enhanced decision making. In particular, it is critical for
concerned organizations to prevent, protect against, respond decision making before, during, and after emergency response.
to, recover from, and mitigate the effects of all-hazard inci‐
dents. The proper application of technology can help effi‐ 4.4.1.3.1 Computer-Aided Dispatch (CAD). CAD is a suite of
ciently manage the implementation of preparedness efforts. hardware and software used to initiate public safety calls for
Technology can be a tool to provide timely, critical information serviceand dispatch and to maintain the status of responding
to stakeholders. resources in the field.

4.4.1.2.1 Pre-Incident Planning. A pre-incident planning proc‐ 4.4.1.3.2 In-Vehicle Applications. In-vehicle applications
ess involves responder familiarization to specific site informa‐ consist of hardware and software systems designed to send and
tion. This information is documented for use by all responders. receive information. This information is transmitted and
Typical site information might contain access points, automatic received to create efficiencies in the delivery of services estab‐
systems controls, enunciator panel locations, and travel routes lished in the organization's mission. These applications can
range from a simple preloaded set of tools and data to a sophis‐

2016 Edition
951-8 BUILDING AND UTILIZING DIGITAL INFORMATION

ticated system with live data feeds from remote systems. These visualized to assess specific problems and area trends. Reports
can include information from pre-incident planning databases and photographs of damage and debris can be linked to
with data on access and egress, water source, exposures, and specific geographic sites. Pre-incident imagery and GIS data
hazards as well as real-time automatic vehicle location (AVL) can be critical during damage assessment and assist during the
and data exchanges with other systems. reimbursement and recovery phase.
4.4.1.3.3 Mobile/Field Connectivity. Mobile devices allow 4.4.1.4.2 Infrastructure Restoration. After damage to critical
responders to send and receive information, assist in locating infrastructure is assessed, short- and long-term actions can be
an incident, assess the incident, implement a response, and determined for restoration efforts. Determining reconstruction
provide on-scene information regarding the incident status. priorities and costs can be enhanced by technology.
4.4.1.3.4* Search and Rescue (SAR). SAR is a multifaceted 4.4.1.4.3 Economic and Community Recovery. Utilization of
process that ranges from finding the lost (search) to bringing existing data and geospatial information enhances effective
them back to safety (rescue). Technology is an integral part of recovery of critical infrastructure, commerce, and displaced
search and rescue operations. Many of the datasets used across populations.
the planning, preparedness, response, and recovery phases
serve a critical role in SAR operations. 4.4.1.4.4 Environmental Stabilization. If an incident or
response activities result in a disturbed environment, damages
4.4.1.3.5 Evacuation, Shelter, and Mass Care. Technology can from such disturbances must be mitigated and the environ‐
support determination of suitable shelter locations and/or ment must be stabilized to reduce future damage. Mobile devi‐
mass care operations, including supporting materials and ces are often used to document and catalog needed
power. Geographic information can be utilized to select shelter rehabilitation/stabilization activities, while GIS software
locations and route evacuated populations appropriately. provides for visualization, prioritization, and progress tracking.
Spatially enabled models provide impact analyses to determine
4.4.1.3.6 Public Warning and Notification. Public warning and the activities necessary to reduce the risk of future damage.
notification consists of four primary methods: public warning
systems, telephony, media, and push notifications. Technology 4.4.1.4.5 Public Information. Information can be published in
has a significant impact on all four of these methods through many forms to facilitate transparency, encourage communica‐
faster relay, targeted audience, and control of the message. tions, and engage the public. Access to accurate information
about the status of an incident, shelters, and access to supplies
4.4.1.3.7 Command and Control. Effective and efficient and services can be managed, maintained, reported on, and
command and control requires accurate and timely informa‐ published in an enterprise database. Notification of ability to
tion to fulfill the command function. Depending on the return, return routes, damage assessments, and reporting
complexity and size of the incident, the information and data requirements (e.g., FEMA, insurance) can also be provided.
requirements can vary. Having access to essential information
(including, but not limited to, GIS data) provides an accurate 4.4.1.4.6 Analysis and Management of Recovery Efforts. The
picture of the event and supports critical command decision analysis of recovery efforts can integrate information using
making. dynamic data, including incident locations, unit tracking, traf‐
fic, weather, and other relevant data. The product of the analy‐
4.4.1.3.8* Incident/Resource Management. Incident sis can be queried based on various attributes including
command systems (ICS) organize personnel and resources to incident type, cause, time, units assigned, or other attributes.
manage an emergency. A well-designed information system With a geospatial framework, organizations can manage the
provides integrated support to the ICS components: finance, recovery efforts visually. This allows for incident analysis to be
logistics, operations, and planning. done quickly, displayed logically, and understood easily.
4.4.1.3.9* Multidisciplinary Coordination. Through the use of 4.5 Governance and Policy.
relational data, an integrated information system becomes an
ideal platform for enhancing situational awareness and 4.5.1 Governance Structure. There are many ways to organize
supporting collaborative decision making for events requiring a strategic technology plan governing structure. There is no
multi-agency and multijurisdictional coordination. universal governance model. Determining the governance
structure will be unique to each organization. The form of
4.4.1.3.10 Operational Intelligence. Technology synthesizes governance that will be most effective depends on many factors
information from different and often disparate systems and such as department size, resources, level of cooperation among
delivers it to various platforms. This intelligence provides stakeholders, existing system dynamics, level of regional coordi‐
crucial support for decision making throughout the various nation, and training. A technology needs assessment entity
functions of the organization. must have an authorizing document or charter. The gover‐
4.4.1.4 Recovery. The aim of the recovery phase is to restore nance structure that is selected must enable technology devel‐
the affected area to its previous state. Recovery efforts are opment, participant support, stakeholder representation, user
primarily concerned with actions that involve rebuilding involvement, and management commitment.
destroyed property, re-employment, and the repair of other 4.5.1.1 Governance Structure Scalability. The governance
essential infrastructure. Recovering from a disaster can be a model should evolve as the organization’s capabilities mature
lengthy process. Technology can make the recovery process and should be as scalable as the system, resources, and demand
faster, more efficient, and available for archiving. require. This can be different for different-sized systems. They
4.4.1.4.1 Damage Assessment and Debris Removal. Mobile can be as simple or as complex as needed, ranging from an
devices enable field workers to code debris and parcels with informal agreement with local community groups to large
descriptive attributes such as the type and degree of damage, quasi-governmental entities with formal joint power agree‐
time, and location. This data can be analyzed, queried, and

2016 Edition
 PROCESS 951-9

ments (JPAs) and memorandums of understanding (MOUs) needs to be able to expand or contract as requirements
among AHJs and across regions and states. change. Adherence to the requirements in NFPA 950 will allow
migration of valuable data as the system evolves, including
4.5.2 Policy. The governing body must establish clear policies legacy data.
concerning technology and data access. Policies should be
established that relate to both procedure and data manage‐ 4.7 Planning and Implementation of NFPA 950: An Overview
ment. of Implementing Technology and Technical Standards for Fire
and Emergency Service Organizations. The single most impor‐
4.5.2.1 Procedural Policy. The AHJs must have clearly defined tant factor in successfully implementing technology within any
and aligned access policies as described in Chapter 5. organization is proper project planning and management.
Procedural policies should address the following: Technical projects seldom fail due to technology; rather, their
failure results from lack of vision, poor planning, communica‐
(1) Procurement (infrastructure and software) tion failures, and imperfect execution. Technical solutions are
(2) Maintenance (infrastructure and software) often attempted without a clear understanding of how the final
(3) Security (see Section 5.6) system should work and are implemented without understand‐
(a) Security levels (user access) ing the impact on users. It is essential that implementation of
(b) Security system health emergency services information technology adheres to
(c) Internal use/misuse access policy NFPA 950, commencing with a thorough and well-guided
(d) Protection of sensitive information needs assessment. All technical solutions must be standards-
(4) Levels of IT support (when and who) based and interoperable. Overall, a needs assessment should
(5) Illegal or prohibited activities include the following steps:
(6) User application guidelines (including policy for standar‐ (1) Identify the problem.
dized training) (2) Identify all parties affected by the problem.
4.5.2.2 Data Policy. The AHJs must have clearly defined and (3) Assemble a representative group to guide the needs
aligned access policies as described in Chapter 5. Data policies assessment process.
should address the following: (4) Conduct start-up educational sessions.
(5) Interview potential participants and users.
(1) Integrity (see Section 5.1) (6) Synthesize results to create the optimal solution.
(2) Security (see Section 5.6) (7) Draft an implementation plan.
(3) Accuracy of data (see 5.8.1.2) (8) Provide initial training and prepare for ongoing train‐
(4) Data validation and verification of data exchange (see ing.
Section 5.8) (9) Implement the solution.
(5) Data timeliness (see 5.6.3) (10) Maintain and improve the system.
(6) Include spatial components with data (see 5.8.1)
(7) Provide metadata for all data (see 5.7.2) 4.7.1 Identify the Issue. To identify the scope of the issue, the
(8) Quality assurance and control (see 5.7.1) organization should review all data systems together rather
(9) Data exchange and compatibility (see Chapter 6) than individually. For example, a department might dispatch
(10) Shared data access policy (see Section 5.6) companies to incidents using CAD, use a separate system to
track responding or available companies (AVL), and use GPS
4.6* Interoperability and Scalability. To maximize the invest‐ for navigation on individual units — which might not work in
ment of financial and personnel resources, an understanding an interoperable manner. On the surface, integration of all
of interoperable and scalable solutions is imperative. three technologies should be simple as all three technologies
4.6.1 Interoperability. In general, interoperability refers to the share a spatial common base. A deeper analysis of the issue
ability of emergency responders to work together seamlessly reveals a myriad of challenges, such as multiple users, hard‐
without any special effort. Emergency responders need to share ware, and different information systems. Complexity can
vital data, information, and communications across disciplines increase exponentially if interoperability with neighboring
and jurisdictions to respond effectively. Data and format must departments and jurisdictions is required. By carefully defining
be compliant with Chapter 6 of NFPA 950 to be recognizable the issue and the desired outcome before commencing any
and exchangeable by all system users. This enables standar‐ action, managers can identify solutions and pitfalls for data
dized analytical methods and decision making that lead to integration.
comprehensive situational awareness. Five critical success 4.7.1.1 Using the Needs Assessment to Identify the Issue. The
elements that must be addressed to achieve an interoperable needs assessment process works best by identifying the issue(s),
data solution are as follows: using consensus to fully scope and create the requirements,
(1) Governance and defining and prioritizing the solution(s). Needs assessment
(2) Technology planning findings should result in a clear issue statement, a listing of
(3) Policies concerned parties, and a senior/executive level mandate for a
(4) Process/application development solution The outcome of a needs assessment is a set of standar‐
(5) Evaluation and feedback dized documents that describe what needs to be created. The
resulting system must be standards based and interoperable.
4.6.2* Scalability. To be successful, a technology plan must (See 4.8.3.)
incorporate the concept of scalability. Scalability implies that
the information system will accommodate expansion when 4.7.1.2 Issue Statement. After identification of the issue, an
requirements evolve, technology advances, and/or funding official issue statement should be created. The issue statement
becomes available. Historically, it has proven most effective to and the need for finding a solution should be issued as a
build an information system in manageable phases. The system department directive or mandate from the most senior execu‐

2016 Edition
951-10 BUILDING AND UTILIZING DIGITAL INFORMATION

tive level (e.g., chief of department or higher). This provides (1) Completion by a group through a single convening
clear, empowering guidance to seek a solution to the issue and authority:
ensures management buy-in to the solutions process. Failure to (a) A diversity of ideas
do so can result in conflicting guidance, competing priorities, (b) Ensure buy-in
and a fragmented or compartmentalized solution that minimi‐ (c) Quality assurance
zes return on investment. (2) Identify the users:
4.7.1.3 Role of Technology. Technology must be used to (a) Document workflow processes
improve efficiency — whether through improved response (b) Determine the level of technical competencies of
times, appropriate staffing requirements, improved emergency users
response outcomes, or other measurable results. Implemented (c) Identify what a final product as applied to the
technologies must be interoperable within the larger context of desired outcome looks like
fire and emergency service organization operations and (3) Identify the issue. Look at the work flow process of the
management as achieved through the use of standards such as target audience and identify where technology will serve
NFPA 950. Technology should never be implemented simply as a force multiplier or improve efficiency.
for technology’s sake. (4) Identify the desired outcome. A technological system of
4.7.2 Identification of the Parties Involved. The needs assess‐ some sort that meets the requirements established by the
ment process is completed through a group empowered by a needs assessment process and NFPA 950
single convening authority. The group should represent the (5) Identify technology elements that support desired
broadest possible base of potential stakeholders and include outcomes:
system users, managers, creators, and subject matter experts. (a) List how the technology will be used to solve a prob‐
This approach not only guarantees a diversity of ideas, but facil‐ lem, for example, computerized preplans
itates buy-in at all levels and promotes a high standard of qual‐ (b) Note what type of functionality is required within
ity throughout the development process, which mitigates “not each application to accomplish the goal, for exam‐
invented here” syndrome and creates a sense of ownership ple, a map that depicts the occupancies with
among all stakeholders. A charter should be established outlin‐ preplan information
ing the goals, objectives, and responsibilities of the group. (c) Data requirements:
4.7.2.1 Successful needs assessments are as inclusive as possible i. Data designs that meet NFPA 950
at the outset. Consideration should be given to fire fighters, ii. The data needed to support each application
telecommunicators, IT support personnel, and other potential and their inherent functions
contributors or collaborators. They can benefit not only an (d) Data maintenance procedures: Identify who, what,
individual fire and emergency service organization but also the when, where, and how each data element will be
larger community. created and maintained, including who financially
supports those activities
4.7.3 Conducting Start-Up Educational Sessions. As per the (e) Determine how it will be managed:
charter, initial needs assessment committee meetings should
serve to further revise the problem scope and educate partici‐ i. Fiscal responsibility (Who is funding the
pants about potential solutions. A determined effort should system and how?)
seek out case studies that document how similar problems were ii. Accountability (Who manages the people, the
resolved using a standards-based approach in other places. hardware, etc.?)
Where permissible, committee members should experience iii. Pitfalls and common mistakes (How do data
solutions firsthand. These case studies and experiences guide and people’s need drive the needs assessment
the development of an educational session about the problem process?)
and potential range of solutions for presentation to the larger 4.8.2 Conducting a Needs Assessment. The needs assessment
stakeholder audience by their representative committee should be conducted in the following manner:
members. Again, this approach facilitates maximum buy-in and
establishes a high level of competence and awareness among (1) A start-up meeting should be conducted to educate
stakeholder organizations. Education sessions represent an potential users about the present issue(s).
important opportunity for bi-directional information flow. (2) Potential users should be interviewed about their specific
Prudent committee members will capture comments from the job functions. All interviews should be documented in the
stakeholder audience. Educational sequencing as recommen‐ following standardized way:
ded in this guide for technology efforts is as follows: (1) Each job function, importance, and frequency
(1) Interviews with all potential participants and users should be captured.
(2) Synthesize results to create the optimal solution (2) The data required for each job function should be
(3) Draft an implementation plan identified.
(4) Training — and more training (3) Workflow should be documented.
(5) Putting the solution in play (4) Dataflow should be documented.
(6) Maintenance and improvement 4.8.3 Develop an Implementation Plan. An implementation
4.8* Technology Planning. plan should include the stated purpose as well as timelines and
budgets required to make the following components possible:
4.8.1 Needs Assessment. The needs assessment should take (1) Results of the needs assessment, which should cover the
into consideration the following elements: following:

2016 Edition
 DATA ADMINISTRATION 951-11

(a) A systematic look at how entities within an organi‐ 5.2.1.1 For the purposes of this guide, external data is defined
zation view and use data as data acquired from and/or maintained by an outside source.
(b) A description of enhanced communication among Once the data elements are integrated and maintained within
users of like data types internal information systems, it becomes internal data and
(c) Its use as a basis for future learning should follow the internal data criteria in accordance with
(2) A theoretical framework that describes in nontechnical Section 5.3. While the same criteria should apply to validating
terms how the ideal system works internal and external data, policy definitions that affect the
(3) A survey that reviews the following: distinction between the data types should include specific
(a) Internal and external data that will support all of language regarding the limitations and associated risks of using
the applications included in the plan external data sources.
(b) NFPA 950–compliant hardware and software 5.2.2 Additional Data. After review and analysis of technology
elements and combinations required to execute all and data needs, it might become evident that additional data is
the applications in the plan needed. This additional data will be included in the require‐
(4) Detailed database planning and design, which includes a ments of the new system.
translation of the theoretical model (how the ideal
system works in nontechnical terms) into the logical 5.2.3 Data Structure. Data can be stored in many formats and
model (technical terms) used in the application locations. To make use of the data, the data needs to be struc‐
(5) Application development, as follows: tured, compiled, and documented. The data is typically stored
in a relational or tabular structure. This structure is defined by
(a) Standardized data formats that will exist independ‐ the user. Consideration should be given to data exchange and
ently of the data sourced interoperability.
(b) Data independence in accordance with NFPA 950
(6) Acquisition, as follows: 5.3 Management/Organization. There should be an overall
(a) Database construction and assembly of all required data management plan for how data elements are used, shared,
data elements into a single database and exchanged. The data management plan should include
(b)* Acquisition and timing of hardware and software the following:
(7) Pilot study/benchmark test (1) Objectives of the plan, including minimizing data redun‐
(8) Review and modification of original plan dancy, entry errors, and creating interoperability
(9) Implementation, as follows: (2) A properly designed data structure
(a) Training (3) Standardized reporting
(b) Identification of gaps 5.4* Data Models and Schemas. A data model, data dictionary,
(10) Release of the new system to production and database schema are defined as follows:
(11) Maintenance (system continuous improvement cycle)
(1) Data model. A data model serves as the foundation of the
database. A data model indicates what information is
Chapter 5 Data Administration contained in the database, how the information will be
used, and how the items in the database will be related.
5.1 General. Once a clear vision, strategy, and technology plan (2) Data dictionary. A data dictionary standardizes the data
has been developed to implement the system, a data adminis‐ elements and is a centralized repository of information
tration plan will guide the actual administration of the data about data such as meaning, attributes, relationships,
environment. Chapter 5 frames the elements necessary for origin, usage, and format. The data dictionary specifies
successful data administration. Developing policies and guide‐ the details of the objects in the database. A data diction‐
lines for the effective administration of an information system ary is a useful tool for application developers and data‐
should be based upon need and is a function of the system base managers to share information.
architecture. Management of issues associated with data admin‐ (3) Database schema. A database schema is a blueprint of how
istration such as integration, security, replication, modification a database is constructed, which is based on the data
to, import and translation processes, and updates should be model and defines the objects that are included in the
included in the policy in accordance with Sections 5.1 and 5.2 database.
of NFPA 950.
5.5* Data Sources and Acquisition. Acquiring data requires
5.2 Data. Data elements are a fundamental key to success. consideration of how the data are going to be used. Issues of
Understanding what data elements are available and their accuracy, format, licensing, maintenance, and security are areas
format is imperative to a technology’s implementation success. that need careful consideration. There are many sources and
methods that can be leveraged to obtain or create data, includ‐
5.2.1 Internal and External Data. There is a distinction ing sources within the agency, from other agencies, from
between internal and external data. This distinction is based commercial data providers, or from data that the agency devel‐
upon the extent to which the data have been manipulated and ops. Requirements for data acquisition should be defined by
integrated into the agency’s information environment. These the specific uses and its associated applications.
distinctions will vary depending on the specific system architec‐
ture and environment, local and regional policies governing 5.5.1 Existing Data. Chances are that much of the data
data, and the choices of the strategic planning committee. needed to support the agency’s data requirements already exist
While the approach will vary based on these factors, the strate‐ in some format. The challenge comes in knowing where to
gic planning process should generate consensus on this distinc‐ look for the data.
tion and on the ownership of data. These decisions should be
cleary stated in the policies governing data administration. 5.5.2 Intra-Agency Data. The first step in determining data
sources and acquisition should be to investigate what data have

2016 Edition
951-12 BUILDING AND UTILIZING DIGITAL INFORMATION

been developed and are available from other local agencies. (1) Internal use: Access to data can be limited to select individ‐
Many local governments have invested in extensive data gather‐ uals who meet specific criteria. It can be categorized as
ing and collection and might already have many data elements “for official use only,” or “for internal use only.” It can be
that will be useful to supporting the functions of fire and emer‐ classified at various levels with appropriate legal penalties
gency service organizations. Because much of the data that are for dissemination.
used in the fire and emergency service organizations are spatial (2) External use: Access to data can be limited for public
in nature, determining if a local agency utilizes geospatial tech‐ dissemination information. These limitations should
nology is a key question to answer. Establishing a strong rela‐ consider privacy issues, HIPAA compliance, and other
tionship with information and geographic information data security, federal, state, and local regulations, laws,
professionals (e.g., police, tax assessors, public works) will be and ordinances. Through the Freedom of Information
key as the technological and data infrastructure is established, Act, the public reserves the right to request data from an
implemented, and maintained. organization.
5.5.3 Free or Open-Source Data. Many sources of data are 5.6.1.2 Types of Data. The ability to access information can be
publicly available (e.g., USGS, Geography Network) at low or limited to certain types of data. This includes access based on
no cost to the user. This data can come at varying degrees of field selection, criteria query, or predefined ranges.
accuracy and in many formats. As with any data, it must be veri‐
fied that it meets the requirements to support the anticipated 5.6.1.3 Conditional Access. Data can be released based on
functions. “need to know” or circumstantial criteria such as legal require‐
ments or emergency events.
5.5.4 External Agency Data. Other sources of data are govern‐
mental or quasi-governmental agencies, including county, state, 5.6.2 Security Features. Once it has been established that
or federal governmental agencies, associations of government, there are restrictions to the sharing of information, security
and regional authorities. Additional data might be available features must be put in place. Security features can include
from water, wastewater, or other utility districts. GIS professio‐ system security, data exchange physical security, and metadata
nal staff, if available, are a good resource for data that other and life cycle maintenance.
agencies have and might make available for your use. They 5.6.2.1 System Security. Information can be secured by physi‐
might already have agreements with these other agencies for cal parameters such as a lock, digital keycard, or security
the use of their data. token) or software parameters such as passwords and biomet‐
5.5.5 Commercially Available Data. Another source for many rics. Ideally, a two-factor authentication is recommended using
types of data is commercial data vendors. Many companies something known such as a password, and something one has,
collect, compile, and maintain a wide array of information. such as a digital security token.
This data can be purchased or licensed for use. 5.6.2.2 Data Exchange Physical Security. Data can be pushed
5.5.6 New Data. In each case, care must be taken to ensure out (all or selected fields) at one time or at periodic intervals,
that the accuracy and resolution is identified and consistent or pulled from either individual sources or a central data ware‐
among sources and is adequate for the designated purpose. house that is populated by contributing agencies. Once the
information is gathered, similar rules can apply as to with
5.5.6.1 Manually Generated Data. There are numerous meth‐ whom the information can be shared.
ods for creating data to populate databases and/or GIS, includ‐
ing manual digitizing or data entry, document or map 5.6.2.3 Metadata and Life Cycle Maintenance. Once data
scanning, and conversion of existing digital data. have reached the end of their useful life, much of the data will
become obsolete on their own. All open source/readily obtain‐
5.5.6.2 Data Collection. Data can be generated new from able information can be disposed of in the easiest manner;
sources such as raw GPS data or remotely sensed data such as however, many fields could retain sensitive information and will
aerial photography, or by compiling sets of data from various need to be disposed of by approved methods. Information can
sources like spreadsheets to create a new dataset. be archived, destroyed, or returned to the source.
5.5.6.3 Derived Data. New data can be created from existing 5.6.3 Audit/Review. Once the security and distribution rules
information in systems such as CAD, RMS, and AVL. New data have been established, it is important to review these policies
are generated from the output of these kinds of applications. periodically to ensure that they are being followed and that
Derived data also include the results of analysis such as drive they are still relevant.
time polygons and risk layers.
5.7 Maintenance. Proper data maintenance ensures accuracy,
5.6 Security. currency, and relevancy of information used to support the
workflows and functions of the organization.
5.6.1 Permissions (Access and Sharing). An organization has
the ability to subject its collected data to limitations related to 5.7.1 Quality Assurance and Quality Control. The importance
distribution, public dissemination, or disposition of the infor‐ of quality data cannot be overemphasized. Accurate data is crit‐
mation. Access to information can be limited to by role and/or ical to the analysis and reporting phase, which is the purpose
type of data. These information-sharing rules and management for collecting data. Where specific accuracy criteria exist, they
responsibilities should be documented in the standard operat‐ should be stated so that errors are known and bound. Data
ing procedures (SOPs) and periodically reviewed as required in resolution should be identified, since the accuracy can be only
NFPA 950. as good as the resolution of the data. The quality control func‐
tion will include sampling of data to determine if it is within
5.6.1.1 Role-Based Security. Role-based security can be divi‐ the required specifications. Report sampling should also be
ded into the following two use categories: performed to ensure that report calculations and other data

2016 Edition
 DATA ADMINISTRATION 951-13

manipulations are correct. The quality assurance procedure for use within fire and emergency service organizations when
includes validating the practice of collecting the data and opti‐ captured within 10 m of true location is of sufficient accuracy
mizing the process both from a data collection standpoint as for meeting the requirements of NFPA 950.
well as a data accuracy perspective. Ensuring data is not corrup‐
ted, truncated, or transposed in the process of collecting infor‐ 5.8.1.3 Geographic Coordinate System. A geographic coordi‐
mation is critical. nate system (which by definition is unprojected) represents the
surface of the earth in three-dimensional (round) geometry,
5.7.2 Metadata (Models, Dictionaries, and Schema). Metadata such as degrees, minutes, and seconds. A projected coordinate
describes the data that is collected, providing further details system, such as State Plane or Universal Transverse Mercator
about the information. Good metadata simplifies the mainte‐ (UTM) converts three-dimensional units into two dimensional
nance process by documenting the information that is collec‐ (flat) or planar units such as an X,Y pair. Using an unprojected
ted and stored, as well as describing how it is used. Metadata geographic coordinate system, like longitude and latitude, facil‐
includes a description of the database schema and it provides itates the exchange of spatial data between different software
information on the structure and content of the data being platforms, agencies, and systems.
collected. Metadata would include such characteristics as the
name, size, and data type, as well as field lengths, hierarchical 5.8.1.4* Symbology. Symbology is the set of conventions, rules,
information, and information about the data source. or encoding systems that define how geographic information is
graphically represented on a map. A characteristic of a map
5.7.3 Update Intervals/Methods (per Data Element/Type). feature can influence the size, color, and shape of the graphic
An up-to-date accurate address model can be used by many used. An attribute must exist for symbol class that depicts the
agencies to support many of their business functions. Success‐ geographic feature or resource type and capability using an
ful data model implementations should include a plan and appropriate symbol. Other specialized symbology should be
process to have contributing agencies regularly use and update clearly defined and agreed upon as part of the technology plan‐
the data. The update process will define parameters such as ning process established in Chapter 4.
how often the information is updated, how to handle conflicts
as well as archival instructions. Updates can vary by data type to 5.8.1.4.1 Emergency mapping symbology are specialized sets of
include partial updates, such as an individual layer rather than symbols used by various organizations when planning for or
the entire database. Update frequency varies with the type of responding to emergencies. These emergencies can be natu‐
data. Some fields can be updated as new information becomes rally caused (tsunami, earthquake, tornado, etc.) or human
available, while other fields can be updated on a monthly/ caused (rioting, terrorism, hijacking, etc.). Currently there is
quarterly or other periodic schedule. no international standard for emergency mapping symbology,
which means that various nations have created their own
5.7.4 Purge and Retention. As new information is updated, or national symbology set. Recognized and standardized symbol
as existing information becomes dated, a process is needed to sets help create a common operating picture (COP) for varied
define how long the data is stored and what to do with old data. organizations that have been brought together during a crisis
Is the data purged, archived, or kept on the system? How are or emergency. Symbols that are easy to identify with and easy to
conflicts handled as new data are obtained? What is the distribute are seen as key elements in creating maps that can be
medium for retention (e.g., disk, tape, on-line storage)? In used to reduce fatalities, injuries, or loss of property.
addition, there might be security constraints on the old infor‐
mation such that a simple deletion might not be adequate, and 5.8.1.5 Labeling. Labels are used to identify and quickly
additional processes or procedures might be needed (i.e., communicate information about various features.
return information to supplying agency, purge via approved 5.8.1.5.1 Having label attributes already available in the dataset
methodologies, or just archive old data and maintain for a simplifies the use of exchanged spatial data. If the dataset lacks
specified period of time). the attributes needed for labels, the user will have to create or
5.8 Data Exchange. calculate them to produce meaningful maps quickly. For exam‐
ple, to display the coordinates of a helicopter landing zone on
5.8.1 Spatial Data. Spatial data is data that has a spatial a map, the lat/long coordinates need to be recorded as attrib‐
component that references a place on earth. Spatial data utes. If they are not an attribute, they need to be calculated
enables a comprehensive framework for managing and sharing before they can be labeled. The minimum attributes required
intelligence through geographic awareness and data integra‐ for spatial data to be exchanged are listed in 5.3.1 of NFPA 950.
tion.
5.8.1.5.2* U.S. National Grid (USNG) is the national standard
5.8.1.1 Spatial Data Component. A spatial data component coordinate system established by the Federal Geographic Data
gives a relative or absolute location to data. It can be an address Committee and was recognized by FEMA in 2001. It is NFIRS-
or a geographic coordinate such as latitude and longitude or compliant and is a useful supplement to all addressing needs.
the U.S. National Grid (USNG). The added spatial component
allows the user of the data to establish where the location is in 5.8.2* Nonspatial Data. ASCII standard is an accepted format
relationship to the surface of the earth. for exchanging text data. Other commonly accepted nonspatial
file formats, such as JPG and WAV files, can be readily
5.8.1.2 Accuracy and Precision. Data collection devices and exchanged and used in their native formats. Using these
data services identify accuracy and precision levels in their industry-accepted standards facilitates the exchange of nonspa‐
specifications. Accuracy is defined as the relative difference tial data between different software platforms, agencies, and
between the actual and measured location. Precision is defined systems. The formats required for nonspatial data to be
as the repeatability of measurement within a given tolerance. It exchanged are listed in Chapter 5 of NFPA 950. These stand‐
is important to be aware of the specifications and limitations of ards have been identified for their universal acceptance and
the device in use. The overwhelming majority of data required use.

2016 Edition
951-14 BUILDING AND UTILIZING DIGITAL INFORMATION

5.8.3 TCP/IP Internet Protocol (IP). TCP/IP standard is an 6.4 Incident Typing Information.
accepted protocol for transmitting and receiving data. It is the
most common and incorporates acknowledgment of data trans‐ 6.4.1 NFPA 950 recognizes the National Fire Incident Report‐
fers. Using these industry-accepted standards facilitates the ing System (NFIRS) and the National EMS Information System
transfer and exchange of data. (NEMSIS) as the standard incident reporting systems currently
required by most U.S. states and territories. This framework
establishes a transferrable data set and as such meets the intent
Chapter 6 Data Sharing and Exchange of NFPA 950. This guide does not imply the use of any particu‐
lar software for recording incident data. This component of the
6.1 Introduction. This chapter sets forth the technical specifi‐ standards refers only to the typing standards within these
cations and business rules all fire and emergency service organ‐ frameworks.
izations should follow in creating an interoperable data sharing
and exchange environment. The technical specifications for 6.4.2 The “plus 1” append provides the local jurisdiction with
acquisition, display, and management are set forth in the previ‐ an opportunity to amend data for local use. This gives jurisdic‐
ous chapters. This chapter includes a description of the funda‐ tions the ability to review subsets of data for incident analysis.
mental data components that need to be exchangeable and 6.5 Text. ASCII is a universally accepted text standard.
specifies the format for each of those data components. This in Compliance with this protocol will enable ready transfer of text
no way limits the AHJ from creating local policies with addi‐ data using all of the standard data exchange methods specified
tional requirements, but for data exchange to be compliant, all herein.
components must, at a minimum, be in the formats specified
within NFPA 950. 6.6* CAD, RMS, CAD/CAD, CAD/RMS, and RMS/RMS
Exchange.
6.2 Addresses. This guide follows the protocols established by
the Federal Geographic Data Committee (FGDC) and main‐ 6.6.1 Design and Construction. Design and construction of
tained by the U.S. Census Bureau. This format is most often CAD/CAD, CAD/RMS, and RMS/RMS interfaces and applica‐
and easily recognized by geocoding engines. It is readily accep‐ tions should comply with all technical elements set forth in
ted and recognized by responders and the general public. Chapters 4, 5, and 6 of NFPA 950. The integration of all depart‐
Addressing in many jurisdictions has traditionally evolved from ment systems, including, but not limited to, CAD and RMS,
non-standards-based conventions that do not follow these must be considered at the design level. This guidance is inten‐
standards. This often creates challenges for agencies attempt‐ ded to be device and software agnostic. Specific to incident
ing to comply with nationally recognized standards such as response, this establishes the data framework required to
NFPA 950. Several approaches exist to resolve these discrepan‐ support this essential mission element.
cies. The jurisdiction should adopt a strategy that best fits the 6.6.2 Intent. The intent of this language is to emphasize the
data and resource environment within which they operate. The importance of a seamless flow of data. This will enable appro‐
most direct and short-term method for becoming compliant priate utilization of data assets throughout the organization
with NFPA 950 is to supplement the street address with a and into the entire public safety ecosystem. This environment
geographic coordinate (in accordance with NFPA 950, USNG, will enhance data accuracy and drive the ability to leverage data
or latitude and longitude). While this will not make an address resources for data driven decisions, comprehensive situational
data NFPA-compliant, it will allow the agency or department to awareness, and essential communications to all stakeholders in
deliver services on time in the right place without a significant the community. In short, unlocking data assets from propriet‐
change to the jurisdiction’s naming conventions. ary systems and structures will provide the data environment
6.3 Date and Time. NFPA 950 follows the most commonly that can support effective management.
recognized protocol currently in use in the United States. The 6.6.3 Dynamic Technology. NFPA 950 specifically calls out
committee recognizes that other date schemas are available CAD and RMS systems because these are the dominant nomen‐
and preferred by some agencies. This format is widely recog‐ clature for computer applications currently in use to perform
nized by civilian and governmental agencies. these functions at the time of this writing. NFPA 950 is written
6.3.1 Time Stamp. It is recommended that the time stamp be with the full understanding of a rapidly changing landscape.
recorded based on the incipient incident record time refer‐ The implicit intention of the committee in the writing of
ence. NFPA 950 was to set forth a standard that applies any informa‐
tion system designed to aid in the analysis, visualization, and
6.3.2 Decimal Time. Decimal time is a universal standard distribution of data intended to support the fire and emer‐
format that allows for numeric computations. gency service organization mission.
6.3.3 Time Reference. Time is referenced to the local time 6.6.4 Spatial Data Influence. When an emergency occurs,
zone and UTC. The committee acknowledges that storing the spatial data becomes an important backdrop to the entire
date twice is redundant but recognizes the inconsistency of sequence of events. From the moment a 911 call is received, an
time zone applications across regional boundaries. accurate incident location is the one attribute that ties together
6.3.4 Time Calibration. Time calibration is a critical compo‐ and sifts through all the other information available to support
nent of all incident record keeping because of the legal impli‐ a successful outcome. When that location is stored in a
cations associated with incident response. As such, calibration modern, standards-based, NFPA 950–compliant information
provides a legal framework for incident records. system, it provides the foundation to everything else that
follows:
(1) Call takers can confirm the accurate location of the inci‐
dent.

2016 Edition
 ANNEX A 951-15

(2) Station personnel can quickly reference the location. (b) Capture and reuse tradecraft (analytical models)
(3) Digital route maps with standard symbology can augment (2) Community risk and vulnerability analysis
the driver’s situational awareness. (a) Augment fire fighter safety
(4) Accurate hazard and hydrant locations support the scene (b) Community characteristics (physical and social)
size-up. (c) Protection priorities (critical infrastructure)
(5) Preplan layouts in scalable formats provide lifesaving (d) At-risk communities /neighborhoods
detail for search operations and attack strategies. (3) Preplanning and response analysis
(6) Incident Command assist data.
(a) Resource optimization (staffing, location alloca‐
6.6.5 Accuracy. Call location, initial incident description, tion)
routes, locations of responding vehicles, water sources, expo‐ (b) Response analysis (routing, service areas)
sures, hazards, access, and egress are all crucial, all about geog‐ (c) Demand for service (incident density maps)
raphy, and all need to be right. (4) Return on Investment (ROI) analysis
6.6.6 All location data needs to be accurate, consistent with its (a) Strategic /capital planning
intended use. (5) Actionable information and knowledge
(a) Command center
Annex A Explanatory Material (b) In field collaboration
(c) Partner organizations
Annex A is not a part of the recommendations of this NFPA docu‐
ment but is included for informational purposes only. This annex Benefits of such a system include the following:
contains explanatory material, numbered to correspond with the appli‐ (1) Improved understanding of the community and its land‐
cable text paragraphs. scape
A.1.1.1 The committee believes that in order for the data (2) Ability to prioritize and mitigate risk
exchange concept to become a reality, all components must be (3) Improved ability to preserve life and property and reduce
integrated into a comprehensive information management the consequences of emergencies
system. All system components in this context include (4) Improved understanding of agency capacity and perform‐
computer hardware, software, and procedures designed to ance
support the capture, management, manipulation, analysis, and (5) Quicker and more informed response
display of information. (6) Ability to develop a well-informed incident action plan
(7) Improved level of service
This integration is the key element the committee used in (8) Improved coordination
the development of NFPA 950 and this guide. By using this (9) Informed citizens
approach, the committee believes the environment allows for
improvements and development of comprehensive, integrated Data Management. To accomplish these kinds of analytics, fire
data and management systems that leads to improved incident and emergency service organizations need accurate informa‐
and organizational decision making. tion. Collecting, maintaining, and accessing data is central to
providing a data environment to support the full range of
A.1.1.2 Data sharing at all operational levels and components system requirements.
refers to the vertical and horizontal integration data exchange.
This enables the organization to share information seamlessly Systems that support effective data management include the
throughout. following:
(1) Management of relevant and authoritative content
Users seeking to implement NFPA 950 must be aware of the
multifaceted aspect of information systems. Constituent (a) Leverages a common information model
components include the personnel used to staff such systems (b) Access to online content
and the training involved to make them efficient, the hardware (c) Supports sharing across roles and jurisdictions
and software systems chosen, the well-documented processes (2) The ability to organize and discover information using a
that must be followed to achieve repeatable results, and the mission/role-based context
data stored or analyzed. While the scope of this guide is to (a) Mission (plan, respond, recover)
provide guidance and best practices about data capture, stor‐ (b) Stakeholders (internal and external)
age, manipulation/query, retrieval, and presentation, the focus (c) Workflow focus
is on doing such in an interoperable fashion. (d) Support for metadata
A.1.3.5 Comprehensive situational awareness is truly possible (3) Access and exchange of information through multiple
only when an effective information management strategy helps mediums
fire and emergency service organization personnel combine (a) Intelligent maps (analytical capability included in
appropriate data and analysis to answer the right questions. By the delivery of the map)
performing these analytics, expanded sets of information (b) Apps
become available to support all functions of the agency. (c) Services (geoprocessing, locator, etc.)
(4) The ability to collect information from multiple sources
Systems that support effective planning and analysis include
the following: (a) Supports multiple platforms (desktop, mobile, web)
(b) Supports integration with other information systems
(1) The transformation of current and historic data into (web services)
actionable information (c) Multiplatform real-time data collection
(a) Integration of information from disparate systems

2016 Edition
951-16 BUILDING AND UTILIZING DIGITAL INFORMATION

Benefits of such a system include the following: (5) Access anywhere, anytime, on any device
(1) Improved access to relevant information Benefits of such a system include the following:
(2) Improved protection, prevention, response, and recovery
(3) Informed and consistent decisions (1) Improved ability to manage and monitor operations
(4) Improved organizational efficiencies (2) Improved decision-making
(5) Reduced risk (3) Reduced risk
(6) Positive public perception (4) Ability to measure organizational performance
(5) Improved internal and external communications
Field Mobility. Increasingly data is supported on multiple devi‐ (6) Effective and efficient use of resources and investments
ces for many different forms of field support. Safe and effective (7) Safe and satisfied constituents
tactical response actually begins well before an emergency ever
happens through years of training, planning, and information Designing and building a standards-based integrated infor‐
gathering. mation management system will provide numerous benefits to
the agency. As well, designing and building a standards-based
Systems that support effective field mobility include the integrated information management system will provide
following: numerous benefits to partner organizations with shared goals
(1) The effective exchange of information to and from the and objectives.
field Implementing such a vision will provide the agency with
(a) Integrated as part of overall system more information, more sources of data to draw from, and
(b) Supports multiple mobile devices supplemental sources to aid in the decision making process.
(c) Works in connected or disconnected environments Shared and exchanged data enables smooth flow as the inci‐
(2) Effective and safe response dent escalates. Data accuracy also becomes critically important
in this process, because inaccurate or incomplete information
(a) Supports fire ground accountability can lead to poor decisions. These decisions can have an impact
(b) Supports an accurate and up-to-date COP on first responder safety and the public.
(c) Supports effective resource allocation
(d) Pre-plans A.3.2.1 Approved. The National Fire Protection Association
(e) Routing does not approve, inspect, or certify any installations, proce‐
(f) Hydrants /water sources dures, equipment, or materials; nor does it approve or evaluate
(g) Community assets /hazards (utility networks) testing laboratories. In determining the acceptability of installa‐
(h) Photo/floor plans tions, procedures, equipment, or materials, the authority
(3) Timely and accurate exchange of information and knowl‐ having jurisdiction may base acceptance on compliance with
edge NFPA or other appropriate standards. In the absence of such
(a) Command centers standards, said authority may require evidence of proper instal‐
(b) In field collaboration lation, procedure, or use. The authority having jurisdiction
(c) Mutual aid partners may also refer to the listings or labeling practices of an organi‐
zation that is concerned with product evaluations and is thus in
Benefits of such a system include the following: a position to determine compliance with appropriate standards
(1) Quick and more complete event assessment, ensuring for the current production of listed items.
timely and effective response A.3.2.2 Authority Having Jurisdiction (AHJ). The phrase
(2) Improved decision making “authority having jurisdiction,” or its acronym AHJ, is used in
(3) Better ability to track, manage, and prioritize field opera‐ NFPA documents in a broad manner, since jurisdictions and
tions and resources approval agencies vary, as do their responsibilities. Where
(4) More effective communication from and to the field public safety is primary, the authority having jurisdiction may
(5) Improved fire fighter safety be a federal, state, local, or other regional department or indi‐
(6) Improved public service vidual such as a fire chief; fire marshal; chief of a fire preven‐
Situational Awareness.Situational awareness systems include tion bureau, labor department, or health department; building
the following: official; electrical inspector; or others having statutory author‐
ity. For insurance purposes, an insurance inspection depart‐
(1) An up-to-date and accurate comprehensive view of opera‐ ment, rating bureau, or other insurance company
tions representative may be the authority having jurisdiction. In
(a) Supports multiple platforms many circumstances, the property owner or his or her designa‐
(b) Supports sharing across roles and jurisdictions ted agent assumes the role of the authority having jurisdiction;
(2) The ability to collect, organize, exchange, and analyze at government installations, the commanding officer or depart‐
authoritative information mental official may be the authority having jurisdiction.
(a) Can be leveraged before, during, and after emer‐ A.3.2.3 Guide. There are other standards-making bodies that
gency incidents define the word guide differently.
(b) Supports the ability to collect and leverage field
observations A.3.2.4 Listed. The means for identifying listed equipment
(3) Knowledge in an easy-to-understand, role-based interface may vary for each organization concerned with product evalua‐
(4) Access to authoritative information tion; some organizations do not recognize equipment as listed
unless it is also labeled. The authority having jurisdiction
(a) Base maps should utilize the system employed by the listing organization
(b) Operational information to identify a listed product.

2016 Edition
 ANNEX A 951-17

A.4.3 The basics needs assessment process required for mation and are designed to provide immediate and long-term
adequate design and performance are best found in Tomlin‐ benefits to people working on real GIS projects while support‐
son, Thinking About GIS, and Becker et al., GIS Development ing existing standards.
Guide.
Organizations representing the fire and emergency services
A.4.4.1.3.4 The MapSAR Group has developed a set of proto‐ have partnered with Esri to develop a national GIS data model
cols for using GIS to support wilderness search and rescue to support regular and disaster-related operations at the local
operations. These protocols can be extended to other types of level. This effort will complement and extend existing national
SAR events as well. Access to group resources is open and avail‐ geospatial data models. The leadership team for the project
able at no charge. To request an invitation to join the group includes representatives from the Metropolitan Fire Chief and
website go to www.mapsar.net Volunteer Fire Sections of the International Association of Fire
Chiefs (IAFC), The National Association of State Fire Marshals,
A.4.4.1.3.8 For information on GIS use within ICS, see the The National Alliance for Public Safety GIS (NA-PSG), and GIS
National Wildfire Coordinating Group (NWCG) publication specialists from the public and private sectors. The U.S. DOT
GIS Standard Operating Procedures on Incidents. Pipeline and Hazardous Materials Safety Administration
A.4.4.1.3.9 One example is a geospatial system that can be (PHMSA) provided initial leadership and project support.
utilized to display incidents, units, target hazards, and available The purpose of this project is to provide reference solutions
resources. Additionally, integrated information systems store and information models to assist fire departments in managing
valuable data that can contribute to data fusion centers, allow geospatial data and implementing solutions. The solutions are
robust spatial analysis, and improve resource allocation.. incorporated into the local government information model
A.4.6 Guidance with respect to specific hardware and software available at http://solutions.arcgis.com/local-government.
performance requirements and expectations can be found at A.5.5 Geospatial data can be found through a number of local,
this link: regional, and federal sources or can be created by a fire service
http://wiki.gis.com/wiki/index.php/System_Design_Strat‐ agency. External sources include internet map services (web
egies_Preface services) and internet portals. For guidance on assembling
local datasets, see Price, Fire Mapping: Building and Maintaining
Investment in personnel trained to use information systems, Datasets in ArcGIS, which describes a process and sources for
especially those with a geospatial context, represent a signifi‐ finding, assembling, and maintaining geospatial data.
cant investment of time and resources. The National Geospa‐
tial Advisory Committee provides sound advice for workforce A.5.8.1.4 Several standard symbology sets have been developed
development in support of efforts such as those proposed for emergency response and the fire service, including the
herein: following:

www.fgdc.gov/ngac/ngac-geospatial-workforce-development- (1) NFPA 170

paper-final.pdf www.nfpa.org/aboutthecodes/AboutTheCodes.asp?
A.4.6.2 For scaling across the digital and paper environments, DocNum=170
see Brooks and Swaminathan, “Integrating the Paper and Digi‐ (2) Federal Geographic Data Committee “Best Practices for
tal Environments for Crisis/Emergency Response: Lessons Local Government Geospatial Programs”:
Learned.” www.fgdc.gov/ngac/ngac-local-gov-gis-best-practices-
A.4.8 The Capability and Readiness Assessment Tool Prototype paper.pdf
prepared by the National Association for Public Safety GIS (3) Homeland Security Working Group Symbology Reference
(http://www.napsgfoundation.org/) provides a video and www.fgdc.gov/HSWG/index.html
general guidance about the inclusion of geospatial information (4) NAPSG Symbology Working Group:
for fire service information management and use. This tool is
available at: www.napsgfoundation.org/the-incident-map-
symbology-story
http://carat.napsgfoundation.org/index.cfm (5) NWCG ICS Symbology, pp. 50–52:
A.4.8.3(6)(b) Hardware and software should not be purchased www.nwcg.gov/pms/pubs/gstop.pdf
until late in the process to avoid depreciation.
A.5.8.1.5.2 The official USNG website is www.fgdc.gov/usng.
A.5.4 Managing and integrating disparate data streams is at the
core of NFPA 950. Environmental Systems Resource Institute A.5.8.2 To standardize the exchange of data, two established
(Esri) provides a solid geospatial data model in the work below. protocols are specified as XML for the transfer of nonspatial
data elements and GML for the transfer of geospatial data
A data model describes the thematic layers used in the appli‐ elements.
cation (e.g., hamburger stands, roads, and counties), their
spatial representation (e.g., point, line, or polygon), their A.6.6 Several Association of Public-Safety Communications
attributes, their integrity rules and relationships (e.g., counties Officials International (APCO) operational standards refer‐
must nest within states), their cartographic portrayal, and their ence CAD-to-CAD exchange: www.apcointl.org/standards
metadata requirements.
The goal of data models is to provide a practical template for
implementing GIS projects. Common data models are key to
making better decisions based on available geographic infor‐

2016 Edition
951-18 BUILDING AND UTILIZING DIGITAL INFORMATION

Annex B Informational References Tomlinson, R. Thinking About GIS, 4th edition, Redlands, CA:
Esri Press, 2011.
B.1 Referenced Publications. The documents or portions
thereof listed in this annex are referenced within the informa‐ B.2 Informational References. The following documents or
tional sections of this guide and are not advisory in nature portions thereof are listed here as informational resources
unless also listed in Chapter 2 for other reasons. only. They are not directly referenced in this guide.

B.1.1 NFPA Publications. National Fire Protection Associa‐ B.2.1 Other Publications.
tion, 1 Batterymarch Park, Quincy, MA 02169-7471. Sommer, S., and T. Wade, A to Z GIS: An Illustrated Dictionary
NFPA 170, Standard for Fire Safety and Emergency Symbols, 2015 of Geographic Information Systems, Redlands, CA: Esri Press, 2006.
edition. B.2.2 Websites.
NFPA 950, Standard for Data Development and Exchange for the
Fire Service, 2015 edition. Esri information models: http://solutions.arcgis.com/local-
government/fire-service
B.1.2 Other Publications.
The Federal Geographic Data Committee: www.fgdc.gov
Fire Protection Research Foundation Report: A Collection of
Geospatial Technological Approaches for Wildland and Wild‐ Standards for interoperability:www.opengeospatial.org/
land Urban Interface (WUI) Fire Events: standards

www.nfpa.org/research/fire-protection-research- Geospatial Intelligence Standards (GEOINT, NCGIS):

foundation/reports-and-proceedings/other-research-topics/ www1.nga.mil/ProductsServices/geointstandards/Pages/
geospatial-technological-approaches-for-wildland-and-wildland- default.aspx
urban-interface-fire-events International Organization for Standards (ISO) TC 211
Becker, P., et al., GIS Development Guide, Local Government Geographic Information/Geomatics: www.iso.org/iso/iso_cata‐
Technologies Services, State Archives and Records, New York logue/catalogue_tc/catalogue_tc_browse.htm?commid=54904
State, 1999. ISO Technical Committee 211 and its scope of work (PDF):
Brooks, T. J., and S. Swaminathan, “Integrating the Paper www.sbsm.gov.cn/pcgiap/bangalore/bangalore_isorep.pdf
and Digital Environments for Crisis/Emergency Response: North Carolina Parcel Data Draft Guideline (PDF):
Lessons Learned.” Proceedings of Global Spatial Data Infrastruc‐ www.nationalcad.org/data/documents/NC%20Guideline
tures 12. Singapore, Malaysia, 2011. %20Content%20Elements%20for%20Parcel%20Publishing-
Esri, GIS for the Fire Service, Redlands, CA: Esri Press, 2012. v5.pdf

NAPSG Foundation, GIS Geospatial Standard Operating Guid‐ Subcommittee for Cadastral Data: www.nationalcad.org
ance for Multi-Agency Coordination Centers 2.0, Washington, DC: USGS National Geospatial Program: www.usgs.gov/ngpo
NAPSG Foundation, 2011.
B.2.3 Sample Fire Technology Strategy. Henrico County Divi‐
www.napsgfoundation.org/resources. sion of Fire, Henrico, VA, has developed a technology strategy
NWCG, GIS Standard Operating Procedures on Incidents. PMS (plan) utilizing NFPA 950 and the Committee feels is notewor‐
#936/NFES #2809, National Interagency Fire Center, Boise, ID, thy as an example. It can be accessed at www.napsgfounda‐
2014. gis.nwcg.gov/pms/pubs/gstop.pdf tion.org/resources/nfpa-data-development-exchange-
standard/
Price, M., Fire Mapping: Building and Maintaining Datasets in
ArcGIS, Redlands, CA: Esri Press, 2012. www.esri.com/library/ B.3 References for Extracts in Informational Sections.
ebooks/fire-mapping.pdf. (Reserved)

2016 Edition
 INDEX 951-19

Index
Copyright © 2015 National Fire Protection Association. All Rights Reserved.

The copyright in this index is separate and distinct from the copyright in the document that it indexes. The licensing provi‐
sions set forth for the document are not applicable to this index. This index may not be reproduced in whole or in part by any
means without the express written permission of NFPA.

-A- Data Exchange Physical Security, 5.6.2.2

Administration, Chap. 1 Metadata and Life Cycle Maintenance, 5.6.2.3
Application, 1.3 System Security, 5.6.2.1
Purpose, 1.2 Data Sharing and Exchange, Chap. 6
Scope, 1.1 Addresses, 6.2
Approved CAD, RMS, CAD/CAD, CAD/RMS, and RMS/RMS
Exchange, 6.6, A.6.6
Definition, 3.2.1
Accuracy, 6.6.5
Authority Having Jurisdiction (AHJ)
Design and Construction, 6.6.1
Definition, 3.2.2
Dynamic Technology, 6.6.3
-D- Intent, 6.6.2
Data Administration, Chap. 5 Spatial Data Influence, 6.6.4
Data, 5.2 Date and Time, 6.3
Additional Data, 5.2.2 Decimal Time, 6.3.2
Data Structure, 5.2.3 Time Calibration, 6.3.4
Internal and External Data, 5.2.1 Time Reference, 6.3.3
Data Exchange, 5.8 Time Stamp, 6.3.1
Nonspatial Data, 5.8.2, A.5.8.2 Incident Typing Information, 6.4
Spatial Data, 5.8.1 Introduction, 6.1
Accuracy and Precision, 5.8.1.2 Text, 6.5
Geographic Coordinate System, 5.8.1.3 Definitions, Chap. 3
Labeling, 5.8.1.5
-E-
Spatial Data Component, 5.8.1.1
Symbology, 5.8.1.4, A.5.8.1.4 Explanatory Material, Annex A
TCP/IP Internet Protocol (IP), 5.8.3
-G-
Data Models and Schemas, 5.4, A.5.4
Guide
Data Sources and Acquisition, 5.5, A.5.5
Definition, 3.2.3
Commercially Available Data, 5.5.5
Existing Data, 5.5.1 -I-
External Agency Data, 5.5.4
Information System/Geographic Information System (GIS)
Free or Open-Source Data, 5.5.3
Definition, 3.3.1
Intra-Agency Data, 5.5.2
Informational References, Annex B
New Data, 5.5.6
Interoperability
Data Collection, 5.5.6.2
Definition, 3.3.2
Derived Data, 5.5.6.3
Manually Generated Data, 5.5.6.1 -L-
General, 5.1
Listed
Maintenance, 5.7
Definition, 3.2.4
Metadata (Models, Dictionaries, and Schema), 5.7.2
Purge and Retention, 5.7.4 -P-
Quality Assurance and Quality Control, 5.7.1 Process, Chap. 4
Update Intervals/Methods (per Data Element/Type), 5.7.3 General, 4.1
Management/Organization, 5.3 Governance and Policy, 4.5
Security, 5.6 Governance Structure, 4.5.1
Audit/Review, 5.6.3 Governance Structure Scalability, 4.5.1.1
Permissions (Access and Sharing), 5.6.1 Policy, 4.5.2
Conditional Access, 5.6.1.3 Data Policy, 4.5.2.2
Role-Based Security, 5.6.1.1 Procedural Policy, 4.5.2.1
Types of Data, 5.6.1.2 Interoperability and Scalability, 4.6, A.4.6
Security Features, 5.6.2

2016 Edition
951-20 BUILDING AND UTILIZING DIGITAL INFORMATION

Interoperability, 4.6.1 Conducting Start-Up Educational Sessions, 4.7.3

Scalability, 4.6.2, A.4.6.2 Identification of the Parties Involved, 4.7.2
Mission Requirements and User Needs, 4.4 Identify the Issue, 4.7.1
List of Workflows, 4.4.1 Issue Statement, 4.7.1.2
Planning, 4.4.1.1 Role of Technology, 4.7.1.3
Capability Assessment, 4.4.1.1.1 Using the Needs Assessment to Identify the Issue, 4.7.1.1
Inspections, 4.4.1.1.3 Technology Planning, 4.8, A.4.8
Vulnerability and Risk Assessment, 4.4.1.1.2 Conducting a Needs Assessment, 4.8.2
Preparedness, 4.4.1.2 Develop an Implementation Plan, 4.8.3
Pre-Incident Planning, 4.4.1.2.1 Needs Assessment, 4.8.1
Program Management, 4.4.1.2.3 Technology Strategic Planning, 4.3, A.4.3
Resource Deployment, 4.4.1.2.2 Technology Strategic Visioning, 4.2
Training and Exercises, 4.4.1.2.4
Recovery, 4.4.1.4 -R-
Analysis and Management of Recovery Referenced Publications, Chap. 2
Efforts, 4.4.1.4.6 Response
Damage Assessment and Debris Removal, 4.4.1.4.1 Definition, 3.3.3
Economic and Community Recovery, 4.4.1.4.3
Environmental Stabilization, 4.4.1.4.4 -S-
Infrastructure Restoration, 4.4.1.4.2 Scalability
Public Information, 4.4.1.4.5 Definition, 3.3.4
Response, 4.4.1.3 Scalable
Command and Control, 4.4.1.3.7 Definition, 3.3.5
Computer-Aided Dispatch (CAD), 4.4.1.3.1 Standard
Evacuation, Shelter, and Mass Care, 4.4.1.3.5 Definition, 3.2.5
In-Vehicle Applications, 4.4.1.3.2
Incident/Resource Management, 4.4.1.3.8, A.4.4.1.3.8 -T-
Mobile/Field Connectivity, 4.4.1.3.3 Text Data
Multidisciplinary Coordination, 4.4.1.3.9, A.4.4.1.3.9 Definition, 3.3.6
Operational Intelligence, 4.4.1.3.10
Public Warning and Notification, 4.4.1.3.6 -W-
Search and Rescue (SAR), 4.4.1.3.4, A.4.4.1.3.4 Workflow
Planning and Implementation of NFPA 950: An Overview of Definition, 3.3.7
Implementing Technology and Technical Standards
for Fire and Emergency Service Organizations, 4.7

2016 Edition
 Sequence of Events for the Standards Committee Membership
Development Process Classifications1,2,3,4
As soon as the current edition is published, a Standard is open The following classifications apply to Committee mem-
for Public Input bers and represent their principal interest in the activity
of the Committee.
Step 1: Input Stage 1. M Manufacturer: A representative of a maker or
• Input accepted from the public or other committees marketer of a product, assembly, or system, or
for consideration to develop the First Draft portion thereof, that is affected by the standard.
• Committee holds First Draft Meeting to revise Stan- 2. U User: A representative of an entity that is subject
dard (23 weeks) to the provisions of the standard or that volun-
Committee(s) with Correlating Committee (10 weeks) tarily uses the standard.
• Committee ballots on First Draft (12 weeks) 3. IM Installer/Maintainer: A representative of an en-
Committee(s) with Correlating Committee (11 weeks) tity that is in the business of installing or main-
• Correlating Committee First Draft Meeting (9 weeks) taining a product, assembly, or system affected
• Correlating Committee ballots on First Draft (5 weeks) by the standard.
• First Draft Report posted 4. L Labor: A labor representative or employee con-
cerned with safety in the workplace.
Step 2: Comment Stage 5. RT Applied Research/Testing Laboratory: A representa-
tive of an independent testing laboratory or in-
• Public Comments accepted on First Draft (10 weeks)
dependent applied research organization that
• If Standard does not receive Public Comments and the
promulgates and/or enforces standards.
Committee does not wish to further revise the Stan-
6. E Enforcing Authority: A representative of an agen-
dard, the Standard becomes a Consent Standard and
cy or an organization that promulgates and/or
is sent directly to the Standards Council for issuance
enforces standards.
• Committee holds Second Draft Meeting (21 weeks)
7. I Insurance: A representative of an insurance
Committee(s) with Correlating Committee (7 weeks)
company, broker, agent, bureau, or inspection
• Committee ballots on Second Draft (11 weeks)
agency.
Committee(s) with Correlating Committee (10 weeks)
8. C Consumer: A person who is or represents the ul-
• Correlating Committee First Draft Meeting (9 weeks)
timate purchaser of a product, system, or ser-
• Correlating Committee ballots on First Draft (8 weeks)
vice affected by the standard, but who is not
• Second Draft Report posted
included in (2).
9. SE Special Expert: A person not representing (1)
Step 3: Association Technical Meeting
through (8) and who has special expertise in
• Notice of Intent to Make a Motion (NITMAM) ac- the scope of the standard or portion thereof.
cepted (5 weeks)
• NITMAMs are reviewed and valid motions are certified NOTE 1: “Standard” connotes code, standard, recom-
for presentation at the Association Technical Meeting mended practice, or guide.
• Consent Standard bypasses Association Technical NOTE 2: A representative includes an employee.
Meeting and proceeds directly to the Standards Coun-
NOTE 3: While these classifications will be used by the
cil for issuance
Standards Council to achieve a balance for Technical
• NFPA membership meets each June at the Association
Committees, the Standards Council may determine that
Technical Meeting and acts on Standards with “Certi-
new classifications of member or unique interests need
fied Amending Motions” (certified NITMAMs)
representation in order to foster the best possible Com-
• Committee(s) and Panel(s) vote on any successful
mittee deliberations on any project. In this connection,
amendments to the Technical Committee Reports
the Standards Council may make such appointments
made by the NFPA membership at the Association
as it deems appropriate in the public interest, such as
Technical Meeting
the classification of “Utilities” in the National Electrical
Step 4: Council Appeals and Issuance Code Committee.
of Standard NOTE 4: Representatives of subsidiaries of any group
are generally considered to have the same classification
• Notification of intent to file an appeal to the Standards as the parent organization.
Council on Association action must be filed within 20
days of the Association Technical Meeting
• Standards Council decides, based on all evidence,
whether or not to issue the Standards or to take other
action

12/15-A
Submitting Public Input / Public Comment through the Electronic Submission System (e-Submission):
As soon as the current edition is published, a Standard is open for Public Input.

Before accessing the e-Submission System, you must first sign-in at www.NFPA.org. Note: You will be asked to sign-in or
create a free online account with NFPA before using this system:

a. Click in the gray Sign In box on the upper left side of the page. Once signed-in, you will see a red “Welcome”
message in the top right corner.
b. Under the Codes and Standards heading, Click on the Document Information pages (List of Codes & Standards),
and then select your document from the list or use one of the search features in the upper right gray box.

OR

a. Go directly to your specific document page by typing the convenient short link of www.nfpa.org/document#,
(Example: NFPA 921 would be www.nfpa.org/921) Click in the gray Sign In box on the upper left side of the page.
Once signed in, you will see a red “Welcome” message in the top right corner.

To begin your Public Input, select the link The next edition of this standard is now open for Public Input (formally
“proposals”) located on the Document Information tab, the Next Edition tab, or the right-hand Navigation bar. Alternatively,
the Next Edition tab includes a link to Submit Public Input online

At this point, the NFPA Standards Development Site will open showing details for t he document you have selected. This
“Document Home” page site includes an explanatory introduction, information on the current document phase and closing
date, a left-hand navigation panel that includes useful links, a document Table of Contents, and icons at the top you can click
for Help when using the site. The Help icons and navigation panel will be visible except when you are actually in the process
of creating a Public Input.

Once the First Draft Report becomes available there is a Public comment period during which anyone may submit a Public
Comment on the First Draft. Any objections or further related changes to the content of the First Draft must be submitted at
the Comment stage.

To submit a Public Comment you may access the e-Submission System utilizing the same steps as previous explained for the
submission of Public Input.

For further information on submitting public input and public comments, go to: http://www.nfpa.org/publicinput

Other Resources available on the Doc Info Pages

Document information tab: Research current and previous edition information on a Standard

Next edition tab: Follow the committee’s progress in the processing of a Standard in its next revision cycle.

Technical committee tab: View current committee member rosters or apply to a committee

Technical questions tab: For members and Public Sector Officials/AHJs to submit questions about codes and standards to
NFPA staff. Our Technical Questions Service provides a convenient way to receive timely and consistent technical assistance
when you need to know more about NFPA codes and standards relevant to your work. Responses are provided by NFPA staff
on an informal basis.

Products/training tab: List of NFPA’s publications and training available for purchase.

Community tab: Information and discussions about a Standard

12/15-B
 Information on the NFPA Standards Development Process
I. Applicable Regulations. The primary rules governing the processing of NFPA standards (codes, standards, recommended practices, and
guides) are the NFPA Regulations Governing the Development of NFPA Standards (Regs). Other applicable rules include NFPA Bylaws,
NFPA Technical Meeting Convention Rules, NFPA Guide for the Conduct of Participants in the NFPA Standards Development Process,
and the NFPA Regulations Governing Petitions to the Board of Directors from Decisions of the Standards Council. Most of these rules and
regulations are contained in the NFPA Standards Directory. For copies of the Directory, contact Codes and Standards Administration at
NFPA Headquarters; all these documents are also available on the NFPA website at “www.nfpa.org.”

The following is general information on the NFPA process. All participants, however, should refer to the actual rules and regulations for a
full understanding of this process and for the criteria that govern participation.

II. Technical Committee Report. The Technical Committee Report is defined as “the Report of the responsible Committee(s), in
accordance with the Regulations, in preparation of a new or revised NFPA Standard.” The Technical Committee Report is in two parts and
consists of the First Draft Report and the Second Draft Report. (See Regs at 1.4)

III. Step 1: First Draft Report. The First Draft Report is defined as “Part one of the Technical Committee Report, which documents the
Input Stage.” The First Draft Report consists of the First Draft, Public Input, Committee Input, Committee and Correlating Committee
Statements, Correlating Input, Correlating Notes, and Ballot Statements. (See Regs at 4.2.5.2 and Section 4.3) Any objection to an action
in the First Draft Report must be raised through the filing of an appropriate Comment for consideration in the Second Draft Report or the
objection will be considered resolved. [See Regs at 4.3.1(b)]

IV. Step 2: Second Draft Report. The Second Draft Report is defined as “Part two of the Technical Committee Report, which documents
the Comment Stage." The Second Draft Report consists of the Second Draft, Public Comments with corresponding Committee Actions
and Committee Statements, Correlating Notes and their respective Committee Statements, Committee Comments, Correlating Revisions,
and Ballot Statements. (See Regs at Section 4.2.5.2 and 4.4) The First Draft Report and the Second Draft Report together constitute the
Technical Committee Report. Any outstanding objection following the Second Draft Report must be raised through an appropriate
Amending Motion at the Association Technical Meeting or the objection will be considered resolved. [See Regs at 4.4.1(b)]

V. Step 3a: Action at Association Technical Meeting. Following the publication of the Second Draft Report, there is a period during
which those wishing to make proper Amending Motions on the Technical Committee Reports must signal their intention by submitting a
Notice of Intent to Make a Motion. (See Regs at 4.5.2) Standards that receive notice of proper Amending Motions (Certified Amending
Motions) will be presented for action at the annual June Association Technical Meeting. At the meeting, the NFPA membership can
consider and act on these Certified Amending Motions as well as Follow-up Amending Motions, that is, motions that become necessary as
a result of a previous successful Amending Motion. (See 4.5.3.2 through 4.5.3.6 and Table1, Columns 1-3 of Regs for a summary of the
available Amending Motions and who may make them.) Any outstanding objection following action at an Association Technical Meeting
(and any further Technical Committee consideration following successful Amending Motions, see Regs at 4.5.3.7 through 4.6.5.3) must be
raised through an appeal to the Standards Council or it will be considered to be resolved.

VI. Step 3b: Documents Forwarded Directly to the Council. Where no Notice of Intent to Make a Motion (NITMAM) is received and
certified in accordance with the Technical Meeting Convention Rules, the standard is forwarded directly to the Standards Council for action
on issuance. Objections are deemed to be resolved for these documents. (See Regs at 4.5.2.5)

VII. Step 4a: Council Appeals. Anyone can appeal to the Standards Council concerning procedural or substantive matters related to the
development, content, or issuance of any document of the Association or on matters within the purview of the authority of the Council, as
established by the Bylaws and as determined by the Board of Directors. Such appeals must be in written form and filed with the Secretary
of the Standards Council (See Regs at 1.6). Time constraints for filing an appeal must be in accordance with 1.6.2 of the Regs. Objections
are deemed to be resolved if not pursued at this level.

VIII. Step 4b: Document Issuance. The Standards Council is the issuer of all documents (see Article 8 of Bylaws). The Council acts on
the issuance of a document presented for action at an Association Technical Meeting within 75 days from the date of the recommendation
from the Association Technical Meeting, unless this period is extended by the Council (See Regs at 4.7.2). For documents forwarded
directly to the Standards Council, the Council acts on the issuance of the document at its next scheduled meeting, or at such other meeting
as the Council may determine (See Regs at 4.5.2.5 and 4.7.4).

IX. Petitions to the Board of Directors. The Standards Council has been delegated the responsibility for the administration of the codes
and standards development process and the issuance of documents. However, where extraordinary circumstances requiring the intervention
of the Board of Directors exist, the Board of Directors may take any action necessary to fulfill its obligations to preserve the integrity of the
codes and standards development process and to protect the interests of the Association. The rules for petitioning the Board of Directors
can be found in the Regulations Governing Petitions to the Board of Directors from Decisions of the Standards Council and in 1.7 of the
Regs.

X. For More Information. The program for the Association Technical Meeting (as well as the NFPA website as information becomes
available) should be consulted for the date on which each report scheduled for consideration at the meeting will be presented. For copies of
the First Draft Report and Second Draft Report as well as more information on NFPA rules and for up-to-date information on schedules
and deadlines for processing NFPA documents, check the NFPA website (www.nfpa.org/aboutthecodes) or contact NFPA Codes &
Standards Administration at (617) 984-7246.
12/15-C
 Are you IN?
NFPA Xchange TM

Our online community lets you connect with NFPA® technical staff, network
with professionals worldwide, and explore content on everything from fire
protection systems, electrical, building and life safety, emergency response, and
more. Plus, you can:

SHARE ideas
ASK questions
POST discussions
Have a question about the code or standard you’re reading right now? NFPA
Members enjoy exclusive access to the ‘Members Only’ section on NFPA
Xchange, where you can submit technical standards questions,* as well as
search questions submitted by others and view the answers!

JOIN NFPA Xchange TODAY—IT’S FREE AND EASY!

1 2 3

Go online Enter YOU’RE IN!

NFPA.ORG/Xchange YOUR NFPA ID# OR
EMAIL ADDRESS AND
PASSWORD

INformation. INtelligence. Get INvolved.

*For the full terms of use, please visit nfpa.org/standard_items/terms-of-use#xchange. NFPA® is a registered
trademark of the National Fire Protection Association, Quincy, MA 02169

12/15-D