Marketing Memos

March 15, 2006

Is there a market for enterprise mash?

Mashups are a hot topic among consumer content providers and others struggling to find revenue from the Internet.  For the uninitiated or semi-conscious, a mashup if the amalgamation of different online data to create new usefulness.  Zillow  is the newest and most popular concept, bridging pubic record data on home sales with satellite photographs, and offering a pictorial view of how one’s homestead is faring as a personal piggybank.

Combining previously isolated data to create new insight has been the hallmark of IT software since Moses was in short pants.  But IT software is often impenetrable, written using incompatible technologies, siloed in dissimilar databases, and undocumented to the point of uselessness.  The effort to bridge any two pieces of highly relevant information has been so
painful that it was only attempted when there was provable economic value to the enterprise, or when the CIO’s medication wore off.

The Weird Wide Web is not thusly hampered.  People are creating mashups for the sheer sport of it, and because a lot of content providers are using service oriented architectures (SOA) to make mashups easier to construct.  Even semi skilled, and semi erect programmers can cobble together a web site that borrows on-the-fly content from Google, Amazon, Yahoo and others to create
new value from seemingly disconnected data.

And that may just be the hot, new IT software market - Enterprise Mashups (copyright 2006, Guy Smith, all rights reserved, so send royalty checks directly to me).

SOA adoption in the enterprise is still nascent, an the Enterprise Mashups are a prophesy. But enterprises have a distinct advantage in that they can (and will) expose more corporate data through SOA as part of cross-application integration efforts.  With very little extra thought and/or work,
generalized services can be created that may not have any current use, but which will be available for consideration by other developers.  Thus new capabilities and insights may well be garnered by in-house or third party developers mashing together data that either nobody had before contemplated, or which had been just too darn difficult.

And herein are the markets for Enterprise Mashups:

  • Packaged application mashups:  Add-on tools that exploit
    services exposed by well known ERP, CRM, m-o-u-s-e packages to create new
    business dashboards, ad-hoc investigations, and even business processes.
  • Internal/external mashups:  Tying together public services
    from the Internet and services from packaged or in-house software.
  • Business facing external mashups: Combining publicly available
    services into information abstractions useful to business.
  • Internal mashups: Mainly a services play where business
    consultants create necessary data aggregations from internal services to
    create specific in-house competitive value.
  • Portals: Create a generalized mashup portal, or rent one out ala
    Software as a Service (SaaS).

The genesis for each of these approaches is most likely to be based on industry verticals — uniting information to create more meaningful insights is almost always uniquely tied to the type of industry consuming the data.  There will be horizontal plays where broad swatches of information are combined for universal purposes (human resources planning is an example).  But industries that live and die by data, that have specific data services, and thus can create unique mashups . . . they will be prime targets for generating demand.

Now, where did I put that XML reference manual?

March 2, 2006

Sue Microsoft?

Last year, members of the community created an Open Source patent pool, where they intend to store patents, trademarks, patent pledges, and other Intellectual Properties (IP).

Should Microsoft and Sun be worried?

A while back, I described the growing signs of the software apocalypse, and
speculated that Gates and McNealy might be preparing for litigious warfare
against their common enemy, Linux.  The Open Source community appears to
have created a defensive shield by gathering together their own IP.

It would be categorically insane for OSDL and friends to launch a first
strike against Microsoft and the rapidly setting Sun, but a defensive
counterstrike is both possible and reasonable. As IBM taught us so long ago in
their fight with the Feds, and recently in their fight with SCO, wearing your
enemy down to a nub with a barrage of claims, discovery, motions, and a league
of lawyers is a sound strategy.  Death by a thousand paper cuts if you
will.

What should Microsoft and Sun do?  You will note that they were not
contributors to the Open Source IP pool, but perhaps they should be.  If it
ever comes to a duel between lawyers, it helps to know your enemy, and you tend
to get to know someone you sleep with.  Could or should OSDL snub patent
contributions by Sun or Microsoft?  Were I running OSDL (and thankfully I’m
not), I’d decline their phone calls much less their software.

The tasty corner case within my demented speculation would be the OSDL
counter suits.  What if OSDL held IP that either Microsoft or Sun had
leveraged, however innocently?  What if the community could demand an
injunction on all new Windows sales?  What if they could extract payment
for every Windows license Microsoft had sold?

If I were Bill Gates, I’d learn how to play nice — damn fast.

 
Contact    Site Map    Search    Privacy    Copyright