Emergic: Rajesh Jain's Blog

Emergic: Rajesh Jain's Blog header image 2

Emergic: The Vision

August 24th, 2002 · No Comments

Have been meaning to do a detailed write-up for quite some time. I finally got some time recently, and put this longish note together. It consolidates a lot of my thinking in recent months. (It needs to be linked with some of my earlier posts to add depth – will get around to doing that sometime later.)

The Concept

Emergic is about creating a software platform which brings down costs of technology by a factor of 10, thus making it affordable for consumers and enterprises in the worlds emerging markets.

Emergic is about realising Bill Gates vision of a computer on every desktop and in every home a vision which has not yet gone beyond the worlds 10,000 large companies and 500 million consumers, most of whom are in the worlds developed markets.

Emergic is going to become the computing platform for the next 500 million consumers and the worlds 25 million SMEs who have not been able to adopt technology because of its dollar-denominated pricing.

Emergic is targeted at the worlds emerging markets, because they are where technology has not yet penetrated deeply, and yet, for whom, technology offers perhaps the last opportunity to better integrate into the worlds value chain and improve the standard of living for their people.

The Emergic architecture provides 4 key benefits, which are unmatched in any existing solution in todays marketplace:
1. Brings down the cost of hardware on the desktop to USD 125-150
2. Brings down the cost of software on the desktop to USD 5-10 per person-month
3. Creates a solution that is easy to manage and scale through server-based computing
4. Integrates with the Windows world, by supporting MS Office file formats

Emergic is a solution which can thus bring down the total cost of ownership of technology (hardware, software, training, support) to no more than USD 15-20 per person-month. More importantly, from an emerging market perspective, it ensures that most of the IT spend is recycled among local companies, thus providing a fillip to the domestic IT industry, especially the independent software vendors (ISVs).

The key components that comprise Emergic:

  • Enterprise Server side: Thick Server
  • Enterprise Client side: Thin Client and Digital Dashboard
  • Enterprise Applications: eBusiness Suite and RosettaNet Basics

    Thin Client-Thick Server

    Tentatively christened Emergic Freedom, this is the Linux-based platform which can bring down computing costs dramatically by leveraging older computers (anything from 486 machines with 16 MB RAM will work) and combining it with a Linux-based desktop (KDE) and set of open source applications (Evolution for email and calendaring, Mozilla for browsing, OpenOffice for the productivity applications word processing, spreadsheet and presentation, GAIM for instant messaging, providing a single-window login to Yahoo, MSN, AOL, ICQ and Jabber). Think of TC-TS as providing new wine in an old bottle.

    What is different about Thin Clients this time around? After all, theyve been talked about ever since computing began.

    The major difference is the re-use of older hardware. We use older cars, older manufacturing plants, older homes, but we dont tend to use older computers. The problem is that on the desktop, we do not get access to older software from Microsoft! Only the latest versions of Windows and Office are available all of which require the latest processors and plenty of memory. It is a vicious circle which forces upgrades of desktop computers every 3-4 years. It also maintains Microsofts monopoly on the desktop there is no alternative because the world uses DOC, XLS and PPT file formats.

    The price points of USD 700-900 for a new desktop and USD 500 for MS Windows and Office may be fine in countries like US, UK, Germany and Japan, but it pinches a lot (and is almost unaffordable for the masses) in countries like India, China, Brazil and Mexico. For these low-income markets, hardware and software need to cost a tenth to bring them in line with what their people are earning for technology to go mass market and become a utility. Older PCs can now be leveraged as Thin Clients, without sacrificing performance or the desktop look or the applications.

    The worlds developed markets have been saturated with technology. New PC sales now imply upgrades, creating a huge supply of older computers. The PCs that are being still have a lot of life left in them after all, they are no more than a few years old. These PCs, which incidentally have become an environmental hazard in the developed markets, can now be shipped to the emerging markets where the Emergic platform brings them to life once again on the desktops and in the homes of people who may never have tasted computing. These PCs can be available for USD 100 or so in large numbers or more USD 125-150 in smaller quantities. Add USD 50 if one only uses the old motherboard and goes in for a new keyboard, mouse and monitor.

    This happens because of the use of Linux in a server-computing mode. All the applications are run off the server, with only the display happening on the client side. In that sense, the desktop becomes a Terminal. The difference this time around is that the Linux-based Thin Client has all the key applications that the majority of people need to use (email, browser, instant messaging, word processing, spreadsheet, presentation) and there is no performance penalty even though the applications run off the server. The most recent releases of the open source versions of the applications is now more than good enough both from the point of view of stability and Windows compatibility.

    Server-based computing using Linux (and built on the X protocol) is now possible because LAN speeds have gone up to 100 Mbps enabling the transfer of a lot more data over the same network. The result is that a Thick Server (which is actually a new desktop with 1 GB RAM and 2 hard disks in a software RAID configuration) can easily support 30-40 users. Such a Server would cost about USD 1,500-2,000, implying a per client cost of no more than USD 50.

    Taken together, the Thin Client and Thick Server combination not only brings down the cost of both hardware and software by 90%, but also provides the IT manager complete control of the client desktop from the server. What every user sees on their Thin Client can be standardized and controlled from the Thick Server itself. In addition, the use of Linux does away with all the virus-related problems. Server-based computing also centralises management of data (backup and restore, for example).

    The Thin Client-Thick Server solution is ideal for three environments:

    1. Where there is software piracy (illegal copies of Microsoft Windows and Office). At one stroke, all users can now be given legal compatible software for a small incremental cost (10% or less of what MS Windows and Office would cost). Considering that Microsoft and the Business Software Alliance have been targeting businesses in emerging markets, the Emergic architecture provides an alternative which is not disruptive and can be implemented very rapidly.

    2. Where there is an abundance of older PCs and the upgrade costs are proving to be prohibitive. This is where the same older PCs can now be converted into Thin Clients, thus protecting the investment that has already been made.

    3. Where computing is not present. This means providing a computer on the desktop of every person in the organisation. Consider the economics: the Thin Client-Thick Server solution costs about USD 15-20 per person-month. This means that if a person earning USD 150-200 per month can become 10% more productive using a computer, the investment pays back from itself from day one! The computer is perhaps the most transformative invention in the past century and the defining device for todays Information Age. It has significantly improved productivity wherever it has been utilised. The emerging markets of the world and the bottom of the enterprise pyramid are where computers have not yet penetrated because of their costs. The Thin Client-Thick Server solution now makes it possible to level the technology playing field for the SMEs in the emerging markets.

    The limitation of course is that this solution will not support native Windows applications. There are some alternatives:

    1. Try out Wine and other solutions on Linux (Win4Lin, Crossover Office) to see if they will support Windows applications.
    2. See if the client application can work in a browser; the back-end can be Windows 2000 or anything else.
    3. Use vncviewer to provide a Windows desktop (on a Linux Thin Client) grabbed from a Windows machine (only one user at a time).
    4. Use the Windows Terminal Server to provide multiple users access to Windows on the Thin Client.

    The way I look at it is that our primary focus should be on users who are either non-users or need just the base set of applications. We are not trying to position this as a Windows-clone. This solution will co-exist with Windows. Our approach is to look at whom we can delight rather than whom we may disappoint.

    The Thin Client-Thick Server as envisioned here leverages the R&D that has given in the world. No solution for the bottom of the pyramid can be cost-effective if it involves significant R&D efforts (and the time associated with it), especially in technology where the research costs are huge. By lagging hardware technology by a few years but creating software using the latest modules and standards, we create a good and potent mix. In fact, the operative phrase for much of what Emergic is about is value-added aggregation. The innovation needs to be less in new technology, but in how one can best leverage the existing technologies which exist.

    If we think of Emergic as a 40-cent (Rs 20) pizza, then the Thin Client-Thick Server solution creates the pizza base and a 20-cent (Rs 10) one at that! What we need next: the Cheese and the Toppings. That is where the Digital Dashboard and the eBusiness Applications come in.

    Digital Dashboard

    Digital Dashboard is to applications on the desktop and in the enterprise what Samachar.com is to India-related news sites: both bring together everything that users want on a single page. Samachar brought together news headlines from dozens of Indian newspapers on a single page, along with categorized news links. It became the de facto home page for Indians worldwide. What Samachar did was value-added aggregation, leveraging existing standards (HTML and HTTP) to automatically put its page together. What the users saw was that it increased the information that they could process on India by a factor of 10 that is, in the same amount of time that they spent on India everyday (3-5 minutes), they now could get many more headlines and even go to their local city news (perhaps in their native language) by following one of the news links. Samachar also worked because it was one page my belief is that every link that a user has to click on reduces the probability by half or more that the user will actually click on (especially if one is expected to do it every day). Scrolling up and down for reading is still much more easier.

    The Digital Dashboard works at three levels:

    1. It aggregates all the personal information that I need from my Inbox (mail), Calendar (appointments), Contacts, Documents (my recent/frequently access files), and more. This is what Outlook does and what Evolution to a limited extent does. We want to retain Evolution as the write-environment, but make the Dashboard as the value-added read environment. For example, when I do a search, it should do so across my Inbox, IM log, my contact database, files, etc. This is a super-PIM (personal information management) system. It may even integrate with SMS to provide me updates on a cellphone, thus ensuring real-time alerts.

    2. It navigates the space from a PIM to PKM (personal knowledge management). It does so by providing the infrastructure for blogging and RSS feeds. I can now build by third memory (after my own brain and Google). The blog aggregates news, links, quotes, comments. It can also be extended to the enterprise in the form of k-logs (knowledge blogs). So now, I have a writing space (which could even be OpenOffice rather than just a text editor, or even my Mail application), with my creating public, group or private posts. I can even set up filters to take specific actions for posts that come into my weblog. This is more relevant for the third level at which the Digital Dashboard operates.

    3. This is where the blog (the RSS aggregator) also subscribes to enterprise events. Thus, the different enterprise applications can be enabled to become RSS publishers which can be fed to the individual dashboards of various users, after appropriate authentication. This is where the vision of the Information Refinery (or Router) comes in.

    Lets discuss this in more detail. The Digital Dashboard is the framework which integrates two worlds the desktop applications world (Evolution, Mozilla, OpenOffice) and the enterprise applications world (Accounting, CRM, Databases, Spreadsheets, etc.) Today, these two worlds are not glued together. This is where the Digital Dashboard and its collection of glue tools comprising of blogs, RSS and outliners comes in.

    This is an edge strategy. We let the applications be, and do what they are doing best. What we are doing is aggregating all the information from the various silos in a single place. This will initially entail writing adaptors first for the desktop apps and then for the enterprise apps. We want to use the desktop apps for what they do best do not re-invent the wheel, because we have open source components here for mail, browsing and the PIM. However, such a situation does not exist with respect to the enterprise applications. Over time, we will need to think of re-writing the enterprise apps bottom-up in an integrated manner (this is the next topic). The Digital Dashboard works at the edges of the applications but in due course of time become the core the first screen that users see everyday and multiple times during the day.

    In that sense, this strategy is very similar to Samachar: it worked at the edges by screen scraping the existing news sites for the headlines, but in due course of time, become the core, the gateway which funneled traffic on to the various news sites, in effect becoming a news portal. Similarly, the Digital Dashboard will, in due course of time, become the Corporate/Enterprise portal.

    I want the Digital Dashboard to become the killer app which will even make Windows users switch to the Thin Client because it will make them process 10X the information in the same amount of time, and in due course, make them much more productive. The Dashboard software is key to our plans its the connector between the Thin Client-Thick Server world (which anyone else could theoretically replicate since much of it is built out of open source components) and the Enterprise Applications world (which needs solutions specific to businesses and countries, and thus all that we can become are the component manufacturers).

    That is why I think of the Digital Dashboard as the Cheese on the Pizza Base of the Thin Client-Thick Server solution. The Toppings will vary by segment, but the cheese should taste the same.

    Enterprise Software Applications

    Enterprise Software is what every business needs, and yet few can afford it. The penetration of ERP, CRM, SCM applications have so far been limited to perhaps the top 10,000 enterprises in the world. Of course, thats not bad because these enterprises have the millions that the enterprise software vendors and the consultants charge for putting the solution together. The enterprise software applications capture the business processes and embed the information. The problem is that different enterprise apps have their own formats and models, effectively creating silos of information.

    In the world that we are targeting, most enterprises will have just 1-2 applications, with accounting being the most common. Other information may be on the computer, but is likely to be in Foxpro/Microsoft-SQL Server databases or even in MS-Excel.

    What we want to do here is to make available the business software applications that the enterprises need for no more than USD 5-10 or so per person-month. Compare this to the hundreds or thousands of dollars that are paid per seat for enterprise applications today. Our price point will make the apps available to the bottom of the enterprise pyramid and if we are smart (and lucky), we may be able to move up the ladder (but that is not as important).

    We will begin by writing adaptors to standard applications that exist and by defining a common business process reference model which encompasses the key processes, flows and numbers for the different types of businesses (manufacturing, trading, services, etc.). This is again an edge strategy: we are not going and saying we want to replace the application right away. What we are saying is that we can combine data from different applications via the Digital Dashboard to provide you reports and views of the business you may not have seen before. In defining these APIs, we need to leverage two sets of standards: web services (usage of XML, SOAP, UDDI and WSDL) and business processes (RosettaNet and others).

    The next step is to start putting together the actual application building blocks evolving from the enterprise models that we have created and tailored to fit the business process standards. The Enterprise Model we need to build must be event-driven, on the lines of what Tibcos Vivek Ranadive speaks of in his book The Power of Now. We need to think in terms of a (near) real-time enterprise. We should look at the messaging frameworks and application integration being done by companies like KnowNow, Kenamea, Bang and Juice.

    Our enterprise objects would perhaps have 70-80% of the functionality. These are the enterprise Lego blocks which could be assembled by Independent Software Vendors (ISVs) for a customised solution. ISVs will play an important role because they have the last-mile enterprise/industry knowledge and the customer relationship. We should publish the APIs of all our objects so if others build a better object, so be it. This is what Microsoft has done well leverage the developer community. Our success to a great extent here will also depend on whether we can get ISVs to extend (and replace) our enterprise objects.

    Alternately, the enterprise itself could choose to take an existing set of processes from an online library which exists and then customise it. The latter needs the equivalent of a Visual Biz-ic, a scripting-base workflow programming environment which does for business processes what Visual Basic has done for software. We need to make this business rules driven (like what Versata claims to have done).

    Either way, the enterprise events and information flow is to the Digital Dashboard. In parallel, we need to use inter-enterprise standards to streamline document flow based on standards between enterprises using RosettaNet (Basics).

    Our approach here should be like that of a TV serial maker rather than a film-maker: we do want to wait for 3 years in the hope of a blockbuster. Rather, we want to come out with new objects every week, so we can do course correction any time, if required.

    The integrated set of enterprise applications will leverage a common database, wth storage in XML. They will also follow what Ray Ozzie calls the OHIO principle: only handle information once. Data should not be replicated for storage. It is possible for us to think like this because we are building the base set of objects from scratch. We will use open source to make this happen with EJB/J2EE as the development environment, JBoss as the application server and PostgreSQL as the backend database. We should also see how to integrate OpenOffice Calc it is much more than a spreadsheet. We can think of it as a computational engine, with excellent reporting and graphing/charting capabilities.

    The Enterprise Applications thus become like the toppings on the pizza-cheese base. Different segments may want different toppings. Either we can provide the toppings (or the recipes) or others can do their own.

    What Emergic is Missing

    There are many things which we will need to look at over time to complete the picture. I have just outlined some of them here, so we do not ignore them down the line:

    – Communications / Connectivity: look at WiFi
    – Software for Project Management (what we all do), Content Management
    – Website Publishing with eCommerce support for small businesses (like what Trellix offers)
    – Content and Community: an Enterprise Readers Digest meets Slashdot to create clusters of SMEs
    – Customisation for different verticals (eg. Schools, Homes) what will need to be done differently
    – SME Marketplace like what eBay has created
    – MicroFinancing so that SMEs or even individuals can invest in these technologies
    – SME 7-11s: tech shops in neighbourhoods which can also serve as cybercafes, demo centres, meeting points, payment collection centres and wireless hubs
    – Custom Thin Clients, which use cheaper chips to create Thin Clients for USD 50 or so. My hesitation on this is I am very reluctant to get into the hardware R&D business.
    – Optimising the Thin Client-Thick Server protocols in two steps: first, to bring down the LAN speed requirement to 10 Mbps so it will work over 802.11 (wireless) networks, and then bring it down to 1 Mbps so it can work on cable, thus enabling us to target the Home segment.
    – Collaborative Workspaces across firewalls (like what Groove offers)

    Perhaps the biggest thing missing is how we will go to market with Emergic how will be brand, price, distribute, sell and support this not just in India, but in other markets. I dont have many answers right now, but will do so soon. This is where we will need to experiment with different ideas in the next few months.

    Netcores MailServ: A Starting Point

    The Linux-based Messaging Server that we have, which includes support for Instant Messaging (via Jabber), Proxy (via Squid), a basic Firewall, Global Address Book (supporting LDAP), and integrated anti-virus screening. We have now begun work on the next version (4.0), which we hope to have ready by the end of the year. This is the product that is our bread-and-butter business right now, with an installed base of over 100 customers and 300 locations all over India. This gives us the first set of prospects to talk to for Emergic. This is what we have just started to do.

    Going Ahead

    The Thin Client-Thick Server, Digital Dashboard and the Enterprise Applications strategies create the foundation for a new IT infrastructure based on Linux and Open Source for SMEs. Our solution cost will be a fraction of what the big players charge, but in functionality we must not be far behind. It is a strategy used by the Indian pharma companies in the last two decades as they made low-cost drugs available to the local populace (helped no doubt by the lack of copyright protection. In our case, we will build on open source technologies.) A similar strategy has been used by Huawei in China to take on the telecom majors like Cisco, Lucent and Nortel it provides perhaps half the functionality but at a fifth of the price.

    Theres a lot that we have to do. The vision is quite audacious and large in its scope. But I sincerely believe that many things in technology are now coming together to dramatically change computing in the next decade. The Internet was one such 10X Tsunami which brought the worlds computers closer. And yet, a large part of the world is still relatively untouched by technology, largely because it is driven by US companies and dollar-based pricing. This other world is the one that now needs to be impacted by technology. I think of Emergic as the next Tsunami which will brings this worlds people and enterprises closer.

  • Tags: Emergic

    0 responses so far ↓

    • There are no comments yet...Kick things off by filling out the form below.

    Leave a Comment