Emergic Software Factory

One way to think about our business is as a software factory, where we work with channel partners who do the hardware integration around the software we provide. There’s no one really offering “software processors” at the lower-end and we can be that. 80% open source, 20% proprietary.

This idea came up as we talked to our MailServ (messaging product) channel partners. Their feedback was they wanted to see the TC-TS and Messaging product bundled both in terms of running on the same server (hardware) but also in pricing. Then I realised they were looking at us as a “software objects” supplier. So I thought maybe we can do more. There is a lot that exists in open source, its just that no one tries to integrate it all together across the entire platform. Thats the opportunity – put it together at 1-10% of what the big so-called SME vendors sell their software for. Start at the bottom of the pyramid and then move up.

Emergic Vision

Emergic is about bringing down technology costs by a factor of 10, and thus become the computing platform of choice for the next billion consumers and other 20 million small and medium enterprises (SMEs) who have not been able to fully leverage expensive and proprietary dollar-denominated technologies.

Emergic is about the other 90% – the people and organisations in the worlds emerging markets. This is where technology has not yet penetrated deeply. Yet, for this 90%, technology offers perhaps the last opportunity to better integrate into the worlds value chain and improve the standard of living for their people.

Emergic is about realising the vision of a computer on every desktop and in every home in every developing country of the world, at price-points they can afford.

Detailed note (written on August 24)

Emergic Software Architecture

Here’s something I put together as a possible software architecture for Emergic:

Emergic Dashboard
Next-Generation Desktop
RSS, Publish-Subscribe, Outliners
Personal and Enterprise Events
Amplify Information Processing by 10X

Emergic Enterprise
Integrated eBusiness Suite
Visual Biz-ic, ERP+CRM+SCM
Web Services, Business Process Standards
Enable the Intelligent, Real-time Enterprise

Emergic Intranet
Collaboration, Content Management
Personal and Group Publishing via K-Logs
Share and Manage Tacit Knowledge

Emergic Freedom
Thin Client Desktop-Thick Server OS
Server-centric Computing and Storage
Desktop Applications, File and Print Servers
Reduce Cost of Computing by 75%

Emergic MailServ
Identity Management, Email, IM
Enable Real-time, Integrated Messaging

Emergic Central
Proxy, Firewall, VPN, Anti-Virus
Secure and Connect the Enterprise

Linux
Local Language Support
Build on Open-source Software base

Billing Relationship

In response to a post on Decentralisation by Kevin Werbach, Rafe Needleman has an interesting comment on WiFi:

My big question regarding WiFi access is, who will bill for it? Ultimately i don’t think end-users will have multiple small WISP accounts. I think the cellcos and telcos are in the best position to extend their billing relationships with their customers.

Which leads to the question: What will they be billing for? Their own hotspots? Boingo’s? The one in my house? I don’t know.

Is it possible to meld the two worlds — the chaotic and wonderful decentralized WiFi infrastructure + the convenient telephone bill?

In much of what we do, we under-estimate the importance of billing, and the implicit relationship that the biller has with the billee. This will become especially importance in the context of our plan to make Emergic as a “tech utility”, which implies that we need to bill at regular intervals of time. Collecting money on a regular basis is a challenge. What if customers don’t pay on time? What does the cost of collection become? Will customers ask for credit? What can we do to make customers pay on time, or even in advance?

Emergic Update

I have been travelling for the past couple weeks so have not done an update on Emergic. Here goes:

Thin Client-Thick Server: Our CD product is ready – its a 3-CD install. Installs the Thick Server and provides the base for doing the Thin Client configurations. Need to do the initial documentation – we’ll be ready with our first beta ready to ship end of the week. Where we have not made much headway has been in getting the first TC-TS sites for installation. Perhaps, by trying to target our MailServ cutsomers, we are going after the wrong segment. They are mainly medium-to-large corporates who already have 1:1 computer:person ratio in their head offices. Most already have paid for Windows licences, and they also have some specific Windows applications which makes it hard for them to switch. Need to think differently about how we should be takling our product ot market and who can be our first customers.

Enterprise Applications: We’ve been working on the Client Information System within Netcore. Have written MS-Excel (Customer Information) and MySQL (Support Information) adaptors to be able to extract data out from these databases (we will do one for Tally for the accounting data later). We’ve also creates the database structures in which to map this information. The development will now be done in Java using JBoss. We’ve also been working on a broader level to map out customer processes and the order mmanagement processes.

Digital Dashboard: We are putting together a dashboard with information from Mail, IM, OpenOffice and the internal (enterprise) blogs aggregated together, along with links to key applications used on the desktop. This is a starting point. Am convinced that a Dashboard is what we all need – “value-added aggregation” which captures all the info we need ona single screen. Will put out a screenshot once we are ready with it.

Plenty of ideas swirling in my head — will put these out in the coming days. We are definitely on the right track, but we do need in the coming months to get some paying customers! At the end of the day, technology is a good thing to do, but money in the bank is the best validation.

Continue reading Emergic Update

Emergic Marketing – Anand

Some more comments by Anand Patwardhan, regarding the market-side of Emergic:

I think it will be important for us to devise unique approaches for different segments of the market. The segments will be important not only for the software design & productization but also for distribution, channel management and the underlying business model. One primary reason for this is the dependence of the TC – TS model on network availability & performance. This factor will pose constraints on the TC design, and therefore on the overall system itself.

For example, I think that in the home segment, we will have to provide some limited application functionality on the TC, because we cannot assume guaranteed network availability & performance. Question is, do we need a HDD, or can we fit the limited applications in DiskOnChip, so that we can go with a simple single board design?

One important segment for us (low-hanging fruit) is hotels. Today, most “business” hotels offer some form of Internet access. It starts from a business center with dial-up access, to a RAS in the hotel (dialup from room), to wireless ethernet, and finally as I saw in Seoul, a dedicated PC in the room with wired ethernet. Hotels are just the kind of controlled environment where we can get our TC-TS environment set up, and ideal for brand-building. We probably have all the pieces already to offer the product – maybe a bit of work to integrate with the hotels billing system (for authentication and for generating a bill for usage).

Another important segment is business centers or cybercafes. In general, my suspicion is that anywhere we have shared Internet access, our solution is ideal – first, there is no element of personalization, people do not expect to have their applications and data available to them. Second, the functionality people expect from the client is limited (because they are
doing a limited set of tasks). Third, having a TS enables much more efficient use of network bandwidth, because you can do local caching and proxy. In a sense, the most difficult segment for us would be one where an individual uses a single PC in a stand-alone fashion (which is really the home).

Continue reading Emergic Marketing – Anand

Anand on Emergic Software

Enclosed below are two emails I received from Prof. Anand Patwardhan (School of Management at IIT-Bombay), who also happens to be a very good friend. The emails provide a lot of food for thought, especially in the context of what we want to do in Emergic and John Robb’s post on the Next Generation Desktop:

Most of the time we need to do very simple information processing tasks – write a letter, send an email, do some arithmetic, play a game. Sometimes, we need to do something more complex. This is as true with software as it is with hardware. And it is as true for enterprise software as it is for application software.

First thing we need to do is to separate the function from the application. That is, separate the task (or function) of writing a letter from the use of MS Word. To do this we need a different architecture for the applications, one in which functions can be invoked as required (again, server side computing will help here). Having done, this we perhaps also need to change the front-end completely from a computer-oriented desktop to a task or function oriented desktop. The digital dashboard should actually become a functional tool. Perhaps one could use a diary (personal blog format) to maintain the context, rather than a file system. So that even when I’m writing a letter, the previous context is available to me. Actually, I’m not completely sure about this – to the extent that we have migrated the office metaphor to the computer – tasks, corresponding to folders, individual items to files, I dont know if we can move completely to a diary orientation.

Second, we need to have a lot of application integration at the back end. So, that many things can happen automatically on the server side. For example, format conversions, or other kind of processing (virus checking etc.).

The second email:

It is actually very hard for developers to think of a user who is not like themselves. We are actually not representative users at all for Emergic. We have been used to a situation where we had to end up knowing a good bit of computers to really use them, and in situations where we dont, we are almost at the mercy of the machines, or the support people / system administrators. For a “real” user, the computer is a tool, to perform tasks or functions. Ok, so this is nothing new (Don Norman – Invisible Computer, Dertouzous – Unfinished Revolution), but what does it mean for us, and what can we do about it in practical terms?

So, with this in mind, let me try and put down what I think the Thin Client (TC) desktop should look like and do.

The TC desktop should have a diary, a writing area and a set of icons for functions, and a “command interpreter” of sorts for non-standard tasks. What might the standard tasks be? Depends on the user segment. I can think of groups of tasks, for example, communication tasks (email, chat, message), daily tasks (these are all related to the “diary” metaphor – would include, for example, to-do lists and appointments, daily accounts, and notes). Accounts is actually important. By this I dont mean Tally, nor do I mean MS Money and Quicken, but a simple tool where I can enter expenses and receipts and which understands what is being put in. MS Money and Quicken are good examples of what happens when we put everything but the kitchen sink in the application.

There is also a group of “common tasks” – this really depends on the context. Might include writing by default – but even there, customization is possible, for example, for secretaries there may be a separate button called write letters. This button might invoke the same application, but with a letter writing module, but in any case, the user should not worry about what is being run. If we really go segment-wise, I think we will find that are are a fairly limited number of tasks in all, spread over these three groups – communication, daily and common.

When it comes to the UI, in a sense, the advantage of Linux for us is precisely that it is modular and customizable. That is, we can layer our own UI over the X server.

Many of these ideas have been tried by Apple, but then it is a single piece – you cannot take apart the hardware / software bundle and reconfigure and reprice it the way you may want for the particular set of users you want to address.

This brings me to my next point, going beyond the UI to the application architecture and design. A product like MS Word is extraordinarily powerful and feature-rich. This is because the designers have had to figure out in advance all of the ways in which a user might use Word, because once the application is out there, it has to function by itself in whichever environment it is and for whatever use it is being put to. Emergic needs an application architecture which on the other hand, caters to really the least common denominator, only the core set of
features that all users will need. It needs a unified way to store data (perhaps XML), so that other applications can also access it and work on it for special purpose tasks. We need to be able to customize the application very rapidly – server based computing is an advantage here, as we dont have to worry about modifying the application on 100’s of clients.

We need to replace feature-richness and consequent design costs by rapid specialization for particular settings.

So, as I see it, Emergic really starts looking like a software solution now, with a UI component (partly server based and partly on the TC), an XML-based data model for data storage and handling, and core and extended applications invoked by the user. There is, obviously, an OS there, but completely transparent to the user on the TC.

Many enterprise (and even consumer) applications are based on the notion of “automation”. Sure, some things can (and should be automated). But what I think is more important is for IT to assist the user, and not only automate. In trying to automate, we are in fact making it more difficult for people to use IT in the first place. Because, for example, we are asking business logic to conform to the information model embedded in the ERP. If you recall, this was exactly the difference between a transaction processing system and a decision support system that was brought out during our SME survey.

Whew, I think thats it for now! Btw, feel free to put the emails I’ve been sending you on Emergic – I’ve no idea how to create a blog, but I’d be happy to get and respond to comments.

Meeting with Traction Software

I also met with Traction Software yesterday – with Greg, Chris and Jordan. Traction has a very interesting enterprise blogging platform – and I use the word platform with care. It has its roots in the work done in hypertext over the past decades and creates a very rich environment. For us who thrive in information, it works like magic with all its cross-referencing, “collection” and ease of publishing. A must-look if one is looking at collaborative applications with a blogging base.

Greg made an interesting point on his blog after the meeting: “It was very refreshing to talk with Rajesh this morning. He has a very clear, simple and direct way of making his points, while communicating a personal sense of his values and commitment. I’d call it his reality enhancement field in contrast to Steve Job’s well known reality distortion field. The experience made me reflect on the personal aspect of blogging that I find valuable: it’s the ability to use a cultivated record of the sources, insights and opinions of people I choose to trust (including me!) as a non-intrusive source of facts, opinions, and more effective understanding of their point of view.”

The one thing I am convinced about is that the blogging revolution and its use in enterprises is just beginning. Just like the web and home pages began as a consumer thing and later began being adopted by enterprises (initially through the efforts of small teams or even individuals running skunkwork operations), I see blogs penetrating deep into the enterprise – to a point that they will become invisible and embedeed in what we do as information workers.

John Robb on Emergic

Yesterday, I had a wonderful meeting with John Robb of Userland. John is one of my favourite bloggers, and it was a delight meeting up with him. We had a great 2-hour session on the world of blogs and software. He has posted his summary of our discussion on the K-logs Yahoo Groups (you must join it if you have interest in knowledge management or weblogs). Have reproduced it in its entirety here.

Dear K-Loggers,

Yesterday, I had the distinct pleasure of meeting Rajesh Jain, the CEO of India’s Emergic, at my home (in the midst of a double birthday party for two of my lovely daughters). Rajesh is working on building a desktop for the 80-90% of people working at corporations in developing countries that don’t have PCs yet.

The problem is that in order to extend PCs to the vast majority of employees at these companies, the cost of software and hardware needs to come down to around $200 a desktop. He is already working on sourcing older PCs that cost $150 a pop. By putting Linux on them, they are nearly as powerful as new PCs we buy today with Windows (Windows has a lot of overhead that radically slows the performance of a PC). Next, he needs to be able to build almost every type of application people would need on a PC for under $50 a year. He needs Swiss
army software.

The solution of course is to build applications as websites on the desktop. Given that people he is selling to don’t have a legacy problem (they aren’t already using existing last generation apps like Office, ERP, CRM, e-mail, etc. from the major vendors nor are they likely to), the opportunity is to provide them a new, more functional experience. His idea, which I think is wonderful, is to put K-Logs at the center of the desktop for these employees and surround them with digital dashboards that connect them to the data they need to do their job. Search, very much like a Google on the desktop, would tie it all together.

Basically, the K-Log would serve as the routing system for employee data entry. This means, that employees could enter data into the system using a browser-based interface and route the data to where it needs to go (to one app
or multiple apps). This creates a single point of data entry for KM K-Logs, ERP, CRM, financial, and e-mail. All entries would be logged on a personal K-Log (a time-organized back-up brain). Some entries would be published to a central K-Log on the Intranet for general consumption by other employees (KM). A digital dashboard would enable employees to see data on sales, financial performance, e-mail, supply information, news, etc. All of that data would arrive as RSS subscriptions or Web Services delivered in real-time (all data displayed could be easily subscribed to ala carte — also data could be annotated and added to the K-Log through a simple post procedure).

The advantages to this approach are too numerous to list.

Although initially, much of this may be centralized, the longer term vision is to totally decentralize it. So, in five years, the standard PC used by a large percentage of the employees in the world may be running Linux, Radio (which includes a database, content management system, development environment, and web server that runs on the desktop — Swiss army software), and web apps powered by centralized Web Services built by Emergic.

Nice!

Note: It was so great to talk/work with someone that really didn’t care about all the buzzwords spewing out of the big technology companies. We are all so overmarketed in the states, particularly in regards to software, that most of us don’t realize how really bad or nonfunctional most of what we buy is. Buzzwords, jargon, branding, etc. totally cloud our judgement. Legacy systems and mindsets freeze us in place. Unfortunately, I think we are stuck with it. Rajesh is planning to build a system to allow companies in emerging markets to leapfrog us in terms of the productivity, flexibility, and functionality of their information systems. I expect tales of woe in five to seven years about how America missed the opportunity to reinvent software but didn’t. Fingers will be pointed, particularly given the billions that were spent. It would be interesting to see Microsoft, IBM, and Sun treated like GM, Ford, and Chrysler were 17 years ago when Japanese imports crushed their marketshare.

John has summarised Emergic’s Vision better than I ever could have!

Emergic: The Vision

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.

  • Emergic Update

    Thin Client-Thick Server: We have deployed the TC-TS at one of our other offices, which has 6 users. The usage pattern is quite different, it being an administrative office- there is more use of OpenOffice and Tally (a popular Indian accounting package). We did manage to get Tally returning on Linux using Wine, but are having problems with printing. We did have a few teething problems needed to upgrade the LAN to 100 Mbps and the server. Within our office, we are moving users to a dual CPU system. There is still the occasional crash, and we need to get to the bottom of why it happens. Have also done a few demos, but still no definitive beta customer. Need to make the TC-TS into a CD-installable product. Also, need to try out different Windows applications on Wine (especially Foxpro, VB-apps, Microsoft SQL). In our R&D effort, need to do (a) a graphical booting process for the TC (b) Local Apps on the TC to reduce the bandwidth (c) understand the X protocols better to see where we can optimise network traffic (d) Wireless LAN support.

    Digital Dashboard: We deployed the weblogs platform internally for about 15 people in the company. People have begun blogging, but most posts are either to the private or the group blog. There is something missing in the flow here, and we need to make it easier for people to do it, and create the collaborative space. Weve also studied Traction and Scopeware. Traction has some interesting concepts. Our next step here is put together a DD in a browser which encompasses an aggregation for much of the users personal information (links to recent mails, IM buddies, frequently accessed files, bookmarks, calendar, contacts, etc.) the idea being that the respective application would be launched from the DD. The user gets a snapshot of his home directory and personal information in one page. This becomes the first layer, adding to the other layer of enterprise blogs which weve already done. The part which needs thinking is how to fit this together into a scalable architecture, like that of the Information Refinery. Weve also spent some time studying XSLT and the XML format of OpenOffice Calc. The idea of the latter work is to see if we can use OO Calc as a computation engine without actually invoking OO.

    Enterprise Software: Weve been working to put together a model and a plan (and a team). The Digital Dashboard (personal and executive, which would comprise enterprise events) is the first step. Next is to put together a business process model for the basic applications. EAI and B2BAI come in later. More practically, we need to continue to work on building the Client Information System which integrates information from accounting (Tally), marketing (spreadsheet) and support (MySQL database). Weve also put together a working platform comprising Rational Rose, ArcStyler, Weblogic and JBoss. It is a mix of commercial and open source tools the former give us an idea of the best tools, while the latter is what we need to actually use. One idea I need to think through is that of an Enterprise Emulator like a SimCity which simulates an enterprise ecosystem. This would be useful for us as a testbed for the software we develop.

    MailServ: We have decided to begin work on version 4.0 of MailServ, so as to get it ready by the end of the year. Need to put together the feature list of what we want. They key features our current 3.2 version has are: Mail Server, Proxy Server, IM (through Jabber), basic Firewall, Anti-Virus software, Global Address Book (via LDAP). Some initial ideas: enhance the Proxy Server capabilities, add Collaboration (Calendar, Contacts, Group Scheduling) such that the backend storage is in XML and can later be integrated into the Digital Dashboard, Project Management, stronger Firewall capabilities and perhaps, VPN support.

    BlogStreet: We are at about 10,000 blogs. Need to think if we want to deploy additional resources on this. Ideally, Id like to see this work with blogs within the enterprise, but we are not there yet.

    My Blog: We need to do some clean-up on some mess-up which we have done with the database (result is that some posts now have incorrect categories and the search results show duplicates). Going ahead, need to get Related Stories for each post that I do, thus creating a chain of thoughts and stories. There are a few other ideas also: for example, it would be nice to add a blog page consisting of the headlines for the major publications; make Search more effective I use it quite a lot when writing my Tech Talks and am unhappy with the limited control htdig gives me (I at least need to get relevant posts in reverse chronological order today, it seems quite random!). More broadly, how can I do value-added aggregation to build up a niche in the blogosphere. There needs to be something innovative which I should think of. Overall, am quite happy with the posts, etc. I have now blogged for pretty much all of the past 100 days with an average of 5-6 posts daily. Now, to think of how we can raise the standard of Emergic.org. Perhaps, we need to add a discussion forum like Slashdot for discussing topics relevant to technology in emerging markets. Theres still too much of just me talking, though of late the comments are increasing.

    East Asia Trip Update

    A few thoughts from my recent visit to Hong Kong, Beijing and Bangkok, and meetings with companies. Much of the discussion relates to the Thin Client-Thick Server product that we’ve been working on. Overall, I think we are definitely on the right track with the TC-TS and other Emergic ideas. Need to now sustain the development and productisation, and take it to customers within India and outside.

    1. Need to be able to give a demo on a single notebook: “seeing is believing”. If not a single book, I should be able to make my notebook the TS and use one of their clients as a TC (ie, make the bootup floppy and do the configuration, even connecting both to a hub). We should be able to set this up in no more than 10-15 minutes.

    2. Productisation of TC-TS is very important. We need to do this my mid-September — be able to send a set of CDs with documentation.

    3. We need to get some beta customers and then some paying customers: this increases everyone’s confidence that we have a “commercial” proposition, rather than just an interesting tool.

    4. What people find very interesting (and which they havent thought of) is the idea of using old PCs. It also means we need to figure out the second hand PC supply chain, to ensure a stable supply.

    5. I am becoming inclined towards a “utility” type pricing option – a subscription price for hardware and software combined. We will also offer the software separately, but the customer should see a solution, and not have to buy hardware and software separately. This needs more thought.

    6. 802.11b (Wireless LAN) is the way we need to offer connectivity. Wiring up with cables can get quite expensive. WLAN cards are dropping in prices – available at USD 40-50, with access point for about USD 125-150 (or even less). Expected to go down further. This also means we need to optimise our solution to work well on a 10 Mbps connectivity and not 100 Mbps since 802,11b works at 11 Mbps. Later, we need to get the speed requirement down to 1 Mbps for cable connectivity (especially if we target the residential market).

    7. Think: what if Microsoft makes Windows free for developing markets, and/or reduces the price of MS-Office. From my point, our solution does 3 things: (a) reduce hardware price needed (b) reduce software price (c) increase manageability. There is no equivalent solution which does all three things.

    8. Need to see if we can use TVs as display. Can we modify the TV output stream (for video) so we can do better than the 640×480 fuzzy display? TVs are there everywhere, and this saves the price of a monitor in some segments.

    9. The User Interface has to become better. We should learn from the Mac OS X interface.

    10. What is going to be our business model? How are we going to sell/distirbute the TC-TS?

    11. We could even talk later to some CPU companies (eg. Intel XScale, Via) for making custom motherboards for TCs based on their chips.

    12. We should also look at an interim “Boot-off-the-CD” TC, since this can help reduce the traffic flow across the Network.

    13. Blogs are still an unknown quantity. But I think they will become critical for knowledge sharing in the coming months. Ray Ozzie (Lotus Notes creator and now CEO of Groove) has been blogging a lot on these areas recently. His mantra: OHIO – Only Handle Information Once. Thats the philosophy we need to use for our Digital Dashboard and Eneterprise Software.

    14. To do business in China, we must know Chinese language (read, write and speak).

    On a lighter note, did do some sightseeing: Great Wall and Forbidden City. I found both somewhat underwhelming. One thought that struck me: The Chinese emperors seemed to leave a lot less ostentatiously than our local Maharajas! In fact, I think India has a lot more attractions that greater depth and variety but we have just not leveraged our heritage enough, as compared to the East Asian countries.