1 July 12, 2006/10a Fire Emissions Tracking System White Paper Fire Emissions Joint Forum July 11-12, 2006 Portland, OR Dave Randall, Air Sciences Inc.

2 Presentation Objectives To bring the FEJF up-to-speed with the FTS Task Team on the current thinking re: the development of the WRAP’s FETS. For the FEJF to reach consensus on the direction the FTS Task Team will take to develop the WRAP’s FETS.

3 Presentation Outline ID Purpose & Objectives of FETS Review FTS Evaluation & Conclusions Recommendations – Approach to Develop FETS –Contractual Relationship (Air Sciences/CIRA) –Preliminary Scope –Cost Estimate –Schedule

4 Purpose of WRAP FETS Regional Haze Rule (Rule) Requirements: –309 states – FETS is part of the GCVTC recommendations –308 states – FETS is likely an important tool for the effective management of fire sources: inventory fire location & type (natural or anthropogenic) calculate & inventory fire emissions data influences choices on planned burns

5 Objectives of WRAP FETS Consistently track fire activity & emissions Accommodate regional coordination Create fire emission inventories Apply Emission Reduction Techniques (ERT) Implement Annual Emission Goals (AEG) FETS data available to States/Tribes for Regional Haze planning

6 FTS Evaluation Project Cursory Overview Is there an existing FTS system that will satisfy WRAP’s FTS requirement? Review Web-based & historical systems Primary emphasis: real-time data import and export capabilities. Evaluation made from the perspective of an FTS user.

7 FTS Evaluation Goals Evaluate existing FTS and provide: –A feasibility assessment of existing systems. –An analysis of modifying each system to include WRAP needs. –Estimate resources needed to modify the system to meet the required elements for tracking prescribed fires.

8 ElementsDate of Burn Burn Location Area of Burn Fuel Type Pre-Burn Fuel Loading Type of Burn Nat/Anth Annual Emission Goal Info AEG (addl) Projections Emissions Emissions (addl) System Features Real time data import and export Web based Can info easily be shared between states GIS/mapping capabilities Conventional system language & design Important Characteristics Straightforward queries Straightforward reporting Important Elements for Regional Coordination Basic Elements of FTS Policy KEY FEATURES OF WRAP FTS

9 Table 1 – Feasibility Study Point System Data ElementsCritical Elements Evaluated Max Possible Points Task 2.A. Basic Data Elements Burn DateStart date; end date10 Burn LocationLatitude/longitude10 Burn AreaSize of burn (acres); fuel type10 Components related to Annual Emission Goals15 Emission Reduction TechniquesAny ERT element5 Bonus Ranking 5 Total for Basic Data Elements55 Task 2.B. System InformationWeb-based, exporting capabilities 15 Task 2.C. Back-End and Front-End Applications 10 Task 2.D. Indexing and Reporting 10 Task 2.E. Optional Modules 5 Task 2.F. Interface and/or Data Exchange 5 Total for System-Related Features45 Total Maximum Possible Score100

10 Table 2 - FTS Evaluations Data Elements Max Possible Points San Joaquin Valley Airshed Management System (MT/ID) Smoke Management Database (NM) Nez Perce Tracking System South Carolina Tracking System Florida Tracking System USDA Smoke Management System Task 2.A. Basic Data Elements Burn Date Burn Location Burn Area Components related to Annual Emission Goals Emission Reduction Techniques Bonus Ranking Total for Basic Data Elements Task 2.B. System Information Task 2.C. Back-End and Front-End Applications Task 2.D. Indexing and Reporting Task 2.E. Optional Modules Task 2.F. Interface and/or Data Exchange Total for System-Related Features Total Maximum Possible Score

11 Table 3 – WRAP FTS Requirements

12

13

14

15 Recommendations - Method Extended the Technical Modifications assessment to Post-Modification period. –By dedicating a estimated amount of labor, how would each FTS perform as the WRAP’s FTS? –Tabulated this assessment and used results to inform the Project Team’s recommendations.

16

17

18

19 Conclusions of FTS Evaluation What existing FTS would work best “as-is” for the WRAP’s FTS? MT/ID FTS –Currently functioning system –Supports burn managers in Montana & Idaho –Uses SQL Server database Meets the needs of the WRAP region Fully functional user interface

20 Conclusions of FTS Evaluation What existing FTS requires least amount of modification to work well as WRAP FTS? NM FTS –Upgrading Access database to SQL Server, NM FTS would be capable of meeting current & future WRAP needs –Estimated 120 labor hours to complete upgrade –Already supports limited emissions estimation (PM10) –Generates maps of burn locations –Unsupported features in existing MT/ID & USDA FTSs –Estimated 140 labor hours to implement features in NM FTS.

21 Conclusions of FTS Evaluation What is the best case scenario WRAP FTS (most features & capabilities)? Modified version of the MT/ID FTS –Advantage because it already uses SQL Server database. –Advantage because the preferred interactive GIS system is already being designed for the MT/ID FTS

22 Conclusions of FTS Evaluation What are the benefits of building the WRAP’ FETS from and existing FTS? –Each FTS already incorporates many of the essential features –Two systems will include preferred GIS –Time and money already spent: down- payment on building the WRAP’s FTS.

23 Conclusions of FTS Evaluation Is there an alternative way for the WRAP to proceed with building the WRAP FTS? Commodity-based FETS –NM/FEJF specifications on super-industrial system –Programming to make it look slick & contemporary Make an existing “Commodity” FTS Upgrade NM to be industrial strength database Host on existing e-commerce site (e.g., Yahoo!) Multi-users accommodated on a Web interface Export events to Google Earth for review and regional coordination

24 Benefits for WRAP of Developing Commodity-based FETS 1.The limited dollars in future WRAP grants and the effects on FEJF project funding 2.Lessons learned in the Fire EI preparation and analysis for haze planning purposes over the past several years 3.Plans to provide states and tribes ongoing regional technical support and data access for their haze plans 4.The timing needs for getting the FEJF FTS on-line and fully operational for states to be using for tracking and regional coordination, as well as to point to in their December 2007 haze SIPs.

25 Mechanical Description of WRAP’s FETS Mechanical Description of WRAP’s Fire Emissions Tracking System Planned RX Burn Raw Data Acquisition Data Entry & QC Requested Burn Data Acquisition, Data Entry & Regional Coordination Burn Decisions Emission Inventory Development & QC Pre-Burn Burn/Post-Burn

26 Mechanical Description of WRAP’s FETS need to mod/include pieces

27 Operable FETS Operable FETS will: –Provide real-time access to planned fire event data –Build comprehensive database of all wildland fire events Operable FETS will not: –Provide air quality bases for ad hoc decisions of ESMP –Include a module to estimate the air quality impacts due to emissions from fire events

28 Other Operations of the FETS Gather, compile, QC, query fire activity & emissions data for wildland fires. Planned fire data added to FETS real-time or in advance Data for unplanned events (wildfire) obtained after event using crawls FETS database will require QA/QC, but minimal “ground-up” data gathering Critical Challenge: SMP’s to optimize collection of accurate data for planned fire events

29 Recommendations: Approach Commodity-based development of FETS FETS attached to WRAP’s TSS Advantages: –FETS would be built to serve specific needs of WRAP states & tribes –Fire emission inventory work integrated into TSS –ESMPs can then integrate fire data into regional haze emissions, monitoring & modeling data –Integrating FETS into TSS will support development of regional haze SIPS

30 Preliminary Scope of Work Air Sciences –Technical & developmental lead for FETS project –ID other contractors possibly contributing to development of FETS –Work closely with Task Team assigned to project –Bring development issues to Task Team for guidance –Prepare periodic updates on project’s progress for FEJF –Work closely with Technical Director of WRAP, CIRA personnel involved in WRAP’s TSS & TSS team CIRA: provide technical & developmental oversight for project; integrate FETS into WRAP TSS

31 Tasks for FETS Project 1.Documentation –Detailed Workplan –Technical support (methods, assumptions, etc) –FETS users guide

32 Tasks for FETS Project 2.FETS Software Development: –Database architecture –Data retrieval & input –User interface –Data QC & security –Database functionality –Queries & exports for real-time use of fire data & reporting –Commodity-based mapping routines (Google Earth) –Data reporting –Data archiving & back-up

33 Tasks for FETS Project 3.FETS Technical Integration to TSS –Integrate fire emissions into emission summary tools –Annual Emission Goal demonstration tool –Support Regional Haze SIP content pertaining to fire emissions 4.FETS Support & Maintenance –QA/QC –Data archiving & retrieval –Data reports & export files for SIP and modeling apps –System repair

34 Hours & Cost Estimate Assumptions for preliminary estimates: –Average hourly rate for CIRA = $60/hour –Subcontractor hours would replace Air Sciences &/or CIRA hours –Hardware (if necessary), software licensing (if applicable), hosting costs: not included in current cost estimate –CIRA will charge $2,250 overhead fee (45% of the first $25,000 of Air Sciences labor billed through the subcontract.

35 Hours & Cost Estimate Project Development Cost: –Air Sciences - $120,000 (labor) –CIRA - $37,650 (labor + overhead) Annual Support/Maintenance Cost: –Air Sciences - $20,000/year

36 Hours & Cost Breakdown 1.Documentation Air Sciences – 250 hours/$30,000 CIRA – 40 hours/$2,400 2.FETS Software Development Air Sciences hours/$75,000 CIRA– 160 hours/$9,600 3.FETS Technical Integration to TSS Air Sciences hours/$15,000 CIRA– 240 hours/$14,400 4.FETS Support & Maintenance Air Sciences hours/$20,000

37 Schedule – Major Milestones 07/15/06 – FEJF approval of approach 08/01/06 – Signed subcontract (Air Sci/CIRA) & contract (CIRA/WGA) 08/15/06 – Draft Project Workplan 11/01/06 – Operational Test Version of FETS 01/01/07 – FETS Operational, Technical Support Document & User’s Guide 03/01/07 – TSS Fire Tools Developed

38 Summary Recommend: –Start with a nuts-and-bolts database structure of the FETS (NM FTS) –Build a commodity-based FETS –FETS attached to WRAP’s TSS This will support development of regional haze SIPs –Develop User’s Guide & Technical Support Documents Request for FEJF to reach consensus on providing direction to FETS Task Team with regard to developing the FETS.

39

40 Reference

41 Essential Components of WRAP FTS Minimum information required to calculate emissions, assess impacts on haze, meet requirements of Rule 1.Date of Burn 2.Burn Location 3.Area of Burn 4.Fuel Type 5.Pre-Burn Fuel Loading 6.Type of Burn 7.Classification: “Natural” or “Anthropogenic”