Software Pricing and Business Models Maido Käära, Rando Mihkelsaar, Martin Raie, Lauri Vare, Rainer Villido

Total Page:16

File Type:pdf, Size:1020Kb

Software Pricing and Business Models Maido Käära, Rando Mihkelsaar, Martin Raie, Lauri Vare, Rainer Villido Software Economics - Homework 4 Software Pricing and Business Models Maido Käära, Rando Mihkelsaar, Martin Raie, Lauri Vare, Rainer Villido 1. In 2003, Scalix delivered zero revenues. Identify and analyze the possible reasons for this failure. In 2003 Scalix sales strategy was built around the notion that there were plenty of medium and large enterprises who were not satisfied their current e-mail system. There was two major companies offering e-mail solutions and switching to Linux-based e-mail solution was expensive. Also administrators didn't have skill set or the comfort to move to Unix-based e-mail systems. Because Scalix was a start- up it faced with the challenge of establishing credibility. Pilots showed that the product wasn't mature - users wanted more functionality (for example single-sign-on, Active Directory, Windows-like graphical administration environment support) compared to Microsoft Outlook. 2. Who were the target customers of Scalix as of June 2004? What obstacles was Scalix facing in June 2004 and what were their options for overcoming those obstacles? The target customers before were medium and large enterprises looking for a corporate messaging solution. Large enterprises had lack of trust in Scalix as a small start-up that had not gained any customers. Until June 2004 the only customers they had were from mid-market public sector deals like city of Bloomington, Indiana with about 800 seats and the county of Pottawattamie, Iowa with about 300 seats. They also tried to extend their business to international market and small enterprises. There were two main obstacles for Scalix. First one was selling to international customers. Because setting up an European telesales organization was difficult for a number of reasons they overcome that problem by signing up resellers to focus on the German small enterprise market. Second problem was with domestic small enterprises like Cincinnati Financial which is a holding company with subsidiaries which underwrite fire, automobile, casualty and other forms of insurance. They had 3000 employees and were vigorous Linux adopters. Problem was that Scalix didn't have everything in place by that time, like 24/7 support which is very important for a company that size. Also Cincinnati Financial didn't really like the idea that Scalix didn't have any other clients their size. To overcome their problem they needed to get more clients and get their services like 24/7 support up and running. The main problem was a lack of trust caused by lack of customers. In order to gain trust, they needed to gain more customers to use their solution. Open sourcing would be a way to penetrate small enterprise market by letting the product to be free for small enterprises. That way, they would get more users to their solution and would build up their trust in large enterprises to whom they could sell their corporate product. 3. Using the framework exposed in the article by Rajala et al., analyze the business model of Scalix Corporation at the time the case study was written (2005). The framework described in the article is used to analyse software companies' and their business models. The categorization of different business models is based on the following four features: "product strategy", "revenue logic", "distribution model", "services and implementation". The values of those four features for the Scalix Corporation are as follows: ● Product Strategy - Uniform core product Scalix is an enterprise e-mail, calendar and collaboration software solution. ● Revenue Logic - License sales and royalties Revenue is collected from licenses sold (per seat pricing) and yearly maintenance fee. ● Distribution Model - Direct contact with customers Direct contact between customers and Scalix's inside sales representatives and field sales representatives. ● Services and Implementation - On-line services, Self-services Software is deployed and maintained by customers themselves. Scalix offers on-line technical support. 4. In July 2006, Scalix adopted an open-source strategy. Analyze the open-source strategy of Scalix, the reasons for adopting this strategy, and the impact of this strategy on the business model of Scalix. Scalix now has dual licensing model. The Scalix Public License is based on the Mozilla Public License and is a non-permissive license. There is also a commercial license for the Scalix enterprise product. The Community Edition is a product for organizations that don't need the Enterprise Edition and can still use the messaging solution. Since they had difficulties building up their customer base and many new customers wanted to see larger customer base before they agreed to adapt to Scalix. They didn’t trust a start up without customers. Open Sourcing lesser version (Community Edition) of their product would help them gain customers from smaller companies so that larger companies would follow with paying for the enterprise license (Enterprise Edition). According to Scalix, the product has rapidly gained popularity after the open source version was released. Becoming more popular and widely used would make them more trustworthy for larger enterprises as selling enterprise licenses, proprietary components, product support and training are the main sources of revenues for Scalix. Before open sourcing, the successful sales have been with mainly smaller companies (and in public sector) who consciously want to adopt Linux and cut costs on IT spending dramatically (like Pottawattamie County for example). Very often these companies have people in their IT staff (so called Linux guys) who know more about Linux and are more likely to prefer Linux over Microsoft. The smaller the companies are, the more likely techies can influence decision making. Many customers had discovered Scalix on their own and not with help of intensive sales force. This was a new market segment for Scalix that provided new opportunities. Also, many new competitors from Linux world were emerging. Companies like Novell (with their GroupWise enterprise collaboration solution), Stalker Software, and Bynari all provided their own Linux-based messaging solutions. Scalix product was further behind than his competitors and something needed to be done about that. Being open source, Scalix can have relationships with other related open-source communities to support the product, like support for anti-virus, anti-spam etc. As a result of open sourcing their product, Scalix gained more popularity and trust in their product and can sell it more easily to the enterprise customers who are willing to pay for the enterprise license and additional services. These customers are their main target market. 5. In July 2007, Scalix was acquired by Xandros. Analyze the business reasons behind this acquisition both from the viewpoint of Scalix and that of Xandros. How has Scalix been integrated into Xandros? In different news about this acquisition the representatives of both parties tell why this deal was good for them. We don't know the actual business reasons behind this but according to the news it seems that it was meant to be and both parties are pleased with it. Even the FAQ-s on Scalix's home page say that it was natural to explore the acquisition - Scalix and Xandros have already had close engineering and executive level working collaboration. Scalix wanted to expand their business but they seemed to have not enough resources for that. They were too small to make large enterprise customers trust them. Acquisition by Xandros increased their credibility. It also gave them access to much larger financial and engineering resources and significant new technologies in order to maintain, develop and enchance their products. Furthermore, Scalix will continue to operate independently and their products will continue to be developed with the same vision and roadmap as planned and the interoperability of Scalix on Xandros, RedHat, SUSE Linux and other distributions will remain exactly the same. Xandros will also continue Scalix-related open source projects. Scalix customers will benefit from strengthened support and service offerings provided through a larger combined reseller and partner network. With more offices around the world they would get new customers more easily too. So, from Scalix's point of view everything seems to be great. The only negative side is that they don't own the company anymore but the money they got from the deal should have compensated this. Even the sales support and engineers staff stayed on with Xandros, although vice president of finance left the company. The President and CEO Glenn Winokur stayed through the transition and became a member of Xandros' advisory board. From the viewpoint of Xandros, the aquisition was quite good as well. Xandros was looking to build up their solution stack. They already had desktop, SMB and advanced enterprise servers and management tools to run these. But they felt that one of the most important components of an end-to-end solution is e-mail. Having an e-mail server would be a huge benefit. And since Scalix had been the leader on open source market it was the best choice. Now all important elements of their solution were under one roof. Xandros had already integrated Scalix into their desktop and server but now they were looking to add significant dimensions to it. Mainly they have brought out the fact of fulfilling their vision of being an end-to-end solution company. Now they just had to make their investment to earn back. Otherwise the acquisition would not have been that good. The current tight integration of Scalix within the Xandros Server provides an all-in-one groupware solution that can be centrally administered through the remote, all-graphical Xandros Management Console. The combined solution provides business clients with scalable industrial strength world-class e-mail and calendaring, with choice for a wide array of e-mail rich clients, including Outlook, Thunderbird, the AJAX-based Scalix Web Access Client, as well as various popular wireless handheld devices.
Recommended publications
  • About SEP Sesam Hybrid Backup and Disaster Recovery
    Hybrid Backup & Disaster Recovery SEP sesam’s Backup & Disaster Recovery Capabilities for the Red Hat Ecosystem 1 Global Storage Management SEP sesam’s Backup and Disaster Recovery Capabilities for the Red Hat Ecosystem Table of Contents Table of Contents 1 About this Document 3 About SEP 3 About SEP sesam Hybrid Backup and Disaster Recovery 3 SEP’s Mission 4 Red Hat Statement 4 SEP‘s Collaboration with Red Hat 5 Value Proposition for Red Hat Solutions 5 Red Hat® Enterprise Linux 7 Bare Metal Recovery Capability for Linux 8 Red Hat® Virtualization 8 Red Hat® Virtualization Backup White Paper 8 Red Hat® Storage 9 SEP‘s Collaboration with SAP 9 SAP HANA Certifications 10 SAP Ecosystem - Protection Overview 10 Datacenter 10 Platforms 10 Hypervisors 10 Operating Systems 10 Databases 11 Applications 11 SAP Statement 11 SEP sesam Customer References in SAP Environments 11 Uniorg 11 Kwizda 12 Linck 12 Inecom Business Solutions 12 Service Provider and Cloud engagement 12 SEP was named one of the 2018 Gartner Peer Insights Customers’ 12 Choice for Data Center Backup and Recovery Software Here are a few examples of our customers statements: 13 Summary / Authors 13 www.sepsoftware.com I SEP sesam’s Backup and Disaster Recovery Capabilities for the Red Hat Ecosystem 2 Global Storage Management SEP sesam’s Backup and Disaster Recovery Capabilities for the Red Hat Ecosystem About this Document This document serves a Red Hat® and SEP value proposition for the joint solutions. Beside of general information we will highlight the sup- port of Red Hat® Virtualization, Red Hat® Enterprise Linux®, Red Hat® Storage, SAP and Service Providers.
    [Show full text]
  • Head-To-Head: Zimbra Vs Scalix
    Head-to-Head: Zimbra vs Scalix Key Positioning vs Scalix • Innovation leadership . Zimbra has consistently demonstrated innovation leadership in emerging areas of messaging and collaboration, including web-based mash-ups (Zimlets), rich web document authoring and sharing, native over-the-air mobile synchronization, comprehensive server-side indexing/search, and VOIP. Conversely, with less demonstrable innovation, Scalix has relied mostly upon TCO positioning based on Linux. In addition, Scalix’s reliance on HP OpenMail (15+ years old and discontinued by HP) and Oddpost limit Scalix’s ability to innovate in core product areas. • Foundation in open source. Zimbra started as an open source company (as most leading open source projects have done) and open sources all of its key product components -- providing full product transparency and customer investment protection. Conversely, Scalix is attempting to migrate to open source (a strategy without successful market precedent), is open sourcing a discontinued code base (likely not attractive to the open source community), and has no plans or entitlements to open source its web client. In addition, Zimbra has strong relationships with leading open source companies (such as Red Hat and MySQL), is deployed at many leading open source vendors (such as Digium/Asterisk and Mozilla), and has been a key contributor to open source projects such as the OpenAjax Alliance. Finally, Zimbra’s open source foundation enables clean bundling of best-of-breed open source components as product building blocks – a strategy Zimbra regularly employs with the Zimbra Collaboration Suite (which currently bundles 40+ open source components) to rapidly provide innovation and high-quality solutions.
    [Show full text]
  • Installing the Scalix Management Console
    Scalix Installation Guide Version 11.0.01 1 Scalix Installation Guide Notices The information contained in this document is subject Published by Scalix Corporation to change without notice. 1400 Fashion Island Blvd., Suite 602 Scalix Corporation makes no warranty of any kind with San Mateo, CA 94404-2061 regard to this material, including, but not limited to, the implied warranties of merchantibility and fitness USA for a particular purpose. Scalix Corporation shall not be liable for errors contained herein or for incidental Contents copyright © 2007 Scalix Corporation. or consequential damages in connection with the All rights reserved. furnishing, performance, or use of this material. Product Version: 11.0.1 Unix is used here as a generic term covering all versions of the UNIX operating system. UNIX is a E: 2.12.2007 registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. Linux is a registered trademark of Linus Torvalds. Red Hat, and Fedora are registered trademarks of Red Hat Software Inc. rpm is a trademark of Red Hat Software Inc. SUSE is a registered trademark of Novell Inc. Java is a registered trademark of Sun Microsystems Inc. Microsoft, Windows XP, Windows 2000, Windows NT, Exchange, Outlook, Active Directory, and Internet Explorer are either registered trademarks or trademarks of Microsoft Corporation in the United States and other countries. Restricted Rights Legend Use, duplication, or disclosure is subject to restrictions as set forth in contract subdivision (c)(1)(ii) of the Rights in Technical Data and Computer Software clause 52.227-FAR14. 2 Scalix Installation Guide | Contents Introduction To This Guide .
    [Show full text]
  • Auf Und Ab Groupware
    08/2015 Die Entwicklungen bei Linux-Groupware – eine Zwischenbilanz Sysadmin Auf und ab Groupware 58 Der Groupwaremarkt ist ebenso groß wie schwierig: Microsoft Exchange und Lotus Notes halten die dicken Brocken fest, soziale Netzwerke und Google drängen nach. Freie Software kann gleichwohl auf schöne Erfolge verweisen, gerät aber immer wieder in die Opferrolle – meist wegen externer Finanzierung. Markus Feilner, Dirk Ahrnke www.linux-magazin.de Connect (Abbildungen 1 und 2). Obwohl einige Einzellösungen aus dem Linux- und Open-Source-Umfeld, zum Beispiel Spam assassin, Open SSL und Qt, inte- griert sind, vertreibt Kerio sein Produkt Connect vollständig und ohne jede Aus- nahme unter einer proprietären und rein © mahout, 123RF © mahout, kommerziellen Lizenz. Außer für Linux ist das Produkt darüber hinaus auch für Windows und Mac OS X erhältlich. Gerade Letzteres dürfte eini- ges zur Verbreitung beigetragen haben, denn für die Apple-Serverplattform gibt es relativ wenige Groupwarelösungen. Kerio hat zudem auch als einer der ersten Dritthersteller eine Implementierung der Exchange Web Services (EWS) geschafft. Unter OS X setzt mittlerweile nicht nur Outlook auf die HTTP-basierte Anbin- dung an Exchange. Seit OS X (Snow Leo- Vier Jahre her ist der letzte Groupware- sehen sich dabei natürlich Produkte, pard) lässt sich auch das zum Mac-Sys- vergleich im Linux-Magazin [1] – Grund deren Entwicklung (zum Teil) in einer tem gehörende Mail via EWS anbinden. genug, erneut den Blick auf die für Un- Community erfolgt – sprich Open-Source- ternehmen wichtige Collaboration-Sparte Software. Diese Einschätzung teilt die Caldav und Carddav zu richten, die allein in Deutschland rund Wagniskapitalbranche offenbar, denn in 700 Millionen Euro Jahresumsatz schwer die meisten Groupware-Unternehmun- Es sind allerdings nicht nur die alterna- ist.
    [Show full text]
  • Exploring Open Source Options the Redmonk Going Open Source Series, Part 1
    April 19, 2007 Page 1/9 Exploring Open Source Options The RedMonk Going Open Source Series, Part 1 Overview Now more than ever, one of the top questions for a software company is: Michael Coté to what degree should we participate in open source? Open source is James Governor indisputably the most significant trend affecting the software world at the current time. More than any other single approach, strategy, or tactic, open Stephen O'Grady source has compelled vendors once thought to be unassailable in their respective markets - such as IBM, Microsoft and Oracle – to significantly alter their strategies. While substantial attention is paid to the source aspects of the code –the fact that it is visible, and in some cases alterable and distributable – the distribution advantages may be the most transformative, at least in the commercial world. From application servers to operating systems to programming languages to relational databases to web servers, very few categories of infrastructure software have been immune to open source competition. The packaged application market appears to be the next archipelago in the path of the tsunami, and vertical applications are undoubtedly close behind. None of this is to say that open source is necessarily the single path forward for software vendors; while that may or may not be true in the distant future, it is being actively refuted by the continuing ability of vendors such as Microsoft and Oracle to sell products that are less freely available and higher priced than their open source competition. In the case of many, if not most, of these established vendors, however, success rests more on the basis of significant market barriers to entry than on pure technical grounds.
    [Show full text]
  • Funambol Installation and Administration Guide
    Funambol Installation and Administration Guide Last modified: January 5, 2011 Table of Contents 1. Introduction....................................................................................................................... 6 2. Getting started................................................................................................................... 7 2.1. Preparing a host computer............................................................................................................... 7 2.1.1. Minimum system requirements...............................................................................................7 2.1.2. Preparing the Funambol Server package installation............................................................ 7 2.2. Obtaining the Funambol Server package......................................................................................... 8 3. Installing the Funambol Server package......................................................................... 9 3.1. Installation on a Windows host server.............................................................................................. 9 3.1.1. Verifying the server startup..................................................................................................... 9 3.1.2. What to do if the server does not automatically start............................................................ 10 3.1.3. Run Funambol As Microsoft Windows Service (from XP to above)...................................... 10 3.2. Installation on a Linux host
    [Show full text]
  • Servicio De Mensajería De Correo Utilizando Software Libre Para
    Servicio de mensajería de correo utilizando software libre para mejorar el tiempo de respuesta de atención Tesis para optar el Título de Ingeniero de Sistemas y Cómputo Presentado por César Antonio Rojo López Asesor Dr. Santiago Raúl Gonzales Sánchez Lima – Perú Noviembre de 2020 DEDICATORIA Dedico este trabajo a mi familia particularmente a mis padres Mercedes López de Rojo y César Rojo Fernando como también a mi prometida Ximena Veliz que dia a dia me dan fuerza y motivacin para seguir adelante, como también al Gerente General de TecnoWeb Latam Diego Benavente por brindarme todas las herramientas para la implementación tecnologcia. 2 ÍNDICE ÍNDICE DE FIGURAS ............................................................................................................................. 5 INDICE DE TABLAS ............................................................................................................................... 7 RESUMEN ................................................................................................................................................. 8 ABSTRACT ............................................................................................................................................... 9 INTRODUCCIÓN ................................................................................................................................... 10 CAPÍTULO I: PLANTEAMIENTO DEL PROBLEMA ..................................................................... 12 1.1. Situación Problemática ..........................................................................................................
    [Show full text]
  • Scalix Installation Guide
    Scalix Installation Guide Version 12.5 1 Scalix Installation Guide Notices The information contained in this document is subject Published by Scalix, Inc. to change without notice. Scalix Inc. Scalix Inc. makes no warranty of any kind with regard 488 Madison Ave, to this material, including, but not limited to, the 4th Floor, implied warranties of merchantability and fitness for New York, NY a particular purpose. Scalix Inc. shall not be liable for 10022 errors contained herein or for incidental or conse- quential damages in connection with the furnishing, performance, or use of this material. Copyright © 2015 Scalix, Inc. All rights reserved. UNIX is a registered trademark of The Open Group. Product Version: 12.5 Linux is a registered trademark of Linus Torvalds. Document Revision: 5 Fedora is a registered trademark of Red Hat, Inc. Red Hat is a registered trademark of Red Hat Software, Inc. Enterprise Linux is a trademark of Red Hat, Inc. RPM is Notice for Open-Source Software a trademark of Red Hat Software, Inc. Copyright (c) 1998-2013 The OpenSSL Project. All rights reserved. SUSE is a registered trademark of Novell, Inc. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are Java is a registered trademark of Sun Microsystems, met: Inc. 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. Microsoft Windows 8,Windows 7,Windows XP, 2. Redistributions in binary form must reproduce the above copyright Windows 2000, Windows NT, Exchange, Outlook, notice, this list of conditions and the following disclaimer in the doc- umentation and/or other materials provided with the distribution.
    [Show full text]
  • Linux Client Migration Cookbook Version 2
    Front cover Linux Client Migration Cookbook, Version 2 A Practical Planning and Implementation Guide for Migrating to Desktop Linux For any organization that is exploring or planning for a Linux desktop migration Provides in-depth detail on the technical and organizational challenges Includes methods for planning and implementation Chris Almond Jeroen van Hoof Nick Lassonde Ben Li Kurt Taylor ibm.com/redbooks International Technical Support Organization Linux Client Migration Cookbook, Version 2 A Practical Planning and Implementation Guideline October 2006 SG24-6380-01 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. Second Edition (October 2006) © Copyright International Business Machines Corporation 2004, 2006. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Notices . xi Trademarks . xii Forward . xv Bernard Golden, Navica . xv Greg Kelleher, IBM . xvii Preface . xix The team that wrote this redbook. xx Acknowledgements . xxi Become a published author . xxii Comments welcome. xxii Part 1. Choosing Linux. 1 Chapter 1. Introduction. 1 1.1 The migration landscape today . 2 1.2 Identifying suitable environments . 2 1.3 Strategic context . 3 1.4 Client environments. 5 1.5 Why Linux . 6 1.6 Linux overview and distribution choices . 7 1.7 Desktop Linux futures . 7 1.8 The rest of this book . 23 Chapter 2. The case for migration . 25 2.1 Why migrate . 27 2.1.1 Desktop security . 27 2.1.2 Costs related to Linux client . 32 2.1.3 Manageability of the Linux client .
    [Show full text]
  • Doc-To-Help Standard Template
    GO!NotifyLink Pre-Installation Guide Enterprise Server Pre-Installation Checklist Globo Mobile Technologies What's in this Document 1 Table of Contents What's in this Document 3 System Hardware Recommendations 4 Pre-Installation Tasks 6 Port Requirements and Connection Tests 9 CommuniGate Pro Port Requirements and Connection Tests ............ 10 Exchange Port Requirements and Connection Tests .......................... 11 FirstClass Port Requirements and Connection Tests .......................... 12 GroupWise Port Requirements and Connection Tests ........................ 13 Kerio Port Requirements and Connection Tests ................................. 14 MDaemon Port Requirements and Connection Tests ......................... 15 Meeting Maker Port Requirements and Connection Tests .................. 16 Mirapoint Port Requirements and Connection Tests ........................... 17 Oracle Communications Unified Communications Suite Port Requirements and Connection Tests .................................................. 18 Oracle Port Requirements and Connection Tests ............................... 20 Scalix Port Requirements and Connection Tests ................................ 21 Sun Java Enterprise System Port Requirements and Connection Tests22 Zimbra Port Requirements and Connection Tests .............................. 24 Enterprise Server Software Installation 25 Post Installation Tasks 27 Server Configuration ........................................................................... 27 User and Device Activation ................................................................
    [Show full text]
  • What's New in Gnome 2.10
    REVIEWS Gnome 2.10 What’s new in Gnome 2.10 LOOKING FOR TRACKS The new Gnome desktop adds a variety of applications and applets. Under the hood, Gnome 2.10 is more robust. BY CHRISTIAN MEYER ince version 2.0, Gnome has the Gnome panel. Whereas previous harvested both criticism and versions had two entries: Applications Sacclaim. Just two and a half and Actions, Gnome 2.10 introduces a years ago, nobody would have consid- completely new structure with three cat- ered it possible for a graphical desktop egories: Applications, Places, and with a six month release cycle to main- System. tain the high quality standards that The Application category still has the Gnome has maintained. full set of Gnome programs, but now Despite the integration of new func- contains the Run program… item, which tions, the basic libraries continue to be was previously assigned to the Actions downwardly compatible, and this is category. something that has convinced major IT Places takes you to frequently used players such as Red Hat, Novell, or Sun directories. These frequently used direc- to use Gnome as the basis for their prod- tories could include home directories, uct lines. bookmarks from the file browser dialog, The new Gnome Version 2.10 down- any removable media mounted right load became publicly available on 9th now, any network servers, and the last March. This article will be looking at the few documents you opened. You can most important changes introduced by connect to a server from here and search Gnome 2.10, many of which are not just for locally or remotely stored files.
    [Show full text]
  • Market Observation D12.3 Report on Key Technology Issues in Current EAI, E- Business and Knowledge Management (Enterprise Collaboration with Semantic Web Services)
    Report on key technology issues in current EAI, E-Business and Knowledge Management DIP Data, Information and Process Integration with Semantic Web Services FP6 - 507483 Deliverable WP 12: Market Observation D12.3 Report on Key Technology Issues in Current EAI, E- Business and Knowledge Management (Enterprise Collaboration with Semantic Web Services) Joachim Quantz, Berlecon Research Thorsten Wichmann, Berlecon Research January 4th , 2005 Deliverable 12.3 i 04/01/2005 Report on key technology issues in current EAI, E-Business and Knowledge Management EXECUTIVE SUMMARY Work Package 12 provides the DIP consortium and in particular the technology providers in DIP with real-world background information on potential application areas for Semantic Web Services (SWS). This deliverable continues the work started in D12.1 and provides an in-depth analysis of the potential of SWS in Enterprise Collaboration. Enterprise Collaboration is the second application area investigated in detail after Business Process Management, which is evaluated in Section 4 of D12.1. Subsequent deliverables will analyse the other application areas having high potential for SWS, namely content syndication, search/mining, and social software. Enterprise collaboration is an application area combining technology from portals, groupware and personal information management (PIM). It comprises basic groupware solutions (e.g. Microsoft Exchange), collaboration infrastructure (e.g. Lotus Workplace), and complex portal technology (e.g. Plumtree). Its main purpose is to provide all functionality needed for business collaboration within and across enterprise boundaries. Instead of having separate standalone products for functionality such as document exchange, conferencing, messaging or scheduling, an integrated solution will be required in the future Semantic Web Services could be used in enterprise collaboration to • realize the interfaces provided by the various collaboration components, • provide centralized information used throughout the individual collaboration components, e.g.
    [Show full text]