Large FLOSS Study Gets the Real Facts
Hans Kwint writes "The European Commission's enterprise and industry department has just released the final draft of what could be the biggest academic interdisciplinary study on the economic / innovative impacts of free/libre/open source software (1.8-MB PDF). The study was done by an international consortium led by the United Nations University / University of Maastricht. The lead researcher, Rishab Aiyer Ghosh, has overseen a large volume of FLOSS studies in the last few years, including ones on FLOSS policies and worldwide FLOSS adoption. This academic-grade study has a very broad scope and has collected real-world information that is valuable for both companies and government bodies thinking about migration. The study is about the economic impact of FLOSS, not excluding the hidden indirect impact. It compares scenarios of open and proprietary software futures of Europe. The study looks at the FLOSS's competitiveness compared to proprietary software and also provides a few TCO comparison case-studies.
As the article summary clearly states (as does the Wikipedia article on FLOSS), FLOSS actually stands for Free/Libre/Open-Source Software.
Rubbish.
Both the article summary, original paper (page 9) and Wikipedia article you linked to clearly state that FLOSS = "Free/Libre/Open-Source Software (FLOSS)".
Or were you too busy trying to get First Post?
Gan Family Homepage
I'm not going to read a 1.8 mb PDF TFA unless I know whether or not its conclusions agree with my predisposed bias!
You don't have to. Start in the table of contents and you will find the conclusion is on a single page. It's on page 283. It's a PDF so I can't cut and paste and If you are not going to read it, I'm not taking the time to retype the conclusion page.
For me, I like the conclusion. MS will not.
The truth shall set you free!
this is pure laziness by the story poster. I don't come to slashdot to read 286 page documents, the whole purpose of a news site is to give me news, and then link to the complete document.
Anyway, for the benefit of others, I shall attempt to quote relevant sentences from the conclusion.
Our findings show that, in almost all the cases, a transition toward open source reports of savings on the long term costs of ownership of the software products. Costs to migrate to an open solution are relevant and an organization needs to consider an extra effort for this. However these costs are temporary and manly are budgeted in less than one year. OpenOffice.org has all the functionalities that public offices need to create documents, spreadsheets, and presentations We also investigated the productivity of the employees in using Microsoft office and OpenOffice.org....Our findings report no particular delays or lost of time in the daily work due to the use of OpenOffice.org. Employees may perceive that their work is under-valued using 'cheap' OSS products or changing operating model to OSS is problematic.To overcome these pre-conception it is recommended to adopt a policy of both ad hoc and periodic training to fill the lack of knowledge/experience in relation to what OSS products are appropriate and how they might be deployed.
It is not always justified to base the migration on the promise of lower license costs Another good crucial reason of costs is training. Although training costs are a substantial part of the migration costs their benefits can be realized over time. There are no extra costs due to lack of productivity arising from the use of the OOo.Someone who reads the whole thing might be able to do justice to the summary of the document, but for many, this should suffice.
If you don't want to read through the entire PDF (which I can understand, since it's 287 pages in size), there are some interesting figures in the first paragraph which highlights the study's key findings.
"Europe is the leading region in terms of globally collaborating FLOSS software developers, and leads in terms of global project leaders, followed closely by North America (interestingly, more in the East Coast than the West), Asia and Latin America face disadvantages at least partially due to language barriers, but may have an increasing share of developers active in local communities."
"Weighted by regional PC penetration, central Europe and Scandinavia provide disproportionally high numbers of developers; weighted by average income, India is the leading provider of FLOSS developers by far, followed by China."
"The existing base of quality FLOSS applications with reasonable quality control and distribution would cost firms almost Euro 12 billion to reproduce internally. This code base has been doubling every 18-24 months over the past eight years, and this growth is projected to continue for several more years."
"The existing base of FLOSS software represents a lower bound of about 131.000 real person-years of effort that has been devoted exclusively by programmers. As this is mostly by individuals not directly paid for development, it represents a significant gap in national accounts of productivity. [...]"
"Defined broadly, FLOSS-related services could reach a 32% share of all IT services by 2010, and the FLOSS-related share of the economy could reach 4% of European GDP by 2010. [...]"
"[...] FLOSS and proprietary software show a ration of 30:70 (overlapping) in recent job postings indicating significant demand for FLOSS-related skills."
There is a huge amount of information in this PDF, and while it pertains directly to Europe, it's also interesting to read for people who don't live there. Basically, it discusses the role of software libre in the European economy (both its direct and indirect impacts), and its general trends, scenarios and policy strategies. Everything is in great detail, too.
(of pages 9-12 of the PDF article)
FLOSS role in the economy- FLOSS applications are first, second or third-rung products in terms of market share in
several markets
- FLOSS market penetration is also high
- Almost two-thirds of FLOSS software is still written by individuals
- Europe is the leading region in terms of globally collaborating FLOSS software developers
- (more details on specific role in Europe in paper)
Direct economic impact- The existing base of quality FLOSS applications with reasonable quality control and distribution would cost firms almost Euro 12 billion to reproduce internally... code base has been doubling every 18-24 months
- This existing base of FLOSS software represents a lower bound of about 131 000 real person-years of effort that has been devoted exclusively by programmers... it represents a significant gap in national accounts of productivity
- Firms have invested an estimated Euro 1.2 billion in developing FLOSS software that is
- made freely available... represent in total at least 565 000 jobs and Euro 263 billion in annual revenue
- FLOSS-related services could reach a 32% share of all IT services by 2010, and the FLOSS-related share of the economy could reach 4% of European GDP by 2010
- (more statistics in the paper)
Indirect economic impact- Strong network effects in ICT... risk leading to innovation resources being excessively allocated to defensive innovation. There is a case for a rebalancing of innovation incentives... (to target) publicly available technology for new functionality.
- FLOSS potentially saves industry over 36% in software R&D investment
- ...a large and increasing share of user-generated content is not accounted for and needs to be addressed by policy makers
- Increased FLOSS use may provide a way for Europe to compensate for a low GDP share of ICT investment relative to the US
Trends, scenarios and policy strategiesGan Family Homepage
Our analysis has been performed on six organizations in different European countries.
The majority of them are public bodies. The organizations have followed different types of
migration on the base of their context.
We have investigated the costs of migration, and the cost of ownership of the old and
the new solution differentiating them between the costs of purchasing and the costs of
ownership of the software solutions. Special attention has been put on the intangible nature of
the costs. Costs have been classified in categories defined trough existing studies and selected
by a top down approach called Goal Question Metric. This instrument has been also used to
define the questionnaires used to collect the data.
Our findings show that, in almost all the cases, a transition toward open source reports
of savings on the long term costs of ownership of the software products.
Costs to migrate to an open solution are relevant and an organization needs to
consider an extra effort for this. However these costs are temporary and manly are budgeted
in less than one year. The major factor of cost of the new solution even in the case that the
open solution is mixed with closed software is costs for peer or ad hoc training. These are
the best example of intangible costs that often are not foreseen in a transition. On the other
hand not providing a specific training may cause and adverse attitude toward the new
technology. Fortunately those costs are limited in time and are not strictly linked to the nature
of the new software adopted.
We also investigated the productivity of the employees in using Microsoft office and
OpenOffice.org. Office suites are widely used and are a good test bed and representative for a
comparison on issues like effort and time spent in the daily routine of work. Delays in the
task deliveries may have a bigger impact than costs on the organization's management. Our
findings report no particular delays or lost of time in the daily work due to the use of
OpenOffice.org.
I have no qualms about extracted good, useful conclusions from well-researched academic papers so others don't have to download a 1.8MB file. (Thanks for pointing out the usefulness of the conclusion, though).
From page 283 (emphasis mine):
Conclusion
Our analysis has been performed on six organizations in different European countries. The majority of them are public bodies. The organizations have followed different types of migration on the base of their context.
We have investigated the costs of migration, and the cost of ownership of the old and the new solution differentiating them between the costs of purchasing and the costs of ownership of the software solutions. Special attention has been put on the intangible nature of the costs. Costs have been classified in categories defined trough existing studies and selected by a top down approach called Goal Question Metric. This instrument has been also used to define the questionnaires used to collect the data.
Our findings show that, in almost all the cases, a transition toward open source reports of savings on the long term - costs of ownership of the software products.
Costs to migrate to an open solution are relevant and an organization needs to consider an extra effort for this. However these costs are temporary and manly are budgeted in less than one year. The major factor of cost of the new solution - even in the case that the open solution is mixed with closed software - is costs for peer or ad hoc training. These are the best example of intangible costs that often are not foreseen in a transition. On the other hand not providing a specific training may cause and adverse attitude toward the new technology. Fortunately those costs are limited in time and are not strictly linked to the nature of the new software adopted.
We also investigated the productivity of the employees in using Microsoft office and OpenOffice.org. Office suites are widely used and are a good test bed and representative for a comparison on issues like effort and time spent in the daily routine of work. Delays in the task deliveries may have a bigger impact than costs on the organization's management. Our findings report no particular delays or lost of time in the daily work due to the use of OpenOffice.org.
Gan Family Homepage
"Libre software" was first used publicly in 2000, by the European Commission... The word "libre", borrowed from the Spanish and French languages, does not have the freedom/cost ambiguity problem that "free" does.
"FLOSS" was used in 2001 as a project acronym by Rishab Aiyer Ghosh as an acronym for Free/Libre/Open-Source Software. Later that year, the European Commission (EC) used the phrase when they funded a study on the topic.
Note that Rishab Aiyer Ghosh is the same author of this academic paper.
Gan Family Homepage
Based on project homepage, especially the list of parnters, it seems that this study was mostly financed by the EU. The secondary sources include interested parties (an association of Indian IT companies, Mitsubishi) and non-interested ones (e.g. the Soros foundation). This leads me to trust the study more than ones funded by Redhat and Microsoft.
"Start in the table of contents and you will find the conclusion is on a single page. It's on page 283."
No it's not. That's only the conclusion page for section 12, "Appendix 2: Report on user-level productivity and relative cost of FLOSS / proprietary software." The executive summary is the where the overall conclusions can be found in this paper. The whole thing is considerably more than just a TCO study.
Use xpdf on Linux to read them. If you want to stick to proprietary, FoxIt Reader is much better than Adobe Acrobat Reader.
It's a PDF so I can't cut and paste and If you are not going to read it, I'm not taking the time to retype the conclusion page.
I Can:
12.7. Conclusions
Our analysis has been performed on six organizations in different European countries. The majority of them are public bodies. The organizations have followed different types of migration on the base of their context.
We have investigated the costs of migration, and the cost of ownership of the old and the new solution differentiating them between the costs of purchasing and the costs of ownership of the software solutions. Special attention has been put on the intangible nature of the costs. Costs have been classified in categories defined trough existing studies and selected by a top down approach called Goal Question Metric. This instrument has been also used to define the questionnaires used to collect the data.
Our findings show that, in almost all the cases, a transition toward open source reports of savings on the long term - costs of ownership of the software products.
Costs to migrate to an open solution are relevant and an organization needs to consider an extra effort for this. However these costs are temporary and manly are budgeted in less than one year. The major factor of cost of the new solution - even in the case that the open solution is mixed with closed software - is costs for peer or ad hoc training. These are the best example of intangible costs that often are not foreseen in a transition. On the other hand not providing a specific training may cause and adverse attitude toward the new technology. Fortunately those costs are limited in time and are not strictly linked to the nature of the new software adopted.
We also investigated the productivity of the employees in using Microsoft office and OpenOffice.org. Office suites are widely used and are a good test bed and representative for a comparison on issues like effort and time spent in the daily routine of work. Delays in the task deliveries may have a bigger impact than costs on the organization's management. Our findings report no particular delays or lost of time in the daily work due to the use of OpenOffice.org.
12.7.1. Considerations
With our analysis we achieve a good level of understanding of the costs, benefits and productivity of a transition. The following are the considerations we have drawn upon.
1. Before buying, upgrading proprietary office software one needs consider that: OpenOffice.org has all the functionalities that public offices need to create documents, spreadsheets, and presentations Upgrading office programs is time-consuming and expensive. It requires installation time, potential document conversions, and new training. It also poses a risk because some documents containing code or macros may not be readable anymore OpenOffice.org is free, extremely stable, and supports the ISO Open Document Standard.
2. In our study the motivations to transit to OSS are: the exchange of documents in an open shared format (ODS), reuse of old hardware in some cases, and being independent of software vendors even when creating a distribution or an application for local needs. Employees may perceive that their work is under-valued using 'cheap' OSS products or changing operating model to OSS is problematic. Economic impact of FLOSS on innovation and competitiveness of the EU ICT sector © 2006 MERIT. Prepared on November 20, 2006 284 To overcome these pre-conception it is recommended to adopt a policy of both ad hoc and periodic training to fill the lack of knowledge/experience in relation to what OSS products are appropriate and how they might be deployed.
3. It is not always justified to base the migration on the promise of lower license costs, although in our study initial purchasing costs are lower for the OSS (they includes deployment and customization for the first run of the configuration). This is because these costs are too much influenced
Skip to page 241 for the summary of the results.
;)
(For regular readers I'll give you a hint - in all cases closed source solutions cost significantly more, and in five out of six organisations compared yearly cost savings are predicted.)
Oh yeah - and everyone likes OpenOffice
The truth is that every country in EU made their own study on office software. I live in Slovenia and I just found similar study comparing transition of government 11.800 workstations to Open Office. It clearly says NO to open source for 3 years. It's a document dating 14.11.2005. This study has a conclusion that migrating software from MS to Open Office is possible and functionality of both packages are more then enough for government needs. The things that changed their mind and are considered greater risk that brings higher costs over this 3 year period are:
.gov sites offering ODF formats as well as .doc and .pdf. THIS IS THE PLACE WHERE REAL TRANSITION SHOULD START AS WELL AS INSTALLING OPEN OFFICE ON GOV COMPUTERS FOR TESTING AND GRADUAL ADOPTION.
- retraining people
- doc-> odf conversion (especially concerned about automatic conversion of documents-especially macros in doc files)
- and of course very concerned about support (there is no company's supporting Open Office - or they have no real business plans) what they see as the greatest risk migrating to ODF !!
This is 5 page document giving some numbers WITHOUT ANY EXPLANATIONS where those numbers came from. The only thing I noticed is that they ware waiting what happens in Munich at the time.They clearly know for IDABC initiative for ODF - ISO format. Their strategy is making public tenders to create support Open Office.
What I'm really concerned about is that there is no plan for gradual adoption of ODF. If there is a serious intent for adopting ODF I'd expect at least
Anyway I see this document as excuse to FLOSS community without any REAL intent to change things in the future.
This is the real picture of FLOSS support in EU. The point is that country's in EU take this reports as consideration but on the end they make their own conclusions based on MS deals because they can't make or don't want to make a real cost comparison.
One interesting negative point concerned those people (sometimes found here too) who believe that you only get what you pay for.
Reduce, reuse, cycle
Free can be either Gratis or Libre, stating Libre in the acronym emphasises that the intent of the acronym is to describe software that can be freely developed on and is not encumbered rather than describing software that is free as in price.
Don't be idiotic. I might just extend my assumption of "not read the paper" to "not read any serious paper". Your "conclusions in the paper" were the conclusions for the last section in the appendix. It wasn't even part of the paper - you obviously flipped to the end and read a subsection called "Conclusions" without realising it wasn't part of the actual paper. (even though there are several other subsections throughout the paper labelled "Conclusions", and you never ever put conclusions for the entire paper in a bloody subsection) Look at the Executive Summary for the real findings - that's what the Executive Summary is for.
Well, you can also program macros in Python an Javascript if you like. Nobody said you had to use StarBasic, or OO.O basic, which is what it's called on my version.
Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.