An organization looking to leverage crowdsourced information in their operations may have trouble identifying the first step to consuming this data. In this section we will assist you in building a framework that allows for the integrated use of both traditional and crowdsourced data. While the focus of this toolkit is on crowdsourced data, the steps below should also help you organize your traditional data and improve situational awareness in your organization. This section covers:
Community Lifelines are a construct for outcomes-based stabilization efforts. Simply, A lifeline enables the continuous operation of government functions and critical business, and is essential to human health and safety or economic security.
Each Community Lifeline contains two to six "components" which drill down to the Essential Elements of Information (EEIs) necessary for each.
FEMA has developed a Community Lifelines Implementation Toolkit to assist organizations in leveraging this framework. The Community Lifelines concept can assist your organization in organizing crowdsourced and traditional data to better inform overall incident situational awareness.
The Community Lifelines construct helps the emergency manager organize their information collection and answer the overwhelming questions of:
Information is gathered through the use of Essential Elements of Information (EEIs). EEIs are key pieces of information an official needs to inform decision making. You typically can identify the EEIs for your organization will be before they are needed. When stakeholders come together and determine what information they will need to make good decisions in an emergency, the resulting list of information needs are known as EEIs.
If your organization has not already identified EEIs, the FEMA Community Lifelines Implementation Toolkit has provided a list of recommended EEIs to start with. Some of these EEIs may not be applicable to your organization and you may also identify additional EEIs unique to your operations. This resource is meant to get you started in the development of your list of EEIs. Working to develop EEIs collaboratively will identify common EEIs which may already be collected by your partners.
FEMA has developed an Information Collection Plan process to determine the possible data sources and collection schedule to inform the Essential Elements of Informations (EEIs) and situational awareness products for decision makers. This template may be a helpful resource and logical next step after determining your organization's EEIs. The template is meant to be continuously updated throughout the incident lifecycle as sources change. Like the Community Lifelines & Essential Elements of Information concepts, an Information Collection Plan extends far beyond crowdsourced information but is a helpful resource prior to embarking on a crowdsourcing program. NOTE: Much of the language in this template is FEMA-centric. It is recommended you work with your team to customize this tool.
If your organization has organized its information collection process, and determined the Essential Elements of Information (EEIs) necessary to make decisions, you can move on to developing the format for data collection.
It is not uncommon for organizations to collect information during a crisis using a completely different format from a neighboring jurisdiction or partner agency. The middle of a crisis is not the time to try and make a significant change to how you are collecting data. If working with a Digital Volunteer Network or Tech Sector partner, determine if they can provide applicable crowdsourced data in a format that aligns with your traditional sources. After the incident, it will be important to determine if a data standard can be leveraged to collect data on your EEIs.
Spending some time with your stakeholders in advance to determine the approach for data collection, data format, data attributes, and data sharing methods will save you considerable time converting both crowdsourced and traditional data sources to a format that your organization will be able to use. A significant amount of time is spent during each incident working to deduplicate data entries and crosswalking data fields between various sources. There are a few approaches that can assist with advanced planning to reduce this unnecessary process.
To better integrate the symbology of crowdsourced data with traditional data, organizations can leverage the NAPSG Symbol Library Tool. The NAPSG Foundation has been working with the US Department of Homeland Security (DHS) to bridge gaps in incident symbols and the supporting frameworks required to achieve a common language for communicating incident information. They have been developing a consistent incident symbology framework, guideline, and symbol set for use at the incident level on maps and in GIS applications. The NAPSG Symbol Library Tool can be accessed here.