/
IRWIN IRWIN

IRWIN - PowerPoint Presentation

mitsue-stanley
mitsue-stanley . @mitsue-stanley
Follow
378 views
Uploaded On 2016-02-26

IRWIN - PPT Presentation

IS NOT Another username and password Intended to replace or eliminate existing applications A monolithic database of all wildland fire data The 100 solution to our data challenges 2 IRWIN is ID: 232612

fire data incident irwin data fire irwin incident cad standards authoritative geospatial exchange discovery source enterprise nwcg gov208 year egp doi ios

Share:

Link:

Embed:

Download Presentation from below link

Download Presentation The PPT/PDF document "IRWIN" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.


Presentation Transcript

Slide1

Slide2

IRWIN

IS NOT

Another username and passwordIntended to replace or eliminate existing applications

A monolithic database of all wildland fire dataThe 100% solution to our data challenges

2Slide3

IRWIN is…

A capability that orchestrates data exchange between operational applications

Reduce redundant data entryIncrease data consistencyProvide authoritative operational data

3Slide4

Year One

First six applications

WildCAD Integrated Fire Management (IFM) – State of AlaskaFireCodeWFDSS

ICS209 (Updated)Enterprise Geospatial Portal (EGP)Additional Data IntegratorsRemote Sensing Application CenterState of UtahState of Texas

4Slide5

Year Two

Discovery and prototype

Fire Incident Mapping Tools (FIMT) NWCG Unit IDse-ISuite

AK Fire Service CAD - FireBeansUnified Incident Command Decision Support (UICDS – DHS)ROSS (new version)

NPS and FWS Fire Reporting SystemsInciwebLive by March 2015

ROSS targeted for 2017

5Slide6

Out Years

Year Three

WFMI Fire Reporting (BIA, BLM, NPS)

Fire Management Information System (FMIS – FWS)FireStat (USFS)FAM Web Data WarehouseYear FourNFPORS / FACTSInciWeb

Weather (WIMS, ROMAN)Aviation (AFF)ICBS

At Any Time

CAD Lite

Other CADS

6Slide7

Data Exchange Requirements

Data Exchange Standards

Provides clear definitions and common valuesData must be passed in the standardSlide8

Data Exchange Requirements

NWCG Data Standards & Terminology SC

Approximately 75 approved standards3 New Geospatial Data Layer Standards for review21 new/revised Data Elements Standards in development

Approximately 12 more to be assignedSlide9

Computer Aided Dispatch

CADs – WildCAD, IFM, others

THE authoritative source for “header data”Changes to this data must be made in the CADAll incidents must start in CADAll FireCode requests for incident

Specific changes to WildCAD tomorrowSlide10

Header Data

Fire

Name Fire Discovery Date / TimeDiscovery AcresLocal

Incident IdentifierFire Cause (General)Point of Origin Responsible UnitInitial Lat/Long

Point of Origin Lat/LongSlide11

FireCode

All required data from CAD for Fires

Non-Fire FireCodes not requested through CADSlide12

WFDSS

Automatically create record

Goal to eliminate Dispatcher and Author RolesFields are “greyed out” when it is not the authoritative sourceCAD/ICS209 dependencySlide13

ICS 209

Select incident from list

Updates submitted to IRWIN on approvalFields are “greyed out” when it is not the authoritative sourceHeader DataSlide14

ICS 209

THE

authoritative source for Complex dataComplex Member AssociationMaintains data for each incidentRolls up to Complex SummarySlide15

Enterprise Geospatial Portal (EGP)

Geospatial presentation of IRWIN

datahttp://egp.nwcg.gov/Contact Sean Triplett to request user accountSlide16

Geospatial Data

Conflict Detection

Uses Point of Origin and Discovery Date/Time to identify potential conflicts1000 meter buffer for nearest State/County/GACC

10 Mile buffer on international borders16Slide17

The Good (or GREAT!)

17

IRWIN will reduce redundant data entry and provide consistent, current data across participating applicationsSlide18

The Bad (or challenging)

18

Data exchange will require modification and standardization of existing business practicesSlide19

The Ugly

19

We’ve never done this before, it will be bumpy

and IRWIN will not accommodate every exception to the rule.Slide20

IRWIN Project Contacts

20

Chris Markle

Assistant Director, Enterprise Systems and Decision SupportChristopher_Markle@ios.doi.gov208-334-1569

Roshelle PedersonIRWIN Business LeadKimber_Pederson@ios.doi.gov208-407-6685

Jaymee Fojtik

IRWIN Project Manager

Jaymee_Fojtik@ios.doi.gov

208-334-6191