The BIT Conference at UCLA Anderson had some great speakers and diverse mix from academia and industry. Two must see talks here
1. Terry Kramer on the wireless industry
2. Ravi Kalakota on Renovation as compared to Innovation
I was honored to be part of an industry panel. Here is my presentation
Thursday, August 4, 2011
Natural Advantage created for the Service Industry by Cloud Computing
Labels: Cloudcomputing, SaaS, ucla Links to this post
Monday, June 28, 2010
Creating a Two Sided Market in Insurance using Technology
Several people including me had big hopes on Pay-Per-Mile insurance. I even categorized this innovation as an Insurance 2.0 innovation and termed it as part of the next-gen insurance model. After all , Pay-Per Mile gives the ability for carriers to track your driving usage and you as the consumer are passed down the savings. Several agencies had research published claiming that the miles driven could reduce by 10% and a savings of $270 could be achieved. Carriers like Progressive and vendors like On Star launched their products with a lot of fanfare only to find that consumers did not really opt-in for the plan.
The problem, in my opinion, for the limited success of the product is that the benefits to consumer in pay-per-mile insurance product are not clearly articulated and more so, not proven. Knowing that there is a big brother watching you and that your costs could go either-ways (up or down depending on the usage) makes the consumers shy off going to a pay-per-use plan. Instead a better approach for carriers could be to provide a free value added service in return for the customer's allowing the carriers to track the usage patterns. Essentially creating a two sided market where one feeds the other
So here is an example of how this could be achieved. Refer to the diagram below.
In my sample next generation insurance company model below(refer diagram), I am creating a two-sided marketplace between the Commercial Auto (Tow Truck ) and the Personal Lines Auto (Consumers). Each side is feeding the other and also deriving value by joining this new entity. Consumers -Like the ability to have an efficient tow truck dispatch capability on their cell phones. The Tow Truck carriers would not mind sharing their location data when they are shown that they get new business referrals via this technology.
Labels: insurance Links to this post
Friday, June 11, 2010
Spring Roo and AppEngine
I don't really get what springsource is trying to do with the Spring Roo product. Seems like it is trying to be the Java equivalent of the RAILS/GRAILS world; Fast and quick way to develop applications.
But does the approach truly work? I don't think so.
So I decided to look under the hood and build an application. I tried the much publicized Google AppEngine/ Spring Roo Integration. While I could build the scaffolding of the application very quickly, I did not see much value in what Roo did for me. Here is what it does :
1. Builds the Object to Database connection layer with finders and getters based on just the Entity Object definitions.
2. Builds a generic GUI for Data Entry and View.
Now - if you are in the RDBMS world - there is probably some value to automatically creating the scaffolding around capturing the Data Access layer with a tool like Roo. But , if you are working with AppEngine , I dont see the value. Building the Data access layer in AppEngine is super easy already there is not much other tools can do here. You just define your objects with JDO/JPA annotations and you are done. Why would I make comprises in the choice of a programming model when I don't get much from Roo's efficiency. Note that Roo uses JPA only with No DAO layer and uses Aspects.(not everybody in the world likes Aspects including myself)
I liked the idea of building a generic gui for your object model. If this idea would work with any Object Model I create. i.e not something that was generated via SpringRoo then I would be interested in it. Since the gui is more of a testing tool for your Object Model - there is value in having such a gui as a backdoor entry to your data. But the GUI cannot be used even as a starting point for true real-world applications.
IMHO - the only way I see Spring Roo fit into my world if it targets its positioning as the "Microsoft Access for the Cloud" .Afterall , what MS access gives you is an ability to define Tables(Entities) , Edit Data Items and Report on them. Trying to target Spring Roo as a potential Web Application development paradigm does not fly with me.
Labels: appengine, springsource Links to this post
Monday, January 11, 2010
The Business IT Alignment Problem -2009
Tuesday, December 8, 2009
The Cloud is ready but the Enterprise is not
Labels: Cloudcomputing, SaaS Links to this post
Friday, December 4, 2009
If Oracle firewalls mysql
Interesting post today here.
Update: dec 07 - Apparently Oracle says that the new york post report is false.
The OSS route was developing into - I along with others write some software , get some adopotion and then redemption with an Acquisition . Now the redemtion part is questionable.
Labels: opensource, oracle, sun Links to this post
Monday, July 13, 2009
Enterprise IT - The future sales model
In his blog post , Mike Speiser, argues that Small to Medium Business segment is the next growth engine for Software and that Enterprise IT Providers should look out for disruption in their space led by the consumer web revolution.
While I agree with the conclusion of Mike (refer my earlier post that made similar conclusions here) , I do not agree with some of his arguments.
Mike's key argument is that with cost of sales going down ,as a result of the realization of the vision of self service technologies and next-to-zero software distribution costs, it creates an opportunity for new startup's to take advantage of this and hence this is the engine you should be looking at.
I would argue that there is more nuance to selling into SMB than having great self service technology and a cost model based on SaaS. Although people think SMB and Consumer segment are similar as a result of the fragmented nature of the markets , there are actually some significant dissimilarities. SMB's make decisions in groups typically influenced by a large Enterprise facilitator. i.e Doctor's would buy office software that works with the files their hospital uses. Insurance agents will typically buy their Insurance carrier recommended IT software. In a lot of cases Enterprise IT vendors sell to associations and groups ,realizing the actual sale with the SMB business; as a result the assumption that you cannot have direct sales for SMB is not true. Assuming that having better self service capabilities makes their life simpler is also not necessary true. Their life gets simpler with more factors like better integration with their affiliates.
So to play in the SMB technology space you need to have a platform provider that aligns all the relevant players. Microsoft has been this platform provider untill now. People like SAP understood this and focused on the Enterprise Solutions that integrated the SMB into the Enterprise processes but did not enter the SMB space per se.
Google is trying to be the new platform provider as a result of the platform moving to the web. So the opportunity now exists for start-up's the bet on the success of this platform and hence be successful.
Labels: business models, google Links to this post
Tag Interest
- google (20)
- SaaS (15)
- insurance (11)
- open source (11)
- Cloudcomputing (9)
- business models (9)
- web2.0 (8)
- sun (7)
- Amazon (6)
- Information Management (6)
- soa (5)
- BRMS (3)
- BI (2)
- GWT (2)
- ILOG (2)
- business rules (2)
- microsoft (2)
- opensource (2)
- personal auto (2)
- Economics (1)
- HaaS (1)
- IT consulting (1)
- PandC (1)
- Pega (1)
- SAP (1)
- agent (1)
- ajax (1)
- appengine (1)
- chrome (1)
- consulting (1)
- cpc (1)
- databse2.0 (1)
- google apps (1)
- govt (1)
- ibm (1)
- investing (1)
- jobs (1)
- math (1)
- openoffice (1)
- oracle (1)
- outsourcing (1)
- self service (1)
- social software (1)
- software appliance (1)
- springsource (1)
- ucla (1)


