2. Jos van Dongen
> 20 yrs BI
Principal Consultant
Author/Speaker/Analyst
Proud member of #BBBT
Web: www.tholis.com
Email: jos<at>tholis.com
Phone: +31-(0)6-51169606
Skype: tholis.jos
LinkedIn: jvdongen
Twitter: josvandongen
IRC: _grumpy
3.
4. Java Server Pages
JFreeReports
OpenFlashCharts Dashboard Framework
JPivot
Mondrian
MySQL
7. The Industry Radar Screens
Forrester Wave for BI, Q4 2010
Gartner BI Magic Quadrant
7
8. The value of the Radar Screens
Source: Doug Laney, May 13, 2008
8
9. Open Source Everywhere
“By 2012, 80 percent of all
commercial software will include
elements of open-source
technology ”
Many open-source technologies are mature, stable and well supported.
They provide significant opportunities for vendors and users to lower
their total cost of ownership and increase returns on investment.
Ignoring this will put companies at a serious competitive disadvantage.
Embedded open source strategies will become the minimal level of
investment that most large software vendors will find necessary to
maintain competitive advantages during the next five years.
Gartner Group, 2008
9
11. Open Source Disrupts the Market
Overkill
st omers
High demanding cu
Dis
What Customers Want
rup
tio
n
stomers
Low demanding cu
Perceived as a Toy
Time
Source: The Innovators Dilemma, Clayton Christensen
12. What is Open Source?
Informal:
If the software has an Open Source Licence, it's Open Source
Formal:
1. Free Redistribution
2. Source Code
3. Derived Works
4. Integrity of The Author's Source Code
5. No Discrimination Against Persons or Groups
6. No Discrimination Against Fields of Endeavor
7. Distribution of License
8. License Must Not Be Specific to a Product
9. License Must Not Restrict Other Software
10. License Must Be Technology-Neutral
12
15. Why Open Source?
Source:
Open Source Adoption
in the BI Market
3rd Nature, 2009
15
16. ...And Why Not?
Problem ReportedbyRespondents
s
Missing or incomplete features 72%
Scalabilityproblems 34%
Required more internal expertise than expected 32%
Difficultyintegrating into current environment 29%
Difficulty finding available solutions 28%
Reliability problems 25%
Lack of available consulting 21%
Source:
Interoperability problems 19% Open Source Adoption
in the BI Market
Higher costs than anticipated 18% 3rd Nature, 2009
Lack of vendor service or support 16%
T he biggest r eason is maturity of the softwar e.
16
23. The 'BIG 4'
⇨ Palo, Jaspersoft & Pentaho: Community &
Professional/Enterprise Editions
⇨ SpagoBI only real FOSS platform
⇨ Is licensed under LGPL (Yes, that's LGPL)
⇨ Has integrated DTAP migration tools
⇨ Can integrate multiple engines:
23
24. ⇨ Project by Italian system integrator & software engineer
⇨ Engineering Ingegneria Informatica
⇨ Company founded 1980, listed on Milan Stock exchange
⇨ Invested €65 Mln from 2003-2006 in 40 R&D projects, including Spago BI
(started 2004)
⇨ Highlights:
⇨ Only FOSS BI platform!
⇨ > 100 production sites
⇨
Strengths:
⇨ Multi engine platform
⇨ Only OS BI tool to address KPI, Metadata management & Geo Info
⇨
Weaknesses:
⇨ Support only from EII: Italian based
24
27. ⇨
2004: Company founded by BI industry veterans
⇨ Adopted existing projects (JFreeReport, Kettle, Mondrian, JPivot, Weka)
⇨ BI Platform is own development. 1st release: 2005
⇨
Total funding to date: $33Mln
⇨ Highlights:
⇨ Plug-in architecture (extensibility)
⇨ Community Edition contains full BI Suite
⇨ Strengths:
⇨ Employment of component Chief Architects
⇨ Very strong & active community
⇨
Weaknesses:
⇨ Diversity of components; aimed at developers
27
28. End to End BI
Reporting
Operational, Production
Embedded
Web-based Ad-hoc
Analysis
Interactive slice, dice, and drill
Web-based or Excel
Dashboards
KPIs
Mash-ups
Data Integration / ETL
Data Mining
BI Platform
Scheduling & bursting
Notification
Content sharing
Security integration
28
30. ⇨ 2001: JasperReports project started by 1 developer; Panscopic founded
⇨ 2004: Panscopic adopts JasperReports, changes name to JasperSoft & goes OS
⇨ Adopted existing projects (iReport, Mondrian, JPivot, Talend)
⇨ BI platform is own development, total funding to date $45.5Mln
⇨ Highlights:
⇨ JasperBabylon (multi-language model)
⇨ Ingres Icebreaker appliance
⇨ Strenghts:
⇨ Complex, operational reporting
⇨ Scalability to >1.000 users
⇨ Weaknesses:
⇨ No control over main platform components (Analysis, ETL)
⇨ More and more a proprietary vendor with a free edition
30
34. Palo BI Suite
⇨ 2002: Jedox Founded by Kristian Raue
⇨ Main promise: “Excel without Hell”
⇨ BI platform is own development
⇨ Highlights:
⇨ Palo in memory OLAP database
⇨ Easy to use web-based ETL & modeling
⇨ Strenghts:
⇨ Budgetting, planning & analysis including write back
⇨ Excel & OpenOffice Calc as front-end
⇨ SAP/R3 connectors (Palo as BW alternative)
⇨ Weaknesses:
⇨ BI is more than cubes
⇨ Worksheet Server 3 still very buggy (as of Feb. 2010)
34
37. Palo OS Ecosystem
PalOOCa
plugin
Palo ETL Server
Jpalo
web
PALO
client
Jpalo client
37
38. Is Open Source BI for you?
OR ?
CSF
No 1!
⇨ Business Case
⇨ BI Maturity
⇨ Internal Skills
⇨ Culture
⇨ Infrastructure
⇨ Applications
⇨ Vendors
⇨ Support Partners
38
39. Open Source BI To Do
⇨ Performance Management
⇨ Vertical/horizontal applications
⇨ Sharepoint & MS/Open Office integration
⇨ Collaboration (users & developers)
⇨ Interactive Visual Analysis
⇨ Drag & drop free form reporting
⇨ Meta data integration, lineage, impact
⇨ Books & documentation
⇨ Consulting, training, support
39
40. Recommendations
1.Don't focus solely on cost savings.
People did not mention as up-front
reasons many of the benefits they
discovered later.
2.Plan to augment, not replace,
existing software with open source.
Rather than trying to saving money by
replacing software, look at gaps in the
BI portfolio or data warehouse stack
and use open source to supplement
your systems.
Source: Mark Madsen, Third Nature
40
41. Recommendations
3.Consider developing open source
policies. Most organizations are
adopting open source in an ad-hoc
fashion, project by project.
4.Evaluate open source like any
other software. It doesn't matter if
the software is free if it takes longer
to build, manage and deploy
solutions to end users, if it is
unstable, or if it is missing a key
feature
5.Make open source the default
option. When there are no internal
tools, open source should be the
first alternative.
Source: Mark Madsen, Third Nature
41