Operational, Timely Fire Data on an Open Source Stack Angus Carr, Saskatchewan Forest Centre

Quick Fire Primer Fine Fuel Moisture Code Temp, rh, ws, wdir Duff Fire Weather Index Yesterday's Codes Drought Code

Quick Fire Primer Overtime! Temp, rh, ws, wdir Rate of Spread Action Fire? Hire Helicopters? Patrol? Topography Head Fire Intensity Fuels Type of Fire

The Initial State MySQL 3, PHP, Perl site No Source Control Staff Exit 2 years on life support by external consultant (me) with ”minimal-time” instructions DB as data holder with little business logic Cron Orchestrator

The Ideal State Business Logic in DB Event-Driven Orchestration Integrating operational activities You can probably follow where this is going...

The Technology So Far PostGIS Programming In Python PHP Shell Scripts Perl Apache/Mapserver/OpenLayers Still ”Web 1.0” - data presentation

Local Customization Lightning Weather Data Logging Callouts on failure Fire Intelligence Calculations Business Logic Informing Managers Integration of operational activities with the system

The Value Proposition X X On the lower right of the Cost/Function Graph Our costs were staff time only We're not done yet X X Function Cost

We Brought to the Org Full logging of all products in system Higher reliability Near-Live Mapping Higher Speed Fire Intelligence Not a full redesign of processes Not a simplification of data systems Not a complete solution

The Big Issue Hearts and Minds Fear of uncertainty Discomfort with ”new stuff” Why do I have to learn something new? Why doesn't the system work the way I want?

What's Next? Integration of fire growth modelling and predictive modelling Build in forms and business activities for operations Decrease in the number of systems calculating stuff Decreased complexity = Increased relibility Integration of archival and production systems