1. Incident Based Automation CTSP Workshop 2008

2. Agenda IBA Background Phase 2 Strategic Analysis Phase 3 Projects I-Suite e-ISuite

3. Background IBA was chartered by the National Wildfire Coordinating Group (NWCG) in 2003 NWCG Incident Based Automation Project Phases Phase 1Phase 2Phase 3 I-Suite Stabilization and Support Project Incident Based Automation Strategic Planning Project Incident Based Automation Component Projects  Stabilize Application  Initiate Change Management  Provide User Support  Provide Operations and Maintenance  Identify Key Business Areas  Conduct Business Area Analysis  Conduct Strategic Project Planning  Prioritize and Recommend Phase 3 Projects  Infrastructure Components  Business Area Components  Web-based I-Suite

4. Phase 2 Completed Spring 2006 Strategic Areas: Data/Information and Applications/Technology Infrastructure/Connectivity Trained and Skilled Workforce

5. Phase 2 Recommendations  Develop Enterprise models of the Incident Management processes, data, applications and technology  Develop standards for a National contract to supply the infrastructure required to support all computer users at the Incident Base

6. Phase 2 Recommendations  Convert I-Suite to a web application  Work with all agencies on IT policy to address IMT concerns  Provide training findings to TWT

7. Addressing Recommendations Will set the stage for: Incident Based Automation re-engineering: Data Exchange between existing and/or new applications Incorporation of new or existing technology – AIT, ESB, PDAs, etc. Data Availability to the Incident – Intel data, Costs, Resources use, etc. Methodology for new systems that will insure consistency with IBA standards & integration

8. Phase 3 Projects Business Processes/Data Modeling and Gap Analysis Infrastructure Contract e-ISuite

9. Business Processes/Data Modeling and Gap Analysis “ Develop and publish incident management enterprise business process and conceptual data models” “Develop and publish a “Gap Analysis” between the “As-Is” system set and a potential “To-Be” system set”

10. Project Tasks Deliverables: Business Process Models Data Models Gap Analysis Document Effort and Cost Estimate

11. Project Tasks Will assist Management with determining the need for:  New systems  Improvements to existing Systems  Replacing Systems

12. Business Process/Data Modeling IBM December 2006 through February 2008 Interviewed over 50 Subject Matter Experts (SMEs) SMEs from ROSS, I-Suite, IQCS, CTSP Task Group Incident Visits

13. Business Process/Data Modeling Incident Management Team Meetings Position Taskbooks Validated Models with SMEs Reviewed IBA Phase 2 Deliverables

14. Business Process/Data Modeling ICS Forms Handbooks Applications and User Guides Mobilization Guides Incident Action Plans

15. Business Process Models Models provide: Business Processes for each Section Business Processes for most Section Roles Data Sharing and Dependencies between Roles Dependencies between Processes

16. Business Process Models Incident Lifecycle Initial Attack Extended Attack Sections/Roles Demob and Reassignment Transfer Back to Local Unit Closeout

17. Business Process Models Sections: Lifecycle Initial Camp Setup Intelligence Gathering Daily Steady State Activities More Complex Processes

18. Data Models Incident Base Data Considered: I-Suite ROSS import ABS ICS Forms Business Process Models Data not included: Dispatch Fire Behavior Pre-Planning Geospatial / GIS Training

19. | Data Modeling Opportunities What business processes use or need which data? Are there gaps? What systems use which data? Are there gaps and redundancies? What is the authoritative source of each data element?

20. | Data Modeling Opportunities CRUD Matrix Shows how data and business processes are related Detailed information about the support of a business process by systems and data

21. | Data Modeling Opportunities Data Analysis We can now identify: Duplicate data entry Redundantly stored data Similar data but stored and/or formatted differently Different identification and classification schemes for similar data Different system physical structures for similar data

22. Gap Analysis September 2007 through February 2008 Documents difference between the “As-Is” and potential “To-Be” business processes and automation 36 “Findings & Opportunities”

23. Gap Analysis Opportunities Source of ideas gathered from: Interviews Incident Visits Incident Management Team Meetings Business Process Modeling Validation with Incident Management Personnel

24. Gap Analysis Opportunities Functional Areas System Situational Awareness Miscellaneous  Effort and Cost Estimate included with each Opportunity

25. What’s Next… The Government signed off on deliverables IBPWT bought off PMO/NWFEA IRMWT NWCG $$$ and Support

26. Infrastructure/Connectivity National Emergency Information Technology Services Contract (aka “Infrastructure Contract”)

27. Intent “Seamlessly supply, install, configure, and maintain the information infrastructure and support to incidents and events throughout the contiguous United States, Alaska, Hawaii, and Puerto Rico.”

28. Intent “The Contractor shall be responsible for furnishing all equipment, materials, supplies, support and management personnel and support services.”

29. Intent “Information Technology Infrastructure and Support is needed prior to first operational period to facilitate creation of the IAP and for each subsequent operational period until incident management activities conclude. This includes being present at the IMT in-briefing.”

30. Progress Statement of Work completed RFI posted on FedBizOps (closed) Determining how to solicit Contract Contract documents being finalized Will go to WO and USDA for approval

31. IBA Web Page http://iba.nwcg.gov Includes all Project Phases Projects Scope/Briefings Interview Notes Deliverables (TBD)

32. Questions?