Last fall, NFPA sponsored its inaugural Responder Forum in Indianapolis. Using information that was shared at the Forum, as well as follow up research that Forum attendees conducted in the ensuing months, three whitepapers were developed so that others can learn about three emerging topics:
- Unmanned Aerial Systems
- Data and the Fire Service
- Civil Unrest
The topic of SMART Firefighting/Unmanned Aerial Systems was explored by one work group with a focus on the challenges that agencies face in deploying this technology. Another team looked at Data in the Fire Service and recommended ways to improve the collection, analysis and use of data. A third group examined the Fire Service Response to Civil Unrest, and assisted in the development of a sample standard operating procedure that was recently included in a white paper endorsed by the Urban Fire Forum. These three white papers and SOP serve as a record of Responder Forum discussions and are available for use by NFPA technical committees and others.
The NFPA Responder Forum brings together representatives from 13 key fire organizations, subject matter experts, industry leaders, and NFPA staff to address emerging issues. It was established to help build a bridge from research into practice by highlighting new technologies that the fire service must understand. Forum discussions inform the fire service community, research efforts, and NFPA codes and standards – and encourage forward-thinking among different fire disciplines.
The 2016 Forum will take place November 7-9 in Charlotte, North Carolina. On November 7, at 10:15 AM (EST), Casey Grant of the Fire Protection Research Foundation will present, The Future Firefighter, a one-hour presentation on smart firefighting, which will be live-streamed. Register here to view the live-stream.
Learn how the Responder Forum is Impacting the Future of the Fire Service . The three white papers and more information on the Responder Forum can be found here. To discuss first responder ideas and issues, please contact me at email@example.com.