540 likes | 678 Views
Establishing an Enterprise-wide Data Warehousing Strategy. By Michael G. Miller National Director - Enterprise Intelligence Butler Technology Solutions mgmiller@butler.com. Agenda. Introduction Current State of Data Warehousing Current Problems / Potential Solution
E N D
Establishing an Enterprise-wide Data Warehousing Strategy By Michael G. Miller National Director - Enterprise Intelligence Butler Technology Solutions mgmiller@butler.com
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 Solutions • Enterprise Relationship Management • E-Commerce • Enterprise Intelligence • Enterprise Network Solutions • Network Design, Construction, Operation, Assessment, etc. • Quality Assurance Solutions • Testing – Automated, Manual, Performance, etc. • Staff Augmentation Solutions
Butler Technology Solutions Clients • American Re-Insurance • Avon • Banc One • Bell South/RAM • Citigroup • Chase • Estee Lauder • First Data • IBM • JP Morgan • John Hancock • MCI • Merrill Lynch • Prudential • Solomon Smith Barney • UPS
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 nothing to do with the technology-they have to do with delivering value to the users, maintaining the data warehouse, and shifting from a transaction-processing to a decision support mindset.” - Larry Greenfield Datamation, 3/1/96
Original ProblemOperational System Stovepipes M a r k e t i n g I n v e n t o r y A c c o u n t i n g M a i n t e n a n c e H u m a n R e s o u r c e s P r o d u c t i o n S a l e s R & D F i n a n c e T r a n s p o r t a t i o n
Data Warehouse Stovepipes 90 Day Data Warehouse 30 Day ODS M a r k e t i n g I n v e n t o r y A c c o u n t i n g M a i n t e n a n c e H u m a n R e s o u r c e s P r o d u c t i o n S a l e s R & D F i n a n c e T r a n s p o r t a t i o n 15 min. Data Mart
Current Problems • Stove Pipe Data Warehouses • Stove Pipe Data Marts • Stove Pipe ODSs • Results in “Islands of Information”
Islands of Information Marketing DM ISLAND Financial DM Island Customer ODS Island Product DW Island
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… • “Where are you today?” & • “Where do you want to be tomorrow?” • “What is the gap between where you are today & where you want to be tomorrow? • 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.
Enterprise Architecture – A Framework TIME MOTIVATION PEOPLE DATA What FUNCTION How NETWORK Where Who When Why List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE SCOPE to the Business Business Performs the Business Operates to the Business Important to the Business (CONTEXTUAL) (CONTEXTUAL) Planner Function = Class of Ends/Means=Major Bus. Goal/ ENTITY = Class of Node = Major Business Planner People = Major Organizations Time = Major Business Event Business Process Critical Success Factor Business Thing Location e.g. Master Schedule e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Business Plan ENTERPRISE ENTERPRISE System MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) Owner Owner Ent = Business Entity Proc. = Business Process Node = Business Location End = Business Objective People = Organization Unit Time = Business Event Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM Architecture Architecture MODEL MODEL (LOGICAL) (LOGICAL) Node = I/S Function Ent = Data Entity Proc .= Application Function Time = System Event People = Role End = Structural Assertion (Processor, Storage, etc) Designer Designer Cycle = Processing Cycle Reln = Data Relationship I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Control Structure e.g. Rule Design e.g. Presentation Architecture TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) (PHYSICAL) Node = Hardware/System Builder Ent = Segment/Table/etc. Proc.= Computer Function End = Condition Builder People = User Time = Execute Software Reln = Pointer/Key/etc. I/O = Data Elements/Sets Cycle = Component Cycle Means = Action Link = Line Specifications Work = Screen Format DETAILED e.g. Security Architecture e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- REPRESEN- TATIONS TATIONS (OUT-OF (OUT-OF- CONTEXT) CONTEXT) Sub- Sub- End = Sub-condition Contractor Proc.= Language Stmt Ent = Field Node = Addresses Time = Interrupt People = Identity Contractor Cycle = Machine Cycle Reln = Address I/O = Control Block Link = Protocols Work = Job Means = Step FUNCTIONING FUNCTIONING e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY ENTERPRISE ENTERPRISE John A. Zachman, Zachman International (810) 231-0531 TM
Enterprise Architecture – A Framework TIME MOTIVATION PEOPLE DATA What FUNCTION How NETWORK Where Who When Why List of Things Important List of Processes the List of Locations in which List of Organizations List of Events Significant List of Business Goals/Strat SCOPE SCOPE to the Business Business Performs the Business Operates to the Business Important to the Business (CONTEXTUAL) (CONTEXTUAL) Planner Function = Class of Ends/Means=Major Bus. Goal/ ENTITY = Class of Node = Major Business Planner People = Major Organizations Time = Major Business Event Business Process Critical Success Factor Business Thing Location e.g. Master Schedule e.g. Semantic Model e.g. Business Process Model e.g. Business Logistics e.g. Work Flow Model e.g. Business Plan ENTERPRISE ENTERPRISE System MODEL MODEL (CONCEPTUAL) (CONCEPTUAL) Owner Owner Ent = Business Entity Proc. = Business Process Node = Business Location End = Business Objective People = Organization Unit Time = Business Event Reln = Business Relationship I/O = Business Resources Link = Business Linkage Work = Work Product Cycle = Business Cycle Means = Business Strategy e.g. Logical Data Model e.g. Application Architecture e.g. Distributed System e.g. Human Interface e.g. Processing Structure e.g., Business Rule Model SYSTEM SYSTEM Architecture Architecture MODEL MODEL (LOGICAL) (LOGICAL) Node = I/S Function Ent = Data Entity Proc .= Application Function Time = System Event People = Role End = Structural Assertion (Processor, Storage, etc) Designer Designer Cycle = Processing Cycle Reln = Data Relationship I/O = User Views Link = Line Characteristics Work = Deliverable Means =Action Assertion e.g. Physical Data Model e.g. System Design e.g. Technology Architecture e.g. Control Structure e.g. Rule Design e.g. Presentation Architecture TECHNOLOGY TECHNOLOGY MODEL MODEL (PHYSICAL) (PHYSICAL) Node = Hardware/System Builder Ent = Segment/Table/etc. Proc.= Computer Function End = Condition Builder People = User Time = Execute Software Reln = Pointer/Key/etc. I/O = Data Elements/Sets Cycle = Component Cycle Means = Action Link = Line Specifications Work = Screen Format DETAILED e.g. Security Architecture e.g. Data Definition e.g. Program e.g. Network Architecture e.g. Timing Definition e.g. Rule Specification DETAILED REPRESEN- REPRESEN- TATIONS TATIONS (OUT-OF (OUT-OF- CONTEXT) CONTEXT) Sub- Sub- End = Sub-condition Contractor Proc.= Language Stmt Ent = Field Node = Addresses Time = Interrupt People = Identity Contractor Cycle = Machine Cycle Reln = Address I/O = Control Block Link = Protocols Work = Job Means = Step FUNCTIONING FUNCTIONING e.g. DATA e.g. FUNCTION e.g. NETWORK e.g. ORGANIZATION e.g. SCHEDULE e.g. STRATEGY ENTERPRISE ENTERPRISE John A. Zachman, Zachman International (810) 231-0531 TM
Column 6 – Motivation (Why?) • ‘List of Major Business Goals/Strategies/ Critical Success Factors’ John A. Zachman
Column 6 – Motivation (Why?) • What are the current major… • Business Goals? • Business Strategies? • Critical Success Factors? • Compensation Methods?
Column 6 – Motivation (Why?) • What are the future major… • Business Goals? • Business Strategies? • Critical Success Factors? • Compensation Methods?
Column 6 – Motivation (Why?) • What is the gap between the current & future major… • Business Goals? • Business Strategies? • Critical Success Factors? • Compensation Methods?
Column 6 – Motivation (Why?) • 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
Column 2 – Function (How?) • How do you intend to do what you do? (future) • Future Functions • Future Processes
Column 2 – Function (How?) • What is the gap between today's & tomorrow’s functions and processes?
Column 2 – Function (How?) • 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
Column 4 - People (Who?) • 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.
Column 4 - People (Who?) • 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.
Column 4 - People (Who?) • 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?
Column 4 - People (Who?) • Can you bridge the gap between today's & tomorrow’s organizations for EDW in the allotted time?
Column 4 -Who is your Customer? Executive Management Focus: Long Range (1 year +) Perspective: External & Future STRATEGIC Middle Management Focus: Mid Range (30days to 1yr.) Perspective: External/Internal & Recent Past TACTICAL Operations Focus: Short Range (1-30 days) Perspective: Internal & Now OPERATIONAL
Column 1 – Data (What?) • “List of Things Important to the Business” John A.Zachman
Column 1 – Data (What?) • What current things are important to the business? • Customers/Markets • Products/Services • Suppliers • Money • Employees
Column 1 – Data (What?) • What future things are important to the business? • Customers/Markets • Products/Services • Suppliers • Money • Employees
Column 1 – Data (What?) • What is the gap between today's & tomorrow’s data?
Column 1 – Data (What?) • 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
Column 5 – Time (When?) • 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.
Column 5 – Time (When?) • 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.
Column 5 – Time (When?) • What is the gap between current & future significant events/cycles? (Rate of Change)
Column 5 – Time (When?) • 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
Column 3 – Network (Where?) • 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.
Column 3 – Network (Where?) • 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.
Column 3 – Network (Where?) • What is the gap between today's & tomorrow’s locations?
Column 3 – Network (Where?) • 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