data architecture why tools are not enough

15
Data Architecture Why Tools are Not Enough Dan Hooper, Principal, ISI

Upload: innotech

Post on 13-May-2015

197 views

Category:

Business


0 download

DESCRIPTION

Presented at InnoTech Dallas 2014. All rights reserved.

TRANSCRIPT

Page 1: Data Architecture Why Tools Are Not Enough

Data ArchitectureWhy Tools are Not

Enough Dan Hooper, Principal, ISI

Page 2: Data Architecture Why Tools Are Not Enough

What’s Wrong.

What’s Offered.

What’s Needed.

Demo.

Q&A.

Agenda

Page 3: Data Architecture Why Tools Are Not Enough

Data’s purpose?

profit

What’s Wrong?

Page 4: Data Architecture Why Tools Are Not Enough

Leading issues with data:

1. Integrity.

2. Security.

3. Disparate.

4. IT.

5. Intelligence.

6. Latency.

7. Growth (complexity, volume).

What’s Wrong?

Page 5: Data Architecture Why Tools Are Not Enough

State of the Market…

1. 36% have what they need (format, time, access).

2. 66% have shrinking decision window.

3. Average time to market (new data, dashboards, ad hoc): Leaders 4-5 days Followers 19 – 55 days

4. Single, centralized BI platform: Leaders 80% Followers 41%

5. Self-Service capabilities (create, configure, collaborate): Leaders 63% Followers 28%

6. Actionable BI, outcome manageable: Leaders 74% Followers 39%

Aberdeen Group, June 2013

Page 6: Data Architecture Why Tools Are Not Enough

What’s Offered

Page 7: Data Architecture Why Tools Are Not Enough

What’s Needed

BI 1.0 BI 2.0

Software Driven Architecture Driven

Views/VirtualizationIntegration + Business

Logic

What Tool ? What Decisions ?

Proprietary/Specialists Common Standards

Managed Development Managed Content

Static Data Model, Views Dynamic Data Model

Redundant Automated

Governance? Governed

Page 8: Data Architecture Why Tools Are Not Enough

What’s Needed

BI Consumption

Cap

acity

for

Ana

lysi

s

ApplicationsBI 1.0

ArchitectedBI 2.0

Subscribers

Page 9: Data Architecture Why Tools Are Not Enough

Now that I think about it…

BI consumers more self-sufficient?

Ad hoc requests dropped?

Multiple versions of the truth?

Ready for growth in data complexity, volume and demand?

Reliance on manual Excel processes or tribal knowledge?

Costs and complexity?

Develop

Test

Deploy

What’s Needed

Page 10: Data Architecture Why Tools Are Not Enough

Data Strategy

What’s Needed

Data Governance

Primary Owners – LOB

Data Architecture

Primary Owners – IT

Page 11: Data Architecture Why Tools Are Not Enough

Data Architecture

1. LOB Requirements (from Governance Model).

2. Enterprise Data Model.a. Data Sources.b. Security.c. Terminology.d. Key Measures & Standards.e. Growth & change.f. Business Logic.g. System Controls & Interfaces.

3. Development Plan.

What’s Needed

Page 12: Data Architecture Why Tools Are Not Enough

What’s Needed

Page 13: Data Architecture Why Tools Are Not Enough

Consider the ODS – Operational Data Store

Realization of Enterprise Data Model.

True source of Operational BI (C-Level focus).

Time & cost to market.

BI is Content Managed, not Development Managed.

Security and Data Integrity.

Change Control and Integration Hub.

What a Tool needs, what larger audience wants.

What’s Needed

Page 14: Data Architecture Why Tools Are Not Enough

Demo

What’s Needed

Page 15: Data Architecture Why Tools Are Not Enough

Dan Hooper Lori AdamsPrincipal, Sales & Marketing VP, SalesIntegrated Services, Inc. Integrated Services, Inc.

[email protected] [email protected]

1. DFW Business Intelligence User Community.

2. DFW SharePoint User Community.

3. ISI Data Strategy Session (off the clock).

Next Steps & Resources