Transcript ross.nwcg.gov isuite.nwcg.gov National Logistics Workshop March 9, 2004 ROSS / IBA Projects National Logistics Workshop March 9, 2004

ross.nwcg.gov
isuite.nwcg.gov
National Logistics Workshop
March 9, 2004
ROSS / IBA Projects
National Logistics Workshop
March 9, 2004
Today’s Topics
About the ROSS Project
 ROSS Project Update
 2003 Field Season Reviews, Lessons
Learned, and Actions
 IBA / I-Suite
 Messages to Take Home

National Logistics Workshop
March 9, 2004
What the NWCG Asked Us to Do
Develop and Deploy ROSS Application
 Develop and Deploy Dispatch
Messaging System (DMS)
 Maintain and Support Systems
 Provide User Training and Support
 Partner with other Government
Agencies / Initiatives

National Logistics Workshop
March 9, 2004
Evolving ROSS Partnerships
FEMA / ARMS
 USDA Animal and Plant Health
Inspection Service (APHIS)
 Colorado Department of Public Safety
 Emergency Management Assistance
Compacts (EMACs)
 Forest Fire Protection Compacts

National Logistics Workshop
March 9, 2004
ROSS Application Requirements
Automate business functions related to
the resource ordering and status
process used in dispatch
 Capable of providing status and tracking
of all tactical, logistical, service, and
support resources
 Meet ICS and be flexible to other
standards

National Logistics Workshop
March 9, 2004
ROSS Application Requirements

Capable of operating within varying
dispatch organizational structures:
Horizontal / Vertical
 Multi-tiered (e.g. National, geographic
area, zone, local)

All risk incident capability
 Fast and easy installation

National Logistics Workshop
March 9, 2004
ROSS Application Requirements

Provide External Application Interfaces
Qualification Systems (IQCS, IQS)
 Cache Supply System (ICBS)
 Incident Based Automation (I-Suite)

National Logistics Workshop
March 9, 2004
Interface with Pre-existing
Systems
USGS
NIMA
- Military route maps
FAA
- Navigation information
- Airports
ICBS
I-Suite
IRSS
ICARS
IAP
(2004)
Qualification Systems
ITS
National Logistics Workshop
March 9, 2004
IQCS
(Federal)
IQS
(State)
Real-Time Reports
National Logistics Workshop
March 9, 2004
Data Warehouse
ROSS
Data
Sources
Incident
Resources
Orders
Statuses
Data
Dictionary
Status
Counts
Other Data Sources
I-Suite
ICBS
Planning
Levels
???
Organizations
Extract
Transform
Load
Reporting Tools
•MS Access DB
•Text Files/Excel
•I/SQL
•Brio
Resource
Assignments
Dispatch
Workload
Data Warehouse
National Logistics Workshop
March 9, 2004
Resource
Destination
???…
Maps
National Logistics Workshop
March 9, 2004
Implementation Scope
Dispatch
 Expanded Dispatch
 Incident Caches
 Incidents and Mgt (Reports / Data)

National Logistics Workshop
March 9, 2004
Project Update
Project Update

Project Independent Verification and
Validation




RobbinsGioia, LTD
Cost, Schedule, Staffing, Technology
Perfect Score (12 points)
Completed OMB Exhibit 300 submission


Scored 3.9 (2nd highest of all submissions by
USFS)
Project is officially baselined with OMB
National Logistics Workshop
March 9, 2004
Project Update

Data Stats as of 0730 – 3/9/2004
6611 Incidents (1,444 open)
 147195 Requests Processed
 107,720 Assignments Processed
 710,592 Request Transactions
 450 Dispatch Offices on line
 6000+ Vendors
 110,540 Resource Items

National Logistics Workshop
March 9, 2004
Project Update
Helpdesk Availability
 1051 days direct incident support in
2003
 Data Warehouse design / development
initiated
 ORACLE Corp. system performance
evaluation

National Logistics Workshop
March 9, 2004
Interesting Time Saving Fact

FOIA Requests (24 so far) – Examples
include:
ICT3, ICT4, ICT5, DIVS, OPBD
 Southern California
 # Engines Deployed
 # Crews Deployed
 # Requests for IMT mgt Incidents between
10/9/03 and 12/1/03 west of the
Mississippi

National Logistics Workshop
March 9, 2004
Project Funding Basics

Lots of moving parts
OMB Exhibit 300
 IT Investment Review Board
 Departmental and Agency Approvals
 etc etc etc

National Logistics Workshop
March 9, 2004
2003 Review Findings,
Lessons Learned and
Actions
ROSS Implementation Review

Large Incident Strategic Decision and
Assessment Team Request

Interview
Area Command Teams
 Incident Teams
 Expanded Dispatch

Collect Issues and Concerns
 Identify Data Needs

National Logistics Workshop
March 9, 2004
ROSS Implementation Review
Answer Questions
 Address Perceptions
 Develop a report of findings and
recommendations

National Logistics Workshop
March 9, 2004
General Findings





Data Availability to MAC Groups, Area
Commands, and Incidents
Training
ROSS Screen Design and Process
Speed
Business Practices


Inconsistent interpretation of business rules and
practices
Application Bugs
National Logistics Workshop
March 9, 2004
Action Plan
DRAFT
ROSS Implementation Review – Northern Rockies
Action Plan
Working Copy – 2/3/2004
National Logistics Workshop
March 9, 2004
Action Plan Review
Based on Focus Areas
 Actions are guided by:

Project Charter
 Available funding
 Schedule limitations


Not everything can be resolved by 2004
season
National Logistics Workshop
March 9, 2004
Action Plan Focus Areas





Data Availability to MAC Groups, Area
Commands and Incidents
Training
ROSS screen design & process
Speed (Application / System Speed)
Business Practices
National Logistics Workshop
March 9, 2004
Geographic Area
Review and Input
Geographic Area Dispatch
Input
Interviewed each Geographic Area for
top items
 Many Items Similar
 Tops items vary considerably by
Geographic Area

National Logistics Workshop
March 9, 2004
Focus Areas
Performance , Speed
 Travel (Roster, Status, Reassignment)
 Request Status (Resource Location,
Assignment History)
 Usability (Edit request / assignment)
 Reports (Ad-Hoc, Data Exports, Fix
Errors in Standard Reports, Print All)

National Logistics Workshop
March 9, 2004
Focus Areas
Release (Notification, Travel)
 Pending Request (Show All resources
regardless of incident)
 Qualifications / Classifications (Only
want 1 qualification)
 Name Requests

National Logistics Workshop
March 9, 2004
Focus Areas
Resource Status (stop sorting to top of
screen when status is changed)
 Resource Order Printing
 Pending Request (flag UTF verse New)
 Aircraft Management
 Data Cleanup

National Logistics Workshop
March 9, 2004
Changes Here or Coming
Key Inputs Guiding ROSS for
the future
1.
2.
3.
Project Charter (Scope, Schedule, Budget)
Budget
Direction
a)
b)
c)
4.
NWCG
Wildland Fire Leadership Council (WFLC)
Agency
Reviews
a)
b)
c)
d)
National Cost Containment Teams
National Implementation Review – Northern Rockies
Southwest National Fire Reviews
Geographic Area Coordinators and Dispatchers
National Logistics Workshop
March 9, 2004
2004 / 2005 ROSS Goals
1.
2.
3.
4.
Address critical software problems
(bugs).
Address performance and usability
issues.
Continue development within
approved scope.
Address reporting needs.
National Logistics Workshop
March 9, 2004
Version 1.2.6 Overview








Incident may now issue request numbers
Block numbers
Pre-cut orders for external organizations
Retrieve requests
Last action column on pending requests
Manifesting of CWN crews
Reminder flag for travel
More printing / reporting capability
National Logistics Workshop
March 9, 2004
Version 2.0 Overview
Release expected late March 2004
 Infrastructure Focus




Server hardware replacement
Network performance review
System Software Upgrade




ORACLE 9i
IBM WebSphere
Versata 5.5
BRIO 8.X
National Logistics Workshop
March 9, 2004
Version 2.0 Overview

ROSS Application
Code migration to Versata 5.5
 Application Query Tuning
 Increased Security


Focus in on hardware performance
National Logistics Workshop
March 9, 2004
Version 2.1 Overview


Release planned for mid June 2004
Contract Module


Add “Agreement” type for use with EERA and
other agreement types.
Web Status Module



Permit use by government non-dispatch units
(e.g. Rural Fire Districts)
Permit remote supervisors
Resolve issues with nested supervisors
National Logistics Workshop
March 9, 2004
Version 2.1 Overview

Pending request





Fill with new resource (change to
restricted by role)
Fill with agreement (incident record only)
Fill with AD (incident record only)
Release to home (restricted by role)
Ordering chain visibility
National Logistics Workshop
March 9, 2004
Version 2.1 Overview



Search for a Resource (Where's
Waldo?)
Name Requests
Pending Request

EFF / AD overhead shown on available
tab as default per National Mob Guide
National Logistics Workshop
March 9, 2004
Version 2.1 Overview

Edit Request while placed




Catalog Item can be edited while request
is placed, as long as it is not filled
Prepositioning Issues
Assignment Roster Issues
Roster requests placed to Status-Only
Offices that cannot be filled.
National Logistics Workshop
March 9, 2004
Version 2.1 Overview
Incident Resources – Reassignment of
Group Requests
 Work Load Report
 Transfer Person (Changing provider for
an overhead resource) / IQS Import

National Logistics Workshop
March 9, 2004
Version 2.1 Overview
Existing Report Problems
 Resource Order Form
 Data Warehouse
 I-Suite Export

National Logistics Workshop
March 9, 2004
By Summer 2005
Aerial Delivered Resource Mgt.
 Setting availability by qualification
 Setting availability group only
 Adding finance code by anyone unit in
the ordering chain
 Creating and filling supply requests

National Logistics Workshop
March 9, 2004
By Summer 2005
Merge Incident
 Transfer Incident
 Reassign Multiple Incident Resources
(restricted by role)


Move large quantities of resources to
another incident.
Request and fill done simultaneously
 Can be done between to non-local units

National Logistics Workshop
March 9, 2004
By Summer 2005

Reassign Multiple Incident Resources
(restricted by role)

Move large quantities of resources to
another incident.
Request and fill done simultaneously
 Can be done between to non-local units


Reengineer Catalog Functionality
National Logistics Workshop
March 9, 2004
By December 2005








Security
Incident Complex
Consistency Audits – Part 1 & Part 2
Refinement of existing capability for usability
Maps (more detail)
More Reports
Software Problems (Bugs, Rework…)
Data Warehouse
National Logistics Workshop
March 9, 2004
FY-2005 Funding Requests
Contracts / Agreement Enhancement
 Tactical Aviation Management
 IQCS Interface
 Hot Site

National Logistics Workshop
March 9, 2004
FY-2006 Funding Requests
Telephone Status
 Standalone Hot Sync
 Draw Down Levels
 Incident Prioritization
 CAD Interface (generic)
 Compacts
 FIRECODE Interface

National Logistics Workshop
March 9, 2004
Lessons Learned
Lessons Learned
That ##$%@#$ darn ROSS!!! Things
people said!!
 ROSS is responsible for global warming.
 ROSS is causing all delays at NICC!
 George Foreman wants to interface his
Cooker with ROSS.

National Logistics Workshop
March 9, 2004
Lessons Learned

What happened on June 23, 2003?
What could have been done different?
 What are we doing about disaster
recovery?

Share Information
 Networks are key
 Adjust business rules
 Realign Dispatch Processes in Expanded

National Logistics Workshop
March 9, 2004
NWCG Incident
Based Automation
Project
NWCG Incident Base Automation (IBA) Project Phases
Phase 1
Phase 2
I-Suite Stabilization and
Support Project
(IRSS, ICARS, ITS, IAP)
Stabilize
Application
Initiate Change Management
Provide User Support
Provide Application
Maintenance
Incident Based Automation
Strategic Planning Project
Identify
Key Business Areas
Conduct Business Area
Analysis
Conduct Strategic Project
Planning
Prioritize and Recommend
Projects
I-SUITE Operations and Maintenance
FY-2003 / FY-2005
FY-2004 / FY-2005
Phase 3
Incident Based Automation
Component Projects
Infrastructure
Projects
Business Area Projects
I-Suite
Replaced
FY-2006 and Beyond
IBA (Phase I) - Interagency I-Suite Stabilization
and Support Project (IISS)
1.
2.
3.
4.
Stabilize the existing I-Suite application for use by
multiple users at an incident.
Add / Finish the Incident Action Plan capability.
Initiate a structured user support system (user
helpdesk, user guides, and training materials) that
meets the availability requirements for incident
operations.
Initiate application maintenance support to assure
application stability.
National Logistics Workshop
March 9, 2004
IBA (Phase I) - Interagency I-Suite Stabilization
and Support Project (IISS)
5.
6.
7.
8.
Initiate a software test and release process that
minimizes impact on field operations.
Develop and/or update existing training materials
for users, Incident Computer Technical Specialists,
and trainers.
Conduct user training for all groups identified
within the Implementation Scope
Establish Interagency NWCG IT & data operating
standards for use of I-Suite.
National Logistics Workshop
March 9, 2004
IBA (Phase I) - Interagency I-Suite Stabilization
and Support Project (IISS)
Application Scope








Incident Resource Status System (IRSS)
Incident Cost Accounting and Reporting System (ICARS)
Incident Time System (ITS)
Incident Action Plan (IAP)
Incident Supply System
Incident Merge / Split (IMS)
General communications and office management software
such as e-mail, ftp, word processing etc..
National Logistics Workshop
March 9, 2004
Incident Based Automation Strategic Planning
(Phase II) – <NOT CHARTERED YET>

Identify Key Business Areas





Conduct Business Area Analysis




Document key business processes that could benefit from
information technology
Define Business Area Projects


Operations
Logistics
Planning
Support
Define project scope, benefits, and constraints.
Prioritize and Recommend Projects
Select Information Technology Projects
Allocation Resources
National Logistics Workshop
March 9, 2004
Incident Based Automation Project Execution
(Phase III)

Infrastructure Projects









Priority #1
Priority #2
Priority #3
Priority #n



Priority #1
Priority #2
Priority #3
Priority #n
Priority #1
Priority #2
Priority #3
Priority #n
•
Business Area #4
–
– Priority #1
– Priority #2
– Priority #3
– Priority #n
Business Area #n
– Priority #1
– Priority #2
– Priority #3
– Priority #n
Priority #1
Priority #2
Priority #3
Priority #n
Business Area #2

Business Area #3
–
–
–
–
Business Area #1

•
National Logistics Workshop
March 9, 2004
Messages to Take Home
Be Flexible to Change
 See the Big Picture
 Keep Challenging Us (in a Pro-active
Way) to Make Things Better
 Fasten Your Seatbelt and Hang On
 Be Apart of the Success.

National Logistics Workshop
March 9, 2004
Thanks for your
Support and your Time