Data Architecture Why Tools Are Not Enough

  • 133 views
Uploaded on

Presented at InnoTech Dallas 2014. All rights reserved.

Presented at InnoTech Dallas 2014. All rights reserved.

More in: Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
133
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
12
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Data Architecture Why Tools are Not Enough Dan Hooper, Principal, ISI
  • 2. What’s Wrong. What’s Offered. What’s Needed. Demo. Q&A. Agenda
  • 3. Data’s purpose? profit What’s Wrong?
  • 4. Leading issues with data: 1. Integrity. 2. Security. 3. Disparate. 4. IT. 5. Intelligence. 6. Latency. 7. Growth (complexity, volume). What’s Wrong?
  • 5. 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
  • 6. What’s Offered
  • 7. What’s Needed BI 1.0 BI 2.0 Software Driven Architecture Driven Views/Virtualization Integration + 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
  • 8. What’s Needed BI Consumption CapacityforAnalysis Applications BI 1.0 Architected BI 2.0 Subscribers
  • 9. 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? What’s Needed
  • 10. Data Strategy What’s Needed Data Governance Primary Owners – LOB Data Architecture Primary Owners – IT
  • 11. 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
  • 12. What’s Needed
  • 13. 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
  • 14. Demo What’s Needed
  • 15. Dan Hooper Lori Adams Principal, Sales & Marketing VP, Sales Integrated Services, Inc. Integrated Services, Inc. dhooper@isi85.com ladams@isi85.com 1. DFW Business Intelligence User Community. 2. DFW SharePoint User Community. 3. ISI Data Strategy Session (off the clock). Next Steps & Resources