Many organizations are frustrated with OBIEE. What they are looking for is an ideal tool which can replace OBIEE like for like and also provide great visualization, blending, data wrangling, and speed of change. But does such a tool exist in the market today?
A lot of organizations are looking towards Tableau and wondering if it can replace OBIEE entirely plus do what Tableau does best. In this presentation, we explore:
* What are your options after OBIEE?
* Is it possible to replace OBIEE with Tableau?
* Should OBIEE and Tableau co-exist?
* How BI Connector combines the best of Tableau and OBIEE to allow business users to gain Tableau visualization of OBIEE while repurposing the IT investment in OBIEE metadata model and security model.
4. Searching for an ideal solution
State of
OBIEE
Customers
Latest
Visualization
Data
Blending
Data
Wrangling
Speed of
Change
Like-for-like
replacement
6. First, Let us look at OBIEE’s Strengths
Metadata Repository aka RPD!
Also its Achilles’ heel.
7. CONFIDENTIAL – For use by Guidanz Inc employees and other audiences under NDA only.
Common Enterprise Model
The RPD Advantage
E
Physical Layer
Business Model &
Mapping Layer
Presentation Layer
OBIEE
8. CONFIDENTIAL – For use by Guidanz Inc employees and other audiences under NDA only.
The RPD Advantage
Well suited for IT led projects
12. Good for enterprise dashboards
• standardized dimensions, filters,
and metrics
• Well suited for a significant
portion of enterprise data
Other Advantages
13. • IT centered
• Add new data source? Wait for weeks/months
Business groups build their own offline datamarts
OBIEE’s Weakness: Speed of Change
Speed of Change
14. Not possible with OBIEE 11g.
Limited with OBIEE 12c, only with Excel.
Requires additional license.
Lack of Mash-up/Blending
New
Insights
Blend/Mash-up
OBIEE
SQL
BIG DATA
Not possible
with OBIEE
15. Too little
Too late
More cost
Too Many Clicks
Steep learning curve
OBIEE subject areas only
Lack of Modern Visualization
16. Can you overcome these
challenges by replacing
OBIEE with Tableau?
17. CONFIDENTIAL – For use by Guidanz Inc employees and other audiences under NDA only.
Tableau succeeds where
OBIEE fails
Let’s look at Tableau’s Strengths
Data
discovery
Visualization Mash-ups
Speed of
Change
Quick to
learn
✓ ✓ ✓ ✓ ✓
18. Is Tableau a like-for-like replacement?
OBIEE and
Tableau are
fundamentally
different tools
Designed and
used for
different
reasons
Like-for-like replacement is
lengthy, difficult, and
expensive approach.
19. Handling Complex Data Models
There is no
equivalent to
this in
Tableau
Challenging
beyond 25+
tables and
16+ text
columns
OBIEE RPD can centrally
handle complex data model
• Joins hundreds of tables
• Hundreds of columns in a
subject area
• Complex business logic
built-in
21. Other Factors To Consider
Majority of BI replacement projects are never ever 100% complete
Cost New Updates
Development
Team
Changing
requirements
22. So, let us revisit the current state
• Business users love Tableau
• Purchased Tableau desktop and
server licenses for department use
• Download OBIEE data and upload via
excel into Tableau
data duplication issues
security issues
system of record issues.
has invested
years and
millions into
building out
the OBIEE
RPD, reports
and
dashboards.
What should you do next?
IT
BUSINESSUSERS
23. Enterprise dashboards “Transient” data
Self-service BI
Data discovery
Visualization
Mashups
Slowly changing requirements
Large data models
Strong security model
So what should customers do?
OBIEE
TABLEAU
What is the alternative to replacement?
Is download and upload the best long term solution?
Recognize the fact there is a need for two kinds of BI tools
24. What is the Ideal Solution?
Bring together
the best of both
worlds!
OBIEE TABLEAU
25. What is the Ideal Solution?
Connect from
Tableau to
OBIEE.
Reuse OBIEE data
model, connect live to it
and build Tableau
visualizations on top of it.
Blend
external
data with
OBIEE
data.
Reuse
OBIEE
security
rules.
Repurpose huge
investment in
OBIEE + Benefits
of Tableau.
26. Introducing BI Connector
Seamless
User
Experience
Secured by OBIEE
security model
No Changes to
OBIEE, Reuse
OBIEE business
logic Cost and
Time savings
Easy Installation,
Information Consistency
Best of
Tableau +
OBIEE
OBIEE TABLEAU
27. CONFIDENTIAL – For use by Guidanz Inc employees and other audiences under NDA only.
BI Connector Live Demo
28. Benefits
Business users love
• Tableau visualization
for OBIEE
• Mash-ups
• Speed of change
• No OBIEE changes
• No data migration
• Easy to deploy
• Works with
10g,11g and 12c
OBIEE
• Eliminate Excel
exports from OBIEE
• Secure access to
OBIEE
Reuse OBIEE investment
while supporting business
need for modern
visualization tools.
Win-Win for IT and Business!
$
29. Summary
Recognize that you need two kinds of BI
Tools
• OBIEE
• stable requirements
• large data models,
• security – Driven by IT
• Tableau
• data discovery
• visualization,
• mash-ups
• transient data – Business user
friendly
Combine, not
replace OBIEE with
Tableau
• best of both,
• win-win for both
Business and IT.
BI Connector
can help you
achieve this
goal quickly.
Download free trial at
www.biconnector.com
30. CONFIDENTIAL – For use by Guidanz Inc. employees and other audiences under NDA only.
Download free trial at
www.biconnector.com
Thank You
Contact:
info@biconnector.com
Ph: 650.549.4843
Editor's Notes
Can Tableau deliver the capabilities that OBIEE has failed to deliver?
Should you replace OBIEE with Tableau?
Or, should you complement OBIEE with Tableau?
If so, what is the best approach
are frustrated with OBIEE
Weakness in visualization, ease of use, blending, and speed of change.
Busness users – find OBIEE hard to use
started using Tableau desktop –
Easy for non-technical users, simple to wrangle data, blend it, visualize it and create reports quickly.
Tableau server – offline datamarts where they extract data from the database and upload to Tableau server.
Frustration built up
Looking for an alternative
Like-for-like replacement + modern visualization + data blending + data wrangling + speed of change
Looking to either replace OBIEE or add a tool to work with OBIEE.
Growing tableau adoption
Looking to Tableau.
Can Tableau meet this lofty objectives for the alternative tool?
Is this realistic?
People are frustrated with OBIEE, but they lose sight of its strengths. Let us go over them.
The power of OBIEE is the meta data repository also called as the RPD. It is also its achiles’ heel.
RPD provides the common enterprise model where the physical, logical and presentation layers are well defined. Before a single report can be built, any new data source has to designed and built across these three layers by a technically competent person. The business model is usually well thought out and built.
Because of the RPD, OBIEE is well suited for IT led projects – which are supported and enhanced by IT.
Good for well-established data sources
Follow traditional waterfall model
get requirements from business users, design, development in RPD, testing and move to production projects.
Great for reusing the data models over many years.
Another significant advantage of OBIEE is its robust security model. It provides
object level security such as permissions on subject areas, presentation, or physical tables,
data-level security such as row filters,
Presentation Catalog security such as what dashboards and reports are available to which users, roles and LDAP groups.
Meets the security requirements of large organizations.
If implemented correctly, OBIEE provides, tested, accurate, and trusted data models which can be useful for a very long time.
OBIEE works well for enterprise level dashboards with common and standardized dimensions and metrics.
Users can come to the dashboard change their filters and get the data they need periodically.
A significant portion of data needs in every company fits in this bucket and OBIEE is a really useful tool to address these needs. For example, definitions for financial metrics like profits, gross-margins, cost of sales are not going to change very much and could be delivered using OBIEE.
But the reality in today’s world is that data is fast changing, requirements are evolving quickly, and more users are data savvy requiring more self service capability.
Another important challenge is the Speed of change
The number of data sources have increased. New data source or new table, column needs to be added to RPD before it can be used by end users. and nobody is willing to wait for IT to go through the development cycle to bring in new data sources.
Due to development delays, business users go ahead and create their own offline data marts and using tools like Tableau for visualization.
let us look the challenges with OBIEE in the context of today’s business environment.
The number of data sources have increased and nobody is willing to wait for IT to go through the development cycle to bring in new data sources. The new data sources could be in Excel, SQL server, Oracle data base or Hadoop. Almost all of you are in OBIEE 11g or 10g and it doesn’t provide the mash-up capability to analyze new data sources.
Even OBIEE 12c offers limited capability, you can blend OBIEE data only with Excel. Moreover, this feature requires an additional license.
Users
Building reports/dashboards in OBIEE is not intuitive and involves too many clicks.
It has a steep learning curve.
Visualization is not appealing to end users.
Visual Analyzer in OBIEE 12c begins to address some visualization challenges.
But, Visual Analyzer only connects to OBIEE subject areas, so data has to be made available by IT.
Additional license for Visual Analyzer.
Having seen all these challenges of OBIEE, can you overcome these shortcomings by using Tableau?
Tableau succeeds where OBIEE fails.
Business users love Tableau because it is a great tool for data discovery, quick to learn, provides out of the box visualizations, makes it easy to mash-up data and is designed to accelerate changes in your business intelligence applications.
But is Tableau a like-for-like replacement to OBIEE?
They are fundamentally different tools with different strengths that are designed and used for different reasons.
Replacing OBIEE like-for-like with Tableau would be a lengthy, difficult and expensive process.
Let us look at the factors that make replacing OBIEE with Tableau so complex.
Several organizations have OBIEE RPDs with complex data models. These data models have hundreds of joins and hundreds of columns in some folders. They also have complex business logic and security model built into these RPDs.
There is no equivalent designing approach in Tableau. Tableau sometime has challenges handling beyond 25+ tables and 16+ text columns.
Organizations have built hundreds/thousands of reports in OBIEE over the years. Manual redevelopment of these reports in Tableau is time consuming and expensive.
You also have to consider several other features:
If you get past technical challenges, what is the opportunity Cost?
When you do a lift and shift projects, it results in a Fluid BI environment.
The Changing requirements makes it very complex.
You also have to consider and plan for new versions of OBIEE and Tableau during redevelopment
You also need to consider the organization aspects such as development team, testing team for Tableau versions of OBIEE reports.
BI platform replacements are so complex that majority of the BI platform replacement are never ever 100% complete.
So, let us revisit the current state in many organizations.
With OBIEE and Tableau in their environment what should you do next?
If you do not replace then is downloading reports from OBIEE and loading into Tableau the best way forward?
Is this the best long term solution?
An ideal solution should bring together the best of both OBIEE and Tableau.
Let us look at the ideal solution.
The ideal solution should enable you to
I would like to introduce BI Connector which brings together the best of Tableau and OBIEE.