Wildland Fire IampT What is IRWIN Current development phase Development timeline QampA 2 Wildland Fire Information amp Technology WFIT MOU final signature August 1 2012 Harris Sherman USDA Under Secretary Natural Resources and Environment ID: 680256
Download Presentation The PPT/PDF document "Context for IRWIN development" 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.
Slide1
Slide2
Context for IRWIN development
Wildland Fire I&T What is IRWIN?Current development phase
Development timelineQ&A2Slide3
Wildland Fire Information & Technology
(WFIT)
MOU final signature August 1, 2012Harris Sherman – USDA Under Secretary – Natural Resources and EnvironmentRhea Suh – DOI Assistant Secretary – Policy, Management and Budget
Concurrence:Chief, USFS; Directors – BIA, BLM, FWS, NPS, USGS; Administrator – US Fire AdministrationSlide4
So what does that mean?
Interdepartmental process for managing Wildland Fire I&T investments
Emphasis on Wildland Fire Business driving I&T solutions and servicesSolutions are interoperable and interconnectedReduce complexity to usersSlide5
Special focus areas
National Computer Aided Dispatch
Task team charteredFast track effort – recommended solution by mid-FY14Reviewing previous work (2008 Dispatch Study, etc)
Validating, updating business requirementsA CAD needs to do “this” because…Dispatch and management perspectivesConsideration of overall IT portfolio capabilitiesConsidering national standards or a single applicationSlide6
Special focus areas
Data Management Program
Charter being developedTasked with managing data across all applicationsIncludes review of historical fire occurrence data, aka Final Fire ReportsIdentification of Authoritative Data Sources
Management of Data Element and Geospatial Data Layer StandardsGoal: Simplify data entry and maintenance requirements for the field while providing more consistent, timely, and reliable data Slide7
What is IRWIN?
I
ntegrated Reporting of Wildland-Fire Information
Reduce redundant data entryIncrease data consistencyProvide authoritative operational dataSpeed access to data in diverse source systemsChartered by DOI and USDA FSDOI is the managing agency
“Black Box” – orchestrates data exchange between applications
7Slide8
IRWIN
8Slide9
Development
Five systems prototyped
WildCAD (Refresh & CAD Integration Server)FireCodeWFDSSSit209 (Updated)Enterprise Geospatial Portal (EGP)
9Slide10
CAD (WildCAD as prototype)
When used, CAD is expected to be the Authoritative Data Source for basic incident data
Fire Name, Discovery Date/Time, Initial Location, etcCADs will need a mechanism to submit initial incident data to IRWIN and/or request a FireCode
“Get FireCode” buttonConflict Resolution – surfaced to dispatcher for resolution upon detectionExample criteria:6hrs, ½ mile, not from the same center
10Slide11
FireCode, WFDSS, Sit209
FireCode
Goal is to request and receive a FireCode without leaving the CADAll FireCode required data must originate in the CADWFDSS/Sit209Incident data from IRWIN will be used to create new records using a drop down list in the application
11Slide12
Enterprise Geospatial Portal (EGP)
New FS application being developed with IRWIN
Provides a geospatial presentation of IRWIN dataWill present a map interface for Conflict ResolutionProvides a Common Operating PictureRole based views: Incident, regional, national, executive summary, public
12Slide13
IRWIN potential impacts & issues
13
Standardization of data across applicationsDo we all really know what Location means at any point in time?
Initial location, updated location, final “Point of Origin”Does every system need the location data?What are the implications if only the ADS has that data element?Slide14
Current Development Timeline
Development of IRWIN Database and exchange capabilities underway
User Acceptance Testing planned for Fall 2013Production (Go Live) planned for Spring 2014Identifying next applications for prototyping in 2013Additional CADs, ROSS, weather, NWCG Unit IDs,
etcRepeat this basic process of prototyping, development and implementation of 4-7 applications each year through 2017
14Slide15
Questions or Comments?Slide16
IRWIN Project Contacts
16
Chris Markle
IRWIN Project ManagerChristopher_Markle@ios.doi.gov208-334-1569
Roshelle PedersonIRWIN Business LeadKimber_Pederson@ios.doi.gov208-407-6685
Jaymee
Fotjik
IRWIN Associate Project Manager
Jaymee_Fotjik@ios.doi.gov
208-387-5829Slide17
Wildland Fire Information & Technology
(WFIT)
FS
DOI
Executive Board
Program Board
Wildland Fire
Information and Technology
Governance and Management
User Advisory Board
S&T Advisory Board
Planning
Board
Development
Board
Operations
Board
CIO / Investment Processes
Jim Hubbard / Kim
Thorsen
National FA IT Managers
How existing work and functions across all agencies will be coordinatedSlide18
IRWIN Data Dictionary
18
FORS
IRWIN Data Element
Wildcad
SIT209
WFDSS
FireCode
EGP
Incident Timeframe Originated
n/a
IRWINID
R
R
R
R
R
1 - Initial Report
x
UniqueFireIdentifier
CRUD*
CRUD*
CRU*D*
CRU*D*
R
1 - Initial Report
LocalIncidentIdentifier
CRUD*
CRUD*
CRU*D*
CRU*D*
R
1 - Initial Report
x
IncidentName
CRUD*
CRUD*
CRU*D*
CRU*D*
R
1 - Initial Report
x
FireDiscoveryDate
CRU*D*
CRU*D*
CRU*D*
CRU*D*
R
1 - Initial Report
x
POOLatitude
CRUD*
CRUD*
CRUD*
CRU*D*
R
1 - Initial Report
x
POOLongitude
CRUD*
CRUD*
CRUD*
CRU*D*
R
1 - Initial Report
x
POOResponsibleUnit
CRUD*
CRUD*
CRU*D*
CRU*D*
R
1 - Initial Report
IsComplex
CRU
CRU
R
CRU*
R
1 - Initial Report
ComplexIRWINParentID
CRU
CRU
R
CRU*
R
1 - Initial Report
x
FireCode
CRU*D*
R
R
CRU*D*
1 - Initial Report
x
IncidentTypeKind
CRU*D*
CRU*D*
CRU*D*
R
1 - Initial Report
x
IncidentTypeCategory
CRU*D*
CRU*D*
CRU*D*
R
1 - Initial Report
x
FireCauseKind
CRUD*
CRUD*
CRUD*
R
1 - Initial Report
DailyAcres
CRUD*
CRUD*
CRUD*
R
3 - Contain
x
ControlDate
CRUD*
CRUD*
CRUD*
4 - Control
x
FireResourceKind
CRUD*
CRUD*
R
2 - Initial Response
x
FireResourceCategory
CRUD*
CRUD*
R
2 - Initial Response
x
FireResourceType
CRUD*
CRUD*
R
2 - Initial Response
InitialResponseResourceQuantity
CRU*D*
CRU*D*
R
2 - Initial Reponse
x
ResourceQuantity
CRUD*
CRUD*
R
2 - Initial Response
IncidentCommanderName
CRUD*
CRUD*
R
1 - Initial Report
x
ContainmentDate
CRUD*
CRUD*
3 - Contain