1 / 37

Training Session Fire Emissions Tracking System

This presentation will probably involve audience discussion, which will create action items. Use PowerPoint to keep track of these action items during your presentation In Slide Show, click on the right mouse button Select “Meeting Minder” Select the “Action Items” tab

pmazurek
Download Presentation

Training Session Fire Emissions Tracking System

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. This presentation will probably involve audience discussion, which will create action items. Use PowerPoint to keep track of these action items during your presentation • In Slide Show, click on the right mouse button • Select “Meeting Minder” • Select the “Action Items” tab • Type in action items as they come up • Click OK to dismiss this box • This will automatically create an Action Item slide at the end of your presentation with your points entered. Training Session Fire Emissions Tracking System Technical Support System Orientation & Review Workshop June 19-20, 2007, Denver CO Air Sciences Inc.

  2. 1.1 Opening Remarks • Introduction to beta Version of WRAP Fire Emissions Tracking System (FETS). • First…get FETS functioning as a stand-alone system. • Later…integrate FETS into the WRAP’s Technical Support System. • Need, want, must have your input & feedback! Air Sciences Inc.

  3. WRAP FETS Fly-by Air Sciences Inc.

  4. Section 51.309.(d)(6) of the Regional Haze Rule requires each State to establish an emissions inventory and tracking system (spatial and temporal). WRAP’s Fire Tracking System Policy approved by the WRAP Board 4/2/2003(http://wrapair.org/forums/fejf/documents/fts/WRAPFTSPolicy.pdf) Facilitate Regional Coordination among Smoke Management Programs 1.2 Overview of FETSWhy do we need it? Air Sciences Inc.

  5. 1.2 Overview of FETSWhat is it? • A secure, easy-to-implement database software package and development environment. • Simple, efficient, “commodity” programming language and software packages to communicate with the database, control data mining, and provide an effective, fully-functional web interface. Air Sciences Inc.

  6. 1.2 Overview of FETSWhat is it? • A reliable, secure web-hosting server to act as the gateway for all FETS users. • Server storage space sufficient for database record storage and archiving well into the future, on the order of 100 GB. Air Sciences Inc.

  7. Features of the FETS Mapping tool Web User Interface Google Maps API Cold Fusion Map/File Export External Database Interface CIRA SQL Server Python Python GRASS CONSUME TSS SQL Server Emissions Fuel layer node Air Sciences Inc.

  8. Critical Functions of the FETS • Questions to Consider as QC Procedures are Developed • After data are used for day-to-day regional coordination, how do we improve the quality of the data? • Will it require additional reporting? COLLECT AND STORE Output Results • Intended Use of the Data • Planned emissions/regional coord. (very frequent use) • QC’d data/periodic reporting • Refined emissions for input to modeling Level 1 QC Level 2 QC Level 3 QC Improve quality of emissions estimates TSS Air Sciences Inc.

  9. Projects Project Name Location information General fuels information Time window (start and end dates). Planned Burns Burn Date Specific fuels information Acres Emission Reduction Technique (ERT) information Data Provider emission estimates 1-to-Many 1.2 Overview of FETSWhat’s in it? Planning Info Submitted to SMP’s prior to the burning season. Unit ID (MT) Burn Permit ID (WA) Project ID (NM) Fire Event Day Info Submitted to SMP’s the day before a planned burn. Fire ID (MT) Request ID (WA) Burn Days (NM) Air Sciences Inc.

  10. 1.2 Overview of FETSWhat’s in it? • Minimum Data Elements (per WRAP’s FTS Policy) Air Sciences Inc.

  11. FETS Database Mirrors TSS Database Emissions Planned Burn Data Project Data Lookup Tables User Data Air Sciences Inc.

  12. 1.2 Overview of FETSWhat Does it Deliver? • Storage Device for Fire Activity Data • Efficient data acquisition • Automated and custom QA/QC • Version control / archiving / back-up • Real-time Information Tool for Smoke Management Programs (maps and fire statistics) • Cost Effective Data Retrieval Tool • Integrates Fire Data into Regional Haze SIPs Air Sciences Inc.

  13. 1.2 Overview of FETSWhat Else Does it Do? • Fuel and Emissions Node • Dedicated Linux machine for emissions calculation and fuels assignment • GIS software (Geographic Resources Analysis Support System – GRASS) overlays fire data on 1-km Fuel Characterization Classification System (FCCS) 1.1 map (Lower 48) or Canadian Forest Fire Danger Rating System (CFFDRS) (Alaska) • JAR-implemented CONSUME 3.0 calculates emissions • Procedures automated on a set schedule (to be determined) Air Sciences Inc.

  14. Remote Linux machine • Manage fuel class assignment • Perform GIS calculations • Manage/perform emission calc’s • Web Server (shared host) • Stores all .html and .cfm pages • Controls data entry and queries • Manages mapping tool Send queried data for calculation Send queried data for display - Send new event info - Update existing events - Query existing data • Query records missing fuel class/emissions • - Update fuel class info • - Update event emissions • Database Server • Stores all fire data Fuel and Emissions Node Air Sciences Inc.

  15. 2.0 Fire Science in the FETS2.1 Fuel Loading • Fire science applications run through FETS Task Team in a “Strawman” process. • Fuel Loading Hierarchy • User-provided, when available. • For users entering data via the web interface, select fuel class directly from pull down list. • For batch data with no fuel loading, Fuel and Emissions Node assigns. • At this time, a single fuel classification will correspond to a given set of fire event coordinates (e.g., fire perimeter information will not be incorporated). Air Sciences Inc.

  16. 2.0 Fire Science in the FETS2.1 Emissions Estimates Hypothetical Emissions Hierarchy for a fire event: • Emissions Estimates - hierarchy • User-Provided • When available, always used for emission inventories. • CONSUME • Used for emission inventories when User-Provided data is not available. • WRAP-method • Always used for regional coordination map displays. Air Sciences Inc.

  17. 2.0 Fire Science in the FETS2.1 Emission Reduction Techniques • ERT’s noted at the time of Planned Burn data entry. • DEFAULT - WRAP (and Alaska) ERT Seasonal Suites. • OPTION – Choose from pull down list of ERTs with associated Emission Reduction Factor (ERF) • OPTION – Enter ERF Air Sciences Inc.

  18. 2.0 Fire Science in the FETS2.1 Emission Reduction Techniques • Post-burn confirmation to include ERT information and emissions averted calculation. • Interface to assist website users with selecting appropriate ERTs. • WRAP ERT Technical Package will be available as a reference for users. • QC’d EIs will include emissions averted estimates. Air Sciences Inc.

  19. 3.0 FETS Navigation tss Projects tss Resources-Emissions Air Sciences Inc.

  20. User Permission Levels Public no login limited viewing privilege Data Provider login required data manipulation privilege Data reporting/export privilege Data User Login required Data reporting/export privilege 3.0 FETS Navigation fets home page Air Sciences Inc.

  21. 4.0 Fire Data Manipulation Air Sciences Inc.

  22. 4.1 Manipulating Fire Data Data Acquisition Plan • Wildfire • Upload Batch Data – Scheduled data mining of public databases (e.g., ICS-209). • Manual data entry at FETS • All other fire types • Upload Batch Data - Scheduled retrieval from existing Fire Tracking Systems and designated FTP site. • Manual data entry at FETS Air Sciences Inc.

  23. 4.1 Uploading Batch Data Simple CSV files (comma delimited) Same fields required in manual data entry mode Example Format Blue Sky CSV Files (comma delimited) More fields available. Fewer defaults used to estimate emissions Example Format • Schedule for Automated Data Acquisition – • midnight; 9a; 11a Mountain time Air Sciences Inc.

  24. CSV File Format – Basic Project and Planned Burn Data Uploads CSV File Format – Blue Sky-Formatted Planned Burn Data Uploads Air Sciences Inc.

  25. 4.1 Uploading Batch Data • Internal QA/QC Procedures • Record-by-record rejection • File format or Burn ID duplicity • Rejection reports indexed on Burn ID. • Automated QC procedures for date and county. • Automated (and relatively immediate) notification to data provider. • No “Smart” QA/QC Procedures planned • E.g., “black sitka spruce” vegetation type in Arizona. Air Sciences Inc.

  26. 4.2 Entering Data Air Sciences Inc.

  27. 4.2 Entering Data • QA/QC Procedures • Project level checks • Current calendar year • On-screen confirmation • Review Data Submitted • Mini-map showing burn location • Planned Burn level • Date within project window • On-screen confirmation • Review data submitted • Location (not implemented) • Duplicity: One planned burn per project per day Air Sciences Inc.

  28. 4.3 Editing Data INSERT SCREEN CAP OF VIEW MY PROJECTS PAGE Air Sciences Inc.

  29. 4.4 Deleting Data Air Sciences Inc.

  30. 5.0 Fire Data Applications INSERT SCREEN CAP OF MAP Air Sciences Inc.

  31. 5.1 Regional Coordination State and Tribal Smoke Manager Contacts Air Sciences Inc.

  32. 5.1 Regional Coordination Mapping Tool Air Sciences Inc.

  33. 5.2 FETS Data Query & Download5.3 Google Earth Air Sciences Inc.

  34. Air Sciences Inc.

  35. Milestones • FETS Technical Features Operational (BETA ver) – June 2007 • WRAP Technical Support System Workshop (June 19-20, 2007) • Incorporate comments from workshop, “bells and whistles” (Summer 2007) • Grant User Access, begin acquiring data (September 1, 2007) • Tools to integrate fire emissions into TSS data analyses & summaries (Fall 2007) • Integration of fire data to WRAP TSS (continuous) • Emissions Inventory "Lessons Learned" workshop and FETS Training at FEJF meeting (Sept. 25-27, 2007) • Documentation • Technical Support Document • FETS User Guide Air Sciences Inc.

  36. Links/Contact Information • www.wrapfets.org Dave Randall, Air Sciences Matt Mavko, Air Sciences drandall@airsci.com mmavko@airsci.com 303.988.2960 x221 503.525.9394 x115 Air Sciences Inc.

  37. Questions? Air Sciences Inc.

More Related