Forest Service Enterprise Data Warehouse (EDW) -- PROJECT -- - PowerPoint PPT Presentation

1 / 20
About This Presentation
Title:

Forest Service Enterprise Data Warehouse (EDW) -- PROJECT --

Description:

Enterprise Data Warehouse (EDW) ... environment May through August Testing July/August Moved into Enterprise Data Center September/October Training, ... – PowerPoint PPT presentation

Number of Views:170
Avg rating:3.0/5.0
Slides: 21
Provided by: usdafores1
Category:

less

Transcript and Presenter's Notes

Title: Forest Service Enterprise Data Warehouse (EDW) -- PROJECT --


1
Forest ServiceEnterprise Data Warehouse (EDW)--
PROJECT --
  • Bill Wettengel
  • Andy Peavy

2
Presentation Outline
  • What is the Enterprise Data Warehouse (EDW)
  • How and where is it being created
  • What will it do
  • What wont it do
  • What really cool future does the EDW lead the
    Agency to

3
What is a Data Warehouse?The Wikipedia Version
  • A centralized repository
  • Provides a common data model regardless of the
    data's source
  • Designed and tuned to facilitate reporting and
    analysis (OLAP)
  • Data is transformed or summarized to a consistent
    standard
  • Data is formatted for easier retrieval
  • Separates use from transactional systems and
    workflows

4
What Does Warehousing Mean to FS
  • Stop the one size fits all or the square peg in
    the round hole syndrome (Transactional vs
    Reporting)
  • A place to more easily support data standards for
    reporting and analysis
  • An easier way to provide quality data to the
    public
  • Provides foundational data to do our business

5
Enterprise Data WarehouseFeeds Many Uses
6
EDW Project Highlights
  • Deep roots
  • IT data management best practices
  • FSNRA Published Data Mart prototype
  • IBE Enterprise Reporting and Analysis (I-6)
  • Part of EDC architecture
  • Fits within CIO/ISO priorities
  • Ties to existing efforts like CDW (IWeb)
  • Project team with many ties to others
  • Iterative or phased approach
  • Focused on standard data

7
EDW RecommendationsIBE Issue 6
  • Establish a limited scope Enterprise Data
    Warehouse (EDW)
  • Focus on standard data (e.g., GIS Data
    Dictionary)
  • Establish an EDW governance process
  • Establish agency wide authentication and
    authorization
  • Improve coordination among agency programs that
    need warehouse technology
  • Develop the requirements to guide selection of a
    standardized toolset for data warehousing (ETL
    and Business Intelligence Tools)

8
EDW Phase I Project Objectives
  • Establish EDW at the EDC
  • Establish a spatial Extract Transform and Load
    (ETL) Process
  • Data must be regularly updated (Timed Jobs)
  • Allow data to be available to public
  • Establish EDW governance
  • Support GIS Data Dictionary standards
  • Document requirements for enterprise Business
    Intelligence (BI) tool
  • Establish agency wide authentication and
    authorization to guide access to the EDW
    environment

9
EDW Deliverables Highlights
  • Follow standard project management process
  • Data warehouse governance proposal to management
  • Draft EDW governance board charter
  • Training plan and materials
  • Documented data sources and data map (ETL)
  • EDW deployed to PHE and EDC
  • Approved set of data residing in the EDW at the
    EDC
  • Deployed user interface(s) at PHE and EDC (Tied
    to eGIS Web Services)

10
EDW Iteration IWill Be
  • Established in the Enterprise Data Center
  • Built using Agency IT direction
  • A collection of spatial and related attribute
    data
  • Easy to use for general query and display
  • Direct Access to the Data
  • Fat and Flat
  • Extracted Transformed and Loaded (ETL) from
    complex transactional data
  • The foundation for other uses to follow
  • Beginning of enterprise warehouse
  • Support and management put in place
  • Tied to eGIS Web Services effort

11
EDW Project Timeline Highlights
  • Initiated in February
  • TAG Architecture Approval April
  • Requirements finished end of April
  • Development (PHE) environment May through August
  • Testing July/August
  • Moved into Enterprise Data Center
    September/October
  • Training, Communications and Marketing
    October/November Time Frame

12
What Does it Look Like?
13
What Does it Look Like?
14
What Does it Look Like?Geospatial Interface (GI)
15
What Does it Look Like? Web Service
  • Easy and direct linkage to data at EDW
  • Better performance then SDE connections
  • Specific data can be made accessible to public

16
EDW Phase I Limitations
  • We are focused on the data
  • Web Services or interfacing need to be
    established outside of this project (i.e., GI,
    eGIS)
  • In some cases you need to know how to deal with
    the data
  • National or Regional data extents
  • Single Projection (eGIS Direction) will be used
  • Data issues need to be dealt with somewhere else
    (Transactional side)
  • Phase I will only focus on spatial data
  • Tabular data structures (Star Schema, OLAP Cube,
    etc) and Reporting (BI) will need to be
    developed in future Phases

17
EDW Future
  • More direct use of Web Services (eGIS Lead)
  • More than just spatial
  • Data structures designed for output performance
  • Agency BI tools for more robust analysis
  • Other tools can rely on the data to add value
    (e.g., GI)
  • More timely and robust public access to our data
  • Much easier to produce products and/or standards
    to meet business needs
  • Rapid adjustments means small changes to ETL
    process

18
Greater Information Use
19
EDW Communication Plan Summary
  • Keep management and interested communities
    informed
  • Communicate as we make progress
  • Take advantage of the situation
  • Geospatial 09, existing call, briefing, etc
  • Document outcomes
  • Lessons learned, process, requirements,
    recommendation, etc
  • Improve cooperation through info sharing

20
EDW Web Site
  • http//fsweb.ftcol.wo.fs.fed.us/IBE/Enterprise_Rep
    orting/EDWProject.shtml
Write a Comment
User Comments (0)
About PowerShow.com