A Utility Approach

The more I think about it, the more I think that in Emergic we will need to go to customers with a solution which (a) integrates hardware and software, and (b) offers computing on a subscription basis.

Companies want a solution – they don’t want to think of Thin Clients and Thick Servers. We need to be able to go and provide them the complete computing infrastructure, not parts and labour. Also, the market we are targeting is not a “rich” market – for them, paying monthly also will enable them to see tangible benefits (and returns) in terms of productivity and the investment they are making on technology.

So, we need to think of what we are doing in terms of the following groups:
– Software Factory: the software development group
– Integrators: create a solution by combining hardware and software
– Services: the value-added development that some clients may need
– Financing: directly or indirectly, since the end-users will pay monthly

As of now, we know that with some work, the software for the Thin Client-Thick Server can be a disruptive innovation. But that’s as far as the tech goes. What is needed is also creativity in terms of how we are going to integrate and sell the solution. We need to get 100 out of 100 things right to succeed!

That’s the part I like best about a start-up. One is, at times, competing with oneself in coming up with new ideas. There are no establish pathways to walk on. One has to imagine the future and then build it. This blog is helping me document some of these decisions and the thinking that is going behind each of them. A year later, I’ll be able to reflect on what we did right and where we went wrong. That’s a great way to learn. Hopefully, by thinking aloud, we minimise the possibility of making mistakes.

The canvas that we want to build is large, very large. It is in creating the computing platform for the next 500 million users. We’ve just taken a few baby steps towards where we want to go. But its exciting enough already. I know we can make a big difference in the world of computing in the developing markets. We can be a disruptive force, a positive one. The game is for us to play and win.

Software Factory

Have been travelling this week, hence updates may be a little less. But one of the side benefits of travelling is that it gives me time to think and reflect more deeply on what we are doing.

I think there is a definite opportunity to build a “software factory” which leverages the used PC base. Just as Microsoft focuses the latest hardware for its software, we can think of creating software for hardware which is 1-2 generations (3-7 years) old. The benefit of this is that the hardware costs almost go down to zero, making their use possible in areas which were previously out of reach because of the cost — emerging markets, for example.

The world is going to see a huge supply of old PCs which is going to be available. What will be required is to streamline this into a “market” so it becomes possible to buy one easily. Also, one needs to standardise performance into layers so that they fall into 2-3 segments and can be used for different purposes (one as a Thin Client, one as a Firewall, one as a Home Router).

The Software Factory thus is built on the following ideas:
– software should work great on old hardware (PCs and other hardware)
– it is built usin Linux and open source
– the software components are modular and integratable (like Lego)
– it is “emergent”: the whole is greater than the sum of the parts
– it leverages the latest standards (web services, RosettaNet, RSS, J2EE…)
– others (independent software vendors) can build on it

The Software Factory will sell to the “bottom of the pyramid” — emerging everything (markets, enterprises, consumers…). These are the untapped markets.

Emergic Update

BlogStreet: We have launched a beta with the Blog Neighbourhood Analysis and a listing of the top 500 blogs at http://www.blogstreet.com. We will not be doing further development for now. The site should grow its blogs automatically. Need to step back a little and think what we want to do next. The basic technology developed needs to be (later) applied to within enterprises for the blogs.

Digital Dashboard: We’ve launched blogs internally for 15 people in our company. Have built this on MovableType. Have enabled private, group and public blogs. RSS Aggregator is also available for all. Now, lets see if people blog!

From next week, we will have a unified update for BlogStreet and Digital Dashboard called “Information Refinery Infrastructure (IRI)”. In the near-term, we want to look at Traction and Scopeware. We also want to do IM-based blog notification. In parallel, also do a more detailed study on XSLT.

Thin Client-Thick Server: We have begun talking to organisations outside to get beta customers where we can deploy the solution. Initial reaction is quite positive. In Aug-Sep, we need to get 8-10 different organisations where we can do a beta.

Enterprise Software: Have been examining various platforms for the development. We’ll be using a mix of some commercial tools for the initial work and then port to open-source software. The idea is to (a) get our project – Client Information System – done, and (b) get a sense of what the best development tools do.

Emergic Update

The big development of last week was thinking through the Information Refinery (IR) concept, which will now serve as the framework on which much of the software will be built. The TC-TS can be thought of as the underlying infrastructure on which the IR will be built. The two are like the equivalent of an enterprise Windows and Office. We still need to detail out the architecture in much more detail, but for the first time, we now have a vision which integrates the world of blogs, RSS syndication, events and enterprise software.

BlogStreet: We will be putting out the beta in the next few days. It will have a blog neighbourhood analyser and a listing of the top 500 blogs. We’ve also created a service wherein anyone can request the related blogs given a blog URL. Quite useful – made me aware of some more blogs which I should be reading regularly!

Digital Dashboard: We will be launching blogging internally within our company using MovableType. People will be able to set up private, group and public blogs. This will also have the RSS aggregator.

Going ahead, the two projects will be merged into what we will call the IRI (Information Refinery Infrastuture) – will see if I can come up with a better name!

One of the early tasks will be to create an RSS-ifier, which given a URL gives the RSS feed. This is important because when we need to get content for people to read and post into the RSS aggregator. There are many sites which do not produce an RSS feed. We will use some of the proglet ideas which we have used earlier to get blogrolls and related blogs for screen scraping to get the headlines from a page. Also this week, need to put together the roadmap for developing the IRI, especially the architecture.

Thin Client-Thick Server: We managed to get Tally to run on the Linux Thick Server. It is a round-about way, but at least we were able to do it. This came up because without Tally it would have been difficult to get people to use the Thin Clients in many companies. With this, we can now deploy the TC-TS at our first external location this week. We’ve also formed a Productisation group to bridge the TC-TS engineering efforts and the market needs.

Enterprise Software: We’ve decided to do an internal application which is on the lines of a client information system (outlined in the IR post). To begin with, we will integrate information from accouting, marketing and support on a single page per client. This will use the blog and digital dashboard base. We may also use one of the commercial application servers (probably Weblogic) initially for development, and then later switch to JBoss.

Going ahead, we will thus have 3 product development groups: the TC-TS as it exists now, IRI and the Enterprise Apps. Will fine-tune this in the coming week. Am also thinking of setting up a small RD team which looks at some new ideas like 802.11b.

Information Refinery

Much of what we do as information/knowledge workers is process information. We get it from multiple resources, we assimilate it, we route it to others, we translate it into different formats. In fact, in the enterprise, we can think of business processes as rules for routing information, as tracing the flow of events through various filters and actions. In essence, we have information ores which are refined by the enterprise. What we have been thinking about in BlogStreet and Digital Dashboard can now be encapsulated into the concept we will call an Information Refinery.

Whether it is news items or blog posts or enterprise events, the information refinery should be handle to handle all of them. The refinery consists of the following entities:

Miners

Just likes ores need to be extracted from mines, RSS miners collect the RSS feeds from different sources. Miners listen to sources which send the raw, unstructured information to them, or extract information through bots. They then take the information and send them to specialized adaptors for RSS extraction.

Adaptors

These are the interfaces to the outside world. A 1-way Input Adaptor takes events and RSS-ifies them for use by the refinery. A 1-way Output Adaptor takes an RSS feed and converts it into events suitable for use by an external application. A 2-way adaptor does both. In other words, from the point of view of the refinery, an Input Adaptor is read-only and an Output Adaptor is write-only. The 2-way adaptor is read-write.

For example, there are Blog 1-way adaptors which will take RSS feeds from weblogs (or create RSS feeds if one does not exist). We can think of News Adaptors which take a URL for the site, and make an RSS feed comprising the headlines. A Mail Adaptor can read from an email message and convert to RSS. A File adaptor can take information about the file and create an RSS feed about it (extracting perhaps the first few sentences from the file as the description). We can think of a Tally (or Quicken) 1-way adaptor which extracts information from the application and creates RSS events (using financial reporting standards) which can be fed into the information refinery.

As of now, some news and blog sites put out RSS feeds. But most enterprise applications are not publishing RSS. This is what we will need to develop. Thus, the Adaptors will need to know (a) the I/O formats of the proprietary applications, and (b) the vocabularies that the segment uses. For starters, we should think of 1-way (read-only) adaptors which enable us to aggregate the raw material (information ores) from multiple disparate sources.

RSS Spoolers

They take the RSS feed from the adaptors. They take subscription requests for the feeds through Agents. An agent is instantiated for every subscription request. Agents have rules to decide what to do. For example, Rams agent can decide that he wants the News.com and WSJ RSS feeds in full, while he wants all other entries with the keyword XML in them. The agents look at each of the incoming feeds and take the appropriate action. They route the RSS feeds/entries to other RSS spoolers or RSS Aggregators.

RSS Aggregators

There is one RSS Aggregator per subscriber/entity which is the end consumer of RSS feeds. Think of these as comprising one set of end points (the other being the information sources). RSS Aggregators have an RSS Store (database), for archiving older entries. They can publish the aggregate feed to an RSS Viewer. Or, then can send the RSS entries to Processors.

Processors

They embed business logic/ rules as to what action needs to be taken with RSS feeds. For example, they can send events to an Alerts engine to notify the user via email/IM/SMS, or create other RSS events. As such, processors can thus also be considered as information sources which put out RSS feeds for re-distribution. Processors can also work on the RSS store to create specialised applications (eg. Talent Search in an organization, Business Process Analytics to see how information flows and where the potential bottlenecks could be).

RSS Viewer

This shows all the RSS entries organized by source or time to a user, who can then decide if he wants to either delete the entry or publish it to a blog. An RSS Viewer should be capable of having multiple pages to support categorization of the incoming entries.

Blog Publisher

This uses the Blogger API to post events to a blog.

Blog Platform

This is a weblog tool like MovableType or Radio which enables management of the blog. A blog should be capable of having multiple categories (with sub-levels). The user can decide on the access rights for the categories (public, private, group). It should also be able to publish RSS feeds for specific categories.

Digital Dashboard

This is a browser with 3 tabs: one for viewing the RSS Aggregator feed, one for writing and one for viewing a users own blog. It is the unified read-write interface.

Putting It All Together

What the information refinery creates is a peer-to-peer architecture of information sources and RSS routers, filters and processors. Initially, we should look at starting at the edges this means, that let the enterprise applications do their own thing. What we want to extract from there is an RSS feed which can be aggregated with other feeds and put forward before the user. We should not focus initially on trying to create the information. As an analogy, Samachar.com did the aggregation of news content through using templates and a single page as the viewer. It did not try to create the content. Similarly, we need to create adaptors and miners for the various information sources that are there (news sites, blogs, mail, enterprise applications) to aggregate them together.

One of the first applications we can consider for application within the enterprise is the following: create a Client Information System, with a weblog which has one page per client to aggregate financial, technical, marketing interactions, support and external news together.

– Extract accounting events from Tally (cheque deposited, payment made, etc.)
– As marketing and support people interact with a client, they write the conversations or forward the mails to the client blog page. If they need to write, they should write in their own space, and then publish to the client blog.
– Invoices sent should be linked as files from the blog, with a brief summary of the contents. Invoices are sent by the marketing department.
– Scan various newspapers and magazine RSS feeds to search for news relevant to the client.

This way, there is a (reverse) chronological history of all interactions with the client in a single page, across the diverse groups in the company. Today, this resides in different mail folders of people, and different applications and spreadsheets. This is one example of how the Information Refinery can streamline the raw data ores to create an integrated emergent system, where the whole is much greater than the sum of the parts.

There are, perhaps, many knowledge management systems and corporate portal applications which could do something similar. The difference in the approach we have taken here is that this can be built in a very general-purpose manner (and even customizable easily at the interface points like Processors), it encourages users to continue what they are doing with the only addition of writing they will do this because they will derive significant value from the system, since it creates a positive feedback with the information flow, it can be put together quite quickly, and it leverages the existing enterprise applications.

The key is to first start at the edges and create the unified viewing interface (the digital dashboard, as it were) a read-only interface, but with information aggregated from multiple sources. In general, in organizations, there are 10x more readers than writers (i.e, one person may update the accounts information, but there are likely to be 10 people relying on that information for analytics and decision-support). The next step is to enable two-way communication into the applications, so the Digital Dashboard can also become a writable area which interfaces to applications. This is as a precursor to then replacing the expensive non-integrated enterprise applications with integrated web services- compatible components.

Whats missing in here is a more detailed discussion on how business processes can be reflected and managed through this information refinery, and how we can use business process standards as embedded in RosettaNet.

This approach is obviously not going to work for every organization. The main target are the SMEs, who today use very few enterprise applications. They can now, over time, be given a full suite of applications through a common interface. Just as the browser created the front-end which became a window to the web, with HTML and HTTP taking care of the backend, similarly, we want the RSS-driven Digital Dashboard to become the enterprise information workers front-end with the back-end being composed initially of adaptors to existing enterprise applications and later of newly minted web services compliant software components which embed the appropriate business logic and work together like Lego blocks.

Taken together with the Thin Client-Thick Server project which creates the IT infrastructure providing connected computers for all, the Information Refinery and its constituents provide the framework to build the Real-Time Enterprise for SMEs. The price point is what Ive talked about in the past: all the hardware, software, support and training thats needed for no more than USD 20 per person month. This, according to me, is the next real opportunity, and the vision that we want to work towards in Emergic.

Emergic Update

Have done separate updates for each of our projects:
– Blogstreet
– Digital Dashboard
– Thin Client-Thick Server
– Enterprise Software
– My Blog Enhancements

This weekly update idea works out quite well. It enables me to take stock of the situation, and by putting it up on the blog, it also gives all who are working on the prject, a clearer idea of my thinking. Every once in a while, I need to make sure I trace back to ensure that all the good ideas are being captured and implemented, and we aren’t letting some slip through the cracks.

Emergic Update

Last week was a slow, testing week. Progress was incremental. Though one thing has become increasingly clear to me: we are on the right track. This is a long journey. There are going to be some good weeks and some not-so-good weeks. Last week fell somewhere in between.

BlogStreet: There were some dramatic performance improvements, and one can actually see neighbourhoods of about 1000+ blogs. Need to iteratively build this through to 10,000+. We ran into a problem with haywire bots, and are working to fix this. Also, code reviews and optimisations. This week, we will begin with the Blog Auto-Categorisation. Once we do that, then we are ready to do a beta of the site.

Digital Dashboard: Problems with different kinds of RSS feeds slowed us down in the RSS Aggregator. But, we did get a first implementation of the deletion of entries in the feeds. This now makes it possible for me to view only the new entries: a big jump in terms of usability.

Thin Client-Thick Server: We are trying to get the hardware and software RAIDs working. This is important because data on the server cannot be lost. We also want to put in place testbed with a “data recorder”, so we can better debug problems when they come. Moved two of our marketing staff to TCs, and are now working through the OpenOffice compatibility issues.

Enterprise Software: We gained a better understanding of JBoss and RosettaNet this week, both building blocks. This process will continue in the coming week.

A Linux user switches to Windows

Writes Tony Collins:

After three and a half years of trying to make GNU/Linux work on the desktop, I’ve decided that it’s simply too hard for the average home user. Before I go into my reasons for going back, let me outline what I believe an ‘average’ home user is. Mr Joe Average is someone who wants to install their OS, boot it up, and it works. He wants to be able to upgrade his PC , and have the hardware work in a few short minutes. He wants to read email, browse the web, talk to his mates online, and play some games.

Three and a half years; that’s how long I’ve been trying to make Linux work on my desktop computer. Hear now my sad tale of why Linux isn’t suitable for my desktop.

Also see: Slashdot comments on the story

Emergic’s Markets

It is important to understand the entry barriers for using Linux on the desktop, and then work on breaking down each one of them. The key thing to note is that in Emergic we are not trying to switch users from Windows to Linux (or thick desktops to thin clients), but open up computing to the non-users.

In countries like India, 9/10 people in the workforce do not use computers. Thats the target market. The first-time user. The goal should be to delight a new user, rather than disappoint an existing user. Linux will never match Windows with the full functionality. But it is a “good enough” solution with an amazingly attractive price point.

We don’t want to create a world of pirates in emerging countries. We want them to respect and pay for software. But the price has to be right. Not many can afford to pay USD 1,200 for a new thick desktop with Windows and Office. However, if we can bring down that price to USD 200 for a Thin Client with Linux, it can now become attractive for the mass market in SMEs.

That is the key to Emergic: opening up new markets for computing, getting the next 500 million users in the world who are all in the world’s emerging markets — at the “bottom of the enterprise pyramid”. What we need to think of is how we address the needs of this market.

We need to find the people we can delight with the low-end solution. It is a market which can pay pennies, not dollars. But it is a hungry market. It too wants to taste computing. Emergic is about creating solutions for these segments.

Platform Permavantage

I was listening to Warren Buffet in an interview on CNBC. When asked why he did not invest in technology, he had a very interesting answer — he could not tell who would dominate technology in 10 years. It wasn’t clear if there was any such thing as a long-term competitive advantage.

I thought of a word for this – “permavantage” (permanent advantage, like permalink). Look at the past quarter-century in technlogy (that may be too short a time-frame in Buffet’s world, though). The baton for technology leadership keeps shifting. IBM, Compaq, Microsoft, Cisco, Oracle, Nokia, AOL,Yahoo — everyone has seen leadership come and leadership go. Today, each of these companies faces challenge going ahead. Leave alone visibility for the next decade, many of the companies don’t have visibility for the next quarter!

So, is there such a thing as a permavantage? I think there is, and that comes from owning a platform. Microsoft has succeded in doing that with Windows and Office, though I think it will be hard pressed to maintain that with the next set of PC buyers for whom cost considerations will be of paramount importance. Intel owns the CPU platform, but as the ground shifts to a graphics-intensive world, it too is being threatened by Nvidia. Nokia now has to worry about companies like Samsung because it never really built a platform in cellphones. Brand yes, but not a platform. In fact, all the technology leaders have great brand, but to build a sustainable advantage, what is going to be needed is platform leadership.

That’s what we will need to accomplish in Emergic. We have to think of Emergic as a platform for the technology needs of the world’s emerging markets. Building one or two products may be easy, but building a platform is going to be our greatest challenge. To succeed means getting a hundred things right, and not a single one wrong. Only one company in the past quarter century has managed to come close — Microsoft.

The basic vision of Emergic can be summarised in 3 sentences:
– a computer on every desktop and in every home – for no more than USD 100
– all the software needed for USD 5 per person month
– combine the bottom of the (enterprise) pyramid into emergent networks (where the whole is smarter than the sum of the parts)

Emergic will definitely need to build a brand on the marketing front, and a platform on the technology front. There is an opportunity in the world today — as companies look inward and focus on how to survive the downturn, we need to think disruptively and innovatively to build out Emergic as the Next Technology Platform, covering Computing, Software, Communications and Business Processes.

Emergic Update

BlogStreet: We’ve got three things ready in BlogStreet: (i) a Blog Neighbourhood Analyser, which given a blog gives you its friends as analysed through the blogroll and bloglinks on its home page, (ii) a Blog Search which is keyword-based and covers the home pages (iii) Blog Ranking, wherein every blog is given a rank based on its count among the blogrolls. We’ve botted about 1800 blogs. Our program is a little slow, but we are working to optimise it. We should make it available this week. We also have links to a blog’s RSS feed, with the ability to add into an RSS Aggregator. Plan for the coming week: auto-categorisation of blogs.

Digital Dashboard: Last week, we built on the RSS Aggregator to ensure we’d catch most formats. We also added a feature which lists the collective list of blogs being subscribed to by others in the group (enterprise). The key feature which needs to be added now is the Delete option, so it will enable the viewing of only the new entries in the feed (on a per-person basis). Once this is ready, we should (a) make the post option work with Radio and Blogger.com, in addition to MopvableType, and (b) making this available as a hosted web service. The combination of BlogStreet and Digital Dashboard should make it very interesting for bloggers.

Thin Client-Thick Server: Last week, we began our productisation efforts. We are now working towards making an installable set of CDs. This means automating all the steps we had done manually over the past 2 months. We’ve made substantial progress on this front and should have a first-cut CD ready this week. Have also been seeing how the Windows Terminal Server option can be used to provide Windows support for those who may need it (on the Linux Thin Client desktop). We’ve also been testing both hardware and software RAID. This should be the work we’ll be finally moving the Marketing team to Thin Clients.

Enterprise Software: We’ve been doing a study of EJB, J2EE and JBoss (an open source application server). Have also begun a review of the business proces standards – ebXML, RosettaNet and BizTalk.

This Blog: We did a few enhancements: Categories, Search which goes directly to an individual post and GoogleBox. Next up: adding a ListServ so we can send out emails, auto-posting the day’s traffic info to the blog, referer analysis and upgrading to MovableType 2.2. I also created a private blog.