Work Package 6 Exploitation planning & Market study by Frode Skjævestad & Stein Runar Bergheim Asplan Viak Internet as
Overview Establishing the starting point / baseline How do we do it – methodology What are our products IPR and ownership Market study, indications SWOT and Potential Exploitation plan, selected products
TECHNOLOGY CONSTRAINTS As a totality, the Paths platform includes many technologies, i.e. many software components, many licenses, many upgrade schedules
Complexity of Platform JavaXMLJSON Doc- uments Postgre SQL Records Hier- archies Python Java- Script C#.NET SQLSOLR Mongo- DB IIS Mapnik PostGIS Apache Wind- ows Linux ESE Offline NLP tools iOS App
POTENTIAL SIZE OF MARKET Who may realistically be interested in using the entire PATHS platfom?
Total size of market Europeana/GLAM sector Technologically sophisticated Potential Size of Market Willing to replace/extend their technology stack
SELECT A STRATEGY Do we try to push the “entire thing” or bits and pieces – what is most likely to succeed?
«Divide & Conquer» PATHS Platform Further research Commercial exploitation Open Source contriibution Knowledge Software products Services, methodologies
HOW DO WE SET ABOUT IT Market study methodology
Methodology for development of exploitation plan
WHAT ARE OUR PRODUCTS AND SERVICES? The whole PATHS platform is comprehensive – but consists of many simple modules.
Paths «Products» Research results, knowledge PATHS as a paradigm for navigating (cultural heritage) collections, Information Retrieval, Recommender Systems, Natural Language Processing, Information Visualization Software products Natural language processing tools for enrichment of metadata, “Topic map”, map visualization of thesaurus, Recommender system: real-time generation of links to relevant content in same collection, Sentiment analysis for web content resources, Open Web API for working with PATHS Services, methodologies Content enrichment, Development of user requirements specifications, Web application user evaluation
Product Descriptions Exist in the individual deliverables D1.x, D2.x, D3.x, D4.x, D5.x The detailed description of each «Product» has not been repeated in the Exploitation plan Is modesty a virtue in this context? From the perspective of the reader, it would perhaps be less demanding to put everything into one document From the perspective of follow-up and implementation, a compact document is more handy as each follow-up activity only uses a small sub-set of info. Setting the boundary between implicit and explicit information is a challenge.
WHO OWNS PATHS PRODUCTS? IPR constraints of project results and propagated constraints from underlying components
IPR Ownership Matrix ProductLicenseIP owner NLP toolsGPL + propagated terms & conditions from licenses of optional vocabularies USFD, EHU Sentiment analysis toolsProprietary, exclusivei-sieve technologies Web API and information retrieval GPLUSFD, AVINET Recommender systemGPLUSFD, EHU “Map-based” visualization of thesauri GPLUSFD
HOW DO WE GET TO KNOW ABOUT OUR MARKET? Probing representatives of our market segment for feedback
What we wish to achieve? Learn market requirements for PATHS “products” Interest, attitude Current usage Delivery methods Business models Identify exploitation potential
Attitudes to Paths Products 77% interested or very interested 58% interested or very interested
Attitudes, continued 80% interested or very interested 81% interested or very interested
Attitudes, continued 88% interested or very interested 65% interested or very interested
Attitudes, continued 50% interested or very interested 77% interested or very interested
Attitudes, continued 46% interested or very interested 77% interested or very interested
Attitudes, continued 73% interested or very interested
Service Delivery & Money Willingness to pay In general, wants for free (most) Some acceptance of costs... License one-time, < 1000 € (some) License one-time, <10000 € (some) License per month € (many) License per year €(many) No willingness to pay per view/use/seat
Positive to Open Source Complies well with desire for «free» things Bodes well for those products that will be followed up using the Open Source strategy In line with recommendation from reviewers at second review
Potential of Products For each product assess: Strengths Weaknesses Opportunities Threats Filter out those who have have potential for follow-up
The Exploitation Plan Describe methodology Define PATHS products Define Intellectual Property Rights Summarize Market Study Identify Market Potential Decide Per Product Market Strategy Actions, Timings and Responsibilities
Filtering of Candidates Targeted exploitation activities for each component is time and resource consuming It is necessary to filter which «products» to pursue through structured actions Remaining «products» follow-up strategy indicated in SWOT
Selected for Exploitation 1/2 NLP tools for data enrichment Used and further developed in LoCloud Explore pay-per-volume service Open-source servers based on virtualization Open WebAPI for app development Avinet uses PATHS IR/Search Components in the upcoming release of Adaptive 3.0 A product with 60 server instances, thousands of users Good, market outreach and stable developer community Code for GPLed components available on GitHub
Adaptive Web API on GitHub
Selected for Exploitation 2/2 PATHS in alternative domains Pursuing a project on using Paths and implicit trails in the legal domain Utilizing log data to derive paths (in an implicit) way For legal professionals to capturing knowledge in a tangible way For educational/training purposes. Sentiment Analysis Tools for Digital CH Content i-sieve to use PATHS as showcase to approach CH clients with the help of other partners
Questions & Thanks for the Attention (Stein) Runar Bergheim