Enterprise Software: Way Forward

There are two aspects to what we are doing in our vision to create enterprise software applications for the mass market: within the enterprise, and between enterprises.

Within the enterprise, we want to build (a) the software components, (b) the business process framework – what I’ve called Visual Biz-ic, and (c) the business process libraries from different organisations. The layers of the solution will look like this:

Digital Dashboard
Web Browser
Customised Enterprise Modules
Enterprise Components
Basic Software Components
Application Server (JBoss)
Database (PostgreSQL)

The three layers in the middle are what we will need to develop. The Digital Dashboard (comprising an RSS Aggregator and a Blogging tool) comes from the other project that we are doing . All that the enterprise software modules will need to dois to put out events in RSS format.

We need to create the building blocks, and then work with Independent Software Vendors (ISVs) who can take this platform and customise for different verticals. It is possible that to jumpstart this process, we ourselves may need to create the enterprise modules for some verticals.

Across enterprises, we want to use RosettaNet Basics as the business process standards for exchanging documents. While RosettaNet has only been made for certain industries, it is generic enough to be usable by most SMEs. What is needed is for one of the bigger enterprises (which interacts with a lot of SMEs) to mandate the use of RosettaNet for its interactions.

To make this happen, the three areas that we will need to understand well are:
– Web Services: all software we develop should have XML/SOAP interfaces, so the components can be re-used. (An idea here is to take existing open source software components on the Web, and provide them withan XML/SOAP interface.)
– J2EE/EJB: We will use Java as the building platform, with an Application Server (JBoss). Also look at some of the IDEs like NetBeans and Eclipse.
– RosettaNet: for inter-business communications

In the near-term, we need to:
– build an Accouting+CRM module which integrates with Tally, but is architected using the component structure described above. Later, add additional modules for HR, Payroll, etc.
– implement RosettaNet for our interactions with our channel/support partners

Basically, we need to think of “edge services” as we attempt to make inroads into enterprises.

Two ideas which require more thought:
– Enterprise Emulator
– Slashdot for SMEs
Will get to them sometime later.

Published by

Rajesh Jain

An Entrepreneur based in Mumbai, India.