Open Source TCO: look at the COSPA frameworks (part 1)!
The EC funded COSPA project recently mentioned, defined frameworks to identify possible returns or losses of a transition to Open Data Standards or Open Source software.
Two frameworks by clbaran
The Workpackage 3 derived two frameworks. The first one, from assimilation theory, is aimed at investigating adoption, is in relation to the often-found gap between initial acquisition and eventual adoption of a technology.
Acquiring Open Source software is easy, so the distinction between the adoption events of acquisition and actual deployment of a technology is of great importance. Considering that most of the time there is no blueprint indicating the required steps to guarantee successful deployment of OSS, the gap between the acquisition and actual deployment is often significant.
The following set of constructs form the framework used to investigate the assimilation of Open Source software:
- Organization age & size – Older organizations are expected to be risk averse and less likely to undertake radical IT implementation initiatives such as OSS. Also, larger organizations may be better able to leverage the advantages of new technology, and have access to appropriately skilled personnel.
. - Industry type – Certain industry types may be more capable of leveraging the benefits of technology as it may suit their particular value chain configuration.
. - Strategic investment rationale – Strategic value propositions may justify resource commitments to adopt potentially beneficial technologies.
. - Increasing returns to adoption – Economies of scale and network externality effects may arise through the increasing contribution of additional adopters.
. - Knowledge barriers – extent of experience – Assimilation of new technology can be impeded by lack of relevant knowledge or experience.
. - Top management championship – New technology assimilation may require radical and high-risk initiatives that require proactive top management championship.
. - Extent of coordination – Coordination of knowledge across functional units of the organization can promote risk sharing & educate as to benefits of new technology.
. - Sophistication of IT infrastructure – Organizations with sophisticated IT infrastructure are more likely to have higher levels of knowledge about new IT possibilities, and thus embark on innovative IT assimilation.
The second framework – related to the cost of transition – is aimed at revealing the causes of costs in relation to a specific context, especially to determine lock-in situations or to identify intangible costs. Intangible costs represent 75% of the IT when effects of innovation and productivity are monitored over more than five years, hence the importance to assess such costs.
TCO takes into account hidden costs and their propagation in the long run better than ROI, but also Switching Costs are important to better understand lock-in situations. Some switching costs are created by the vendor (endogenous) and are often measurable, others are exist in their own (exogenous), like the cost of gathering information about alternative products or vendors. Implicit costs, as customer uncertainty, are not measurable and often not even identifiable.
The framework used to assess the cost a transition to OSS take into account the Migration path (total migration from proprietary, partial from proprietary, partial from mixed, from scratch), the Type of Administration (High/Low economic resource growth, High/Low size of the organization) and with a strong emphasis on the difference between volatile nature of costs of migration and the cost of ownership.
Both migration and ownership costs depend on context, types of migration and organization, as above discussed. The framework defines measures and questions about five main causes of costs:
- Learning/training.
. - User acceptance: usefulness and ease of use;
. - Unproductive user labour: lack of productivity due to excessive time spent in training;
. - Internal training methods: casual learning/self-support;
. - Formal training methods: expenses for course time.
. - Software.
. - Acquisition and licenses fees: software and add-ons, installation included;
. - Maintenance: cost of routine tasks;
. - Operational interoperability;
. - Non standard PC configuration: configuration of new software;
. - Security: licenses cost to prevent security violations.
. - Contracts.
. - Loyalty programs: benefits from incumbent;
. - Contractual agreements: contractual commitments costs, including compensatory or liquidated damages.
. - Staffing.
. - IT-Staff payroll: including overtime and bonuses.
. - IT-Staff attitude/culture.
. - Support.
. - External consultancies: fees for external support and services;
. - Support search: including services for seeking qualifying apps and quality evaluation;
. - Security: labour cost for preventing security violations.
The next post will cover some case studies, focusing on how Open Source software is being used by public authorities across Europe.
A new light by 
Roberto Galoppini, 
Michel, and 2 others are discussing. 
Reply