Wildland Fire Line of Business LOB

1
Wildland Fire Line of Business (LOB)

• Modernization Blueprint
• IRMWT
• September 28th, 2004

2
Agenda

• Drivers for Wildland Fire Modernization
  Blueprint.
• DOI Modernization Blueprint Method and Wildland
  Fire status?
• DOI Blueprint Findings and Recommendations
• DOI Blueprint Next Steps
• DOIs Input into Inter-agency EA
• Questions Answer Session

3
Drivers for Wildland Fire Modernization

• Improve capability to predict fire occurrence
• treatment efforts
• planning efforts
• Improve capability to respond to incidents
• Protection of life, property and environment
• Improve information timeliness and reliability
• Budget management and forecasting
• Resource utilization understanding
• Fire behavior understanding (near real time)
• Improve Total Cost of System Ownership
• Leverage DOI and USDA technology standards and
  newly implemented e-Gov technologies (portal,
  middleware, content management)

4
DOI IEA Key Background Information

• Four Lines of Business Identified for Interior
  Enterprise Architecture (IEA) in FY04
• Wildland Fire
• Law Enforcement
• Recreation
• Finance
• DOI Blueprint Methodology formally approved by
  E-Gov Team Nov 2003
• DOI Enterprise Architecture Repository (DEAR)
• Online January 2004
• Federal Enterprise Architecture (FEA) alignment
• Wildland Fire As-Is Data Collection started
  October 2003
• April Meeting included additional data collection

5
Wildland Fire Involves Non-DOI Organizations
6
Scope of Wildland Fire Modernization Effort

• DOI Modernization Blueprint Scope
• DOI Systems (less aviation)
• USFS systems skeletons provided by April meeting
• Used to establish business and system context in
  support of DOI effort
• Constraints on Blueprint
• Does not provide a complete understanding of all
  the USFS systems in the context of the domains of
  the architecture (business, data, technology,
  investments etc.)
• Blueprint is a mechanism for DOI to contribute
  efficiently to an inter-agency WF EA.

7
Fire Systems In DEAR
External Government Services
E-Government
Contracted Services
Administrative Services
Forest Service Systems
State Systems
8
Wildland Fire Line of Business (LOB)
Modernization Blueprint Background
9
So what is a Blueprint and Where are we?
E-GOV Team Approved Approach in November 03
DOI Architect Started Here! Got Methodology in
place and approved
1. Establish Methodology for Defining
Modernization Blueprint.
Modernization blueprints a related set of
tactical and strategic modernization
recommendations.
DOI Senior Management identified LOB... Wildland
Fire Data Collected
IEA Team is publishing and vetting the
recommendations
DOI Architecture Teams put DEAR in Place
2. Determine Scope of Assessment and Collect Data
4. Develop Tactical and Strategic Modernization
Blueprints
Department Enterprise Architecture Repository (DEA
R)
IEA Team Has Analyzed and aligned information
3. Assess Alignment With FEA and DOI Architectures
The Department Enterprise Architecture Repository
(or DEAR) will be the system of record for
critical EA information.
10
History As-Is Data Collection

• Sources used to help create System As-Is
• NWCG Yellow Book
• Data Collection Tools and SME Interviews
• Available application repositories
• NWCG
• BLM, NPS, USFS
• Frames etc
• Investments (Exhibit 300 and 300-1)
• Security Asset Valuation Guides (AVG)
• Web searches
• System and Project Documentation

11
History As-Is Data Collection

• Built Draft Business Reference Model (BRM)
• Derived from
• OMB BRM, DOI ABC models, Yellow Book
• DOI Wildland Fire BRM Version 1.0
• Deliverable from DOI Mod. Blueprint Meeting in
  April
• Data Architecture
• Derived From Yellow Book
• Used artifacts from the Blueprint team

12
History Data Validation

• Review session with SME held at NIFC in March
• Business Model Review -- Facilitated development
  of Fire BRM.
• System Description and Relationship Review
• Investment Review

13
History WF Architecture Repository

• Created the WF Architecture Repository to store
  data, relationships to FEA, and to conduct
  analysis reporting.

14
History EA Analysis and FEA Alignment

• Loaded As-Is Information into the DEAR
• Business Reference Model (BRM)
• Data Reference Model (DRM)
• Performance Reference Model (PRM- DOI Strategic
  Plan)
• Systems and Investments
• Data
• Technologies and Services (TRM and SRM)
• Deployment Information
• System Interface Diagrams
• Classified all information in FEA taxonomy
• Related the artifacts within the model

15
History EA Analysis Reports

• As-Is Reports Published in Jan 2004
• Generated As-Is Text Reports from DEAR
• Provides views of relationships
• System to technology
• Technology to System
• Investment to Business
• Performance to Investment
• System Lists
• Technology Lists
• Generated As-Is Graphical Reports
• Provide Graphical Views
• Business Model
• Performance Model
• Data
• System Interfaces
• System Architectures
• No Comments Received on DOI Wildland Fire
  Modernization Blueprint As-Is Report

16
Systems are assessed against established criteria
then classified
Business Architecture
Data Architecture
Technology Architecture
Application Architecture

• Extent to which the system complies with current
  security requirements
• Extent of progress through the CA process.

Security Architecture
System Assessment

• Degree of architectural compliance with the
  Target Architecture.
• Extent to which system design requirements are
  defined and documented
• Extent to which systems interfaces are defined
  and documented
• Extent to which high-level design or operational
  concepts are defined.

• Systems capability for supporting associated
  Strategic goals and objectives as defined in DOI
  Strategic Plan.
• Extent of stakeholders feedback for accomplishing
  performance measures associated with strategic
  goals, objectives and performance measures.
• Lack of functional overlap with other systems as
  defined by DOI BRM.
• System incorporates re-engineered/streamlined
  business processes (workflow) in an automated
  fashion that supporting DOI Strategic goals and
  objectives.

• Existence and documentation of data standards
  and Protocols
• Relative maturity and accessibility of system's
  data storage and access methods
• Relative overlap with data stored in other
  Interior systems .

• Extent of maximum use of shared, existing
  infrastructure components and services
• Extent of compliance with Technology Reference
  Model standards, protocols and best practices.

DRM
SRM / CBA
TRM
PRM / BRM
The modeling of DOI enterprise architecture
elements and their relationship to assessment
criteria facilitates line of sight analyses.
Popkin SA is used to model the relationship
between inputs, outputs, and outcomes. Model
queries and analyses support the assessment
process
17
History Assessment and Alignment

• Scored systems against DOI approved Methodology
  criteria
• Mined all domains of information for
• Redundancies
• Gaps
• Obsolescence
• Internal Alignments
• Evaluate E-Gov connections

18
History Assessment of Business and Tech Fit
19
Development of the DOI Blueprint

• The DOI Fire Blueprint has been created to
  effectively prepare DOI for its contribution to
  the inter-agency Wildland Fire Architecture.
• The DOI Fire Blueprint includes a series of
  findings and recommendations that will better
  prepare DOI to be a more effective partner in
  meeting the Federal Fire mandate.

20

• DOI Draft Wildland Fire Findings and
  Recommendations

21
Finding 1

• Finding Many Fire related applications enable
  the same or similar business functions in the
  current architecture. Furthermore, many of the
  existing applications require similar data sets.
  The current architecture does not promote the
  re-usability of data and technology through
  horizontal services.
• Recommendations
• Investigate existing horizontal services within
  DOI and services being introduced within the next
  12 months
• Retire systems that are redundant with available
  horizontal services within DOI or other partner
  Departments
• Market to other business areas the data that Fire
  maintains as the source of record. Provide
  master data records to customer business areas
  like Recreation.

22
Current State Geographic Information System
(GIS) Services built into Specific Applications
IAMS
WildCad
NFPORS
Point to Point connections and Interfaces
23
GIS Service-Oriented Architecture (SOA)
ROSS
Fire Modeling
FPA
Future Applications Will take advantage of common
services, technologies and information
Common GISServices
Multiple Existing Systems Capabilities Collapse
to common services
24
Finding 2

• Finding The overall systems architecture and
  business enablement for the Fire program is
  difficult to manage due to incomplete accounting
  of the systems portfolio within the CPIC process.
• Recommendations
• Account for all IT systems within the CPIC
  process to ensure mission and technology
  compatibility as well as functional significance.
• Establish a cross-organizational IT portfolio to
  ensure that investments are appropriate within
  the Federal Fire mission context in addition to
  the organizational context.
• Incorporate full IT System Portfolio Reviews as a
  part of the Investment Cycle

25
Finding 3

• Finding The business area is not currently
  supported by a Systems Engineering organization
  that is integrated into the investment and system
  development life cycles. This missing
  engineering component increases the risk of a
  fragmented target architecture and increased
  long-term system development dollars and OM
  costs.
• Recommendations
• Implement a Systems Engineering (SE) organization
  that impacts early in the development of business
  cases and system development (particularly
  requirements development and pre-acquisition.
• Focus the SE organization on requirements
  management, risk assessment of baseline issues,
  technology evaluations, system designs and
  interface designs.
• Encourage the SE organization to embrace a
  framework (e.g. CMMI) to guide development and
  incremental improvements

26
Finding 3 Details
The Systems Engineering organization could be
used to solve existing service redundancy issues.
The Fire Community has many systems that feature
help desk and self-help capabilities. The
Systems Engineering organization would be
instrumental in consolidating these redundant
capabilities and integrating the future state
Help Desk service with the legacy systems and
processes.
27
Finding 3 Details
The Systems Engineering organization could be
used to solve existing desktop interoperability
issues.

• Investigate the use of thin client hosting
  services to simplify Desktop Interoperability and
  distributed security issues.
• Migrate legacy desktop client server applications
  and O/A to server-based computing model
• Develop Hosting services for deployed Fire
  Support base where network capacity permits
• Create a common desktop image per user role
• Install simulators and client software, bureau
  specific software such as Time and Attendance
• Put this image on a server accessible via VPN
• Backup Put image onto CD/DVD/flash drive for
  disconnected users

28
Finding 4

• Finding Within the Fire organizations, there
  are a fixed number of business functions that are
  enabled through a multitude of systems and
  technologies. In many instances, a single
  function is enabled by more than one system. In
  other instances, critical systems are not
  interfaced appropriately to other dependent
  systems.
• Recommendations
• Identify systems with functional overlap (map to
  the BRM)
• Sunset redundant systems where investment
  justifications are not approved
• Leverage Department level middleware standards to
  implement an EAI approach to data exchange
• Leverage the ESN initiatives improvements to DOI
  infrastructure to better support the enabling
  systems

29
Finding 4 Details

• Systems with Functional Overlaps
• The following systems have functional overlaps.
  Alaska has specialized needs that could be met
  through a standard solution with an Alaska
  specific instance.
• Alaska Fire Service Fire Weather Database
• Alaska Fire Stores
• Alaska Lightning Detection
• Utah Wild Fire Attack Dispatch Application
• Alaska Teletype System
• WILDCAD
• FMIS
• GBOCOO
• FireBase
• ICECAP

30
Finding 4 Details

• System Interface Challenges
• System to system interfaces result in redundant
  data sets, inconsistent data, single use
  interfaces, increased costs
• ASCADs
• GIS data stores
• Effpay
• The lack of critical interfaces results in manual
  data entry, duplicative data collections efforts,
  and inconsistent decision making
• Double keying of critical information
• FireCode

31
Finding 4 Details Current Interface Model
32
Finding 5

• Finding The existing Geo-Spatial architecture
  includes solutions that need to be integrated,
  some solution redundancy, and a lack of data
  standards, data quality, and data collection
  standards.
• Recommendation The Fire community should be a
  customer of the Geo-Spatial service provider
  organization much like other business areas such
  as Recreation. As a result, the Fire community
  should be a key customer participant in future
  Geo-Spatial focused modernization studies.

33
Finding 6

• Finding Much of the Fire related information is
  distributed through regions and by projects and
  activities. This has resulted in a de facto
  disparate information access model that makes it
  challenging to access integrated decision making
  information.
• Although there has been movement towards
  centralization, there is still vast amounts of
  duplicate data
• INCIDENT Situation Information
• TRAINING
• ORGANZATIONAL
• ANALYTICAL
• Forms
• Aviation etc
• Difficult to find all the good work that is being
  done throughout the organization
• Need for true Portal and content management
  strategy with dual focus
• Internal Work force oriented NON
  Organizational view
• Citizen Centric.

34
Finding 6

• Recommendation
• Implement a Portal based architecture to
• Reduce content management cost
• Reduce risks of inaccurate information
• Provide a new access model
• Support basic business processes and application
  access

35
Next Steps for DOI Blueprint

• Provide Outreach to Wildland Fire Community
  (today)
• Publish Report on 10/8 with IBAT and ARB
  briefings in parallel. Final business briefings
  on 11/1 in preparation for IRB on 11/17.
• Three week comment and review cycle (starts at
  publishing of report)

36
Questions?