ohsu-alumnidinner-2014
ohsu-alumnidinner-2014
0 0
ohsu-alumnidinner-2014
Talk for the OHSU Division of Environmental and Biomolecular Systems Alumni Dinner - April 11th 2014On Github aaronr / ohsu-alumnidinner-2014
ERMA
Next generation disaster response from NOAA
Aaron Racicot - aaron.racicot@noaa.gov / aaronr@z-pulley.com reprojected.com / @reprojected github.com/aaronr aaronr.github.io/ohsu-alumnidinner-2014
Who I am?
- SW Developer
- Environmental Scientist
- Open Source Advocate
Computer Science
Bridging the Gap
Environmental Science
OR&R
The ERMA application and team
The Deepwater Horizon experience
Our little project...
Environmental
Response
Management
Application
What is ERMA?
National Coverage - Regional ERMA's
History
DWH
DWH - By the numbers
- 11 men perished
- 200+ million gallons of oil spilled
- 580+ miles of shoreline oiled
- 1.70+ million gallons dispersants applied
- 400+ controlled burns
- 4+ million feet of containment boom and 9+ million feet of sorbent boom
DWH and ERMA
- Over 180 Individual Federal/State GIS Staff
- 30-40 specifically ERMA (up from 4 normally)
- 3 ERMA developers
The ORR Continuum
Response > Assessment > Restoration
ERMA Shines as COP
- Less than 48 hours to deploy
- Scalable – 1400+ response users, 16,000+ layers (DWH)
- 30,000+ layers today
- Nimble – over 850 code commits in DWH first year
- Public ERMA – over 20 million hits in 24 hours!
Common Operational Picture (COP)
Response > Assessment > Restoration
(Where we are now)
What is NRDA?
www.gulfspillrestoration.noaa.gov/assessmentNatural Resource Damage Assessment
- Field data collection
- TWGs (technical working groups)
- Archival, aggregation, and visualization of data
- Support ongoing court cases
Response > Assessment > Restoration
Future project planning and tracking
Continued push toward multi-agency
cooperation and data sharing
Scaling in new ways
(leveraging the cloud)
So how/why does this matter to you?
The nuts and bolts might not...
the philosophy does
Focus on small teams of experts
Leverage open tools,
but own the deployment
- This gives us the benefit of a large community of developers
- This gives us the freedom modify and adapt when needed
Utilize open data
and open standards
Doing more with less
(This is a good investment for NOAA)
ERMA's Future?
- Scale
- Deep integration across agencies
- Mobile
- Stand-Alone instances with sync
Future of response?
- There will be more spills
- There will be more hurricanes
- There will be more tsunamis
- Things will be BIGGER and more frequent
Key to the future?
- Build nimble, open, and scalable tools...
- Talk together via open protocols...
- The right data (both open and closed)...
- The right dedicated people behind them...