The fourth annual Open Source Think Tank event, held earlier this month in Napa Valley, brought together some of the best ideas and thinking in open source software. While listening to the CIO panel, I stitched together a number of conversations I’ve had during the past few months – and realized the most vanguard CIOs (and IT organizations) recognize the real advantages of the open source software model and integrate these solutions into their businesses.
The CIO panelists emphasized that open source commonly suffers from misperceptions that prevent serious consideration of the products. The solution they offered is for open source vendors to spend more time and money courting them, much like the aged, proprietary companies with whom open source vendors, now more than ever, compete. While I agree with (and appreciate) their feedback, I disagree with their proposed remedy. And, here’s why.
About one month earlier, I received a call from the CIO of a multi-billion dollar technology company who nicely summarized the predicament facing all IT organizations. While lamenting the 80% of his budget dedicated to maintaining legacy systems, he was struggling to find ways to reduce costs and increase innovation. To make matters worse, he just received his annual maintenance bill from his long-time (proprietary) BI mega-vendor and the amount increased from 20% to 22% of his original license price, adding meaningfully to his “80% problem.” Subsequently, he offered his summary:
“I’ve come to realize that the traditional software industry pricing and packaging model is fundamentally broken. I spend huge sums on license fees, services and support in advance of even knowing if the complicated software is going to provide the return I’ve been promised. I bear all the risk.”
The transparency, greater simplicity and enormous cost-savings of open source software solves his business problem. CIOs and open source vendors have a complementary relationship because IT team’s can wade into the technology at their own pace, learn about a product‘s capabilities and even put it into use, before any money is spent on license, services or support. In this sense, the return on the prospective use of the open source product is known before any investment occurs (not including the time and energy of the internal IT team) – which fundamentally rights the upside down model we’ve become accustomed to during the past 40 years.
So, I’ll assert that commercial open source vendors are the most closely aligned with the IT organization and it’s time for CIOs to take proactive steps to learn more about open source alternatives. This is where I disagree with the suggestion of the CIO panel at the Think Tank event. If open source software companies ramp up sales and marketing to behave like the dated, proprietary vendors, the significantly higher costs would reduce some of the advantage we pass along to customers. Instead, I urge CIOs and IT staffers to make it their job to learn more about open source software and reach out to those vendors who are best aligned to help them reduce their 80% maintenance cost problem and finally get back to innovating, much like the CIO that contacted me.
Brian Gentile
Chief Executive Officer
Jaspersoft
Monday, March 23, 2009
Monday, March 9, 2009
First U.S. Government CIO Offers Hope through Efficiency and Transparency
Late last week, President Obama announced the appointment of the United States Federal Government’s first-ever Chief Information Officer, Vivek Kundra. Mr. Kundra’s experiences and accomplishments align very well with the needs of this role. I am most impressed with Kundra’s ability to drive focus within his IT teams which has lead to both cost savings and new innovation. Specifically, he has a record of implementing clever processes for IT Governance, improving transparency and accessibility while driving efficiency. InfoWorld reported on Kundra’s appointment and emphasized these very abilities:
"’It's tough in tight budgets to find the innovative path,’ Kundra notes, which is why he was so focused on gaining stock-market-like efficiencies in weeding out wasteful projects and identifying strong ones. Thanks to the savings already established from this approach, he was able to set up an R&D lab to test new ideas.”
Mr. Kundra has an historic opportunity to help set the agenda not only for Information Technology within the U.S. government, but throughout the public sector and even in private enterprise. As he constructs his game plan in this new role, I’ll offer Mr. Kundra three ideas to literally transform our government’s approach to IT:
1. Tackle the “80% maintenance cost” problem head-on by creating the most efficient IT infrastructure in the world. Do this by using the array of proven technologies that can measurably eliminate costs, especially cloud-based computing services and open source software. Avoiding the status quo (aged, proprietary software and hardware models) will help free up funding for the next two points.
2. Drive innovation by making the most vital applications more accessible and available through an increasingly consumer-like user experience. [Note: Kundra has specific experience here, impressively]. This could encourage a whole new generation of IT personnel who will want to work for the government.
3. Support your President’s agenda by using information technology to re-create the government of the people, by the people and for the people. Social services, contracts and procurement, and public safety are all great places to start. Most interestingly, the entire process of creating law can be made transparent and accessible through wiki’s, blogs, forums, and the collaborative construct of a Government “Forge”. Call it “OneWorldForge” and use it to re-establish the United States as the upstart democracy that once again changes the world.
I offer my congratulations to Vivek Kundra and wish him much success in this important new role.
Brian Gentile
Chief Executive Officer
Jaspersoft
"’It's tough in tight budgets to find the innovative path,’ Kundra notes, which is why he was so focused on gaining stock-market-like efficiencies in weeding out wasteful projects and identifying strong ones. Thanks to the savings already established from this approach, he was able to set up an R&D lab to test new ideas.”
Mr. Kundra has an historic opportunity to help set the agenda not only for Information Technology within the U.S. government, but throughout the public sector and even in private enterprise. As he constructs his game plan in this new role, I’ll offer Mr. Kundra three ideas to literally transform our government’s approach to IT:
1. Tackle the “80% maintenance cost” problem head-on by creating the most efficient IT infrastructure in the world. Do this by using the array of proven technologies that can measurably eliminate costs, especially cloud-based computing services and open source software. Avoiding the status quo (aged, proprietary software and hardware models) will help free up funding for the next two points.
2. Drive innovation by making the most vital applications more accessible and available through an increasingly consumer-like user experience. [Note: Kundra has specific experience here, impressively]. This could encourage a whole new generation of IT personnel who will want to work for the government.
3. Support your President’s agenda by using information technology to re-create the government of the people, by the people and for the people. Social services, contracts and procurement, and public safety are all great places to start. Most interestingly, the entire process of creating law can be made transparent and accessible through wiki’s, blogs, forums, and the collaborative construct of a Government “Forge”. Call it “OneWorldForge” and use it to re-establish the United States as the upstart democracy that once again changes the world.
I offer my congratulations to Vivek Kundra and wish him much success in this important new role.
Brian Gentile
Chief Executive Officer
Jaspersoft
Monday, March 2, 2009
Building on the Success of Open Core, guest post by Matt Aslett
My thanks to Matt Aslett from The 451 Group for guest blogging here at The Open Book on BI. Matt has been an active participant in the debate on open core, and has agreed to share his last words on the topic here today. The views and opinions expressed are his own.
Building on the success of Open Core
Thanks to Brian Gentile for the chance to guest post on the debate surrounding open source business models. Brian recently joined that debate, writing that the Open Core model offers the best model for community and commercial success.
I absolutely agree that Open Core is a successful strategy. In the report, Open Source is Not a Business Model, we noted that it is now the most popular commercial open source licensing strategy, used by 23.7% of the 114 vendors we assessed and 40.4% of those that were using a commercial licensing strategy to generate revenue from open source.
However, I also recently questioned whether the Open Core model is sustainable in the long-term (I'm thinking 5-10 years).
This is partially based on my belief that we will see a shift away from vendor dominated open source projects (such as MySQL and JasperSoft) to vendor-dominated open source communities (such as Eclipse and Symbian) during this period, but also because there are other potential problems that arise with the Open Core model.
Rather than re-hash those issues here I thought it would be better to use this guest-post opportunity to suggest some strategies that could be used to ensure a sustainable implementation of the Open Core model.
Many of these are being implemented by the various Open Core vendors - including JasperSoft - and with that in mind - along with the final caveat that unlike Brian I am the chicken in this debate (involved but not committed) - these are the issues that I think are critical to a successful Open-Core model:
Truth in advertising
Be absolutely transparent about licensing. Potential customers don't like feeling confused or misled and it is vital that the marketing makes it clear that the community version is open source and the enterprise edition is not. Personally, I believe that Open Core vendors could and should be referred to as "open source vendors" but that is something of a hypothetical construct. What is clear is that if the product in question does not use an OSI-approved license it is not open source, and should not be referred to as open source.
Don't promise what you can't deliver
On a related note, open core vendors must avoid overselling the benefits of open source. Be an advocate for open source, but never forget that the revenue generating products and features are not open source. Tarus Balog of the OpenNMS Group recently highlighted the theoretical contradiction at the heart of the Open-Core model in the context of the request from open source vendors, including some open core advocates, for open source to be included in President Obama's economic stimulus plans. If you ask the government to mandate open source, don't be surprised if it insists on the source code to your proprietary functionality. Similarly in our Cost Conscious report, we found that 73% of end users surveyed expected to generate cost savings from deploying open source software through reducing the cost of software licenses. Clearly some of them are going to be disappointed if they need to be deploying software licenses to get the functionality they require.
The new UK government policy on open source software also makes the distinction between the treatment of open source licensed products and the exit, rebid and rebuild costs associated with proprietary software. Yes, there are licensing mechanisms that can be used to ensure Open-Core products can be used as part of pro-open source adoption policies, but Open-Core vendors must make sure they are not selling customers a vision of open source while delivering the proprietary licenses they are supposedly trying to avoid.
Separation of church and state
The further removed the proprietary functionality is from the needs of community users the less likely it is that the community will develop their own alternatives and the easier it will be to manage the needs of both commercial and community users. If the vendor is hearing constant demands from the community for features in the enterprise version then the balance is wrong. It might sound like a great opportunity for up-sell but if the community users are never going to pay for the enterprise product then it just creates confusion and antagonism. When deciding on proprietary features vendors should create a list of features that is only ever going to solve the problems faced by enterprise customers. In the context of the law of Conservation of Attractive Profits, articulated by Clayton Christensen in The Innovator's Solution, it also makes sense for a vendor to focus its attention further up the value chain than the stage it is actively commoditizing with the open source community version.
Care in the community
Brian is right to say that "Community and Commercial customers form a necessary and symbiotic virtuous circle" and that "done properly, the resulting broad use yields benefit and value to both the Community and Commercial customers." Doing it properly means looking after and understanding the community. Among other things a vendor needs to:
Defining and creating understanding about licensing and revenue strategies is important but philosophical debates between open source vendors can appear from the outside like a fight between two bald men over a comb (and yes I am totally aware that I am guilty of propagating the current debate, I fully intend this will be my last word on the subject of Open Core for a while). Michael Tiemann recently claimed that the world wastes $1 trillion per year in "dead-loss writeoffs of failed proprietary software implementations" and maintained that open source software is the way to solve that problem. He also stated that "semi-proprietary strategies... are all too clever by half, because they all imagine winning the next battle in a war that's already been lost." Of course he might not be right, but $1 trillion makes it worth thinking about.
I realize that for many Open Core vendors I am preaching to the converted. Many of the same themes were discussed on a panel on open source at the recent Accel Symposium at Stanford, for example.
Open Core is definitely the most popular and successful model of commercial open source in use today, and I expect it to remain so for the next few years, but the conclusion of Sun's Zack Urlocker on that Accel open source panel is worth bearing in mind:
"There are many different ways to skin this cat. There isn't one single model for commercializing open source, and things will continue to evolve as the market expands. What worked in the past may not always apply in the future."
Matt Aslett
Analyst, enterprise software, The 451 Group
Blog
Twitter
Building on the success of Open Core
Thanks to Brian Gentile for the chance to guest post on the debate surrounding open source business models. Brian recently joined that debate, writing that the Open Core model offers the best model for community and commercial success.
I absolutely agree that Open Core is a successful strategy. In the report, Open Source is Not a Business Model, we noted that it is now the most popular commercial open source licensing strategy, used by 23.7% of the 114 vendors we assessed and 40.4% of those that were using a commercial licensing strategy to generate revenue from open source.
However, I also recently questioned whether the Open Core model is sustainable in the long-term (I'm thinking 5-10 years).
This is partially based on my belief that we will see a shift away from vendor dominated open source projects (such as MySQL and JasperSoft) to vendor-dominated open source communities (such as Eclipse and Symbian) during this period, but also because there are other potential problems that arise with the Open Core model.
Rather than re-hash those issues here I thought it would be better to use this guest-post opportunity to suggest some strategies that could be used to ensure a sustainable implementation of the Open Core model.
Many of these are being implemented by the various Open Core vendors - including JasperSoft - and with that in mind - along with the final caveat that unlike Brian I am the chicken in this debate (involved but not committed) - these are the issues that I think are critical to a successful Open-Core model:
Truth in advertising
Be absolutely transparent about licensing. Potential customers don't like feeling confused or misled and it is vital that the marketing makes it clear that the community version is open source and the enterprise edition is not. Personally, I believe that Open Core vendors could and should be referred to as "open source vendors" but that is something of a hypothetical construct. What is clear is that if the product in question does not use an OSI-approved license it is not open source, and should not be referred to as open source.
Don't promise what you can't deliver
On a related note, open core vendors must avoid overselling the benefits of open source. Be an advocate for open source, but never forget that the revenue generating products and features are not open source. Tarus Balog of the OpenNMS Group recently highlighted the theoretical contradiction at the heart of the Open-Core model in the context of the request from open source vendors, including some open core advocates, for open source to be included in President Obama's economic stimulus plans. If you ask the government to mandate open source, don't be surprised if it insists on the source code to your proprietary functionality. Similarly in our Cost Conscious report, we found that 73% of end users surveyed expected to generate cost savings from deploying open source software through reducing the cost of software licenses. Clearly some of them are going to be disappointed if they need to be deploying software licenses to get the functionality they require.
The new UK government policy on open source software also makes the distinction between the treatment of open source licensed products and the exit, rebid and rebuild costs associated with proprietary software. Yes, there are licensing mechanisms that can be used to ensure Open-Core products can be used as part of pro-open source adoption policies, but Open-Core vendors must make sure they are not selling customers a vision of open source while delivering the proprietary licenses they are supposedly trying to avoid.
Separation of church and state
The further removed the proprietary functionality is from the needs of community users the less likely it is that the community will develop their own alternatives and the easier it will be to manage the needs of both commercial and community users. If the vendor is hearing constant demands from the community for features in the enterprise version then the balance is wrong. It might sound like a great opportunity for up-sell but if the community users are never going to pay for the enterprise product then it just creates confusion and antagonism. When deciding on proprietary features vendors should create a list of features that is only ever going to solve the problems faced by enterprise customers. In the context of the law of Conservation of Attractive Profits, articulated by Clayton Christensen in The Innovator's Solution, it also makes sense for a vendor to focus its attention further up the value chain than the stage it is actively commoditizing with the open source community version.
Care in the community
Brian is right to say that "Community and Commercial customers form a necessary and symbiotic virtuous circle" and that "done properly, the resulting broad use yields benefit and value to both the Community and Commercial customers." Doing it properly means looking after and understanding the community. Among other things a vendor needs to:
- Hire a proven, experienced and respected community manager to liaise between the company and the community
- Create a forge - if you don't know who your community is and what they are doing with the software you cannot hope to understand why an individual or company is part of the community and respond to their wants and needs.
- Encourage partners to become part of the community, rather than part of commercial partnerships, to help improve the core code base and enable new commercial strategies.
Defining and creating understanding about licensing and revenue strategies is important but philosophical debates between open source vendors can appear from the outside like a fight between two bald men over a comb (and yes I am totally aware that I am guilty of propagating the current debate, I fully intend this will be my last word on the subject of Open Core for a while). Michael Tiemann recently claimed that the world wastes $1 trillion per year in "dead-loss writeoffs of failed proprietary software implementations" and maintained that open source software is the way to solve that problem. He also stated that "semi-proprietary strategies... are all too clever by half, because they all imagine winning the next battle in a war that's already been lost." Of course he might not be right, but $1 trillion makes it worth thinking about.
I realize that for many Open Core vendors I am preaching to the converted. Many of the same themes were discussed on a panel on open source at the recent Accel Symposium at Stanford, for example.
Open Core is definitely the most popular and successful model of commercial open source in use today, and I expect it to remain so for the next few years, but the conclusion of Sun's Zack Urlocker on that Accel open source panel is worth bearing in mind:
"There are many different ways to skin this cat. There isn't one single model for commercializing open source, and things will continue to evolve as the market expands. What worked in the past may not always apply in the future."
Matt Aslett
Analyst, enterprise software, The 451 Group
Blog