1. System Overview 18 March 2008

2. I-Suite is An Automated Incident Business Information and Support Tool Written as a Portable Client/Server Application WILDLAND FIRE HURRICANES NATIONAL DISASTERS What is I-Suite

3. 18 Mar 20083 ISuite Functionality Track Resources  Check In  Demobilization Record Time  Produce Invoices Calculates Cost  Estimations  Actuals  Projections Track Supplies Record Injury and Illness Data Develop Incident Action Plan (IAP) Provide Reports and Data  Incident  Others

4. 18 Mar 20084 e-ISuite Background Next Generation Version of I-Suite Project Objectives  Migrate current ISuite to web-enabled environment  Make minimal functional enhancements (1 st Release)  Provide enterprise-wide incident data  Support all incidents (i.e., IA to Close-out)  Use the remote application without an internet connection Java Based UML Modeling Approach SabiOso Located in Clearfield, Utah

5. 18 Mar 20085 Benefits of e-ISuite Generate Invoices for Casual Hires  Training, dispatch, and cache work Install on One Computer at Site Easily Retrieve Data From Other Systems  ROSS, ICBS, IQCS, etc Incident Data Available to Other Systems Newer Technologies  MS Visual Basic is no longer supported by MS  Extend the application lifecycle Historical Data

6. 18 Mar 20086 System Architecture Constraints System of Two Primary Components  Enterprise application at NITC  Remote, stand-alone, portable application at incident site Browser Based No Proprietary or Licensed Components (Remote Application) Enterprise Application is System of Record For e-ISuite Originated Data Accessible via Internet Accessible via Agency Intranets Remote is Usable Without Internet Connection Protect Sensitive Data From Unauthorized Disclosure Support Team Transitions and Incident Transitions

7. 18 Mar 20087 Conceptual Architecture Agency Office(s) Intranet (or Internet) Internet Incident Site (e-ISuite Remote) ESBESB e-ISuite Enterprise Other Data Services

8. 18 Mar 2008 Software Components Site  Small foot print  Single application  Automated component  Uses web services of enterprise Enterprise  Multiple applications  Scalable  Web application  Web services  JMS message handlers  Application monitoring

9. 18 Mar 2008 Enterprise Components Load Balancer Tomcat Web Container(s)  Contains UI components  Contains application (business logic) components Spring for Application Management Spring-WS or Xfire for Web Services Java Server Faces for UI Oracle for Database(s) Apache ActiveMQ for JMS Broker

10. 18 Mar 2008 Site Components Tomcat Web Container  Contains UI components  Contains application (business logic) components Spring for Application Management Quartz Scheduler for Automatic Components MySql for Database Swing Application on Server Machine to Manage application Simple Install

11. 18 Mar 200811 Data Flow Enterprise is the Data Repository for What Happens at Incidents Multiple Input Sources  Site installation  Government offices  Other government systems (ROSS, ICBS, etc) Multiple Output Requests  Site installation  Government offices  Other government systems (ROSS, ICBS, etc)  Data warehouse New Roles Related to Data Flow  Data Transfer Role  Data Reconciliation Role

12. 18 Mar 200812 Site and Enterprise Data Transfer Only Data Differences  Based on date-time stamp Based on Data Transfer Credentials  Entered at the Site  Authenticated on the Enterprise Data is Encrypted

13. 18 Mar 200813 Site and Enterprise Data Transfer Based on Data Transfer Credentials  Entered on administration screen of site application  User name and password  Uniquely identifies user transferring data  Must exist on enterprise system with the data transfer role  Does NOT need to be the same as the name/password used at the site  Stored in memory at site  Must be re-entered if site server reboots  Automatically included in each transmission (send or request) from site to enterprise Data is Encrypted  Public/Private key cryptology  One set for enterprise  One set for all sites  Public keys shared, private keys held

14. 18 Mar 2008 Transfer Mechanisms Internet at Site  Automatic (no manual intervention)  Scheduled  Frequent  Manual override (“do- it-now” button)  Via enterprise web service No Internet at Site  Manual (operator initiated)  Data to portable media  Upload to enterprise web application  Web application calls enterprise web service Internet

15. 18 Mar 2008 Transfer Complete Send Data Frequently  Minimum of once a day (Finance requirement)  Smaller file means less time Request Data Frequently  Resource data arrives at camp before the resource  Reduces manual data input at camp  Reduces data errors  Reduce the need for reconciliation Data Reconciliation  Must have the Data Reconcile role  Can assign this new role to any user

16. 18 Mar 200816 Questions