1 / 12

P rescribed F ire I ncident R eporting S ystem ( PFIRS )

PFIRS is a structured database and web system facilitating communication among land managers, burners, and regulators for evaluating burn decisions. It ensures transparency and public access to pertinent information. The database includes smoke management, forecast, and burn emissions data. Hardware and database setup details are provided, along with roles of key stakeholders like land managers, air districts, and the ARB. A timeline outlines the system's development and testing phases before the launch. For more information, contact Jeff Lindberg at jlindber@arb.ca.gov or 916.322.2832.

ebogart
Download Presentation

P rescribed F ire I ncident R eporting S ystem ( PFIRS )

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Prescribed Fire Incident Reporting System (PFIRS) Jeff Lindberg California Air Resources Board IASC November 14, 2005

  2. What is PFIRS? • Structured database & web pages • Interface between land managers, burners & regulators • Assists in gathering, evaluating, and communicating burn decisions • Provides all parties access to information • Presents Summary Information to the Public

  3. What is PFIRS? (continued) • The database will contain: • Smoke management planning information • Forecast & approval information • Burn emissions information • Burn follow-up information

  4. Hardware Setup • Successfully installed new OS on server • Mandrakelinux 10.0 • Successfully installed database software • Postgress SQL • Successfully installed Scripting Language • PHP • All products open source (free)

  5. Database Logic & Structure • Project Level Information • Project Name, General Location, “Owning” Burner Unit • Smoke Management Plan • Component Level Information • Burn Unit Name, Fuel Loading and Type • Air District(s) Identified (registration) • Burn Requests and Approvals California Air Resources Board

  6. Land Manager Role • Land Managers Fill out SMP Information: • Location, Smoke & Met. Monitoring, Smoke Contingency Measures, Public Contact Methods, Alternatives Used, etc. • Burn Unit Info (Components) • Fuel Loading, Acreage, Cover Type • Used as FOFEM5 Inputs for Emission Calculations • Post Burn Follow-up California Air Resources Board

  7. Air District Role • Air Districts Approve Burning • Evaluate & Approve SMPs • Approval From All Air Districts with Project Acreage Needed Prior to Ignition Request • Approve Ignitions • Air Districts can only approve acreage within their boundaries • Permission Based • Provide CB-3 Information – ARB or Authorized Districts • Permission Based

  8. ARB Role • Gate keeper • Approve Initial User Accounts • Once an Air District or Burner Unit has an “admin” account all new user accounts can be approved locally or by ARB • Provide assistance to Air Districts as needed • Issues 24-hr Basin Burn Day Decisions • Issues CB-3s

  9. Where are We Now? • Server is set up and running • Agency/Unit/User ID Request Form complete • Burner Data Entry Forms Complete • Air District/ARB Data Entry Forms 20% Complete • Public Views (Reports) 0% complete

  10. What’s Still Needed • Complete Air District and ARB Pages • 24-hr Basin Burn Day Decisions • 24-Hr Ignition Approvals • CB-3 Details • Complete Project Summary (Public Info) Pages • SMP Views, Project Registration List, Basin Burn Day Decisions Report, Approved Ignitions 48-hr Summary • Complete Post Burn Reporting Pages

  11. Timeline to Completion • Winter 05/06 - Internal pre-Beta Testing • Feb - March 2006 - Beta Testing (limited users) • Identify/Correct Bugs • Spring 2006 - Go Live (?)

  12. Contact Jeff Lindberg jlindber@arb.ca.gov 916.322.2832

More Related