Establishing an Enterprise-wide Data Warehousing Strategy By Michael G. Miller National Director - Enterprise Intelligence Butler Technology Solutions

Establishing an Enterprise-wide Data Warehousing Strategy

By Michael G. Miller National Director - Enterprise Intelligence

Butler Technology Solutions

[email protected]

Agenda

• Introduction

• Current State of Data Warehousing

• Current Problems / Potential Solution

• Establishing the EDW Strategy

Utilizing the Zachman Framework

• Questions & (hopefully) Answers

Butler International

Today, through our 50 offices,

6200 Butler employees serve

over 1600 client companies

worldwide.

Butler Awards

Arthur Andersen’s 1998 International Best Practices Award, one of top three companies worldwide in Exceeding Customer Expectations, and number one regionally.

New Jersey Technology Council Award for Customer Service Company of the Year in 1998

Internet Business Network Award, ranked as one of the top 6 Third Party Recruiting Web Sites in 1998

Butler Technology Solutions Areas of Expertise

• Enterprise Applications SolutionsEnterprise Applications Solutions– Enterprise Relationship Management– E-Commerce– Enterprise Intelligence

• Enterprise Network SolutionsEnterprise Network Solutions– Network Design, Construction, Operation, Network Design, Construction, Operation,

Assessment, etc.Assessment, etc.• Quality Assurance SolutionsQuality Assurance Solutions

– Testing – Automated, Manual, Performance, etc.Testing – Automated, Manual, Performance, etc.• Staff Augmentation SolutionsStaff Augmentation Solutions

Butler Technology Solutions Clients

American Re-InsuranceAvonBanc OneBell South/RAMCitigroupChaseEstee LauderFirst Data

IBMJP MorganJohn HancockMCIMerrill LynchPrudentialSolomon Smith BarneyUPS

Current State of Data Warehousing

• Good news & bad news– The good news…

• Data Warehouse is no longer considered bleeding edge or leading edge technology.

• It is now considered a main stream technology and in many cases, a mission critical technology.

– The bad news…• Data Warehouse is no longer considered bleeding edge or

leading edge technology.

• It is now considered a main stream technology and in many cases, a mission critical technology.

Current State of Data Warehousing

• More bad news…– In many organizations,

Data Warehouse is thought of as just another application development effort,

rather than,

as a whole new platform or whole new environment, separate & distinct from the operational systems.

Enterprise Data Warehouse Construction...

...the toughest data warehousing problems have nothingto do with the technology-they have to do with delivering valueto the users, maintaining the data warehouse, and shifting froma transaction-processing to a decision support mindset.” - Larry Greenfield

Datamation, 3/1/96

Original ProblemOperational System Stovepipes

Marketing

Sales

Accounting

Finance

Transportation

R&D

Maintenance

Production

Inventory

Human

Resources

Data Warehouse Stovepipes

Marketing

Sales

Accounting

Finance

Transportation

R&D

Maintenance

Production

Inventory

Human

Resources

Current Problems

• Stove Pipe Data Warehouses

• Stove Pipe Data Marts

• Stove Pipe ODSs

• Results in “Islands of Information”

Islands of Information

3 Stages of Data Warehousing

• Stage 1 – Reporting

• Stage 2 – OLAP

• Stage 3 – Data Mining

Strategy & Architecture

• Microsoft says “Where do you want to go today?” I say…

1. “Where are you today?” &

2. “Where do you want to be tomorrow?”

3. “What is the gap between where you are today & where you want to be tomorrow?

4. Can you bridge that gap in the time allotted?

Utilizing the Zachman Framework

• Now..– Identify a Enterprise Data Warehouse strategy

to successfully bridge the gap & set your direction,

– Using the Zachman Enterprise Architecture Framework as a vehicle for communication.

TM

e.g. DATA

Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer

SYSTEMMODEL(LOGICAL)

TECHNOLOGYMODEL(PHYSICAL)

DETAILEDREPRESEN- TATIONS(OUT-OF- CONTEXT)

Sub-Contractor

FUNCTIONINGENTERPRISE

DATA FUNCTION NETWORK

e.g. Data Definition

Ent = FieldReln = Address

e.g. Physical Data Model

Ent = Segment/Table/etc.

Reln = Pointer/Key/etc.

e.g. Logical Data Model

Ent = Data EntityReln = Data Relationship

e.g. Semantic Model

Ent = Business EntityReln = Business Relationship

List of Things Importantto the Business

ENTITY = Class ofBusiness Thing

List of Processes theBusiness Performs

Function = Class ofBusiness Process

e.g. Application Architecture

I/O = User ViewsProc .= Application Function

e.g. System Design

I/O = Data Elements/Sets

Proc.= Computer Function

e.g. Program

I/O = Control BlockProc.= Language Stmt

e.g. FUNCTION

e.g. Business Process Model

Proc. = Business ProcessI/O = Business Resources

List of Locations in which the Business Operates

Node = Major BusinessLocation

e.g. Business Logistics System

Node = Business LocationLink = Business Linkage

e.g. Distributed System

Node = I/S Function(Processor, Storage, etc)Link = Line Characteristics

e.g. Technology Architecture

Node = Hardware/SystemSoftware

Link = Line Specifications

e.g. Network Architecture

Node = AddressesLink = Protocols

e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING

MOTIVATIONTIMEPEOPLE

e.g. Rule Specification

End = Sub-condition

Means = Step

e.g. Rule Design

End = Condition

Means = Action

e.g., Business Rule Model

End = Structural AssertionMeans =Action Assertion

End = Business ObjectiveMeans = Business Strategy

List of Business Goals/Strat

Ends/Means=Major Bus. Goal/Critical Success Factor

List of Events Significant

Time = Major Business Event

e.g. Processing Structure

Cycle = Processing CycleTime = System Event

e.g. Control Structure

Cycle = Component CycleTime = Execute

e.g. Timing Definition

Cycle = Machine CycleTime = Interrupt

e.g. SCHEDULE

e.g. Master Schedule

Time = Business EventCycle = Business Cycle

List of Organizations

People = Major Organizations

e.g. Work Flow Model

People = Organization UnitWork = Work Product

e.g. Human Interface

People = RoleWork = Deliverable

e.g. Presentation Architecture

People = UserWork = Screen Format

e.g. Security Architecture

People = IdentityWork = Job

e.g. ORGANIZATION

Planner

Owner

to the BusinessImportant to the Business

What How Where Who When Why

John A. Zachman, Zachman International (810) 231-0531

SCOPE(CONTEXTUAL)

Architecture

e.g. STRATEGYENTERPRISE

e.g. Business Plan

Enterprise Architecture – A Framework

TM

e.g. DATA

Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer




Sub-Contractor










e.g. Semantic Model








e.g. System Design



e.g. Program


e.g. FUNCTION














e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING



End = Sub-condition

Means = Step

e.g. Rule Design

End = Condition

Means = Action














e.g. SCHEDULE













e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

Enterprise Architecture – A Framework

Column 6 – Motivation (Why?)

• ‘List of Major Business Goals/Strategies/ Critical Success Factors’

John A. Zachman


• What are the current major…– Business Goals?– Business Strategies?– Critical Success Factors?– Compensation Methods?


• What are the future major…– Business Goals?– Business Strategies?– Critical Success Factors?– Compensation Methods?


• What is the gap between the current & future major…– Business Goals?– Business Strategies?– Critical Success Factors?– Compensation Methods?


• Can you bridge the gap between today's & tomorrow’s business goals, strategies, critical success factors in the time allotted?

Column 2 – Function (How?)


• How do you do what you do?– Current Functions– Current Processes


• How do you intend to do what you do? (future)– Future Functions– Future Processes


• What is the gap between today's & tomorrow’s functions and processes?


• Can you bridge the gap between today's & tomorrow’s functions & processes in the time allotted?

Column 4 - People (Who?)

• “List of Organizations important to the Business”

John A. Zachman


• Who are today’s organizations for EDW?– Who are the current …

• EDW champions?• EDW opponents?• EDW customers (users)?• EDW & general management?• EDW consultants?• EDW product vendors?• EDW other parties?

– Ex. Stockholders, Investors, Venture Capitalists, etc.


• Who are tomorrow’s organizations for EDW?– Who are the future …

• EDW champions?• EDW opponents?• EDW customers (users)?• EDW & general management?• EDW consultants?• EDW product vendors?• EDW other parties?

– Ex. Stockholders, Investors, Venture Capitalists, etc.


• What is the gap between today's & tomorrow’s organizations for EDW?– What is the gap between current & future…

• EDW champions?

• EDW opponents?

• EDW customers (users)?

• EDW & general management?

• EDW consultants?

• EDW product vendors?

• EDW other parties?


• Can you bridge the gap between today's & tomorrow’s organizations for EDW in the allotted time?

Column 4 -Who is your Customer?

OPERATIONAL

TACTICAL

STRATEGIC

OperationsFocus: Short Range (1-30 days)Perspective: Internal & Now

Middle ManagementFocus: Mid Range (30days to 1yr.)Perspective: External/Internal & Recent Past

Executive ManagementFocus: Long Range (1 year +)Perspective: External & Future

Column 1 – Data (What?)

• “List of Things Important to the Business”

John A. Zachman


• What current things are important to the business?– Customers/Markets – Products/Services– Suppliers– Money– Employees


• What future things are important to the business?– Customers/Markets – Products/Services– Suppliers– Money– Employees


• What is the gap between today's & tomorrow’s data?


• Can you bridge the gap between today's & tomorrow’s data in the time allotted?

Column 5 – Time (When?)

• “List of Events Significant”

John A. Zachman


• When do significant events/cycles currently occur?

• Ex. Data created, process occurs, location becomes operational, person hired, customer cancels order

• Ex. Merger, Acquisition, Divestiture, Web Site crash, Reorganization, Downsizing, Rightsizing, etc.

• Ex. Earthquake, hurricane, other acts of God.


• When will significant events/cycles occur in the future? (Faster, slower, not at all)

• Ex. Data created, process occurs, location becomes operational, person hired, customer cancels order

• Ex. Merger, Acquisition, Divestiture, Web site crash, Reorganization, Downsizing, Rightsizing, etc.

• Ex. Earthquake, hurricane, other Acts of Nature.


• What is the gap between current & future significant events/cycles? (Rate of Change)


• Can you bridge the gap between today's & tomorrow’s events / cycles in the time allotted?

Column 3 – Network (Where?)

• “List of Locations in which the Business Operates”

John A. Zachman


• Where are today’s …– Operations currently conducted?– Operations managed (from)? [Tactical Level]– Operations directed (from)? [Strategic Level]– Customers located?– Other stakeholders located?

• Ex. Regulators, Stockholders, EDW Consultants, etc.


• Where are tomorrow’s …– Operations to be conducted?– Operations to be managed (from)? [Tactical Level]– Operations to be directed (from)? [Strategic Level]– Customers located?– Other stakeholders located?

• Ex. Regulators, Stockholders, EDW Consultants, etc.


• What is the gap between today's & tomorrow’s locations?


• Can you bridge the gap between today's & tomorrow’s locations in the time allotted?

E.D.W. - S.W.O.T Analysis

• Internal View– Strengths

– Weaknesses

• External View– Opportunities

– Threats

Determine EDW Strategy

• JAD Strategy Sessions

• Document Strategy

• Begin to develop architecture

TM

e.g. DATA

Builder

SCOPE(CONTEXTUAL)

MODEL(CONCEPTUAL)

ENTERPRISE

Designer




Sub-Contractor










e.g. Semantic Model








e.g. System Design



e.g. Program


e.g. FUNCTION














e.g. NETWORK

Architecture

Planner

Owner

Builder

ENTERPRISEMODEL

(CONCEPTUAL)

Designer

SYSTEMMODEL

(LOGICAL)

TECHNOLOGYMODEL

(PHYSICAL)

DETAILEDREPRESEN-

TATIONS (OUT-OF

CONTEXT)

Sub-Contractor

FUNCTIONING



End = Sub-condition

Means = Step

e.g. Rule Design

End = Condition

Means = Action














e.g. SCHEDULE













e.g. ORGANIZATION

Planner

Owner




SCOPE(CONTEXTUAL)

Architecture


e.g. Business Plan

Enterprise Data Warehouse Architecture

Future Direction

• Think Business Information Portal…• Think XML• Think Wireless (any time, any where)

The End – Thank You

• Any further questions contact…

Michael G. Miller National Director - Enterprise Intelligence

Butler Technology Solutions

3601 Algonquin Road #323

Rolling Meadows, IL 60008

847-506-7456

[email protected]

Documents

Establishing an Enterprise-wide Data Warehousing Strategy By Michael G. Miller National Director - Enterprise Intelligence Butler Technology Solutions