1. GACC Feedback Sessions Fall 2014

2.  Overview of IRWIN  2014 Production  2015 and beyond  Bumps, Successes and Impacts of IRWIN  Incidents in IRWIN via the Observer  Q&A 2

3.  Reduce redundant data entry  Identify Authoritative Data Sources for operational data  Improve the consistency and quality of wildland fire data  Speed access to data from diverse source systems PROJECT GOALS

4.  May 20, 2014  Five applications reading and writing data  WildCAD  Integrated Fire Management (IFM) (AK DNR CAD)  FireCode  WFDSS  Sit209 4 2014 PRODUCTION

5.  Read Only applications  Enterprise Geospatial Portal (EGP)  Remote Sensing Applications Center (RSAC)  Ventura County Fire Department  Kern County Fire District  Keno Fire Protection District  Situation Analyst Montana 5 2014 PRODUCTION

6.  Read Only in Development  Smart Fire (USFS)  USFS Air Quality Program  CalFire Governor's Report  Utah Department of Natural Resources  Colorado Division of Fire Prevention and Control  UC Davis  NOAA 6 2014 PRODUCTION

7.  CADS  FireBeans (AK Fire Service)  Dispatch Tracker (TX FS)  ROSS (Header Data ONLY)  e-ISuite (excluding Resource Data)  Read Only  Fire Management Information Tool (FMIT)*  GeoMac*  InciWeb*  Additional data elements from 209 & FireCode  IRWIN Observer and Admin Tools 7 2015 PLANNED PRODUCTION

8.  Federal Final Fire Reporting Systems  FireStat - FS Fire Reporting  WFMI - NPS Fire Reporting  WFMI - BLM Fire Reporting  WFMI - BIA Fire Reporting  FMIS - FWS Fire Reporting  State of Washington Fire Reporting  National Fire Incident Reporting System (NFIRS) – US Fire Administration (?)  FamWeb Data Warehouse 8 2016 PLANNED PRODUCTION

9.  Resource Data  ROSS  Multiple CADs  e-ISuite  ICS 209  Weather Data  WIMS  ROMAN  WFMI Weather  Fuels Treatment Data  NFPORS  FACTS  IFT-DSS 2017 PLANNED PRODUCTION

10. FEEDBACK

11. IRWIN IMPLEMENTATION ISSUES

12.  Users adapting to a data exchange environment  FireCode implementation  No WildCAD  Issuing multiple FireCodes  Incomplete implementation of Conflict Resolution  Locking records  Contract challenges BUMPS THIS YEAR

13.  WildCAD  IT Security approval delays  Scheduling IT Support for installation  FireCode impact  Multiple FireCodes  Fire Season BUMPS THIS YEAR

14.  Users adapting to a data exchange environment  Extended Team Ownership  WFDSS  The Surprise….Complexes?!?! STANDOUTS THIS YEAR

15.  Standardization of data across applications  Fields that use Unit IDs  Owner, Jurisdictional, Responsible, Protecting, Responding,  Requires NWCG define terms in relationship to each other  Requires refinement of NWCG Data Standards 15 IRWIN IMPACTS & ISSUES

16.  The governmental entity having overall land and resource management responsibility for a specific geographical area as provided by law.  Ultimately responsible for the fire report to account for statistical fire occurrence  Responsible for setting fire management objectives  Jurisdiction cannot be re-assigned by agreement  The nature and extent of the incident determines jurisdiction (e.g., Wildfire vs. All Risk) JURISDICTIONAL UNIT

17.  Landowner - The person or entity that owns the land or has the authority to convey title to others.  Protecting Unit – The entity responsible for providing direct incident management and services to a given area pursuant to its jurisdictional responsibility or as specified by law, contract or agreement.  Protection can be re-assigned by agreement  The nature and extent of the incident determines protection (e.g., Wildfire vs. All Risk) OWNER & PROTECTING UNIT

18.  Geospatial Data  GeoMac, EGP, FIMT, ftp site, WFDSS, InciWeb, etc  Authoritative Data Layers  NWCG Geospatial Subcommittee to solve 18 IRWIN IMPACTS & ISSUES

19.  FireCode  ID BLM, Region 1 & 4, Idaho Dept of Lands  Change to FireCode User Guide in June  Responsible to Jurisdictional/ Protecting  Recommendations:  Establish FireCode oversight body / change management board  Update to add Jurisdictional and Protecting  Consider Fiscally Responsible Unit  Clarify business rules and definitions 19 IRWIN IMPACTS & ISSUES

20.  Data Management for Complexes  Need common guidance adopted by all agencies  Examples in IRWIN move the discussion forward  Group meeting Sept 10-11  Recommendations:  Complex parent is not a wildfire itself  Created just to group incidents  Child incidents retain uniqueness in all applications 20 IRWIN IMPACTS & ISSUES

21.  Resources  Need standards for naming and identifying individual resources across CADs, ROSS, eISuite, ICS209 and IRWIN 21 IRWIN IMPACTS & ISSUES

22.  Requirements  User authentication and roles  Tools for detecting and resolving data quality issues  Business view vs. Developer tools IRWIN OBSERVER Irwinoat.doi.gov/audit/#!/ http://irwinoat.doi.gov/audit_1.2.1/#!/

23. 23 IRWIN PROJECT CONTACTS Chris Markle IRWIN Project Manager Christopher_Markle@ios.doi.gov 208-334-1569 Roshelle Pederson IRWIN Business Lead Kimber_Pederson@ios.doi.gov 208-407-6685 Jaymee Fotjik IRWIN Associate Project Manager Jaymee_Fotjik@ios.doi.gov 208-387-5829