1 / 14

CAL FIRE

CAL FIRE. P roject Ac tivity Dat abase (PACDAT) 11/17/10. Presented by: Mark Rosenberg On Behalf of: Fire Plan Technical Committee. Goals and Objectives. CAL FIRE is developing a new project activity tracking database called PACDAT.

chaman
Download Presentation

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/17/10 Presented by: Mark Rosenberg On Behalf of: Fire Plan Technical Committee

  2. Goals and Objectives • CAL FIRE is developing a new project activity tracking database called PACDAT. • PACDAT will contain Geographic (GIS) and tabular information. • The Goal is to improve project tracking and fiscal reporting to support assessment, planning and emergency response • Multiple programs are collaborating: • CFIP • Forest Legacy • VMP • Fire Plan • FHEP • Prevention • Urban Forestry • FRAP

  3. Goals and Objectives • 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 and manage

  4. Project Activity Database(PACDAT) • What is PACDAT? • Common (GIS) framework and database standard • Tools and procedures to assist reporting • Information requirements and timelines • PACDAT will support • Fiscal reporting requirements • Hazard and risk assessment (Performance) • SWARS annual reporting • Coordination and planning activities • Emergency response

  5. 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 and influence zones (to report performance measures) • Tabular data: Database tables to track and report projects, treatments, funding, costs, activities and other information

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

  7. Database Attributes Standards are developed for GIS and Tabular data: • GIS Database Attributes: • Project Polygons • Treatment Polygons • Support Polygons, lines and points • Non-Spatial Tabular data • Funding • Activities • Ownership • Stakeholders

  8. Project ID & Treatment ID • In the PACDAT model, Project Polygons are parents to Treatment Polygons. Treatment Polygons are parents to Activity records. • Golden Rule: Anytime you add a new record into the database, you must enter a Project ID and/or a Treatment ID.

  9. Add New Project Polygon • Projects are treatment activities that are engaged to address a specific fire problem. • PACDAT is made up of separate “tables” and GIS files (currently 10 of them). • The “Project ID” is the glue that makes this structure work and is called the “Primary Key”. • The “Project ID” allows us to associate many treatment polygons, many funding sources, and many stakeholders to a specific project and set of activities. • The “Project ID” is created from 4 fields in the database (“ Unit “, “ Year “, “ Program “, “project number “). • These Identifiers must be Unique to each project

  10. Add New Treatment Polygon • Treatments “ are areas where one or more “Activities” will be conducted to address a fire problem (e.g. fuel break, controlled burn, LE-100 inspection campaign) • “Treatment tables and GIS files use the “ Project ID“ to Link Treatments to Projects Tables • The “ Activities Table “ is used to track specific tasks needed to complete a treatment • The “ Activities table “ uses “Treatment ID “ (GUID) to link specific activities to treatments (e.g. mastication, pruning, burning)

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

  12. 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 (improved coordination) • Maximize ability to match federal funds • Potential to incorporate non-CAL FIRE projects

  13. ArcGISDemonstration

  14. Thank You

More Related