Académique Documents
Professionnel Documents
Culture Documents
Daniel Field
Internet of Services Collaboration event, Brussels
17/10/2012
Agenda
Introduction & Synopsis The role of an ownership and governance model in project exploitation The Baseline: Grant Agreement and Consortium Agreement 6 standard ownership models 3 standard governance models How to identify the right one(s) for your project Examples Conclusion
Introduction
About me
Business Consultant at Atos Spain, 5 years experience working in R&D Focused mainly on IoS: Cloud, software engineering, Grid etc. Chair of exploitation workshop in 2011 IoS meeting Heading a team of business analysts working in exploitation, involved directly or indirectly with more than 15 R&D projects ranging from large IPs to CSAs
Techniques developed over course of many projects (SMARTLM, Cloud4SOA, Aladdin, etc.) Recently formalized during the sustainability analysis for the BonFIRE project (IP in the obj. 1.7 (FIRE) unit). Acknowledgements to co-authors in BonFIRE: Kostas Kavoussanakis (EPCC); Michael Boniface (IT Innovation); John Barr (the 451 Group), Carmelo Ragusa (SAP), Frederick Gittler (HP).
The synopsis:
Exploitation uses a business model to generate value from IPR which is generated and claimed by partners. Exploitation needs a business model, an ownership model and a governance model. Certain combinations of these three models are untenable The basic options and process for determining these are common to all projects.
4
The synopsis
+
Business Model
A lot of practice
Whitepaper
A bit of theory
Knowledge sharing
Project Idea
Market Analysis
Business Modelling
Feasibility Analysis
Business plan
Exploitation
Project Idea
Technical results & innovation
Market Analysis
Partners Business models
Business Modelling
Feasibility Analysis
Existing Synergies Ownership & IPR Governance
Business plan
Exploitation
Governance model:
10
From experience, in many projects the consortium is left with the following issue to resolve:
but
How to breakdown the foreground and how to quantify the generating work is left unspecified.
Which means consortia must tackle this issue internally. Failure to address this issue will result in uncertainty over the right to exploit the results and prevent further investment.
Disclaimer: Not professional legal advice. Consortia should consult their own legal experts to interpret the relevant agreements.
14
15
1. Lines of Code The partner that wrote the code owns the asset. Joint ownership is assigned according to lines of code. Easy to implement Grounded in Grant Agreement legal framework Open to manipulation and deliberate code inflation Penalises efficient programmers over inefficient code writers
2. Technical Input All technical input (requirements, design, programming, review, testing) are summed to give contributions Fairer definition of generating work. Grounded in Grant Agreement legal framework. Absence of objective and quantifiable measures of input. Subjective decision required to weight different types of input.
Beyond the largest level of granularity this process becomes excessively complex.
17
3. Non-technical Input Here one selects a proxy for technical input choosing from: time-input (e.g. MM) or financial input (funding, own investment, cost) and potentially also including weightings of different activities Simple, fair, objective and quantifiable Grounded in Grant Agreement legal framework. Issues in practice: Are specialist hours equivalent to nonspecialist hours? Do we penalise efficient organisations for having a low overhead? Again complexity can be the killer if asset granularity is too fine.
18
These three models can be termed Bottom-up. They start with an agreement on how to do it, and then see what the result is. However: the result may not be ideal for exploitation: Assets may be co-owned by partners with wildly different exploitation paths Multiple owners of assets can lead to profit sharing and a disincentive for further investment Dominant ownership of key assets by one partner may result in them becoming kingmaker (or demanding a kings ransom).
19
An alternative approach is based on deciding on the desired outcome and working backwards to see what agreement the partners must reach. We can term these top-down. We propose three top-down approaches
20
4. Musketeer Model
Here all partners effectively become full owners of all assets regardless of input - with the right to act independently of each other.
No need to negotiate with other partners to deliver the full value chain. No need to share profits, increasing ROI of further investment. Collaboration is based on capabilities not IPR leading to more synergic joint ventures. A level playing field Legal and bureaucratic barriers are minimised. Some partners may be left marginalised due to their profile Partners could compete on identical basis if exploitation contract does not prevent this. Not grounded in Grant Agreement legal framework requires additional contract.
21
22
23
Joint Venture
24
25
A participating consortium members form an official venture to continue collaborating, short of a new legal entitiy but acting with some autonomy relative to parent organisations Shared benefits, risks Flexibility Low initial investment Hierarchy can be strong conferring benefit of new legal entity Easy exit route for partners can lead to instability Can require quorum on key decisons Difficulties aligning JV strategy with partners Profit sharing mechanism not clear
26
Consortium participants interact as per standard buyer-seller relationships, each providing a product or service in return for a fee (business as usual). Low initial investment Bureaucratically easy All partners incentivized to remain competitive Responsibility and profit sharing clear Underperforming partners can be swapped for competitors Without central control the overall value chain may not be optimised With too many links the chain will become unwieldy. Where switching costs are high, profits may be absorbed by a dominant partner Will favour some partners over others.
27
28
Choosing a model
We suggest that choosing the right model for ownership and governance are decisions which must include the business model. Some combinations simply will not work.
Business Model
We must analyse each potential combination in the context of the project
29
Choosing a model
Combining a Supply Chain with our ownership models The supply chain is based on each partner fulfilling a role in the value chain. Under top-down models this is not necessary as any partner can provide the full value chain. With bottom-up models, each partner has a role protected by their ownership of the assets required.
In the former, partnership is based on capabalitiy synergy. In the latter, there are risks relating to the bargaining power of partners and the complexity of the chain (dependent on the number of partners.
30
Choosing a model
Combining a new legal entity or joint venture with our ownership models Top-Down
The top-down models potentially provide all partners with all assets so collaboration is not required to gain control of the value chain: any partner could do so Again any partnership is based on capability synergies
31
Choosing a model
Combining a new legal entity or joint venture with our ownership models In a new legal entity IPR is either transferred or licensed to the new legal entitiy by the owners
All partners are in the NLE/JV & transfer Ownership All partners are in the NLE/JV but merely transfer access rights
Bottom up approaches
All partners are in the NLE/JV but only some transfer ownership (others license)
At least one co-owner of each asset is in the NLE/JV and can license or grant access rights Few partners are in and not all assets are covered
32
Choosing a model
Combining a new legal entity or joint venture with our ownership models bottom-up
All partners are in the NLE/JV & transfer Ownership
All partners are in the NLE/JV but merely transfer access rights All partners are in the NLE/JV but only some transfer ownership (others license)
At least one co-owner of each asset is in the NLE/JV and can license or grant access rights
Few partners are in and not all assets are covered
Choosing a model
- example results of the first stage analysis
New legal entity and joint venture Individual ownership Musketeer model Mutual Granting of Access rights Open Source model
Supply chain Individual ownership Musketeer model Mutual Granting of Access rights Open Source model
Viability
*
Viability
34
Choosing a model
- Combination with the business model
Questions to be asked for each business model include (inter-alia): Level of capital investment required. Level of operating investment. Value of the IPR transferred or in use, its uniqueness, resale value and exclusivity. Specific partners required (competencies, asset owners, etc.). Legal & bureaucratic hurdles Complexity of the system and differing partner objectives. The bargaining power of the endeavour (or supply chain link). Potential income & income distribution for each governance model The potential competition to each business model.
Choosing a model
- Final outcome
Taking Ownership and Governance into consideration as part of the exploitation roadmap will: Allow the project to design an ownership structure adequate for the intended exploitation Eliminate theoretically promising business models which are impractical at an early stage. Give direction to the project regarding establishing the governance structure and morphing the project to that structure.
Governance and Ownership model
New Legal Entity Bottom-up ownership Musketeer model Mutual Granting of Access rights Open Source model Joint Venture Bottom-up ownership Musketeer model Mutual Granting of Access rights Open Source model Supply chain Bottom-up ownership Musketeer model Mutual Granting of Access rights Open Source model
N/A N/A N/A N/A
36
BM #n
BM #1
BM #2
BM #3
BM #4
Examples
Pioneered musketeer model
Bottom-up Joint Venture Has used this process to identify 4 possible combinations (from 60)
37
Conclusions
Ownership and Governance are aspects which should be tackled early in exploitation. A number of Ownership and Governance models exist and are well known.
38
Further reading
This powerpoint and the whitepaper are available free (CC-BY-NC) at: Dropbox:
https://dl.dropbox.com/u/43532760/WHITEPAPER%20%20Ownership%20and%20governance%20models%20in%20collaborative%20I T%20projects%20-V10%20Oct%202012.pdf
Thank you
Atos, the Atos logo, Atos Consulting, Atos Worldline, Atos Sphere, Atos Cloud and Atos WorldGrid are registered trademarks of Atos SA. June 2011 2011 Atos. Confidential information owned by Atos, to be used by the recipient only. This document, or any part of it, may not be reproduced, copied, circulated and/or distributed nor quoted without prior written approval from Atos.
17/10/2012
License terms
This work is licensed under the attribution-NonCommerial CC BY-NC creative commons license. If you would like to use this work under any other terms please contact the author. You are free: to Share to copy, distribute and transmit the work to Remix to adapt the work
Under the following conditions: Attribution You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work). Noncommercial You may not use this work for commercial purposes.
41