1 / 18

CAL FIRE

CAL FIRE. P roject Ac tivity Dat abase (PACDAT) 11/2/10. Presented by: Mark Rosenberg Rich Walker Suzanne Lang. Overview. Outline Group “Charter” Identify what is being developed (PACDAT) Review expected benefits to CAL FIRE Consider management support needs ($’s) Discuss next steps.

vashon
Télécharger la présentation

CAL FIRE

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. CAL FIRE Project Activity Database (PACDAT) 11/2/10 Presented by: Mark Rosenberg Rich Walker Suzanne Lang

  2. Overview • Outline Group “Charter” • Identify what is being developed (PACDAT) • Review expected benefits to CAL FIRE • Consider management support needs ($’s) • Discuss next steps

  3. Group Charter • Goal is to improve project tracking and fiscal reporting in a spatial context to support assessment, planning and emergency response • Multiple programs are collaborating to develop the database model, data collection requirements, procedures and work flows. • FHEP in South Region was proposed as potential pilot area (early adopter?)

  4. Group Charter • Background – review of previous efforts • 1996 – Prescribed fire data captured as a part of the CA Fire Plan • 2003 – Insect caused tree mortality treatments captured by FHEP • 2007 – Prop 40 Database developed and deployed to track all Prop 40 funded projects. Business process developed and spatial data capture achieved. Key personnel left positions and data capture ceased • 2008 – Spatial Analysis Project (SAP) requires collection of all Forest Stewardship projects for federal reporting requirements. All CFIP projects (going back 10 years) are captured in GIS 2009 –Group was tasked by Deputy Director for Resource Management (Bill Snyder) to develop protocols for RM • 2010 –WebDET pilot with ESRI and USFS reveals modifications would need to be made for this product to meet California’s needs • 2010 – Strategic Fire Plan implementation re-invigorates this effort

  5. Group Charter • Why develop PACDAT? • Need to establish standards for reporting CAL FIRE activities and performance measures • Current efforts are insufficient to meet emerging Fire Plan Reporting and Federal Grant Requirements • Develop infrastructure to support upward reporting to Legislature, BOF and Granting Agencies • Standardized content across programs • Centralized database more efficient to access, manage and use

  6. Group Charter • Goal: Develop a spatial (GIS) database of CAL FIRE project activities that augment, mitigate or manage fuels and forest resources. • Phase 1: • Identify programs that are funding, supporting or executing projects that need to be tracked spatially • review existing databases and data capture activities • Identify required utility based on end user and management needs • Determine salient features and attributes to capture • Phase 2: • Develop and test database schema (attributes and structure) • Set draft protocols for data capture, maintenance, and distribution • Develop prototype, test and finalize Version 1 database • Phase 3: • Implementation

  7. Group Charter Departmental programs involved • CFIP • Forest Legacy • VMP • Fire Plan • Forest Health Improvement Program (FHEP) • Conservation Camps • Prevention • Urban Forestry • FRAP External partners and stakeholders: • Resource Conservation Districts and NRCS • Community Fire Safe Councils • Mountain Area Safety Taskforce (MAST) • Forest Area Safety Taskforce (FAST) • USFS

  8. Project Activity Database(PACDAT) • Identify what is being developed (PACDAT) • Common (GIS) framework and database standards • Tools and procedures • Reporting needs and timelines • PACDAT will support • Fiscal reporting requirements • Hazard and risk assessment (Performance) • SWARS annual reporting • Coordination and planning activities • Emergency response

  9. Project Activity Database(PACDAT) • Common framework and database standard • Database Standards: Common attributes and codes will be maintained and enforced via database domains and control tables • Spatial Database: Boundaries (GIS Maps) depicting project areas, treatment areas, influence zones (to report performance measures) • Tabular data: Database tables to track and report projects, treatments, funding, costs, activities and other information

  10. Prevention: • Inspected Properties • FHEP: • Zone of Infestation area • FAST/MAST area • Fire plan: • Project Influence Areas • Treatment Influence Areas • Planning Areas

  11. Project Activity Database(PACDAT) • Reporting requirements (developed by The Fire Plan Analysis Workgroup) • Project Areas / Management Plan Boundaries • Treatment Areas • Treatment Activities and Status • Project and Treatment Influence Zones for reporting performance measures • Ownership Information • Funding and Cost Data

  12. Draft User Interface choices Project Activity Database(PACDAT) Tools and procedures • enter • edit • review • query • report • upload

  13. Review expected benefits • Improved project reporting and fiscal accountability • Increased usefulness of data • Consistency and clarity in upward reporting • Better access to data and reports across program areas • Potential to incorporate non-CAL FIRE projects

  14. Review expected benfits • Accessible data to support program implementation and meet information requests • Improved cross-program coordination (one point of contact of all data reporting per Unit, PFE?) • Timely reporting to management and funding agencies • Maintain fiscal accountability • Maximize ability to match federal monies

  15. Management Support Needs • Buy-in across programs and at the Unit level • Establish policy for project activity reporting • Identify program roles and responsibilities • Ongoing fiscal, staff, and infrastructure support

  16. Discuss next steps • Identify program responsibilities for reporting of activities • Determine staffing, funding, hardware and software support needs • Develop user interface for data entry and reporting • Develop policies and procedures for reporting, including minimum standards, report frequency, and schedules

  17. Discuss next steps DevelopmentNeeds • Operational protocols for • Data entry • Centralized data management • Data feedback to units • Upward reporting to funders • Report generation • User interface to aid data entry • Varies per program (may require assistance of ITS programmer or external programmer) • Web Services • Internal • Public facing (hosted on CalAtlas)

  18. Thank You

More Related